Github messages for voidlinux
 help / color / mirror / Atom feed
From: sug0 <sug0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] go-ipfs: update to 0.11.0
Date: Thu, 10 Feb 2022 23:25:32 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35519@inbox.vuxu.org> (raw)

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

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

https://github.com/sug0/void-packages ipfs
https://github.com/void-linux/void-packages/pull/35519

go-ipfs: update to 0.11.0
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - armv7l-musl


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-ipfs-35519.patch --]
[-- Type: text/x-diff, Size: 1107 bytes --]

From 5e9ec0328084287c199723fb4ae366d1339b2101 Mon Sep 17 00:00:00 2001
From: Tiago Carvalho <sugoiuguu@tfwno.gf>
Date: Thu, 10 Feb 2022 22:24:04 +0000
Subject: [PATCH] go-ipfs: update to 0.11.0

---
 srcpkgs/go-ipfs/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/go-ipfs/template b/srcpkgs/go-ipfs/template
index a38fb43b84b7..b653c5a49df6 100644
--- a/srcpkgs/go-ipfs/template
+++ b/srcpkgs/go-ipfs/template
@@ -1,7 +1,7 @@
 # Template file for 'go-ipfs'
 pkgname=go-ipfs
-version=0.10.0
-revision=2
+version=0.11.0
+revision=1
 build_style=go
 go_import_path="github.com/ipfs/go-ipfs"
 go_package="${go_import_path}/cmd/ipfs"
@@ -13,7 +13,7 @@ license="MIT, Apache-2.0"
 homepage="https://ipfs.io"
 changelog="https://github.com/ipfs/go-ipfs/blob/master/CHANGELOG.md"
 distfiles="https://github.com/ipfs/go-ipfs/archive/v${version}.tar.gz"
-checksum=d145f13eb98b61eefc9b30ace35246215876ba1adf79bf74e9ddd43a54671803
+checksum=e1558182bb6d67caa3e4e58dd73092e2eaf00611aedb9202f265479205e5edcb
 
 system_accounts="_ipfs"
 make_dirs="/var/lib/ipfs 0700 _ipfs _ipfs"

             reply	other threads:[~2022-02-10 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 22:25 sug0 [this message]
2022-02-12 15:54 ` [PR PATCH] [Merged]: " paper42

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-35519@inbox.vuxu.org \
    --to=sug0@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).