[Buildd-tools-devel] Bug#482491: Bug#482491: sbuild: extracts the source while installing b-deps
Lucas Nussbaum
lucas at lucas-nussbaum.net
Fri May 23 13:19:32 UTC 2008
On 23/05/08 at 12:08 +0100, Roger Leigh wrote:
> On Fri, May 23, 2008 at 09:25:01AM +0200, Lucas Nussbaum wrote:
> > It seems that sbuild now extracts the source while installing
> > build-deps. See:
> >
> > Selecting previously deselected package gettext.
> > Unpacking gettext (from .../gettext_0.17-2_i386.deb) ...
> > Selecting previously deselected package intltool-debian.
> > Unpacking intltool-debian (from .../intltool-debian_0.35.0+20060710gpg:
> > Signature made Wed Apr 19 12:53:15 2006 CEST using DSA key ID 8E635A5E
> > gpg: Can't check signature: public key not found
> > dpkg-source: extracting crip in crip_3.7-3
> > dpkg-source: info: unpacking crip_3.7.orig.tar.gz
> > dpkg-source: info: applying crip_3.7-3.diff.gz
> > .1_all.deb) ...
> > Selecting previously deselected package po-debconf.
> > Unpacking po-debconf (from .../po-debconf_1.0.13_all.deb) ...
> > Selecting previously deselected package debhelper.
> > Unpacking debhelper (from .../debhelper_7.0.9_all.deb) ...
> >
> > This produces confusing build log. If this change was made on purpose,
> > please provide an option to serialize those steps, so I can get "clean"
> > build logs when reporting bugs.
>
> There have not been any changes made on purpose. install_deps() is
> called before build(). One possiblity is that the logging stream PLOG
> is doing some odd buffering in subprocesses, and flushing the stream at
> certain points would help (the logging is done in a separate process).
>
> It would be interesting to know the the git master head
> git://git.debian.org/git/buildd-tools/sbuild
> also suffers from this problem, and if the log is identical between
> sbuild runs.
>
> sbuild has had quite a lot of refactoring done over the last two weeks
> or so, and it's possible that something broke as a result, but none of
> this work should have changed the program logic.
Hi,
git bisect shows that the first bad commit is
c1e3cbc8699da54f9f540bdabc6436a128eaa668 .
A test case is to build crip_3.7-3 : it builds fine before the commit,
and fails to build with the commit.
Have fun ;) (sorry, no more time to investigate this)
--
| Lucas Nussbaum
| lucas at lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lucas at nussbaum.fr GPG: 1024D/023B3F4F |
More information about the Buildd-tools-devel
mailing list