[Bug 1248433] [NEW] incorrect behavior when dependency is missing for downgrade
Stelian Galmati
1248433 at bugs.launchpad.net
Wed Nov 6 07:42:25 UTC 2013
Public bug reported:
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
** Affects: python-apt (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- package is not downgraded, it is simply removed
+ incorrect behavior when dependency is missing for downgrade
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1248433
Title:
incorrect behavior when dependency is missing for downgrade
Status in “python-apt” package in Ubuntu:
New
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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1248433/+subscriptions
More information about the foundations-bugs
mailing list