From: jpastuszek <jpastuszek@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] etcd: fixed go_import_path
Date: Thu, 20 Apr 2023 17:33:38 +0200 [thread overview]
Message-ID: <20230420153338.ojqUl1KhyumJevRJin_7b5z-F7i7ddSbWGsyCSaoq2g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43543@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
There is an updated pull request by jpastuszek against master on the void-packages repository
https://github.com/jpastuszek/void-packages etcd
https://github.com/void-linux/void-packages/pull/43543
etcd: fixed go_import_path
#### Testing the changes
- I tested the changes in this PR: YES
#### Local build testing
- I built this PR locally for my native architecture, x86_64
The original package contains no binaries:
```
$ xls etcd
/etc/sv/etcd/conf
/etc/sv/etcd/log/run
/etc/sv/etcd/run
/etc/sv/etcd/log/supervise -> /run/runit/supervise.etcd-log
/etc/sv/etcd/supervise -> /run/runit/supervise.etcd
```
Looks like the name of the Go import path was changed.
With this fix:
```
$ xls etcd
/etc/sv/etcd/conf
/etc/sv/etcd/log/run
/etc/sv/etcd/run
/usr/bin/etcd
/usr/bin/etcdctl
/etc/sv/etcd/log/supervise -> /run/runit/supervise.etcd-log
/etc/sv/etcd/supervise -> /run/runit/supervise.etcd
```
I set it up and it is running; I can put and get a value form it.
A patch file from https://github.com/void-linux/void-packages/pull/43543.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-etcd-43543.patch --]
[-- Type: text/x-diff, Size: 1155 bytes --]
From a2d461e32e140bf676f23b467a0bb929d06f5a61 Mon Sep 17 00:00:00 2001
From: Jakub Pastuszek <jpastuszek@protonmail.com>
Date: Thu, 20 Apr 2023 16:13:33 +0100
Subject: [PATCH] etcd: fixed go_import_path
---
srcpkgs/etcd/template | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/etcd/template b/srcpkgs/etcd/template
index e3ee7f15ec8a..ce54b3e43cfb 100644
--- a/srcpkgs/etcd/template
+++ b/srcpkgs/etcd/template
@@ -1,16 +1,15 @@
# Template file for 'etcd'
pkgname=etcd
version=3.4.24
-revision=2
+revision=3
build_style=go
-go_import_path="github.com/etcd-io/etcd"
+go_import_path="go.etcd.io/etcd"
go_package="${go_import_path} ${go_import_path}/etcdctl"
-go_mod_mode=off
short_desc="Distributed reliable key-value store"
maintainer="Andrea Brancaleoni <abc@pompel.me>"
license="Apache-2.0"
homepage="https://coreos.com/etcd/docs/latest/"
-distfiles="https://${go_import_path}/archive/v${version}.tar.gz"
+distfiles="https://github.com/etcd-io/etcd/archive/v${version}.tar.gz"
checksum=cc490495ffc04ced61a7f549dffd4f9a2e62723245c66432394659361d6ab659
conf_files="/etc/sv/etcd/conf"
system_accounts="etcd"
next prev parent reply other threads:[~2023-04-20 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 15:19 [PR PATCH] " jpastuszek
2023-04-20 15:32 ` [PR PATCH] [Updated] " jpastuszek
2023-04-20 15:33 ` jpastuszek [this message]
2023-04-22 22:19 ` [PR PATCH] [Merged]: " classabbyamp
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=20230420153338.ojqUl1KhyumJevRJin_7b5z-F7i7ddSbWGsyCSaoq2g@z \
--to=jpastuszek@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).