> 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.
This is not that easy, because the creation of the chroot is done as root, apt-get update should be run as user sbuild on host, which gets root on chroot with schroot. It works without further modifying schroot config: # su -c "schroot -c etch -u root apt-get update" sbuild But what if I resync my mirror afterwards? I didn't change the chroot then, but the stored package lists would become invalid, wouldn't they? > 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. Oh, thanks for the hint to /usr/share/sbuild/, but as I can see, these tools are not for schroot usage of sbuild, are they? >> 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. Ok, I won't file a new bug for it, you might retitle (or clone) this one if you think it's necessary. (If one preinstalls debconf with debootstrap --resolve-deps --variant=buildd --include=fakeroot,debconf this works around those questions for now) Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
