tags 310606 + patch
thanks

Hi,

The build failure is fixed with this patch:

--- xc.orig/ximian-connector-2.2.2/debian/control       2005-05-24 
18:31:18.293206088 +0100
+++ xc.new/ximian-connector-2.2.2/debian/control        2005-05-24 
19:24:30.691887720 +0100
@@ -2,7 +2,7 @@
 Section: gnome
 Priority: optional
 Maintainer: Lawrence Walton <[EMAIL PROTECTED]>
-Build-Depends: cdbs, debhelper (>= 4.1.0), intltool, evolution-dev (>= 2.2), 
evolution-data-server1.2-dev (>= 1.2), libgnomeprintui2.2-dev, libldap2-dev, 
libkrb5-dev, libdb3-dev, libldap2-dev (>= 2.1.30-2), libedata-book1.2-dev, 
libedata-cal1.2-dev, libecal1.2-dev, libedataserverui1.2-dev, libcamel1.2-dev
+Build-Depends: cdbs, debhelper (>= 4.1.0), intltool, evolution-dev (>= 2.2), 
evolution-data-server1.2-dev (>= 1.2), libgnomeprintui2.2-dev, libldap2-dev, 
libkrb5-dev, libdb4.1-dev, libldap2-dev (>= 2.1.30-2), libedata-book1.2-dev, 
libedata-cal1.2-dev, libecal1.2-dev, libedataserverui1.2-dev, libcamel1.2-dev
 Standards-Version: 3.6.1
 
 Package: evolution-exchange


The package is not lintian clean:

W: evolution-exchange: postinst-has-useless-call-to-ldconfig
W: evolution-exchange: postrm-has-useless-call-to-ldconfig
W: evolution-exchange: binary-or-shlib-defines-rpath 
./usr/lib/evolution-data-server-1.2/camel-providers/libcamelexchange.so 
/usr/lib/evolution/2.2
W: evolution-exchange: binary-or-shlib-defines-rpath 
./usr/lib/evolution/2.2/evolution-exchange-storage /usr/lib/evolution/2.2
W: evolution-exchange: binary-or-shlib-defines-rpath 
./usr/bin/ximian-connector-setup-2.2 /usr/lib/evolution/2.2

You should also fix the rpath warnings with chrpath, and build-depend
on chrpath.  The postinst/rm script also need tweaking, if only to
make them lintian-clean.


Regards,
Roger

-- 
Roger Leigh
                Printing on GNU/Linux?  http://gimp-print.sourceforge.net/
                Debian GNU/Linux        http://www.debian.org/
                GPG Public Key: 0x25BFB848.  Please sign and encrypt your mail.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to