From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: gnutls: Replace with 3.5.8 [fixes GNUTLS-SA-2017-{1, 2}].
Date: Thu, 12 Jan 2017 15:18:24 +0100 [thread overview]
Message-ID: <8760lk4b0v.fsf@gnu.org> (raw)
In-Reply-To: <20170111171741.GA21549@jasmine> (Leo Famulari's message of "Wed, 11 Jan 2017 12:17:41 -0500")
Leo Famulari <leo@famulari.name> skribis:
> On Tue, Jan 10, 2017 at 06:08:39PM -0500, Leo Famulari wrote:
>> On Tue, Jan 10, 2017 at 11:41:40PM +0100, Ludovic Courtès wrote:
>> > Leo Famulari <leo@famulari.name> skribis:
>> > > The last time I noticed an exported replacement, I found that it was
>> > > resolved non-deterministically (using `guix build -S` in a loop), and
>> > > we made the replacement private:
>> > >
>> > > http://git.savannah.gnu.org/cgit/guix.git/commit/?id=69aa6e0995b55a38d5ce174602a107645be726d5
>> >
>> > I can’t seem to reproduce it here, but it sounds like an interesting
>> > bug. :-)
>>
>> Me neither. IIRC, it would manifest at least 1/10 iterations of the
>> loop.
>
> I can reproduce it by applying the diff below on
> 88f2dd1ddf8123f628ee0b64406b6fd2a6a9f076 and running:
>
> $ while true; do ./pre-inst-env guix build gnutls -S; done
> guix build: warning: ambiguous package specification `gnutls'
> guix build: warning: choosing gnutls-3.5.4 from gnu/packages/tls.scm:139:2
> /gnu/store/kfjzkvlxjp98mcf356ay027vy5p5lsp3-gnutls-3.5.8.tar.xz
> guix build: warning: ambiguous package specification `gnutls'
> guix build: warning: choosing gnutls-3.5.4 from gnu/packages/tls.scm:216:2
> /gnu/store/kfjzkvlxjp98mcf356ay027vy5p5lsp3-gnutls-3.5.8.tar.xz
> guix build: warning: ambiguous package specification `gnutls'
> guix build: warning: choosing gnutls-3.5.4 from gnu/packages/tls.scm:216:2
> /gnu/store/kfjzkvlxjp98mcf356ay027vy5p5lsp3-gnutls-3.5.8.tar.xz
> guix build: warning: ambiguous package specification `gnutls'
> guix build: warning: choosing gnutls-3.5.4 from gnu/packages/tls.scm:139:2
> /gnu/store/kfjzkvlxjp98mcf356ay027vy5p5lsp3-gnutls-3.5.8.tar.xz
Oh, I see. I can imagine that this has to do with the ordering of
package objects and first-class variables in the various hash tables and
vhashes involved.
I’d say it doesn’t matter much because we shouldn’t be providing two
packages with the exact same name and version in the first place (which
is what this patch does).
Ludo’.
prev parent reply other threads:[~2017-01-12 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 18:18 GnuTLS security advisories Leo Famulari
2017-01-10 22:15 ` [PATCH] gnu: gnutls: Replace with 3.5.8 [fixes GNUTLS-SA-2017-{1, 2}] Ludovic Courtès
2017-01-10 22:36 ` [PATCH] gnu: gnutls: Replace with 3.5.8 [fixes GNUTLS-SA-2017-{1,2}] Leo Famulari
2017-01-10 22:41 ` [PATCH] gnu: gnutls: Replace with 3.5.8 [fixes GNUTLS-SA-2017-{1, 2}] Ludovic Courtès
2017-01-10 23:08 ` [PATCH] gnu: gnutls: Replace with 3.5.8 [fixes GNUTLS-SA-2017-{1,2}] Leo Famulari
2017-01-11 17:17 ` Leo Famulari
2017-01-12 14:18 ` 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=8760lk4b0v.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).