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
maintainer think this needs to be handled in python-bzrlib, by all
means
re-assign it.
The current situation as it stands though is, that this combination
of
package is not installable, which to me is RC.
No, it's not a threat. It's just the fact that this BTS ticket has
absolutely nothing to do with python-paramiko package as it is
python-bzrlib that put a Conflict in place. The problem with paramiko
already has it's own ticket and it's being addressed by an upstream
ticket already as well. The python-bzrlib made their package
uninstallable on purpose and I can't do anything about that. Even when I
get the fixed version of paramiko uploaded and available through the
mirror network, python-bzrlib will still be uninstallable until it
releases a new version removing the Conflict. In my opinion that only
makes matters worse. Nothing I will do will affect python-bzrlib being
installable. Therefore this ticket is a "wontfix" ticket as there is no
"cantfix" tag.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
