← Back to team overview

myunity team mailing list archive

[Bug 999771] Re: myunity depends upon DISTRIB_RELEASE being the second entry in /etc/lsb-release

 

OK I uploaded and accepted it. I'm not sure about the version number (we
don't really have precedent for this), but it should be alright.

I'd really appreciate someone backporting these fixes to the precise
(release) package.

and you could use pgrep (from procps) instead of that ps | grep -v grep
stuff ;-).

-- 
You received this bug notification because you are a member of MyUnity
team, which is subscribed to MyUnity.
https://bugs.launchpad.net/bugs/999771

Title:
  myunity depends upon DISTRIB_RELEASE being the second entry in /etc
  /lsb-release

Status in MyUnity:
  New
Status in Precise Backports:
  New
Status in “myunity” package in Ubuntu:
  Invalid
Status in “myunity” source package in Precise:
  New
Status in “myunity” source package in Quantal:
  Won't Fix

Bug description:
  myunity incorrectly parses the lsb-release file in Main.module.  It makes assumptions about the order of lines.  Since lsb-release is a list of shell variables which can be sourced by other programs, perhaps it would be better to use the shell to parse it, rather than just cat it.  Something more like:
  SHELL "source /etc/lsb-release; echo $DISTRIB_RELEASE" to Uversion

To manage notifications about this bug go to:
https://bugs.launchpad.net/myunity/+bug/999771/+subscriptions


Follow ups

References