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: Tue, 06 Jul 2021 00:03:33 +0000	[thread overview]
Message-ID: <a76e9e2941715b864042c80527a32ab95cc7549e.camel@posteo.net> (raw)
In-Reply-To: <tNuBKoaI8bHsZaFio2MR9KrBJ5_yzvB38GqnX45U2Z174ERcD2rAEgEV76tS5RnZ2Yl3WHkzhKUUJ81zvkEj3xJ7x-Ibad2tU_X3Dqtiemw=@protonmail.com>

> It seems like moving to openexr 3 should be done to address security
> issues: https://issues.guix.gnu.org/47509This looks like it may
> involve patching many of the dependent packages, based on what I see
> in Arch (which only has openexr 3 and numerous small patches, though
> looked easy enough).

I left a comment on that issue. OpenEXR addressed those vulnerabilities
in version 2.5.4, while we're at 2.5.5.

> So I think this update to Darktable is okay, but we should move to
> openexr 3 for everything due to #47509.

Looking at the releases page for openexr, it seems that both versions 2
and 3 are being actively maintained. We can have both, and IMO we
should. But there's no need to work on it immediately.

I built the package and executed darktable --version and also see that
openexr support is enabled. This patch LGTM then. I will now wait for a
committer to review.

Thanks,

Vinicius





  parent reply	other threads:[~2021-07-06  0:04 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
2021-07-04  0:38 ` John Kehayias via Guix-patches via
2021-07-06  0:03 ` Vinicius Monego [this message]
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=a76e9e2941715b864042c80527a32ab95cc7549e.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.