Debian Bug report logs - #955501
yaz: please make the build reproducible

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: "Chris Lamb" <lamby@debian.org>

To: submit@bugs.debian.org

Subject: yaz: please make the build reproducible

Date: Wed, 01 Apr 2020 18:30:16 +0100

[Message part 1 (text/plain, inline)]

Source: yaz
Version: 5.29.0-2
Severity: wishlist
Tags: patch
User: reproducible-builds@lists.alioth.debian.org
Usertags: buildpath
X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0] we noticed that
yaz could not be built reproducibly.

This is because it embeds the absolute build path into the /usr/bin/
yaz-config file.

A patch is attached. As this path will not exist at runtime, assuming
that yaz works today (!), then the application of this patch could be
reasoned to therefore be harmless.

 [0] https://reproducible-builds.org/


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org / chris-lamb.co.uk
       `-

[yaz.diff.txt (text/plain, attachment)]

Message #10 received at submit@bugs.debian.org (full text, mbox, reply):

From: Adam Dickmeiss <adam@indexdata.dk>

To: Chris Lamb <lamby@debian.org>, 955501@bugs.debian.org

Cc: submit@bugs.debian.org

Subject: Re: Bug#955501: yaz: please make the build reproducible

Date: Wed, 1 Apr 2020 22:04:54 +0200

[Message part 1 (text/plain, inline)]

Thanks for the patch.

We are using yaz-config for side-by-side builds which means we can't apply
that patch as is.. the echo_source definition.. We will have to make two
yaz-config's .. One for the side-by-side build which obviously will have
those build directories and another one to be installed in /usr/bin without
those.

/ Adam


On Wed, Apr 1, 2020 at 7:33 PM Chris Lamb <lamby@debian.org> wrote:

> Source: yaz
> Version: 5.29.0-2
> Severity: wishlist
> Tags: patch
> User: reproducible-builds@lists.alioth.debian.org
> Usertags: buildpath
> X-Debbugs-Cc: reproducible-bugs@lists.alioth.debian.org
>
> Hi,
>
> Whilst working on the Reproducible Builds effort [0] we noticed that
> yaz could not be built reproducibly.
>
> This is because it embeds the absolute build path into the /usr/bin/
> yaz-config file.
>
> A patch is attached. As this path will not exist at runtime, assuming
> that yaz works today (!), then the application of this patch could be
> reasoned to therefore be harmless.
>
>  [0] https://reproducible-builds.org/
>
>
> Regards,
>
> --
>       ,''`.
>      : :'  :     Chris Lamb
>      `. `'`      lamby@debian.org / chris-lamb.co.uk
>        `-
>

[Message part 2 (text/html, inline)]

Message #20 received at 955501@bugs.debian.org (full text, mbox, reply):

From: "Chris Lamb" <lamby@debian.org>

To: "Adam Dickmeiss" <adam@indexdata.dk>, 955501@bugs.debian.org

Subject: Re: Bug#955501: yaz: please make the build reproducible

Date: Wed, 01 Apr 2020 22:58:03 -0000

Hi Adam,

> We are using yaz-config for side-by-side builds which means we can't 
> apply that patch as is.

What do you mean by side-by-side build? I have not come across this
term before. (Do you mean you are Build-Depending on yaz from another
package?)


Regards,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
       `-

Message #25 received at 955501@bugs.debian.org (full text, mbox, reply):

From: Adam Dickmeiss <adam@indexdata.dk>

To: Chris Lamb <lamby@debian.org>

Cc: 955501@bugs.debian.org

Subject: Re: Bug#955501: yaz: please make the build reproducible

Date: Thu, 2 Apr 2020 13:06:03 +0200

[Message part 1 (text/plain, inline)]

On Thu, Apr 2, 2020 at 12:58 AM Chris Lamb <lamby@debian.org> wrote:

> Hi Adam,
>
> > We are using yaz-config for side-by-side builds which means we can't
> > apply that patch as is.
>
> What do you mean by side-by-side build? I have not come across this
>

Probably a bad term, that I invented. It just means that we can use
yaz-config from another tree without installing yaz.

  cd yaz
  ./configure && make
  cd ../idzebra
  ./configure # looks in ../yaz for yaz-config
  make

