← Back to issue list

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

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1524663
Type
issue
State
closed
Author
~liu-xiao-guo
Labels
Created
Updated
Closed

Current evaluation

Closed without resolution. The report detailed snapcraft.yaml validation errors involving null plugins and file patterns. With zero comments and over a decade of inactivity, the issue was abandoned.

Suggested action:

No scores available.

Issue body

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

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Closed without resolution. The report detailed snapcraft.yaml validation errors involving null plugins and file patterns. With zero comments and over a decade of inactivity, the issue was abandoned.
qwen/qwen3.6-35b-a3b Closed without resolution or maintainer response. The issue reported snapcraft.yaml validation errors but received no comments or fixes, indicating it was abandoned due to prolonged inactivity.
qwen/qwen3.6-35b-a3b Closed without resolution or comments. The reported snapcraft.yaml validation errors were not addressed, indicating the issue was abandoned due to inactivity.
qwen3.6-35b-a3b-mtp-q6 Abandoned and closed without resolution. The reported snapcraft.yaml validation errors stem from outdated documentation or syntax changes. No fix or merge occurred.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#1697468 snapcraft doesn't validate plugs: values snapcraft (launchpad) open Request to add whitespace validation for plugs values in snapcraft.yaml (e.g. 'home x11' instead of 'home, x11'). Filed ~2015 during the build.snapcraft.io era, zero comments, no labels, no maintainer interaction in 9+ years.
73%
#1604326 snapcraft init doesn't fail if there is a .snapcraft.yaml file snapcraft (launchpad) closed Closed without resolution or linked pull request. The bug where snapcraft init fails to detect existing .snapcraft.yaml files remains unfixed. Likely abandoned due to prolonged inactivity.
71%
#1276 sources: validate unknown source-type in yaml snapcraft closed Closed without merging due to unresolved review comments and a failing CLA check caused by an email mismatch. The proposed validation for unknown source types in snapcraft.yaml was abandoned.
70%