The package fell victim to the maintainer's obsessive hacking out of anything even vaguely Python2. There IS a Python3 version of trac and it works fine. Reproducible: Always
Please be polite. It was removed because nobody was willing to look after it.
Ebuilds don't maintain themselves.
I'm trying to be polite but just recently I'm seriously being forced to consider abandoning Gentoo entirely because of all the packages that are getting removed (mostly by the same person). In this case, it took me all of five minutes to convert the ebuild that got removed into one that calls up the Python 3 version of trac, and that included having to check how Python ebuilds are put together.
(In reply to Robert Pearce from comment #3) > I'm trying to be polite but just recently I'm seriously being forced to > consider abandoning Gentoo entirely because of all the packages that are > getting removed (mostly by the same person). > In this case, it took me all of five minutes to convert the ebuild that got > removed into one that calls up the Python 3 version of trac, and that > included having to check how Python ebuilds are put together. You are welcome to volunteer to look after the package though. Just nobody did. One person is removing them because nobody steps up or actually maintains them. If you want to move forward constructively, see https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers and I can help. We also have #gentoo-proxy-maint on Freenode which is a good place to ask questions (it's easy to miss stuff on Bugzilla).
(In reply to Robert Pearce from comment #3) > I'm trying to be polite but just recently I'm seriously being forced to > consider abandoning Gentoo entirely because of all the packages that are > getting removed (mostly by the same person). > In this case, it took me all of five minutes to convert the ebuild that got > removed into one that calls up the Python 3 version of trac, and that > included having to check how Python ebuilds are put together. Gentoo is a community project, you don't pay for support nor have any guarantees things will work. It's just a goodwill of others who put their time and effort so that you have the best possible experience. Michał asked multiple times if anyone wishes to take care of Trac, nobody volunteered meaning nobody has interest in keeping in up to date and thus he removed it because Trac was standing in the way of having Gentoo current with Python 3 only. Sorry, there is no Python 2 support anymore. As Sam mentioned, feel free to invest that 5 minutes and open a PR to re-add it to portage and add yourself as the maintainer. Please don't blame others for it, Michał (and others) are doing the best they can whilst their time is limited. If you cannot live with this model, feel free to look for another distro.
(In reply to Tomáš Mózes from comment #5) > > Gentoo is a community project, you don't pay for support nor have any > guarantees things will work. That's fine if your goal is to be a minority also-ran, like AntiX or Bodhi. > Michał asked multiple times if anyone wishes to take care of Trac, But who did he ask? I'm sure there are mechanisms for raising such questions among the maintainers but that's surely inadequate. If a package lacks a maintainer, you're not going to find one unless the wider user base - and particularly those of us using the package - get asked. I can tell you that I was completely unaware of any "asking" going on. In fact I only discover packages are "in need of help" when they suddenly vanish into thin air. I knew Python2 was being removed but I also knew trac had a Python3 port. Perhaps portage should give big warnings about any installed packages "at risk", with invitations to take on the mantle. > As Sam mentioned, feel free to invest that 5 minutes and open a PR to re-add > it to portage and add yourself as the maintainer. I would but I get the impression you expect the maintainer to be intimately involved with the package and - as I've seen demanded in a PR thread - to have a proven record of fixing bugs in the package. I don't know the trac code at all, I'm only a user. The only package I could take on in that context would be GPSim.
(In reply to Robert Pearce from comment #6) > (In reply to Tomáš Mózes from comment #5) > > Michał asked multiple times if anyone wishes to take care of Trac, > > But who did he ask? I'm sure there are mechanisms for raising such questions > among the maintainers but that's surely inadequate. If a package lacks a > maintainer, you're not going to find one unless the wider user base - and > particularly those of us using the package - get asked. I can tell you that > I was completely unaware of any "asking" going on. In fact I only discover > packages are "in need of help" when they suddenly vanish into thin air. > > I knew Python2 was being removed but I also knew trac had a Python3 port. > > Perhaps portage should give big warnings about any installed packages "at > risk", with invitations to take on the mantle. It was asked on the dev-mailing list: https://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg90322.html Since Gentoo users don't register their e-mail the only notification you've received was the package mask that you see when you interact with portage. The mask usually stays there for 30 days so you know in advance that the package is to be removed. Maybe opt-in for the dev-announce list to see these messages in advance. > > > As Sam mentioned, feel free to invest that 5 minutes and open a PR to re-add > > it to portage and add yourself as the maintainer. > > I would but I get the impression you expect the maintainer to be intimately > involved with the package and - as I've seen demanded in a PR thread - to > have a proven record of fixing bugs in the package. I don't know the trac > code at all, I'm only a user. The only package I could take on in that > context would be GPSim. I'm almost certain that if the Trac ebuild was in good shape you could just take the removed files, adjust to new versions and commit a PR and it would be accepted if you add yourself as maintainer.
