Re: Git commit+

On Sat, Feb 11, 2017 at 10:56 AM, Mark Shuttleworth wrote: > What am I missing? It's not you, it's us. I was just playing with mosh and I see that copying the snapcraft.yaml to the part/src dir is not enough. It also needs to be in part/build. I don't have a workaround for that,

Re: Git commit+

OK, glad it's a known issue. The 'source-type: git' piece didn't fix anything for me, though, I still see the dirty-commit version number. snap/snapcraft.yaml contains this: parts: keepalived: plugin: autotools source: . source-type: git What am I missing? Mark On 11/02/17

Re: Git commit+

Hello! This is bug: https://bugs.launchpad.net/snapcraft/+bug/1662388 We will discuss if removing the yaml is needed at all. But in the meantime, add source-type: git. pura vida. -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at:

Git commit+

Hi folks In a branch with a snap/snapcraft.yaml I am seeing that git reports a version with a dirty commit (suffix+) for snaps built from the branch. Is there a way to prevent this, or is snapcraft doing something during the snapping process which will cause git to think the checkout is dirty?