unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Status update on reproducible builds in Guix
Date: Sun, 5 Nov 2017 20:04:47 +0100	[thread overview]
Message-ID: <CAE4v=piNGtAa9fgDB1XGJ4YibVD+1G_5U9RsCHTy6R5upPjfJw@mail.gmail.com> (raw)
In-Reply-To: <87efpcsp3m.fsf@gnu.org>

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

Yesteday we had a discussion about that on irc.
Here it goes:


[15:15:16] <g_bor> hello guix!
[15:16:01] <g_bor> do we have a proposed way to build pyc files
reproducibly?
[15:16:50] <g_bor> I've read in the report, that we are not there yet, but
is someone working on it?
[15:17:58] <lfam> g_bor: This is the report you mention? <
https://bugs.gnu.org/22533>
[15:18:10] <lfam> I'm not sure if anyone has been working on it since the
last message
[15:20:26] * Guest74 has joined #guix
[15:23:05] <g_bor> thx, just what i was looking for.
[15:23:26] <lfam> It's possible that some work in this area is pending on
the 'core-updates' Git branch, but I'm not sure
[15:37:41] <mb[m]1> At this stage we might as well wait for this to land
upstream: https://www.python.org/dev/peps/pep-0552/

So, it seems, that we are waiting for this pep to land upstream.


2017-11-05 16:49 GMT+01:00 Ludovic Courtès <ludo@gnu.org>:

> Jan Nieuwenhuizen <janneke@gnu.org> skribis:
>
> > Ludovic Courtès writes:
> >
> >> Here’s an update on reproducibility in Guix:
> >>
> >>   https://www.gnu.org/software/guix/news/reproducible-builds-
> a-status-update.html
> >
> > At least 78% to possibly 91% reproduciblility of packages is not bad.
> >
> > Is there a (small) core that is already 100% reprocucible, like the
> > installation binaries/USB installer, bare-bones.tmpl or even
> > lightweight-desktop.tmpl?
>
> Good question!  I think as soon as you have Python .pyc files in the
> dependency graph (reference graph), there are non-reproducible bits.  We
> certainly have Python stuff in the base system reference graph, so
> that’s one thing we should fix most urgently I guess.
>
> Ludo’.
>
>

[-- Attachment #2: Type: text/html, Size: 3322 bytes --]

  reply	other threads:[~2017-11-05 19:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 10:33 Status update on reproducible builds in Guix Ludovic Courtès
2017-11-01  6:22 ` Jan Nieuwenhuizen
2017-11-05 15:49   ` Ludovic Courtès
2017-11-05 19:04     ` Gábor Boskovits [this message]
2017-11-05 19:16       ` Hartmut Goebel
2017-11-05 19:17       ` ng0
2017-11-06  8:52       ` Ludovic Courtès
2017-11-06 10:19         ` Hartmut Goebel
2017-11-06 11:47           ` Gábor Boskovits
2017-11-07  9:55             ` Eric Myhre
2017-11-07 10:12               ` Hartmut Goebel
2017-11-06 21:29           ` Marius Bakke
2017-11-07  9:16             ` Hartmut Goebel
2017-11-07 19:00               ` Marius Bakke
2017-11-06 21:14         ` Marius Bakke

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='CAE4v=piNGtAa9fgDB1XGJ4YibVD+1G_5U9RsCHTy6R5upPjfJw@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).