all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vinicius Monego <monego@posteo.net>
To: 49357@debbugs.gnu.org
Subject: [bug#49357] [PATCH] gnu darktable update to 3.6.0
Date: Sat, 03 Jul 2021 16:29:41 +0000	[thread overview]
Message-ID: <e831f9988a9cd90fb45e404a9a9a934c9c9b1c64.camel@posteo.net> (raw)
In-Reply-To: <tNuBKoaI8bHsZaFio2MR9KrBJ5_yzvB38GqnX45U2Z174ERcD2rAEgEV76tS5RnZ2Yl3WHkzhKUUJ81zvkEj3xJ7x-Ibad2tU_X3Dqtiemw=@protonmail.com>

Hello,

I noticed a warning in the build that darktable now expects LLVM-12,
and this:

> CMake Warning at src/CMakeLists.txt:332 (find_package):
>   Could not find a configuration file for package "OpenEXR" that is
>   compatible with requested version "3.0".
> 
>   The following configuration files were considered but not accepted:
> 
>     /gnu/store/rhixcbc778wwbi9g7j7qdcbbzpv5rgf7-openexr-
> 2.5.5/lib/cmake/OpenEXR/OpenEXRConfig.cmake, version: 2.5.5
> 

Is the openexr export working in the compiled package? If not, I'd
suggest renaming openexr to openexr-2, packaging openexr 3, and then
updating darktable to keep the same set of features. WDYT?

OpenEXR 3 seems to be incompatible with version 2 [1].

[1]
https://github.com/AcademySoftwareFoundation/Imath/blob/master/docs/PortingGuide2-3.md





  reply	other threads:[~2021-07-03 17:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03 16:17 [bug#49357] [PATCH] gnu darktable update to 3.6.0 John Kehayias via Guix-patches via
2021-07-03 16:29 ` Vinicius Monego [this message]
2021-07-04  0:38 ` John Kehayias via Guix-patches via
2021-07-06  0:03 ` Vinicius Monego
2021-07-06 21:51 ` John Kehayias via Guix-patches via
2021-07-08  7:47   ` bug#49357: " Nicolas Goaziou
2021-07-08 14:39     ` [bug#49357] " John Kehayias via Guix-patches via

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=e831f9988a9cd90fb45e404a9a9a934c9c9b1c64.camel@posteo.net \
    --to=monego@posteo.net \
    --cc=49357@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.