Re: missing dependencies while updating
Riccardo Mottola <[email protected]>
| Newsgroups | gmane.linux.debian.ports.powerpc |
|---|---|
| Message-ID | <[email protected]> |
Hi Adrian, John Paul Adrian Glaubitz wrote: > For example, libssl3 is called these days [3]. The fact that your is not, is > an indicator you haven't updated this machine for a long time. I wanted to use archive for transition as well as for kernel tests, since the current one doesn't boot. Arbitrarily choose July 2024 as a starting point. as per info; since they are over a year old, I specify no validity check. I suppose we need unstable/unreleased as usual, so i did deb [check-valid-until=no] http://snapshot.debian.org/archive/debian-ports/20240701T014213Z/ unstable main deb [check-valid-until=no] http://snapshot.debian.org/archive/debian-ports/20240701T014213Z/ unreleased main Even if I run: apt-get --allow-unauthenticated update I get: E: The repository 'http://snapshot.debian.org/archive/debian-ports/20240701T014213Z unstable InRelease' is not signed. N: Updating from such a repository can't be done securely, and is therefore disabled by default. I tried adding allow-insecure=yes, but it was not enough, nor trusted=yes. But together I could finally upgrade things, even if getting errors: e.g.: deb [check-valid-until=no allow-insecure=yes trusted=yes] https://snapshot.debian.org/archive/debian-ports/20240612T013548Z/ unstable main Just for info. Riccardo