Github messages for voidlinux
 help / color / mirror / Atom feed
From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] libproxy: update to 0.4.18
Date: Mon, 22 Aug 2022 02:09:27 +0200	[thread overview]
Message-ID: <20220822000927.7ibYWfoGHGAsqs6NhV8JLqdbiNE1RR_eh3_5Yqn-uXs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38818@inbox.vuxu.org>

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

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

https://github.com/oreo639/void-packages libproxy
https://github.com/void-linux/void-packages/pull/38818

libproxy: update to 0.4.18
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**

Fixes build with gcc12:
```
In file included from /builddir/libproxy-0.4.15/libproxy/extension_config.hpp:24,
                 from /builddir/libproxy-0.4.15/libproxy/proxy.cpp:28:
/builddir/libproxy-0.4.15/libproxy/url.hpp:53:32: error: ISO C++17 does not allow dynamic exception specifications
   53 |         url(const string& url) throw (parse_error);
      |                                ^~~~~
/builddir/libproxy-0.4.15/libproxy/url.hpp:56:36: error: ISO C++17 does not allow dynamic exception specifications
   56 |         url& operator=(string url) throw (parse_error);
      |                                    ^~~~~
/builddir/libproxy-0.4.15/libproxy/extension_config.hpp:34:61: error: ISO C++17 does not allow dynamic exception specifications
   34 |         virtual vector<url>      get_config(const url &dst) throw (runtime_error)=0;
      |                                                             ^~~~~
In file included from /builddir/libproxy-0.4.15/libproxy/proxy.cpp:31:
/builddir/libproxy-0.4.15/libproxy/extension_pacrunner.hpp:44:44: error: ISO C++17 does not allow dynamic exception specifications
   44 |         virtual string run(const url& url) throw (bad_alloc)=0;
      |                                            ^~~~~
/builddir/libproxy-0.4.15/libproxy/extension_pacrunner.hpp:50:63: error: ISO C++17 does not allow dynamic exception specifications
   50 |         virtual pacrunner* get(string pac, const url& pacurl) throw (bad_alloc);
      |                                                               ^~~~~
/builddir/libproxy-0.4.15/libproxy/extension_pacrunner.hpp:58:66: error: ISO C++17 does not allow dynamic exception specifications
   58 |         virtual pacrunner* create(string pac, const url& pacurl) throw (bad_alloc)=0;
      |                                                                  ^~~~~
ninja: build stopped: subcommand failed.
```

<!--
#### 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/38818.patch is attached

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

From faf8ec1208f7775b79e70922bfbb74c672bae533 Mon Sep 17 00:00:00 2001
From: oreo639 <31916379+Oreo639@users.noreply.github.com>
Date: Sun, 21 Aug 2022 15:14:33 -0700
Subject: [PATCH] libproxy: update to 0.4.18

---
 srcpkgs/libproxy/template | 14 +++++++++-----
 1 file changed, 9 insertions(+), 5 deletions(-)

diff --git a/srcpkgs/libproxy/template b/srcpkgs/libproxy/template
index d6103007032e..3b516025354e 100644
--- a/srcpkgs/libproxy/template
+++ b/srcpkgs/libproxy/template
@@ -1,18 +1,22 @@
 # Template file for 'libproxy'
 pkgname=libproxy
-version=0.4.15
+version=0.4.18
 revision=1
 build_style=cmake
 configure_args="-DWITH_GNOME=0 -DWITH_KDE4=0 -DWITH_MOZJS=0 -DWITH_NM=0
  -DWITH_PERL=0 -DWITH_PYTHON=1 -DWITH_WEBKIT=0"
 hostmakedepends="pkg-config python"
 makedepends="zlib-devel"
-short_desc="A library handling all the details of proxy configuration"
+short_desc="Library handling all the details of proxy configuration"
 maintainer="Orphaned <orphan@voidlinux.org>"
+license="LGPL-2.1-or-later"
 homepage="http://github.com/libproxy/libproxy"
-license="LGPL-2.1"
-distfiles="https://github.com/libproxy/libproxy/archive/${version}.tar.gz>${pkgname}-${version}.tar.gz"
-checksum=18f58b0a0043b6881774187427ead158d310127fc46a1c668ad6d207fb28b4e0
+distfiles="https://github.com/libproxy/libproxy/releases/download/${version}/libproxy-${version}.tar.xz"
+checksum=69b5856e9ea42c38ac77e6b8c92ffc86a71d341fef74e77bef85f9cc6c47a4b1
+
+post_patch() {
+	vsed '/add_test(NAME url-test/d' -i libproxy/test/CMakeLists.txt
+}
 
 libproxy-devel_package() {
 	depends="libproxy>=${version}_${revision}"

  parent reply	other threads:[~2022-08-22  0:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-21 22:15 [PR PATCH] " oreo639
2022-08-21 22:18 ` [PR PATCH] [Updated] " oreo639
2022-08-21 22:27 ` oreo639
2022-08-22  0:08 ` oreo639
2022-08-22  0:09 ` oreo639 [this message]
2022-08-22  2:22 ` oreo639
2022-08-28 22:15 ` [PR PATCH] [Merged]: " 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=20220822000927.7ibYWfoGHGAsqs6NhV8JLqdbiNE1RR_eh3_5Yqn-uXs@z \
    --to=oreo639@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).