Installation is a server type deployment so no GUI or extra packages beyond the vanilla server type deployment.
This is our first installation of Stretch and my /etc/apt/sources.list file has the following:
Code: Select all
deb http://security.debian.org/debian-security stretch/updates main contrib non-free
deb http://deb.debian.org/debian/ stretch-updates main contrib non-free
deb http://deb.debian.org/debian stretch main contrib non-free
Troubleshooting ruled out firewall rules, network configuration, etc.
When I run 'apt-get update' I see something like this:
Code: Select all
Ign:xx http://blah blah blah
Err: xx http://blah blah blah
403 Forbidden [IP: 151.101.196.204 80]
...
W: The repository 'http://security.debian.org/debian-security stretch/updates Release' does not have a Release file
various warnings related to the other repositories not having Release files
E: Failed to fetch http://deb.debian.org/debian/dists/stretch-updates/main/binary-amd64/Packages 403 Forbidden [IP: 151.101.196.204 80]
same errors for the other repositories
E: Some index files failed to download. They have been ignored, or old ones used instead.[code]
This happens fairly late in the apt-get update process and not right off the bat.
I have poked around here, Google, etc and I see some indications that there might be a GPG related issue with Stretch (or was) or more strict connection checks with the base Stretch repositories but I haven't seen anything concrete and the error I'm seeing here versus other reports is more vague - 403, Releases missing, one probably causes the other, etc.
I double checked my repository list against the Debian sources and they look correct.
I have commented out all but one sources line and the issue follows the active repository entry in /etc/apt/sources.list. The issue also follows different mirrors so not obvious that I have a lemon of a mirror.
At this point I'm not sure what to do other than scrub the installation on Stretch and stick with Jessie but that isn't a long-term solution really.
For grins I tried multiple Stretch installations on multiple Hyper-V hypervisors and they all do the same thing so this has to be some configuration related deal or a shim that I need to put in place to make this go.
I have to be missing something small but important here.