Snapcraft

snap directory excluded from cleanbuild tarball

Bug #1661391 reported by Kyle Fazzari on 2017-02-02

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	Snapcraft	Fix Released	High	Kyle Fazzari

Bug Description

The upcoming snapcraft release moves to using the `snap/` directory for holding plugins and the snapcraft.yaml, but the `snap/` directory gets excluded from the cleanbuild tarball (because `prime/` was historically called `snap/`).

Tags:

Revision history for this message

Kyle Fazzari (kyrofa) wrote on 2017-02-02:

Fix here: https://github.com/snapcore/snapcraft/pull/1102

Changed in snapcraft:
status:	New → In Progress
importance:	Undecided → High
assignee:	nobody → Kyle Fazzari (kyrofa)

Revision history for this message

Leo Arias (elopio) wrote on 2017-02-03:

Thanks for the quick fix!
Sorry for not catching it earlier.

Kyle Fazzari (kyrofa) on 2017-02-03

Changed in snapcraft:
status:	In Progress → Fix Committed

Leo Arias (elopio) on 2017-02-03

tags:

added: regression

Leo Arias (elopio) on 2017-02-09

tags:

added: cleanbuild

Leo Arias (elopio) on 2017-09-08

Changed in snapcraft:
status:	Fix Committed → Fix Released

Revision history for this message

Lucio (luciomarinelli) wrote on 2018-08-16:

build log Edit (13.1 KiB, text/plain)

I am bulding gtk-gnutella package for i386 and amd64 using Launchpad-Github integration following instructions at https://docs.snapcraft.io/build-snaps/ci-integration however build failed because of the error:

Could not find snap/snapcraft.yaml. Are you sure you are in the right directory?
To start a new project, use `snapcraft init`
Build failed

Full log attached.

Looks similar to the issue related to this bug... any suggestion?