Re: Problem with apt update (is not signed)
kopecpa...@gmail.com wrote: > >Hello, > >since yesterday (2023-10-25) I received an error during the apt update >command: Only since yesterday? Was it working fine previously? >docker run -it debian:bullseye /bin/bash >Unable to find image 'debian:bullseye' locally >bullseye: Pulling from library/debian >69b3efbf67c2: Pull complete >Digest: >sha256:c141beaa9e0767774221cc82efe3a6712a1cc4f75d2699334dfd9a28a6f7357b >Status: Downloaded newer image for debian:bullseye > >root@eb335ad71846:/# apt-get update >Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] >Get:2 http://deb.debian.org/debian-security bullseye-security InRelease >[48.4 kB] >Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] >Err:1 http://deb.debian.org/debian bullseye InRelease > Â At least one invalid signature was encountered. >Err:2 http://deb.debian.org/debian-security bullseye-security InRelease > Â At least one invalid signature was encountered. >Err:3 http://deb.debian.org/debian bullseye-updates InRelease > Â At least one invalid signature was encountered. >Reading package lists... Done >W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least >one invalid signature was encountered. >E: The repository 'http://deb.debian.org/debian bullseye InRelease' is >not signed. >N: Updating from such a repository can't be done securely, and is >therefore disabled by default. >N: See apt-secure(8) manpage for repository creation and user >configuration details. >W: GPG error: http://deb.debian.org/debian-security bullseye-security >InRelease: At least one invalid signature was encountered. >E: The repository 'http://deb.debian.org/debian-security >bullseye-security InRelease' is not signed. >N: Updating from such a repository can't be done securely, and is >therefore disabled by default. >N: See apt-secure(8) manpage for repository creation and user >configuration details. >W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: >At least one invalid signature was encountered. >E: The repository 'http://deb.debian.org/debian bullseye-updates >InRelease' is not signed. >N: Updating from such a repository can't be done securely, and is >therefore disabled by default. >N: See apt-secure(8) manpage for repository creation and user >configuration details. What are you running as a host OS here? Are you running the same arch on both the host and inside the container (i.e. i386 on i386, or amd64 on amd64)? I've seen this kind of symptom in the past when a docker image included software which depended on system calls only provided by a newer kernel. Docker is *awful* here - it doesn't actually isolate you from this kind of mismatch; instead it hides the details of problems to make them almost impossible to debug. -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I...
Re: Problem with apt update (is not signed)
As another data point, I've tried the following: $ docker run -it debian apt update $ docker run -it debian:bullseye apt update $ docker run -it debian@sha256:c141beaa9e0767774221cc82efe3a6712a1cc4f75d2699334dfd9a28a6f7357b apt update And these all complete successfully: ❯ docker run -it debian@sha256:c141beaa9e0767774221cc82efe3a6712a1cc4f75d2699334dfd9a28a6f7357b apt update Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB] Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] Get:4 http://deb.debian.org/debian bullseye/main amd64 Packages [8062 kB] Get:5 http://deb.debian.org/debian-security bullseye-security/main amd64 Packages [256 kB] Get:6 http://deb.debian.org/debian bullseye-updates/main amd64 Packages [17.4 kB] Fetched 8544 kB in 2s (4269 kB/s) Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. So this would rule out an issue with the docker image. Instead, the only difference would be which mirror you pulled from. https://deb.debian.org/ is the mirror service provided by Fastly. Fetching URLs on deb.debian.org will transparently redirect you to a mirror close to you. Now, it's possible that the mirror was in the process of updating. It's also (less likely) possible that someone tampered with the mirror (and so the failing signatures did exactly what they're supposed to do, prevent you downloading malicious software). Unfortunately, unless you can identify which mirror you were directed to, it will be difficult for you to know who to notify. On 26/10/2023 07:29, Paweł Kopeć wrote: Hello, since yesterday (2023-10-25) I received an error during the apt update command: docker run -it debian:bullseye /bin/bash Unable to find image 'debian:bullseye' locally bullseye: Pulling from library/debian 69b3efbf67c2: Pull complete Digest: sha256:c141beaa9e0767774221cc82efe3a6712a1cc4f75d2699334dfd9a28a6f7357b Status: Downloaded newer image for debian:bullseye root@eb335ad71846:/# apt-get update Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB] Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] Err:1 http://deb.debian.org/debian bullseye InRelease At least one invalid signature was encountered. Err:2 http://deb.debian.org/debian-security bullseye-security InRelease At least one invalid signature was encountered. Err:3 http://deb.debian.org/debian bullseye-updates InRelease At least one invalid signature was encountered. Reading package lists... Done W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://deb.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian-security bullseye-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Where I should send this problem? Regards OpenPGP_signature.asc Description: OpenPGP digital signature
Problem with apt update (is not signed)
Hello, since yesterday (2023-10-25) I received an error during the apt update command: docker run -it debian:bullseye /bin/bash Unable to find image 'debian:bullseye' locally bullseye: Pulling from library/debian 69b3efbf67c2: Pull complete Digest: sha256:c141beaa9e0767774221cc82efe3a6712a1cc4f75d2699334dfd9a28a6f7357b Status: Downloaded newer image for debian:bullseye root@eb335ad71846:/# apt-get update Get:1 http://deb.debian.org/debian bullseye InRelease [116 kB] Get:2 http://deb.debian.org/debian-security bullseye-security InRelease [48.4 kB] Get:3 http://deb.debian.org/debian bullseye-updates InRelease [44.1 kB] Err:1 http://deb.debian.org/debian bullseye InRelease At least one invalid signature was encountered. Err:2 http://deb.debian.org/debian-security bullseye-security InRelease At least one invalid signature was encountered. Err:3 http://deb.debian.org/debian bullseye-updates InRelease At least one invalid signature was encountered. Reading package lists... Done W: GPG error: http://deb.debian.org/debian bullseye InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://deb.debian.org/debian-security bullseye-security InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian-security bullseye-security InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. W: GPG error: http://deb.debian.org/debian bullseye-updates InRelease: At least one invalid signature was encountered. E: The repository 'http://deb.debian.org/debian bullseye-updates InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Where I should send this problem? Regards
Re: Problem with apt update
On 10/20/2019 10:41 AM, Reco wrote: Hi. On Sun, Oct 20, 2019 at 10:25:27AM -0400, Stephen P. Molnar wrote: I know the the command worked because I can access -i386 applications. However, when I run: comp@AbNormal:~$ sudo -s apt update none of the Debian i386 repositories are listed. Why is this the case? If the mirror has not changed its contents since your last update, apt will only show *checking* Release files, but won't show downloading new index files. For instance, these are shown without an architecture: Get:1 http://security.debian.org buster/updates InRelease [39.1 kB] Hit:2 http://ftp.debian.org/debian buster InRelease Get:3 http://ftp.debian.org/debian buster-updates InRelease [49.3 kB] Get:4 http://ftp.debian.org/debian buster-backports InRelease [46.7 kB] But these ones are shown with the one: Ign:6 http://security.debian.org buster/updates/main arm64 Packages Ign:7 http://security.debian.org buster/updates/main amd64 Packages .. Ign:10 http://ftp.debian.org/debian buster-updates/main amd64 Packages.diff/Index Ign:11 http://ftp.debian.org/debian buster-updates/main arm64 Packages.diff/Index Also, if you need to check your multiarch status, the following does it for me (any meaningful library should do it): apt policy libc6:* Reco Thanks for the reply. your suggestion shows that the i386 files are, indeed, there. My main concern is the corollary to Murphy's Law - 'if one thing is wrong many others are probably at risk also'. Happily, that doesn't seem to be the case, at least so far!. -- Stephen P. Molnar, Ph.D. www.molecular-modeling.net 614.312.7528 (c) Skype: smolnar1
Re: Problem with apt update
Hi. On Sun, Oct 20, 2019 at 10:25:27AM -0400, Stephen P. Molnar wrote: > I know the the command worked because I can access -i386 applications. > However, when I run: > > > comp@AbNormal:~$ sudo -s apt update > > none of the Debian i386 repositories are listed. Why is this the case? If the mirror has not changed its contents since your last update, apt will only show *checking* Release files, but won't show downloading new index files. For instance, these are shown without an architecture: Get:1 http://security.debian.org buster/updates InRelease [39.1 kB] Hit:2 http://ftp.debian.org/debian buster InRelease Get:3 http://ftp.debian.org/debian buster-updates InRelease [49.3 kB] Get:4 http://ftp.debian.org/debian buster-backports InRelease [46.7 kB] But these ones are shown with the one: Ign:6 http://security.debian.org buster/updates/main arm64 Packages Ign:7 http://security.debian.org buster/updates/main amd64 Packages ... Ign:10 http://ftp.debian.org/debian buster-updates/main amd64 Packages.diff/Index Ign:11 http://ftp.debian.org/debian buster-updates/main arm64 Packages.diff/Index Also, if you need to check your multiarch status, the following does it for me (any meaningful library should do it): apt policy libc6:* Reco
Problem with apt update
I have just reinstalled Buster on my main computer. While I was setting up my desktop I ran: sudo -s dpkg --add-architecture i386 without any warning or error messages. I know the the command worked because I can access -i386 applications. However, when I run: comp@AbNormal:~$ sudo -s apt update Hit:1 http://mirror.cc.columbia.edu/debian buster InRelease Hit:2 http://mirror.cc.columbia.edu/debian buster-updates InRelease Ign:3 http://dl.google.com/linux/earth/deb stable InRelease Hit:4 http://dl.google.com/linux/earth/deb stable Release Hit:5 http://security.debian.org/debian-security buster/updates InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. N: Skipping acquire of configured file 'main/binary-i386/Packages' as repository 'http://dl.google.com/linux/earth/deb stable InRelease' doesn't support architecture 'i386' none of the Debian i386 repositories are listed. Why is this the case? Thanks in advance. -- Stephen P. Molnar, Ph.D. www.molecular-modeling.net 614.312.7528 (c) Skype: smolnar1
