unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: guix-devel@gnu.org
Subject: Re: Reproducible Builds Summit 2022, nar support in diffoscope
Date: Sat, 05 Nov 2022 11:18:52 +0100	[thread overview]
Message-ID: <87r0yhk8du.fsf@cbaines.net> (raw)
In-Reply-To: <Y2PF0aUsG3QQlAa9@pbp>

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


Efraim Flashner <efraim@flashner.co.il> writes:

> Chris and I are here at the reproducible builds summit in Venice, we're
> winding down now but it's been a great time meeting everyone and
> planning out upcoming tasks.

One thing I forgot to tell Efraim about is that I got around to looking
at nar support in diffoscope. I know this isn't essential as you can
just unpack the nars, then compare (as I think guix challenge does), but
I've been thinking this could make it easier to compare nars.

Anyway, as part of this I proposed adding lzip support, since nars can
be lzipped, that turned out to be quite easy:

  https://salsa.debian.org/reproducible-builds/diffoscope/-/merge_requests/106

I'm finding nar support a bit harder though, I've raised a merge request
anyway to see if I can get any feedback:

  https://salsa.debian.org/reproducible-builds/diffoscope/-/merge_requests/107

Chris

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

  parent reply	other threads:[~2022-11-05 10:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 13:44 Reproducible Builds Summit 2022 Efraim Flashner
2022-11-03 15:25 ` Ludovic Courtès
2022-11-05 10:18 ` Christopher Baines [this message]
2022-11-05 18:04   ` Reproducible Builds Summit 2022, nar support in diffoscope Ludovic Courtès
2022-11-05 12:30 ` Reproducible Builds Summit 2022 zimoun
2022-11-05 13:25   ` Christopher Baines

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=87r0yhk8du.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    /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).