all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 53556@debbugs.gnu.org
Subject: [bug#53556] [PATCH 1/2] gnu: Remove luminance-hdr.
Date: Thu, 27 Jan 2022 01:10:28 -0500	[thread overview]
Message-ID: <YfI3VHrfYOoDnbGB@jasmine.lan> (raw)
In-Reply-To: <87sft923ye.fsf@gmail.com>

On Wed, Jan 26, 2022 at 11:32:57PM -0500, Maxim Cournoyer wrote:
> As I mentioned on #guix, I don't think removing broken but still
> actively developed packages is the way to go.  Have you opened an issue
> with upstream about the build failure?  I've searched but haven't seen
> it.  Development now happens here:
> https://github.com/LuminanceHDR/LuminanceHDR/

I think that asking upstream is something that can be done by people who
aim to use this package. The packages have to sustain themselves with
user contributions: this work can't be done by just a handful of us.

Since this package hasn't built in a couple months (at least; that's as
far back as ci.guix.gnu.org shows us), one could guess it has no users.
A question of the chicken and the egg, perhaps, but we need a whole
henhouse regardless.

Additionally, this package depends on QtWebKit, which I am working to
remove from the distro:

https://issues.guix.gnu.org/53289

I respectfully insist that we wait 2 weeks for patches to fix this
package or else remove it from Guix.




  reply	other threads:[~2022-01-27  6:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 18:25 [bug#53556] [PATCH 1/2] gnu: Remove luminance-hdr Leo Famulari
2022-01-26 18:25 ` [bug#53557] [PATCH 2/2] gnu: Remove aseba Leo Famulari
2022-01-27  4:39   ` Maxim Cournoyer
2022-01-28 22:57     ` bug#53557: " Ludovic Courtès
2022-01-27  4:32 ` [bug#53556] [PATCH 1/2] gnu: Remove luminance-hdr Maxim Cournoyer
2022-01-27  6:10   ` Leo Famulari [this message]
2022-01-27  7:14     ` Liliana Marie Prikler
2022-01-27 19:12       ` Leo Famulari

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=YfI3VHrfYOoDnbGB@jasmine.lan \
    --to=leo@famulari.name \
    --cc=53556@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.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 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.