Default track not respected in names output for command-not-found

Bug #1900119 reported by Adam Collard
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Snap Store Server
New
Undecided
Unassigned

Bug Description

In order to support command-not-found, snapd queries the store to find out what snaps are available, and with what version. This data doesn't seem to respect default tracks, nor closed channels.

As seen in the maas snap:

$ maas

Command 'maas' not found, but can be installed with:

sudo snap install maas # version 2.3.3-6498-ge4db91d-snap, or
sudo apt install maas # version 1:0.7

See 'snap info maas' for additional versions.

More specifically, using `snap advise-snap` - https://paste.ubuntu.com/p/h2Ff8fVqvb/

As can be seen in `snap info maas` or on snapcraft.io - https://snapcraft.io/maas/releases there is no 2.3.3 version published. This was however the last version published in latest/stable.

I expect the store, and then snapd to respect the default track, and respond with the "most stable" version in that track for command not found - currently that would be 2.8.2-8577-g.a3e674063

William Grant (wgrant)
tags: added: default-track names
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.