From: duckology <duckology@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] monero: update to 0.18.1.1.
Date: Thu, 22 Sep 2022 22:59:28 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39426@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
There is a new pull request by duckology against master on the void-packages repository
https://github.com/duckology/void-packages monero-update-0.18.1.1
https://github.com/void-linux/void-packages/pull/39426
monero: update to 0.18.1.1.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!-- 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):
- armv6l-musl
A patch file from https://github.com/void-linux/void-packages/pull/39426.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-monero-update-0.18.1.1-39426.patch --]
[-- Type: text/x-diff, Size: 2930 bytes --]
From 93183f600c804bf5f3321254a7e096be6181efd0 Mon Sep 17 00:00:00 2001
From: duckology <kallio.aino@proton.me>
Date: Thu, 22 Sep 2022 22:27:54 +0200
Subject: [PATCH] monero: update to 0.18.1.1.
---
srcpkgs/monero/patches/system-miniupnpc.patch | 9 +++++----
srcpkgs/monero/template | 6 +++---
2 files changed, 8 insertions(+), 7 deletions(-)
diff --git a/srcpkgs/monero/patches/system-miniupnpc.patch b/srcpkgs/monero/patches/system-miniupnpc.patch
index 3d9c8bb08bbc..b87045caab89 100644
--- a/srcpkgs/monero/patches/system-miniupnpc.patch
+++ b/srcpkgs/monero/patches/system-miniupnpc.patch
@@ -41,9 +41,9 @@ index 9b21705e..76340a22 100644
--
2.17.0
---- a/external/CMakeLists.txt 2018-10-10 13:13:55.759414180 +0200
-+++ b/external/CMakeLists.txt 2018-10-10 13:19:33.363411827 +0200
-@@ -34,22 +34,46 @@
+--- a/external/CMakeLists.txt 2022-08-17 17:56:16.277171566 +0100
++++ b/external/CMakeLists.txt 2022-08-17 18:12:39.342914327 +0100
+@@ -34,24 +34,46 @@
# We always compile if we are building statically to reduce static dependency issues...
# ...except for FreeBSD, because FreeBSD is a special case that doesn't play well with
# others.
@@ -54,8 +54,10 @@ index 9b21705e..76340a22 100644
-find_package(Miniupnpc REQUIRED)
-
-message(STATUS "Using in-tree miniupnpc")
+-set(UPNPC_NO_INSTALL TRUE CACHE BOOL "Disable miniupnp installation" FORCE)
-add_subdirectory(miniupnp/miniupnpc)
-set_property(TARGET libminiupnpc-static PROPERTY FOLDER "external")
+-set_property(TARGET libminiupnpc-static PROPERTY POSITION_INDEPENDENT_CODE ON)
-if(MSVC)
- set_property(TARGET libminiupnpc-static APPEND_STRING PROPERTY COMPILE_FLAGS " -wd4244 -wd4267")
-elseif(NOT MSVC)
@@ -99,4 +101,3 @@ index 9b21705e..76340a22 100644
+endif()
find_package(Unbound)
-
diff --git a/srcpkgs/monero/template b/srcpkgs/monero/template
index eebce3d0a551..67a82ce5e741 100644
--- a/srcpkgs/monero/template
+++ b/srcpkgs/monero/template
@@ -1,7 +1,7 @@
# Template file for 'monero'
pkgname=monero
-version=0.17.2.3
-revision=3
+version=0.18.1.1
+revision=1
_randomx_version="1.1.9"
# the revision monero uses as a submodule for the specific version
_rapidjson_gitrev="129d19ba7f496df5e33658527a7158c79b99c21c"
@@ -23,7 +23,7 @@ distfiles="https://github.com/monero-project/monero/archive/v${version}.tar.gz
https://github.com/tevador/RandomX/archive/v${_randomx_version}.tar.gz
https://github.com/Tencent/rapidjson/archive/${_rapidjson_gitrev}.tar.gz
https://github.com/monero-project/supercop/archive/${_supercop_gitrev}.tar.gz"
-checksum="e4462f8909bdc5e66d76f4023374ff759159c15fe7d407f0c21619769e87c35d
+checksum="6caa8fb6106fce3934f44d08d4fa13cf34ebc00cef994c306089cdf18dfb853f
b878fd6ea6d4e1dcdfa085427ce4666c1085e8c5a9e049c04ca2036b4aead0f5
44b007d419ac21b6affec58991e865ee572346ead19b73cf1c3e4e11c7a81273
b973b9d8269ec4d97c3c3443f0dad96d09f72b1b30e616e0947557adbdbb03f7"
next reply other threads:[~2022-09-22 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 20:59 duckology [this message]
2022-09-24 14:47 ` [PR PATCH] [Closed]: " ghost
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-39426@inbox.vuxu.org \
--to=duckology@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).