← Back to issue list

snapcraft snap <directory> fails due to looking for package.yaml

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1541987
Type
issue
State
closed
Author
~kyrofa
Labels
—
Created
Updated
Closed

Current evaluation

Bug fixed in merged PR ubuntu-core/snapcraft#297 (commit 53236ee): `snapcraft snap <directory>` now looks for snap.yaml instead of the obsolete package.yaml.

Resolution: closed resolved

Reason: Maintainer ~kyrofa commented linking the fix at https://github.com/ubuntu-core/snapcraft/pull/297, which changed the snap command to look for snap.yaml rather than package.yaml, and the Launchpad bug was closed.

Evaluated by: mr-cal-bot

No scores available.

Issue body

And Snappy and Snapcraft has moved to using snap.yaml. To reproduce: 1. Choose one of the example snaps. 2. Create the snap via `snapcraft snap`. 3. Create the snap again via `snapcraft snap snap`, running on its own output. Notice the failure complaining about the lack of package.yaml.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Bug fixed in merged PR ubuntu-core/snapcraft#297 (commit 53236ee): `snapcraft snap <directory>` now looks for snap.yaml instead of the obsolete package.yaml.
stealth/space-bunny-alpha — closed resolved Fixed in merged PR #297 (commit 53236ee27): `snapcraft snap <directory>` now looks for snap.yaml instead of the obsolete package.yaml, fixing LP bug #1541987.
stealth/space-bunny-alpha — closed resolved Fixed by merged canonical/snapcraft#297, which made directory-based snapping look for snap.yaml instead of package.yaml (merge commit 53236ee27).
qwen/qwen3.6-35b-a3b — — Superseded by Snapcraft's migration from package.yaml to snap.yaml. The format change resolved the lookup failure, rendering the report obsolete.
qwen/qwen3.6-35b-a3b — — Closed as superseded. Snapcraft migrated to snap.yaml, eliminating the package.yaml dependency and resolving the directory build failure.
qwen3.6-35b-a3b-mtp-q6 — — Closed as obsolete after Snapcraft migrated from package.yaml to snap.yaml. The directory build failure was resolved by the upstream format change.

Update history

Date Change
created

Related work

  • Likely Fixed By: ubuntu-core/snapcraft#297 (confidence 95%)

    PR linked by maintainer kyrofa in the closing comment; commit 53236ee switches the snap command to snap.yaml.

Related issues

Issue Project State Summary Similarity
#297 Snap: When snapping a directory, look for snap.yaml. snapcraft merged Directory-based snap packaging now finds snap.yaml; #297 merged via 53236ee27, fixing LP #1541987.
78%
#4769 snapcraft 8.2.1: `snapcraft pack` not respecting `<directory>` arg to find `snapcraft.yaml` snapcraft closed Fixed in Snapcraft 8.2.6 by PR #4794 (commit 48483c4e3), restoring project-file lookup for snapcraft pack <directory>; the reporter confirmed the fix.
77%
#1604326 snapcraft init doesn't fail if there is a .snapcraft.yaml file snapcraft (launchpad) closed Fixed by merged snapcraft#669 (commit 2cd727259): snapcraft init now detects an existing .snapcraft.yaml and fails instead of creating snapcraft.yaml.
71%
#1717413 snapcraft snap with an unexisting dir shows a traceback snapcraft (launchpad) closed Missing-directory handling was fixed to return a clear SnapcraftEnvironmentError instead of a traceback; Launchpad bug #1717413 is closed as Fixed.
71%