I confirm the same issue, both for libbz2 and libx11. In the end I 'downgraded' both packages from the leftover resolute updates version to the stonking version and that allowed me to continue. Still, this was an unpleasant experience - in the past I thought I had observed Ubuntu version strings were named so to avoid precisely this kind of conflict. Why should this be considered invalid just because it was an upgrade?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2168687 Title: Version skew in development release: bzip2 strictly depends on libbz2-1.0 (= 1.0.8-6build2), causing multiarch conflicts with 1.0.8-6ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bzip2/+bug/2168687/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
