From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Hilton Chain <hako@ultrarare.space>
Cc: 65034@debbugs.gnu.org
Subject: [bug#65034] [PATCH v2 3/3] gnu: go-github-com-golang-protobuf-proto: Rename to go-github-com-golang-protobuf.
Date: Sun, 21 Jan 2024 18:00:43 -0500 [thread overview]
Message-ID: <87ttn670mc.fsf@gmail.com> (raw)
In-Reply-To: <fb3bff6d7f0e9f689ace38481d9b112304a7b24c.1695521520.git.hako@ultrarare.space> (Hilton Chain's message of "Sun, 24 Sep 2023 10:39:57 +0800")
Hi Hilton,
Hilton Chain <hako@ultrarare.space> writes:
> * gnu/packages/golang.scm (go-github-com-golang-protobuf-proto): Rename to...
> (go-github-com-golang-protobuf): ... this.
> [arguments]<#:import-path>: Set to "github.com/golang/protobuf".
> <#:unpack-path>: Remove argument.
> <#:phases>: Build all Go packages and run tests for them.
> (go-github-com-lucas-clemente-quic-go,go-github-com-prometheus-common)
> (go-github-com-prometheus-client-golang,go-github-com-onsi-gomega)
> [propagated-inputs]: Adjust accordingly.
> * gnu/packages/syncthing.scm (go-github-com-prometheus-client-model)
> (go-github-com-matttproud-golang-protobuf-extensions-pbutil)
> [propagated-inputs]: Likewise.
I wanted to apply this to core-updates but I think I had merge
conflicts. Could you check if it still applies cleanly, else upload a
v3?
--
Thanks,
Maxim
next prev parent reply other threads:[~2024-01-21 23:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 8:46 [bug#65034] [PATCH 0/3] gnu: go-google-golang-org-protobuf: Update to 1.31.0 Hilton Chain via Guix-patches via
2023-08-03 8:47 ` [bug#65034] [PATCH 1/3] " Hilton Chain via Guix-patches via
2023-09-05 13:49 ` [bug#65034] [PATCH 0/3] " Maxim Cournoyer
2023-09-23 13:43 ` Hilton Chain via Guix-patches via
2023-08-03 8:47 ` [bug#65034] [PATCH 2/3] gnu: go-github-com-golang-protobuf-proto: Update to 1.5.3 Hilton Chain via Guix-patches via
2023-08-03 8:47 ` [bug#65034] [PATCH 3/3] gnu: go-github-com-golang-protobuf-proto: Rename to go-github-com-golang-protobuf Hilton Chain via Guix-patches via
2023-09-24 2:39 ` [bug#65034] [PATCH v2 0/3] gnu: go-google-golang-org-protobuf: Update to 1.31.0 Hilton Chain via Guix-patches via
2023-09-24 2:39 ` [bug#65034] [PATCH v2 1/3] " Hilton Chain via Guix-patches via
2023-09-24 2:39 ` [bug#65034] [PATCH v2 2/3] gnu: go-github-com-golang-protobuf-proto: Update to 1.5.3 Hilton Chain via Guix-patches via
2023-09-24 2:39 ` [bug#65034] [PATCH v2 3/3] gnu: go-github-com-golang-protobuf-proto: Rename to go-github-com-golang-protobuf Hilton Chain via Guix-patches via
2024-01-21 23:00 ` Maxim Cournoyer [this message]
2024-01-25 17:10 ` Hilton Chain via Guix-patches via
2024-01-25 17:12 ` [bug#65034] [PATCH v3 core-updates 0/3] gnu: go-google-golang-org-protobuf: Update to 1.31.0 Hilton Chain via Guix-patches via
2024-01-25 17:13 ` [bug#65034] [PATCH v3 core-updates 1/3] " Hilton Chain via Guix-patches via
2024-01-25 17:13 ` [bug#65034] [PATCH v3 core-updates 2/3] gnu: go-github-com-golang-protobuf-proto: Update to 1.5.3 Hilton Chain via Guix-patches via
2024-01-25 17:13 ` [bug#65034] [PATCH v3 core-updates 3/3] gnu: go-github-com-golang-protobuf-proto: Rename to go-github-com-golang-protobuf Hilton Chain via Guix-patches via
2024-06-20 11:57 ` bug#65034: [PATCH 0/3] gnu: go-google-golang-org-protobuf: Update to 1.31.0 Sharlatan Hellseher
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=87ttn670mc.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=65034@debbugs.gnu.org \
--cc=hako@ultrarare.space \
/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).