I still haven't been able to track down a cause for ^, do you happen to
remember anything?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/1570#issuecomment-1696001800
You are receiving this because you are subscribed to this thread.
M
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/2634
-- Commit Summary --
* Polish the build process docs a bit
* Drop an extraneous Dependencies section from the spec manual
* Add a build tunables section to the refere
This is a nice-to-have and not critical for 4.19, dropping the milestone.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2471#issuecomment-1695406039
You are receiving this because you are subscribed to this thread.
Message ID: ___
On a related note - kinda inspired by this: #2632
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2617#issuecomment-1695197487
You are receiving this because you are subscribed to this thread.
Message ID:
As pointed out by @dralley in
https://github.com/rpm-software-management/rpm/discussions/2374#discussioncomment-6826927:
we support indexed db queries for "pkgid" and "hdrid", which are actually
backed by SIGMD5 and SHA1HEADER tags. These aren't really security sensitive
because they're just an
Oh, those... Thanks for the reminder. We'll indeed need to figure what to do
with those because they are even indexes in the rpmdb.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/discussions/2374#discussioncomment-6839182
You are receiving th
Network access in both build and install scriptlets is basically a packaging
bug as the result depends on external factors, and various build-systems
already enforce this on top of rpmbuild. I see no reason we could or could not
do this on the rpm-level already, both for build and install-time s
