unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 46186@debbugs.gnu.org
Subject: bug#46186: Some substitutes are broken (TLS error)
Date: Mon, 08 Feb 2021 09:49:40 +0100	[thread overview]
Message-ID: <375e692bb5fbd09c20327e4afebe83810ee709c3.camel@telenet.be> (raw)
In-Reply-To: <87wnvjy42v.fsf@gnu.org>

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

On Sun, 2021-02-07 at 22:12 +0100, Ludovic Courtès wrote:
> Is it still happening, consistently?  Or did you eventually manage to
> download that substitute?

IIRC, I eventually just build libreoffice with --no-substitutes or
--fallback.  I'll have to check if this still happens, though I
don't know how at the moment  (an up-to-date libreoffice and emacs
is currently installed).

> This could related to <https://issues.guix.gnu.org/46330>.

Seems plausible to me.

> > To reproduce:
> > guix time-machine --commit=23a5dcce1d893b8f5c5301ae3c1af863776ed3cf \
> >   build libreoffice
> 
> I tried just in case but couldn’t reproduce it.  What matters here is
> the guix-daemon in use (which store item?), but I suspect it’s
> non-deterministic anyway.

I looked at the "guix pull --list-generations" output, and I couldn't
find the commit 23a5dcce1d893b8f5c5301ae3c1af863776ed3cf, weird.  (I
was trying to find the corresponding date and then look in the closest
guix system generation for the guix-daemon version)

Thanks,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-02-08 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30  9:52 bug#46186: Some substitutes are broken (TLS error) Maxime Devos
2021-02-07 21:12 ` Ludovic Courtès
2021-02-08  8:49   ` Maxime Devos [this message]
2021-02-08  9:31     ` Maxime Devos
2021-02-09  8:36     ` Ludovic Courtès
2021-02-09 12:29       ` Maxime Devos

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=375e692bb5fbd09c20327e4afebe83810ee709c3.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=46186@debbugs.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).