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 withi
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 packa
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 is
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 bu
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
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 patc
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 lan
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
8 matches
Mail list logo
