[Pkg-gpe-maintainers] Bug#514921: Processed: reassign 514921 to libmimedir0, libmimedir-gnome0-dev

[Neil Williams]

On Wed, 11 Feb 2009 21:51:03 +0000
owner at bugs.debian.org (Debian Bug Tracking System) wrote:

> Processing commands for control at bugs.debian.org:
> 
> > reassign 514921 libmimedir0,libmimedir-gnome0-dev
> Bug#514921: libmimedir0: tries to overwrite file owned by libmimedir-gnome0-dev
> Bug reassigned from package `libmimedir0' to `libmimedir0,libmimedir-gnome0-dev'.
> 

Barry, your upload of libmimedir 0.5.1-1 introduced the relevant file
into libmimedir0 when it does not exist in Lenny:

http://packages.debian.org/lenny/amd64/libmimedir0/filelist
/usr/lib/libmimedir.so.0
/usr/lib/libmimedir.so.0.0.0
/usr/share/doc/libmimedir0/README
/usr/share/doc/libmimedir0/changelog.Debian.gz
/usr/share/doc/libmimedir0/changelog.gz
/usr/share/doc/libmimedir0/copyright

http://packages.debian.org/sid/amd64/libmimedir0/filelist
/usr/lib/libmimedir.a
/usr/lib/libmimedir.so.0
/usr/lib/libmimedir.so.0.0.0
/usr/share/doc/libmimedir0/README
/usr/share/doc/libmimedir0/changelog.Debian.gz
/usr/share/doc/libmimedir0/changelog.gz
/usr/share/doc/libmimedir0/copyright

Why was this file introduced? I don't see that this is a bug in
libmimedir-gnome0-dev, it appears to be a bug in libmimedir0,
specifically libmimedir0 (0.5.1-1) - there's nothing I can see in the
changelog to explain this addition.

There should be no .a file in the library package and there wasn't one
in the -dev in Lenny either (for whatever reason).

Now, whether libmimedir-gnome0-dev should contain /usr/lib/libmimedir.a
and not something like /usr/lib/libmimedir-gnome.a is a different
question. Moray?

IMHO it's far less troublesome for the two -dev packages to conflict.

$ apt-cache rdepends libmimedir0
libmimedir0
Reverse Depends:
  python-rra
  librra0
  librra-tools
  libmimedir-dev

$ apt-cache rdepends libmimedir-gnome0.4
libmimedir-gnome0.4
Reverse Depends:
  libmimedir-gnome0-dev
  libgpevtype1
  gpe-contacts
  gpe-calendar
  gpe-bluetooth

The only extra dependency of the -gnome version is libglib2.0-0 -
python-rra already depends on libglib2.0-0 via a dependency on
libdbus-glib, in turn via http://packages.debian.org/sid/libsynce0, and
http://packages.debian.org/sid/librra0 also depends on libsynce0.

Maybe the best thing would be:

1. Remove /usr/lib/libmimedir.a from libmimedir0 asap.
2. Migrate librra0 and reverse dependencies to libmimedir-gnome0.4
after Lenny
3. Remove the orphaned libmimedir0

Doing that means that the "problem" of /usr/lib/libmimedir.a in
libmimedir-gnome0-dev goes away completely.

-- 


Neil Williams
=============
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
Url : http://lists.alioth.debian.org/pipermail/pkg-gpe-maintainers/attachments/20090211/40a42f6d/attachment.pgp