Your message dated Tue, 14 Nov 2006 09:46:27 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#398488: libgecode7-dev should be libgecode8-dev to match
SONAME
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: gecode
Severity: serious
The source package as exists in Debian generates a libgecode8 binary
package that contains, as one would expect, a libgecode.so.8 library.
Yet the matching development binary package is named libgecode7-dev,
while it contains a libgecode.so that links to libgecode.so.8
There's no mention of any specialness in the changelog, so I assume this
is simply a case of forgetting to change the -dev package name?
--- End Message ---
--- Begin Message ---
On Tue, Nov 14, 2006 at 02:52:03AM +0000, Scott James Remnant wrote:
> Yet the matching development binary package is named libgecode7-dev,
> while it contains a libgecode.so that links to libgecode.so.8
The numbers in -dev packages are bumped with API changes and the
libraries' numbers are bumped with ABI changes. There's no reason why
they should correspond to each other.
> There's no mention of any specialness in the changelog, so I assume this
> is simply a case of forgetting to change the -dev package name?
* Added a default value for prop_bnd in int/distinct.hh to maintain API
compatibility.
Feel free to reopen this bug if you find that API had changed between
1.3.0 and 1.3.1.
--- End Message ---
