From: Greg Hogan <code@greghogan.com>
To: 54957@debbugs.gnu.org
Subject: [bug#54957] [PATCH core-updates] gnu: boost: Update to 1.79.0.
Date: Fri, 15 Apr 2022 11:12:28 -0400 [thread overview]
Message-ID: <CA+3U0ZnJoV3UT7kMTfFZg-Z94G5uBqSzwEWgYSbkaUCU3BWdzw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1905 bytes --]
From 62b23ed9dfa8ff5d85bc900c406d3ab2c9645c68 Mon Sep 17 00:00:00 2001
From: Greg Hogan <code@greghogan.com>
Date: Thu, 14 Apr 2022 17:54:57 +0000
Subject: [PATCH core-updates] gnu: boost: Update to 1.79.0.
* gnu/packages/boost.scm (boost): Update to 1.79.0.
[source](patches): Add new and remove old upstream patches.
---
gnu/packages/boost.scm | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/gnu/packages/boost.scm b/gnu/packages/boost.scm
index 2373dd9feb..ec9228f55d 100644
--- a/gnu/packages/boost.scm
+++ b/gnu/packages/boost.scm
@@ -67,7 +67,7 @@ (define (boost-patch name version hash)
(define-public boost
(package
(name "boost")
- (version "1.78.0")
+ (version "1.79.0")
(source (origin
(method url-fetch)
(uri (string-append "
https://boostorg.jfrog.io/artifactory/main/release/"
@@ -75,13 +75,13 @@ (define-public boost
(version-with-underscores version)
".tar.bz2"))
(patches
(list (boost-patch
- ;; 1.78.0 was released with a faulty installation
routine:
- ;; <https://github.com/bfgroup/b2/pull/113>.
- "0001-b2-fix-install.patch" version
-
"02ljm22a4gcaj10xng8ww8aifrrlzm1pgyp08c06fd75f9pbkrbi")))
+ ;; 1.79.0 was released with a segmentation fault:
+ ;; <https://github.com/boostorg/json/issues/692>.
+ "0001-json-array-erase-relocate.patch" version
+
"1b0izwj8w92imr8ydzrh522syncprpf82n3kcy6apxn6p54b7p0f")))
(sha256
(base32
- "1k5w6l3xsa9vipwk14sjb1vhsj88xwz7jr964996rcmxsisz30c6"))))
+ "0fggarccddj6q4ifj3kn7g565rbhn4ia1vd45fxb7y57a6fmhpa7"))))
(build-system gnu-build-system)
(inputs (list icu4c zlib))
(native-inputs
--
2.35.1
[-- Attachment #1.2: Type: text/html, Size: 2641 bytes --]
[-- Attachment #2: 0001-gnu-boost-Update-to-1.79.0.patch --]
[-- Type: text/x-patch, Size: 1945 bytes --]
From 62b23ed9dfa8ff5d85bc900c406d3ab2c9645c68 Mon Sep 17 00:00:00 2001
From: Greg Hogan <code@greghogan.com>
Date: Thu, 14 Apr 2022 17:54:57 +0000
Subject: [PATCH core-updates] gnu: boost: Update to 1.79.0.
* gnu/packages/boost.scm (boost): Update to 1.79.0.
[source](patches): Add new and remove old upstream patches.
---
gnu/packages/boost.scm | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/gnu/packages/boost.scm b/gnu/packages/boost.scm
index 2373dd9feb..ec9228f55d 100644
--- a/gnu/packages/boost.scm
+++ b/gnu/packages/boost.scm
@@ -67,7 +67,7 @@ (define (boost-patch name version hash)
(define-public boost
(package
(name "boost")
- (version "1.78.0")
+ (version "1.79.0")
(source (origin
(method url-fetch)
(uri (string-append "https://boostorg.jfrog.io/artifactory/main/release/"
@@ -75,13 +75,13 @@ (define-public boost
(version-with-underscores version) ".tar.bz2"))
(patches
(list (boost-patch
- ;; 1.78.0 was released with a faulty installation routine:
- ;; <https://github.com/bfgroup/b2/pull/113>.
- "0001-b2-fix-install.patch" version
- "02ljm22a4gcaj10xng8ww8aifrrlzm1pgyp08c06fd75f9pbkrbi")))
+ ;; 1.79.0 was released with a segmentation fault:
+ ;; <https://github.com/boostorg/json/issues/692>.
+ "0001-json-array-erase-relocate.patch" version
+ "1b0izwj8w92imr8ydzrh522syncprpf82n3kcy6apxn6p54b7p0f")))
(sha256
(base32
- "1k5w6l3xsa9vipwk14sjb1vhsj88xwz7jr964996rcmxsisz30c6"))))
+ "0fggarccddj6q4ifj3kn7g565rbhn4ia1vd45fxb7y57a6fmhpa7"))))
(build-system gnu-build-system)
(inputs (list icu4c zlib))
(native-inputs
--
2.35.1
next reply other threads:[~2022-04-15 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 15:12 Greg Hogan [this message]
2022-05-08 9:32 ` bug#54957: [PATCH core-updates] gnu: boost: Update to 1.79.0 Ludovic Courtès
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=CA+3U0ZnJoV3UT7kMTfFZg-Z94G5uBqSzwEWgYSbkaUCU3BWdzw@mail.gmail.com \
--to=code@greghogan.com \
--cc=54957@debbugs.gnu.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.
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).