Your message dated Wed, 29 May 2013 10:00:16 +0000
with message-id <e1uhdb2-0004tb...@franck.debian.org>
and subject line Bug#708584: fixed in alglib 3.7.0-5
has caused the Debian Bug report #708584,
regarding versioning system/package name allows for binary incompatible 
libraries
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
708584: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=708584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: alglib
Version: 3.7.0-1~exp1
Severity: serious

the version of alglib is 3.7.0. Debian now is assigning a SONAME version of 3.
This is incorrect as it implies all 3.x.x libraries are binary compatible,
which they are not. Upstream changelog explicitly states that not binary 3.7.0
and 3.6.0 are not binary compatible, for example.

When assigning a SONAME version that differs from upstream, use the "debian"
word in the SONAME. For example, 3debian0 would be an appropriate SONAME, but
you would have to keep track of backwards incompatible changes to symbols and
bump the next version when it comes out (e.g. 3debian1). If you don't do this,
you risk making libraries that are incompatible with other distributions and
upstream. That's why the old build system used the "-release @VERSION@" flag
instead of "-version", so ensure that the soname remained blank. You can assign
a SONAME to the library, but please append "debianX" or keep the old system so
we can follow policy 8.2 "The run-time shared library must be placed in a
package whose name changes whenever the SONAME of the shared library changes."
I preferred the old system since I didn't like assigning a SONAME that upstream
was not using.

Other issues, not directly related to this bug, but somewhat at an RC level so
we can take care of it before it migrates to testing:
1) Why was alglib bumped at all? Does another package need it? Why was the new
version uploaded, breaking the only depending package in Debian without first
checking with that package?
2) Why did a team upload switch from autotools to cmake?
3) Why did 1 and 2 happen without consulting with the current uploaders of
alglib or the depending package?



-- System Information:
Debian Release: wheezy/sid
  APT prefers raring-updates
  APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500, 
'raring-proposed'), (500, 'raring'), (100, 'raring-backports')
Architecture: i386 (i686)

Kernel: Linux 3.8.0-20-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message ---
Source: alglib
Source-Version: 3.7.0-5

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

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 708...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anton Gladky <gl...@debian.org> (supplier of updated alglib 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 ftpmas...@debian.org)


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

Format: 1.8
Date: Sun, 26 May 2013 23:34:37 +0200
Source: alglib
Binary: libalglib-dev libalglib3.7 libalglib3.7-dbg
Architecture: source amd64
Version: 3.7.0-5
Distribution: unstable
Urgency: low
Maintainer: Debian Science Team 
<debian-science-maintain...@lists.alioth.debian.org>
Changed-By: Anton Gladky <gl...@debian.org>
Description: 
 libalglib-dev - Development files for the alglib library
 libalglib3.7 - Numerical analysis and data processing library
 libalglib3.7-dbg - Debugging symbols for the alglib library
Closes: 708584
Changes: 
 alglib (3.7.0-5) unstable; urgency=low
 .
   * [d579857] Replace libalglib3 by libalglib3.7 package. (Closes: #708584)
Checksums-Sha1: 
 61253621d25f558039ad3850b6a908dc49916a01 2092 alglib_3.7.0-5.dsc
 c131283cabed692e8e5fc08b9504e11e6964e37a 4904 alglib_3.7.0-5.debian.tar.gz
 eb58774cd317b25b9201d1f9aead1e0260b5a4de 386416 libalglib-dev_3.7.0-5_amd64.deb
 035dce7fbd8b975d3a62dd4f2f0464e19e1526cb 870828 libalglib3.7_3.7.0-5_amd64.deb
 0435a430f8183072e7d0fa344a0e855b9c47d3e3 1825386 
libalglib3.7-dbg_3.7.0-5_amd64.deb
Checksums-Sha256: 
 cb4e012382b90fe7b4ebbe2b07af7eaf41254915540b2596e05517077876f321 2092 
alglib_3.7.0-5.dsc
 ca9e67d1bf8d98934aa89ae2175bbc586327138c6cddde9ea93256fe0057767c 4904 
alglib_3.7.0-5.debian.tar.gz
 199e81c702dca2ddb0c2f52e334b4661958a985daf7ef6e20ad4e93cddfacef7 386416 
libalglib-dev_3.7.0-5_amd64.deb
 d22a7ebd8b7ccbaaf5504a193b3cfd3cba8da9f99bcce00debd79449029978a6 870828 
libalglib3.7_3.7.0-5_amd64.deb
 6d082b010756448243a9fa589a9c0dd83fd5ed8b85dd4ce4a2ae075cf878ce24 1825386 
libalglib3.7-dbg_3.7.0-5_amd64.deb
Files: 
 3a0f611c28799b80006b0182d22f70a2 2092 libs optional alglib_3.7.0-5.dsc
 16a81e54229ba6b7bc27c8deda64908c 4904 libs optional 
alglib_3.7.0-5.debian.tar.gz
 5f70925f7517a3ce0555c54520248d06 386416 libdevel extra 
libalglib-dev_3.7.0-5_amd64.deb
 ddfd83a5b34d38070a5723263a936075 870828 libs optional 
libalglib3.7_3.7.0-5_amd64.deb
 75d1aa9d0fa5d2668575fa28c29aef9f 1825386 debug extra 
libalglib3.7-dbg_3.7.0-5_amd64.deb

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

iQIcBAEBAgAGBQJRoo3BAAoJENPhc4PPp/8GMh8QAINQPyYio2svVs0pRXfTRxoC
NmevIgWqALLP5/eM8gHTUOf8O622oy2XdfCxo+kLu45+xu1DzZqKekxTPl2eAHlW
oNYSBrdorbld66Ce57jj2PvY5hc1SQX5ARt2qoCaDo/3AjVsTDs9iL8W/+VX8qi4
efcKZAIxTIwQfe5VcBKTFU/MG6mYHmAhFvfsAZAudxFW+ZYfmNDCelErv473XMRu
xwz+eCvcvE6/dzZsB5Y7Pmk6Q9f4DdVHQC0z4MlZlNEcAp9ybdE/W0qczBfGIMmz
M+4/Jf0oJibPznmfduQbR7FES55DtJk9/pWE1OHfyiTviLKpbVmn/amTZLaw8/iH
/MOkKAXRsIiht0wVFGOaMWbjl0z5KoeFUVqS4KFCdkSdUV9+mWooJIlsRNPeqxaA
kxpyK00Z46Vz4Cl25VrV91GcbGJ3HeCZiwEGOcRh7dE48HCSm3tpbpeVe4zx2coZ
IopQKVchqNjBJ/mB75W4A0neyhTwTAHtLTUN+O2zsIzpSHsxCpSYi+eTZnLDu4/Z
QlVzG7aucAm3HDfFgLVUYcvaPoYt7l7HqvBSaQKnRTX39AnqNH6s1ETuOMGK2D4s
LxqjUEyKFsqQI1vmYJ5Kp/WeLEDw6tULTDJdIVgkwOB1Lo8SU1wiuTV8ZafnvWXU
a89cGknATgwg3gRolgTk
=IEWo
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to