--pm-cmd / --dnf-cmd - ? mock
by lejeczek
Hi guys.
What options such as '--dnf-cmd' do, can you tell?
Man page is pretty confusing - well to me it is - in that respect.
I thought that was for 'args', parameters in other words which are
available to the 'dnf' command itself but that does _not_ seem to be the
case.
At the same time - I hit something which might be common I'd imagine:
...
- cannot install the best update candidate for package
mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-4.1.0-8.el8.x86_64 and mpfr-3.1.6-1.el8.x86_64
- cannot install both mpfr-3.1.6-1.el8.x86_64 and mpfr-4.1.0-8.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest'
to use not only best candidate packages)
...
If '--dnf-cmd' is not for those things then how to rectify such a problem?
many thanks, L.
1 year, 3 months
automated rpm signing woes
by John Florian
What is the recommended solution for this these days? What is
fedoraproject.org using?
I presently have a setup using Sigul on CentOS 7 but that's leading to
my current problem of being unable to upgrade anything. I can't find
anything workable with CentOS 8, meanwhile my Koji Hub is stuck at
1.21.1 because I'm unaware of any newer builds via epel7. My Koji
Builders are now stuck at Fedora 33 because tasks fail if they have a
newer version of Koji than the Hub.
My attempts at moving Sigul to CentOS 8 Stream have just led to one bug
after another using the only build I could find, located at
https://kojipkgs.fedoraproject.org/repos-dist/epel$releasever-infra/lates....
I've fumbled my way through a few fixes and would be happy to contribute
when I can or, at least, report bugs. However, whenever I go to
https://pagure.io/sigul/, the apparent upstream for the project, I see
the last commit as 10 months ago, the last comment on any issue as 7
months ago, no issues closed, no PRs merged. Is it dead?
1 year, 3 months