Be more explicit about grade/confinement combinations and their impact

Bug #1630901 reported by Daniel Holbach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Software Center Agent
Confirmed
Undecided
Unassigned

Bug Description

I received this in an email from an upstream who got confused about the options available for publication:

------------
* On the http://myapps.developer.ubuntu.com/ website, after I uploaded
my very first snap manually, when I eventually pressed the "Publish"
button, I somehow got the following error message:

    Revision 1 (strict) cannot target a stable channel (stable, grade: devel)

  which was rather confusing because I did *not* target the stable channel.
  Later, I realized that targeting the "candidate" channel would
trigger the same error.
  Perhaps the "candidate" channel was added rather recently, and the
error message
  has not been updated to reflect that? I would rather it say
something like this:

        Revision 1 (strict) cannot target a stable or candidate
channel (stable, grade: devel)

  so newbies like me won't get confused.
------------

Stephen Stewart says:
<beowulf> "Revision #1 cannot target a stable channel as it's <a href="/help/grade">grade</a> is set to 'devel'"
<beowulf> i think
<beowulf> dholbach: if you can include a link to a help page for grade ^^ in the bug

Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Once the PR gets merged, http://snapcraft.io/docs/build-snaps/publish would be a good place to link to.

Revision history for this message
Stephen Stewart (stephen-stewart) wrote :

8:26 AM <beowulf> "Grade / Channel mismatch: a devel grade package cannot target a stable channel. Please check your yamls."

(another option, with no help link)

Changed in software-center-agent:
status: New → Confirmed
Revision history for this message
Daniel Holbach (dholbach) wrote :
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.