The subject has all the information. Revbumping dev-python/flask-migrate to current 2.5.2 fixes it. Reproducible: Always
Nothing needs to be fixed. =dev-db/pgadmin4-4.13 depends on >=dev-python/flask-migrate-2.4.0 and =dev-python/flask-migrate-2.5.2 resolves that dependency just fine. What you call a "revbump" here is unclear: Normally that means changing the revision of an ebuild after changing what the ebuild installs or depends on, but in this case you seem to use it as a verb that describes changing a dependency atom in the ebuild.
(In reply to Jeroen Roovers from comment #1) > Nothing needs to be fixed. > > =dev-db/pgadmin4-4.13 depends on >=dev-python/flask-migrate-2.4.0 and > =dev-python/flask-migrate-2.5.2 resolves that dependency just fine. > > What you call a "revbump" here is unclear: Normally that means changing the > revision of an ebuild after changing what the ebuild installs or depends on, > but in this case you seem to use it as a verb that describes changing a > dependency atom in the ebuild. I see that dev-python/flask-migrate-2.5.2 is in the tree now. So now pgdamin4 installs for me, no changes necessary.