snap contains python 3.8 and 3.9 libs
Metadata
Current evaluation
A core20 build staged Python 3.8 and 3.9 files; Duplicity added a packaging workaround, but the underlying Snapcraft conflict and potential side effects remain unresolved.
Suggested action: keep open
Reason: The reporter explicitly says the Duplicity workaround does not address the underlying Snapcraft bug or establish its side effects. No Snapcraft commit resolves the primitive-package provenance problem, and reproducing it requires the missing YAML plus compatible core20 tooling and base packages.
Evaluated by: mr-cal-bot
Impact:
58
Quick Win:
8
Complexity:
68
Confidence:
79
Actionability:
45
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 |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
8
Complexity:
68
Confidence:
79
Actionability:
45
|
keep open | A core20 build staged Python 3.8 and 3.9 files; Duplicity added a packaging workaround, but the underlying Snapcraft conflict and potential side effects remain unresolved. | |
| stealth/space-bunny-alpha |
Impact:
57
Quick Win:
10
Complexity:
73
Confidence:
86
Actionability:
67
|
needs triage | Duplicity's snap stages both Python 3.8 and 3.9 libraries. Duplicity MR !83 removes Python 3.9 as a workaround, while the possible underlying Snapcraft staging issue remains untriaged. | |
| stealth/space-bunny-alpha |
Impact:
58
Quick Win:
14
Complexity:
43
Confidence:
58
Actionability:
42
|
needs triage | Duplicity snaps reportedly bundle Python 3.8 and 3.9; librsync is only in 3.8, so the executable may select the incompatible 3.9 library. The attached recipe is unavailable. | |
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
16
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. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Related To:
snapcraft (launchpad)#1956157
(confidence 98%)
The reporter explicitly identifies this earlier Dropbox msgpack problem as a possible recurrence of the same multi-library conflict.
Related issues
No related issues found above the similarity threshold.