Package: libmimelib1
Version: 4:3.3.0-3
Severity: serious
$ md5sum libmimelib1*
6a5566e8fc95625e417521cf35c358d6 libmimelib1_3.2.3-1_i386.deb
a00edf1dd47f1acc19697989d277edf0 libmimelib1_3.3.0-1_i386.deb
$ dpkg -x libmimelib1_3.2.3-1_i386.deb before
$ dpkg -x libmimelib1_3.3.0-1_i386.deb after
$ objdump -TC before/usr/lib/libmimelib.so.1.0.1 | grep AllFieldBodiesAsString
0001cf60 g DF .text 000000be Base
DwHeaders::AllFieldBodiesAsString(DwString const&)
$ objdump -TC after/usr/lib/libmimelib.so.1.0.1 | grep AllFieldBodiesAsString
$
this obviously leads to broken installations if one upgrades mimelib
without upgrading, e.g., kmail.
* * *
my intention with this bug report is to trigger some discussion among
debian-qt-kde members as if it would make sense to effectively forbid
binary packages of different versions to be installed simultaneously,
since it seems that is what upstream expects.
this would be achieved via conflicts or similar methods, and of course
only for binary packages from a same source package. for example, one
could have the "kdepim-base" (empty) packge on which all kdepim binary
packages would depend on (with = X.Y.Z-d, and "kdepim-base" itself
would conflict all other kdepim packages << X.Y.Z *and* >> X.Y.Z.
if the above is regarded as to cause more grief than it would solve,
reconsider after s/X.Y.Z/X.Y/ in the last line of the above paragraph.
* * *
discussion welcome,
--
Adeodato Simó
EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
Listening to: Luis Eduardo Aute - Dear Peter (Te debo esta canción)
A hacker does for love what other would not do for money.
