[Starlingx-discuss] Upcoming removal of pip's legacy resolver

Scott Little scott.little at windriver.com
Wed Mar 9 16:24:07 UTC 2022


Thanks for the heads up Jeremy

I've scanned the current master branch code base an fount the following 
hits.
All are found in 'tox.ini' files.  We can expect...
- Build failures due to failed unit tests
- Zuul to vote -q on code reviews in some repos

Most commit messages acknowledge that the use of '--use-deprecated 
legacy-resolver'
is a quick fix, and that followup will be required to deal with 
dependency conflicts.


Raised Launchpad: https://bugs.launchpad.net/starlingx/+bug/1964372

List of offenders:

cgcs-root/stx/integ/tox.ini
# pylint zuul jobs are failing due to incompatible dependencies that 
cause the new version of pip to abort.
# Sha: c13cf2a27d84413887e58a3b63144812b7e7ad35
# Related-Bug: 1907125

cgcs-root/stx/audit-armada-app/python-k8sapp-auditd/k8sapp_auditd/tox.ini
# day one
# Sha: b486699ea96974efc08a8b858d70e66a9710029a
# Story: 2008849
# Task: 42988

cgcs-root/stx/openstack-armada-app/python-k8sapp-openstack/k8sapp_openstack/tox.ini
# introduced as part of python 3.9 support,
# Sha: 79fdbd4dde6b2dc05a1b2585f037f8519bd0a785
# Story: 2071901
# Task: 43189

cgcs-root/stx/platform-armada-app/python-k8sapp-platform/k8sapp_platform/tox.ini
# Quick fix for a new version of pip, Dec 3, 2020.
# Sha: 086a81deea855d51c65d70cc2288a266d671b9b4
# Story: 2008162
# Task: 41347
# Related-Bug: #1907125

cgcs-root/stx/portieris-armada-app/python-k8sapp-portieris/k8sapp_portieris/tox.ini
# introduced as part of python 3.9 support,
# Sha: b6dab011137beb645d9bdfcfd6ac991601489658
# Story: 2009101
# Task: 43187

cgcs-root/stx/ptp-notification-armada-app/python-k8sapp-ptp-notification/k8sapp_ptp_notification/tox.ini
# introduced as part of python 3.9 support,
# Sha: 26fff85a2fcb0fb34e793b22dd432c4a0cd58507
# Story: 2006796
# Task: 43227

cgcs-root/stx/snmp-armada-app/python-k8sapp-snmp/k8sapp_snmp/tox.ini
# introduced as part of python 3.9 support,
# Sha: 386b5daa15906676338bb27ce269f2578e6add00
# Story: 2006796
# Task: 43208

cgcs-root/stx/vault-armada-app/python-k8sapp-vault/k8sapp_vault/tox.ini
# introduced as part of python 3.9 support,
# Sha: 92ec55097cdf27d824da6912673e352b2a0c6680
# Story: 2006796
# Task: 43225

Scott



On 2022-03-07 07:49, Jeremy Stanley wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> The pip maintainers are starting the information gathering phase to
> determine whether removal of its old non-coherent dependency
> management model can be removed in an upcoming release. I see from a
> quick search[*] that a number of StarlingX test environments rely on
> `pip install --use-deprecated legacy-resolver ...` for their tox
> install_command. You'll want to prepare for contingency solutions,
> or provide feedback[**] to the pip maintainers if there's something
> broken about the new dep solver which is preventing use of it.
>
> [*] https://codesearch.opendev.org/?q=use-deprecated
> [**] https://discuss.python.org/t/14099
> --
> Jeremy Stanley
>
> _______________________________________________
> Starlingx-discuss mailing list
> Starlingx-discuss at lists.starlingx.io
> http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss





More information about the Starlingx-discuss mailing list