From: dkwo <dkwo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] squid: update to 5.7
Date: Fri, 03 Feb 2023 16:49:35 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42054@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
There is a new pull request by dkwo against master on the void-packages repository
https://github.com/dkwo/void-packages O3sq
https://github.com/void-linux/void-packages/pull/42054
squid: update to 5.7
- I tested the changes in this PR: no
- I built this PR locally for my native architecture, (x86_64-musl)
seems to build fine with openssl 3 #openssl3
A patch file from https://github.com/void-linux/void-packages/pull/42054.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-O3sq-42054.patch --]
[-- Type: text/x-diff, Size: 1048 bytes --]
From c60808964c041625d11835f6c15b8da85dc9518f Mon Sep 17 00:00:00 2001
From: dkwo <nicolopiazzalunga@gmail.com>
Date: Fri, 3 Feb 2023 10:47:26 -0500
Subject: [PATCH] squid: update to 5.7
---
srcpkgs/squid/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/squid/template b/srcpkgs/squid/template
index 626972525bc0..3306180dbec7 100644
--- a/srcpkgs/squid/template
+++ b/srcpkgs/squid/template
@@ -1,6 +1,6 @@
# Template file for 'squid'
pkgname=squid
-version=5.3
+version=5.7
revision=1
build_style=gnu-configure
configure_args="
@@ -65,7 +65,7 @@ license="GPL-2.0-or-later"
homepage="http://www.squid-cache.org/"
changelog="http://www.squid-cache.org/Versions/v5/changesets/"
distfiles="http://www.squid-cache.org/Versions/v5/squid-${version}.tar.xz"
-checksum=45178588df1311ded41ebadd632840c4d93a8d7f5f60e38e74acf2f1ae2f1715
+checksum=6b0753aaba4c9c4efd333e67124caecf7ad6cc2d38581f19d2f0321f5b7ecd81
system_accounts="squid"
# squid-conf-tests requires a squid user in the system
make_check=no
next reply other threads:[~2023-02-03 15:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 15:49 dkwo [this message]
2023-02-03 16:02 ` dkwo
2023-02-03 16:03 ` kruceter
2023-02-03 16:05 ` dkwo
2023-02-03 16:11 ` kruceter
2023-02-03 16:21 ` [PR PATCH] [Updated] " dkwo
2023-02-03 16:25 ` kruceter
2023-02-03 16:25 ` [PR PATCH] [Updated] " dkwo
2023-02-03 16:42 ` dkwo
2023-02-03 17:00 ` kruceter
2023-02-03 17:00 ` kruceter
2023-02-03 17:00 ` kruceter
2023-02-03 18:29 ` kruceter
2023-02-03 18:40 ` Vaelatern
2023-02-03 18:50 ` kruceter
2023-02-03 18:56 ` [PR PATCH] [Updated] " dkwo
2023-02-03 18:57 ` dkwo
2023-02-03 22:18 ` kruceter
2023-02-04 16:20 ` [PR PATCH] [Updated] " dkwo
2023-02-04 16:22 ` dkwo
2023-02-04 21:09 ` kruceter
2023-02-05 6:20 ` [PR PATCH] [Merged]: " Vaelatern
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-42054@inbox.vuxu.org \
--to=dkwo@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).