[upload] Catch name registration issue and explain how

[Daniel Holbach]

Earlier I got this:
-----------------
Uploading existing moon-buggy_1.0.51.9_amd64.snap.

Uploading moon-buggy_1.0.51.9_amd64.snap [================================] 100%
Checking package status... |

Upload did not complete.
Some errors were detected:

You must register moon-buggy name for 16 before uploading, please register it and try again.
-----------------

It'd be nice if snapcraft linked to https://myapps.developer.ubuntu.com/dev/click-apps/register-name/

[Vincent Ladeuil (vila)]

There is WIP to issue:

Oops! It looks like you don’t own the “moon-buggy” name. See “snapcraft register-name” for guidance on reserving snap names.

[Natalia Bidart (nataliabidart)]

Just as a side note, the error message should not point the user to the server, given the CLI will allow for name registration, and we don't want to break the CLI workflow by giong to the web.

[Claudio André (claudioandre.br)]

I would like to see a clear direction in the error message and the URL is the best one.

I failed to find any useful documentation about name registration in google (top items) only a few bug reports. Even inside (https://myapps.developer.ubuntu.com/dev/click-apps/) I found no link like 'register a name'.

So, it will help packagers a lot if a clear direction is seen inside the error message: That said, +1 to:

-----------------
It'd be nice if snapcraft linked to https://myapps.developer.ubuntu.com/dev/click-apps/register-name/

[Thomi Richards (thomir-deactivatedaccount)]

I just spent 30 minutes uploading a snap, only to be told *afterwards* that I hadn't registered the name. At the very least snapcraft should check before starting the upload. Ideally it'd give me the option to do it right then and there, since it's almost always what I want to do anyway...

[Gustavo Niemeyer (niemeyer)]

There's a whole new workflow coming for this soon. You'll be able to actually register the name from the command line too.

[Mark Shuttleworth (sabdfl)]

As Gustavo said, sorry about this, the fix is in the queue now.

Mark

[Leo Arias (elopio)]

In order to fix this as Natalia suggest, we first need to implement the register command. That's bug #1595013.

[Simon Quigley (tsimonq2)]

It seems to me like this is a server-side issue as there is no message in the code indicating that this is client-side. I've looked at all of the files that could be responsible and I also grepped. Nothing. So this looks to me like this isn't an issue with Snapcraft.

Can anybody confirm/deny my findings?

[Leo Arias (elopio)]

The store will return a 404 if the snap was not registered before the upload. But there's something else we are missing. We start the upload by pushing the files to up/down, in the unscanned-upload. Before that, we need to check if the user is allowed to push the snap. There is no dry-run for the upload, so I think we are missing some work from the store.

@nessita, could you please confirm?

[Sergio Schvezov (sergiusens)]

https://github.com/snapcore/snapcraft/pull/632

[Simon Quigley (tsimonq2)]

Thanks Sergio :)