Unable to disable repositories since the latest big update

I’m currently using Silverblue, and after the latest big update to Fedora 43, I seem to be unable to disable repositories, even though I successfully edited their files in /etc/yum.repos.d/ to have enabled=0, they just ignore that, and keep being enabled anyway. This wasn’t happening before the Fedora 43 update. How do I fix this?

Can you share what repos you are referring to? How do you notice those repos are still enabled?

What does GNOME Software show in the Software Repositories list? What about rpm-ostree refresh-md?

I’m referring to any of the default repos. I notice they’re enabled cuz their metadata is refreshed while doing system updates, so they’re also shown in repository lists, such as the rpm-ostree refresh-md

I am not sure how repo config files are checked on atomic desktops, but it might well be that the default Fedora repos (fedora, fedora-updates) cannot be disabled, since it doesn’t make sense on image-based systems, given that the base image is built using such repos. This would mean that the enabled flag in their config files is ignored. This assumption is confirmed by the fact that if you go to GNOME Software, these two repos specifically cannot be disabled.

However, other repos enabled by default (e.g. fedora-cisco-openh264 and updates-archive can be disabled in GNOME Software.

Can you share why would you want to disable the default repos?

the specific repository I’m trying to disable is fedora-multimedia, because due to some sort of geographic restrictions (?), it is no longer available for me to download from or even refresh; which means, I cannot update my system or install (layer) any rpm packages. I assume it’s related to the openh264 restrictions in some countries (which do affect where I live, yes). All the other repositories work fine. I was gonna try a vpn, but in order to get my vpn working, I need to layer a specific package, which also needs all repositories refreshed haha. I tried to install that package using rpm-ostree install package –-cache-only, but it just says Nothing provides [package] needed by [the package I'm trying to install], so I’m looking for a way to disable the repository instead. Again, I successfully disabled it before Fedora 43, so it would be weird if they suddenly decided that you should no longer be able to do this

There is no such repo as fedora-multimedia in current versions of Silverblue. Was this repo shipped with older versions of Fedora Atomic, or did you set it up manually?

On the other hand, it’s fedora-cisco-openh264 which has some geographic restrictions AFAIK, are you referring to this? If so, I assume you want to layer the openh264 package? Can you share the output of rpm-ostree status?

In order to have multimedia codecs on Fedora Atomic, a solution would be to layer RPM-Fusion repos (if not done already), and then to run:

rpm-ostree install libavcodec-freeworld

I for one am using multimedia apps from Flathub, which bring the needed runtime extensions for multimedia codecs, no RPM-OSTree layering needed.

:thinking: I did not set it up manually, but it was there by default on my system. I been told that the repo files in /etc/yum.repos.d/ have a partially immutable property, so they’re immutable by default, but if user makes some changes to them (using root), then the system will remember those changes and keep them from being reset by daily updates. This could be why the repo just stayed in there I guess. I did make changes to these files before.

no, the package I’m trying to layer is not openh264. It’s just some vpn configurator thing. But rpm-ostree demands all repositories to be refreshed before layering anything. Ofc, since I’m on Silverblue, I also try to install flatpaks first whenever possible, but yknow, this isn’t the case for that.

but anyway, after 5 days of thinking about this problem, my braincell decided to activate and tell me that the solution was to simply right click in the /etc/yum.repos.d/ directory, click the “Open in terminal” option and then sudo rm fedora-multimedia.repo and sudo rm negativo17-fedora-multimedia.repo
it seems to persist across daily updates, so it works :+1:

there is a warning about this though, if you happen to layer anything that needs packages from these repositories, it might as well just not work. But these are multimedia repositories, and it’s recommended to use flatpaks for that on Silverblue anyway

The second repo is certainly not an official Fedora repo, and I tend to believe neither is the former one.

Nevertheless, I’m glad to hear you’ve sorted it out.