On Tue, Oct 04, 2005 at 12:29:46AM +0200, Martin Koeppe wrote: > When running sbuild with schroot, and giving a .dsc file to sbuild, > it should run "apt-get update" before trying to install the Build-Depends. > > I did: > # debootstrap --resolve-deps --variant=buildd --include=fakeroot etch > /chroot/etch http://mirror/debian > # cp /etc/apt/sources.list /chroot/etch/etc/apt/sources.list > # cp -p -R /var/lib/sbuild /chroot/etch/var/lib/ > # mkdir -p /chroot/etch/build/buildd/ > # chown sbuild. /chroot/etch/build/buildd > # ln -s ../build/buildd /chroot/etch/home/sbuild > # su - sbuild > $ pwd ; ls > /home/sbuild > mc_4.6.0-4.6.1-pre4-2.diff.gz > mc_4.6.0-4.6.1-pre4-2.dsc > mc_4.6.0-4.6.1-pre4.orig.tar.gz > > $ sbuild -d etch mc_4.6.0-4.6.1-pre4-2.dsc > > (build fails because apt-get: W: Couldn't stat source package list > http://mirror ...) > > $ schroot -c etch -u root > # apt-get update > # exit
Well, I believe it is not sbuild's job to maintain your chroots. In your case, you created a new chroot and then changed it's behaviour (by modifying sources.list), at which point you should have run apt-get update yourself. A case could be made for locally built packages you need as Build-Depends, but for that as well the commands in /usr/share/sbuild/ should suffice. > $ sbuild -d etch mc_4.6.0-4.6.1-pre4-2.dsc > > here 2 interactive questions are asked, which should be avoided, too: > What interface should be used for configuring packages? 6 > Ignore questions with a priority less than... critical > but after that, the build succeeds, besides #331506 Those should not be asked (but this is a different bug report), sbuild should set the debconf frontend to noninteractive. I thought it did that already. Michael -- Michael Banck Debian Developer [EMAIL PROTECTED] http://www.advogato.org/person/mbanck/diary.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
