I’ve just tried building a new snap for the first time and the output includes a line suggesting there’s an error, but I don’t think it’s an error:
Launching a VM.
error: no changes of type "auto-refresh" found
(...and then a bunch of stuff about building...)
I don’t know exactly what this is doing, but I would guess the following:
snapcraft is trying to auto-refresh some things and there currently aren’t any in need of it?
this is being seen as an error, either because snapcraft is using the wrong command to auto-refresh things (so it is an error, but it’s snapcraft’s error, not mine) or because there not being any auto-refresh changes is being reported as an error when it isn’t
this is at most a warning (since it doesn’t abort the process) and probably shouldn’t be shown at all because it’s some sort of snapcraft internal thing and not to do with my app
Since I’m not sure what causes it, I don’t know what to propose to fix it, but I do know that it’s worrying when the build process contains the word “error”, and it shouldn’t unless there actually is an error.
This appears to be an attempt to wait for the ensure that no snap is refreshed while the build proceeds (which would make it impossible to reproduce the build).
Looking at the documentation for snap watch, changing the last argument to --last=auto-refresh? would provide the desired behaviour: wait for an auto-refresh change to complete, but don’t print an error if no such change exists.
As this looked fairly simple, I’ve submitted a fix for it: