I agree and will change the one in stonking-proposed, that way if there
is any implication to mismatches/dependencies it would flag on excuses.
Once it migrates it carries being in multiverse with it into stonking-
release (= lots of words for why I'm not changing 3.3.4-1 in -release).
./change-override -c multiverse -s stonking-proposed --source-and-binary scrcpy
Override component to multiverse
scrcpy 4.0-1 in stonking: universe/misc -> multiverse
scrcpy 4.0-1 in stonking amd64: universe/net/optional/100% -> multiverse
scrcpy 4.0-1 in stonking amd64v3: universe/net/optional/100% -> multiverse
scrcpy 4.0-1 in stonking arm64: universe/net/optional/100% -> multiverse
scrcpy 4.0-1 in stonking armhf: universe/net/optional/100% -> multiverse
scrcpy 4.0-1 in stonking ppc64el: universe/net/optional/100% -> multiverse
scrcpy 4.0-1 in stonking riscv64: universe/net/optional/100% -> multiverse
scrcpy 4.0-1 in stonking s390x: universe/net/optional/100% -> multiverse
Override [y|N]? y
8 publications overridden.
** Changed in: scrcpy (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2148208
Title:
scrcpy: please move to multiverse
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scrcpy/+bug/2148208/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
