I have a question regarding the debian package. In the control file, there is the following entry for the libgdamm3.0-10 binary package:
----------------------------------------------------------------------------------------------
Package: libgdamm3.0-10
Architecture: any
Conflicts: libgdamm3.0-8, libgdamm-3.0-8, libgdamm3.0-9
Replaces: libgdamm3.0-8, libgdamm-3.0-8, libgdamm3.0-9
Depends: ${misc:Depends}, ${shlibs:Depends}
Description: C++ wrappers for libgda3
libgdamm is a set of C++ bindings for the libgda3 database API.
libgda is the GNU Data Access library.
.
This package contains the shared library.
-----------------------------------------------------------------------------------------------------
Based on the discussion above (StefanPotyra et. al.), I was under the impression that there should not be conflicts/replaces fields for a library package with a soname bump since it might lead to breakage. What am I missing?
libgdamm3.0_2.9.82-0ubuntu2 was uploaded yesterday. So the problems with the conflicts/replaces fields for the -dev and -doc binary packages has been corrected. However, having the stable release of the library is probably a good idea.
I have a question regarding the debian package. In the control file, there is the following entry for the libgdamm3.0-10 binary package:
------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ---
libgdamm- 3.0-8,
libgdamm3. 0-9
libgdamm- 3.0-8,
libgdamm3. 0-9
${shlibs: Depends} ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ------- ---
Package: libgdamm3.0-10
Architecture: any
Conflicts: libgdamm3.0-8,
Replaces: libgdamm3.0-8,
Depends: ${misc:Depends},
Description: C++ wrappers for libgda3
libgdamm is a set of C++ bindings for the libgda3 database API.
libgda is the GNU Data Access library.
.
This package contains the shared library.
-------
Based on the discussion above (StefanPotyra et. al.), I was under the impression that there should not be conflicts/replaces fields for a library package with a soname bump since it might lead to breakage. What am I missing?
libgdamm3. 0_2.9.82- 0ubuntu2 was uploaded yesterday. So the problems with the conflicts/replaces fields for the -dev and -doc binary packages has been corrected. However, having the stable release of the library is probably a good idea.