#10730 Mass "add to admin" needed for some rubygems
Closed: Fixed 2 years ago by humaton. Opened 2 years ago by tdawson.

  • Describe the issue
    Vit (vondruch) is the Fedora maintainer for a large number of rubygem packages. He does not want to maintain them in EPEL.
    Troy (tdawson) is willing to be the co-maintainer for those rubygems, specifically for EPEL.
    Due to the number of packages, it is impractical for Vit to go through them all and set tdawson as co-maintainer, and to have the EPEL bugzilla assignee be set to tdawson.

Please set tdawson as a co-maintainer, and as the EPEL bugzilla assignee for the following packages.

rubygem-activemodel
rubygem-activesupport
rubygem-Ascii85
rubygem-backports
rubygem-bacon
rubygem-coffee-script
rubygem-coffee-script-source
rubygem-connection_pool
rubygem-creole
rubygem-cucumber-core
rubygem-cucumber-wire
rubygem-erubi
rubygem-execjs
rubygem-ffi
rubygem-jquery-rails
rubygem-listen
rubygem-method_source
rubygem-mustache
rubygem-nokogiri
rubygem-pdf-core
rubygem-prawn
rubygem-pry
rubygem-rack
rubygem-rails-dom-testing
rubygem-railties
rubygem-rb-inotify
rubygem-RedCloth
rubygem-redis
rubygem-ruby-rc4
rubygem-sass
rubygem-sass-rails
rubygem-shoulda-context
rubygem-temple
rubygem-tilt
rubygem-ttfunk
rubygem-tzinfo

  • When do you need this? (YYYY/MM/DD)
    2022/04/06

  • When is this no longer needed or useful? (YYYY/MM/DD)
    N/A

  • If we cannot complete your request, what is the impact?
    These packages will not be built in epel9.


I am aware and support this. Thx for handling this in bulk

Mamoru (mtasaka) also has several rubygem packages. He also does not want to support them in EPEL, and has also agreed to let Troy (tdawson) be a co-maintainer for those rubygems, specifically for EPEL.

Please set tdawson as a co-maintainer, and as the EPEL bugzilla assignee for the following packages.

rubygem-contracts
rubygem-flexmock
rubygem-kramdown
rubygem-kramdown-parser-gfm
rubygem-rouge

Hi, I tried to write a script for this today, but pagure documentation is a little bit cryptic on how to set one as a collaborator on specific branches. I will give it a chance for a while more if unsuccessful will process this manually.

Metadata Update from @mohanboddu:
- Issue tagged with: low-gain, low-trouble, ops

2 years ago

Metadata Update from @mohanboddu:
- Issue untagged with: low-trouble
- Issue tagged with: medium-trouble

2 years ago

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata
Boards 1
Ops Status: Backlog