Package: dpkg
Version: 1.15.5.6
Severity: wishlist
If the administrator tries to upgrade or downgrade a package in such a
way as to violate another package’s dependencies, dpkg does nothing to
stop him or her.
You can try it:
1. Build packages packagea_1_<arch>.deb and packageb_1_<arch>.deb,
such that packageb Depends: packagea (<= 1).
2. dpkg -i packagea_1_*.deb packageb_1_*.deb
3. Build a new version, packagea_2_<arch>.deb.
4. dpkg -i packagea_2_*.deb
dpkg won’t complain.
I suggest updating the checks when configuring and unpacking a package
to take dependencies and pre-dependencies of installed packages
(respectively) into account. Fixing this would make downgrading
packages safer.
What do you think?
Jonathan
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
