Open issues in Gentoo lead to package removal in less than 30 days

[michl85]

The Gentoo maintainer will remove x11-plugins/lurch and its dependencies net-libs/libomemo and net-libs/libaxc from its package management in less than 30 days due to "open issues" (https://bugs.gentoo.org/940725). Is there any chance to fix these issues so that the packages can remain in Gentoo's packaging system?

[lowusage]

Looking at the issues, most of them seems to already exist as, or are linkted to some, issues here. Note that since today the package isn't in the repos anymore.

The two latest commits (27 october), have been the first since 2 years.
I think the maintainer is already aware of those issues, and putting much pressure isn't needed.

Nevertheless, I think it might be useful to have informations on the current state of the project; if @gkdr isn't interested in maintaining it anymore it is understandable, otherwise I believe some people might want to show support in any manner.

[iasdeoupxe]

Related to these?

• Tests fail to compile with GCC 14 #187
• Use pkg-config to locate libgcrypt #190

[gkdr]

Hi @michl85, @lowusage, @iasdeoupxe, thanks for calling it to my attention.
Not to make excuses, but unfortunately I only got email notifications from @iasdeoupxe's posts last week and not any of the earlier ones, including the linked new issues. I don't think this is a GH issue, I suspect my dying email provider and will change it in the settings.

I was in fact not aware, and sorry I didn't make it in time. I'm still willing to do maintenance work like that and will check out the related issues. For anything bigger, I am waiting on Pidgin 3, which afaik is incompatible with current plugins and will require a complete rewrite anyway.

Is there something that can be done about the issue at hand, now that the package is gone from the Gentoo package repo?

[eli-schwartz]

I suppose it's possible that @hartwork may be willing to add it back again, having been originally interested in packaging it and considering that the reason for dropping it was it seeming unmaintained.

Although the discussion in #177 indicates there may be other issues at hand?

Please take a look at https://bugs.gentoo.org/940725 including the list of "blocks". Probably it would be a good idea to ensure that none of those are still issues, before adding it back.

In particular:

• GCC 14: hopefully fixed
• mxml 4 support
• segfault during tests, maybe the same as the gcc 14 issue? https://bugs.gentoo.org/881373

[hartwork]

I suppose it's possible that @hartwork may be willing to add it back again [..]

@eli-schwartz not me, no.