Update-manager list earlier changes for certain packages before the relevant change for the update in question
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
boost-defaults (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
chromium-browser (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
update-manager (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
Steps to reproduce:
1. Have an old version of some boost package when a newer version is available.
2. Open update-manager, select the boost package and look at the "Changes" tab.
Expected result:
The tab should contain which version I have currently installed, which version is available, and a section from the changelog summarizing the changes between those two versions.
Actual result:
While the boost packages have this, it is far down below a series of older changelog entries. All of these are for versions older than the one currently installed and as such are already included in the version I have. Furthermore they push down the "currently installed/available version" part which should always be listed at the top.
I am not sure why this happens, and why it only happens with boost packages. I have seen this before with a previous boost update (unfortunately I failed to file a bug before updating), but not in any other packages.
$ apt-cache policy libboost-
libboost-
Installed: 1.49.0-3.1ubuntu1.1
Candidate: 1.49.0-3.1ubuntu1.2
Version table:
1.
500 http://
500 http://
*** 1.49.0-3.1ubuntu1.1 0
100 /var/lib/
1.
500 http://
With the package above installed, this issue should be easy to reproduce. I have also attached the content of the "Changes" tab in update-manager.
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: update-manager 1:0.174.4
ProcVersionSign
Uname: Linux 3.5.0-23-generic i686
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
Date: Sun Feb 24 15:04:06 2013
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InstallationDate: Installed on 2012-10-20 (127 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
MarkForUpload: True
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)
summary: |
- Update-manager list earlier changes for boost packages before the + Update-manager list earlier changes for certain packages before the relevant change for the update in question |
I have seen this a couple of more times over the years, but I recently caught the same issue with chromium-browser. This is on 20.04, according to `apt policy` the changes are
$ apt policy chromium-browser 61-0ubuntu0. 18.04.1 97-0ubuntu0. 20.04.1 0.4103. 97-0ubuntu0. 20.04.1 500 no.archive. ubuntu. com/ubuntu focal-updates/ universe amd64 Packages 61-0ubuntu0. 18.04.1 100 dpkg/status 0.3987. 163-0ubuntu1 500 no.archive. ubuntu. com/ubuntu focal/universe amd64 Packages
chromium-browser:
Installert: 83.0.4103.
Kandidat: 83.0.4103.
Versjonstabell:
83.
500 http://
*** 83.0.4103.
100 /var/lib/
80.
500 http://
However, the attached log is what update-manager display under technical details -> changes. It seems to be the complete history of the chromium-browser package.
Noticing now (from the output above), could this be related to my recent upgrade from 18.04 to 20.04. In other words, when upgrading from an -updates package in one series to a package from -updates in another series the comparision is confused because the older version was newer published in the newer series and thus it doesn't have a lower bound in the changelog?