Hallo, * Mathias Behrle [Mon, Mar 16 2015, 06:06:30PM]: > > And both lines you mentioned should have the same effect... but they > > shouldn't be used both, of course. > > I added the debug line and attached the complete log of the screen session of > the docker build to this mail.
Ok now this starts becoming interesting: [0mGet:1 http://security.debian.org jessie/updates InRelease [84.1 kB] [91mAnswer for: http://http.debian.net/debian/dists/jessie/InRelease [0m[91mHTTP/1.1 404 Not Found [0m[91mContent-Length: 0 [0m[91mDate: Mon Mar 16 17:01:19 2015 [0m[91mServer: Debian Apt-Cacher NG/0.8.0 [0m[91mX-Original-Source: http://ftp2.debian.org/debian/dists/jessie/InRelease [0m[91mConnection: Keep-Alive That's obviously wrong. ftp2.debian.org does not exist. Where exactly does it come from? I guess it's configured in your /etc/apt-cacher-ng/backends_debian file and the next question is... how was it added? Manually by somebody? (that somebody maybe wanted to add ftp.de.debian.org?) I am also wondering about that particular status code. ACNG should have detected a DNS resolution error and would report it as such. Also, "Not Found" is not generated by ACNG with that spelling (verified by Mr. grep). So what's the cause? Do you have some broken DNS that resolves to some catch-all IP? Maybe an ISP DNS that redirects mistyped domains to their advertising network or similar crap? Regadrs, Eduard. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
