incorrect behavior when dependency is missing for downgrade

Bug #1248433 reported by Stelian Galmati
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
In Progress
Undecided
Unassigned

Bug Description

Having the following scenario:

Package: a
Status: install ok installed
Version: 2
Depends: b (= 2)
Architecture: all

Package: b
Status: install ok installed
Version: 2
Architecture: all

Package: a
Version: 1
Depends: b (= 1)
Architecture: all

If I mark_install a, version 1 then it will simply mark package a, version 2 for removal.
I would expect an message like "... you have held broken packages" since package b, version 1 is missing from the repository.

Tested on:
--------------------------
Ubuntu 12.04 amd64
python-apt 0.8.3ubuntu7.1

Thanks

summary: - package is not downgraded, it is simply removed
+ incorrect behavior when dependency is missing for downgrade
Revision history for this message
Julian Andres Klode (juliank) wrote :

That's an APT bug. It's fixed in Debian, I need to investigate whether the fix is in Ubuntu.

affects: python-apt (Ubuntu) → apt (Ubuntu)
Changed in apt (Ubuntu):
status: New → In Progress
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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