Drop python3-bloom from ros-dev-tools RPM variant#9
Conversation
claraberendsen
left a comment
claraberendsen
left a comment
There was a problem hiding this comment.
I think we might be closer to be able to have bloom on EPEL once we move to vcs2l. @leander-dsouza has a PR open to make vcs2l a replacement of vcstools on bloom.
However it makes sense to exclude it if there is no support for bloom in EPEL, it might have been wishful thinking it's inclusion.
| # Bloom is not currently supported in Fedora/EPEL due to vcstools | ||
| # Requires: python3-bloom |
There was a problem hiding this comment.
I think this might be solved once we merge and test this ros-infrastructure/vcs2l#43 and shift to vcs2l.
There was a problem hiding this comment.
I agree, I think we're pretty close. We did run into issues in the T&T party that would be solved by having this package available, and I think we hit them in Kilted as well.
I'm optimistic we'll land the Bloom stuff soon but I want to hedge bets and get this in so we can update the documentation before Lyrical releases.
2 participants
This package has never worked due to the lack of bloom, and I think we should stop waiting for that to materialize.