From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Sarah Morgensen <iskarian@mgsn.dev>
Cc: 49228-done@debbugs.gnu.org
Subject: bug#49228: guix import go fails when module does not have a documenation on pkg.go.dev
Date: Mon, 28 Jun 2021 08:58:27 +0200 [thread overview]
Message-ID: <20210628085827.6e89f13f@alma-ubu.fritz.box> (raw)
In-Reply-To: <86eecp77ar.fsf@mgsn.dev>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
Hi Sarah,
On Fri, 25 Jun 2021 18:18:04 -0700
Sarah Morgensen <iskarian@mgsn.dev> wrote:
> There is currently a patch for this (mine; though I could have named
> it better, I suppose):
>
> https://issues.guix.gnu.org/49200
Nice coincident :-)
I pushed your patch as
9d9152425e96c408357d0f4961767a5c08076c13
Thanks.
> > Additionally, it would be nice if the go-module->guix-package would
> > print out the module it would fetch next (like I did above). Then
> > the broken module would be easier to find in recursive mode.
>
> Error reporting in the importers is currently pretty inconsistent and
> could use a lot of improvement. You might be interested in taking a
> look at the PATCH v3 in <https://issues.guix.gnu.org/49196> which
> somewhat addresses this. Comments are always welcome! :)
Good to know. I will have a look at these patches the next days/weeks.
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2021-06-28 6:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 22:30 bug#49228: guix import go fails when module does not have a documenation on pkg.go.dev Björn Höfling
2021-06-26 1:18 ` Sarah Morgensen via Bug reports for GNU Guix
2021-06-28 6:58 ` Björn Höfling [this message]
2021-06-28 16:24 ` zimoun
2021-06-30 21:20 ` raingloom
2021-07-01 4:18 ` Sarah Morgensen via Bug reports for GNU Guix
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=20210628085827.6e89f13f@alma-ubu.fritz.box \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=49228-done@debbugs.gnu.org \
--cc=iskarian@mgsn.dev \
/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).