From: zimoun <zimon.toutoune@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 27100@debbugs.gnu.org
Subject: bug#27100: Unnecessary backtrace by guix/build/download.scm
Date: Thu, 25 Feb 2021 00:56:02 +0100 [thread overview]
Message-ID: <86ft1lkokt.fsf@gmail.com> (raw)
In-Reply-To: <86h7pnmumd.fsf@gmail.com> (zimoun's message of "Wed, 18 Nov 2020 00:27:54 +0100")
Hi,
On Wed, 18 Nov 2020 at 00:27, zimoun <zimon.toutoune@gmail.com> wrote:
> On Sat, 27 May 2017 at 13:36, Danny Milosavljevic <dannym@scratchpost.org> wrote:
>> guix [env]$ ./pre-inst-env guix import pypi flex
>> Backtrace:
>
> [...] Ugly
>
>> guix/build/download.scm:417:6: In procedure tls-wrap:
>> guix/build/download.scm:417:6: X.509 certificate of 'pypi.python.org' could not be verified:
>> signer-not-found
>> invalid
>>
>> Also, the most interesting information, which is which certificates it DID know and where it got them, is not printed.
>
> Well, the bug #27100 [1] is solved now, I guess. First, the command
>
> $ guix import pypi flex
>
> works now. And the command:
>
> $ guix import pypi kikoo
> following redirection to `https://pypi.org/pypi/kikoo/json/'...
> guix import: error: failed to download meta-data for package 'kikoo'
>
> fails gracefully. What remains is “guix import pypi kikoo -r” but it is
> tracked by #44115 about the recursive option of all the importers.
I think this bug is now addressed and could be closed. WDYT?
All the best,
simon
next prev parent reply other threads:[~2021-02-24 23:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 11:36 bug#27100: Unnecessary backtrace by guix/build/download.scm Danny Milosavljevic
2017-05-27 11:40 ` bug#27100: And another unnecessary " Danny Milosavljevic
2020-11-17 23:27 ` bug#27100: Unnecessary " zimoun
2021-02-24 23:56 ` zimoun [this message]
2021-02-25 1:18 ` Danny Milosavljevic
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=86ft1lkokt.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=27100@debbugs.gnu.org \
--cc=dannym@scratchpost.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 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.