public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Last rites: media-gfx/gmic
Date: Wed, 25 Oct 2023 23:41:10 -0400	[thread overview]
Message-ID: <dcc60ca4-5f13-45b9-9c18-8fca8220ad6e@gmail.com> (raw)
In-Reply-To: <254730d8-2987-49b8-9ca7-2e50a071b121@gentoo.org>

On 10/25/23 9:29 PM, Jonas Stein wrote:
> Hi Marecki,
> 
> this is a very powerful package with many users.
> Thank you for maintaining it till now.
> 
> Could you address the exact problems to upstream, so they are aware and
> can improve it?
> I think not only Gentoo, but also other distributions suffer if it does
> not build smooth.
> 
> Looks to me as if the package is not broken now, but there is a lack of
> manpower to update it. 30 days is the minimum for a removal.
> 
> I suggest to keep it for a few more months.


It's difficult to tell whether the problems were reported upstream since
upstream has deleted the repository and purged all issues, PRs, commits,
tags, and anything else whatsoever back in April.

The commit message is elucidative: "Clean repository".

Per https://github.com/GreycLab/gmic/issues/1#issuecomment-1521421747

"""
Yes, my fault. I've completely messed up (mainly because I'm still a git
novice after all these years!). I had to delete/recreate the repository
from scratch.
"""

This is of course either untrue or every kind of over-reaction, and
users have commented there to the effect of being willing to help sort
things out but there has been radio silence. It is long past the 90 days
where outright github-level recovery is possible.

I think this also offers some compelling arguments against maintainers
being willing to  deal with the challenges of this software -- this is a
pretty steep social cost to investing time and effort into caring about,
using, or maintaining such software.

I suppose it's always possible to orphan the package and let it rot
until it gets last-rited for not working. Marecki -- is there any
specific concern that it's likely to rot quickly if it lacks a maintainer?


-- 
Eli Schwartz



  reply	other threads:[~2023-10-26  3:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  1:00 [gentoo-dev] Last rites: media-gfx/gmic Marek Szuba
2023-10-26  1:29 ` [gentoo-dev] " Jonas Stein
2023-10-26  3:41   ` Eli Schwartz [this message]
2023-10-27 11:52     ` Marek Szuba
2023-10-27 11:24   ` Marek Szuba
2023-10-31  6:50     ` Zoltan Puskas
2023-10-31  7:05       ` Sam James

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=dcc60ca4-5f13-45b9-9c18-8fca8220ad6e@gmail.com \
    --to=eschwartz93@gmail.com \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox