← Back to issue list

Wrong version installed even when explicit

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1886717
Type
issue
State
open
Author
~kenneth-loafman
Labels
—
Created
Updated
Closed
—

Current evaluation

Reporter claims a pip3 system install ignored 'six>=1.12.0' and shipped 1.11.0 from base dist-packages; reporter self-closed in Feb 2022 saying it can no longer be reproduced.

Suggested action: close stale

Reason: The only substantive maintainer response (cjp256, 2020-07-08) attributes it to pip3 system install 'ignores the version requirement if the distribution package is already installed', and the reporter closed it themselves on 2022-02-16: 'Just closed this one. I can no longer confirm the issue.' The referenced code path is also gone from this tree — snapcraft/parts/plugins/python_plugin.py now just subclasses craft_parts' PythonPlugin and only overrides interpreter selection (snapcraft/parts/plugins/python_common.py), with no pip3 system-install logic. With the attached snapcraft.yaml, exact part definition, and a reproducer unavailable and declared unconfirmable by the author after 18 months, there is nothing actionable left; confidence is limited only because the tracker still shows the bug as open and no explicit closure event is visible.

Evaluated by: mr-cal-bot

Impact: 30 Quick Win: 4 Complexity: 45 Confidence: 70 Actionability: 22

Issue body

I've attached the snapcraft.yaml I'm using. As you can see, six is specified as six>=1.12.0. The problem is that /snap/duplicity/104/usr/lib/python3/dist-packages/six.py is at version 1.11.0, not >= 1.12.0. This sounds like it's coming from the Ubuntu repositories (woefully behind) instead of from the current pip offering, which is something like 1.14.0.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 30
Quick Win: 4
Complexity: 45
Confidence: 70
Actionability: 22
close stale Reporter claims a pip3 system install ignored 'six>=1.12.0' and shipped 1.11.0 from base dist-packages; reporter self-closed in Feb 2022 saying it can no longer be reproduced.
stealth/space-bunny-alpha
Impact: 38
Quick Win: 3
Complexity: 52
Confidence: 90
Actionability: 18
close stale A Python package version constraint was reportedly ignored during a legacy pip3 system install, but the reporter later closed it because the behavior could no longer be reproduced.
stealth/space-bunny-alpha
Impact: 42
Quick Win: 14
Complexity: 40
Confidence: 84
Actionability: 57
needs triage Python dependency resolution appears to ignore an explicit six>=1.12.0 constraint, leaving Ubuntu's six 1.11.0; this untriaged report needs a current supported-base reproduction.
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18
Staleness: 90
Complexity: 40
Confidence: 65
Support Request: 20
close stale Report from ~6 years ago that a duplicity snap built with snapcraft got six 1.11.0 from Ubuntu repos instead of six>=1.12.0 from PyPI. No labels, no comments, no maintainer response; affected snapcraft 2.x era is long gone.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 85
Support Request: 30
close stale Snapcraft installs an outdated 'six' package (1.11.0) instead of the specified >=1.12.0, likely pulling from Ubuntu repos. Issue has been inactive for over 4 years with no maintainer response.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 45
Confidence: 90
Support Request: 20
close stale Snapcraft packaging issue where an explicit six>=1.12.0 dependency resolves to an older Ubuntu repo version (1.11.0). Issue is six years old with no maintainer interaction or comments.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 30
Confidence: 85
Support Request: 20
close stale Report of incorrect Python six package version installed in a snap despite explicit version constraints in snapcraft.yaml. Issue has no maintainer comments and is over six years old.

Update history

Date Change
created

Related issues

No related issues found above the similarity threshold.