Debian Bug report logs - #901473
jenkins.debian.org: Vary merged-usr in reproducibility testing?

Package: jenkins.debian.org; Maintainer for jenkins.debian.org is Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>;

Reported by: Chris Lamb <lamby@debian.org>

Date: Wed, 13 Jun 2018 20:12:01 UTC

Severity: wishlist

Done: Holger Levsen <holger@layer-acht.org>

Bug is archived. No further changes may be made.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to debian-bugs-dist@lists.debian.org, jrtc27@debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Wed, 13 Jun 2018 20:12:04 GMT) (full text, mbox, link).

Acknowledgement sent to Chris Lamb <lamby@debian.org>:
New Bug report received and forwarded. Copy sent to jrtc27@debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>. (Wed, 13 Jun 2018 20:12:04 GMT) (full text, mbox, link).

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

Package: jenkins.debian.org
Severity: wishlist
X-Debbugs-CC: jrtc27@debian.org

From #debian-devel:

   < jrtc27> does r-b do merged/non-merged [usr] variation?
   
    < lamby> No. Do you expect it to find *r-b* variations, or simply
             FTBFS?
             
   < jrtc27> lamby: both, but more worried about the former
   < jrtc27> e.g. systemd had been broken when built in usr-merge
             chroots as it searched PATH for various core utilities
   < jrtc27> the result was hard-coded in the output binary so blew up
             on non-usr-merge systems
   < jrtc27> (#843433)


Best wishes,

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

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Sat, 14 Jul 2018 10:03:02 GMT) (full text, mbox, link).

Acknowledgement sent to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>. (Sat, 14 Jul 2018 10:03:02 GMT) (full text, mbox, link).

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

debootstrap was changed (again) in 1.0.102 to now default to
--merged-usr [1].

Systems are not forcefully upgraded to a merged-usr setup atm though.
buildds are regularly re-created from scratch and will thus have a
merged-usr setup.
This means, binaries that were built in a merged-usr buildd environment
will now run on a lot of non-merged-usr setups.

If we could auto-detect any problems resulting from that via the
reproducible builds effort, this would be great.

regards,
Michael



[1] https://packages.qa.debian.org/d/debootstrap/news/20180613T134920Z.html
    https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839046

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

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

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

On Sat, Jul 14, 2018 at 11:59:37AM +0200, Michael Biebl wrote:
> debootstrap was changed (again) in 1.0.102 to now default to
> --merged-usr [1].
> 
> Systems are not forcefully upgraded to a merged-usr setup atm though.
> buildds are regularly re-created from scratch and will thus have a
> merged-usr setup.
> This means, binaries that were built in a merged-usr buildd environment
> will now run on a lot of non-merged-usr setups.

Is that really so?  I expect buildds to run with stable's debootstrap,
so for now they should be using non-merged-usr chroots.

