all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stephen Paul Weber <singpolyma@singpolyma.net>
To: 52362@debbugs.gnu.org
Subject: bug#52362: [PATCH] guix: import: go: Use correct tag for go module in subdirectory.
Date: Fri, 14 Jan 2022 20:56:06 -0500	[thread overview]
Message-ID: <YeIpthv5P/B5zTbG@singpolyma-beefy.lan> (raw)
In-Reply-To: <20220115014333.26372-1-singpolyma@singpolyma.net>

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

Somebody claiming to be Stephen Paul Weber wrote:
>https://go.dev/ref/mod says a module in a subdirectory has a tag prefixed with
>the subdirectory.

Dang.  This patch as written causes import of guix import go
github.com/jackc/pgx/v4 to fail. The /v4 suffix in this case appears to refer to
a branch and not a subdirectory, but the syntax is identical?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-01-15  1:57 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 [this message]
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 ` bug#52362: another patchset Attila Lendvai

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=YeIpthv5P/B5zTbG@singpolyma-beefy.lan \
    --to=singpolyma@singpolyma.net \
    --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 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.