← 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

 

Hi,

If the package was still present in quantal, this would be a normal
upload+backport, instead of an sru.  But since it's not in quantal, can
the backport already present in precise-backports be updated, please?

The bugs fixed are not "critical" in the sense that they do not break
the installation, but they are bad enough to worsen user experience.
Fixing the current backport would make it a more usable program for
precise users.  The three bugs are:

1) myunity depends upon DISTRIB_RELEASE being the second entry in /etc/lsb-release
2) myunity depends on no user running unity-2d on the machine, regardless of which user is running it.
3) myunity depends on no user running any command with "myunity" as part of its command line.

-- 
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


References