← Back to issue list

snapcraft clean <part> doesn't remove the bin/ directory

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1591056
Type
issue
State
closed
Author
~elopio
Labels
clean
Created
Updated
Closed

Current evaluation

Reported that `snapcraft clean <part>` left an empty parts/<part>/bin dir behind. Maintainer confirmed fixed in master (via the pkg-config rework), verified the part dir is fully removed, and closed after the snapcraft.io tour was updated.

Resolution: closed resolved

Reason: Maintainer ~elopio confirmed in July 2016 that the bug was fixed in master (not yet released to xenial), demonstrating `snapcraft clean gnu-bash` removes parts/gnu-bash/ entirely; the issue was closed on 2016-09-02 once the snapcraft.io tour was updated.

Evaluated by: mr-cal-bot

No scores available.

Issue body

snapcraft clean <part> doesn't remove the bin/ directory from this part. $ snapcraft clean gnu-bash $ ls parts/gnu-bash/ bin -> I would completely remove parts/gnu-bash directory and its content, as if the part wasn't pulled or anything. Indeed, it would be weird to have a potentially empty parts/gnu-bash/ directory, especially if we rename one part.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Reported that `snapcraft clean <part>` left an empty parts/<part>/bin dir behind. Maintainer confirmed fixed in master (via the pkg-config rework), verified the part dir is fully removed, and closed after the snapcraft.io tour was updated.
stealth/space-bunny-alpha — closed resolved Fixed in master: snapcraft clean <part> now removes the entire parts/<part> directory, including bin/. The fix was not yet available in the Xenial release.
stealth/space-bunny-alpha — closed stale Closed as stale after more than 10 years without a documented fix; no resolving PR or release was identified.
qwen/qwen3.6-35b-a3b — — The bug where snapcraft clean <part> leaves the bin/ directory behind was abandoned and closed without resolution. No fix was implemented or merged, likely due to prolonged inactivity.
qwen/qwen3.6-35b-a3b — — The snapcraft clean command failing to remove the bin directory was closed without resolution or comments, indicating it was abandoned. No fix or merge was implemented.

Update history

Date Change
created

Related work

  • Related To: snapcraft#421 (confidence 35%)

    Likely the pkg-config rework commits that stopped creating a bin/ directory during clean

Related issues

Issue Project State Summary Similarity
#1690139 "snapcraft clean <part>" fails if the files I asked it to clean don't exist snapcraft (launchpad) closed Closed after a maintainer reported that `snapcraft clean` works as expected; no resolving PR or commit was cited.
74%
#1734145 snapcraft clean <part-name> destroys everything when using containers snapcraft (launchpad) closed Fixed targeted container cleanup: `snapcraft clean <part>` no longer deletes the LXD container while other parts remain; merged in #1762 (dbce9a058).
73%
#1497371 snapcraft clean fails on a clean directory snapcraft (launchpad) closed The missing parts-directory crash in #1497371 was closed without a documented fixing PR, commit, release, or maintainer explanation.
71%