-- 
regards,
                        Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540      .''`.
more about me:  https://mapreri.org                             : :'  :
Launchpad user: https://launchpad.net/~mapreri                  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-

[signature.asc (application/pgp-signature, inline)]

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

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

Am 14.07.2018 um 12:28 schrieb Mattia Rizzolo:
> On Sat, Jul 14, 2018 at 11:59:37AM +0200, Michael Biebl wrote:
>> debootstrap was changed (again) in 1.0.102 to now default to
>> --merged-usr [1].
>>
>> Systems are not forcefully upgraded to a merged-usr setup atm though.
>> buildds are regularly re-created from scratch and will thus have a
>> merged-usr setup.
>> This means, binaries that were built in a merged-usr buildd environment
>> will now run on a lot of non-merged-usr setups.
> 
> Is that really so?  I expect buildds to run with stable's debootstrap,
> so for now they should be using non-merged-usr chroots.

I would have expected that buildds use debootstrap from unstable, but
I'm not a buildd admin, so I trust you to know more about that then me.
Thanks for correcting me on that and sorry if that caused confusion.

Still, in the hopefully not too distant future, we will have such a
debootstrap in stable, so it's probably a good idea to be prepared for
that by then. TTBOMK, there are no plans to forcefully upgrade systems
to a merged-usr setup on stretch → buster upgrades.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Acknowledgement sent to Philipp Kern <pkern@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>. (Sat, 14 Jul 2018 16:42:02 GMT) (full text, mbox, link).

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

On 14.07.2018 13:01, Michael Biebl wrote:
> Am 14.07.2018 um 12:28 schrieb Mattia Rizzolo:
>> On Sat, Jul 14, 2018 at 11:59:37AM +0200, Michael Biebl wrote:
>>> debootstrap was changed (again) in 1.0.102 to now default to
>>> --merged-usr [1].
>>>
>>> Systems are not forcefully upgraded to a merged-usr setup atm though.
>>> buildds are regularly re-created from scratch and will thus have a
>>> merged-usr setup.
>>> This means, binaries that were built in a merged-usr buildd environment
>>> will now run on a lot of non-merged-usr setups.
>>
>> Is that really so?  I expect buildds to run with stable's debootstrap,
>> so for now they should be using non-merged-usr chroots.
> 
> I would have expected that buildds use debootstrap from unstable, but
> I'm not a buildd admin, so I trust you to know more about that then me.
> Thanks for correcting me on that and sorry if that caused confusion.

For the record: buildds usually (except new architectures) run stable
and hence have no easy way of pulling in a newer debootstrap. That also
makes them relatively easy to reason about. Packages we forked in the
past were sbuild and sometimes schroot (although we try very hard to
avoid that).

> Still, in the hopefully not too distant future, we will have such a
> debootstrap in stable, so it's probably a good idea to be prepared for
> that by then. TTBOMK, there are no plans to forcefully upgrade systems
> to a merged-usr setup on stretch → buster upgrades.

I suppose this point still stands. :)

Kind regards
Philipp Kern

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Thu, 08 Nov 2018 17:57:02 GMT) (full text, mbox, link).

Acknowledgement sent to Simon McVittie <smcv@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>. (Thu, 08 Nov 2018 17:57:02 GMT) (full text, mbox, link).

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

On Sat, 14 Jul 2018 at 18:39:36 +0200, Philipp Kern wrote:
> On 14.07.2018 13:01, Michael Biebl wrote:
> > I would have expected that buildds use debootstrap from unstable, but
> > I'm not a buildd admin, so I trust you to know more about that then me.
> > Thanks for correcting me on that and sorry if that caused confusion.
> 
> For the record: buildds usually (except new architectures) run stable
> and hence have no easy way of pulling in a newer debootstrap. That also
> makes them relatively easy to reason about. Packages we forked in the
> past were sbuild and sometimes schroot (although we try very hard to
> avoid that).

According to <https://bugs.debian.org/913229> buildds now run debootstrap
from stretch-backports, so they would already be using merged /usr if
it wasn't for the fact that the debootstrap backport is currently out
of date with respect to buster.

    smcv

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Thu, 08 Nov 2018 18:45:05 GMT) (full text, mbox, link).

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

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

On Sat, 14 Jul 2018 at 11:59:37 +0200, Michael Biebl wrote:
> If we could auto-detect any problems resulting from that via the
> reproducible builds effort, this would be great.

The attached patch is entirely untested, but hopefully works.

    smcv

[0001-reproducible-perform-build2-in-merged-usr-environmen.patch (text/x-diff, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Fri, 09 Nov 2018 13:15:03 GMT) (full text, mbox, link).

Acknowledgement sent to Holger Levsen <holger@layer-acht.org>:
Extra info received and forwarded to list. Copy sent to Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>. (Fri, 09 Nov 2018 13:15:03 GMT) (full text, mbox, link).

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

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

Hi,

On Thu, Nov 08, 2018 at 06:41:18PM +0000, Simon McVittie wrote:
> On Sat, 14 Jul 2018 at 11:59:37 +0200, Michael Biebl wrote:
> > If we could auto-detect any problems resulting from that via the
> > reproducible builds effort, this would be great.
> The attached patch is entirely untested, but hopefully works.

thanks, Simon, applied and deployed.

do any of you know a package which currently builds differently
depending on this? I'd like to test this change now :)


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Reply sent to Holger Levsen <holger@layer-acht.org>:
You have taken responsibility. (Fri, 09 Nov 2018 13:21:07 GMT) (full text, mbox, link).

Notification sent to Chris Lamb <lamby@debian.org>:
Bug acknowledged by developer. (Fri, 09 Nov 2018 13:21:07 GMT) (full text, mbox, link).

Message #43 received at 901473-done@bugs.debian.org (full text, mbox, reply):

closing, as merged & deployed.


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Fri, 09 Nov 2018 13:24:03 GMT) (full text, mbox, link).

Acknowledgement sent to Simon McVittie <smcv@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>. (Fri, 09 Nov 2018 13:24:03 GMT) (full text, mbox, link).

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

On Fri, 09 Nov 2018 at 13:10:26 +0000, Holger Levsen wrote:
> On Thu, Nov 08, 2018 at 06:41:18PM +0000, Simon McVittie wrote:
> > On Sat, 14 Jul 2018 at 11:59:37 +0200, Michael Biebl wrote:
> > > If we could auto-detect any problems resulting from that via the
> > > reproducible builds effort, this would be great.
> > The attached patch is entirely untested, but hopefully works.
> 
> thanks, Simon, applied and deployed.
> 
> do any of you know a package which currently builds differently
> depending on this? I'd like to test this change now :)

The version of quilt in buster (0.65-2) builds differently, in simple
enough ways to give nice diffoscope output. That bug is fixed in unstable
(0.65-3), so please try building both - I hope you will find that quilt
is currently unreproducible in buster and reproducible in unstable.

    smcv

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Fri, 09 Nov 2018 13:39:06 GMT) (full text, mbox, link).

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

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

On Fri, Nov 09, 2018 at 01:21:13PM +0000, Simon McVittie wrote:
> The version of quilt in buster (0.65-2) builds differently, in simple
> enough ways to give nice diffoscope output. That bug is fixed in unstable
> (0.65-3), so please try building both - I hope you will find that quilt
> is currently unreproducible in buster and reproducible in unstable.

triggered both, thanks.


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Fri, 09 Nov 2018 14:00:15 GMT) (full text, mbox, link).

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

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

On Fri, Nov 09, 2018 at 01:21:13PM +0000, Simon McVittie wrote:
> The version of quilt in buster (0.65-2) builds differently, in simple
> enough ways to give nice diffoscope output. That bug is fixed in unstable
> (0.65-3), so please try building both - I hope you will find that quilt
> is currently unreproducible in buster and reproducible in unstable.

works nicely, see
https://tests.reproducible-builds.org/debian/rb-pkg/buster/amd64/diffoscope-results/quilt.html
while quilt in unstable indeed builds reproducible.

nice work, thanks again!


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Fri, 09 Nov 2018 14:12:02 GMT) (full text, mbox, link).

Acknowledgement sent to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>. (Fri, 09 Nov 2018 14:12:02 GMT) (full text, mbox, link).

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

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

Am 09.11.18 um 14:10 schrieb Holger Levsen:
> do any of you know a package which currently builds differently
> depending on this? I'd like to test this change now :)

Another test case should be src:systemd

When built in a merged-usr environment, meson will embed a wrong RUNPATH
into the test-binaries.
This should show up in the diffoscope output.

Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Fri, 09 Nov 2018 14:15:03 GMT) (full text, mbox, link).

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

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

On Fri, Nov 09, 2018 at 03:09:01PM +0100, Michael Biebl wrote:
> Another test case should be src:systemd
> When built in a merged-usr environment, meson will embed a wrong RUNPATH
> into the test-binaries.
> This should show up in the diffoscope output.

triggered as well. (you can do this too: just click on the 'recycle'
icons on eg reproducible.debian.net/systemd :)


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Fri, 09 Nov 2018 19:00:03 GMT) (full text, mbox, link).

Acknowledgement sent to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>. (Fri, 09 Nov 2018 19:00:03 GMT) (full text, mbox, link).

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

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

Am 09.11.18 um 15:12 schrieb Holger Levsen:
> On Fri, Nov 09, 2018 at 03:09:01PM +0100, Michael Biebl wrote:
>> Another test case should be src:systemd
>> When built in a merged-usr environment, meson will embed a wrong RUNPATH
>> into the test-binaries.
>> This should show up in the diffoscope output.
> 
> triggered as well. 

Thanks!
Looks like this did indeed trigger a failure:
https://tests.reproducible-builds.org/debian/dbdtxt/unstable/amd64/systemd_239-11.diffoscope.txt.gz

I do see the expected RUNPATH related diffs like e.g. in:

> │ │ │ ├── ./usr/lib/systemd/tests/test-hexdecoct
...
> │ │ │ │ │    0x00000878 48415245 44002f6c 69622f73 79737465 HARED./lib/syste
> │ │ │ │ │ -  0x00000888 6d640068 61726564 00                md.hared.
> │ │ │ │ │ +  0x00000888 6d640068 61726564 3a244f52 4947494e md.hared:$ORIGIN
> │ │ │ │ │ +  0x00000898 2f2e2e2f 2e2e2f2e 2e2f2e2e 2f6c6962 /../../../../lib
> │ │ │ │ │ +  0x000008a8 2f783836 5f36342d 6c696e75 782d676e /x86_64-linux-gn
> │ │ │ │ │ +  0x000008b8 7500   


Now we just need an archive rebuild and a before and after to see which
new failures we get because of merged-usr :-)

Michael



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Fri, 09 Nov 2018 19:24:04 GMT) (full text, mbox, link).

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

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

On Fri, Nov 09, 2018 at 07:56:27PM +0100, Michael Biebl wrote:
> Thanks!
> Looks like this did indeed trigger a failure:
> https://tests.reproducible-builds.org/debian/dbdtxt/unstable/amd64/systemd_239-11.diffoscope.txt.gz
> 
> I do see the expected RUNPATH related diffs like e.g. in:
> 
> > │ │ │ ├── ./usr/lib/systemd/tests/test-hexdecoct
> ...
> > │ │ │ │ │    0x00000878 48415245 44002f6c 69622f73 79737465 HARED./lib/syste
> > │ │ │ │ │ -  0x00000888 6d640068 61726564 00                md.hared.
> > │ │ │ │ │ +  0x00000888 6d640068 61726564 3a244f52 4947494e md.hared:$ORIGIN
> > │ │ │ │ │ +  0x00000898 2f2e2e2f 2e2e2f2e 2e2f2e2e 2f6c6962 /../../../../lib
> > │ │ │ │ │ +  0x000008a8 2f783836 5f36342d 6c696e75 782d676e /x86_64-linux-gn
> > │ │ │ │ │ +  0x000008b8 7500   
 
That's due to usrmerge? (and not rebuilding in a different path?)
There's no "usr/bin" in that diffoscope output anywhere?

> Now we just need an archive rebuild and a before and after to see which
> new failures we get because of merged-usr :-)

should be done in 3-4 weeks for amd64 and arm64, on buster and sid. i386
and armhf will follow 1-2 weeks later.


-- 
cheers,
	Holger

-------------------------------------------------------------------------------
               holger@(debian|reproducible-builds|layer-acht).org
       PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C

[signature.asc (application/pgp-signature, inline)]

Information forwarded to debian-bugs-dist@lists.debian.org, Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>:
Bug#901473; Package jenkins.debian.org. (Fri, 09 Nov 2018 20:36:03 GMT) (full text, mbox, link).

Acknowledgement sent to Michael Biebl <biebl@debian.org>:
Extra info received and forwarded to list. Copy sent to Debian Jenkins Team <qa-jenkins-dev@lists.alioth.debian.org>. (Fri, 09 Nov 2018 20:36:03 GMT) (full text, mbox, link).

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

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

Am 09.11.18 um 20:22 schrieb Holger Levsen:
> On Fri, Nov 09, 2018 at 07:56:27PM +0100, Michael Biebl wrote:

>>> │ │ │ ├── ./usr/lib/systemd/tests/test-hexdecoct
>> ...
>>> │ │ │ │ │    0x00000878 48415245 44002f6c 69622f73 79737465 HARED./lib/syste
>>> │ │ │ │ │ -  0x00000888 6d640068 61726564 00                md.hared.
>>> │ │ │ │ │ +  0x00000888 6d640068 61726564 3a244f52 4947494e md.hared:$ORIGIN
>>> │ │ │ │ │ +  0x00000898 2f2e2e2f 2e2e2f2e 2e2f2e2e 2f6c6962 /../../../../lib
>>> │ │ │ │ │ +  0x000008a8 2f783836 5f36342d 6c696e75 782d676e /x86_64-linux-gn
>>> │ │ │ │ │ +  0x000008b8 7500   
>  
> That's due to usrmerge? (and not rebuilding in a different path?)
> There's no "usr/bin" in that diffoscope output anywhere?

Yeah, somehow meson get's confused on a usr-merged system and then
embeds such a bogus RUNPATH
See
https://github.com/mesonbuild/meson/issues/4392
and
https://github.com/systemd/systemd/issues/10430

regards,
Michael


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Bug archived. Request was from Debbugs Internal Request <owner@bugs.debian.org> to internal_control@bugs.debian.org. (Sat, 08 Dec 2018 07:32:50 GMT) (full text, mbox, link).

Send a report that this bug log contains spam.

Debian bug tracking system administrator <owner@bugs.debian.org>. Last modified: Wed May 17 10:44:31 2023; Machine Name: buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Debian Bug report logs - #901473 jenkins.debian.org: Vary merged-usr in reproducibility testing?

Debian Bug report logs - #901473
jenkins.debian.org: Vary merged-usr in reproducibility testing?