all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tanguy Le Carrour <tanguy@bioneland.org>
To: "Marius Bakke" <mbakke@fastmail.com>,
	"Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: gnu: python: Update to 3.8.0.
Date: Wed, 13 Nov 2019 09:03:23 +0100	[thread overview]
Message-ID: <20191113080323.u2xfipa43dhecr3w@rafflesia> (raw)
In-Reply-To: <CAE4v=piqy0-NeANKOAhVyhi_yRTHhO7K-EVufPTzDAKv=a+K3A@mail.gmail.com>

Hi Marius, hi Gábor!

Le 11/04, Gábor Boskovits a écrit :
> Tanguy Le Carrour <tanguy@bioneland.org> ezt írta (időpont: 2019. nov. 4., H, 11:50):
> > Le 11/04, Gábor Boskovits a écrit :
> > > Tanguy Le Carrour <tanguy@bioneland.org> ezt írta (időpont: 2019. nov. 4.,
> > > > `./pre-inst-env guix build --rounds=2 python@3.8` always fails with:
> > > > """
> > > > output ‘/gnu/store/…-python-3.8.0’ of ‘/gnu/store/…-python-3.8.0.drv’
> > > > differs from previous round
> > > > """
> > […]
> > First time I hear of diffoscope! I had a look at the output (html
> > attached), but couldn't make sense of it!
> Nice, one thing that looks problematic is that there seems to be a mismatch
> in the hash.
>  At one line you can see the shabang modified to a different path...
> I don't yet know the reason of that, but it quite suspicious...
> One thing, when dealing with things like like this, one should first fix
> the readable differences,
> and only then dig deeper, as fixing those often cascade, and fix more than
> anticipated.

Sorry it took me so long, but I finally had some time yesterday evening to go
through the report!

I found 4 types of errors:

 1. `stat` reporting a different "Birth" for folders, which I assume are
    perfectly normal.
 2. different paths for `python3.8` in the shebang of some scripts.
 3. different paths in prefix for `python3.8` (some origin as above).
 4. everything else is "Max report size reached"!

I don't really know where to go from here? Am I supposed to investigate
errors of type 4?!

Regards,

-- 
Tanguy

  reply	other threads:[~2019-11-13  8:03 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23  9:11 gnu: python: Update to 3.8.0 Tanguy Le Carrour
2019-10-23 11:42 ` Hartmut Goebel
2019-10-23 12:51   ` Tanguy Le Carrour
2019-10-23 13:16     ` Hartmut Goebel
2019-10-30 16:04       ` Tanguy Le Carrour
2019-10-30 18:01         ` Tanguy Le Carrour
2019-10-31 23:08           ` Marius Bakke
2019-11-04  9:15             ` Tanguy Le Carrour
2019-11-04  9:19               ` Gábor Boskovits
2019-11-04 10:50                 ` Tanguy Le Carrour
2019-11-04 12:31                   ` Gábor Boskovits
2019-11-13  8:03                     ` Tanguy Le Carrour [this message]
2019-11-13 11:29                       ` Tobias Geerinckx-Rice
2019-11-13 13:25                         ` Tanguy Le Carrour
2019-11-13 11:34                       ` Gábor Boskovits
2019-11-13 13:23                         ` Tanguy Le Carrour
2019-11-13 13:27                           ` Gábor Boskovits
2019-11-14  8:48                             ` Tanguy Le Carrour
2019-11-10 23:02               ` Marius Bakke
2019-10-23 17:48   ` Marius Bakke
2019-10-24  8:03     ` Hartmut Goebel

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

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

  git send-email \
    --in-reply-to=20191113080323.u2xfipa43dhecr3w@rafflesia \
    --to=tanguy@bioneland.org \
    --cc=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mbakke@fastmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.