then you have to remove the runtime dependency, won't migrate:

totem-pl-parser (3.10.6-1ubuntu1 to 3.10.6-4ubuntu2)
Maintainer: Ubuntu Developers
0 days old
autopkgtest for tracker/1.9.1-2ubuntu1: amd64: Pass, armhf: Pass, i386: Pass, 
ppc64el: Pass, s390x: Ignored failure
Invalidated by dependency
Depends: totem-pl-parser libquvi (not considered)
Not considered


** Also affects: totem (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: totem (Ubuntu)
   Importance: Undecided => High

** Changed in: totem (Ubuntu)
    Milestone: None => ubuntu-16.09

** Changed in: totem (Ubuntu)
     Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop)

** Package changed: totem (Ubuntu) => totem-pl-parser (Ubuntu)

** Changed in: totem-pl-parser (Ubuntu)
     Assignee: Ubuntu Desktop (ubuntu-desktop) => (unassigned)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libquvi in Ubuntu.
https://bugs.launchpad.net/bugs/1547395

Title:
  MIR: new dependencies for libquvi-scripts / libquvi

Status in libquvi package in Ubuntu:
  Invalid
Status in libquvi-scripts package in Ubuntu:
  Invalid
Status in lua-bitop package in Ubuntu:
  Invalid
Status in lua-expat package in Ubuntu:
  Invalid
Status in lua-json package in Ubuntu:
  Invalid
Status in luasocket package in Ubuntu:
  Invalid
Status in totem-pl-parser package in Ubuntu:
  New

Bug description:
  MIR: new dependencies for libquvi-scripts / libquvi

  libquvi is owned by the desktop team, but not libquvi-scripts. Please
  subscribe to it.

  libquvi-scripts gained runtime dependencies on some lua packages which
  need the MIR:

  luasocket, lua-json, lua-expat, lua-bitop

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libquvi/+bug/1547395/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to