Re: Removing python2 packages
On July 24, 2019 4:08:54 PM UTC, Scott Talbert <swt@techie.net> wrote:
>On Tue, 23 Jul 2019, Ondrej Novy 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?
It depends (pun intended). I've recently upgraded some Python applications to python3, so python-foo depends changed to python3-foo. If the only reason python-foo was installed was because it was a dependency of the application, then it'll be eligible for apt autoremove.
Scott K
Reply to: