let's not yet hijack this package (Re: Intend to hijack xchat-xsys)
On Tue, 2008-03-11 at 22:19 -0200, UlisesVitulli wrote: Hi debian-devel, I've been talking with the maintainer[1] of xchat-xsys[2] Private conversation ? for several bugs I don't see several bugs. http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=xchat-xsys and many new upstream releases hold back on Debian, Two upstream releases. grep ^v xsys-2.2.0/ChangeLog | head -n 3 v2.2.0 v2.1.0 v2.0.9 Please report a bug to the bts requesting the newest upstream release to be packaged in Debian. and he communicated me that he is not longer interested on maintaining it any more. Private conversation ? Unfortunately, my suggestion of orphaning the pkg made no difference to the current maintainer, as he showed no cares at all for it. Maybe the maintainer does not agree about orphaning ? With a modest popcon of 242[3] and a bug related to a dep, rendering the pkg in an unusable state, Please report this bug related to a dep in the bts. this package needs attention. I suggest that you use the bts to document that in public. If there are no objections, I object. I plan to upload a new pkg Please follow the NMU procedure if you want to update the package yourself. The current 0-day NMU upload policy might be applicable depending on the severity of the bugs to be fixed. which, not only solves the critical bug I mentioned, Please report this critical bug in the bts. it incorporates about 2 years and a half of updates, Almost 2 years. And, yes, that's a long time, giving the impression that the maintainer is no longer interested, or at least temporarily not active. solving two bugs more listened on BTS. If you have fixes for existing bugs in the bts, then please post the fixes to the bts. Regards, Bart Martens signature.asc Description: This is a digitally signed message part
Re: Intend to hijack xchat-xsys
Hi, On Tue, 2008-03-11 at 22:19 -0200, UlisesVitulli wrote: I've been talking with the maintainer[1] of xchat-xsys[2] for several bugs and many new upstream releases hold back on Debian, and he communicated me that he is not longer interested on maintaining it any more. Tell him to orphan the package, then. Alternatively, but more controversially, you might consider orphaning it yourself, and CC'ing the maintainer. But that's controversial, and I wouldn't recommend it unless you can back up your claims. William signature.asc Description: This is a digitally signed message part
Re: Intend to hijack xchat-xsys
On Tue, Mar 11, 2008 at 10:19:01PM -0200, UlisesVitulli wrote: I've been talking with the maintainer[1] of xchat-xsys[2] (...) Unfortunately, my suggestion of orphaning the pkg made no difference to the current maintainer, as he showed no cares at all for it. If he showed no care at all for it, I would presume he would also be OK with you adopting the package? You don't need him to orphan it first, if he tells you (e.g. in an email), OK, it is yours, you can make an upload changing maintainer to you, and it is not (socially) a hijack. If he actively vetoed you adopting the package, well, there's something I don't understand, so I can't express an opinion. -- Lionel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Intend to hijack xchat-xsys
Hi all! I've been talking with the maintainer[1] of xchat-xsys[2] for several bugs and many new upstream releases hold back on Debian, and he communicated me that he is not longer interested on maintaining it any more. Unfortunately, my suggestion of orphaning the pkg made no difference to the current maintainer, as he showed no cares at all for it. The maintainer stated that he's not using Debian anymore, and thus doesn't want to bother orphaning the package. Also he said that he is ok with Ulises becoming the new maintainer. Thus, THIS IS NOT A HIJACK. This is an adoption without an O: bug, which is actually quite a common practice when the old maintainer and the new maintainer agree on this via IRC or some other medium. There was no need to contact debian-devel about this. I thought we had already agreed on this. -- Besos, Marga -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
