On Sun, 19 Feb 2017 16:43:39 -0800 Adam Williamson <adamwill@xxxxxxxxxxxxxxxxx> wrote: > It's nothing new, this is how Python has always worked, all the way > back to 2.x (not sure about 1.x). Minor release versions always bump > the ABI. I've never noticed it before. It seems counter intuitive to me, like bumping a library so number without raising the version number. I suppose there must be a reason. > I'd just do a --best --allowerasing and see what it's actually blocked > on. There aren't actually many things left that aren't rebuilt for > Python 3.6 at this point, and most of the ones that are left are > pretty obscure. You can see the list in every 'rawhide compose > report' mail, as it lists all packages whose dependencies cannot be > resolved. Most of the issues in the current Rawhide compose are > actually with boost. Thanks, this should be helpful. If I can delete just a few packages, and get the update to succeed, then I can re-install them when they get updated. Yeah, I think I noticed boost in the list of problems dnf produced. _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
