unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>,
	63002-done@debbugs.gnu.org
Subject: bug#63002: Ubuntu 22.04 + GNU Guix, guile-gnutls-3.7.11: dependencies couldn't be built
Date: Fri, 05 Jan 2024 13:07:57 -0500	[thread overview]
Message-ID: <871qav1wn6.fsf@gmail.com> (raw)
In-Reply-To: <87cz3wgrgg.fsf@jpoiret.xyz> (Josselin Poiret's message of "Sat,  22 Apr 2023 12:07:59 +0200")

Hi,

Josselin Poiret <dev@jpoiret.xyz> writes:

> Hi Artyom, 
>
> "Artyom V. Poptsov" <poptsov.artyom@gmail.com> writes:
>
>> Initialized empty Git repository in /gnu/store/dpbxqzqmbhfy7jc2a9dyfi28fdvi04sd-guile-gnutls-3.7.11-checkout/.git/
>> fatal: unable to access 'https://gitlab.com/gnutls/guile/': The requested URL returned error: 403
>> Failed to do a shallow fetch; retrying a full fetch...
>> fatal: unable to access 'https://gitlab.com/gnutls/guile/': The requested URL returned error: 403
>> git-fetch: 'git fetch origin' failed with exit code 128
>
> It rather seems like you're just getting a 403 from gitlab, not that
> you can't validate the TLS certificate.  Can you access that url from a
> browser?  Are you using a proxy, but the Guix daemon is somehow not
> using it?

Closing, with the assumption that this was a transient error outside of
the control of Guix.

-- 
Thanks,
Maxim




      reply	other threads:[~2024-01-05 18:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 19:00 bug#63002: Ubuntu 22.04 + GNU Guix, guile-gnutls-3.7.11: dependencies couldn't be built Artyom V. Poptsov
2023-04-22 10:07 ` Josselin Poiret via Bug reports for GNU Guix
2024-01-05 18:07   ` Maxim Cournoyer [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=871qav1wn6.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=63002-done@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=poptsov.artyom@gmail.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 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).