Hi Chris, Am Samstag 08 März 2008 04:27:50 schrieb Chris Brotherton: > Stefan, > > Sorry. I wasn't clear in my comment above. I used the > conflicts/replaces fields for the binary package name change and not for > the soname change. > > For example: > > Package: libgdamm3.0-9 > Provides: libgdamm-3.0-9 > Conflicts: libgdamm-3.0-9 (<< ${source:Version}) > Replaces: libgdamm-3.0-9 (<< ${source:Version}) > > New package name: libgdamm3.0-9 > Old package name: libgdamm-3.0-9
Now I'm confused, as I don't see a libgdamm[-]3.0-9 package in either debian/unstable or ubuntu. Since debian currently ships the binary libgdamm3.0-8 (probably, to avoid ABI breakage by using a different binary package name), and ubuntu has libgdamm-3.0-8 and the new version has a different SONAME, no dummy package or conflicts/replaces are necessary at all. 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