Re: intent to hijack python-paramiko

2006-07-26 Thread Jeremy Bouse
Go ahead and NMU with my thanks and blessing... I've made my move cross-country but my system at home is still without network connectivity at this time and the telco has been unable to give me anything close to a firm ETA of when they will. Regards,JeremyOn 7/17/06, Martin Michlmayr <[EMAIL PROTEC

Re: intent to hijack python-paramiko

2006-07-17 Thread Martin Michlmayr
* Wouter van Heyst <[EMAIL PROTECTED]> [2006-07-17 20:35]: > > He was moving cross-country in May, so I suggest you NMU for now. > > Would NMUing a new upstream be ok in this instance then? I think so, yes. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTE

Re: intent to hijack python-paramiko

2006-07-17 Thread Wouter van Heyst
On Mon, Jul 17, 2006 at 07:40:37PM +0200, Martin Michlmayr wrote: > * martin f krafft <[EMAIL PROTECTED]> [2006-07-17 19:35]: > > 1.6.1 is now upstream, and #344734 is over half a year old. Unless > > we hear from the maintainer (Jeremy Bouse, on CC to be sure) by the > > end of this week, we will

Re: intent to hijack python-paramiko

2006-07-17 Thread martin f krafft
also sprach Martin Michlmayr <[EMAIL PROTECTED]> [2006.07.17.1940 +0200]: > > 1.6.1 is now upstream, and #344734 is over half a year old. Unless > > we hear from the maintainer (Jeremy Bouse, on CC to be sure) by the > > end of this week, we will take over the package as it's blocking bzr > > He w

Re: intent to hijack python-paramiko

2006-07-17 Thread Martin Michlmayr
* martin f krafft <[EMAIL PROTECTED]> [2006-07-17 19:35]: > 1.6.1 is now upstream, and #344734 is over half a year old. Unless > we hear from the maintainer (Jeremy Bouse, on CC to be sure) by the > end of this week, we will take over the package as it's blocking bzr He was moving cross-country in