E: Failed to fetch https://deb.qubes-os.org/r4.1/vm/dists/bullseye/InRelease Temporary failure resolving 'deb.qubes-os.org'

This might be an easy issue… But i get this error, and i think it’s because i tried to install librewolf but had some error… not sure. i did also clone a qube but that might not be it. How do i fix this?

$ sudo apt-get update
Err:1 https://deb.debian.org/debian bullseye InRelease
  Temporary failure resolving 'deb.debian.org'
Err:2 https://deb.debian.org/debian-security bullseye-security InRelease
  Temporary failure resolving 'deb.debian.org'
Err:3 https://deb.qubes-os.org/r4.1/vm bullseye InRelease
  Temporary failure resolving 'deb.qubes-os.org'
Reading package lists... Done
E: Failed to fetch https://deb.debian.org/debian/dists/bullseye/InRelease  Temporary failure resolving 'deb.debian.org'
E: Failed to fetch https://deb.debian.org/debian-security/dists/bullseye-security/InRelease  Temporary failure resolving 'deb.debian.org'
E: Failed to fetch https://deb.qubes-os.org/r4.1/vm/dists/bullseye/InRelease  Temporary failure resolving 'deb.qubes-os.org'
E: Some index files failed to download. They have been ignored, or old ones used instead.

Thank you.

check your internet ?

1 Like

If your internet connection is fine, wait a bit and try again later.

Thanks, but no it has to do with that i manually picked bullseye here maybe?

# Change this command to choose a distro manually.
distro=$(if echo " bullseye focal impish jammy uma una " | grep -q " $(lsb_release -sc) "; then echo $(lsb_release -sc); else echo focal; fi)

wget -O- https://deb.librewolf.net/keyring.gpg | sudo gpg --dearmor -o /usr/share/keyrings/librewolf.gpg

sudo tee /etc/apt/sources.list.d/librewolf.sources << EOF > /dev/null
Types: deb
URIs: https://deb.librewolf.net
Suites: $distro
Components: main
Architectures: amd64
Signed-By: /usr/share/keyrings/librewolf.gpg

sudo apt update

sudo apt install librewolf -y

You haven’t said, and no one has asked you.
Do you only get this error in the template where you installed
librewolf. Are your other templates updating fine?
That fragment of code you quote couldn’t affect the standard repository

Hello. Thanks, but no it’sonly that cube… I do get this in fedora which is wierd, but that seems to be something i dont understand in fedora:

sudo dnf update && sudo dnf upgrade -y
Last metadata expiration check: 
Dependencies resolved.
 Package                    Arch   Version          Repository             Size
 gstreamer1-plugin-openh264 x86_64 1.20.3-1.fc36    fedora-cisco-openh264  25 k
 mozilla-openh264           x86_64 2.3.0-1.fc36     fedora-cisco-openh264 428 k
 openh264                   x86_64 2.3.0-1.fc36     fedora-cisco-openh264 423 k

Transaction Summary
Upgrade  3 Packages

Total download size: 876 k
Is this ok [y/N]: y
Downloading Packages:
(1/3): gstreamer1-plugin-openh264-1.20.3-1.fc36 5.6 kB/s |  25 kB     00:04    
(2/3): openh264-2.3.0-1.fc36.x86_64.rpm          71 kB/s | 423 kB     00:05    
(3/3): mozilla-openh264-2.3.0-1.fc36.x86_64.rpm  68 kB/s | 428 kB     00:06    
Total                                           104 kB/s | 876 kB     00:08     
Package gstreamer1-plugin-openh264-1.20.3-1.fc36.x86_64.rpm is not signed
Package mozilla-openh264-2.3.0-1.fc36.x86_64.rpm is not signed
Package openh264-2.3.0-1.fc36.x86_64.rpm is not signed
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED
[user@fedora-36 ~]$ ^C
[user@fedora-36 ~]$ 

I just need to clean something i added that’s all. Can someone answer to why there are no signatures in fedora? Debian seems better… Maybe someone forgot to sign and uploaded?

The Fedora error is because you have gpgcheck enabled in the Fedora repo
definition, but fedora packages are not signed. Those are all from the
same repository, which makes me wonder if the gpgcheck is not
appropriate there. (I don’t know, but I wonder.)

With the Debian issue, its strange. If your other updates are working
properly then obviously the connection at the proxy is fine, and it
doesn’t look as if there’s anything wrong with the definition -
https://deb.debian.org/ is standard stuff.

Can you confirm that the only change you made was that librewolf repo?

1 Like

For the past month or so I’ve seen a similar error involving the failure to update the InRelease file when I update any of my Debian templates, on multiple machines. Since I update via sys-whonix (using the .onion repos), I’m accustomed to update failures like this from time to time and a second, or third, attempt is usually sufficient to successfully complete the update. The difference is that the errors now seem to be happening more consistently and always involving the InRelease file. However, most packages update fine on the first attempt despite the error.

For example:

Updating whonix-ws-16

Error on updating whonix-ws-16: Command '['sudo', 'qubesctl', '--skip-dom0', '--targets=whonix-ws-16', '--show-output', 'state.sls', 'update.qubes-vm']' returned non-zero exit status 20
            ID: update
      Function: pkg.uptodate
        Result: False
       Comment: E: Release file for tor+https://fasttrack.debian.net/debian/dists/bullseye-fasttrack/InRelease is not valid yet (invalid for another 48s). Updates for this repository will not be applied.

1 Like

Unless this has changed recently, I believe Fedora packages are signed, while Fedora repos are not.

Indeed, they should be, but apparently these are not.

ok thanks for your answers… I read this a bit late. I fixed the issue last time… I prefer debian over fedora by the way.