Allow using .snapcraft.yaml as input

Bug #1587933 reported by Sergio Schvezov
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sergio Schvezov
snapcraft (Ubuntu)

Bug Description


 * Allow using an alternate snapcraft.yaml which would be hidden (.snapcraft.yaml)

[Test Case]

 1. Running `snapcraft init` creates a snapcraft.yaml
 2. Running `snapcraft` creates a snap using snapcraft.yaml as a source
 3. Create a copy `cp snapcraft.yaml .snapcraft.yaml`
 4. Running `snapcraft` results in an error due to duplicate sources
 5. Remove snapcraft.yaml
 6. Running `snapcraft` creates a snap using .snapcraft.yaml as a source

[Regression Potential]

 * Existing projects can fail to run snapcraft if the logic to check duplicates fails. This should be heavily covered by unit and integration tests (all tests would fail today if the code changed in incompatible ways).

Changed in snapcraft:
status: New → Triaged
Changed in snapcraft:
milestone: none → 2.11
assignee: nobody → Sergio Schvezov (sergiusens)
Revision history for this message
Sergio Schvezov (sergiusens) wrote :
Changed in snapcraft:
status: Triaged → In Progress
Changed in snapcraft:
status: In Progress → Fix Committed
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Sergio, or anyone else affected,

Accepted snapcraft into xenial-proposed. The package will build now and be available at in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at . Thank you in advance!

tags: added: verification-needed
Revision history for this message
Leo Arias (elopio) wrote :

Tested in an up-to-date xenial:

- enabled -proposed
- updated snapcraft to 2.12
- made a .snapcraft.yaml
- snapcraft <- it works
- moved it to snapcraft.yaml
- snapcraft <- it works
- copied to .snapcraft.yaml
- snapcraft <- it fails with a nice error
- verified it doesn't show containers.
- rm snapcraft.yaml
- snapcraft <- it works
- rm .snapcraft.yaml
- snapcraft <- it fails with a nice error

I'm going to mark this as verified, thanks Steve!

tags: added: verification-done
removed: verification-needed
Changed in snapcraft:
status: Fix Committed → Fix Released
Revision history for this message
Chris J Arges (arges) wrote : Update Released

The verification of the Stable Release Update for snapcraft has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Mathew Hodson (mhodson)
affects: Ubuntu Xenial → snapcraft (Ubuntu Xenial)
Changed in snapcraft (Ubuntu Xenial):
importance: Undecided → Wishlist
status: New → Fix Released
Changed in snapcraft (Ubuntu Yakkety):
status: New → Fix Released
importance: Undecided → Wishlist
Changed in snapcraft (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers