That workaround wouldn't work in Landscape for many configurations; we can't assume pocket names as many use custom mirrors or repository snapshots in which the pocket may not match.
It seems to me there is no simple way to resolve this automatically in Landscape, but as that upgrade situation is both infrequent, noisy, and is easy to resolve manually, the real workaround for landscape is to install those versions manually when that case happens. Other than that, managing sources lists to limit them to -security after deployment is the only other simple way to ensure that situation does not happen with landscape. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788486 Title: apt behaviour with strict dependencies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1788486/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
