Github messages for voidlinux
 help / color / mirror / Atom feed
From: kruceter <kruceter@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: squid: update to 5.7
Date: Fri, 03 Feb 2023 23:18:19 +0100	[thread overview]
Message-ID: <20230203221819.cpReNuXA_Sg93fZqVk3LhDpb_GCaWArGNueWUdy27LI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42054@inbox.vuxu.org>

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

New comment by kruceter on void-packages repository

https://github.com/void-linux/void-packages/pull/42054#issuecomment-1416477134

Comment:
Would you mind to include this into the commit message? Thank you.

```markdown
* --sbindir is already defined in
  common/environment/configure/gnu-configure-args.sh

* --enable-useragent-log and --enable-referer-log are obsolete since
  version 3.2.0.4.

* --enable-arp-acl is gone
  (squid-cache/squid@41b91720118a5cf1d0eb47fdb903a841f46bb750).

* --enable-carp is gone, CARP is compiled in
  (squid-cache/squid@b2ea838f690d122679eeafda2ec30faadf1d5e82).

* --enable-truncate was removed upstream
  (squid-cache/squid@b3fb907032613d7151410eceb4622bb43f5af6bc).

* squid_cv_gnu_atomics is replaced with c++11 std::atomic
  (squid-cache/squid@ddd4edb743d82be97fc651d529e04bf55329a50d).

* squid_opt_enable_large_files is the duplicate of --with-large-files.
  Apparently Juan RP (aka xtraeme) used this option back in 2016 to fix
  cross build for arm* and glibc. Now that squid builds completely fine
  without it, it is safe to assume this option is not needed anymore.

* define BUILDCXX properly (CXX_host cannot be set outside of
  functions).

* CVE-2018-1000027 was fixed since version 4.0.23.
```

  parent reply	other threads:[~2023-02-03 22:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 15:49 [PR PATCH] " dkwo
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 [this message]
2023-02-04 16:20 ` 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=20230203221819.cpReNuXA_Sg93fZqVk3LhDpb_GCaWArGNueWUdy27LI@z \
    --to=kruceter@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).