snappy build generates invalid package.yaml when using preinstalled section
Bug #1511050 reported by
Simon Eisenmann
on 2015-10-28
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Snappy |
Undecided
|
Unassigned | ||
Bug Description
When building an OEM package with a package yaml containing a preinstalled section, the resulting snap contains a package.yaml file which was modified and is invalid. In the file inside the snap the preinstalled section was replaced with builtin section and the difference in bytes was added as bogus bytes to the end of the yaml file making it invalid.
| Simon Eisenmann (longsleep) wrote : | #1 |
| Simon Eisenmann (longsleep) wrote : | #2 |
It seems that the issue does not appear when both preinstalled and built-in sections are present.
| Michael Vogt (mvo) wrote : | #3 |
There is no snappy build anymore in snappy 16 anymore. This is now done via "snapcraft snap <directory>". Please reopen against snapcraft if you still see the issue there.
| Changed in snappy: | |
| status: | New → Invalid |
To post a comment you must log in.
We see this issue with ubuntu-snappy-cli installed on wily and vivid (1.5ubuntu1).