From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 53556@debbugs.gnu.org
Subject: [bug#53556] [PATCH 1/2] gnu: Remove luminance-hdr.
Date: Wed, 26 Jan 2022 23:32:57 -0500 [thread overview]
Message-ID: <87sft923ye.fsf@gmail.com> (raw)
In-Reply-To: <7a88f1fb3871c06149160514492af06fb3edac71.1643221548.git.leo@famulari.name> (Leo Famulari's message of "Wed, 26 Jan 2022 13:25:47 -0500")
Hello Leo,
Leo Famulari <leo@famulari.name> writes:
> This package doesn't build anymore:
>
> https://ci.guix.gnu.org/search?query=spec%3Amaster+system%3Ax86_64-linux+luminance-hdr
>
> * gnu/packages/image-viewers.scm (luminance-hdr): Remove variable.
> ---
> gnu/packages/image-viewers.scm | 63 ----------------------------------
> 1 file changed, 63 deletions(-)
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/
Other distributions are offering the package; we should check how they
do it.
At any rate, I don't think we should remove broken packages just because
they happen to be broken now. It seems your concern was to advertise
broken packages to our users? If so the way to do that would be to plug
the CI results in the generated package list on our site (they could be
shown in red or something).
Thanks,
Maxim
next prev parent reply other threads:[~2022-01-27 4:34 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 ` Maxim Cournoyer [this message]
2022-01-27 6:10 ` [bug#53556] [PATCH 1/2] gnu: Remove luminance-hdr Leo Famulari
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
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=87sft923ye.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=53556@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).