removing a hook from snap/hooks does not remove it from prime/snap/hooks
Metadata
Current evaluation
Snapcraft bug: deleting a hook from snap/hooks/ does not remove the stale copy from prime/snap/hooks/, so the hook still ships in the package after a rebuild. Open ~5.5 years, zero comments, no labels, no maintainer response.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and zero comments from ~ogra or any maintainer over 2018 days, so it has never been assessed. It is a genuine bug report (stale hook file shipped in the package), not a support question, but I could not verify via code inspection whether the prime-directory sync logic still has this gap, so it needs a maintainer to confirm reproducibility on a current snapcraft before deciding to fix or close.
Impact:
40
Quick Win:
22.0
Staleness:
85
Complexity:
45
Confidence:
55
Support Request:
5
Issue body
while code changes to snap/hooks/* are properly propagated to the prime directory, the removal of a hook is not ...
i.e. removing snap/hooks/configure leaves prime/snap/hooks/configure in place. re-running snapcraft --destructive-mode in a container after removing a hook just ends up with the hook still being in the package that way.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
40
Quick Win:
22.0
Staleness:
85
Complexity:
45
Confidence:
55
Support Request:
5
|
needs triage | Snapcraft bug: deleting a hook from snap/hooks/ does not remove the stale copy from prime/snap/hooks/, so the hook still ships in the package after a rebuild. Open ~5.5 years, zero comments, no labels, no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
85
Support Request:
10
|
close stale | Snapcraft bug where removing a hook from snap/hooks/ does not update prime/snap/hooks/ on rebuild. The issue has been open for over 5 years with zero maintainer comments or labels. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
10
|
needs triage | Bug where removing a hook from snap/hooks/ fails to delete it from prime/snap/hooks/ during snapcraft builds. Issue remains open with no maintainer response or activity for over five years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Bug in snapcraft where deleting a hook file from snap/hooks/ fails to remove it from the prime directory during builds. Issue is over 5 years old with no maintainer interaction or updates. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
40
Confidence:
85
Support Request:
5
|
close stale | Bug where removing a hook from snap/hooks fails to delete it from prime/snap/hooks during snapcraft builds, leaving stale hooks in the package. Open, unassigned, no comments, inactive for over five years. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1865167 Removing a hook script and building, script still present | snapcraft (launchpad) | open | Snapcraft retains a deleted snap/hooks script in the rebuilt snap because the stale copy in prime/ is never removed; a full clean is required. Open ~6.5 years with zero comments, no labels, and no maintainer response. | |
| #1912540 rebuilding a part that generates hooks does not update the hook in prime/snap/... | snapcraft (launchpad) | closed | Abandoned due to inactivity, the dump plugin bug was closed without resolution. Changing source files in dump parts does not update prime outputs, requiring a full clean rebuild. | |
| #1746403 snapcraft fails to find hooks if ran from snap directory. | snapcraft (launchpad) | open | 2017 report: running snapcraft from the snap/ directory builds without error but omits hooks, causing confusing install failures; proposes enforcing project-root CWD. No maintainer activity in 8+ years; likely obsolete after the core22 rewrite. |