[buildd-tools-devel] Bug#685416: sbuild: symlink to build log is absolute

[Johannes Schauer]

Hi,

On Fri, 21 Aug 2015 09:24:21 +0200 Joachim Breitner <nomeata at debian.org> wrote:
> On Mon, 20 Aug 2012 18:53:02 +0200 Jakub Wilk <jwilk at debian.org> wrote:
> > The symlink to build log that sbuild creates is absolute:
> > 
> > $ readlink python-pipeline_0.1.3-3_i386.build
> > /home/jwilk/python-pipeline_0.1.3-3_i386-20120820-1846.build
> > 
> > It used to be relative in older (<= 0.63.1-1) versions of sbuild. Could you
> > restore the previous behavior? Thanks.
> 
> the bug is still present, and has caused me a minor annoyance.

same here.

Please find a patch attached which uses a relative symlink if the log directory
is equal to the build directory (the default) and if sbuild is not in buildd
mode.

Would this solve the problem?

Thanks!

cheers, josch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: symlink.patch
Type: text/x-diff
Size: 800 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20150821/da8448b4/attachment-0001.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20150821/da8448b4/attachment-0001.sig>