snap always shows license as 'unset' after install
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Triaged
|
Medium
|
Samuele Pedroni | ||
Bug Description
This bug is specifically about the 'snap' command line interface, not the store listing or the GNOME Software integration.
Before installing a snap, 'snap info' shows the correct license metadata from the store listing. However, after installing a snap, 'snap info' always shows 'unset' in the license field. This seems to affect any snap.
Taking as an example, the 'hugo' snap, which I never installed before now:
$ snap info hugo | grep license
license: Apache-2.0
$ snap install hugo
hugo 0.59.1 from Hugo Authors installed
$ snap info hugo | grep license
license: unset
$ snap remove hugo
hugo removed
$ snap info hugo | grep license
license: Apache-2.0
$ snap --version
snap 2.42.1-1
snapd 2.42.1-1
series 16
debian -
kernel 5.2.0-3-amd64
| Changed in snappy: | |
| assignee: | nobody → Samuele Pedroni (pedronis) |
| Samuele Pedroni (pedronis) wrote | #1 |
| Changed in snappy: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| Changed in snappy: | |
| status: | Confirmed → Triaged |
| Mike Miller (mtmiller) wrote | #2 |
| affects: | snappy → snapd |
This relates to the long and not quite converged yet discussion here: https:/
In principle snapd could remember the store set license if it exist and present for snaps that don't carry their own license in the snap itself. Hugo is such a snap.