← Back to issue list

snapcraft whoami fails if run in a place with recipe using base: core

View original Launchpad issue

Metadata

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

Current evaluation

Closed without resolution or fix. The snapcraft whoami command incorrectly parsed snapcraft.yaml and failed on outdated base: core configurations. The issue was abandoned after 513 days with no comments or patches.

Suggested action:

No scores available.

Issue body

snapcraft does not show "whoami" info in there is a snapcraft.yaml with "base: core" in the directory: $ grep base snapcraft.yaml base: core $ snapcraft whoami Base 'core' is not supported by this version of Snapcraft. Recommended resolution: Use Snapcraft 4 from the '4.x' channel of snapcraft where 'core' was last supported. This command should not need to look at snapcraft.yaml afaiu.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without resolution or fix. The snapcraft whoami command incorrectly parsed snapcraft.yaml and failed on outdated base: core configurations. The issue was abandoned after 513 days with no comments or patches.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 85
Support Request: 10
needs triage snapcraft whoami fails with a base compatibility error when run in a directory containing a snapcraft.yaml with the deprecated base: core. Issue is unlabelled, has no maintainer interaction, and has been inactive for over 16 months.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 20
Confidence: 90
Support Request: 10
close stale snapcraft whoami fails with 'base: core' error. Issue is 489 days old, no activity, and suggests using Snapcraft 4. Clearly outdated for current versions.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 70
Support Request: 5
needs triage snapcraft whoami command fails when run in a directory containing a snapcraft.yaml with the deprecated base: core, incorrectly parsing the config file instead of just returning user info.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 15
Confidence: 85
Support Request: 5
close stale snapcraft whoami fails when a snapcraft.yaml with the deprecated base: core is present. Issue is inactive for over a year with no maintainer response.

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.
74%
#1611436 Snapcraft is missing whoami command snapcraft (launchpad) closed Feature request for a whoami command was closed without implementation. With zero comments and no linked pull request, the request was abandoned.
73%
#1803776 snapcraft init missing a base snapcraft (launchpad) closed Closed without resolution. The base requirement for snapcraft init was later implemented in subsequent releases, superseding this report.
72%
#1857019 cannot build snapd snap with build-base: core w/o base: core snapcraft (launchpad) closed Closed without resolution or comments. The snapcraft TypeError when using build-base: core without base: core remains unresolved.
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.
71%
#2099923 Snapcraft builds are failing: install of snap "snapcraft" failed snapcraft (launchpad) open Snapcraft builds failing due to outdated snapd (2.61) on build infrastructure unable to install core20 base. Issue is 556 days old with no maintainer response.
70%
#1869542 snapcraft unable to find snap/snapcraft.yaml file snapcraft (launchpad) open snapcraft 3.11 (2019) loses snap/snapcraft.yaml after a few builds and drops to the VM shell; workaround is snapcraft clean. 6+ years old, no labels, no maintainer comments, tied to a long-superseded build environment.
70%