Anyway the issue is now fixed in upstream, as follows:

https://github.com/indexdata/yaz/commit/370dece3e9cb2fe4feb8c6e1780b46de8bc7fa9d

/ Adam



> term before. (Do you mean you are Build-Depending on yaz from another
> package?)
>
>
> Regards,
>
> --
>       ,''`.
>      : :'  :     Chris Lamb
>      `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
>        `-
>

[Message part 2 (text/html, inline)]

Message #30 received at 955501@bugs.debian.org (full text, mbox, reply):

From: "Chris Lamb" <lamby@debian.org>

To: "Adam Dickmeiss" <adam@indexdata.dk>

Cc: 955501@bugs.debian.org

Subject: Re: Bug#955501: yaz: please make the build reproducible

Date: Thu, 02 Apr 2020 12:12:48 +0100

Hi Adam,

> >  > We are using yaz-config for side-by-side builds which means we can't 
> >  > apply that patch as is.
> > 
> >  What do you mean by side-by-side build? I have not come across this
> 
> Probably a bad term, that I invented. It just means that we can use 
> yaz-config from another tree without installing yaz.
> 
>  cd yaz
>  ./configure && make
>  cd ../idzebra
>  ./configure # looks in ../yaz for yaz-config
>  make

Ah, I see.

> Anyway the issue is now fixed in upstream, as follows:
> 
> https://github.com/indexdata/yaz/commit/370dece3e9cb2fe4feb8c6e1780b46de8bc7fa9d

Hm, I am not quite sure how this will help — @abs_top_srcdir@ will
still be interpolated and therefore will vary across builds... just in
a different place.


Best wishes,

-- 
      ,''`.
     : :'  :     Chris Lamb
     `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
       `-

Message #35 received at 955501@bugs.debian.org (full text, mbox, reply):

From: Adam Dickmeiss <adam@indexdata.dk>

To: Chris Lamb <lamby@debian.org>

Cc: 955501@bugs.debian.org

Subject: Re: Bug#955501: yaz: please make the build reproducible

Date: Thu, 2 Apr 2020 13:14:53 +0200

[Message part 1 (text/plain, inline)]

On Thu, Apr 2, 2020 at 1:13 PM Chris Lamb <lamby@debian.org> wrote:

> Hi Adam,
>
> > >  > We are using yaz-config for side-by-side builds which means we
> can't
> > >  > apply that patch as is.
> > >
> > >  What do you mean by side-by-side build? I have not come across this
> >
> > Probably a bad term, that I invented. It just means that we can use
> > yaz-config from another tree without installing yaz.
> >
> >  cd yaz
> >  ./configure && make
> >  cd ../idzebra
> >  ./configure # looks in ../yaz for yaz-config
> >  make
>
> Ah, I see.
>
> > Anyway the issue is now fixed in upstream, as follows:
> >
> >
> https://github.com/indexdata/yaz/commit/370dece3e9cb2fe4feb8c6e1780b46de8bc7fa9d
>
> Hm, I am not quite sure how this will help — @abs_top_srcdir@ will
> still be interpolated and therefore will vary across builds... just in
> a different place.
>
yaz-config in root will have it. But that's not installed.

util/yaz-config is going to be in /usr/bin or other.. That does not have
build stuff in it.

/ Adam


