no longer reports installed and available versions

Bug #182350 reported by Brian J. Murrell
4
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Triaged
Medium
Michael Vogt

Bug Description

Binary package hint: update-manager

When viewing available updates, update-manager used to report the installed version and the version that was available for update. It no longer does this. This is important to know to understand what you are updating to.

Please restore this functionality.

Tags: regression
Revision history for this message
Data (ubuntuaddress) wrote :

I would second this.

I know that the changelog also contains the version of the packages. But sometimes, the changelog is not available yet and is it IMHO important to know which version you are upgrading to.
The other thing is, that, sometimes you do not know the version of the currently installed package. You can just assume, that it is one version number lower that the update and hope that's in the cangelog history. But that is not always correct (e.g. if you have skipped an update at some point)

However, I do not think that this is a real bug. So I am marking this as wishlist.

Maybe someone who knows, why this change was introduced, could mention the reasons?
Thanks in advance!

Revision history for this message
Data (ubuntuaddress) wrote :

Somehow I do not have the appropriate rights to change the package's importance.

Could someone else please change it to "wishlist"?

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote : Re: [Bug 182350] Re: no longer reports installed and available versions

On Thu, 2008-02-28 at 11:08 +0000, Data wrote:
>
> However, I do not think that this is a real bug. So I am marking this as
> wishlist.

I disagree. It's a but insomuch as it's a regression in behaviour. If
it had never behaved as it did then yes, this would be an RFE, but it's
a bug since it's no longer doing what it used to do. That is a
regression.

> Maybe someone who knows, why this change was introduced, could mention the reasons?

Probably just more of the sad dumbing down of the update tool that is
being seen elsewhere. Unfortunately.

b.

Revision history for this message
Data (ubuntuaddress) wrote :

OK, having followed your argumentation I agree with you that it is a bug.
So I am tagging "regression" and marking as Confirmed.

Let's see what the dev's think about that...

Changed in update-manager:
status: New → Confirmed
Revision history for this message
Brian Murray (brian-murray) wrote :

This was changed in update-manager version 0.87 but I'm uncertain what the changelog entry means by the details tab. I couldn't find it.

  * UpdateManager/UpdateManager.py:
    - remove the "from $version to $version" from the main
      list as this is duplicated information from the details tab

Changed in update-manager:
assignee: nobody → mvo
importance: Undecided → Medium
status: Confirmed → Triaged
Revision history for this message
Data (ubuntuaddress) wrote :

I guess, the details tab mentioned is actually the "changes" tab. And as already stated above, it shows usually (although much later) the version of the package that's going to be installed. However, often you do not know the version of the currently installed package.
Furthermore it is much easier to get this information at "first glance" in the List of packages than somewhere down in a changelog. And I think the versions of the packages are important information!

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :

All of this discussion about versions being shown in the changelog entry assumes a changelog entry. Ubuntu's repository is not the only repository out there and most (all?) other repositories don't maintain changelogs, so the *ONLY* way to know what version you are updating from, to was the ones displayed in the upper window.

This is absolutely a usability regression with only a partial work-around.

Revision history for this message
Richard Birnie (rbirnie-deactivatedaccount) wrote :

This bug is a duplicate of bug 189406. That report has a patch attached that claims to fix the issue so let's continue in that thread. If anyone wants to test the patch feel free. Marking this bug as a duplicate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.