<div dir="ltr"><div class="gmail_extra">Hi,<br><br></div><div class="gmail_extra">I have done this upload, sorry if I broke something or <span lang="en"><span>offended</span></span> somebody.<br>
</div><div class="gmail_extra"><br></div><div class="gmail_extra"><div class="gmail_quote">2013/5/16 Scott Howard <span dir="ltr"><<a href="mailto:showard@debian.org" target="_blank">showard@debian.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Package: alglib<br>
Version: 3.7.0-1~exp1<br>
Severity: serious<br>
<br>
the version of alglib is 3.7.0. Debian now is assigning a SONAME version of 3.<br>
This is incorrect as it implies all 3.x.x libraries are binary compatible,<br>
which they are not. Upstream changelog explicitly states that not binary 3.7.0<br>
and 3.6.0 are not binary compatible, for example.<br>
<br>
When assigning a SONAME version that differs from upstream, use the "debian"<br>
word in the SONAME. For example, 3debian0 would be an appropriate SONAME, but<br>
you would have to keep track of backwards incompatible changes to symbols and<br>
bump the next version when it comes out (e.g. 3debian1). If you don't do this,<br>
you risk making libraries that are incompatible with other distributions and<br>
upstream. That's why the old build system used the "-release @VERSION@" flag<br>
instead of "-version", so ensure that the soname remained blank. You can assign<br>
a SONAME to the library, but please append "debianX" or keep the old system so<br>
we can follow policy 8.2 "The run-time shared library must be placed in a<br>
package whose name changes whenever the SONAME of the shared library changes."<br>
I preferred the old system since I didn't like assigning a SONAME that upstream<br>
was not using.<br></blockquote><div><br></div><div>Ok, if you want, I will create libalglib3.7.0. But I do not know, whether it is necessary for<br></div><div>the package, having just qtiplot in build-rdeps and with popcon 33. But you are the <br>
main maintainer, you should decide.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Other issues, not directly related to this bug, but somewhat at an RC level so<br>
we can take care of it before it migrates to testing:<br>
1) Why was alglib bumped at all? </blockquote><div><br></div><div>Why, actually, the version 2.6.0 has been uploaded into Debian on "06 Mar 2011", <br></div><div>if it was half a year obsolete and unsupported by upstream? The version 3.3.0 was <br>
</div><div>already available [1]. <br></div><div></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Does another package need it? </blockquote>
<div><br></div><div>Yes, not (yet) uploaded into Debian.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Why was the new<br>
version uploaded, breaking the only depending package in Debian without first<br>
checking with that package?<br></blockquote><div><br></div><div>It was my fault, sorry. And I wrote you an email about that and fixed an issue already. </div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
2) Why did a team upload switch from autotools to cmake?<br></blockquote><div><br></div><div>3-versions are completely different from 2-vesions. It was rewritten from scratch.<br></div><div>And yes, personal preferences. Why did you ask about that after uploading the<br>
package?<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
3) Why did 1 and 2 happen without consulting with the current uploaders of<br>
alglib or the depending package?<br><br></blockquote><div>That is not true and I am surprised, that you decided to discuss it here:<br> 1) I sent you and your co-maintainer an email with patches on alglib on April 26th.<br>
</div><div> 2) May 5th the package has been uploaded into experimental.<br></div></div> 3) May 15th, the package has been uploaded into unstable.<br><br></div><div class="gmail_extra">The first communication with you was on May 16th. <br>
<br>So I think, the second part of the bug is not RC.<br></div><div class="gmail_extra">Again, sorry, if I broke something. I will try to be careful next time and ready for co-maintaining.<br></div><div class="gmail_extra">
<br></div><div class="gmail_extra">
<br></div><div class="gmail_extra">Cheers,<br><br>Anton<br><br>[1] <a href="http://www.alglib.net/arcnews.php#date_06_03_2011" target="_blank">http://www.alglib.net/arcnews.php#date_06_03_2011</a><br></div></div>