Hi! intrigeri (2019-07-16): > as announced on this bug report and on debian-devel@ in November 2018, > GTK 2 is going away in Bullseye, so I'm hereby bumping severity of > these bugs, on every reverse-dependency of libgtk2-perl, to RC. > > I hope that upstream will port the code to GTK 3 in time for the > Bullseye freeze :)
A year after this package was removed from testing, I'm wondering what's the best course of action for the next steps. I see that: - The last upstream release dates back to 2006, although Axel Beckert reported on #782341 that a newer version was floating around on the web, although it might be a third-party CVS snapshot not sanctioned by the upstream maintainer. - The last upload to Debian happened in 2015. - The Homepage control field points to Alioth, which was decommissioned a while ago. - In the BTS, there are a bunch of patches submitted years ago. All this suggests to me that you lack interest and/or capacity to maintain this package. That's perfectly OK: life and priorities shifts do happen :) What do you think we should do? I can think of several options, from the least drastic to the most: - File a Request For Help (RFH) bug against wnpp, in order to alert users and fellow Debian people about the current situation. popcon suggests this package is still quite popular, so I have some hope someone could volunteer :) - Orphan the package. - Remove the package from sid. What do you think? Cheers!