>
>
> Best wishes,
>
> --
>       ,''`.
>      : :'  :     Chris Lamb
>      `. `'`      lamby@debian.org 🍥 chris-lamb.co.uk
>        `-
>

[Message part 2 (text/html, inline)]

Message #40 received at 955501-close@bugs.debian.org (full text, mbox, reply):

From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>

To: 955501-close@bugs.debian.org

Subject: Bug#955501: fixed in yaz 5.30.0-1

Date: Sat, 18 Apr 2020 14:40:20 +0000

Source: yaz
Source-Version: 5.30.0-1
Done: Hugh McMaster <hugh.mcmaster@outlook.com>

We believe that the bug you reported is fixed in the latest version of
yaz, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 955501@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hugh McMaster <hugh.mcmaster@outlook.com> (supplier of updated yaz package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 09 Apr 2020 20:50:43 +1000
Source: yaz
Architecture: source
Version: 5.30.0-1
Distribution: unstable
Urgency: medium
Maintainer: Vincent Danjean <vdanjean@debian.org>
Changed-By: Hugh McMaster <hugh.mcmaster@outlook.com>
Closes: 955501
Changes:
 yaz (5.30.0-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update symbols file for yaz 5.30.0.
   * debian/control:
     - Sort Build-Depends list.
     - Use consistent field order in package metadata.
     - Mark libyaz-dev Multi-Arch: same.
   * libyaz-dev:
     - yaz-config and its man page are no longer packaged.
       Please switch to pkg-config (yaz, yaz-icu or yaz-server).
       This also makes the package reproducible.  Closes: #955501
Checksums-Sha1:
 2f5d444b325a6606e452ee96496e4fce82f6d359 2326 yaz_5.30.0-1.dsc
 2f6a29aa7e4aa51cd6ae4b9adedc986c3871bfdf 2604582 yaz_5.30.0.orig.tar.gz
 6e19da02aacec634ac27c2b0fb3007327c29c5da 20596 yaz_5.30.0-1.debian.tar.xz
 5da4979184cfcfcc844ccd31a88a155ba27a3e17 9262 yaz_5.30.0-1_amd64.buildinfo
Checksums-Sha256:
 e22634bdb73bfaaf56b9c6bf994b6670c4085abdf20ff58e0f642b65374a98a1 2326 yaz_5.30.0-1.dsc
 0e25521a68ebc723fec8b899b3d723fb7c22613105b9cf78b7d39ea583576488 2604582 yaz_5.30.0.orig.tar.gz
 92ace81ed9ed64571ca830feaaa98389b4f1a7deba9e257a4bddd6525d669b3c 20596 yaz_5.30.0-1.debian.tar.xz
 5834adc79be698561f1e93ff8101ab5bfe2cdcf0f38505ee21de7c17777813cb 9262 yaz_5.30.0-1_amd64.buildinfo
Files:
 bc7727229dadffa0e5378c56fee18256 2326 utils optional yaz_5.30.0-1.dsc
 a5ec3d3090ff266c6b4da4ec91ac63e2 2604582 utils optional yaz_5.30.0.orig.tar.gz
 c8ff94187b6df5df3d1d21f02b367e57 20596 utils optional yaz_5.30.0-1.debian.tar.xz
 75f5be84a6557b0c9e899daef3714afd 9262 utils optional yaz_5.30.0-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAl6bBsYACgkQCBa54Yx2
K63RhBAAgW3+/pTP8XMAMNu/YCFQITZGlBcqJhVBrTBJFFCnHcckgsV7GvI65eWt
WwaeHECTMsuve0i28ACx0gXaFKlXW8UID1D+pNV9wW2J68jmS+4aPt65A/2G4F7K
JPSEXal1+fTHv7TWQXO09SGzpF4ug9xyHjsqrIaLHupIGUyAGgu9ZjFPynqZX/zq
qNPA5q7SbNJvIbksjttucIaDHTIdoGAiURZCgFwGZZYkneAIUFdvYQS9W/xTA9lt
YmZzybvhu5WlAq17AdjqXrd5YfGCFcO4ZkuMCeHy4y2dAHor3SfQlXoTNhLkFjcZ
5RgzxkvSKtWMKbazOEIIWgs7xS75dcVNpGTaEa69lqpSN/EHdLjwk8C9UD4T36kG
sKBr6wq/rnHELWqNqrp/8PrkClow6jTxoJgN7QqHhHZuBJKqYYtSRwaA2UVmakBC
N+7gXdpQqbiHQQaIvHrVK51u2BwlzQbCzu8t6nAWb7+jdE1IarxLqCzfFGDonePa
f2o39mzyaRy9QX3dSOSBu+3kdO6haxd+1u1bhTwwGsUJB8loTnTs7ZnRAtOBqb4V
4+iDRNXevFhyhNtHULeFtJ70l7i71jPJVcznNIl9EnpImnCsoCgxbYN/YmxGV8t1
FaiQYcg86+2S/STjtlr0tSogZZrTivXa2CGnkz9cTaYyFqJSb9k=
=j0PJ
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.