packit action create-archive / fix-spec-file
See original GitHub issueHi,
I’m hitting an interesting issue with packit actions. I wrote simple action to create a tarball.
15:55:44.931 utils.py DEBUG STDOUT: restraint-0.1.41-1-5-g7889493
15:55:44.931 upstream.py DEBUG version = restraint-0.1.41-1-5-g7889493
15:55:44.931 upstream.py DEBUG sanitized version = restraint.0.1.41.1.5.g7889493
15:55:44.935 upstream.py DEBUG name + version = restraint-restraint.0.1.41.1.5.g7889493
Using user-defined script for ActionName.create_archive: ['make', 'packit-tgz']
15:55:44.935 utils.py DEBUG cmd = 'make packit-tgz'
15:55:45.582 utils.py DEBUG STDOUT: SRPM=$(tito build --tgz --test -o . | tail -1 | awk -F'/' '{print $NF}'); \
echo $SRPM
restraint-git-5.7889493.tar.gz
15:55:45.582 base_git.py DEBUG Action command output: ["SRPM=$(tito build --tgz --test -o . | tail -1 | awk -F'/' '{print $NF}'); \\\necho $SRPM\nrestraint-git-5.7889493.tar.gz\n"]
Created archive: restraint-git-5.7889493.tar.gz
Docs says is expected to return the created archive name. If there are more steps, then one of them has to return the archive name.
Checked!
I don’t have create-patches - default. I don’t have fix-spec-file - default. Exec fix_spec
15:55:45.583 base_git.py DEBUG Running default implementation for ActionName.fix_spec.
14:55:45.716 upstream.py DEBUG new %setup line:
%setup -q -n restraint-restraint.0.1.41.1.5.g7889493
14:55:45.923 upstream.py DEBUG present srpms = {PosixPath('/home/mastyk/work/github.com/StykMartin/restraint/restraint-restraint.0.1.41.1.5.g7889493-1.fc31.src.rpm')}
14:55:45.924 utils.py DEBUG cmd = 'rpmbuild -bs --define _sourcedir . --define _specdir /home/mastyk/work/github.com/StykMartin/restraint --define _srcrpmdir /home/mastyk/work/github.com/StykMartin/restraint --define _topdir /home/mastyk/work/github.com/StykMartin/restraint --define _builddir /home/mastyk/work/github.com/StykMartin/restraint --define _rpmdir /home/mastyk/work/github.com/StykMartin/restraint --define _buildrootdir /home/mastyk/work/github.com/StykMartin/restraint restraint.spec'
Accordingly to fix-spec-file docs first step should be Replaces Source0 with a local path to the generated tarball
. Well, name of my tarball is different and I reported it. Is this behavior intended?
Regards, Martin
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Actions | Packit
Packit supports actions, which can be used to change the default implementation of some steps in the workflow. Packit is able to execute...
Read more >CacheLib/.packit.yaml at main
Pluggable in-process caching engine to build and scale high performance services - CacheLib/.packit.yaml at main · facebook/CacheLib.
Read more >PackIt
Shop PackIt for stylish lunch bags and boxes where the entire bag freezes! PackIt is the only foldable, freezable bag that keeps food...
Read more >Buy Freezable Soft Cooler Lunch Bags with Zip ...
Purchase a PackIt freezable lunch bag. Roomier in all the right places. Its expanded width and depth easily fits two of our new...
Read more >Freezable Lunch Bag
Purchase a PackIt freezable lunch bag. Roomier in all the right places. Its expanded width and depth easily fits two of our new...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I am sorry, but I am really not sure about the outcome of this issue.
I’m going to close the issue, but if you feel something is missing on our site, please don’t be afraid to reopen or (ideally) create a new issue with the more specific request. Thanks in advance!
@StykMartin @TomasTomecek did we discuss this last week? Can you remind me the resolution?