[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#781075: sbuild: Breaks d-i build by assuming it is a deb



control: tag -1 + pending

On 2015-03-24 07:18, Cyril Brulebois wrote:
> Hi,
> 
> Niels Thykier <niels@thykier.net> (2015-03-24):
> > Source: sbuild
> > Version: 0.65.1-1
> > Severity: grave
> > Tags: d-i
> > User: release.debian.org@packages.debian.org
> > Usertags: jessie-is-blocker
> > 
> > Hi,
> > 
> > The debian-installer currently FTBFS on various architectures, but the
> > build itself is followed by "I: Built successfully".  Then there is a
> > message later saying (something to the extend of):
> > 
> > """
> > dpkg-deb: error: `/«CHROOT»/«BUILDDIR»/debian-installer-images_20150324_arm64.tar.gz'
> > """
> > 
> > Which is entirely correct as the debian-installer is a "tar.gz" file.  This
> > happens on both the Wheezy sbuild and the Jessie sbuild.  But only the Jessie
> > version seems to be flagging the build as failed!  We believe it is related
> > the commit [684c57b].
> 
> (Thanks for opening the bug report and letting -boot@ know through x-d-cc
> as requested on IRC.)
> 
> Since debian-installer-images is an arch-indep “package name”, I guess
> an easy way out would be to special-case it and not perform dpkg calls
> on it in lib/Sbuild/Build.pm's build sub? (Even fancier, letting tar xf
> do the work with that particular beast but that's another story, and I'm
> afraid I'm not patching + testing sbuild right now.)

I have just committed a patch to fix that on the master branch [1].

There have been other changes committed to this branch, so we should
decide if they are jessie material or not. I have added Ansgar in Cc for
that.

Aurelien

[1] https://anonscm.debian.org/cgit/buildd-tools/sbuild.git/commit/?id=7ec60100ee315e130e8771d4268debc3eaeff9af

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

Attachment: signature.asc
Description: Digital signature


Reply to: