From: ludo@gnu.org (Ludovic Courtès)
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: help-guix@gnu.org
Subject: Re: Unreproducible packages visibility
Date: Thu, 26 Jul 2018 17:36:58 +0200 [thread overview]
Message-ID: <876012vwit.fsf@gnu.org> (raw)
In-Reply-To: <20180720232435.6736e21b@alma-ubu> ("Björn Höfling"'s message of "Fri, 20 Jul 2018 23:24:35 +0200")
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> skribis:
> On Fri, 20 Jul 2018 12:08:24 -0300
> EuAndreh <eu@euandre.org> wrote:
>
>> Hello Guix!
>>
>> I know that making all packages reproducible is a current ongoing
>> effort, and I've seen a few bug reports in debbugs about specific
>> unreproducible packages.
>>
>> Is there a way to know about all unreproducible packages? Something
>> similar to how Debian reports[0] it's packages.
>>
>> [0]: https://tests.reproducible-builds.org/debian/reproducible.html
>
> https://www.gnu.org/software/guix/packages/reproducibility.html
>
> But it is out-of-date since nearly a year. Who knows more about that
> page? Ludo?
Producing that page was too resource intensive for our poor
hydra.gnu.org server, so we eventually disabled it.
We’re aiming to move the web site to a new server, and we may be able to
resume this and other things on that new server.
Speaking of which, help is needed to move the server! :-) If you’re
interested in helping out, and you’re familiar with DNS and load
balancing and things like that, please email guix-sysadmin@gnu.org!
Ludo’.
prev parent reply other threads:[~2018-07-26 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 15:08 Unreproducible packages visibility EuAndreh
2018-07-20 21:24 ` Björn Höfling
2018-07-26 15:36 ` Ludovic Courtès [this message]
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=876012vwit.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
--cc=help-guix@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.
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).