Has this issue been raised with upstream horizon?
Due to the new pip resolver, conflicts between constraints and requirements cause a build failure. One option would be to lock down the upstream horizon source to a particular SHA and apply a source patch that updates the requirements.txt to override the requirement: https://opendev.org/openstack/horizon/src/commit/6f0200032d5fb26784c0ce1428ae0cad84ef058f/requirements.txt#L15
This could be done with SOURCE_PATCHES added to the stx-horizon.stable_docker_image directives file, similar to the DOCKER_PATCHES done in: https://opendev.org/starlingx/oidc-auth-armada-app/src/branch/master/dex/centos/dex.stable_docker_image
Has this issue been raised with upstream horizon?
Due to the new pip resolver, conflicts between constraints and requirements cause a build failure. One option would be to lock down the upstream horizon source to a particular SHA and apply a source patch that updates the requirements.txt to override the requirement: /opendev. org/openstack/ horizon/ src/commit/ 6f0200032d5fb26 784c0ce1428ae0c ad84ef058f/ requirements. txt#L15
https:/
This could be done with SOURCE_PATCHES added to the stx-horizon. stable_ docker_ image directives file, similar to the DOCKER_PATCHES done in: /opendev. org/starlingx/ oidc-auth- armada- app/src/ branch/ master/ dex/centos/ dex.stable_ docker_ image
https:/