Bug#310863: [Buildd-tools-devel] Bug#310863: sbuild should conflict with apt-listbugs

2006-02-14 Thread Roger Leigh
Michael Banck <[EMAIL PROTECTED]> writes: > On Tue, Feb 14, 2006 at 10:29:05PM +, Roger Leigh wrote: >> This bug will be fixed (or rather, worked around) once we have a >> released version of sbuild supporting schroot, because it is then no >> longer dependent upon the host to run apt-get. >>

Bug#310863: sbuild should conflict with apt-listbugs

2006-02-14 Thread Michael Banck
On Tue, Feb 14, 2006 at 10:29:05PM +, Roger Leigh wrote: > This bug will be fixed (or rather, worked around) once we have a > released version of sbuild supporting schroot, because it is then no > longer dependent upon the host to run apt-get. > > However, all these merged bugs are due to apt-

Bug#310863: sbuild should conflict with apt-listbugs

2006-02-14 Thread Roger Leigh
This bug will be fixed (or rather, worked around) once we have a released version of sbuild supporting schroot, because it is then no longer dependent upon the host to run apt-get. However, all these merged bugs are due to apt-listbugs not respecting the APT configuration, and so IMHO these should

Bug#310863: sbuild should conflict with apt-listbugs

2005-05-26 Thread Francesco Paolo Lovergine
On Thu, May 26, 2005 at 08:56:26PM +0100, Roger Leigh wrote: > >> However, I am a bit worried that this might break sbuild on hurd-i386, > >> as networking inside the chroot is AFAIK not known to work reliably on > >> the Hurd, and users of sbuild have reported trouble with it (though > >> perhaps

Bug#310863: sbuild should conflict with apt-listbugs

2005-05-26 Thread Roger Leigh
Francesco Paolo Lovergine <[EMAIL PROTECTED]> writes: > On Thu, May 26, 2005 at 08:15:35PM +0200, Michael Banck wrote: >> The question rather is: Why does sbuild not run apt in the chroot? I >> guess the answer is: "Because upstream's (i.e. the one used on the >> official buildds) does not eithe

Bug#310863: sbuild should conflict with apt-listbugs

2005-05-26 Thread Francesco Paolo Lovergine
On Thu, May 26, 2005 at 08:15:35PM +0200, Michael Banck wrote: > The question rather is: Why does sbuild not run apt in the chroot? I > guess the answer is: "Because upstream's (i.e. the one used on the > official buildds) does not either, and there was no convincing argument > to change it". >

Bug#310863: sbuild should conflict with apt-listbugs

2005-05-26 Thread Michael Banck
On Thu, May 26, 2005 at 07:01:07PM +0100, Roger Leigh wrote: > > It is such that you do not need to have working apt-get/networking > > inside the chroot. (the chroot typically only has Essential and > > Build-Essential packages installed, which does not include apt-get > > AFAIK) > > This may or

Bug#310863: sbuild should conflict with apt-listbugs

2005-05-26 Thread Roger Leigh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Banck <[EMAIL PROTECTED]> writes: > tags 270357 271031 -moreinfo > tags 270357 271031 -unreproducible > merge 270357 271031 310863 > thanks > > (I guess they are the same, unmerge if not) > > On Thu, May 26, 2005 at 02:53:50PM +0100, Roger Le

Bug#310863: sbuild should conflict with apt-listbugs

2005-05-26 Thread Michael Banck
tags 270357 271031 -moreinfo tags 270357 271031 -unreproducible merge 270357 271031 310863 thanks (I guess they are the same, unmerge if not) On Thu, May 26, 2005 at 02:53:50PM +0100, Roger Leigh wrote: > sbuild uses the non-chrooted install of apt, rather than the copy > installed inside the ch

Bug#310863: sbuild should conflict with apt-listbugs

2005-05-26 Thread Francesco Paolo Lovergine
merge 310863 271031 thanks On Thu, May 26, 2005 at 02:53:50PM +0100, Roger Leigh wrote: > Package: sbuild > Version: 0.35 > Severity: normal > > Hi, > > sbuild uses the non-chrooted install of apt, rather than the copy > installed inside the chroot. I've not investigated why yet. > > If apt-li

Bug#310863: sbuild should conflict with apt-listbugs

2005-05-26 Thread Roger Leigh
Package: sbuild Version: 0.35 Severity: normal Hi, sbuild uses the non-chrooted install of apt, rather than the copy installed inside the chroot. I've not investigated why yet. If apt-listbugs is installed, and requires human interaction before unpacking, sbuild freezes. Removing apt-listbugs