LTS not included in motd

Bug #568628 reported by Brian Murray on 2010-04-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
base-files (Ubuntu)
High
Unassigned
Lucid
High
Unassigned

Bug Description

Binary package hint: base-files

00-header should use lsb_release -d so that LTS appears in the motd instead of the codename.

So instead of: Ubuntu 10.04 (lucid)
We'd have: Ubuntu 10.04 LTS

Related branches

Changed in base-files (Ubuntu Lucid):
importance: Undecided → High
milestone: none → ubuntu-10.04
status: New → In Progress
Brian Murray (brian-murray) wrote :

While we are losing the release code name with this branch it is worth noting that if we were to use lsb_release -d and lsb_release -c we could end up with the following for Maverick.

Ubuntu maverick (development branch) (maverick)

So something fancy could be done to detect if someone is running the development branch but that might be invasive for Lucid.

Steve Langasek (vorlon) wrote :

I think it's actually fine to lose the code name from the banner at release time, and consistent with our overall branding policy.

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package base-files - 5.0.0ubuntu20

---------------
base-files (5.0.0ubuntu20) lucid; urgency=low

  * 00-header: use lsb_release -s -d so LTS is displayed LP: #568628
 -- Brian Murray <email address hidden> Thu, 22 Apr 2010 12:12:29 -0700

Changed in base-files (Ubuntu Lucid):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers