'up arrows' in snap info version list are hard to read and parse

Bug #1814971 reported by Jason Hobbs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
snapd
Triaged
Medium
Unassigned

Bug Description

snap info <blah> output includes unicode up arrows, or carrots when unicode is disabled, to indicate a version is inherited from a more stable channel.

That's clever and it's neat to show off how snap channels work, but it's not as easy to read or parse as it could be. I'm not sure it is obvious at all what the up arrow indicates - it may require understanding how channels work.

If it would just print the version number for the channel, that would be a lot clearer and more straightforward to parse.

Maybe I'm really asking for a parseable snap info output.

summary: - 'up arrows' in snap info version list are unnecessarily clever, hard to
- read, and parse
+ 'up arrows' in snap info version list are hard to read and parse
Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote : Re: [Bug 1814971] [NEW] 'up arrows' in snap info version list are hard to read and parse

For me, parseable snap info is spelt "curl --silent --unix-socket
/var/run/snapd.socket a/v2/find?name=$x". I would like snap to grow a 'snap
query' command like lxc has but until then...

On Thu, 7 Feb 2019 at 11:45, Jason Hobbs <email address hidden> wrote:

> Public bug reported:
>
> snap info <blah> output includes unicode up arrows, or carrots when
> unicode is disabled, to indicate a version is inherited from a more
> stable channel.
>
> That's clever and it's neat to show off how snap channels work, but it's
> not as easy to read or parse as it could be. I'm not sure it is obvious
> at all what the up arrow indicates - it may require understanding how
> channels work.
>
> If it would just print the version number for the channel, that would be
> a lot clearer and more straightforward to parse.
>
> Maybe I'm really asking for a parseable snap info output.
>
> ** Affects: snappy
> Importance: Undecided
> Status: New
>
> ** Summary changed:
>
> - 'up arrows' in snap info version list are unnecessarily clever, hard to
> read, and parse
> + 'up arrows' in snap info version list are hard to read and parse
>
> --
> You received this bug notification because you are a member of Snappy
> Developers, which is subscribed to Snappy.
> https://bugs.launchpad.net/bugs/1814971
>
> Title:
> 'up arrows' in snap info version list are hard to read and parse
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snappy/+bug/1814971/+subscriptions
>

Revision history for this message
Jason Hobbs (jason-hobbs) wrote :

That's helpful Michael, thanks!

On Wed, Feb 6, 2019 at 6:20 PM Michael Hudson-Doyle <email address hidden>
wrote:

> For me, parseable snap info is spelt "curl --silent --unix-socket
> /var/run/snapd.socket a/v2/find?name=$x". I would like snap to grow a 'snap
> query' command like lxc has but until then...
>
> On Thu, 7 Feb 2019 at 11:45, Jason Hobbs <email address hidden>
> wrote:
>
> > Public bug reported:
> >
> > snap info <blah> output includes unicode up arrows, or carrots when
> > unicode is disabled, to indicate a version is inherited from a more
> > stable channel.
> >
> > That's clever and it's neat to show off how snap channels work, but it's
> > not as easy to read or parse as it could be. I'm not sure it is obvious
> > at all what the up arrow indicates - it may require understanding how
> > channels work.
> >
> > If it would just print the version number for the channel, that would be
> > a lot clearer and more straightforward to parse.
> >
> > Maybe I'm really asking for a parseable snap info output.
> >
> > ** Affects: snappy
> > Importance: Undecided
> > Status: New
> >
> > ** Summary changed:
> >
> > - 'up arrows' in snap info version list are unnecessarily clever, hard to
> > read, and parse
> > + 'up arrows' in snap info version list are hard to read and parse
> >
> > --
> > You received this bug notification because you are a member of Snappy
> > Developers, which is subscribed to Snappy.
> > https://bugs.launchpad.net/bugs/1814971
> >
> > Title:
> > 'up arrows' in snap info version list are hard to read and parse
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/snappy/+bug/1814971/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1814971
>
> Title:
> 'up arrows' in snap info version list are hard to read and parse
>
> Status in Snappy:
> New
>
> Bug description:
> snap info <blah> output includes unicode up arrows, or carrots when
> unicode is disabled, to indicate a version is inherited from a more
> stable channel.
>
> That's clever and it's neat to show off how snap channels work, but
> it's not as easy to read or parse as it could be. I'm not sure it is
> obvious at all what the up arrow indicates - it may require
> understanding how channels work.
>
> If it would just print the version number for the channel, that would
> be a lot clearer and more straightforward to parse.
>
> Maybe I'm really asking for a parseable snap info output.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/snappy/+bug/1814971/+subscriptions
>

tags: added: cdo-qa
tags: added: foundations-engine
Zygmunt Krynicki (zyga)
affects: snappy → snapd
Changed in snapd:
status: New → Triaged
Changed in snapd:
importance: Undecided → Medium
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.