← Back to issue list

Noisy output in newest charmcraft

View original Github issue

Metadata

Project
charmcraft
Number
#2006
Type
issue
State
open
Author
dimaqq
Labels
Created
Updated
Closed

Current evaluation

Charmcraft 3.2.2 build logs a pip cache permission warning ('/root/.cache/pip not owned or writable') during dependency install; reporter notes it appears under --verbose and hints at a real cache/permission issue. No maintainer response; last activity 381 days ago.

Suggested action: needs triage

Reason: No maintainer has acknowledged, labelled, or responded to this issue (only the reporter's own follow-up comment), so it remains untriaged. The underlying concern is plausible: the codebase has since added explicit handling to ensure /root/.cache exists (commits 9cc16dc5 'fix(provider): ensure /root/.cache exists (#2134)' and ca66a94c '#2140'), suggesting the cache-permission problem was real and addressed in later versions, but no commit or PR explicitly references this issue, so a human should confirm whether the fix resolves it before closing.

Impact: 30 Quick Win: 18.0 Staleness: 70 Complexity: 40 Confidence: 55 Support Request: 10

Issue body

### Bug Description Building https://github.com/jnsgruk/hello-kubecon in CI, there's for example this: ``` Installing dependencies :: Running external command ['python3', '-m', 'venv', '/root/parts/charm/build/staging-venv'] :: Running external command ['/root/parts/charm/build/staging-venv/bin/pip', 'install', '--force-reinstall', 'pip@https://files.pythonhosted.org/packages/c0/d0/9641dc7b05877874c6418f8034ddefc809495e65caa14d38c7551cd114bb/pip-24.1.1.tar.gz'] :: :: WARNING: The directory '/root/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag. ``` https://github.com/canonical/operator/actions/runs/12045070299/job/33583075577?pr=1461 ### To Reproduce build a charm using charmcraft 3.2.2 ### Environment CI, so amd64, charmcraft 3.2.2, targeting 20.04 I believe. ### charmcraft.yaml ```yaml ... ``` ### Relevant log output ```shell ... ```

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 30
Quick Win: 18.0
Staleness: 70
Complexity: 40
Confidence: 55
Support Request: 10
needs triage Charmcraft 3.2.2 build logs a pip cache permission warning ('/root/.cache/pip not owned or writable') during dependency install; reporter notes it appears under --verbose and hints at a real cache/permission issue. No maintainer response; last activity 381 days ago.
qwen/qwen3.6-35b-a3b
Staleness: 85
Complexity: 30
Confidence: 70
Support Request: 10
needs triage Reports noisy pip cache permission warnings during charm builds with charmcraft 3.2.2. Unlabelled, no maintainer response, inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 70
Support Request: 30
close stale Report of noisy pip cache permission warnings during verbose charm builds in CI using charmcraft 3.2.2. Unlabelled and inactive for over a year with no maintainer response.
qwen3.6-35b-a3b-mtp-q6
Staleness: 92
Complexity: 15
Confidence: 80
Support Request: 10
needs triage Report of noisy CI output and pip cache warnings during charm builds with charmcraft 3.2.2. Issue remains unlabelled, lacks maintainer response, and has been inactive for over 300 days.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 65
Support Request: 35
needs triage Reports noisy pip cache permission warnings and excessive verbose output in charmcraft 3.2.2 builds. Stale for over a year with no labels or recent activity. Needs triage to investigate whether the warnings signal a deeper caching or permission bug.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/charmcraft#2134 (confidence 60%)

    Commit 9cc16dc5 'fix(provider): ensure /root/.cache exists' directly addresses the /root/.cache permission/ownership problem that triggers the pip warning in this issue.

  • Related To: canonical/charmcraft#2046 (confidence 50%)

    Commit 73a7996a 'fix: use the same cache directory in providers' relates to how the cache directory is set up in build providers, the same area implicated by the warning.

Related issues

Issue Project State Summary Similarity
#1374 pip wheel cache ignored charmcraft closed Fixed in charmcraft 2.5.4 by updating pip to version 23+, resolving the wheel cache issue caused by pip 22's --no-binary handling. Verified by the reporter and closed.
72%