Fedora 39 Errors during downloading metadata for repository 'fedora': - Status code: 500

[sweet.cheddar]

Hello fellow qubes users,

I’m running Qubes on version 4.2.1

I tried to install libreoffice and i get this error in fedora-39-xfce-clone-1 runing

[user@fedora-39-xfce-clone-1 ~]$ sudo dnf install libreoffice
Fedora 39 - x86_64                              267  B/s | 704  B     00:02    
Errors during downloading metadata for repository 'fedora':
  - Status code: 500 for http://HTTPS///mirrors.fedoraproject.org/metalink?repo=fedora-39&arch=x86_64&protocol=http (IP: 127.0.0.1)
Error: Failed to download metadata for repo 'fedora': Cannot prepare internal mirrorlist: Status code: 500 for http://HTTPS///mirrors.fedoraproject.org/metalink?repo=fedora-39&arch=x86_64&protocol=http (IP: 127.0.0.1)

I find this issue that seemed similar https://discussion.fedoraproject.org/t/errors-during-downloading-metadata-for-repository-fedora/73771 so i tried to try to modify the /etc/yum.repos.d/fedora.repo file by changing the hostname.
Commenting metalink and adding :

baseurl=http://download.fedoraproject.org/

or

baseurl=http://download.fedoraproject.org/pub/fedora/linux/releases/$releasever/Everything/$basearch/os/

This issue seems to be similar to : Errors during downloading metadata for repository 'qubes-contrib-dom0-r4.2-current'

I’m stuck, please send help

[apparatus]

Do you use apt-cacher-ng?
Seems to be an issue with fedora+cacher:

Tool: Simple Set-up of New Qubes and Software

Great work as always, @unman I’m working out of the new 4.2 repo and all debian-based templates work when using the cacher salt configs. Fedora templates, however, issue Curl errors (5), (500), and (56). I think somewhere I read you suggested changing the repository metalinks or alternating to the baseurls instead? I can’t find the source of that post now. EDIT: Found this in an old email list exchange, for anyone looking to troubleshoot apt-cacher-ng: Yes, apt-cacher-ng works for Fedora u…

Issues with apt-cacher-ng

@unman : I am still confused on some of the internals. Wanting to reply on a forum thread, and not having installed anything under my disp sys-net for a while, I wanted to install wireshark there in current session to install additional tools I needed just for that session… And fell into another rabbit hole. First, as I normally am able to do with current setup on other qubes: [user@sys-net ~]$ sudo dnf update Fedora 36 - x86_64 …

[sweet.cheddar]

Yes, i use apt-cacher-ng

I didn’t knew that there was an issue with fedora+cacher.

Thank you very much @apparatus

[sweet.cheddar]

so what i did is edit the repository files :

$ sudo nano /etc/yum.repos.d/fedora-cisco-openh264.repo
$ sudo nano /etc/yum.repos.d/fedora-updates-testing.repo
$ sudo nano /etc/yum.repos.d/fedora-updates.repo
$ sudo nano /etc/yum.repos.d/fedora.repo
$ sudo nano /etc/yum.repos.d/qubes-r4.repo

and edit the repository definitions

replacing `http://HTTPS///` with `https://`

[unman]

I didn’t knew that there was an issue with fedora+cacher.

Status code 500 indicates an error at the server end. It’s relatively
common with Fedora mirrors for some reason.

If you are using the apt-cacher-ng package that I provide I try to keep
the package updated with extended fedora repository lists and
configuration changes. It works well for 40 and (most of the time) 39.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

[sweet.cheddar]

(didnt know how to reply to specific post)

[sweet.cheddar]

I’m not sur if i use apt-cacher-ng,
because in dom0, when i run “cacher --help” or “apt-cacher-ng --help” i get “command not found”

what can i do to make sure is use apt-cacher-ng ?

It might be possible that i installed it and later deleted it

sould i try installing it again ?

[alimirjamali]

You would please check one thing before reinstallation.

Check inside /etc/qubes-rpc and see if you have file named qubes.UpdatesProxy.rpmnew

[unman]

so what i did is edit the repository files :

You will also need to change the updates proxy used by this template -
you can do this in Qubes Global Config.

I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.

[sweet.cheddar]

there is not this file, i have a similar one qubes.UpdateAppMenuFor

[unman]

I???m not sur if i use apt-cacher-ng,
because in dom0, when i run ???cacher --help??? or ???apt-cacher-ng --help??? i get ???command not found???

It’s not an application in dom0 - it’s an application that runs in a
qube.
You can see if you are using it from Qubes Global Config under the
Updates pane. If you installed the package from simple tools then
a qube called cacher would have been created, and the system configured
to use it.

I never presume to speak for the Qubes team. When I comment in the Forum I speak for myself.

[sweet.cheddar]

ok, so i don’t have it installed @apparatus @unman

I missunterstood because i saw http://HTTPS/// in the repos files

[sweet.cheddar]

I think my issue might come from when i installed an additional template provided by our generous and kind @unman here https://qubes.3isec.org/Templates/

I might have done something strange like starting to install cacher and don’t finish installing it. I don’t remember exactly it was a few weeks ago.

Is it correct to assume that if we use sys-whonix as our update-proxy, there is no benefit to using cacher ?

[sweet.cheddar]

can i mark it as a solution ?
it solved the issue for me

[apparatus]

@sweet.cheddar

Is it correct to assume that if we use sys-whonix as our update-proxy, there is no benefit to using cacher ?

Yes.

@sweet.cheddar

can i mark it as a solution ?

I guess so.

[sweet.cheddar]

and for debian edit those files :

/etc/apt/sources.list
/etc/apt/sources.list.d/qubes-r4.list