[Bug 190744] Re: Request: Upgrade libgdamm3.0 to upstream version 2.9.81

Deng Xiyue manphiz at gmail.com
Wed Mar 19 12:02:28 GMT 2008


Chris Brotherton <chris at protonlab.net> writes:

> 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?
>

They should be "Conflicts/Replaces"ed, because they have the same
contents.  Installing them in parallel will fail.  And 2.9.82-0ubuntu1
doesn't have the problem when installed in parallel with
2.9.81-0ubuntu1 is because the soname changed since 2.9.82: The
additional "-".

> 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.
>
> -- 
> Request: Upgrade libgdamm3.0 to upstream version 2.9.81
> https://bugs.launchpad.net/bugs/190744
> You received this bug notification because you are a direct subscriber
> of the bug.

-- 
Request: Upgrade libgdamm3.0 to upstream version 2.9.81
https://bugs.launchpad.net/bugs/190744
You received this bug notification because you are a member of Ubuntu
Sponsors for universe, which is a direct subscriber.



More information about the Ubuntu-universe-sponsors mailing list