[buildd-tools-devel] Bug#612324: Bug#612324: Bug#612324: Creates log file in package directory -- confuses dpkg-source

[Roger Leigh]

On Mon, Feb 07, 2011 at 07:26:16PM +0000, Roger Leigh wrote:
> On Mon, Feb 07, 2011 at 07:08:08PM +0100, Loïc Minier wrote:
> >  I'm building u-boot packages with something like:
> > git-buildpackage --git-builder='sbuild -A -s --dpkg-source-opt=-i -d unstable'
> >  but I don't think the git-buildpackage part is relevant.
> > 
> >  I'm getting warnings from dpkg-source like this one:
> > dpkg-source: warning: newly created empty file 'build-unstable-20110207-1723.wRCNDh.log' will not be represented in diff
> > 
> >  I think this is due to sbuild creating the log file in the current
> >  directory, just like when it's invoked on a .dsc file, instead of using
> >  the parent directory for the log file when called from a source package
> >  directory.
> 
> I think this is quite possible.  We can certainly change the build
> directory to be .. if called from a source package dir.  Thanks for
> spotting this!  Note sure why I haven't seen this myself, maybe
> different logging settings.

So this is triggered by opening the sbuild main log, /not/ the package
build log.  The package build log is in .. as would be expected.
Unfortunately, the main log is opened when sbuild starts up, and at that
point we don't know that is needs opening in .. rather than . .

I've been wanting to remove the main log for ages; it has a number of
other problems.  The work to feed back all build metadata directly to
buildd will also require the main log to be removed.  At this point the
log contents can become part of the package build log.  The main log
will be redundant with the removal of batch mode (once buildd can do
the batching itself, which isn't very difficult since it's just a
loop).

In the interim, we could instead either
1) write to /tmp
2) write to the log dir, default is ~/logs

I'd say (2) is a good place, unless it interferes with existing users;
currently it's package build logs only.  I'll need to check that the
various buildd parts that process build logs won't get confused with
these extra files.


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 GPG sign your mail.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20110213/4af6609e/attachment.pgp>