* Kevin Fenzi:
On 8/26/19 7:57 AM, Florian Weimer wrote:
> * Kaleb Keithley:
>
>> `dnf update` on my f32/rawhide machine is giving me:
>>
>> Problem 1: conflicting requests
>> - nothing provides module(platform:f31) needed by module
bat:latest:3120190714171319:22d7e2a5-0.x86_64
>> Problem 2: conflicting requests
>> - nothing provides module(platform:f31) needed by module
exa:latest:3120190721165838:22d7e2a5-0.x86_64
>> Problem 3: conflicting requests
>> - nothing provides module(platform:f31) needed by module
libgit2:0.28:3120190714114509:f636be4b-0.x86_64
>> Problem 4: conflicting requests
>> - nothing provides module(platform:f31) needed by module
silver:rolling:3120190728135623:22d7e2a5-0.x86_64
>>
>> What do I need to do for this?
>
> I also see this with
>
> dnf distrosync --releasever=31
>
> on Fedora 30. Is this expected?
Can you expand on what you mean there?
This is a fedora 30 machine you are upgrading to 31 with distrosync and
it shows this in the distro-sync output before you say 'y'? or ?
module(platform:fN) should be provided by fedora-release-whatever-N so
yeah, on upgrades with distro-sync you will see that until you have the
fedora 31 fedora-release installed or unless you pass:
--setopt='module_platform_id=platform:f31' on the distro sync.
dnf system-upgrade is supposed to not need this anymore and do the right
thing.
Thanks for the suggestion. But it turned out that the Beaker automation
had installed an alternate main repository and disabled the real one in
/etc/yum.repos.d/fedora.repo (while leaving updates repository active,
ugh). The alternate repository was not using $releasever. So this was
entirely a user error.
I'll try to keep in mind that I have to tweak repositories in the
future.
Thanks,
Florian