> We could make `%autosetup` use this behavior by default when `-n` isn't
> present, though. It's a "do-what-I-mean" change that would be beneficial for
> most.
That would bring it in line with the way `%forgeautosetup` behaves. I assume
that would be beneficial to both.
--
Reply to this emai
> Note that because of compatibility concerns, we'd probably want this new
> behavior in a new macro.
We could make `%autosetup` use this behavior by default when `-n` isn't
present, though. It's a "do-what-I-mean" change that would be beneficial for
most.
--
Reply to this email directly or v
The height of embarrasment with this crash is that rpm has zero use for the
uid/gid info in this case, we could just skip the rpmug lookups entirely
because the uid/gid is never written to the archive, only the names are.
--
Reply to this email directly or view it on GitHub:
https://github.com
@pmatilai converted this issue into discussion #2829.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2827#event-11368466735
You are receiving this because you are subscribed to this thread.
Message ID:
All that data is in the header, which you cannot split without breaking
signatures and digests. Which you want to be able to verify even for installed
packages too.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2827#issuecomment-1873
Thanks for the report and backtrace. The rpmug thread-unsafety is of course
painfully obvious, that it ends up called during the threaded packaging
operation less so because the call happens from librpm side. It's curious that
nobody has run into this before now. The core issue has been there si
> We should support all the same features for a file list entry here, which
> also means being able to handle regular expressions.
We don't support regexes in a `%files` entry, though, only globs.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/r
Background:
During the daily use of the RPM, the RPM database is abnormal. However, the
cause is unknown. In some cases, the `rpm --rebuilddb` cannot ensure the
complete recovery of the database. For recoverability and locatability, I think
database backup functionality can be added for the foll
