On Tue, Jun 17, 2008 at 08:11:10PM -0700, Daniel Burrows wrote:
On Tue, Jun 17, 2008 at 11:08:33PM +0000, "brian m. carlson" <[EMAIL PROTECTED]> was heard to say:When I tried to upgrade my system today, the new ncurses-base depends on a newer version of libncurses5 than is in unstable (on amd64). As a consequence, the dependency resolver offers to keep ncurses-base at its current version. The next option is to remove ncurses-base; however, ncurses-base is an essential package. If I select this resolution, aptitude seems quite happy to remove ncurses-base. (I did stop it before it actually attempted to invoke dpkg.)I can't reproduce this on my computer. Do you have an example of aptitude removing an essential package without prompting? It should do something like this:
I used the GUI interface, and the bug exhibited itself as part of an upgrade. When I type ! to accept the solution of removing ncurses-bin, no warning window pops up, and if I hit g twice, it will proceed to start downloading. I didn't actually wait to see if it further prompted me. Your example exhibits the same behavior when using the GUI. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only troff on top of XML: http://crustytoothpaste.ath.cx/~bmc/code/thwack OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
signature.asc
Description: Digital signature
