global.ent (ubuntu-docs) wrong distro information

[Brian Smith-Sweeney]

Binary package hint: ubuntu-docs

The distro information listed in global.ent (from ubuntu-docs package) is for Natty Narwhal (11.04), rather than the correct Maverick Meerkat (10.10).

In /usr/share/ubuntu-docs/libs/global.ent:
<!-- VERSIONS -->
<!ENTITY distro-version 'Natty Narwhal'>
<!ENTITY distro-rev '11.04'>
<!ENTITY distro-rev-short '11.04'>
<!-- the distro-rev-short entity should not include the "LTS" in a long term release and can be used for url links -->
<!ENTITY distro-release-date "April 2011">
<!ENTITY distro-support-date "October 2012">
<!ENTITY distro-short-codename "natty">
<!ENTITY distro-apt-cd-name "Ubuntu 11.04_Natty_Narwhal">
<!ENTITY linux-kernel-version "2.6.35">

In /etc/apt/sources.list (using MIT mirror):
# deb cdrom:[Ubuntu 10.10 _Maverick Meerkat_ - Release amd64 (20101007)]/ maverick main restricted
# See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to
# newer versions of the distribution.
deb http://ubuntu.media.mit.edu/ubuntu/ maverick main restricted
deb-src http://ubuntu.media.mit.edu/ubuntu/ maverick main restricted

Notably this means System->About Ubuntu reports the OS version incorrectly.

This install was done using the standard 64-bit desktop install ISO from http://www.ubuntu.com/desktop/get-ubuntu/download.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: ubuntu-docs 10.10.4
ProcVersionSignature: Ubuntu 2.6.35-23.41-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Dec 16 11:43:27 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: ubuntu-docs

[Book 'em Dano (heymrdjd)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 690248, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.