Unmaintained package depending on enchant:0.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bb943e4dcea7afc5c358c626b29bbac5745b2f02 commit bb943e4dcea7afc5c358c626b29bbac5745b2f02 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2023-05-08 16:54:19 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2023-05-08 16:54:19 +0000 profiles: Mask net-im/mcabber for removal Bug: https://bugs.gentoo.org/903131 Bug: https://bugs.gentoo.org/905954 Signed-off-by: Matt Turner <mattst88@gentoo.org> profiles/package.mask | 6 ++++++ 1 file changed, 6 insertions(+)
Can we stop the last rites process? The developer just fixed the crash (which is not in mcabber, but in loudmouth instead) mentioned in #903131.
It also builds fine with the following patch from the developer to support enchant-2: https://lilotux.net/~mikael/pub/mcabber/patches/enchant2.patch
(In reply to Wolfram Schlich from comment #3) > It also builds fine with the following patch from the developer to support > enchant-2: https://lilotux.net/~mikael/pub/mcabber/patches/enchant2.patch Any clue why that's not upstream?
(In reply to Wolfram Schlich from comment #2) > Can we stop the last rites process? Is someone going to maintain the package? If the only time the package gets any effort is to save it from being removed, it's really a pain in the ass.
(In reply to Matt Turner from comment #4) > (In reply to Wolfram Schlich from comment #3) > > It also builds fine with the following patch from the developer to support > > enchant-2: https://lilotux.net/~mikael/pub/mcabber/patches/enchant2.patch > > Any clue why that's not upstream? Yes, the developer just created it for me when I reported the issue to him before he left for vacation (this week).
(In reply to Matt Turner from comment #5) > (In reply to Wolfram Schlich from comment #2) > > Can we stop the last rites process? > > Is someone going to maintain the package? I'm afraid I cannot really answer this question. The only thing I can offer is to proxy-maintain it, as I'm not a dev anymore since quite some time... > If the only time the package gets any effort is to save it from being > removed, it's really a pain in the ass. I'm in direct contact with Mikael Berthe, so I'd say as long as he is taking care of his software, I should be able to take care of the proxy maintainership.
Sounds good. Could you please do a Github PR making a new revision / _p version with the latest (2?) patches added, or ask upstream to cut a new release? Then add yourself as a proxy maintainer and unmask the package from package.mask file. Let me know if you need help with anything. https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide#Proxied_maintainer_in_metadata.xml
Removal is schedule for June 8, in two days.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e2d4d96699cb4f042a83f3bf8089304f52b4a723 commit e2d4d96699cb4f042a83f3bf8089304f52b4a723 Author: Matt Turner <mattst88@gentoo.org> AuthorDate: 2023-06-11 22:20:40 +0000 Commit: Matt Turner <mattst88@gentoo.org> CommitDate: 2023-06-11 22:30:22 +0000 net-im/mcabber: Delete Bug: https://bugs.gentoo.org/848801 Bug: https://bugs.gentoo.org/903131 Closes: https://bugs.gentoo.org/905954 Signed-off-by: Matt Turner <mattst88@gentoo.org> net-im/mcabber/Manifest | 1 - net-im/mcabber/files/README.gentoo | 17 ------ net-im/mcabber/mcabber-1.1.2-r1.ebuild | 99 ---------------------------------- net-im/mcabber/mcabber-9999.ebuild | 99 ---------------------------------- net-im/mcabber/metadata.xml | 20 ------- profiles/arch/mips/package.use.mask | 4 -- profiles/package.mask | 6 --- 7 files changed, 246 deletions(-)
You're welcome to revisit https://bugs.gentoo.org/905954#c8 despite removal.
