← Back to issue list

snap contains python 3.8 and 3.9 libs

View original Launchpad issue

Metadata

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

Current evaluation

Snapcraft 2.x-era report that a built snap bundles both python3.8 and python3.9, causing librsync to fail on the 3.9 interpreter. Unlabelled, zero comments, inactive ~4.4 years; the python plugin was since rewritten to a venv-based design in Snapcraft 3.x.

Suggested action: close stale

Reason: The report is from the Snapcraft 2.x era (1624 days old, 0 comments, no labels/assignee) and describes the old stage-packages-based python plugin bundling the build environment's system python alongside the base's. The current codebase's PythonPlugin (snapcraft/parts/plugins/python_plugin.py) subclasses craft_parts' venv-based python_plugin and no longer stages a system interpreter, so the two-conflicting-system-pythons symptom is no longer reproducible on a supported base. Inactivity alone is not the basis; the specific mechanism has been replaced.

Impact: 35 Quick Win: 15.75 Staleness: 92 Complexity: 55 Confidence: 62 Support Request: 25

Issue body

Using the attached snapcraft.yaml, snap builds with conflicting libs: $ find /snap/duplicity/current/ -type d -name 'python3*' <snip> /snap/duplicity/current/usr/lib/python3 /snap/duplicity/current/usr/lib/python3.8 <-- this should be here **** /snap/duplicity/current/usr/lib/python3.9 <-- this one causes confusion **** <snip> Since duplicity uses _librsync*.so and that's only installed in python3.8, it fails when python 3.9 is used, as is done on Debian 10. It's only one executable and should only have one version of python supplied in the snap.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 15.75
Staleness: 92
Complexity: 55
Confidence: 62
Support Request: 25
close stale Snapcraft 2.x-era report that a built snap bundles both python3.8 and python3.9, causing librsync to fail on the 3.9 interpreter. Unlabelled, zero comments, inactive ~4.4 years; the python plugin was since rewritten to a venv-based design in Snapcraft 3.x.
qwen/qwen3.6-35b-a3b
Staleness: 98
Complexity: 45
Confidence: 90
Support Request: 20
close stale Snapcraft build includes conflicting Python 3.8 and 3.9 libraries, causing runtime failures on Python 3.9 systems. Unlabelled, no maintainer response, inactive for over 4 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 35
Confidence: 85
Support Request: 20
close stale Snapcraft build includes conflicting Python 3.8 and 3.9 libraries, causing runtime failures on systems using Python 3.9. Issue remains unresolved after over four years with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 40
Confidence: 75
Support Request: 20
close stale Snapcraft build includes conflicting Python 3.8 and 3.9 libraries, causing runtime failures when the wrong version is selected. Issue remains unaddressed for over four years with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 35
Confidence: 85
Support Request: 30
close stale Snap build includes conflicting Python 3.8 and 3.9 libraries, causing runtime failures. Issue is over 4 years old with no maintainer response or updates.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft/snapcraft#4044 (confidence 55%)

    Commit 302e58eeb 'plugins: add snapcraft specific python plugin (#4044)' and the venv-based craft-parts rewrite changed how python is bundled, superseding the stage-packages behavior described here.

Related issues

No related issues found above the similarity threshold.