From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] i2pd: update to 2.46.1.
Date: Tue, 21 Feb 2023 22:09:05 +0100 [thread overview]
Message-ID: <20230221210905.Yh8_17-WXizcsN5wAFlKtjY9ItA8NGnN_M3smAd781M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42385@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 i2pd
https://github.com/void-linux/void-packages/pull/42385
i2pd: update to 2.46.1.
<!-- 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/42385.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-i2pd-42385.patch --]
[-- Type: text/x-diff, Size: 1032 bytes --]
From b1a972f876b44c946699c7a5f2888204034d0e03 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ey=C3=9Fer?= <daniel.eysser@gmail.com>
Date: Mon, 20 Feb 2023 22:53:33 +0100
Subject: [PATCH] i2pd: update to 2.46.1.
---
srcpkgs/i2pd/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/i2pd/template b/srcpkgs/i2pd/template
index 91e085f41aca..baf177a68e1e 100644
--- a/srcpkgs/i2pd/template
+++ b/srcpkgs/i2pd/template
@@ -1,6 +1,6 @@
# Template file for 'i2pd'
pkgname=i2pd
-version=2.46.0
+version=2.46.1
revision=1
build_style=gnu-makefile
make_build_args="USE_UPNP=yes"
@@ -12,7 +12,7 @@ license="BSD-3-Clause"
homepage="https://i2pd.website/"
changelog="https://raw.githubusercontent.com/PurpleI2P/i2pd/openssl/ChangeLog"
distfiles="https://github.com/PurpleI2P/i2pd/archive/${version}.tar.gz"
-checksum=daa5e47bb2b80fbdaa3836b209e869017893421f5225dfe019e5d43d3f8a86d4
+checksum=83bb5e2494d566d41ff3a85e4c93078d290d10e3cf1fbe7807bec9f0d024513e
conf_files="
/etc/i2pd/i2pd.conf
next prev parent reply other threads:[~2023-02-21 21:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 21:05 [PR PATCH] " daniel-eys
2023-02-21 21:09 ` daniel-eys [this message]
2023-02-21 21:12 ` daniel-eys
2023-03-26 17:01 ` [PR PATCH] [Updated] " daniel-eys
2023-05-12 12:25 ` [PR PATCH] [Updated] i2pd: update to 2.47.0 daniel-eys
2023-05-12 12:26 ` daniel-eys
2023-06-12 15:21 ` [PR PATCH] [Updated] " daniel-eys
2023-06-27 11:24 ` [PR PATCH] [Closed]: i2pd: update to 2.48.0 Duncaen
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=20230221210905.Yh8_17-WXizcsN5wAFlKtjY9ItA8NGnN_M3smAd781M@z \
--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).