On Thu, Oct 13, 2005 at 01:39:17AM +0200, Erich Schubert <[EMAIL PROTECTED]> was heard to say: > Hello Daniel, > > Could you check whether 0.3.4 does the same thing? At least one bug > > like this has been fixed in that branch. > > 0.3.4 does basically the same thing - except that it gives a reason. ;-) > So this is a lot better; in fact the behaviour makes more sense than > that of apt-get now: argouml is the only reason why libi18n-java is > actually installed; so if it would upgrade libi18n-java by uninstalling > argouml, it would become unused and thus uninstalled, too... ;-) > > [...] > The following packages are BROKEN: > argouml > The following packages are unused and will be REMOVED: > libi18n-java > 0 packages upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > Need to get 0B of archives. After unpacking 81.9kB will be freed. > The following packages have unmet dependencies: > argouml: Depends: libi18n-java (< 0.1.3) but it is not installable > Resolving dependencies... > The following actions will resolve these dependencies: > > Keep the following packages at their current version: > libi18n-java [0.1.2.0.1-1 (now)] > > Score is 61 > > Accept this solution? [Y/n/q/?] > The following packages have been kept back: > libi18n-java > 0 packages upgraded, 0 newly installed, 0 to remove and 1 not upgraded. > Need to get 0B of archives. After unpacking 0B will be used. > Do you want to continue? [Y/n/?] > [...] > > The last [Y/n/?] question doesn't make sense, though: > basically it's a "I'm going to do nothing [Y/n/?]"
Yes, I'll probably eventually get it to automatically skip over the "do nothing" solution from the command-line (I haven't decided about visual mode; it makes some sense to offer to keep everything back there IMO). > Also I would suggest the wording "would be BROKEN" at the beginning. > > Also a more human-readable reasoning would be nice, but I guess you > can't do that... > After all "explaining proofs" is still a big issue in automated > reasoning. You actually can get an explanation about the problem resolver's decisions by typing "o" at the prompt. It won't help much for complicated situations, but it should help with simple ones (you can also enter "e" and jump into visual mode, which makes it more convenient to get at information about what's going on). This isn't a complete explanation, though, because the resolver doesn't know anything about the removal of unused packages. Daniel
signature.asc
Description: Digital signature
