Control: reopen -1
2014-06-26 22:45 GMT+01:00 Michael Biebl <[email protected]>: > Am 26.06.2014 23:34, schrieb Manuel A. Fernandez Montecelo: >> 2014-06-26 22:05 GMT+01:00 Michael Biebl <[email protected]>: >>> Am 26.06.2014 22:51, schrieb Debian Bug Tracking System: >>>> This is an automatic notification regarding your Bug report >>>> which was filed against the razorqt-power package: >>>> >>>> #752442: razorqt-power: upower-1.0 transition >>>> >>>> It has been closed by "Manuel A. Fernandez Montecelo" >>>> <[email protected]>. >>>> >>>> Their explanation is attached below along with your original report. >>>> If this explanation is unsatisfactory and you have not received a >>>> better one in a separate message then please contact "Manuel A. Fernandez >>>> Montecelo" <[email protected]> by >>>> replying to this email. >>>> >>>> >>> >>> Thanks for your reply Manuel. >>> >>> If you aren't sure if razorqt-power is actually affected by the upower >>> 0.99 update, please don't just close it. >>> >>> It's not like the transition can only start if all bugs have been >>> closed. Those bugs are there to actually track progress with affected >>> packages. >>> >>> I had a quick look at razorqt-power/*.cpp and it *does* use the >>> suspend/hibernate functionality from upower, which no longer exists in >>> upower 0.99. >>> >>> In the end it's your choice as maintainer, but closing the bug report >>> seems wrong to me. >> >> I'm hesitant. For me it would be ok-ish to keep it open, but >> realistically I don't see myself investigating and patching it to keep >> it entering the next release. >> >> I've even been pondering doing the contrary: submitting a RC bug to >> keep it removed from testing, or creating kind of transitional >> packages to move people to LXDE-qt versions once they are present >> (however, this is a quite hairy process, I think). >> >> razorqt-session has popcon of 228, which is not too bad, given that >> it's not been in an stable release (when LXDE-Qt is available, maybe >> people migrate "en masse" though). >> >> But then again, I don't think that it is sensible to spend too much >> time in the package, abandoned upstream as it is, not present in any >> stable release (thus: only used by "adventurers" who should know their >> ways around; and no need for formal migrations), and with better >> alternative projects being packaged soon (ITP bugs). >> > > If you don't think razorqt-power is ready for release, re-open the bug, > bump it to serious. > > It will then automatically be removed from testing. > > If you get around to it to actually fix the upower 0.99 integration, you > can close the bug and the package will re-enter testing. > > If on the other hand, say in a year or so, no further development has > happened, you can re-assign this bug to ftp.debian.org and ask for the > complete removal of the package. > > In any case, it makes sense to re-open the bug report. OK, reopened, thanks. -- Manuel A. Fernandez Montecelo <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
