From: Christopher Baines <mail@cbaines.net>
To: "Paul A. Patience" <paul@apatience.com>
Cc: 57685-done@debbugs.gnu.org
Subject: bug#57685: [PATCH v2 0/3] gnu: libharu: Update to 2.4.2.
Date: Sat, 17 Sep 2022 19:20:05 +0200 [thread overview]
Message-ID: <87y1uhrk7c.fsf@cbaines.net> (raw)
In-Reply-To: <20220912192510.420112-1-paul@apatience.com>
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
"Paul A. Patience" <paul@apatience.com> writes:
> The issue causing the saga build to fail was fixed in libHaru 2.4.2, so I
> updated it to that version.
> (I had tested the build of emboss, which also depends on libHaru, but not that
> of saga; I should have.)
>
> saga still needed a patch, and VTK too, because the 2.4.0 update of libHaru
> contained several breaking changes.
>
> Paul A. Patience (3):
> gnu: libharu: Update to 2.4.2.
> gnu: saga: Fix build with newer libHaru.
> gnu: vtk: Use system libHaru.
>
> gnu/packages/geo.scm | 9 ++++++-
> gnu/packages/image-processing.scm | 22 ++++++++++------
> gnu/packages/pdf.scm | 44 ++++++++++++++++---------------
> 3 files changed, 45 insertions(+), 30 deletions(-)
Thanks, these changes generally look good to me, and seem to update/fix
things, so I've gone ahead and pushed them to master as
c967d1153cae419e4acbe0dbed8f558d95ced0e3.
Thanks again,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2022-09-17 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 19:51 [bug#57685] [PATCH] gnu: libharu: Update to 2.4.1 Paul A. Patience
2022-09-10 9:55 ` Christopher Baines
2022-09-12 19:25 ` [bug#57685] [PATCH v2 0/3] gnu: libharu: Update to 2.4.2 Paul A. Patience
2022-09-12 19:25 ` [bug#57685] [PATCH v2 1/3] " Paul A. Patience
2022-09-12 19:25 ` [bug#57685] [PATCH v2 2/3] gnu: saga: Fix build with newer libHaru Paul A. Patience
2022-09-12 19:25 ` [bug#57685] [PATCH v2 3/3] gnu: vtk: Use system libHaru Paul A. Patience
2022-09-17 17:20 ` Christopher Baines [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=87y1uhrk7c.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=57685-done@debbugs.gnu.org \
--cc=paul@apatience.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).