On 9/26/07, Ian McDonald <[EMAIL PROTECTED]> wrote: > Well dist-upgrade installed it for me when trying to resolve which > packages to upgrade. > > This is because of this I suspect (which will get resolved with more > uploads I presume) > > The following packages are BROKEN: > epiphany-extensions [2.18.3-1] > The following packages have been automatically kept back: > ekiga [2.0.9-3 -> 2.0.11-1] libwnck-common [2.18.3-1 -> 2.20.0-1] > The following NEW packages will be automatically installed: > python-elementtree [1.2.6-11] xulrunner-gnome-support [1.8.1.6-1] > The following packages have been kept back: > libopal-2.2 [2.2.8~dfsg1-2 -> 2.2.11~dfsg1-1] > The following NEW packages will be installed: > epiphany-gecko [2.20.0-1] python-elementtree [1.2.6-11] > xulrunner-gnome-support [1.8.1.6-1] > 0 packages upgraded, 4 newly installed, 0 to remove and 3 not upgraded. > Need to get 501kB/1363kB of archives. After unpacking 4235kB will be used. > The following packages have unmet dependencies: > epiphany-extensions: Depends: epiphany-browser (< 2.19) but 2.20.0-1 > is installed. > Resolving dependencies... > The following actions will resolve these dependencies: > > Keep the following packages at their current version: > epiphany-extensions [Not Installed] > > Leave the following dependencies unresolved: > epiphany-gecko recommends epiphany-extensions > Score is -141 >
My apologies for this previous update. When I type y this time around it installed epiphany-gecko just fine. I think dist-upgrade just got a bit confused with the epiphany-extensions not being at 2.20 yet. Ian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]