Your message dated Fri, 01 Dec 2006 14:17:14 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#400307: fixed in libgeda 20061020-3
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
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/


--- End Message ---
--- Begin Message ---
Source: libgeda
Source-Version: 20061020-3

We believe that the bug you reported is fixed in the latest version of
libgeda, which is due to be installed in the Debian FTP archive:

libgeda-dev_20061020-3_amd64.deb
  to pool/main/libg/libgeda/libgeda-dev_20061020-3_amd64.deb
libgeda20_20061020-3_amd64.deb
  to pool/main/libg/libgeda/libgeda20_20061020-3_amd64.deb
libgeda_20061020-3.diff.gz
  to pool/main/libg/libgeda/libgeda_20061020-3.diff.gz
libgeda_20061020-3.dsc
  to pool/main/libg/libgeda/libgeda_20061020-3.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hamish Moffatt <[EMAIL PROTECTED]> (supplier of updated libgeda package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat,  2 Dec 2006 00:56:16 +1100
Source: libgeda
Binary: libgeda20 libgeda-dev
Architecture: source amd64
Version: 20061020-3
Distribution: unstable
Urgency: low
Maintainer: Hamish Moffatt <[EMAIL PROTECTED]>
Changed-By: Hamish Moffatt <[EMAIL PROTECTED]>
Description: 
 libgeda-dev - GNU EDA -- Electronics design software -- development files
 libgeda20  - GNU EDA -- Electronics design software -- library files
Closes: 400307
Changes: 
 libgeda (20061020-3) unstable; urgency=low
 .
   * Improved versioning scheme again!(?). No longer provides: libgeda-NN (27).
     shlibs file now specifies that dependent packages should depend on this
     upstream version only, and not work with any future one.
     (Closes: #400307)
   * Conflicts: with existing application packages before 20061020-2, but
     the conflicts listing should not need to be updated again.
   * Replaced remaining references to libgdgeda with libgd2-xpm-dev in
     debian/control
Files: 
 7315557e169b393d30a2bad35e62576a 759 electronics optional 
libgeda_20061020-3.dsc
 d56e4f5b5b259b28c032897d44a7fd84 4763 electronics optional 
libgeda_20061020-3.diff.gz
 31f75f951683ca56cdad7f6c3985044e 207286 electronics optional 
libgeda20_20061020-3_amd64.deb
 419081241bc5edb91a7d2bdeebcb84f4 235790 electronics optional 
libgeda-dev_20061020-3_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iQCVAwUBRXA2M9iYIdPvprnVAQLRaAP7BihdwzdggZm0CefbO5a+6oOiN4UcQTkR
05Z0F0H+vrVDbjnJF4WRXGdwdBsmQvnxhAD/dtK8MDlmd5FsF5SGAvlIvlq8MRB4
/uwqRL9x2AdYucLYUIT2PY6aMbs9aQE/edij8ZkSrYqpbA6YRWmsSAR6J4ghI7rr
ayvj9+POhLU=
=PJMN
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to