Re: Full-upgrade (apt vs cupt)
On Wed, Sep 23, 2009 at 9:02 AM, Sven Joachim <svenjoac@gmx.de> wrote:
> On 2009-09-23 08:49 +0200, Javier Barroso wrote:
>
>> I wanted to test cupt [1], and then I tried a full-upgrade.
>>
>> aptitude is not capable to resolve dependencies, but cupt yes. Like
>> cupt is very new, I would like to ask about why do you think this diff
>> is here:
>>
>> # LANG=C aptitude full-upgrade
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Reading extended state information
>> Initializing package states... Done
>> The following packages are BROKEN:
>> libempathy-gtk19 libempathy23 telepathy-mission-control-5
>> The following NEW packages will be installed:
>> empathy-doc{a} geoclue{a} geoclue-hostip{a} geoclue-localnet{a}
>> geoclue-manual{a} geoclue-yahoo{a} libchamplain-0.4-0{a}
>> libchamplain-gtk-0.4-0{a} libclutter-1.0-0{a}
>> libclutter-gtk-0.10-0{a} libempathy-gtk28{a} libempathy30{a}
>> libgeoclue0{a}
>> libnm-glib0{a} libnm-util1{a}
>> The following packages will be upgraded:
>> empathy libempathy-common libempathy-gtk-common
>> 3 packages upgraded, 16 newly installed, 0 to remove and 0 not upgraded.
>> Need to get 1264kB/4890kB of archives. After unpacking 8774kB will be used.
>> The following packages have unmet dependencies:
>> libempathy23: Depends: libempathy-common (= 2.26.2-1) but 2.28.0-1
>> is to be installed.
>> libempathy-gtk19: Depends: libempathy-gtk-common (= 2.26.2-1) but
>> 2.28.0-1 is to be installed.
>> telepathy-mission-control-5: Conflicts: telepathy-mission-control
>> but 4.67-4 is installed.
>> The following actions will resolve these dependencies:
>>
>> Keep the following packages at their current version:
>> empathy [2.26.2-1 (now)]
>> libempathy-common [2.26.2-1 (now)]
>> libempathy-gtk-common [2.26.2-1 (now)]
>> libempathy-gtk28 [Not Installed]
>> libempathy30 [Not Installed]
>> telepathy-mission-control-5 [Not Installed]
>>
>> Tier: Safe actions (10000)
>>
>> Accept this solution? [Y/n/q/?] q
>
> You should press n instead and see what else aptitude has to offer.
The fifth solution was the same than with cupt
> new resolver in aptitude 0.5.9 is over-cautious and its first suggestion
> is apparently always a solution that does not remove packages. For the
> full-upgrade action this is rather undesirable.
I agree
Thanks for your reply
Reply to: