Path: csiph.com!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod From: Scott Talbert Newsgroups: linux.debian.maint.python Subject: Re: Removing python2 packages Date: Wed, 24 Jul 2019 20:50:02 +0200 Message-ID: References: X-Mailbox-Line: From debian-python-request@lists.debian.org Wed Jul 24 18:45:09 2019 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.2 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -4.6 Dkim-Signature: v=1; a=rsa-sha256; c=simple/simple; d=techie.net; s=default; t=1563993894; bh=VPUwc1Q2E2WgHb0gS5eS7DgiX/QAYf2FeUIOTmmeMpo=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=Ai4ClTfGdBGBHmIMEUJPCTnCssFpIL3vZfih9fWNbf9otimoC1UPW6Mm3fbfj4axf fkL/iWEca8Bqnlfb2fmC0gva842pRHC/R7qWvFj3JP7xA/O38ODuP6ZFWwrUYm2VW6 8vII6UHJnt6jwqUOhfZPuCpd+d8QEbfN6R4cMvqc= X-X-Sender: talbert@bear.techie.net User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="-2033333575-219163072-1563993894=:7008" X-Mailing-List: archive/latest/17024 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/alpine.DEB.2.21.1907241441050.7008@bear.techie.net Approved: robomod@news.nic.it Lines: 52 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-python@lists.debian.org X-Original-Date: Wed, 24 Jul 2019 14:44:54 -0400 (EDT) X-Original-Message-ID: X-Original-References: <20190724190350.39776cb6@sylvester.codehelp> Xref: csiph.com linux.debian.maint.python:11529 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-219163072-1563993894=:7008 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Wed, 24 Jul 2019, Neil Williams wrote: >>> 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. Assuming python 2 is removed from bullseye, upon an upgrade from buster to bullseye, I guess we are assuming python 2 would remain installed on upgraded systems? Scott ---2033333575-219163072-1563993894=:7008--