rpmrebuild 2.20: rpm2archive called with incorrect arguments
the problem is fixed in 2.21 release
rpmrebuild 2.21 (stable) released
updated web pages for 2.21
web page for 2.21
skip install test for gpg-pubkey packages
add a tool to get fedora spec file
add fedora 41 tags
yes, it looks like older versions of rpm2archive does not support "rpm2archiv $Package | tar ..." and mention only cat $package |rpm2archive - | tar ... I just rewrite the line in the RpmUnpack function
the code is already fixed in the devel branch. Il will release th 2.21 in june
Do you have an ETA on 2.21? I just encountered this bug on AlmaLinux 9 trying the rebuild RPMs built on a CentOS 7 machine (it builds a CentOS 7 component, packages it, then wraps it in an RPM to install on the AlmaLinux 9 server it is downloaded from). The issue is CentOS 7 cannot create the RPM with the proper SHA256 Header and Payload digests, and as a result will not install in FIPS mode... This project solves that problem for me, I just need to be able to tell my build containers to pull release...
Thanks for the quick fi! BTW, it appears that RHEL9 is based off of Fedora 34: https://docs.fedoraproject.org/en-US/quick-docs/fedora-and-red-hat-enterprise-linux/ which is quite a bit older than Fedora 41.
Merge branch 'feature/rpm2archive' into devel
fix rpm2archive syntax for rhel 9 (Blair Zajac)
fix spec file
Merge branch 'feature/multi_line_spec_change' into devel
add src/t/data files
allow multiline spec changes
I am developping rpmrebuild on fedora (currently 41) and I was not able to reproduce the problem - my arch is x84_64, so I can't rebuild bash-5.1.8-9.el9.aarch64.rpm - I have no problem with bash-5.1.8-9.el9.x86_64.rpm but your change is valid and pass my regression test, so it will be included in 2.21 release
cpio turns absolute links into relative links
the 2.20 version is public
rpmrebuild still cannot rebuild packages with backslash in the filename
fixed in 2.20 release
gpg key signing package or source is expired
I'm using RHEL9 and the manual page gives these examples: EXAMPLES rpm2archive glint-1.0-1.i386.rpm ; tar -xvz glint-1.0-1.i386.rpm.tgz cat glint-1.0-1.i386.rpm | rpm2archive - | tar -tvz Here's my reproduction recipe: $ wget https://sourceforge.net/projects/rpmrebuild/files/rpmrebuild/2.20/rpmrebuild-2.20-1.noarch.rpm/download $ mv download rpmrebuild-2.20-1.noarch.rpm $ sudo dnf install rpmrebuild-2.20-1.noarch.rpm $ wget https://download.rockylinux.org/pub/rocky/9/BaseOS/aarch64/os/Packages/b/bash-5.1.8-9.el9.aarch64.rpm...
rpmrebuild 2.20: rpm2archive called with incorrect arguments
The man page of rpm2archive gives several examples of use : rpm2archive glint-1.0-1.i386.rpm | tar -xvz cat glint-1.0-1.i386.rpm | rpm2archive - | tar -tvz the fist line is the way rpm2archive is used in rpmrebuild code, so the syntax should be ok and my regression tests ( in t/rpmrebuild_basic.t file) do not fail. could you send a full output of the failed command : rpmrebuild with args and output ? So I can try to reproduce, fix and add more regression tests
rpmrebuild 2.20: rpm2archive called with incorrect arguments
I'm glad rpmrebuild-2.20 was released, it works fine on my machine. Thank you very much for your work and best wishes to you!
rpmrebuild 2.20 (stable) released
change date and version in html
Merge tag '2.20' into devel
Merge branch 'release/2.20'
release 2.20
Merge branch 'feature/fix_backslash' into devel
add diag on test 42
- bugfix comment missing with spec-only on rpm file
add tags from fedora 41
you can use RPMREBUILD_NOQUOTE on some distribution if filenames contains meta-car
fix build on fedora 41 (buildroot)
Good !, it's better, because it is now the same as on my own fedora. I will now work to finalize the 2.20, because the 2.19 (and before) do not run at all on fedora 41.
gpg key signing package or source is expired
This is the debug message for a failed run
This is the debug message for a successful run.
I don't know what's happening to my machine, I promise I haven't turned it on since the last time I tested it.I tested rpmrebuild-2.20 today by first undeclaring the RPMREBUILD_NOQUOTE environment variable (since I haven't booted the machine since the last time it was declared), and surprisingly, it worked! And it fails when I declare the RPMREBUILD_NOQUOTE environment variable...
ok now it is time to use the debug mode. Could you run the same command with adding the option "--debug". The output should contain a line such "DEBUG: workdir : /home/eric/.tmp/rpmrebuild.62361/work". Make a tar of the given directory, and post it here. I will try to analyse it.
And then, as you say, I tested again with the RPMREBUILD_NOQUOTE environment variable, but for some reason, it still failed...Is it because I'm having some problems with my fedora machine?
I apologize for the late reply.I downloaded the tarball you provided and unzipped it, rebuilt deco-archive-1.7-17.fc40.noarch.rpm using the unzipped rpmrebuild.sh, unfortunately, it failed.
Could you test the 2.20 version. Tell me if the "normal" command works on deco-archive, and if npt successful, test again with the RPMREBUILD_NOQUOTE environment variable : export RPMREBUILD_NOQUOTE=y rpmrebuild.sh -p deco-archive-1.7-17.fc40.noarch.rpm this workaround fix the problem for me on Mageia linux.
Hi, I have worked on 2.20 version
Merge branch 'feature/comment_missing' into devel
bugfix : the comment-missing option was not working on rpm files
- tests : clean generated files
Yes, there's no problem with tar: rpm2archive droid-hal-*.rpm tar -xaf droid-hal-*.rpm.tgz The link is still intact. Can you tell me approximately when the release will be? Thanks for the reply.
Okay, I'll wait for the release. Thank you for your work.
The 2.20 still needs some work : so probably between 1 and 2 months. But I can provide sooner a pre-release with rpm2archive code (the code is already written and tested)
cpio turns absolute links into relative links
Cpio is now a legacy code with bugs which will be never fixed (man cpio on fedora). So in the next release (2.20), rpm2cpio will be replaced by rpm2archive and tar command. Could you give an example, to check if the problem is fixed with tar ?
cpio turns absolute links into relative links
Merge branch 'feature/fix_mo_translation' into devel
bugfix : the comment-missing option can only apply on installed packages
Merge branch 'devel' into feature/fix_mo_translation
add info on buildroot
I think it should be some kind of configuration somewhere, because I have the same problem on another linux. Now I have to find where, and it will be difficult.
bugfix on dir handling (from tests)
no error on chmod : use RPMREBUILD_IGNORE_FILE_ERROR
Amazing! Why is my fedora 40 machine not running successfully? Is there something wrong with the fedora 40 image I'm using... Could you please share the address where you got the fedora 40 mirror? I would like to reinstall a fresh environment and try again. Thank you very much!
previous change was only working on installed packages
remove warning : Explicit %attr() mode not applicable to symlink
I checked on a fresh fedora 40 vm : the 2.19 release is working on deco-archive package. I have changed the user, changed the locale : it works. I now have to understand what is the difference with mageia 9
rpmrebuild loses all translation files
I had a test on vim-common package with rpmrebuild 2.19 on fedora 40 $ rpm -ql vim-common | egrep '.mo$' | wc -l 42 $ rpmrebuild vim-common ... result: /home/eric/rpmbuild/RPMS/x86_64/vim-common-9.1.719-1.fc40.x86_64.rpm $ rpm -qpl /home/eric/rpmbuild/RPMS/x86_64/vim-common-9.1.719-1.fc40.x86_64.rpm | egrep '.mo$' | wc -l 42 so on vim-common, no translation file is missing could you provide a package name example ?
I was able to reproduce the problem on another linux distribution (mageia 9). And I am installing a new fresh vm on fedora 40 to check.
Here are the details of my OS(fedora 40)
I think I have rpm-4.19.1.1-1 on my computer.
Merge branch 'master' into devel
use package in data directory
more detailed list
cpio is legacy, replace it by tar (rpm2cpio => rpm2archive)
rpmrebuild still cannot rebuild packages with backslash in the filename
I have tested the 2.19 again on my computer (fedora 40) on same package and it works. The only difference I can see, is that I have installed (upgraded) the rpm package, and you are using the code from the tar. Is there any installed rpm version ?
rpmrebuild still cannot rebuild packages with backslash in the filename
gpg key signing package or source is expired
Hello I now have a gpg key and sign with subkeys The subkey validity is short (one year) and changed every year : $ gpg --list-key F80D3B85029F2DACC6A8469A364644463D1079A1 pub rsa8192/0x364644463D1079A1 2022-07-22 [C] [expire : 2029-07-21] F80D3B85029F2DACC6A8469A364644463D1079A1 uid [ ultime ] Eric Gerbier eric.gerbier@tutanota.com uid [ ultime ] Eric Gerbier gerbier@users.sourceforge.net sub rsa4096/0xBE1EE0FE980514B7 2022-07-22 [S] [expire : 2025-07-22] sub rsa4096/0xFAA7EA370084E0DB 2022-07-22...
Will rpmrebuild support filetrigger?
the new 2.19 release includes the merge from the github branch thanks to point the missing tag and the github code
rpmrebuild cannot rebuild packages with special symbols in the filename
the new 2.19 release includes this bugfix thanks to report and for the patch
rpmrebuild 2.19 (stable) released