Sync evolution-data-server3 3.0.0-1 (universe) from Debian experimental (main)

[Mathieu Trudel-Lapierre]

Please sync evolution-data-server3 3.0.0-1 (universe) from Debian experimental (main)

All changelog entries:

evolution-data-server3 (3.0.0-1) experimental; urgency=low

  * Rename source package to allow parallel installation/migration for
    libedataserverui.
  * New upstream stable release.
  * 01_calendar_exit.patch: stolen upstream. Fix a process not exiting
    at the end of the session.
  * Fix short description for libcamel.
  * Automatically generate better shlibs for libcamel.
  * Tighten dependencies on libcamel and e-d-s-common.

 -- Josselin Mouette <email address hidden> Sun, 10 Apr 2011 10:55:32 +0200

[Bhavani Shankar (bhavi)]

Hello Matthieu,

if its intended to go to universe, Then you being a MOTU yourself can subscribe archive admins right?

Please correct me if I am wrong.

Regards

[Daniel Holbach (dholbach)]

ACKed.

[Mathieu Trudel-Lapierre (cyphermox)]

No, this is expected to go into main as it replaces evolution-data-server directly. The source package was renamed in Debian to facilitate transition.

[Mathieu Trudel-Lapierre (cyphermox)]

After further discussion with seb128 and the guys in #debian-gnome, we'll instead merge the changes from evolution-data-server3 into evolution-data-server now and won't need a sync.

<seb128> Np237, hey, could you give some details on how the e-d-s source rename is leading to easier transitions? both source build the same binaries so they can't be both working or I'm missing something?
<Np237> Only the differing binaries will remain from e-d-s
<Np237> The bulk of the new versions will be in e-d-s3
<Np237> I checked that at least g-panel linked with the old libedataserverui works with the new e-d-s
<seb128> do you need different sources for that? wouldn't the NBS binaries just stay available until they have no rdepends?
<seb128> cyphermox, ^ btw
<seb128> cyphermox, we should sort that before deciding the sync the new source name, renaming sources create quite some issues for the bugs tracking, vcs, etc
<seb128> Np237, can testing have 2 sources building common binaries? sorry it's not clear to me what the rename bring. do you plan to rename back to e-d-s after the transition?
<Np237> yes and yes
<Np237> I checked with the RT
<Np237> Of course otherwise it wouldn’t make any sense
<seb128> Np237, ok thanks