On Tue, Oct 25, 2011 at 04:15:06PM -0400, Barry Warsaw wrote: > However, when the buildd got to that point, it failed:
> https://launchpadlibrarian.net/83677349/buildlog_ubuntu-precise-amd64.m2crypto_0.21.1-2ubuntu1_BUILDING.txt.gz I think you probably mean this error: chroot-autobuild/build/buildd/python-m2crypto_0.21.1-2ubuntu1_amd64.deb: dpkg-deb: file `chroot-autobuild/build/buildd/python-m2crypto_0.21.1-2ubuntu1_amd64.deb' contains ununderstood data member data.tar.xz , giving up (had to search on 'xz' to find the error in the build logs) This is not part of the package build per se, but is part of extra inspection the buildds do of the package after it's built in order to put useful information into the build logs. This part runs using the dpkg-deb from outside the build chroot, and outside the build chroot we're not running precise - we're running lucid. So you're going to get this error in the build log of any package that uses .xz, whether or not you add the Pre-Depends, and should ignore it. As Micah says, the error we need to care about is not a build-time error at all; it's the archive check that blocks the *upload* of a package that doesn't pass muster. So there's nothing wrong with your sbuild setup that you aren't seeing this locally. > Any idea why it succeeded in sbuild, and do you have any other suggestions > for testing such package builds locally before uploading? Fine-toothed-combing of the merge delta, and, when all else fails, that's what the archive check is there for. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected]
signature.asc
Description: Digital signature
-- ubuntu-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
