I agree to the reverse dependency only being MIR itself

$ reverse-depends --release resolute src:libxml++2.6
Reverse-Depends
===============
* bibshelf                      (for libxml++2.6-2v5)
* cherrytree                    (for libxml++2.6-2v5)
* gobby                         (for libxml++2.6-2v5)
* libcifti-dev                  (for libxml++2.6-dev)
* libcifti0t64                  (for libxml++2.6-2v5)
* libmirwayland-bin             (for libxml++2.6-2v5)
* libsynfig-dev [amd64 amd64v3 arm64 armhf ppc64el riscv64]
* libsynfig0t64 [amd64 amd64v3 arm64 armhf ppc64el riscv64]
* ofx                           (for libxml++2.6-2v5)
* performous [amd64 amd64v3 arm64 armhf ppc64el riscv64]
* pinot                         (for libxml++2.6-2v5)

Packages without architectures listed are reverse-dependencies in:
amd64, amd64v3, arm64, armhf, ppc64el, riscv64, s390x


And of that

rmadison -u ubuntu -s resolute-proposed,resolute bibshelf cherrytree gobby 
libcifti-dev libcifti0t64 libmirwayland-bin libsynfig-dev libsynfig0t64 ofx 
performous pinot
 bibshelf          | 1.6.0-0ubuntu10    | resolute/universe          | source, 
amd64, amd64v3, arm64, armhf, ppc64el, riscv64, s390x
 cherrytree        | 1.2.0+dfsg-1build2 | resolute/universe          | source, 
amd64, amd64v3, arm64, armhf, ppc64el, riscv64, s390x
 gobby             | 0.6.0-3build1      | resolute/universe          | source, 
amd64, amd64v3, arm64, armhf, ppc64el, riscv64, s390x
 libcifti-dev      | 1.6.0-6            | resolute/universe          | amd64, 
amd64v3, arm64, armhf, ppc64el, riscv64, s390x
 libcifti0t64      | 1.6.0-6            | resolute/universe          | amd64, 
amd64v3, arm64, armhf, ppc64el, riscv64, s390x
 libmirwayland-bin | 2.20.2-2ubuntu8    | resolute                   | amd64, 
amd64v3, arm64, armhf, ppc64el, riscv64, s390x
 libmirwayland-bin | 2.25.2-3           | resolute-proposed          | amd64, 
amd64v3, arm64, armhf, ppc64el, riscv64, s390x
 libsynfig-dev     | 1.5.3+dfsg-1       | resolute/universe          | amd64, 
amd64v3, arm64, armhf, ppc64el, riscv64
 libsynfig0t64     | 1.5.3+dfsg-1       | resolute/universe          | amd64, 
amd64v3, arm64, armhf, ppc64el, riscv64
 ofx               | 1:0.10.9-1.1build3 | resolute/universe          | amd64, 
amd64v3, arm64, armhf, ppc64el, riscv64, s390x
 performous        | 1.3.1+ds-3ubuntu2  | resolute/universe          | source, 
amd64, amd64v3, arm64, armhf, ppc64el, riscv64
 performous        | 1.3.1+ds-4         | resolute-proposed/universe | source
 pinot             | 1.23-1             | resolute/universe          | source, 
amd64, amd64v3, arm64, armhf, ppc64el, riscv64, s390x

Demoting 2.6 for promoting 5.0 seems fine.
Is MIR otherwise ready to move and this the last thing holding it back?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2146982

Title:
  [MIR] libxml++-5.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxml++-5.0/+bug/2146982/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to