Summary: | dev-python/pbr-5.11.1: fails to build (configure phase) with dev-python/packaging-23.0 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rémi Cardona <remi2402> |
Component: | Current packages | Assignee: | Matthew Thode ( prometheanfire ) <prometheanfire> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | mgorny, openstack, python |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 891359 |
Description
Rémi Cardona
2023-02-03 06:45:59 UTC
Wondering if this is actually pbr or another package that gets imported. Hard to say, as apparently pbr's main purpose is to monkey patch setuptools and provide extensions for it... So this might be quite the rabbit hole. No bug on the upstream bug tracker (launchpad... so I may have missed something) that I could find. > * dev-python/setuptools : 65.6.3
Here's your culprit. <67 requires <packaging-22, and 65.7.0 (which is the oldest version in ::gentoo) has a correct dep.
I was simply doing: # emerge -DuN @world --changed-deps -av --keep-going like I always do and hit this. So there's a missing/bad dep somewhere? Yes, Portage doesn't aggressively update deps-of-deps *in order* unless there's a constraint somewhere that forces it (which is correct, really). So we need to find somewhere to jam one in, I guess. Simply not having bad versions in tree anymore isn't sufficient. |