[Evolution] bugs #328968 #328970 #329811 #330561

[Lawrence Walton]

Hi I've been taking care of the evolution-exchange packages, and am
effected by the libdb4.x transition. I've also been stung by bug
#329811.

I spent time looking at the best solution to the libdb4.x issues
and have six changes for evolution-data-server_1.2.3 and one for
evolution/evolution-dev. I also have a observation, and a question.


evolution-data-server

Changes and patches to the evolution-data-server_1.2.3: bumped libdb
versions in control and control.in to libdb4.3-dev and removed
debian/patches/02_system_db.patch. I split 02_system_db.patch into three
separate patches. Mostly for my own convenience. Last I updated the
control and control.in files to reflect libdb4.3.


* baseConfigure.patch This is a updated patch adding references to 4.3
instead of 4.2, based on 02_system_db.patch.

* baseMakefile.in.patch Pretty much exactly like 02_system_db.patch.

* libedataserverMakefile.am.patch The lone completely new change.

* libedataserverMakefile.in.patch Updated patch adding references to 4.3
instead of 4.2, based on 02_system_db.patch.

* evolution-data-server.control.patch bumps versions up to libdb4.3-dev
for evolution-data-server and libedataserver1.2-dev

* evolution-data-server.control.in.patch bumps versions up to
libdb4.3-dev for evolution-data-server and libedataserver1.2-dev


evolution

Last I added a dependency to evolution-dev for libdb4.3 amazingly
enough, it brakes evolution-dev without it.

evolution's phantom dependency.

I've yet to see evolution's dependency with libsoup2.2-7 as a bug
against evolution. I did the same thing that Takuo did, un-installed
2.2-7 and re-created the package. Some how the Debian build tools still
picked up the fact that 2.2-7 still had files left on the system, even
though it seemed un-installed.

* Which lead to the strange problem of not being able to install the
package I had just created it on.

I purged libsoup-2.2-7 and rebuilt evolution making sure only to have
libsoup-2.2-8 installed.

This fixed the problem.

A question!

Would making libsoup-dev depend on a specific version of libsoup fix this 
problem?

Patches will come as separate emails. I will eventually get them into svn
if everyone agrees that these patches are a good idea.

But not today.

Comments, flames, suggestions, are welcome and hoped for.
I've cc'd the libdb maintainer. 




-- 
*--* Mail: lawrence at otak.com
*--* Voice: 425.739.4247
*--* Fax: 425.827.9577
*--* HTTP://the-penguin.otak.com/~lawrence
--------------------------------------
- - - - - - O t a k  i n c . - - - - - 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-evolution-maintainers/attachments/20051003/765e08d2/attachment-0001.pgp