Re: Problem with apt maybe related to installation/configuration of apt-cacher-ng

[john doe]

On 5/30/23 19:39, Dennis Heddicke wrote:
> Hello,
>
> i have a problem with "apt update", everytime i execute the command, i
> get the following error messages:
>
> Get:1 http://security.debian.org/debian-security bookworm-security
> InRelease [48,0 kB]
> Get:2 http://deb.debian.org/debian bookworm InRelease [193 kB]
> Err:1 http://security.debian.org/debian-security bookworm-security
> InRelease
>  The following signatures were invalid: BADSIG 112695A0E562B32A Debian
> Security Archive Automatic Signing Key (10/buster) <ftpm...@debian.org>
> Err:2 http://deb.debian.org/debian bookworm InRelease
>  The following signatures were invalid: BADSIG 648ACFD622F3D138 Debian
> Archive Automatic Signing Key (10/buster) <ftpm...@debian.org>
> Fetched 241 kB in 0s (507 kB/s)
> Reading package lists... Done
> W: An error occurred during the signature verification. The repository
> is not updated and the previous index files will be used.
> GPG error: http://security.debian.org/debian-security bookworm-security
> InRelease: The following signatures were invalid:
> BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key
> (10/buster) <ftpm...@debian.org>
> W: An error occurred during the signature verification. The repository
> is not updated and the previous index files will be used.
> GPG error: http://deb.debian.org/debian bookworm InRelease: The
> following signatures were invalid: BADSIG 648ACFD622F3D
> 138 Debian Archive Automatic Signing Key (10/buster) <ftpm...@debian.org>
> W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease
>  The following signatures were invalid: BADSIG 648ACFD622F3D138
> Debian Archive Automatic Signing Key (10/buster) <ftpm...@debian.org>
> W: Failed to fetch
> http://security.debian.org/debian-security/dists/bookworm-security/InRelease  The following signatures were invalid:
> BADSIG 112695A0E562B32A Debian Security Archive Automatic Signing Key
> (10/buster) <ftpm...@debian.org>
> W: Some index files failed to download. They have been ignored, or old
> ones used instead.
>
> I use Debian 12. The only changes i did before the problem occurred,
> were the installation of apt-cacher-ng and i ran "mach bootstrap" in a
> chroot.
>

If you remove apt-cacher-ng, does it work at all?

--
John Doe

[Charles Curley]

On Wed, 31 May 2023 11:36:19 +0200
Dennis Heddicke <dhed...@hotmail.com> wrote:

> Acquire::http {Proxy "http://localhost:3142";};
> Acquire::https {Proxy "http://";};

I'm not comfortable with your second line there. First, you have for
https a non-secure http. I suspect they should match. Second, if you
are going to use hhtps, give the complete URL. Like so:

Acquire::https {Proxy "https://localhost:3142";};

But I don't think that's part of your problem.

For what it's worth, my configuration for ACN looks like:

root@chaffee:~# cat /etc/apt/apt.conf.d/02proxy
Acquire::http::Proxy "http://aptcacherdeb.localdomain:3142";
Acquire::https::Proxy "https://aptcacherdeb.localdomain:3142";
root@chaffee:~#



>
> there are any errors too, although i don't know what  caused them.
> But thank you for your help.

I'm confused: are there errors or are there no errors? If there are
errors, please show a sample.

--
Does anybody read signatures any more?

https://charlescurley.com
https://charlescurley.com/blog/

[john doe]

On 5/31/23 11:36, Dennis Heddicke wrote:
> Yes, after purging apt-cacher-ng the problem was gone. And after i
> reinstalled apt-cacher-ng and configured it that way:
>

For the sake of simplicity and troubleshooting, please modify
sources.list directly.

What does acng.conf look like?


Note that this list uses bottom-posting! :)

--
John Doe