Request for sponsor: pytest-bdd

2019-07-26 Thread Scott Talbert

Hi,

I did a major update for pytest-bdd (new upstream release, dropped py2 
packages, other lintian fixes, etc.).  Does someone mind uploading it?


https://salsa.debian.org/python-team/modules/pytest-bdd

Thanks,
Scott



Re: Removing python2 packages

2019-07-26 Thread Scott Talbert

On Wed, 24 Jul 2019, Neil Williams wrote:


út 23. 7. 2019 v 11:40 odesílatel Scott Talbert 
napsal: When removing leaf python2 packages for bullseye, is there
  anything


__modules__ package :)
 
  special that needs to be done, other than removing the
building of the
  python2 subpackage?

  For example, obsoleting of the old package or anything along
  those lines?


* check reverse-depends and "reverse-depends -b"
* remove from d/control
* remove from d/tests
* remove from d/rules
* check/remove d/python-* files
* test
* upload


Thanks.  The reason I asked about 'obsoleting' is because I wondered
about what will happen on the upgrade case.  Say, I remove python-foo
from bullseye.  When a user running buster with python-foo installed
upgrades to bullseye, what will happen?  Will apt try to remove
python-foo?


Not unless something actually Breaks: or Conflicts: or the user runs
autoremove.

If a leaf package bar changes from Depends: python-foo to python3-foo,
then python-foo will remain installed. There are lots of packages in
Stretch that are not in Buster. Upgrading leaves them in place unless
there is something which actively Conflicts: or Breaks: them. That's
why autoremove is so useful after dist-upgrade.


What about reverse dependencies that are "Suggests" vice "Depends?"  Do 
all Suggests dependencies needs to be removed first as well?


NOTE: reverse-depends (aside from '-b' being broken in unstable right 
now), does not seem to show Suggests dependencies by default.