vondruch reported a new issue against the project: `releng` that you are following:
There is package rubygem-connection_pool, where although the review was finished \[\],
the package was never imported neither built. Later, somebody wanted to use
rubygem-connection_pool, so there was other review \[\]. This was approved (while
unnoticed, there is rubygem-connection_pool already in Fedora) and repository
rubygem-connection-pool was requested (please note the dash instead of underscore in the
repository name). From there, there are coming builds of rubygem-connection_pool here
\[\]. Somebody later noticed and retired the rubygem-connection-pool package \[\],
but really, I am not sure this was the best possible action. There are several concerns:
1. It is not obvious what happened and where the package is coming from. It is surprising,
that the repo request was approved, although it did not match the review.
2. The package is escaping mass rebuilds. Actually I am surprised this kind of
repositories is not detected/reported after rebuild.
3. It is not obvious who is maintaining the package.
For (1) and (2), I hope you can check your tooling and avoid these situations in the
For (3) neither one of the current maintainers is really active. I haven't hear about
@anujmore for past 4 years. I've heard about @axilleas, but I believe he is busy with
other stuff. @ilgrad might still be interested in this package. I can also take the
package over, since it is dependency of Ruby on Rails.
To reply, visit the link below or just reply to this email