severity 65262 wishlist -- On Tue, 6 Jun 2000, Brian White wrote:
> > Basically, you can't do that. This is not something it can reasonably deal > > with. I think there are other bugs reports to this effect.. > This is a valid problem! If an admin chooses to directly force a package > install, then apt needs to honor that decision. This bug should not > be closed. There is no way to directly force anything with the dpkg system. You can wedge a package into some weird state using --forcing options [which leave no record], but the natural behavior of *all* the tools is to fix that somehow. dpkg --configure -a tries to configure all unconfigured packages, dselect tries to remove/install new dependencies to fix missing ones, etc. That is how it works and there isn't much to be done. For you ssh problem I recommend simply editing the status file and removing the offending dependency. Alternatively you could use something like equivs -- if dpkg supported versions provides. Jason
