Github messages for voidlinux
 help / color / mirror / Atom feed
From: lemmi <lemmi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fs-repo-migrations: update to 2.0.2.
Date: Fri, 01 Jul 2022 07:01:37 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37775@inbox.vuxu.org> (raw)

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

There is a new pull request by lemmi against master on the void-packages repository

https://github.com/lemmi/void-packages fs-repo-migrations
https://github.com/void-linux/void-packages/pull/37775

fs-repo-migrations: update to 2.0.2.
This got unnecessarily hard to package. But using the auto download just takes ages. The latest release is missing the 11 to 12 migration. So the version number isn't quite correct.
Anyway, I thought I make it available in case someone needs this to try #37561.
#### Testing the changes
- I tested the changes in this PR: **briefly**



A patch file from https://github.com/void-linux/void-packages/pull/37775.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fs-repo-migrations-37775.patch --]
[-- Type: text/x-diff, Size: 1724 bytes --]

From 0794fc3480ba25314eb93968fbb1c6b757da147a Mon Sep 17 00:00:00 2001
From: lemmi <lemmi@nerd2nerd.org>
Date: Thu, 30 Jun 2022 14:38:55 +0200
Subject: [PATCH] fs-repo-migrations: update to 2.0.2.

---
 srcpkgs/fs-repo-migrations/template | 17 ++++++++++++++---
 1 file changed, 14 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/fs-repo-migrations/template b/srcpkgs/fs-repo-migrations/template
index 3c7016b47218..62b69b07bb76 100644
--- a/srcpkgs/fs-repo-migrations/template
+++ b/srcpkgs/fs-repo-migrations/template
@@ -1,19 +1,30 @@
 # Template file for 'fs-repo-migrations'
 pkgname=fs-repo-migrations
-version=1.7.1
+version=2.0.2
 revision=1
+wrksrc=fs-repo-migrations-fs-repo-11-to-12-v1.0.2
 build_style=go
 go_import_path="github.com/ipfs/fs-repo-migrations"
 short_desc="Tool to upgrade the IPFS filesystem repository"
 maintainer="Christopher Brannon <chris@the-brannons.com>"
 license="MIT"
 homepage="https://github.com/ipfs/fs-repo-migrations"
-distfiles="https://${go_import_path}/archive/v${version}.tar.gz"
-checksum=6fbd68a6ae5eabcebdd0dc81e909a069facb112c4fe0421f159ab58112a041c2
+distfiles="https://github.com/ipfs/fs-repo-migrations/archive/refs/tags/fs-repo-11-to-12/v1.0.2.tar.gz"
+checksum=e6d6320e280f3118873dfb194b68681fa2747b7893d99831fa6fa2bbb67ebd71
 
 # fix: collect2: fatal error: cannot find 'ld'
 export LDFLAGS="-fuse-ld=bfd"
 
+do_build() {
+	for migration in fs-repo-*-to-*; do
+		(
+			cd $migration
+			go install -p "$XBPS_MAKEJOBS" -mod="vendor" -x -tags "${go_build_tags}" -ldflags "${go_ldflags}"
+		)
+	done
+	cd fs-repo-migrations
+	go install -p "$XBPS_MAKEJOBS" -x -tags "${go_build_tags}" -ldflags "${go_ldflags}"
+}
 post_install() {
 	vlicense LICENSE
 	vdoc README.md

             reply	other threads:[~2022-07-01  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-01  5:01 lemmi [this message]
2022-09-22 13:11 ` CMB
2022-09-22 15:54 ` CMB
2022-12-22  1:57 ` github-actions
2023-01-05  1:59 ` [PR PATCH] [Closed]: " github-actions

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37775@inbox.vuxu.org \
    --to=lemmi@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).