← Back to issue list

snapcraft first run doesn't verify parts in parts after keyword on core22

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#2033882
Type
issue
State
closed
Author
~gbeuzeboc
Labels
Created
Updated
Closed

Current evaluation

⚠️ This summary may be outdated — the issue content or evaluation prompts have changed since this evaluation was made.

Closed without resolution. Snapcraft fails to validate non-existent parts in the after keyword on core22, a regression from core20, remains unaddressed.

Suggested action:

No scores available.

Issue body

When listing parts in the after keyword of a part, if the listed part doesn't exist, no error will show. In core20 it was showing an error but not in core22. I believe it should show an error to help developers with potential typos. Example to reproduce: snapcraft.yaml: name: my-snap-name base: core22 version: '0.1' summary: Single-line elevator pitch description: | This is my-snap's description. grade: devel confinement: devmode parts: my-part: plugin: nil override-build: | echo "hello" my-part2: after: [trololo] plugin: nil override-build: | echo "hello" The first build runs fine. The second build properly fails. While the same example in core20 always gives: Failed to get part information: Cannot find the definition for part 'trololo', required by part 'my-part2'. Remote parts are not supported with bases, so make sure that this part is defined in the `snapcraft.yaml`.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without resolution. Snapcraft fails to validate non-existent parts in the after keyword on core22, a regression from core20, remains unaddressed.
qwen/qwen3.6-35b-a3b Closed without resolution. The reported snapcraft core22 validation bug for missing parts in the after keyword was not fixed. The report remains abandoned with no patches implemented.
qwen3.6-35b-a3b-mtp-q6 Closed without resolution due to inactivity. The core22 snapcraft validation for non-existent parts in the after keyword remains unaddressed.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1939713 snapcraft init create base: core18 snap snapcraft (launchpad) closed Closed without direct resolution, likely abandoned due to inactivity. Subsequent Snapcraft releases updated the init default to core20 and core22, effectively resolving the reported behavior.
73%
#5634 Core22 unit tests in snapcraft fails with craft application 5.5.0 snapcraft closed Closed and deferred. The core22 test failure was traced to a validation change in craft-application PR #812. The issue was logged internally as SNAPCRAFT-1188 for tracking.
72%
#2019931 snapcraft is ignoring the "assumes" section snapcraft (launchpad) closed Bug report indicating snapcraft omits the assumes section from snap.yaml when using core22 base. Closed after two days with zero comments, indicating the report was abandoned without resolution.
72%
#1741140 wrong error when a part depends on a part with underscore snapcraft (launchpad) open Snapcraft reports a misleading validation error: when a part's after/before dependency uses an underscore (invalid part name), the error names the valid depending part instead of the invalid dependency. Open since 2017 with no maintainer activity; no fix found in current craft-parts/snapcraft validation code.
72%
#1660696 Snapcraft is testing file collisions on unbuilt parts snapcraft (launchpad) closed Closed without a merged fix. Snapcraft incorrectly checked file collisions on unbuilt parts, causing file not found errors. The author verified a local workaround, but the report was closed without upstream resolution or discussion.
71%
#1842328 snapcraft make plugin does not support core20 snapcraft (launchpad) closed Closed without resolution or comments, likely abandoned. The core20 support gap for the snapcraft make plugin remains unresolved.
71%
#1990550 snapcraft init creates boilerplate which opaquely fails to build by default snapcraft (launchpad) closed Closed without resolution. The report recommended updating snapcraft init to default to core22 instead of core20, preventing opaque build failures and CLI mismatches. No fix or pull request was submitted, leaving the request abandoned.
71%
#1897337 snapcraft build <part> ignores the part snapcraft (launchpad) closed The snapcraft build command ignoring specified parts was closed without a fix or resolution. No comments or patches were provided, indicating the report was abandoned without addressing the filtering behavior.
71%
#1978844 snapcraft try not available for core22-based snap snapcraft (launchpad) closed Closed without resolution or comments. The snapcraft try command remains unavailable for core22-based snaps, with attempts failing or falling back to legacy implementations.
71%
#1826753 Snapcraft should complain multiple `after` properties in a single part snapcraft (launchpad) open Request for snapcraft to error on duplicate 'after' YAML keys in a part definition. 7+ years old, zero comments, no labels, no maintainer interaction. References snapcraftctl and old part format that no longer exist in modern snapcraft.
71%