If you has contacted me you would have found I had the work pretty much done 9
hours before your first commit in your Alioth repository and I was just
finishing my testing which had to wait until I got done with my work day for my
job that pays the bills.
Sent from my Verizon Wireless 4G LTE
On 06/08/2016 08:11 PM, Jeremy T. Bouse wrote:
> Yes I already got the dependency switch from python-crypto to
> python-cryptography addressed as well... Will you let the package
> maintainer do his job and you take care of your own? Thank you.
Great, thanks!
FYI, I had to do the work as I
Yes I already got the dependency switch from python-crypto to
python-cryptography addressed as well... Will you let the package
maintainer do his job and you take care of your own? Thank you.
On 6/8/2016 2:01 PM, Thomas Goirand wrote:
> Actually, please use what's in Alioth, as it contains more
Thomas,
I already have the 2.0.0 paramiko packaging 99% ready to go. There
is no reason for an NMU by you as I stated in my earlier email message
to this ticket.
On 6/8/2016 1:42 PM, Thomas Goirand wrote:
> Hi Jeremy,
>
> I've done a pull request for the paramiko package, and also uploaded
Actually, please use what's in Alioth, as it contains more needed
commits, like switching from python-crypto to python-cryptography to
follow what upstream did, plus more fixups.
Cheers,
Thomas Goirand (zigo)
Hi Jeremy,
I've done a pull request for the paramiko package, and also uploaded it
to alioth at https://anonscm.debian.org/git/openstack/paramiko.git.
Please let me know what you think of my changes, and if it ok if I NMU
the package to experimental.
Cheers,
Thomas Goirand (zigo)
6 matches
Mail list logo
