From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Greg Hogan <code@greghogan.com>
Cc: 62410-done@debbugs.gnu.org
Subject: bug#62410: [staging PATCH] gnu: subversion: Update to 1.14.2 [security fixes].
Date: Fri, 24 Mar 2023 00:20:23 -0400 [thread overview]
Message-ID: <87v8iq2320.fsf@gmail.com> (raw)
In-Reply-To: <20230323184631.1171191-1-code@greghogan.com> (Greg Hogan's message of "Thu, 23 Mar 2023 18:46:31 +0000")
Hi Greg,
Greg Hogan <code@greghogan.com> writes:
> This release contains fixes for CVE-2021-28544 and CVE-2022-24070.
>
> * gnu/packages/version-control.scm (subversion): Update to 1.14.2.
> ---
> gnu/packages/version-control.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/version-control.scm b/gnu/packages/version-control.scm
> index 12e21336ce..526b6bbb2b 100644
> --- a/gnu/packages/version-control.scm
> +++ b/gnu/packages/version-control.scm
> @@ -1995,14 +1995,14 @@ (define-public neon
> (define-public subversion
> (package
> (name "subversion")
> - (version "1.14.1")
> + (version "1.14.2")
> (source (origin
> (method url-fetch)
> (uri (string-append "mirror://apache/subversion/"
> "subversion-" version ".tar.bz2"))
> (sha256
> (base32
> - "1ag1hvcm9q92kgalzbbgcsq9clxnzmbj9nciz9lmabjx4lyajp9c"))))
> + "0a6csc84hfymm8b5cnvq1n1p3rjjf33qy0z7y1k8lwkm1f6hw4y9"))))
> (build-system gnu-build-system)
> (arguments
> '(#:parallel-tests? #f ; TODO Seems to cause test failures on
I decided to push this to master, as the dependent packages count was
rather low. I hope I wasn't misguided :-).
--
Thanks,
Maxim
prev parent reply other threads:[~2023-03-24 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 18:46 [bug#62410] [staging PATCH] gnu: subversion: Update to 1.14.2 [security fixes] Greg Hogan
2023-03-24 4:20 ` Maxim Cournoyer [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v8iq2320.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=62410-done@debbugs.gnu.org \
--cc=code@greghogan.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).