Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Scott Talbert <swt@techie.net>
Newsgroups: linux.debian.maint.python
Subject: Re: Removing python2 packages
Date: Fri, 26 Jul 2019 15:50:01 +0200
Message-ID: <yo8LD-5uL-7@gated-at.bofh.it>
References: <yn4h3-5Wr-9@gated-at.bofh.it> <yn75g-7Kf-15@gated-at.bofh.it> <yns01-48A-5@gated-at.bofh.it> <yntSa-5o1-1@gated-at.bofh.it>
Old-Return-Path: <swt@techie.net>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="-2033333575-1252252491-1564148861=:29330"
Approved: robomod@news.nic.it
Lines: 53
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.python:11531

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---2033333575-1252252491-1564148861=:29330
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT

On Wed, 24 Jul 2019, Neil Williams wrote:

>>> út 23. 7. 2019 v 11:40 odesílatel Scott Talbert <swt@techie.net>
>>> 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.
---2033333575-1252252491-1564148861=:29330--