← Back to issue list

where does the python3 symlink come from?

View original Github issue

Metadata

Project
rockcraft
Number
#401
Type
issue
State
open
Author
cjdcordeiro
Labels
—
Created
Updated
Closed
—

Current evaluation

Question about why the python3 symlink appears when installing the python3.8-venv stage package but not python3.8 alone. Open since ~2022 with no maintainer response or labels; a later spread test documents the symlink as expected behavior from a python3.8-venv dependency.

Suggested action: needs triage

Reason: The issue is a maintainer's own open question (no labels, no comments, no assignee) with no resolution recorded, so it has not been triaged. However, a later spread test (tests/spread/rockcraft/plugin-python3-less) explicitly documents that the python3 symlink is 'brought in by a python3.8-venv dependency', suggesting the behavior is understood and expected, which may make this a candidate for close_not_a_bug once a maintainer confirms.

Impact: 30 Quick Win: 18.0 Staleness: 75 Complexity: 40 Confidence: 60 Support Request: 55

Issue body

### Bug Description When installing the stage package `python3.8-venv`, the `python3` symlink will be set (even though it is not a part of that package). OTOH, if installing `python3.8` instead (which is a dependency on `python3.8-venv`), that symlink won't be there. I can't put my finger on where that symlink comes from, but since these are stage packages, it shouldn't be from the maintainer scripts. Plus, the fact that the symlink is there for the former pkg but not the latter, is also concerning ### To Reproduce Pack the rock. First with the yaml provided below. Then change `python3.8-venv` to `python3.8`, and pack again ### Environment Latest rockcraft ### rockcraft.yaml ```shell name: app base: ubuntu@20.04 version: '0.1' summary: rock description: | some rock license: GPL-3.0 platforms: amd64: parts: python-flask: plugin: nil stage-packages: - python3.8-venv ``` ### Relevant log output ```shell n/a ```

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18.0
Staleness: 75
Complexity: 40
Confidence: 60
Support Request: 55
needs triage Question about why the python3 symlink appears when installing the python3.8-venv stage package but not python3.8 alone. Open since ~2022 with no maintainer response or labels; a later spread test documents the symlink as expected behavior from a python3.8-venv dependency.
qwen/qwen3.6-35b-a3b
Staleness: 92
Complexity: 20
Confidence: 80
Support Request: 85
close not a bug Investigates unexpected python3 symlink creation when staging python3.8-venv in rockcraft. Unlabelled, zero comments, inactive for over two years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 40
Confidence: 85
Support Request: 20
close stale Investigating unexpected python3 symlink creation when staging python3.8-venv in rockcraft. Unlabelled, zero maintainer comments, and inactive for over two years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 90
Complexity: 35
Confidence: 85
Support Request: 70
close stale Investigates unexpected creation of a python3 symlink when staging python3.8-venv instead of python3.8. Unanswered for over two years with zero maintainer interaction.
qwen3.6-35b-a3b-mtp-q6
Staleness: 88
Complexity: 25
Confidence: 75
Support Request: 45
close stale Unexpected python3 symlink created when staging python3.8-venv in Rockcraft, but absent when staging python3.8. Symlink origin is unknown. Issue remains open, unassigned, and untriaged, awaiting investigation.

Update history

No update history recorded yet.

Related work

  • Related To: rockcraft#1021 (confidence 55%)

    Commit 3266ca40 (test(spread): fix python3.6 test, #1021) added the plugin-python3-less spread test whose yaml comment states the python3 symlink is 'brought in by a python3.8-venv dependency', directly addressing the question in this issue.

Related issues

No related issues found above the similarity threshold.