unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@reproducible-builds.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 71024@debbugs.gnu.org
Subject: [bug#71024] Update diffoscope to 268
Date: Tue, 28 May 2024 15:33:22 -0700	[thread overview]
Message-ID: <87plt5o9cd.fsf@wireframe> (raw)
In-Reply-To: <87bk4ti883.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

On 2024-05-25, Maxim Cournoyer wrote:
> Vagrant Cascadian <vagrant@reproducible-builds.org> writes:
>> On 2024-05-21, Maxim Cournoyer wrote:
>>> Vagrant Cascadian <vagrant@reproducible-builds.org> writes:
>>>> On 2024-05-20, Vagrant Cascadian wrote:
>>>>> On 2024-05-20, Maxim Cournoyer wrote:
>>>>>> vagrant@reproducible-builds.org writes:
>>>>>>> From: Vagrant Cascadian <vagrant@reproducible-builds.org>
>>>>> Or fixing diffoscope to work with the older xz version in master
>>>>> (5.2.x?) that guix is already using, which, now that I have spelled out
>>>>> all of the above, seems possibly a much better idea!
...
>> Well, version 268 was just released, which fixes the xz issue ... but
>> introduces a test failure for 7z... which is worked around in the
>> attached patch.
...
>> +              (substitute* "tests/comparators/test_sevenz.py"
>> +                ((", skip_unless_tool_is_at_least") ", skip_unless_tool_is_at_least, skip_unless_tool_is_at_most")
>> +                (("@skip_unless_tool_is_at_least") "@skip_unless_tool_is_at_most(\"7z\", sevenz_version, \"63\")\n@skip_unless_tool_is_at_least"))))
>
> That would LGTM, if it didn't so severely bust our 80 maximum column
> width convention :-).  Would you mind editing it into conformance?

Oops. must not have guix linted that one!


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? :)


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2024-05-28 22:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-18  1:46 [bug#71024] Update diffoscope to 267 (with xz bonus update) Vagrant Cascadian
2024-05-18  1:53 ` Vagrant Cascadian
2024-05-18  1:53   ` Vagrant Cascadian
2024-05-18  2:01     ` Vagrant Cascadian
2024-05-21  2:48     ` Maxim Cournoyer
2024-05-18  3:50 ` [bug#71024] [PATCH 1/2] gnu: Add xz-5.4 variant vagrant
2024-05-18  3:50   ` [bug#71024] [PATCH 2/2] gnu: diffoscope: Update to 267 vagrant
2024-05-21  2:46   ` [bug#71024] Update diffoscope to 267 (with xz bonus update) Maxim Cournoyer
2024-05-21  6:01     ` Vagrant Cascadian
2024-05-21 19:20       ` Vagrant Cascadian
2024-05-22  0:06         ` Maxim Cournoyer
2024-05-24 14:41           ` [bug#71024] Update diffoscope to 268 Vagrant Cascadian
2024-05-26  3:05             ` Maxim Cournoyer
2024-05-28 22:33               ` Vagrant Cascadian [this message]
2024-05-30  1:02                 ` Maxim Cournoyer
2024-05-31 17:30                   ` bug#71024: " Vagrant Cascadian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87plt5o9cd.fsf@wireframe \
    --to=vagrant@reproducible-builds.org \
    --cc=71024@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).