From: Matthew Crews <mailingli...@mattcrews.com>
Date: Wed, 12 Jun 2019 06:00:26 +0200 (CEST)
> What does your "/etc/apt/sources.list" file look like on your two machines?
Here they are.
# imager:/etc/apt/sources.list
# Security updates
deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free
# mirror.it.ubc.ca = 137.82.116.42
deb http://137.82.116.42/debian stretch main contrib non-free
deb-src http://137.82.116.42/debian stretch main contrib non-free
# stretch-updates, previously known as 'volatile'
deb http://137.82.116.42/debian stretch-updates main contrib non-free
deb-src http://137.82.116.42/debian stretch-updates main contrib non-free
# stretch backports
deb http://137.82.116.42/debian stretch-backports main contrib non-free
deb-src http://137.82.116.42/debian stretch-backports main contrib non-free
# dalton:/etc/apt/sources.list
# Security updates
deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free
# mirror.it.ubc.ca = 137.82.116.42
deb http://137.82.116.42/debian stretch main contrib non-free
deb-src http://137.82.116.42/debian stretch main contrib non-free
# debian.oregonstate.edu = 140.211.166.134
#deb http://140.211.166.141/debian jessie main contrib non-free
#deb-src http://140.211.166.141/debian jessie main contrib non-free
# Stable updates
deb http://137.82.116.42/debian stretch-updates main contrib non-free
deb-src http://137.82.116.42/debian stretch-updates main contrib non-free
# Stable backports
deb http://137.82.116.42/debian stretch-backports main contrib non-free
deb-src http://137.82.116.42/debian stretch-backports main contrib non-free
As I see, sources.list from the two systems are identical, except for comments.
> Its unusual to directly point to an IP address for the Debian repos, as
> opposed to point to the domain name.
dalton has dnsmasq. From distant recollection, name resolution failed when
the system was running and dnsmasq was not. That motivated direct reference
to IP addresses. To the best of my knowledge, an IP address should suffice to
identify a server or possibly a cluster of them.
I don't understand the intent or meaning of the hypothetical long path cited
repeatedly. Eg.
root@imager:/home/peter# apt-get update
Get:1 file:/full/path/to/build/packaging/deb ./ InRelease
Ign:1 file:/full/path/to/build/packaging/deb ./ InRelease
Get:2 file:/full/path/to/build/packaging/deb ./ Release
Ign:2 file:/full/path/to/build/packaging/deb ./ Release
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
...
Whereas dalton just confirms the sources.list
root@dalton:/home/peter# apt-get update
Ign:1 http://137.82.116.42/debian stretch InRelease
Hit:2 http://137.82.116.42/debian stretch-updates InRelease
Hit:3 http://137.82.116.42/debian stretch-backports InRelease
Hit:4 http://137.82.116.42/debian stretch Release
Hit:5 http://security.debian.org stretch/updates InRelease
Reading package lists... Done
root@dalton:/home/peter#
Any ideas about that? Incidentally, what is "Ign"?
Thanks, ... P.
--
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140 Bcc: peter at easthope. ca
