From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] libproxy: update to 0.4.18
Date: Mon, 22 Aug 2022 00:15:46 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38818@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3170 bytes --]
There is a new 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: 1286 bytes --]
From 98cab77e1332da272960201781f63042cf8804d8 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 | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/libproxy/template b/srcpkgs/libproxy/template
index d6103007032e..59f12ba774da 100644
--- a/srcpkgs/libproxy/template
+++ b/srcpkgs/libproxy/template
@@ -1,6 +1,6 @@
# 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
@@ -11,8 +11,8 @@ short_desc="A library handling all the details of proxy configuration"
maintainer="Orphaned <orphan@voidlinux.org>"
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/archive/${version}.tar.gz"
+checksum=0b4a9218d88f6cf9fa25996a3f38329a11f688a9d026141d9d0e966d8fa63837
libproxy-devel_package() {
depends="libproxy>=${version}_${revision}"
next reply other threads:[~2022-08-21 22:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 22:15 oreo639 [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38818@inbox.vuxu.org \
--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).