touch-packages team mailing list archive

[Marco Trevisan (Treviño) <mail@xxxxxxxxx>]

** Changed in: unity
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1193120

Title:
  unity-common is not common

Status in Unity:
  Fix Released
Status in “unity” package in Ubuntu:
  Fix Released

Bug description:
  Update-manager is unable to calculate upgrades within saucy today,
  because libunity-core-6.0-5 has to be removed.  The reason for this
  is:

    Package: libunity-core-6.0-5
    Depends: [...] unity-common (= 7.0.0daily13.06.07-0ubuntu1)

   Package: libunity-core-6.0-6
   Depends: [...] unity-common (= 7.0.0daily13.06.19-0ubuntu1)

  Installing libunity-core-6.0-6 as a dependency requires upgrading
  unity-common, which implies removing libunity-core-6.0-5 due to
  unsatisfiable dependencies.

  update-manager cannot distinguish between this kind of "ok" removal
  from other kinds of "unsatisfied dependencies" removals that are not
  ok.  Furthermore, having a strict versioned dependency on a "common"
  package undermines the fundamental purpose of having a library package
  that changes names on soname change - namely, coinstallability.

  I think if these libraries are not going to be coinstallable, it would
  be better to have the contents of unity-common moved directly into
  libunity-core-6.0-x, and have each runtime library package
  Provide/Conflict/Replace unity-common.  This will have the same effect
  in terms of the overall set of packages installed, with the benefit
  that update-manager should be ok with the removal of the old library
  package versions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1193120/+subscriptions