I need apt-cacher-ng as i build system images (Exe GNU/Linux, Devuan+TDE) but have limited internet access.
All repos, including http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x work normally with apt-cacher-ng except when trinity-sb and/or trinity-testing are enabled.
They are configured exactly as per Trinity site instructions and the keyring is installed.
Without using apt-cacher-ng (proxy disabled in /etc/apt/apt.conf.d/) trinity-sb and/or trinity-testing work.
They do work using a (much) older apt-cacher-ng version (0.8.0-3)
Is something wrong with the "InRelease" file?
Thanks in advance..
Dave Hare
############################
root@beowulf:# apt update Hit:1 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_10 InRelease Hit:2 http://pkgmaster.devuan.org/merged beowulf InRelease Get:3 http://exegnulinux.net/apt ascii InRelease [2,840 B] Hit:4 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x buster InRelease Hit:5 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0.x buster InRelease Err:6 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb buster InRelease 500 Apt-Cacher NG does not like that data [IP: ::1 3142] Reading package lists... Done E: Failed to fetch http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb/dists/buster/InR... 500 Apt-Cacher NG does not like that data [IP: ::1 3142] E: The repository 'http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb buster InRelease' is no longer 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.
############################
On Monday 13 of January 2020 00:38:49 David Hare wrote:
I need apt-cacher-ng as i build system images (Exe GNU/Linux, Devuan+TDE) but have limited internet access.
All repos, including http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x work normally with apt-cacher-ng except when trinity-sb and/or trinity-testing are enabled.
They are configured exactly as per Trinity site instructions and the keyring is installed.
Without using apt-cacher-ng (proxy disabled in /etc/apt/apt.conf.d/) trinity-sb and/or trinity-testing work.
They do work using a (much) older apt-cacher-ng version (0.8.0-3)
Is something wrong with the "InRelease" file?
Thanks in advance..
Dave Hare
############################
root@beowulf:# apt update Hit:1 http://download.opensuse.org/repositories/home:/stevenpusser/Debian_10 InRelease Hit:2 http://pkgmaster.devuan.org/merged beowulf InRelease Get:3 http://exegnulinux.net/apt ascii InRelease [2,840 B] Hit:4 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-r14.0.x buster InRelease Hit:5 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-builddeps-r14.0 .x buster InRelease Err:6 http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb buster InRelease 500 Apt-Cacher NG does not like that data [IP: ::1 3142] Reading package lists... Done E: Failed to fetch http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb/dists/buster /InRelease 500 Apt-Cacher NG does not like that data [IP: ::1 3142] E: The repository 'http://mirror.ppa.trinitydesktop.org/trinity/deb/trinity-sb buster InRelease' is no longer 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.
############################
Hi David,
You can read some information from the apt-cacher log?
Currently, repositories are managed in the same way == reprepro is used to generate apt information and are signed with the same GPG key. Therefore, I have no idea what should be different, because InRelease is created in the same way.
Note: On my builders, I use squid-deb-proxy (set as a transparent proxy) and I don't see any problems with accessing the repositories.
Cheers
-
David Hare -
Slávek Banko