Man pages are for documenting options and arguments, and --nodebuginfo is a
POPT alias changeable through configuration, not an executable option.
Documenting POPT aliases as if they are options misses the entire raison d'etre
of POPT aliases.
--
You are receiving this because you are subscrib
rpmbuild --root should do what is expected, namely do a chroot into the prefix
before running scripts.
Yes chroot(2) requires root, thank you POSIX. To preserve the mantra "Never
invoke rpmbuild as root" behavior, rpmbuild should drop root privileges, and
switch back to root only when needed.
See issue #510 for how to deal with rpmbuild running in chroot's without
networking: the AMQP (or other message queue) broker fdno can be opened by
rpmbuild before doing chroot(2) exactly like what is done with multiple fdnos
in use by Berkeley DB with rpm --root.
--
You are receiving this bec
POPT aliases should be documented, just not in the man page. Just saying ...
Producing debuginfo is a form of de facto stripping: there are build root
policy scripts that can be run if symbol tables in binaries are to be reduced.
--
You are receiving this because you are subscribed to this thre
Note that POPT aliases are documented with rpm --help ... Including i18n if
gettext is used correctly.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/497#issuecomment-4128
RPM makes extensive use of POPT aliases: there are easily 2-3 problems solved
recently with a POPT alias.
The review process for patch acceptance usually involves a comment/suggestion
to update the man page.
Adding a separate "POPT aliases" section to the rpm man page that was populated
using
The diversion could be as simple as extracting the section on POPT aliases from
rpm --help and including in the man page section. Retrofit nroff man doc markup
if you wish prettier documentation.
(aside)
The master copy of rpm man pages was written using docbook markup that can
generate man pag
You have traded a memory leak for a segfault.
Meanwhile the issue is minor. The only reason I noticed was trying to provide
assistance to someone who was actually trying to use the "internal" interface
to add tags to headers.
I will add an RFE for using loader maps to ensure "internal" is not e
Without some goal, I cannot do a patch.
Possible goals are:
1) minimal effort: use the existing domain but change to use dgettext() with
explicit domain everywhere.
2) minimal size for library domain: use a different marker for the library
domain, tuned to code paths used by, say, rpm-python.
FYI: popt built in RHEL7 causes rpm5 segfaults: ask Neil Gompa.
The issue is whether the strings in the returned argv string array are
separately malloc'd or concatenated in contiguous memory. So rpm and POPT need
to be compiled the same way.
Rpm4 will be affected if/when I do a POPT release. Y
Users will logically look in man pages to find documentation yes.
Documenting the ability to extend rpm options for convenience is useful for
both users and developers.
Knowing that some modes in rpm are implemented by execing, say, rpmsign, using
POPT functionality, where the well-documented a
If you like the suggested argument markup, then a patch is possible.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/475#issuecomment-413186378___
Issue #487 was closed because a symbol in a library was deemed "internal" but
was exposed in the library and available for linking.
Adding a loader map when creating libraries can/will prevent "internal" symbol
leakage.
--
You are receiving this because you are subscribed to this thread.
Reply
Exceptions preserve existing interfaces, are mostly not too invasive, and a try
... catch paradigm is widely used and "intuitive" (for some nerdy definition of
the word).
otherwise sure, add additional arguments and error indicators to test while
unraveling the call stack on the error path if y
(aside)
It's rather amusing for this author to read "optimization" patches to
macros/argv code when I know quite well the reasons the code was written the
way it was. E.g. bsearch(3) was used as a store largely because of many other
uses of bsearch(3) in rpm (i.e. consistency), and because code
We are working at cross purposes afaict.
Your test case adds a non-existent file to a manifest called junk.
Add a path to an existing *.rpm in order to test whether --nomanifest disables
the reading of a package contained in a manifest.
--
You are receiving this because you are subscribed to t
There is no attempt to test the bit set by --nomanifest at lib/rpminstall.c
lineno 550.
See the equivalent code that reads manifests in lib/rpmgi.c for the test that
needs to be done.
Another part of this bug is that afaict, "nomanifest" is in the query/verify
table which SHOULD scope to only
Ok, the checkin you pointed me too is close to what I am looking for.
However, there is no sign of that checkin in the code I am reading here:
https://github.com/rpm-software-management/rpm/blob/master/lib/rpminstall.c
--
You are receiving this because you are subscribed to this thread.
Reply t
There is no way to reopen an issue closed by a repository owner (per Google
search)
See details at issue #458: basically there is no indication of the commit you
cited in the code that can be browsed at github.
The checkin looks correct, but it is impossible to tell what is happening.
--
You
The patch is correctly applied in this tree:
https://github.com/rpm-software-management/rpm/tree/0e6c5e890460224f455c0ef9e516ea675b00208d/lib
The master branch code displayed through Github is rather different than the
tree from Feb. 2009.
--
You are receiving this because you are subscribed
Thank you for pointing out where the test for --nomanifest is performed.
I do suggest that all the code in rpminstall.c is in need of simplification for
clarity.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://githu
Again my bad: you are correct that the symbol cannot be linked.
What is surprising to me is that there is no longer any obvious low level API
to read rpm package sections provided in the API.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or vi
Closed #513.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/513#event-1792518590___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Loader maps instead of RPM_GNUC_INTERNAL might have some advantages maintaining
an ABI: everything is collected in one location, and a naming discipline (like
"rpm*") with exceptions becomes easier to focus on.
Meanwhile retrofitting an ABI that is maintainable onto old code is painful,
thankle
While assessing whether I should submit a patch to simplify rpminstall.c to use
an rpmgi argument iterator, I find that it is no longer possible to query a
package on the network.
The intent of the refactoring in rpminstall.c and rpmgi.c clearly indicates a
desire to remove rpmio from rpm entir
Entirely equivalent to the scheme above, and perhaps more general, is a glibc
RFE for the ability to attach an opaque vector to a FILE * fp. The scheme
originally outlined could possibly be done without any significant change to
glibc internals: the ability to retrieve an opaque pointer from an
The COPYING file -- such as it has always been -- specifies dual licensing for
code in lib/*.
This leaves the license subject to interpretation, and a strict reading would
render code in build/* or rpmio/* only available under GPL.
A looser reading, keeping in mind the intent was to permit othe
Recent issues -- the pending PR for speeding up rpm kernel builds and the
addition of fsync come to mind -- lead me to ask up front:
What approaches to speeding up rpm installs are deemed acceptable?
The techniques (event loop and/or threads and/or coroutines etc etc) are very
well known.
But
I was referring to using fsync wrapped in an event loop (and on rotating
media), and was referring to rpm, not system, performance. Avoiding blocking
system calls by using non-blocking alternatives in an event loop is what nodejs
does.
Rpmbuild and rpm both do loops over package operations and
This RFE tries to provide a concrete example to known bottlenecks with rpm
install/update mentioned in issue #517.
MQTT is Yet Another Message Queue (YAMQ) like ZeroMQ, or AMQP, or M$ MQ
developed by IBM with a client implementation maintained in the Apache
Foundation.
Message queues are typic
To forestall the obvious objections to using MQTT, please note that I also have
working code for SysV messages, POSIX message queues, AMQP, ZeroMQ, etc.
I also am quite capable of an implementation of asynchronous RPC similar to
above in XMLRPC, jabber, or UNIX domain sockets, or protocol du jou
This RFE is an attempt to document two important remaining known issues that
need to be solved to use LMDB in production.
The issues are:
* file path indices may exceed limits imposed on the size of keys by LMDB
The solution was already suggested by Howard Chu in Fedora bugzilla: use a hash
on
Again this RFE is a result of assessing how to send a patch to simplify
lib/rpminstall.c
It is very clear that years of refactoring has managed to remove almost all
ability for rpm to access the network (the one exception I can find is in
lib/rpminstall.c)
Meanwhile the rpm.8 man page still do
Your comment makes no sense.
RPMIO depends on glibc functionality.
You cannot be uninterested in glibc-specific solutions without also being
uninterested in replacing RPMIO with stdio
Replacing RPMIO with stdio routines was the entire point of this RFE.
--
You are receiving this because you a
Closed #287.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/287#event-1797439542___
Rpm-maint mailing list
Rpm-maint@lists.rpm
The patch to use big endian hdrnums with LMDB is insufficiently general:
hdrnums need to become big endian everywhere, for all back end databases, since
the values are exposed in the API.
Closing.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
Closed #504.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/504#event-1797451440___
Rpm-maint mailing list
Rpm-maint@lists.rpm
I don't need to try network access to know what flaws there are.
Ok we will deal with the issues case by case
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/521#issuecom
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/522___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mai
Reproducer:
rpm --import 0x12345678
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/523___
Rpm-maint mailing list
Rpm-maint@li
You might try code reviews before doing pull requests in the future.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/458#issuecomment-414291751
At one point in time, the rpm CLI supported URLs everywhere that file arguments
were permitted.
Refactoring to remove network support has now limited the places where URLs are
permitted.
E.g. It is not possible to do "rpm --query http://host/package.rpm"; any more.
Either document that URLs ar
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/525___
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mai
In order to implement RPM+BDB, before DBCONFIG existed in BDB, rpm had to
implement a configuration paradigm for the myriad tunables supported by BDB.
Using DBCONFIG to configure BDB is well supported for many years now: there is
no further need to set BDB configuration through rpm macros. In fa
The inability to pass the GPG key to use for package signing along to the
rpmsign helper has been provided elsewhere.
This bug suggests that an error message suggesting that rpmsign be used instead
is better than incomplete legacy compatibility.
--
You are receiving this because you are subscr
I have mentioned this issue more discretely several times before.
Reproducer:
0) create a gpg key with the same userid as, say, RHEL7.
1) sign a package and install with yum.
2) yum initiates a user dialogue using the false userid.
While yum also presents the keyid in the dialogue, the possibili
I'd rather work on code as well.
I understand workload and the need for community transparency.
However, the delays on submitted patches are beginning to be measured in months
and years.
The comments are unhelpful to submitters as well, and are usually one of the
following:
0) where is the PR/
Instead of accusing me of spreading FUD, you might help me understand where the
download has been implemented.
I have read that code path multiple times, and do not see any indication of
download in rpmqv.c nor lib/query.c.
Meanwhile, this RFE was about handling CLI arguments and downloads cons
Ah "network support" is now limited to "download to a tempfile and use that
instead".
The duplicated code in lib/rpminstall.c is what was misleading me as to what
the rpm.org intentions were and are.
I can now see how to generate a patch to clean up lib/rpminstall.c to use rpmgi
I will close o
There is a better implementation of pubkey verification, including a more
intelligent parser of OpenPGP packets than what is in rpmio/rpmpgpg.c, that
includes the ability to verify certification and binding signatures of OpenPGP
packets, that can be reworked to rpm.org code here:
http://rpm5.or
Now that the preliminary and derivative issues with --nomanifest and hkp://
retrieval have clarified the intent, this issue will deal with rewriting
lib/rpminstall.c and will have patches attached for comment.
If you want a hint of what I intend, at least style wise, see
http://rpm5.org/cvs/fil
One issue that needs to be addressed is lack of "network support" (as in the
ability to download files with a curl/wget helper) in an environment where
networking is deliberately not configured or limited by firewalls or other
security protections as in mock/Koji chroot's.
Most of the realities
Last century, pgp.mit.edu was the reference SKS key server.
At a minimum, the Fedora SKS server should be included in macros.in
Better still would be to use one of the SKS server pool URLs for even higher
reliability as well as "best" network response time based on geographic area
and/or cluste
One of the largest flaws (IMHO) doing RPM package management is undoing payload
unpacking side effects on failed installs.
Existing content with identical paths has been clobbered.
The first step in remedying this problem would be to save the existing content
before the new content (which is al
the ability to download pubkeys through HKP from SKS key servers most
definitely "worked".
And still "works" afaik now that confusions induced by sloppily implemented
lib/rpminstall.c have been clarified: it was not at all clear reading that code
what was desired at rpm.org.
--
You are receiv
There are certainly failure modes if firewalls or chroot's prohibit accessing
SKS ports.
That is not a failure of the code in RPM.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/r
Closed #514.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/514#event-1798629319___
Rpm-maint mailing list
Rpm-maint@lists.rpm
@cgwalters: re "speaking of dependency loops and scripts"
yes the current state of affairs with setup and filesystem is insane. Those
packages should be combined, and the dependency that drags in filesystem (or
%setup if you prefer that name) as a prerequisite of glibc should be cast into
stone
@Conan-Kudo: we differ on what a serious patch is: both zstd and LMDB were
shooting fish in a barrel.
Give them a bit of a break ... from what? Ignoring issues takes zero effort.
I am not on iirc, it's a waste of time for me.
--
You are receiving this because you are subscribed to this thread
Closed #172.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/172#event-1800020398___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #197.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/197#event-1800021585___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #246.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/246#event-1800022686___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #269.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/269#event-1800023513___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #288.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/288#event-1800024217___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #289.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/289#event-1800025450___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #290.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/290#event-1800026510___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #410.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/410#event-1800028616___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #409.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/409#event-1800028042___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #412.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/412#event-1800029597___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #413.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/413#event-1800030257___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #416.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/416#event-1800030713___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #430.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/430#event-1800032510___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #432.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/432#event-180005___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #439.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/439#event-1800034023___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #455.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/455#event-1800035750___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #454.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/454#event-1800035139___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #459.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/459#event-1800036870___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #466.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/466#event-1800038279___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #460.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/460#event-1800037600___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #467.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/467#event-1800038698___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #474.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/474#event-1800039344___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #475.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/475#event-1800040306___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #476.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/476#event-1800040740___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #481.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/481#event-1800041204___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #489.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/489#event-1800042005___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #505.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/505#event-1800047331___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #492.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/492#event-1800049350___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #495.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/495#event-1800050573___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #493.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/493#event-1800049896___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #507.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/507#event-1800051207___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #510.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/510#event-1800052994___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #509.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/509#event-1800052399___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #520.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/520#event-1800054291___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #522.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/522#event-1800055371___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #523.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/523#event-1800055999___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #528.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/528#event-1800057039___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #530.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/530#event-1800057718___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #531.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/531#event-1800063225___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #529.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/529#event-1800063702___
Rpm-maint mailing list
Rpm-maint@lists.rpm
Closed #527.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/527#event-1800123531___
Rpm-maint mailing list
Rpm-maint@lists.rpm
601 - 700 of 762 matches
Mail list logo
