la, 2005-11-26 kello 23:11 +0900, Junichi Uekawa kirjoitti: > Hi, > > > > Thanks for the report. > > > I guess that would be the case > > > > > > A quick grep tells me that the following will fail to work: > > > > > > B90linda:3:apt-get install -y linda > > > B91dpkg-i:19:apt-get install $PKGNAMES || true > > > B91dpkg-i:24:apt-get install $PKGNAMES || true > > > B92test-pkg:8: apt-get install -y "$PKG" > > > B92test-pkg:9: apt-get remove -y "$PKG" > > > execute_installtest.sh:22:apt-get install -y "$1" < /dev/null > > > > Indeed so. Mind you, I made a mistake. The correct option is > > --allow-unauthenticated instead. > > pbuilder mostly uses force-yes, since --allow-unauthenticated didn't > work in the earlier days. > > If --allow-unauthenticated now works reliably (with even the current > testing version, and other possibly affected distributions, ubuntu was > released with apt 0.6, wasn't it?), it might be a good idea to switch.
The problem with --force-yes is that it also forces other things like answers to configuration questions, which is not always desirable. An alternative would be to ask the debian-installer team how they enable secure APT when bootstrapping a new Etch installation. We could probably use their trick with pbuilder as well. -- Martin-Éric Racine http://q-funk.iki.fi
signature.asc
Description: Digitaalisesti allekirjoitettu viestin osa
