Holger Levsen [2014-11-18 13:10 +0100]: > no, it's not like that. you are using a specific mirror via http, while the > host could use a file:// mirror via nfs or rsync or just > /var/cache/apt/archives. -> your build results are unreliable and > unpredictable.
autopkgtest does not use any specific mirror. It's just calling "apt-get download", and thus it's using whichever deb source you have in sources.list. If that is a file:// source, then it won't hit the network indeed. This is exclusively a problem if you have some kind of build environment where you put exactly the build deps into /var/cache/apt/archives/, and then build in an environment without any network access to pull other packages from. That's why the bug is still open, but pbuilder, sbuild, cowbuilder, plain debuild etc. all don't work that way. (Hence "unusual environment"). Out of interest, what are you using as a build env? > we've discussed this briefly on #debian-devel today and now there is #770016 > "Clarify network access for building packages in main" against debian-policy > to document this properly. Independently of this, that's a good idea to document, thanks! Martin -- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
signature.asc
Description: Digital signature
