[EPEL-devel] Re: Commit access for EPEL branches?

2016-02-01 Thread Dave Johansen
On Mon, Feb 1, 2016 at 1:07 PM, Adam Miller wrote: > On Mon, Feb 1, 2016 at 12:57 PM, Kevin Fenzi wrote: > > On Mon, 1 Feb 2016 08:58:13 -0700 > > Dave Johansen wrote: > > > >> I would like to package rpmorphan for EL [1].

[EPEL-devel] Re: Commit access for EPEL branches?

2016-02-01 Thread Adam Miller
On Mon, Feb 1, 2016 at 12:57 PM, Kevin Fenzi wrote: > On Mon, 1 Feb 2016 08:58:13 -0700 > Dave Johansen wrote: > >> I would like to package rpmorphan for EL [1]. I created an EPEL 7 >> branch, but the current owner/maintainer of the EPEL 5 and 6 branches

[EPEL-devel] Re: Commit access for EPEL branches?

2016-02-01 Thread Kevin Fenzi
On Mon, 1 Feb 2016 08:58:13 -0700 Dave Johansen wrote: > I would like to package rpmorphan for EL [1]. I created an EPEL 7 > branch, but the current owner/maintainer of the EPEL 5 and 6 branches > hasn't responded to my requests for commit access. Is there some way > for

[EPEL-devel] Re: Orphaned Packages in epel6 (2016-02-01)

2016-02-01 Thread Jason L Tibbitts III
> "o" == opensource writes: o> The following packages are orphaned and will be retired when they are o> orphaned for six weeks, [...] o> directfb orphan, kwizart, thias 17 weeks ago How does the retiring actually happen? I know it's a manual process,

[EPEL-devel] Orphaned Packages in epel5 (2016-02-01)

2016-02-01 Thread opensource
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If

[EPEL-devel] Orphaned Packages in epel6 (2016-02-01)

2016-02-01 Thread opensource
The following packages are orphaned and will be retired when they are orphaned for six weeks, unless someone adopts them. If you know for sure that the package should be retired, please do so now with a proper reason: https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life Note: If

[EPEL-devel] Fedora EPEL 7 updates-testing report

2016-02-01 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 329 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087 dokuwiki-0-0.24.20140929c.el7 91 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f mcollective-2.8.4-1.el7 11

[EPEL-devel] Fedora EPEL 7 updates-testing report

2016-02-01 Thread updates
The following Fedora EPEL 7 Security updates need testing: Age URL 330 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087 dokuwiki-0-0.24.20140929c.el7 92 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f mcollective-2.8.4-1.el7 12

[EPEL-devel] Fedora EPEL 6 updates-testing report

2016-02-01 Thread updates
The following Fedora EPEL 6 Security updates need testing: Age URL 226 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-6828 chicken-4.9.0.1-4.el6 208 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031 python-virtualenv-12.0.7-1.el6 202

[EPEL-devel] Commit access for EPEL branches?

2016-02-01 Thread Dave Johansen
I would like to package rpmorphan for EL [1]. I created an EPEL 7 branch, but the current owner/maintainer of the EPEL 5 and 6 branches hasn't responded to my requests for commit access. Is there some way for me to get commit access or do I have to go through the whole non-responsive maintainer