On 2022-09-11 22:31:59 J Leslie Turriff wrote:
Heh. I got my Trinity repositories working by changing ...-r14.0.12 to ..-r14.0.x, which I should have remembered, having made the same mistake with the openSUSE repositories long ago. :-) Changing
| http://deb.devuan.org/merged | http://pkgmanager.devuan.org/merged
to
| https://deb.devuan.org/merged | https://pkgmanager.devuan.org/merged
got me further, but the first one gets a bad certificate error (that it tells me will be valid in 6min 36secs). Aaaand...eight minutes later it says it will be valid in 3h 58min 18s. I'll try substituting debian for devuan... The deb repository is what provides the base OS binaries, right? If so, there's no way to install or upgrade the OS on the machine until I get it working?
Leslie
But it turns out that deb.debian.org/debian/ doesn't have a merge/ subdirectory, only | debian/ | debian-debug/ | debian-ports/ | debian-security/ so I have no idea what to use instead. The Debian Administrator's Handbook has no information about repository tree structures. And pkgmaster.devuan.org/merged still has a bad certificate, and there is no pkgmaster.debian.org. Having exhausted these possibilities, I tried your apt-get -o Acquire::... method, but that failed, too. See attached.
Leslie