Github messages for voidlinux
 help / color / mirror / Atom feed
From: ologantr <ologantr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] apache: update to 2.4.53.
Date: Sat, 30 Apr 2022 10:43:41 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36919@inbox.vuxu.org> (raw)

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

There is a new pull request by ologantr against master on the void-packages repository

https://github.com/ologantr/void-packages apache-update
https://github.com/void-linux/void-packages/pull/36919

apache: update to 2.4.53.
Fixes CVE-2022-23943, CVE-2022-22721, CVE-2022-22720,
CVE-2022-22719.

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

#### Local build testing
- I built this PR locally for my native architecture (x86_64-glibc)

A patch file from https://github.com/void-linux/void-packages/pull/36919.patch is attached

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

From 2b364ec61ea3a36f030d0e9a7f5cdd97f7e9f5bc Mon Sep 17 00:00:00 2001
From: ologantr <mrphyber@protonmail.com>
Date: Sat, 30 Apr 2022 10:38:10 +0200
Subject: [PATCH] apache: update to 2.4.53.

Fixes CVE-2022-23943, CVE-2022-22721, CVE-2022-22720,
CVE-2022-22719.
---
 srcpkgs/apache/template | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/apache/template b/srcpkgs/apache/template
index 2cdb6ca2f449..4cdb90a6ab04 100644
--- a/srcpkgs/apache/template
+++ b/srcpkgs/apache/template
@@ -1,6 +1,6 @@
 # Template file for 'apache'
 pkgname=apache
-version=2.4.52
+version=2.4.53
 revision=1
 wrksrc="httpd-${version}"
 build_style=gnu-configure
@@ -36,7 +36,7 @@ license="Apache-2.0"
 homepage="http://httpd.apache.org/"
 changelog="http://www.apache.org/dist/httpd/CHANGES_2.4"
 distfiles="https://dlcdn.apache.org/httpd/httpd-${version}.tar.bz2"
-checksum=0127f7dc497e9983e9c51474bed75e45607f2f870a7675a86dc90af6d572f5c9
+checksum=d0bbd1121a57b5f2a6ff92d7b96f8050c5a45d3f14db118f64979d525858db63
 
 system_accounts="_apache"
 _apache_homedir="/srv/www/$pkgname"

             reply	other threads:[~2022-04-30  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-30  8:43 ologantr [this message]
2022-04-30 12:21 ` [PR PATCH] [Updated] " ologantr
2022-04-30 18:28 ` [PR REVIEW] " paper42
2022-04-30 19:15 ` ologantr
2022-05-01  8:49 ` paper42
2022-05-01  9:03 ` paper42
2022-05-01  9:28 ` [PR PATCH] [Updated] " ologantr
2022-05-01  9:57 ` [PR PATCH] [Merged]: " paper42

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-36919@inbox.vuxu.org \
    --to=ologantr@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).