Github messages for voidlinux
 help / color / mirror / Atom feed
From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] arti: update to 1.1.12.
Date: Sun, 10 Mar 2024 02:10:20 +0100	[thread overview]
Message-ID: <20240310011020.322F325E7C@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47611@inbox.vuxu.org>

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

There is an updated pull request by daniel-eys against master on the void-packages repository

https://github.com/daniel-eys/void-packages arti
https://github.com/void-linux/void-packages/pull/47611

arti: update to 1.1.12.
<!-- 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 [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
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, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl
-->


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

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

From 0c0c7642084636ea134facf568461019a3b41e58 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ey=C3=9Fer?= <daniel.eysser@gmail.com>
Date: Tue, 5 Dec 2023 21:28:00 +0100
Subject: [PATCH] arti: update to 1.2.0.

---
 srcpkgs/arti/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/arti/template b/srcpkgs/arti/template
index f21951f2b2dcc1..3b2b01559f3e7b 100644
--- a/srcpkgs/arti/template
+++ b/srcpkgs/arti/template
@@ -1,6 +1,6 @@
 # Template file for 'arti'
 pkgname=arti
-version=1.1.10
+version=1.2.0
 revision=1
 archs="x86_64* i686* aarch64* arm*" # ring
 build_style=cargo
@@ -13,7 +13,7 @@ license="Apache-2.0, MIT"
 homepage="https://gitlab.torproject.org/tpo/core/arti"
 changelog="https://gitlab.torproject.org/tpo/core/arti/-/raw/main/CHANGELOG.md"
 distfiles="https://gitlab.torproject.org/tpo/core/arti/-/archive/arti-v${version}/arti-arti-v${version}.tar.gz"
-checksum=bb7f18385022b616fb0fb04c61b890441524eaa884def1eef3c581b711814842
+checksum=5303da0d272e7be3bcddd482fc61a57f66afb9ced0e653af9d56454808e6a348
 
 if [ "$XBPS_CHECK_PKGS" ]; then
 	case "$XBPS_TARGET_MACHINE" in

      parent reply	other threads:[~2024-03-10  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05 23:42 [PR PATCH] arti: update to 1.1.11 daniel-eys
2023-12-16 11:37 ` [PR PATCH] [Updated] " daniel-eys
2024-01-10  0:02 ` daniel-eys
2024-03-10  1:10 ` daniel-eys [this message]

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=20240310011020.322F325E7C@inbox.vuxu.org \
    --to=daniel-eys@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).