Kernel plugin: Avoid redownloading os.snap on a local Git repo

Kyle Fazzari kyle.fazzari at
Mon Jan 9 21:31:25 UTC 2017

On 01/09/2017 12:08 PM, Michał Sawicz wrote:
> W dniu 09.01.2017 o 20:32, Michał Sawicz pisze:
>> I *think* (may be wrong) that `snapcraft pull` can help here:
> I was able to force `snapcraft pull` to pull things again by messing
> with parts/part-name/state - might wanna try that in case there's no
> better answers.

Careful with this, snapcraft tends to get upset if you mess with its
state behind its back.

Lifecycle steps build upon each other: pull -> build -> stage -> prime.
Let's say you ran `snapcraft build A`, which will pull part A (let's say
it was commit abdc1), and then build it. If commit abcd2 is later made
and you want to build it, you need to clean the pull step (which will
also clean the build step) with `snapcraft clean A`, and build again:
`snapcraft build A`. That will pull any updates that have been made, and
build anew.

Kyle Fazzari (kyrofa)
Software Engineer
Canonical Ltd.
kyle at

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <>

More information about the Snapcraft mailing list