[hardy] Evolution doesn't seem to be fully installed

Hello Caroline,

Thank you for reporting this bug and helping make Ubuntu better. I wonder if what happened was you did a 'dist-upgrade' soon after E-D-S 2.21.91 was put available, but before Evolution 2.21.91 itself was in the repositories. This might have caused Evo to be removed to satisfy E-D-S pre-reqs.

Of course, I am not sure of this, but sounds plausible.

Can you please check your dpkg logs (under /var/log for actions on Evolution itself at the time of your upgrade to E-D-S 2.21.91?

Thank you.

No mention of evo itself in dpkg log

2008-02-12 17:02:50 upgrade evolution-data-server 2.21.90-0ubuntu2 2.21.91-0ubuntu1
2008-02-12 17:02:50 status half-configured evolution-data-server 2.21.90-0ubuntu2
2008-02-12 17:02:50 status unpacked evolution-data-server 2.21.90-0ubuntu2
2008-02-12 17:02:50 status half-installed evolution-data-server 2.21.90-0ubuntu2
2008-02-12 17:02:51 status half-installed evolution-data-server 2.21.90-0ubuntu2
2008-02-12 17:02:51 status unpacked evolution-data-server 2.21.91-0ubuntu1
2008-02-12 17:02:51 status unpacked evolution-data-server 2.21.91-0ubuntu1
2008-02-12 17:02:52 upgrade evolution-data-server-common 2.21.90-0ubuntu2 2.21.91-0ubuntu1
2008-02-12 17:02:52 status half-configured evolution-data-server-common 2.21.90-0ubuntu2
2008-02-12 17:02:52 status unpacked evolution-data-server-common 2.21.90-0ubuntu2
2008-02-12 17:02:52 status half-installed evolution-data-server-common 2.21.90-0ubuntu2
2008-02-12 17:02:52 status half-installed evolution-data-server-common 2.21.90-0ubuntu2
2008-02-12 17:02:52 status unpacked evolution-data-server-common 2.21.91-0ubuntu1
2008-02-12 17:02:52 status unpacked evolution-data-server-common 2.21.91-0ubuntu1

2008-02-12 17:03:25 configure evolution-data-server-common 2.21.91-0ubuntu1 2.21.91-0ubuntu1
2008-02-12 17:03:25 status unpacked evolution-data-server-common 2.21.91-0ubuntu1
2008-02-12 17:03:25 status half-configured evolution-data-server-common 2.21.91-0ubuntu1
2008-02-12 17:03:25 status installed evolution-data-server-common 2.21.91-0ubuntu1

2008-02-19 01:09:15 upgrade evolution-common 2.21.90-0ubuntu1 2.21.91-0ubuntu1
2008-02-19 01:09:15 status half-configured evolution-common 2.21.90-0ubuntu1
2008-02-19 01:09:15 status unpacked evolution-common 2.21.90-0ubuntu1
2008-02-19 01:09:15 status half-installed evolution-common 2.21.90-0ubuntu1
2008-02-19 01:09:19 status half-installed evolution-common 2.21.90-0ubuntu1
2008-02-19 01:09:24 status unpacked evolution-common 2.21.91-0ubuntu1
2008-02-19 01:09:25 status unpacked evolution-common 2.21.91-0ubuntu1

2008-02-21 04:36:47 upgrade evolution-data-server 2.21.91-0ubuntu1 2.21.91-0ubuntu2
2008-02-21 04:36:47 status half-configured evolution-data-server 2.21.91-0ubuntu1
2008-02-21 04:36:47 status unpacked evolution-data-server 2.21.91-0ubuntu1
2008-02-21 04:36:47 status half-installed evolution-data-server 2.21.91-0ubuntu1
2008-02-21 04:36:48 status half-installed evolution-data-server 2.21.91-0ubuntu1
2008-02-21 04:36:48 status unpacked evolution-data-server 2.21.91-0ubuntu2
2008-02-21 04:36:48 status unpacked evolution-data-server 2.21.91-0ubuntu2
2008-02-21 04:36:48 upgrade evolution-data-server-common 2.21.91-0ubuntu1 2.21.91-0ubuntu2
2008-02-21 04:36:48 status half-configured evolution-data-server-common 2.21.91-0ubuntu1
2008-02-21 04:36:48 status unpacked evolution-data-server-common 2.21.91-0ubuntu1
2008-02-21 04:36:49 status half-installed evolution-data-server-common 2.21.91-0ubuntu1
2008-02-21 04:36:49 status half-installed evolution-data-server-common 2.21.91-0ubuntu1
2008-02-21 04:36:49 status unpacked evolution-data-server-common 2.21.91-0ubuntu2
2008-02-21 04:36:49 status unpacked evolution-data-server-common 2...

From January:

2008-01-30 01:02:46 install evolution <none> 2.21.4-0ubuntu1
2008-01-30 01:02:46 status half-installed evolution 2.21.4-0ubuntu1
2008-01-30 01:02:48 status unpacked evolution 2.21.4-0ubuntu1
2008-01-30 01:02:48 status unpacked evolution 2.21.4-0ubuntu1
2008-01-30 01:02:48 install evolution-exchange <none> 2.21.4-0ubuntu1
2008-01-30 01:02:48 status half-installed evolution-exchange 2.21.4-0ubuntu1
2008-01-30 01:02:48 status unpacked evolution-exchange 2.21.4-0ubuntu1
2008-01-30 01:02:48 status unpacked evolution-exchange 2.21.4-0ubuntu1
2008-01-30 01:02:49 install evolution-plugins <none> 2.21.4-0ubuntu1
2008-01-30 01:02:49 status half-installed evolution-plugins 2.21.4-0ubuntu1
2008-01-30 01:02:49 status unpacked evolution-plugins 2.21.4-0ubuntu1
2008-01-30 01:02:49 status unpacked evolution-plugins 2.21.4-0ubuntu1
2008-01-30 01:02:49 install evolution-webcal <none> 2.12.0-1ubuntu1
2008-01-30 01:02:49 status half-installed evolution-webcal 2.12.0-1ubuntu1
2008-01-30 01:02:49 status unpacked evolution-webcal 2.12.0-1ubuntu1
2008-01-30 01:02:49 status unpacked evolution-webcal 2.12.0-1ubuntu1

2008-01-30 01:20:01 configure evolution 2.21.4-0ubuntu1 2.21.4-0ubuntu1
2008-01-30 01:20:01 status unpacked evolution 2.21.4-0ubuntu1
2008-01-30 01:20:01 status unpacked evolution 2.21.4-0ubuntu1
2008-01-30 01:20:01 status half-configured evolution 2.21.4-0ubuntu1
2008-01-30 01:20:12 status installed evolution 2.21.4-0ubuntu1
2008-01-30 01:20:15 configure evolution-exchange 2.21.4-0ubuntu1 2.21.4-0ubuntu1
2008-01-30 01:20:15 status unpacked evolution-exchange 2.21.4-0ubuntu1
2008-01-30 01:20:15 status half-configured evolution-exchange 2.21.4-0ubuntu1
2008-01-30 01:20:21 status installed evolution-exchange 2.21.4-0ubuntu1
2008-01-30 01:20:23 configure evolution-plugins 2.21.4-0ubuntu1 2.21.4-0ubuntu1
2008-01-30 01:20:23 status unpacked evolution-plugins 2.21.4-0ubuntu1
2008-01-30 01:20:23 status half-configured evolution-plugins 2.21.4-0ubuntu1
2008-01-30 01:20:23 status installed evolution-plugins 2.21.4-0ubuntu1
2008-01-30 01:20:23 configure evolution-webcal 2.12.0-1ubuntu1 2.12.0-1ubuntu1
2008-01-30 01:20:23 status unpacked evolution-webcal 2.12.0-1ubuntu1
2008-01-30 01:20:23 status half-configured evolution-webcal 2.12.0-1ubuntu1
2008-01-30 01:20:33 status installed evolution-webcal 2.12.0-1ubuntu1

2008-01-30 22:40:56 startup packages remove
2008-01-30 22:40:56 status installed evolution-plugins 2.21.4-0ubuntu1
2008-01-30 22:41:12 remove evolution-plugins 2.21.4-0ubuntu1 2.21.4-0ubuntu1
2008-01-30 22:41:12 status half-configured evolution-plugins 2.21.4-0ubuntu1
2008-01-30 22:41:12 status half-installed evolution-plugins 2.21.4-0ubuntu1
2008-01-30 22:41:12 status config-files evolution-plugins 2.21.4-0ubuntu1
2008-01-30 22:41:12 status config-files evolution-plugins 2.21.4-0ubuntu1
2008-01-30 22:41:12 status config-files evolution-plugins 2.21.4-0ubuntu1
2008-01-30 22:41:12 status not-installed evolution-plugins <none>
2008-01-30 22:41:12 status installed evolution-exchange 2.21.4-0ubuntu1
2008-01-30 22:41:12 remove evolution-exchange 2.21.4-0ubuntu1 2.21.4-0ubuntu1
2008-01-30 22:41:12 status half-configured evolution-exchange 2.21.4-0...

from /var/log/dist-upgrade

Installing libcamel1.2-10 as dep of evolution-exchange
Installing libecal1.2-7 as dep of evolution-exchange
Installing libedata-book1.2-2 as dep of evolution-exchange
Installing libedata-cal1.2-6 as dep of evolution-exchange
Installing libedataserverui1.2-8 as dep of evolution-exchange
Installing libexchange-storage1.2-3 as dep of evolution-exchange
Installing evolution-data-server as dep of evolution
Installing evolution-data-server-common as dep of evolution-data-server
Installing libegroupwise1.2-13 as dep of evolution-data-server
Installing libgdata-google1.2-1 as dep of evolution-data-server
Installing libgdata1.2-1 as dep of libgdata-google1.2-1
Installing gtkhtml3.14 as dep of evolution

Starting
Starting 2
Investigating evolution-data-server
Package evolution-data-server has broken dep on evolution
  Considering evolution 2 as a solution to evolution-data-server 4
  Will not break evolution as stated in Breaks field in evolution-data-server
  Considering evolution 2 as a solution to evolution-data-server 4
  Will not break evolution as stated in Breaks field in evolution-data-server
Package evolution-data-server has broken dep on evolution-exchange
  Considering evolution-exchange 0 as a solution to evolution-data-server 4
  Will not break evolution-exchange as stated in Breaks field in evolution-data-server
  Considering evolution-exchange 0 as a solution to evolution-data-server 4
  Will not break evolution-exchange as stated in Breaks field in evolution-data-server
Investigating evolution
Package evolution has broken dep on evolution-data-server
  Considering evolution-data-server 4 as a solution to evolution 2
  Removing evolution rather than change evolution-data-server

Investigating evolution-exchange
Package evolution-exchange has broken dep on evolution
  Considering evolution 2 as a solution to evolution-exchange 0
  Removing evolution-exchange rather than change evolution
Investigating compizconfig-backend-gconf
Package compizconfig-backend-gconf has broken dep on libcompizconfig-backend-gconf
  Considering libcompizconfig-backend-gconf -2 as a solution to compizconfig-backend-gconf 0
  Added libcompizconfig-backend-gconf to the remove list
  Fixing compizconfig-backend-gconf via remove of libcompizconfig-backend-gconf
Investigating evolution-plugins
Package evolution-plugins has broken dep on evolution
  Considering evolution 2 as a solution to evolution-plugins 0
  Removing evolution-plugins rather than change evolution

Package restricted-manager has broken dep on restricted-manager-core
  Considering restricted-manager-core 1 as a solution to restricted-manager -1
  Removing restricted-manager rather than change restricted-manager-core
 Try to Re-Instate evolution-data-server
Re-Instated evolution-data-server (1 vs 0)
Done

This looks like it happened when I upgraded this machine from Hardy alpha 3 following a reinstall caused by a bug in gnome system tools.

Is this interesting or just unique to me?

I do remember that, at least at one point in the hardy buildup, I did get an E-D-S upgrade to propose Evo removal (new E-D-S had already been put available in the repositories, but not the corresponding Evo). During Hardy development, the KDE4 updates would every so often cause this.

Every so often I get this type of upgrade behaviour during new releases build-time (and also on Debian -- duh --). So, you are not alone (and I guess a lot of others have also seen/got hit by this). So yes, this is interesting, but mostly to highlight the dangers of running Alpha code: it can be very dangerous to run a blind dist-upgrade.

What I do to survive in the bleeding edge:

1. I never run 'apt-get dist-upgrade' and then say 'Y' to the changes without checking what is being removed. Every time I am using a box that is running the bleeding edge, I *never* run 'apt-get dist-upgrade'. Instead...

2. I usually run Synaptic, click on "Mark all updates", then analyse what Synaptic tells me -- and every so often I cancel *all* changes, and go hunting for the, huh, bad, update(s), until I reach the one(s) that propose to remove what I want to keep -- then I unmark the change(s), and keep on. I guess once burned...

This process can be quite time-consuming if you dist-upgrade every few weeks (a lot of changes to check on worst scenario)... but you will not lose a loved piece of your system :-)

3. Still on Synaptic, after I have have /selected/reviewed all changes I want, I go to "Apply", and -- again -- I check the proposed changes, with special attention on the removal list (usually, if the "to be removed" list header is not bold, then I just go ahead and commit). Otherwise I again check what will be removed. I guess, sigh, twice burned, etc, etc.

In fact, while I was typing this response, I went into Synaptic and ran an update/mark all changes (so that I could get the actual headers), and found one library being removed. I cancelled all changes, searched for the culprits, and found that the update proposing the library removal was doing so because it was also requesting a new package version of the library to be installed.

So... this is, I guess, it. Please tell me if you consider my answer satisfactory (or go ahead and close this bug, if this is the case).

I thought as much! As long as people get evolution at the end who cares..

I was using update manager which I think hides more from you. Apt-get from the command line is probably saner.

I'll close this now - thanks!

update-manager will ask you if you want to dist-upgrade using an extra dialog, if you don't validate this one it'll do a standard upgrade