From: Attila Lendvai <attila@lendvai.name>
To: "52362@debbugs.gnu.org" <52362@debbugs.gnu.org>
Subject: bug#52362: another patchset
Date: Wed, 13 Apr 2022 14:26:51 +0000 [thread overview]
Message-ID: <y9U5agWrhqQDaR0EieoAUTleO_qyVlmgazVP0ilnWM18wIaWY1HKJPQM57N-aV6oA2RonxFQ59fTqY_uG-FHPJpsdS0nUBlxmaDa43XMR54=@lendvai.name> (raw)
In-Reply-To: <Ya/bU8a43auuMRP0@singpolyma-beefy.lan>
FYI,
i have extensive fixes to the go importer that i'm preparing for submission:
https://github.com/attila-lendvai-patches/guix/tree/import
it fixes this issue, and it can also recursively import rclone (and go-ethereum for that matter):
./pre-inst-env guix import go --recursive github.com/rclone/rclone
emits 100+ packages.
unfortunately, it fails on/skips:
guix import go github.com/billziss-gh/cgofuse
i suspect that it's probably because that module is not adhering to the git tag name rules.
--
- attila
PGP: 5D5F 45C7 DFCD 0A39
prev parent reply other threads:[~2022-04-13 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 22:08 bug#52362: guix import go error Stephen Paul Weber
2022-01-12 3:58 ` Stephen Paul Weber
2022-01-12 4:28 ` Stephen Paul Weber
2022-01-15 1:43 ` bug#52362: [PATCH] guix: import: go: Use correct tag for go module in subdirectory Stephen Paul Weber
2022-01-15 1:56 ` Stephen Paul Weber
2022-01-16 2:56 ` bug#52362: [PATCH v2] " Stephen Paul Weber
2022-01-16 3:32 ` bug#52362: [PATCH v3] " Stephen Paul Weber
2023-05-25 16:13 ` bug#52362: guix import go error Simon Tournier
2022-02-28 23:55 ` bug#52362: [PATCH v3] guix: import: go: Use correct tag for go module in subdirectory Nicolas Goaziou
2023-05-25 14:21 ` bug#52362: guix import go error Simon Tournier
2023-05-25 18:58 ` Nicolas Goaziou
2023-05-25 19:08 ` Simon Tournier
2022-04-13 14:26 ` Attila Lendvai [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='y9U5agWrhqQDaR0EieoAUTleO_qyVlmgazVP0ilnWM18wIaWY1HKJPQM57N-aV6oA2RonxFQ59fTqY_uG-FHPJpsdS0nUBlxmaDa43XMR54=@lendvai.name' \
--to=attila@lendvai.name \
--cc=52362@debbugs.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).