"No libraries to exclude from this release" printed many times
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
To reproduce, use this snapcraft.yaml:
name: test
version: '0.1'
summary: test
description: test
parts:
test:
plugin: python
Run:
$ snapcraft
[...]
Priming test
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
No libraries to exclude from this release
[...]
This of course offers no useful information. And note that it is printed without even passing -d.
This should be hidden on a normal snapcraft run.
And when running snapcraft -d, it could be shown but it needs to provide something useful. What does it mean that it's printed so many times? Can we related it to a different source file? Or should we print it only once?
| tags: | added: ui |
| Kyle Fazzari (kyrofa) wrote | #1 |
| Changed in snapcraft: | |
| status: | New → Confirmed |
| RoxD (roxd) wrote | #2 |
This comes when there is no core snap corresponding to a given Ubuntu release (i.e. non-xenial). It means there are no libraries snapcraft knows it can leave off when pulling in system libs. This should probably be a warning, but should likely only be shown once, or at most once per part.