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
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:
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
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
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
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
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
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:
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: ___
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
10 matches
Mail list logo
