Session indicator says "Up to Date", Update Manager "up-to-date"

Bug #864336 reported by Hernando Torque
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Session Menu
Invalid
Undecided
Unassigned
update-manager (Ubuntu)
Low
Robert Roth

Bug Description

This inconsistency in spelling looks a bit weird. Screenshot attached.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: indicator-session 0.3.6-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.20~fdo41059cmt14-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
Date: Sat Oct 1 23:31:40 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110112)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: indicator-session
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
Hernando Torque (htorque) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-session (Ubuntu):
status: New → Confirmed
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

It's Update Manager that is incorrect. :-) An adjective phrase should be hyphenated only if it comes before a noun, not after. An up-to-date system is up to date.

I suggest that this be fixed by using the text shown in <https://wiki.ubuntu.com/SoftwareUpdates#check-interactive>: "The software on this computer is up to date.".

affects: indicator-session (Ubuntu) → update-manager (Ubuntu)
Changed in update-manager (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
tags: added: bitesize
Robert Roth (evfool)
Changed in update-manager (Ubuntu):
assignee: nobody → Robert Roth (evfool)
status: Triaged → In Progress
Conor Curran (cjcurran)
Changed in indicator-session:
status: New → Invalid
Robert Roth (evfool)
Changed in update-manager (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package update-manager - 1:0.154.1

---------------
update-manager (1:0.154.1) precise; urgency=low

  [ Robert Roth ]
  * Change up-to-date text to up to date (LP: #864336)

  [ Michael Vogt ]
  * DistUpgrade/DistUpgradeController.py:
    - add precise as a LTS release
  * AutoUpgradeTester/profile/*/DistUpgrade.cfg:
    - updated to test oneiric->precise and lucid->precise
  * AutoUpgradeTester/UpgradeTestBackendQemu.py:
    - add support for different architectures
  * AutoUpgradeTester/profile/server-amd64/DistUpgrade.cfg:
    - add amd64 server upgrade test profile
  * DistUpgrade/DistUpgradeConfigParser.py:
    - add new "defaults_dir" argument to allow simplifying the
      auto-upgrade-tester config
  * DistUpgrade/DistUpgrade.cfg.lucid:
    - add lucid->precise upgrade config
  * AutoUpgradeTester/UpgradeTestBackendQemu.py:
    - dynamically allocate ssh/vnc ports when multiple testers are run
 -- Michael Vogt <email address hidden> Tue, 08 Nov 2011 09:35:27 +0100

Changed in update-manager (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers