From: daniel-eys <daniel-eys@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] i2pd: update to 2.38.0.
Date: Sat, 10 Jul 2021 17:36:16 +0200 [thread overview]
Message-ID: <20210710153616.gg0oqzS9Efr5tCATF0adytKMzjZdjIYmlH_liUeEylQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31892@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1779 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/31892
i2pd: update to 2.38.0.
<!-- Mark items with [x] where applicable -->
From upstream's 2.35.0 releasenote:
>cmake and make flag with AVX switch (USE_AVX in make and -DUSE_AVX=1 in cmake) was deprecated due to changes in code.
so I removed this flag.
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] 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/31892.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-i2pd-31892.patch --]
[-- Type: text/x-diff, Size: 1350 bytes --]
From 6508db12050c9a6428a8bc35ae806ada4ec2d549 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Daniel=20Ey=C3=9Fer?= <daniel.eysser@gmail.com>
Date: Sat, 10 Jul 2021 17:03:44 +0200
Subject: [PATCH] i2pd: update to 2.38.0.
---
srcpkgs/i2pd/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/i2pd/template b/srcpkgs/i2pd/template
index d0cd1b6e116e..f57d08daa829 100644
--- a/srcpkgs/i2pd/template
+++ b/srcpkgs/i2pd/template
@@ -1,7 +1,7 @@
# Template file for 'i2pd'
pkgname=i2pd
-version=2.37.0
-revision=2
+version=2.38.0
+revision=1
build_style=gnu-makefile
make_build_args="USE_UPNP=yes"
makedepends="zlib-devel boost-devel openssl-devel miniupnpc-devel
@@ -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=072e79e55d4feac9dc3c988000a21ba613eb0c5bc151105cbccebdf84176dced
+checksum=8452f5323795a1846d554096c08fffe5ac35897867b93a5079605df8f80a3089
disable_parallel_build=yes
conf_files="
@@ -24,7 +24,7 @@ make_dirs="/var/lib/i2pd 0700 _i2pd _i2pd"
case "${XBPS_TARGET_MACHINE}" in
x86_64*) ;;
- *) make_build_args+=" USE_AESNI=no USE_AVX=no" ;;
+ *) make_build_args+=" USE_AESNI=no" ;;
esac
pre_install() {
next prev parent reply other threads:[~2021-07-10 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-10 15:31 [PR PATCH] " daniel-eys
2021-07-10 15:36 ` daniel-eys [this message]
2021-07-12 5:54 ` [PR PATCH] [Merged]: " ericonr
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=20210710153616.gg0oqzS9Efr5tCATF0adytKMzjZdjIYmlH_liUeEylQ@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).