[EPEL-devel] Re: EPEL5 man page compression

I have developed a workaround for the issue you reported. I am able to build your package without issue. I have submitted the updated package to testing and I would welcome any testing. In the meantime I will set up another complete el5 rebuild to double-check. Alternately, I could simply

[EPEL-devel] Re: nodejs update

On 09/08/2016 11:27 AM, Stephen Gallagher wrote: On 08/22/2016 11:23 AM, Stephen Gallagher wrote: On 08/11/2016 07:43 AM, Stephen Gallagher wrote: On 08/11/2016 05:16 AM, Zuzana Svetlikova wrote: Hi! As some of you may know, nodejs package that is present in EPEL is pretty outdated. The

[EPEL-devel] Re: nodejs update

On 08/22/2016 11:23 AM, Stephen Gallagher wrote: > On 08/11/2016 07:43 AM, Stephen Gallagher wrote: >> On 08/11/2016 05:16 AM, Zuzana Svetlikova wrote: >>> Hi! >>> >>> As some of you may know, nodejs package that is present in >>> EPEL is pretty outdated. The current v0.10 that we have will >>> go

[EPEL-devel] Fwd: Orphaned Packages in epel7 (2016-09-08)

Something for next weeks meeting. We have a bunch of old packages on this list which either need to be taken over or pulled. -- Forwarded message -- From: Date: 8 September 2016 at 07:15 Subject: [EPEL-devel] Orphaned Packages in epel7 (2016-09-08) To:

[EPEL-devel] Orphaned Packages in epel7 (2016-09-08)

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-09-08)

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