Comment 8 for bug 1831135

Revision history for this message
Ondrej Kubik (ondrak) wrote : Re: [Bug 1831135] Re: prime error: unable to set version: it was already set in the 'build' step

pull clones into parts/<part name>/src
but from there onwards it's hard links into parts/<part name>/build
then build installs files into parts/<part name>/install
and from there it's hard links to stage and prime

However kernel plugging avoids any links between parts/<part name>/src and
parts/<part name>/build

On Thu, 8 Dec 2022 at 15:45, Dean Matsen <email address hidden> wrote:

> No, snapcraft "pull" doesn't just copy, it uses hardlinks
>
> https://bugs.launchpad.net/shiner/+bug/1999091
>
> --
> You received this bug notification because you are a member of Snappy
> Developers, which is subscribed to Snapcraft.
> https://bugs.launchpad.net/bugs/1831135
>
> Title:
> prime error: unable to set version: it was already set in the 'build'
> step
>
> Status in Snapcraft:
> Invalid
>
> Bug description:
> Trying to build Multipass with the following patch:
> http://paste.ubuntu.com/p/PzMKxvpw2m/ to trigger "new" snapcraft.
>
> Having built, trying to `snapcraft prime` I end up with:
>
> Unable to set version: it was already set in the 'build' step.
> Failed to run 'override-build': Exit code was 2.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snapcraft/+bug/1831135/+subscriptions
>
>