Thank you for your time. I believe the rejection to be correct, but allow me to answer the points, for completeness’s sake.
> - #2 - please outline why it can't stay a suggests. Extend the case here > by the reasoning that we should hold against the maintenance effort > and quality bar it has to pass. After digging further into a few rdepends, I believe it can stay as a suggest. However, there is a caveat: upstream has removed the optional dependency and switched to a hard depends with version 4.0.0. This may cause breakage in the future. This change is described by the upstream changelog https://github.com/paramiko/paramiko/blob/8697158113a3eab25ed1d1d541ebe2cad10169a7/sites/www/changelog.rst#L13 Of the various callsites I've looked, all appear to use paramiko.SSHClient, and none of the paramiko.config parser, so we should still be fine without invoke. Additionally, as of paramiko-4.0.0, the import excepts are still in place. So for now, it looks we're fine without invoke. As to the topic of fabric as an alternative, paramiko is a dependency of fabric, thus bringing us back here. > - debian/control: Demote python3-invoke from Recommends to Suggests as > the python-invoke package lacks unit test execution so is not suitable > for main inclusion python-invoke package does have unit tests now and those do run at build time, as visible in the most recent build: https://launchpadlibrarian.net/756784668/buildlog_ubuntu-plucky-amd64.python-invoke_2.2.0-2_BUILDING.txt.gz#:~:text=test%20session%20starts This makes me believe this specific rationale may be outdated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2138736 Title: [MIR] python-invoke (paramiko dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-invoke/+bug/2138736/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
