Hi,
Am Samstag 08 März 2008 23:09:40 schrieb Cesare Tirabassi:
> >Since debian currently ships the binary libgdamm3.0-8 (probably, to avoid
> > ABI breakage by using a different binary package name)
>
> No, they just changed the name to have it similar to the old 1.3 branch.
> They have not yet packaged the new version (where we have seen the ABI
> breakage).
Ah, ok.
>
> >ubuntu has libgdamm-3.0-8 and the new version has a different SONAME, no
> > dummy package or conflicts/replaces are necessary at all.
>
> OK, but you still want to remove 3.0-8 don't you,
Yes.
> and so for the
> transition to 3.0-9 you need a dummy package (and yes, you don't need
> conflicts/replaces).
No. Let me try to explain it again: For the upgrade path, you must always
consider what can happen at the *users* system. Hence a package removed from
the archive, means, that it can still be present on a users system during
upgrading.
Now, a dummy package makes sense, if a binary package was renamed, and
provided the same functionality as the old one, because then on the users
system the new binary package will get installed, when upgrading to the dummy
package.
For a library, where the ABI breaks, however it would be fatal to add a
package with conflicts/replaces or a dummy package: On the users system, an
application linked against the old shared object (let's call it libfoo.so.1),
would require to have libfoo.so.1 present, and would not run without it. A
dummy package, to which libfoo1 could get upgraded prior to upgrading the
application linked against it, would of course not contain this very shared
object. Since the SONAME is different in the new libfoo library package,
there would be a libfoo.so.2 (for example) in there, so it also wouldn't make
the application work (rightfully so, because the ABI changed).
I hope this explanation was better than my first try. Please ask, if s.th. is
not yet clear.
Cheers,
Stefan.
--
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
