On 12/9/19 6:44 PM, Roger Oberholtzer wrote:
On Sat, Dec 7, 2019 at 1:21 AM Simon Lees
wrote: On 12/7/19 12:30 AM, Roger Oberholtzer wrote:
On Fri, Dec 6, 2019 at 1:29 PM Carlos E. R.
wrote: David idea is to provide it without security updates nor assurances. I would say in -deprecated-non-secure form.
I get that this will probably not happen. What I would like to see is a list of the packages that will go away when upstream support for Python2 goes away. That would allow one to decide if any of those packages need to be locked for local use. No fun getting a surprise that some package that one did not expect had a python2 dependency and was removed.
Yep its against openSUSE's policy to ship insecure software, there have been a number of packages dropped from tumbleweed because they are old and security bugs weren't being fixed.
"zypper rm python2" will give you the full list.
I get that this could tell what it claims to tell. But I do not believe that this is how packages to remove from OBS will be managed. After all, packages are not actually installed on OBS. So running a query against installed packages is probably not going to be how it is done.
Or do you mean that this command is what will be run on my system as part of a zypper dup, and that is how my local packages will actually be removed? EXACTLY that command?
I don't see what the problem is with publishing a list of the specific packages that will be removed from OBS.
It probably will be at the time, but it could still change from now, some stuff might get fixed, other stuff has already been removed over the last year so we won't know until then. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B