LTS not included in motd
Bug #568628 reported by
Brian Murray
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| base-files (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
| Lucid |
Fix Released
|
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
lp://staging/~brian-murray/ubuntu/lucid/base-files/bug-568628
- Ubuntu Core Development Team: Pending requested
-
Diff: 23 lines (+7/-1)2 files modifieddebian/changelog (+6/-0)
debian/update-motd.d/00-header (+1/-1)
| Changed in base-files (Ubuntu Lucid): | |
| importance: | Undecided → High |
| milestone: | none → ubuntu-10.04 |
| status: | New → In Progress |
Revision history for this message
| Brian Murray (brian-murray) wrote | #1 |
Revision history for this message
| Steve Langasek (vorlon) wrote | #2 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in base-files (Ubuntu Lucid): | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
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.