Re: [Rpm-maint] [rpm-software-management/rpm] No debugsource with static archives (Issue #2763)
Works for me in a Podman container: ``` # source /etc/os-release; echo $NAME $VERSION_ID openSUSE Tumbleweed 20231204 # rpmbuild -bb a.spec ... # rpm -qlvp /usr/src/packages/RPMS/x86_64/asd-debugsource-0-0.x86_64.rpm drwxr-xr-x2 root root0 Dec 6 11:10 /usr/src/debug/asd-0 -rw-r--r--1 root root 20 Dec 6 11:10 /usr/src/debug/asd-0/x.c ``` -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2763#issuecomment-1842664529 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] Add tag with %{NAME} of SRPM (#1364)
I wonder if we can just have some extension tags to easier access the parts of `sourcerpm` that do the parsing for you. That would also work for old packages (if only with the new rpm binary) -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/1364#issuecomment-1842591776 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] perl.prov mistakenly adds embedded Parse::Yapp::Driver (Issue #2221)
Those generators are something we would happily hand over to a Perl community maintained perl-rpm-macros package. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2221#issuecomment-1842586288 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] [RFE] rpmbuild should present machine parseable failure reports (Issue #2769)
I don't think we will get really machine parseable error reports as many errors are just spit out by random scripts. Also errors will almost always stop the build. So there will only be the first real error being reported. But the error reporting can be better. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2769#issuecomment-1842578177 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] EXDEV error with rename(2) on overlayfs (Issue #2355)
Closed #2355 as completed. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2355#event-11165589193 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] EXDEV error with rename(2) on overlayfs (Issue #2355)
Anyway, it turns out this is not something we'll want to handle explicitly in the RPM code as it's really OverlayFS-specific. I'll close the ticket now. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2355#issuecomment-1842511015 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] EXDEV error with rename(2) on overlayfs (Issue #2355)
Oh... Indeed. Dunno what I was thinking. The correct workaround is this: ``` # cd /usr/lib/sysimage # cp -r rpm rpm.temp # copy-up onto the upper layer # mv rpm.temp rpm # move back to the original path so RPM can find it # rpmdb --rebuilddb ``` Thanks for noticing! -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2355#issuecomment-1842506848 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] No debugsource with static archives (Issue #2763)
Distro is openSUSE Tumbleweed 20231202 amd64. -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2763#issuecomment-1842487050 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] No debugsource with static archives (Issue #2763)
What distro are you running? -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2763#issuecomment-1842484754 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] No debugsource with static archives (Issue #2763)
This looks like some kind of RPM macro (mis)configuration on your system. I've tried this in a Fedora 38 container and it worked fine for me. The `%debug_package` macro isn't necessary on Fedora since it's enabled by default in the `/usr/lib/rpm/redhat/macros` file shipped by the `redhat-rpm-config` package. In fact, if it's used explicitly like in the above SPEC, the build fails due to a "duplicate" debuginfo package. So after commenting that line out: ``` $ rpmbuild -bb a.spec ... Wrote: /root/rpmbuild/RPMS/x86_64/asd-debugsource-0-0.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/asd-0-0.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/asd-debuginfo-0-0.x86_64.rpm ... $ rpm -qlvp /root/rpmbuild/RPMS/x86_64/asd-debugsource-0-0.x86_64.rpm drwxr-xr-x2 root root0 Dec 6 09:11 /usr/src/debug/asd-0-0.x86_64 -rw-r--r--1 root root 20 Dec 6 09:11 /usr/src/debug/asd-0-0.x86_64/x.c ``` Alternatively, removing `redhat-rpm-config` and enabling the debuginfo-related macros by hand yields the same results: ``` # rpm -e --nodeps redhat-rpm-config $ rpmbuild --define '%_enable_debug_packages 1' --define '%_debuginfo_subpackages 1' --define '%_debugsource_packages 1' -bb a.spec ... Wrote: /root/rpmbuild/RPMS/x86_64/asd-debugsource-0-0.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/asd-debuginfo-0-0.x86_64.rpm Wrote: /root/rpmbuild/RPMS/x86_64/asd-0-0.x86_64.rpm ... $ rpm -qlvp /root/rpmbuild/RPMS/x86_64/asd-debugsource-0-0.x86_64.rpm drwxr-xr-x2 root root0 Dec 6 09:13 /usr/src/debug/asd-0-0.x86_64 -rw-r--r--1 root root 20 Dec 6 09:13 /usr/src/debug/asd-0-0.x86_64/x.c ``` -- Reply to this email directly or view it on GitHub: https://github.com/rpm-software-management/rpm/issues/2763#issuecomment-1842484102 You are receiving this because you are subscribed to this thread. Message ID: ___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
