Your message dated Fri, 4 Oct 2019 17:39:40 +1300 with message-id <[email protected]> and subject line Re: Bug#941340: sooperlooper: Should sooperlooper be removed from Debian? has caused the Debian Bug report #941340, regarding sooperlooper: Should sooperlooper be removed from Debian? to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 941340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941340 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: sooperlooper Version: 1.7.3~dfsg0-3 Severity: normal I think it's time to remove the sooperlooper package: * last upstream release was nearly 5 years ago * last package update was more than 2.5 years ago * has low popcon - inst:223 vote:20 * has no reverse dependencies (according to dak rm) * 4 open bugs, only the one from 2010 has any maintainer response * a blocker for the current wxwidgets3.0-gtk3 transition. If there are no objections within two weeks, I'll turn this into an RM bug. Cheers, Olly
--- End Message ---
--- Begin Message ---On Thu, Oct 03, 2019 at 07:41:50PM +0200, Olivier Humbert wrote: > I've had a look to the outstanding bugs. > 1. one is just a user using the wrong binary to launch sooperlooper > (#920813) OK, I've closed that one. > 2. one is probably something coming from the time stretch was in dev > (#836232) and I can't reproduce it now on Stretch or Buster. I've cc-ed the submitter to see if they can (note that the BTS doesn't automatically send replies to the submitter). > 3. one is from a very old version of sooperlooper : 1.6.14 dating back from > 2009 (see http://essej.net/sooperlooper/), so should probably be closed if > unreproducible nowadays (#596392) Hmm, and it was also marked as fixed by one of the maintainers 6 years ago: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596392;msg=43 I assume they failed to notice that setting a fixed version doesn't close the bug. Now closed. > 4. the last one is about building against gtk3 wx instead of gtk wx and it > is the case nowadays if I'm not wrong reading at > https://salsa.debian.org/multimedia-team/sooperlooper/blob/master/debian/control > so should probably be closed as well (#933425) No, that still says "libwxgtk3.0-dev" - it needs to be changed to "libwxgtk3.0-gtk3-dev" for the transition. > I've been talking with upstream those last few days and he might be willing > to release a new version including a bunch of different fixes. See > https://github.com/essej/sooperlooper/pull/13 Yes, that would be good. And thanks for helping to deal with the bug backlog. > It could then be wise to keep it in Debian regarding all of that. OK - I won't push for removal from Debian. Closing this bug. The lack of any evidence of an active maintainer for the Debian package still seems problematic, unless you and/or Nicolas are part of the Debian Multimedia Maintainers team? Also note that the package will get autoremoved from testing unless the maintainers take action since the wxwidgets transition bugs are now RC (but it'll automatically return if/when it's updated for the transition). Cheers, Olly
--- End Message ---
_______________________________________________ pkg-multimedia-maintainers mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
