snapd not wiring alias for 'dotnet' that is in snap assertion

Bug #1897984 reported by Chris Patterson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Invalid
Undecided
Unassigned

Bug Description

$ sudo snap install dotnet-sdk --classic
dotnet-sdk 3.1.402 from Microsoft .NET Core (dotnetcore✓) installed

$ dotnet
Command 'dotnet' not found, but can be installed with:

sudo snap install dotnet-sdk

$ stat /snap/bin/dotnet
stat: cannot stat '/snap/bin/dotnet': No such file or directory

$ snap aliases | grep dotnet
<empty>

$ curl -s "https://api.snapcraft.io/api/v1/snaps/assertions/snap-declaration/16/uHc4y9lWxyqYfxsqcr4xILzAai4L1BHs?max-format=4" -H "Accept: application/x.ubuntu.assertion"
type: snap-declaration
authority-id: canonical
revision: 2
series: 16
snap-id: uHc4y9lWxyqYfxsqcr4xILzAai4L1BHs
aliases:
  -
    name: dotnet
    target: dotnet-sdk
auto-aliases:
  - dotnet
publisher-id: NkziOx5Ju2cGzp2Ei3picHMIev25uDU6
snap-name: dotnet-sdk
timestamp: 2018-01-31T19:47:36.754886Z
sign-key-sha3-384: BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul

$ snap known snap-declaration snap-name=dotnet-sdk
type: snap-declaration
authority-id: canonical
revision: 2
series: 16
snap-id: uHc4y9lWxyqYfxsqcr4xILzAai4L1BHs
aliases:
  -
    name: dotnet
    target: dotnet-sdk
auto-aliases:
  - dotnet
publisher-id: NkziOx5Ju2cGzp2Ei3picHMIev25uDU6
snap-name: dotnet-sdk
timestamp: 2018-01-31T19:47:36.754886Z
sign-key-sha3-384: BWDEoaqyr25nF5SNCvEv2v7QnM9QsfCc0PBMYD_i2NGSQ32EF2d4D0hqUel3m8ul

AcLBUgQAAQoABgUCWnIdWAAAs5AQAJ0LLuZHYY0u7Fki6o5mbc6j5s2u9fNnN7BPrez9VAlv5bAr
iwXpDJ6jH65PnbWVQAzck+16Nfv0D2W87cIX4yfI4lDCt3Rl71igp6HPVFeExKZYSVLCKzl7kLuF
0Qrh+HYwtOGBecdexxmsjFm4mf9LDHfr6Dmt2veNPn6QSFTe+XTdMoruuZV7dePQZX2Fg6Vid78m
j1v32MaZmfHS6DYkj185CExQ3F+fzb+LuNlh+tYGi8UmXJZJag6aZ7x4U4aoBMXtRvxAiUmfqHHg
3K7ksTOXvAWrmf7IkbL4U9WO7N5XgfQ+/yL4ijXIMhsnM19lvCJFx4GrGomRwHFMYlmK0QnZHjIN
jZGDEkwLa8v1tqSxQ1H6ImqVWq0khdEAbjP/wi/ovEe1adgQvDCjlOMPD+V0eCGiuCRg/uSXYu2m
roNYRE2Qfki2ZZezrBZ/+wgdUV8yrTcw0qiw/YVhZvIIAdy7kMPANX4zjxjY5pN/vTkwl7RnInjB
Jde9htd+AO2cZz4AhI1zeGjUsrJApPUye+OJg5+nG1Ac52Ka15DsAe52eD1iCEQ1LF86D5zmFIPI
hNDr3oQ9gVydO6R8rlF631SnBlyJw8nv8HIW3K1Nx+jYSGR/1iD+yvEwopMivIMXYbvgObDH+E1d
5fb0RT950VsJmzASPeP+X0EVwJ2V

Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

I think that the snap declaration is wrong at this point. There is no app named dotnet-sdk in the current revision (98) of the dotnet-sdk snap. From what I can tell looking at the code it should be:

alises:
    - name: dotnet
      target: dotnet

Revision history for this message
Chris Patterson (cjp256) wrote :

Ah, that would make sense! Thank you!

I'm going to close this as it does not look like a snapd bug. :-)

Changed in snapd:
status: New → Invalid
Revision history for this message
Maciej Borzecki (maciek-borzecki) wrote :

@pedronis has updated the snap declaration which contains this now:

type: snap-declaration
authority-id: canonical
revision: 3
series: 16
snap-id: uHc4y9lWxyqYfxsqcr4xILzAai4L1BHs
aliases:
  -
    name: dotnet
    target: dotnet
auto-aliases:
  - dotnet
publisher-id: NkziOx5Ju2cGzp2Ei3picHMIev25uDU6

I can confirm that a dotnet alias was created during installation.

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.