unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Reproducible builds: a means to an end
Date: Tue, 17 Nov 2015 22:45:30 +0100	[thread overview]
Message-ID: <87y4dwqozp.fsf@gnu.org> (raw)
In-Reply-To: <CADrxHD8HrK+Hmzw0277ZyBgUthENodwgsOimVqhtwWZW1ckNow@mail.gmail.com> (Alex Vong's message of "Wed, 18 Nov 2015 02:01:45 +0800")

Alex Vong <alexvong1995@gmail.com> skribis:

> On 16/11/2015, Ludovic Courtès <ludo@gnu.org> wrote:

[...]

>> Sometimes there are ready-made patches that can be found in Debian or
>> other distros, sometimes not.  Often they’re hard to find though (for
>> instance, patch-tracker.debian.org seems to be off-line.)
>>
> Yes, according to
> <https://lists.debian.org/debian-devel/2014/05/msg00889.html>, the
> maintainer of patch-tracker.debian.org has been missing in action
> until now. I think the website will be off-line in the near future.

OK.

>> “guix challenge” is a simple way to find out which packages are non
>> deterministic.  That’s how I found about those that can be seen at
>> <http://bugs.gnu.org/guix> for example.
>>
> Does that mean we should have a bug report for every non-reproducible
> packages? Or should we only have bug reports for popular packages?

It’s OK to have bug reports for any package, as long as people volunteer
to fix the bugs.  Often it’s a trivial timestamp issue; sometimes it’s
more involved, like <http://bugs.gnu.org/21918>.

Does Debbugs allow us to add custom tags?  We could have a “determinism”
tag to facilitate triage.

Ludo’.

  reply	other threads:[~2015-11-17 21:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11 14:55 Reproducible builds: a means to an end Ludovic Courtès
2015-11-12 20:13 ` Jan Synáček
2015-11-16 14:44 ` Ricardo Wurmus
2015-11-16 15:40   ` Ludovic Courtès
2015-11-17 18:01     ` Alex Vong
2015-11-17 21:45       ` Ludovic Courtès [this message]
2015-11-18 13:57         ` Alex Vong
2015-11-18 18:20           ` Ludovic Courtès
2015-11-19  8:14             ` Efraim Flashner
2015-11-19 14:45             ` Alex Vong
2015-11-19 16:09               ` Ludovic Courtès
2015-11-20  6:22                 ` Alex Vong
2015-11-21 10:41                   ` Ludovic Courtès
2015-11-21 13:53                     ` Alex Vong
2015-11-21 15:50                       ` Ludovic Courtès

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=87y4dwqozp.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alexvong1995@gmail.com \
    --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).