Packages might get downgraded to stable release version ignoring active updates/security archives
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ppa-purge |
Triaged
|
Low
|
Unassigned |
Bug Description
I've tried to purge ppa:webapps/preview from my Ubuntu precise installation, but stumbled upon weird behavior: ppa-purge offered to downgrade my 'chromium-browser' package to 18.0.XXXX (from precise/universe) despite the fact that I had had it at version 24.0.XXX (from precise-
I've done some initial research (you can see the full log of ppa-purge command attached) and it appears that ppa-purge fails to remove some of the packages with apt-get since they don't exist in precise archive, then falls back to aptitude and the latter handles "PACKAGE/ARCHIVE" specification differently:
$ sudo apt-get install chromium-
Reading package lists... Done
Building dependency tree
Reading state information... Done
chromium-browser is already the newest version.
Selected version '24.0.1312.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$ aptitude show chromium-
Version: 18.0.1025.
$ aptitude show chromium-
Version: 24.0.1312.
And it requires some tinkering with its query language to make aptitude print expected version:
$ aptitude show '?name(
Version: 24.0.1312.
Aptitude version:
$ aptitude show aptitude | grep -i version
Version: 0.6.6-1ubuntu1.1
ppa-purge version:
$ aptitude show ppa-purge | grep -i version
Version: 0.2.8+bzr56
Related branches
- ppa-purge: Pending requested
-
Diff: 1027 lines (+652/-214) (has conflicts)9 files modifieddebian/changelog (+25/-2)
debian/compat (+1/-1)
debian/control (+12/-12)
debian/copyright (+8/-10)
debian/ppa-purge.8 (+98/-0)
debian/ppa-purge.bash-completion (+86/-67)
debian/ppa-purge.manpages (+1/-1)
dev/null (+0/-33)
ppa-purge (+421/-88)
Changed in ppa-purge: | |
status: | New → Triaged |
importance: | Undecided → Low |
I see the issue with aptitude here, but I think ppa-purge was not supposed to work, if the pkgs are not available for precise. Which release was there for the pkgs then? "apt-cache policy <pkgname>" shows.
BTW If there are pkg available in r.g. trusty-updates, "apt-get install <pkgname>/trusty" seems to use it.