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.
Dne 28. 02. 22 v 13:27 lejeczek napsal(a):
Hi guys.
What options such as '--dnf-cmd' do, can you tell?
E.g.,
mock --dnf-cmddebuginfo-install PACKAGE
is equivalent (very simplified) to:
chroot $chroot
dnf debuginfo-install PACKAGE
dnf-cmd is command, not an option. So you cannot combine --rebuild and --dnf-cmd.
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)
This is problem of repository and needs to be fixed there.
As a workaround you can modify your config and set
config_opts['dnf.conf'] = """ [main]
...
best=0
...
"""
But this will silently hides new version of packages from you and may result to builds which may have broken deps on current distribution.
Miroslav
On 28/02/2022 14:27, Miroslav Suchý wrote:
Dne 28. 02. 22 v 13:27 lejeczek napsal(a):
Hi guys.
What options such as '--dnf-cmd' do, can you tell?
E.g.,
mock --dnf-cmddebuginfo-install PACKAGE
is equivalent (very simplified) to:
chroot $chroot
dnf debuginfo-install PACKAGE
dnf-cmd is command, not an option. So you cannot combine --rebuild and --dnf-cmd.
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)
This is problem of repository and needs to be fixed there.
As a workaround you can modify your config and set
config_opts['dnf.conf'] = """ [main]
...
best=0
...
"""
But this will silently hides new version of packages from you and may result to builds which may have broken deps on current distribution.
Hi.
I've already fiddled with "best=" and it does not help, build still fails, does not get packages build.
I'm told that it is a "classic" chicken-egg problem for, "minimal/standard" buildroot with 'mock' for every/any package, includes "libmpc" - if that is true then:
a) I must recreate buildroot locally and fiddle with it in such a way that then new/higher version of the package replaces old/current and uses that "local" buildroot for everything else - would that work and how to get there?
b) I see this as chance to suggest (can't fix myself) an enhancement, a possible great improvement to 'mock' - where mock will be able to "handle" such a chicken-egg problem by giving priority, always or by an option/argument, to the higher version of the package overwriting(or ignoring) what is in that "standard/minimal" buildroot - would you think I could use Bugzilla for making such a suggestion?
many thanks, L.
buildsys@lists.fedoraproject.org
-
lejeczek -
Miroslav Suchý