Cannot update repositories any more

Support
, ,
21

hey,

and now i am a little bit closer to the truth! reading man pages, in particular the man page for dnf5-config-manager reveals that there are so called ‘adjustments’ to the repository files. in particular /etc/dnf/repos.override.d/99-config_manager.repo.

so, no matter what /etc/yum.repos.d/*.repo contains, if there are ‘adjustments’, then those take precedence. that might explain why i was so confused about the ‘enabled=0/1’ misbehaviour, but doesn’t explain the URLs containing ‘25.11-1’.

greetings…

1 Like
22

A very unusual problem for sure.

The initial problem was using release instead of rolling.

The .repo files are definitely in /etc/yum.repos.d/. dnf determines which .repo file to use from the package distro-release-repos.

The following part I think I am correct on but not 100% positive:

AFAIK release is only for Rock point releases. AFAIK the only correct repos for ROME are rolling. So using release would look for a point release like 5.0 or 6.0 which are Rock releases. Somehow something told dnf to look for a point release for your system and it came up with 25.11-1 which does not exist but is the latest rolling release. I do not know why or how this happened. Maybe this is what happens when someone has rolling distro-release* packages installed and somehow repo selector gets set to release. Definitely have not seen this before now.

1 Like
23

I do understand how this happened now. The advice is if you are using cooker(Cooker) or rolling(ROME) do not even try to use release it won’t work and it will confuse the heck out of dnf. release can only work if you have a Rock system.

If you are using ROME(rolling) pay attention here to know when and when not to upgrade your system.

24

@ben79 as I understand the user never changed the Update channel, he just ticked to enable the /extra repo.
IF we get Release there after install, that’s something we are going to check soon.

25

Looking better at what you wrote

can you please tell what exactly you typed in that command?

26

Perhaps I can learn something here? This is a bit confusing because we do not know if @hemathor was using dnf4 or dnf5 because this literally changed in ROME today. I am guessing it would have been dnf5 because first post says "after the recent update of OMLx ROME ".

Anyway I just tested what I am posting here using a ROME system under dnf5 and Rock system under dnf4.

I do not thing this will do anything regardless of dnf4 or 5:

dnf config-manager <repo>.enabled=0

Either of these will work under dnf4:

dnf config-manager --disable <repo>
or
dnf config-manager --set-disabled <repo>

I think this would work under dnf5:

dnf config-manager setopt <repo>.enabled=0

Something seems missing. Or I am missing something.

1 Like
27

hey,

@ben79 no offense, but i wrote explicitly, that the problem occurred after i upgraded to the newest version of ROME. so it was all dnf5… :wink:

greetings…

28

hey,

@rugyada: here’s what my shell history tells me:

# dnf config-manager setopt release-updates-x86_64.enabled=0 release-updates-x86_64-extra.enabled=0 release-x86_64.enabled=0 release-x86_64-extra.enabled=0

and after that:

# dnf config-manager setopt rolling-x86_64.enabled=1 rolling-x86_64-extra.enabled=1

in hindsight i could have just edited /etc/dnf/repos.override.d/99-config_manager.repo. way less typing.

greetings…

1 Like
29

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.