On 31.07.2014 17:43, Michael Biebl wrote:
Am 31.07.2014 17:38, schrieb Jeremy T. Bouse:
version. I'm therefore tagging as "wontfix" and will be closing it
unless you want to re-assign it to python-bzrlib.
Is that a threat?
Seriously, I don't mind where and how this is fixed. If you, as
maint
Am 31.07.2014 17:38, schrieb Jeremy T. Bouse:
> version. I'm therefore tagging as "wontfix" and will be closing it
> unless you want to re-assign it to python-bzrlib.
Is that a threat?
Seriously, I don't mind where and how this is fixed. If you, as
maintainer think this needs to be handled in py
On Thu, Jul 31, 2014 at 11:38:55AM -0400, Jeremy T. Bouse wrote:
> tag +755910 wontfix
> thanks
>
> This bug report is useless to paramiko as the Conflict/Build-Conflict is in
> python-bzrlib which I have absolutely no control of and if the maintainer
> has decided this route than even when I uplo
tag +755910 wontfix
thanks
This bug report is useless to paramiko as the Conflict/Build-Conflict
is in python-bzrlib which I have absolutely no control of and if the
maintainer has decided this route than even when I upload a new version
of paramiko that addresses the underlying issue which is
Here is the upstream bug report: https://github.com/paramiko/paramiko/issues/285
It looks like someone is already working on a patch.
Regards,
Jordan Metzmeier
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists
Package: python-paramiko
Version: 1.14.0-2
Severity: serious
python-paramiko is no longer installable once bzr is installed, since
the latest python-bzrlib has a Conflicts against python-paramiko >= 1.12.
The python-bzrlib changelog suggests that python-paramiko needs an
update:
* Conflict and
6 matches
Mail list logo
