Hoy, So Gnocchi gate is all broken (agaiiiin) because it depends on "pbr" and some new release of oslo.* depends on pbr!=2.1.0.
Neither Gnocchi nor Oslo cares about whatever bug there is in pbr 2.1.0 that got in banished by requirements Gods. It does not prevent it to be used e.g. to install the software or get version information. But it does break anything that is not in OpenStack because well, pip installs the latest pbr (2.1.0) and then oslo.* is unhappy about it. So I understand the culprit is probably pip installation scheme, and we can blame him until we fix it. I'm also trying to push pbr 2.2.0 to avoid the entire issue. But for the future, could we stop updating the requirements in oslo libs for no good reason? just because some random OpenStack project hit a bug somewhere? For example, I've removed requirements update on tooz¹ for more than a year now, which did not break *anything* in the meantime, proving that this process is giving more problem than solutions. Oslo libs doing that automatic update introduce more pain for all consumers than anything (at least not in OpenStack). So if we care about Oslo users outside OpenStack, I beg us to stop this crazyness. If we don't, we'll just spend time getting rid of Oslo over the long term… My 2c, Cheers, ¹ Unless some API changed in a dep and we needed to raise the dep, obviously. -- Julien Danjou # Free Software hacker # https://julien.danjou.info
signature.asc
Description: PGP signature
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
