Github messages for voidlinux
 help / color / mirror / Atom feed
From: Daxot <Daxot@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] i2pd: update to 2.49.0
Date: Mon, 02 Oct 2023 00:01:31 +0200	[thread overview]
Message-ID: <20231001220131.wnhsbfQ2Dvvc1lDhyMFbKwSl0PcB_fi2zLFqSYG7v7k@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46361@inbox.vuxu.org>

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

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

https://github.com/Daxot/void-packages update-i2pd
https://github.com/void-linux/void-packages/pull/46361

i2pd: update to 2.49.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 [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, **x86_64**



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

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

From 9dca5fd032f72f7e6b3823fa6b0cb850b4479e30 Mon Sep 17 00:00:00 2001
From: Daxot <37917854+Daxot@users.noreply.github.com>
Date: Mon, 2 Oct 2023 00:29:23 +0300
Subject: [PATCH] i2pd: update to 2.49.0

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

diff --git a/srcpkgs/i2pd/template b/srcpkgs/i2pd/template
index 9e75bb66ee8ff..94eba66568929 100644
--- a/srcpkgs/i2pd/template
+++ b/srcpkgs/i2pd/template
@@ -1,7 +1,7 @@
 # Template file for 'i2pd'
 pkgname=i2pd
-version=2.48.0
-revision=2
+version=2.49.0
+revision=1
 build_style=gnu-makefile
 make_build_args="USE_UPNP=yes"
 makedepends="zlib-devel boost-devel openssl-devel miniupnpc-devel"
@@ -11,7 +11,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=ccf417aa66ce37f72ea15b7fbcff4c71e823566ea74bda696b9c1e19aae08739
+checksum=d8e07f78cc9f1ba65e8460db27c649dd0cfdd3ba334725f8d6f9ee815cb40e68
 
 conf_files="
  /etc/i2pd/i2pd.conf

  reply	other threads:[~2023-10-01 22:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01 21:33 [PR PATCH] " Daxot
2023-10-01 22:01 ` Daxot [this message]
2023-10-01 22:03 ` [PR PATCH] [Updated] " Daxot
2023-10-01 22:06 ` Daxot
2023-12-24 21:00 ` Daxot
2023-12-24 21:04 ` Daxot
2023-12-30  9:12 ` [PR PATCH] [Updated] i2pd: update to 2.50.1 Daxot
2024-01-10 20:30 ` Daxot
2024-01-15  9:31 ` [PR PATCH] [Updated] i2pd: update to 2.50.2 Daxot
2024-01-16 15:40 ` [PR PATCH] [Merged]: " sgn

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=20231001220131.wnhsbfQ2Dvvc1lDhyMFbKwSl0PcB_fi2zLFqSYG7v7k@z \
    --to=daxot@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).