Re: Unable to install kde3.1 on unstable
> - --- fam-2.6.9_orig/debian/changelog 2003-01-18 11:51:32.000000000
> +0100
> +++ fam-2.6.9_sv/debian/changelog 2003-01-18 11:59:32.000000000
> +0100 @@ -1,3 +1,9 @@
> +fam (2.6.9-4_1) unstable; urgency=low
> +
> + * added provides and replaces to controlfile
> +
> + -- Sergio Vergata <vergata@stud.fbi.fh-darmstadt.de> Mon, 13 Jan 2003
> 15:47:55 +0100
> +
> fam (2.6.9-4) unstable; urgency=low
>
> * Link the daemon against -lrt and -lpthread for DNotify
> diff -u fam-2.6.9_orig/debian/control fam-2.6.9_sv/debian/control
> - --- fam-2.6.9_orig/debian/control 2003-01-18 11:51:32.000000000
> +0100 +++ fam-2.6.9_sv/debian/control 2003-01-15 12:00:40.000000000 +0100
> @@ -23,7 +23,9 @@
> Section: libs
> Architecture: any
> Depends: ${shlibs:Depends}
> +Provides: libfam0
> Conflicts: libfam0
> +Replaces: libfam0
> Recommends: fam
You should NEVER do this. It's a way to completely break your system.
Maybe doing this with libfam is not as dangerous as with other packages, but
anyway this is completely incorerect and dangerous.
libXXX package contains library with g++2 ABI.
libXXXc102 package contains library with g++3 ABI.
Packages contain same files, but blindly replacing one with other will
render unusable all programs using the library.
In this particular case, any program that is compiled by gcc2 and uses
libfam will crash (most likely with unresolved symbol) on the first attempt
to use any libfam functionality.
libXXXc102 should ALWAYS conflict with libXXX (and NEVER provide it), to
avoid installing g++3 version until there are any packages in the system
that use g++2 version.
Reply to: