Bug#682050: nmu
Now see if you had contacted the maintainer prior to performing the NMU upload you would have found out that your information was in fact flawed. BTS #690080 was to inform of the new upstream maintainer only a month ago and I've been in contact privately. Furthermore 1.9 was only released within the last week by said new upstream maintainer. That my friend is why you contact the maintainer and find out if assistance is in fact needed or else you're just mucking shit up and pissing the maintainer off considerably. On 12.11.2012 22:17, Michael Gilbert wrote: On Mon, Nov 12, 2012 at 9:50 PM, Jeremy T. Bouse wrote: Not my problem... You put the burden on me, I'm giving you the burden since you obviously took the time failing to contact me to ask and ascertain whether the maintainer might actually be in the process of doing anything with the package. I read the bug traffic, and the latest maintainer activity was four months ago. That's usually a strong indicator that the package needs help. The RC issues were introduced by a previous NMU, the issues are resolved in the new upstream release so as far as I'm concerned their wont-fix issues in this version. I understand that this was introduced by the prior nmu, and that's why this nmu is reverting that broken one. But as I'm turning the package over to you, do what you like. You may as well orphan it so it can get cared for either by the QA team or someone who really cares about it. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682050: nmu
Hi, I've uploaded an nmu fixing this issue to delayed/8. The extra time is to give you a chance to do a maintainer upload taking into account your stated dislike for nmus. Please see attached patch. Best wishes, Mike paramiko.patch Description: Binary data
Bug#682050: nmu
On Mon, Nov 12, 2012 at 9:08 PM, Jeremy T. Bouse wrote: Typically one would contact the maintainer before doing an NMU which you failed to do. Quite the contrary. The message you just replied to is my contact prior to the nmu. It has not happened yet. It is currently in a kind of limbo land called deferred. Importantly, you have the power to review it there and cancel it if you don't like it: http://manpages.ubuntu.com/manpages/en/man1/dcut.1.html If you had you would have been informed that I'm waiting on the new upstream maintainer to make the release merging paramiko and it's fork that would fix most of the issues with the current code base the patches introduced by the last NMU improperly fixed and caused regressions. Thanks for the info. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682050: nmu
Typically one would contact the maintainer before doing an NMU which you failed to do. If you had you would have been informed that I'm waiting on the new upstream maintainer to make the release merging paramiko and it's fork that would fix most of the issues with the current code base the patches introduced by the last NMU improperly fixed and caused regressions. On 12.11.2012 18:21, Michael Gilbert wrote: Hi, I've uploaded an nmu fixing this issue to delayed/8. The extra time is to give you a chance to do a maintainer upload taking into account your stated dislike for nmus. Please see attached patch. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682050: nmu
On Mon, Nov 12, 2012 at 9:34 PM, Jeremy T. Bouse wrote: Thank you for volunteering to become the new paramiko package maintainer since you have so much spare time. I did this nmu to try to help make progress against the huge list of rc issues we have in many packages. I'm not that interested in this one so much. I'll be updating the debian/control file with the 1.9.0 upstream release as soon as I've completed it. The release team will probably not accept new upstream versions at this point in the freeze. Since you've put a gun to my head with the 8 day delay hopefully I'll get all the bugs worked out of it before I upload it and let you take over. That delay wasn't meant to be pressuring. It was just a choice that seemed kind of long. Please feel free to go ahead and cancel it if you need more time. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682050: nmu
Thank you for volunteering to become the new paramiko package maintainer since you have so much spare time. I'll be updating the debian/control file with the 1.9.0 upstream release as soon as I've completed it. Since you've put a gun to my head with the 8 day delay hopefully I'll get all the bugs worked out of it before I upload it and let you take over. On 12.11.2012 21:18, Michael Gilbert wrote: On Mon, Nov 12, 2012 at 9:08 PM, Jeremy T. Bouse wrote: Typically one would contact the maintainer before doing an NMU which you failed to do. Quite the contrary. The message you just replied to is my contact prior to the nmu. It has not happened yet. It is currently in a kind of limbo land called deferred. Importantly, you have the power to review it there and cancel it if you don't like it: http://manpages.ubuntu.com/manpages/en/man1/dcut.1.html If you had you would have been informed that I'm waiting on the new upstream maintainer to make the release merging paramiko and it's fork that would fix most of the issues with the current code base the patches introduced by the last NMU improperly fixed and caused regressions. Thanks for the info. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682050: nmu
Not my problem... You put the burden on me, I'm giving you the burden since you obviously took the time failing to contact me to ask and ascertain whether the maintainer might actually be in the process of doing anything with the package. The RC issues were introduced by a previous NMU, the issues are resolved in the new upstream release so as far as I'm concerned their wont-fix issues in this version. But as I'm turning the package over to you, do what you like. On 12.11.2012 21:43, Michael Gilbert wrote: On Mon, Nov 12, 2012 at 9:34 PM, Jeremy T. Bouse wrote: Thank you for volunteering to become the new paramiko package maintainer since you have so much spare time. I did this nmu to try to help make progress against the huge list of rc issues we have in many packages. I'm not that interested in this one so much. I'll be updating the debian/control file with the 1.9.0 upstream release as soon as I've completed it. The release team will probably not accept new upstream versions at this point in the freeze. Since you've put a gun to my head with the 8 day delay hopefully I'll get all the bugs worked out of it before I upload it and let you take over. That delay wasn't meant to be pressuring. It was just a choice that seemed kind of long. Please feel free to go ahead and cancel it if you need more time. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682050: nmu
On Mon, Nov 12, 2012 at 9:50 PM, Jeremy T. Bouse wrote: Not my problem... You put the burden on me, I'm giving you the burden since you obviously took the time failing to contact me to ask and ascertain whether the maintainer might actually be in the process of doing anything with the package. I read the bug traffic, and the latest maintainer activity was four months ago. That's usually a strong indicator that the package needs help. The RC issues were introduced by a previous NMU, the issues are resolved in the new upstream release so as far as I'm concerned their wont-fix issues in this version. I understand that this was introduced by the prior nmu, and that's why this nmu is reverting that broken one. But as I'm turning the package over to you, do what you like. You may as well orphan it so it can get cared for either by the QA team or someone who really cares about it. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
