GNU bug report logs - #71024
Update diffoscope to 268

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Vagrant Cascadian <vagrant <at> reproducible-builds.org>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#71024: closed (Update diffoscope to 268)
Date: Fri, 31 May 2024 17:32:01 +0000

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

Your message dated Fri, 31 May 2024 10:30:50 -0700
with message-id <877cf9opmd.fsf <at> wireframe>
and subject line Re: bug#71024: Update diffoscope to 268
has caused the debbugs.gnu.org bug report #71024,
regarding Update diffoscope to 268
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
71024: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=71024
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Vagrant Cascadian <vagrant <at> reproducible-builds.org>
To: guix-patches <at> gnu.org
Subject: Update diffoscope to 267 (with xz bonus update)
Date: Fri, 17 May 2024 18:46:53 -0700

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

The upcoming patches update diffoscope to 267, which requires a newer
version of xz to pass the test suites (No, no, not the *evil* versions,
just the same version that is in core-updates, 5.4.5! (although that
version has shadows cast on it too due to involvement of a certain
infamous internet identity, caveat emptor)).

I made a versioned xz variant to avoid a world rebuild so we can update
diffoscope before updating core-updates, hopefully I did it mostly
right... :)

Uhhh... so yeah, send in the clowns... er, patches!

live well,
  vagrant

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

[Message part 5 (message/rfc822, inline)]

From: Vagrant Cascadian <vagrant <at> reproducible-builds.org>
To: Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
Cc: 71024-done <at> debbugs.gnu.org
Subject: Re: bug#71024: Update diffoscope to 268
Date: Fri, 31 May 2024 10:30:50 -0700

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

On 2024-05-29, Maxim Cournoyer wrote:
> Vagrant Cascadian <vagrant <at> reproducible-builds.org> writes:
>> Well, again, upstream has fixed it even better:
>>
>>   https://salsa.debian.org/reproducible-builds/diffoscope/-/commit/2a361d7dff135d3e832161f587a55a62fcbec9f2
>>
>> Tested fine for me building against that commit.
>>
>> So ... wait again till another release (and maybe find new breakage in
>> the new release), or build against an untagged commit, or pull in a
>> patch from the upstream commit? :)
>
> If you want to get done with this, I'd recommend pulling a patch from
> the upstream commit.  Then when we get to upgrading to the next release
> we can drop such patch.

Apparently waiting was the thing to do... 269 was released with only
that change!

Pushed as c7888f5361fbdbe5182e7dbe90ccc12e2d95d3c3.

live well,
  vagrant

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

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.