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 [[1]], the package was never imported neither built. Later, somebody wanted to use rubygem-connection_pool, so there was other review [[2]]. 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 [[3]]. Somebody later noticed and retired the rubygem-connection-pool package [[4]], 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 future.
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.
[1]: https://bugzilla.redhat.com/show_bug.cgi?id=967334 [2]: https://bugzilla.redhat.com/show_bug.cgi?id=1267328 [3]: https://koji.fedoraproject.org/koji/packageinfo?packageID=16736 [4]: https://src.fedoraproject.org/rpms/rubygem-connection-pool/commits/master ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7523
The status of the issue: `rubygem-connection_pool mess` of project: `releng` has been updated to: Closed as Fixed by syeghiay.
syeghiay added a new comment to an issue you are following: `` This has been fixed. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7523
vondruch added a new comment to an issue you are following: ``
This has been fixed.
Would you mind providing more details about the fix? The rubygem-connection_pool is still available in Fedora while the repo is still empty. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7523
syeghiay added a new comment to an issue you are following: `` @mohanboddu , please provide more info on fix. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7523
The status of the issue: `rubygem-connection_pool mess` of project: `releng` has been updated to: Open by vondruch.
churchyard added a new comment to an issue you are following: `` Technically, rubygem-connection-pool is retired and rubygem-connection_pool has never been imported and built. If you wish to maintain it, I suggest following the nonrepsonsive maintainer procedure on rubygem-connection_pool maintainers. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7523
vondruch added a new comment to an issue you are following: `` @churchyard You are trying to solve just consequences, but ignores the fact, that the package should have been retired together with the repository. So there should not be rubygem-connection_pool in Fedora ATM. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7523
churchyard added a new comment to an issue you are following: `` I see, rubygem-connection_pool 2.2.0-2.fc24 is still in the repo (source rubygem-connection_pool-2.2.0-2.fc24).
I guess the cause is that we allow to build rubygem-connection_pool source package from rubygem-connection-pool repository. rubygem-connection-pool is bloxcked in koji, but rubygem-connection_pool is not.
i.e. it seems that if I take any of my retired packages and I push a custom kernel.spec in it, I will be able to build kernel from a retired package scm. ``
To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7523
rel-eng@lists.fedoraproject.org
-
Miro Hrončok -
Suzanne Yeghiayan
-
Vít Ondruch