adding the after keyword doesn't mark a part as dirty

Bug #1676243 reported by Leo Arias on 2017-03-27
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snapcraft
Medium
Unassigned

Bug Description

The after keyword puts files in the stage directory, which can affect the build of parts. When the after keyword is added to a part, it has to be marked as dirty so it is forced to run the build step again.

To reproduce:

$ snapcraft init
$ snapcraft
# add `after: [go]` to the part
$ snapcraft

Note that all the steps for the part are skipped.

Kyle Fazzari (kyrofa) wrote :

This for me actually causes the `go` part to be fetched and go through the lifecycle. However, removing the `after` keyword completely does skip everything, which means it indeed isn't included in the dirty calculation.

Changed in snapcraft:
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers