Dependency on libdouble-conversion1 causes conflict

Bug #1649156 reported by Marko Stanković
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
double-conversion
Invalid
Undecided
Unassigned
qtdeclarative-opensource-src (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Hi,

Since this change:
https://launchpadlibrarian.net/295556379/double-conversion_2.0.1-3ubuntu2_2.0.1-4ubuntu1.diff.gz

libdouble-conversion1 breaks libdouble-conversion1v5 and since this change:
https://launchpadlibrarian.net/296573650/qtdeclarative-opensource-src_5.6.1-7ubuntu2~1_5.6.1-7ubuntu2~2.diff.gz

I have a conflict on Zesty with 2 resolutions:
1. Keep libqt5qml5 unupdated
2. Remove libdouble-conversion1v5 and install libdouble-conversion1
What should I do and isn't v5 meant to replace the original libdouble-conversion1?

Cheers,
Marko

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

The name was changed back to libdouble-conversion1.

So please choose the second variant.
This is not a bug, so closing.

Changed in qtdeclarative-opensource-src (Ubuntu):
status: New → Invalid
Changed in double-conversion:
status: New → Invalid
Revision history for this message
Marko Stanković (sm4rk0) wrote :

Thanks Dmitry, I did so. I know this is a development version of Ubuntu and rough edges like are to normal, but can't this transition be done without conflict in package management? Is there a general document describing the GCC5 transition and the future of *v5 packages, aside from these two [1][2] outdated pages, so users can know which variant to keep in situations like this?
1: https://wiki.debian.org/GCC5
2: https://wiki.ubuntu.com/GCC5

Revision history for this message
Dmitry Shachnev (mitya57) wrote :

Sorry for the late response.

This is not a conflict. The library package is usually installed automatically as a dependency of some other package, not manually. So when all reverse dependencies are update to use the new library package name, the package manager will remove the old library and install the new one.

The library was renamed to v5 in Ubuntu, but not in Debian. In Zesty the package was re-synchronized with Debian, so the library got renamed back to its old name. The pages you linked were for the first renaming, which is no longer relevant.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.