Issues while validating snapcraft.yaml: None is not of type 'string'

Bug #1524663 reported by XiaoGuo, Liu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Fix Released
Low
Kyle Fazzari

Bug Description

I have an example project based on the code snippet in the document of "
Snappy Ubuntu Core - Application Developer Manual 15.04". My project is located at:

https://github.com/liu-xiao-guo/null

snapcraft.yaml

parts:
  example-part:
    plugin: null
    stage-packages:
      - gpg
      - wget
    organize:
      opt/bin: bin
    filesets:
      binaries:
       - bin/*
       - usr/bin/*
      headers:
       - *.h
       - -include
    stage:
      - $binaries
      - test/bin/test_app
      - $headers
    snap:
      - $binaries

There are a few bugs related to the project:

1) - *.h gives me the following error:
Issues while validating snapcraft.yaml: expected alphabetic or numeric character, but found '.' on line 20 of snapcraft.yaml

2) If I take out the above line, I come out the following error:
Issues while validating snapcraft.yaml: None is not of type 'string'

3) By the way, I do not fully understand what the "oganize" mean in such a context. the explanation in the document is very weak.

I do not have any clue about the error. By the way, I have changed the "type" in the document to "plugin". However, the errors are the same.

Thanks & best regards,
XiaoGuo

description: updated
Revision history for this message
Daniel Holbach (dholbach) wrote :

I pushed a pull request which makes the example work (https://github.com/liu-xiao-guo/null/pull/1/files), but it was hard to debug because snapcraft's error message didn't reveal anything. :-/

Revision history for this message
Sergio Schvezov (sergiusens) wrote :

This bug is too broad. Usually a 'btw' is an indication of the need for another bug.

Most of the previous errors are from writing improper yaml.

Changed in snapcraft:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Sergio Schvezov (sergiusens) wrote :

Solve by making the error point to the yaml specification.

Changed in snapcraft:
milestone: none → 2.2
Revision history for this message
Kyle Fazzari (kyrofa) wrote :
Changed in snapcraft:
status: Triaged → In Progress
assignee: nobody → Kyle Fazzari (kyrofa)
Kyle Fazzari (kyrofa)
Changed in snapcraft:
status: In Progress → Fix Committed
Changed in snapcraft:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.