snappy build does odd things with poorly formed /meta/package.yaml

Bug #1459212 reported by Rick Spencer on 2015-05-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snappy
Medium
Michael Vogt

Bug Description

Steps:

1. branch this project https://code.launchpad.net/~rick-rickspencer3/+junk/go-template
2. follow the instructions in meta/readme, but start with "build for each arch" (i.e. don't edit the package.yaml file
3. after running snappy build note that the snap package is built, even though the package.yaml has no name

effect:
packages are named _version_.snap

expected:
the snap build command rejects the invocation and directs the user to name the project

Also note that the command accepts a name with a space and then includes the space in the package name, though I do not know if this is a bug or by design

Related branches

description: updated
Michael Vogt (mvo) on 2015-05-27
Changed in snappy:
status: New → Confirmed
importance: Undecided → Medium
Michael Vogt (mvo) on 2015-05-29
Changed in snappy:
status: Confirmed → In Progress
Changed in snappy:
assignee: nobody → Michael Vogt (mvo)
Michael Terry (mterry) on 2015-06-18
Changed in snappy:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers