> Actually, you have it backwards. Initially, ubuntu used the
> libgdamm-3.0-* naming scheme, but we changed it to match debians
> (libgdamm3.0-*). So you should not have to change the binary package
> names in debian.
>
Has this already happened? By searching on http://packages.ubuntu.com/ I haven't found any package named
libgdamm3.0-*, so I guess it's not released yet. Will it be possible
for Ubuntu to remain its naming convention? I've already changed it
in Debian GNOME SVN to add '-'. Please let me know what you plan to
do, and which Conflicts/Replaces field should be added for Ubuntu.
> Murray,
> You don't need to worry about the package names (other than the sonames). Ubuntu just changed the binary package names to match debian. So, in the future, ubuntu can just sync from debian.
>
> --
> 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.
Chris Brotherton <email address hidden> writes:
> Actually, you have it backwards. Initially, ubuntu used the
> libgdamm-3.0-* naming scheme, but we changed it to match debians
> (libgdamm3.0-*). So you should not have to change the binary package
> names in debian.
>
Has this already happened? By searching on packages. ubuntu. com/ I haven't found any package named
http://
libgdamm3.0-*, so I guess it's not released yet. Will it be possible
for Ubuntu to remain its naming convention? I've already changed it
in Debian GNOME SVN to add '-'. Please let me know what you plan to
do, and which Conflicts/Replaces field should be added for Ubuntu.
> Murray, /bugs.launchpad .net/bugs/ 190744
> You don't need to worry about the package names (other than the sonames). Ubuntu just changed the binary package names to match debian. So, in the future, ubuntu can just sync from debian.
>
> --
> Request: Upgrade libgdamm3.0 to upstream version 2.9.81
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.