Container destroyed on snapcraft clean -s pull
Bug #1727445 reported by
Sergio Schvezov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Snapcraft |
Fix Released
|
Medium
|
Cris Dywan |
Bug Description
Destroying the container on a `snapcraft clean` may be debatably ok but destroying it on a `snapcraft clean -s pull`, specially after being instructed to do so with:
```
The 'pull' step of 'osm-ro' is out of date:
The 'python-packages' part property appears to have changed.
In order to continue, please clean that part's 'pull' step by running:
snapcraft clean osm-ro -s pull
```
Is just a major slow down on productivity, more so when running on slow networks.
Changed in snapcraft: | |
status: | In Progress → Fix Committed |
milestone: | none → 2.35 |
Changed in snapcraft: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
This should be a matter of simply not assuming None == 'pull' for that parameter. Refactor suggestions in https:/ /github. com/snapcore/ snapcraft/ pull/1587 will fix it.