Package: libgeda20
Version: 20060906-2
Severity: serious

Hi Hamish,

So looking at libgeda for bug #400252 brings another RC bug to my attention:
you have not been changing your library package name in keeping with the
soname changes of this library, and the shlibs provided by libgeda reference
this same, unchanging package name, which means any packages built against
an older version of the package will be installable but broken when a new
soname of the lib is available.

Evidently you've worked around this in all the in-archive packages that
depend on libgeda by adding versioned conflicts each time a new version of
libgeda comes out, which explains some of the other release-critical bugs
I've seen in the past.  This is technically sound for those packages in
Debian, albeit high-maintenance and aesthetically displeasing; but shlibs
files must contain sufficient information that *others* get correct
dependencies when linking against your library as well, which is currently
not the case.

In addition, since there are no file overlaps between subsequent versions of
libgeda, this breaks co-installability of packages built against different
versions of libgeda for no apparent reason.  If there *were* file conflicts
between the different versions, I would say that your use of Provides: is a
perfectly reasonable technical solution and that the only thing in need of
fixing is the shlibs file, but as it stands I think this is a gratuitous
deviation from Debian library best practices.  Please fix libgeda so that
the library package name matches the soname, and update the shlibs to match. 
Although this does mean new upstream versions of libgeda will have to go
through the NEW queue, it also should require much less packaging work on
the whole when updating...

The library package name is not a release-critical issue, BTW, so if you
insist on keeping this package name, geda won't be kicked from the release
because of it.  But the shlibs do need to be fixed.

Thanks,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/


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

Reply via email to