Bug#381118: [Buildd-tools-devel] Bug#381118: sbuild: schroot + apt
download is broken
Roger Leigh
rleigh at whinlatter.ukfsn.org
Thu Aug 3 18:07:17 UTC 2006
Daniel Stone <daniel at fooishbar.org> writes:
> On Wed, Aug 02, 2006 at 12:44:57PM +0100, Roger Leigh wrote:
>> Daniel Stone <daniel at fooishbar.org> writes:
>> > When using schroot and apt to download packages, the build tanks
>> > quite early: apt-get source is called from within the chroot, but
>> > none of the verify_md5sum stuff is, so it tries to verify the dsc in
>> > ~/build/ in the host, and fails when it isn't there.
>>
>> Interesting.
>>
>> Perhaps we should still run apt-get outside the chroot, even when
>> using schroot? I originally introduced it to make setup simpler, and
>> to work around some bugs with apt-get (specifically, apt-listchanges
>> and friends, and it running some things outside the chroot even when
>> you set all the config parameters to use the chroot).
>
> Depends what your usecase is. My use for this is running an i386
> builder on amd64 (just requires a couple of hacks to pass the
> architecture name in). I'd rather not have an sbuild chroot inside the
> i386 chroot inside my real amd64 system ...
That's a perfectly valid use case, IMO, and you do need the separation
for that to work. I'll keep things the way they are.
>> > Interestingly, the failure mode is a hang in verify_md5sums, because
>> > dsc_md5sums returns null, and verify_md5sums ends up calling
>> > /usr/bin/md5sum, which hangs waiting for input ...
>>
>> That looks like an outright bug. dsc_md5sums should, IMO, return an
>> empty hashref on failure, but doesn't currently.
>
> Correct.
I have attached a patch to
- return an empty hashref on failure
- not to run md5sum if the hashref is empty
Please could you try the patch. It will apply to the current sbuild,
or you can apply to
svn://svn.debian.org/svn/buildd-tools/trunk/sbuild
This doesn't fix the root cause of the problem, just the bug in the
failure path. Could you verify that this works?
Could you additionally try bind mounting /home into the build chroot,
and see if this makes any difference? I think this may be a
requirement (current limitation), due to keeping the file location the
same when building with either sudo or schroot. If this is the case,
it will take a bit more work to fix.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please sign and encrypt your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20060803/4b424a42/attachment-0001.pgp
More information about the Buildd-tools-devel
mailing list