Re: [EPEL-devel] EPSCO is Dead. Long live EPSCO?

On 14 April 2015 at 11:39, Jeff Sheltren j...@tag1consulting.com wrote: On Tue, Apr 14, 2015 at 10:28 AM, Stephen John Smoogen smo...@gmail.com wrote: On 14 April 2015 at 08:03, Jeff Sheltren j...@tag1consulting.com wrote: According to the initial agreement among interested parties, EPSCO

[EPEL-devel] Open Slot on EPEL Steering Committee

I am stepping down from the EPSCO for a time and we have a slot open for someone to sit on the EPSCO and help the project. While I am currently the chair it is more of a 'pass around the baton' seat. Please cc on this email if you are interested. Time commitments are up to 1 hour meeting per week

Re: [EPEL-devel] Package Update

On 13 April 2015 at 02:20, A.H.M Tasbir Farid tasbirfa...@gmail.com wrote: Dear All I have configured EPEL local repository in my network. Other clients get packages from central repo. I need a package named monit with version 5.2 to connect m/monit server. EPEL repo have the older version

Re: [EPEL-devel] Trusted Source Error

On 12 June 2015 at 19:03, Mark LaPierre marklap...@gmail.com wrote: On 06/12/15 20:33, Stephen John Smoogen wrote: On 12 June 2015 at 17:41, Mark LaPierre marklap...@gmail.com wrote: I tried to install security updates: ntfs-3g-2:2015.3.14-2.el6 (x86_64) ntfsprogs-2:2015.3.14-2el6 (x86_64

Re: [EPEL-devel] EPEL 7 i386

On 28 June 2015 at 03:20, Peter pe...@pajamian.dhs.org wrote: Any plans for EPEL 7 i386 now that there is a beta out for CentOS 7 i386? There has been some talk but we would need something beyond a beta and the CentOS 7 guys are looking for more feedback from potential users before moving it

Re: [EPEL-devel] problem with epel mirrors?

On 1 July 2015 at 16:34, Gary Gatling gsgat...@ncsu.edu wrote: Ok, To follow up on the script output. master-out.txt: http://fpaste.org/238632/14357897/ mirror-out.txt: http://fpaste.org/238633/57898001/ I guess it needs to be run when yum is not working with any of the mirrors... EPEL 7

Re: [EPEL-devel] problem with epel mirrors?

On 30 June 2015 at 15:19, Reindl Harald h.rei...@thelounge.net wrote: Am 30.06.2015 um 23:16 schrieb Bernard Lheureux: On 06/30/2015 11:00 PM, Gary Gatling wrote: I have the same troubles with CentOS 5 and 6 and EPEL 5 and 6 ! I noticed today I cannot yum install any packages from epel 7.

[EPEL-devel] NOTICE: python-six has been removed from EPEL as it is in EL6.7

The package python-six is used as a shim for apps needing python3 command in python2 or python2 command in python3. The recent release of Red Hat Enterprise Linux 6.7 brought the package into the 'base' repositories which caused a conflict between the package inside of EPEL and RHEL. When the

Re: [EPEL-devel] Darktable major update

On 9 November 2015 at 13:30, Germano Massullo wrote: > Hi, I am one of the Darktable maintainers. > Darktable 2.0 is going too be released soon. According to EPEL policies, I > could not release such major release for EPEL/RHEL 7. > Do you usually apply this rule

Re: [EPEL-devel] latest python-debian in EPEL7 breaks spacewalk

The package is owned by Miroslav Suchý, email: msu...@redhat.com, Creation: 2008-05-14, IRC Nick: msuchy, Timezone: Europe/Vienna, Locale: en, GPG key ID: F1683540, Status: active I have cc'd him so he can do the push for a downgrade. Is there a bugzilla on this? [Or was he aware and asked you to

Re: [EPEL-devel] Centos 7, 32 bits edition

On 17 October 2015 at 16:37, Karanbir Singh <mail-li...@karan.org> wrote: > On 16/10/15 02:54, Stephen John Smoogen wrote: >> On 15 October 2015 at 16:38, Ian Pilcher <arequip...@gmail.com> wrote: >>> On 10/15/2015 07:29 AM, Matthew Miller wrote: >>>> &

[EPEL-devel] EPEL Steering Committee Meeting 2015-07-10

http://meetbot.fedoraproject.org/fedora-meeting/2015-07-10/epel.2015-07-10-18.03.txt http://meetbot.fedoraproject.org/fedora-meeting/2015-07-10/epel.2015-07-10-18.03.log.html 8:03:30 smooge #startmeeting epel 18:03:30 zodbot Meeting started Fri Jul 10 18:03:30 2015 UTC. The chair is smooge.

Re: [EPEL-devel] Call for Agenda: EPEL

On 24 September 2015 at 14:02, Bryan Chan <bryan.c...@ca.ibm.com> wrote: > Stephen John Smoogen <smo...@gmail.com> wrote on 2015-09-24 02:56:24 PM: > >> I believe the following items are outstanding on EPEL questions: >> >> 1) EPEL for i686 (using CentOS) &g

[EPEL-devel] Call for Agenda: EPEL

I believe the following items are outstanding on EPEL questions: 1) EPEL for i686 (using CentOS) 2) EPEL for arm (using CentOS) 3) EPEL for aarch64 4) EPEL for ppcle 5) EPEL and CentOS sigs (what is the problem trying to be solved) However those can all be closed topics.. if people have any

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPSCo weekly meeting

On 8 January 2016 at 09:13, Kevin Fenzi wrote: > On Fri, 8 Jan 2016 05:00:03 + (UTC) > den...@ausil.us wrote: > >> Dear all, >> >> You are kindly invited to the meeting: >>EPSCo weekly meeting on 2016-01-08 from 17:00:00 to 18:00:00 UTC >>At e...@irc.freenode.net >>

[EPEL-devel] Re: Retiring quassel @el6

On 3 June 2016 at 07:52, Christian Dersch wrote: > Hi all, > > I plan to retire quassel for EPEL6 soon. The package is quite outdated > and affected by some security issues. I'm unable to fix them by moving > to a new release or even backporting the fixes. The main reason is

[EPEL-devel] Re: Update notice FEDORA-EPEL-2016-(several) is broken, or a bad duplicate, skipping.

On 2 June 2016 at 09:24, Michael Mol wrote: > Ran a yum check-update on a staleish host this morning, saw these. They ask > that I contact the epel-testing and epel-testing-source repository owners, > which appear to be this list. > > > Update notice

[EPEL-devel] Re: EPEL conflicts with Satellite 6 packages

On 2 June 2016 at 12:03, Erinn Looney-Triggs wrote: > There are a number of packages in EPEL 6 and 7 that conflict with > packages provided by either RH Satellite or the katello-agent. > A quick run through for an up to date (6.1.9) install of satellite on > RHEL 7:

[EPEL-devel] Re: RHEL build system

On 23 June 2016 at 10:54, Dave Love wrote: > I was reviewing some documentation which includes: > > Redhat for example has a very optimal tool chain which they use for > their Enterprise product line and it is not available to other > distributions (or rebuilds) and

[EPEL-devel] FOSDEM 2016: Whither EPEL?

If you are at FOSDEM 2016 and would like to talk about EPEL, we are having a round table on Sunday in the Dev room https://fosdem.org/2016/schedule/event/whither_epel/ I would be happy to meet with anyone there on Saturday and earlier on Sunday if needed. -- Stephen J Smoogen.

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

On 1 February 2016 at 16:53, Jason L Tibbitts III wrote: >> "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

[EPEL-devel] Re: How to go on with unmaintainable package?

On 23 February 2016 at 14:10, Christian Dersch wrote: > Hi all, > > some weeks ago I took the quassel package to fix security issues. This > worked fine for Fedora and EPEL 7, but for EPEL 6 I'm unable to apply > security fixes as one of them (the most important one...)

[EPEL-devel] EPEL Proposal #3: EPEL Structured releases

EPEL Proposal #3: EPEL Structured releases This started off as a a rawhide post, but I realized it needs to be its own post A staged/forked environment. This version is a lot more complicated and deals

[EPEL-devel] EPEL Proposal #4: Build it all in CentOS promote to RHEL

== EPEL Proposal #4: Build it all in CentOS promote to RHEL == So this one came up when we were going over problems with building alternative architectures in EPEL. One of the big

[EPEL-devel] Re: Missed Meeting this Week. Please put issues into this email.

On 24 February 2016 at 17:50, Jason L Tibbitts III <ti...@math.uh.edu> wrote: >>>>>> "SJS" == Stephen John Smoogen <smo...@gmail.com> writes: > Thank you for the input on this email. > SJS> Things done: > > epel-rpm-macros-6-4 is pushed to

[EPEL-devel] Proposals and such...

Hey I went through my notes and I only have 1 other questioned proposal that people asked about. I will post that later today but if there are things people think should have been talked about please let me know. -- Stephen J Smoogen. ___ epel-devel

[EPEL-devel] Re: Old scl-utils packages?

On 26 February 2016 at 21:01, Dave Johansen wrote: > It looks like EPEL 5/6 have old versions of scl-utils. Those are probably > added back at a point when the base OS didn't have them, but they are now > older versions than what's available in the base OS. > Should EPEL

[EPEL-devel] Re: Exception request: major version bump for Nginx

On 29 January 2016 at 06:51, Jamie Nguyen wrote: > Hi, > > A few days ago, three CVEs for Nginx and were fixed in 1.8.1. Upstream > only maintain 1.8.x and above, so they didn't release any fixes for > older versions of Nginx. I was able to backport the relevant commits to >

[EPEL-devel] Missed Meeting this Week. Please put issues into this email.

I got caught up trying to research a problem with NFS and iscsi and completely missed that I was supposed to run a meeting today. Thanks to the people who pinged me and my apologies. Since I am now a month ahead, I would like to get all the issues that we are wanting done in the next week meeting

[EPEL-devel] Re: EPEL-ANNOUNCE ansible 2.0 in epel

On 23 January 2016 at 09:32, Randy Barlow wrote: >> Since ansible 2.0 is (to a pretty high degree) compatible with the same >> playbooks as 1.9.x, we are going to just update the existing ansible >> package rather than create a parallel installable one. > > Hello! I

[EPEL-devel] Report on various meetings at FOSDEM.

Apologies and So Forth First, I would like to apologize for the delay in getting this post done. I really didn't realize the amount of energy the trip would take from me and how fuzzy brained I was for a week afterwords. Second, I would like to

[EPEL-devel] Re: Report on various meetings at FOSDEM.

On 16 February 2016 at 21:51, Jason L Tibbitts III <ti...@math.uh.edu> wrote: >>>>>> "SJS" == Stephen John Smoogen <smo...@gmail.com> writes: > > SJS> * The packaging guidelines for each EPEL version are not > SJS> clear. This is mainly d

[EPEL-devel] Todays EPEL meeting:

We had a meeting and for the full logs please see https://meetbot.fedoraproject.org/fedora-meeting/2016-02-17/epel.2016-02-17-19.00.log.html -- Stephen J Smoogen. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org

[EPEL-devel] Re: EPEL Proposal #1: Rechartering

On 18 February 2016 at 12:56, Kevin Fenzi wrote: > >> 3. Packages are built against all of an Enterprise Linux 'base' (EG >>whatever is in CentOS/Scientific Linux base). > > I thought we were always clear that we built against RHEL. > But perhaps not. > Sorry what I meant

[EPEL-devel] Re: Report on various meetings at FOSDEM.

On 18 February 2016 at 12:46, Kevin Fenzi <ke...@scrye.com> wrote: > On Tue, 16 Feb 2016 21:42:18 -0700 > Stephen John Smoogen <smo...@gmail.com> wrote: > >> >> Apologies and So Forth >> >> >>

[EPEL-devel] Re: EPEL Proposal #1: Rechartering

On 18 February 2016 at 16:37, Dave Johansen wrote: > On Thu, Feb 18, 2016 at 3:54 PM, Bryan J Smith wrote: >> >> Dave Johansen wrote: >> > RHSCL is a non-starter where I work (and I imagine at other >> > locations). 2-3 years of support just isn't

[EPEL-devel] Re: related question / off topic - EPEL Proposal #1: Rechartering

On 18 February 2016 at 14:13, ~Stack~ <i.am.st...@gmail.com> wrote: > On 02/18/2016 01:56 PM, Kevin Fenzi wrote: >> On Tue, 16 Feb 2016 23:24:58 -0700 >> Stephen John Smoogen <smo...@gmail.com> wrote: > [snip] >>> 1. Packages will never disappear. [They don

[EPEL-devel] Re: related question / off topic - EPEL Proposal #1: Rechartering

On 18 February 2016 at 19:16, ~Stack~ <i.am.st...@gmail.com> wrote: > On 02/18/2016 06:29 PM, Stephen John Smoogen wrote: >> On 18 February 2016 at 14:13, ~Stack~ <i.am.st...@gmail.com> wrote: >>> On 02/18/2016 01:56 PM, Kevin Fenzi wrote: >>>> On Tue, 16

[EPEL-devel] Re: Report on various meetings at FOSDEM.

On 19 February 2016 at 08:35, Kevin Fenzi <ke...@scrye.com> wrote: > On Thu, 18 Feb 2016 14:42:12 -0700 > Stephen John Smoogen <smo...@gmail.com> wrote: > >> >> One of the requests was to have snapshots of the guidelines that we >> worked each channel again

[EPEL-devel] Re: Django in EPEL6

On 9 March 2016 at 02:58, Matthias Runge wrote: > On 08/03/16 18:55, Orion Poplawski wrote: >> On 03/08/2016 10:42 AM, Brian Bouterse wrote: >>> This removal has been problematic for a lot of software including >>> the listed EPEL dependencies and anything those depend

[EPEL-devel] Re: Standing down from EPSCo

On 9 March 2016 at 09:43, Dennis Gilmore wrote: > Hi All, > > Effective immediately I am stepping down from EPSCo, I am unable to give it > the time it deserves. There is just too much going on in Fedora. I will gladly > help and guide people to get involved in making process

[EPEL-devel] Fwd: [rhelv6-beta-list] Red Hat Enterprise Linux 6.8 Beta Now Available for Testing

So the 6.8 Beta is coming out. I would like to use this time as a general request for EPEL packagers wanting to make large updates or retirements of packages from RHEL-6 to do so now. -- Forwarded message -- From: Engineering Partner Management

[EPEL-devel] Re: Owncloud updates

On 15 March 2016 at 15:06, Stephen John Smoogen <smo...@gmail.com> wrote: > On 15 March 2016 at 02:18, James Hogarth <james.hoga...@gmail.com> wrote: >> Hi all, >> >> A situation has come up similar to the nginx one. >> >> Owncloud 7.0 has reached

[EPEL-devel] Re: Owncloud updates

On 15 March 2016 at 02:18, James Hogarth wrote: > Hi all, > > A situation has come up similar to the nginx one. > > Owncloud 7.0 has reached EOL so we either need to bring it up to date in > EPEL6 or retire it. > I am of the opinion is to retire it across the board.

[EPEL-devel] Meeting for 2016-03-30 cancelled

I am unable to run the meeting and too many others are on travel to have quorum. Will do next week. -- Stephen J Smoogen. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org

[EPEL-devel] Cleanup of EL-5 testing

There is a lot of cruft in EPEL-5 testing at the moment. I would like to get an idea of what we can unpush: 2009-07-01 emacs-vregs-mode-1.463-1.el5.noarch.rpm 2009-07-01 grc-0.70-3.el5.noarch.rpm 2009-07-01 perl-SystemC-Vregs-1.463-1.el5.noarch.rpm 2009-07-01

[EPEL-devel] Re: using epel-rpm-macros

On 27 March 2016 at 08:52, Dave Love wrote: > > > Jason L Tibbitts III > writes: > >> If you have a build dependency on the SCL tools then you're obviously >> not building for EPEL, > > Well, I'm building for people running

[EPEL-devel] EPEL Meeting 2016-03-08

Agenda: --- 1. Roll Call 2. Outstanding Issues a. Django removed from EL6 b. Orphans and removals c. EL-5/EL-6 build root changes via tibbs d. ??? 3. Upcoming opportunities a. Recharter EPEL b. Removing EL-5 in 1 year c. Discuss proposed plans. d. Allowing CentOS to "build" a

[EPEL-devel] No EPEL Steering Committee meeting this week

several of the steering committee people are on travel this week and are not able to attend. We will have our next regular meeting on 2016-03-09 -- Stephen J Smoogen. ___ epel-devel mailing list epel-devel@lists.fedoraproject.org

[EPEL-devel] Re: EPEL-ANNOUNCE Re: Upcoming OwnCloud changes in EPEL

On 22 April 2016 at 05:16, James Hogarth wrote: > > > Following on from the previous message EPEL6 has it's final update with the > EOL message. Please arrange to move to the upstream SCL packages or to > migrate to EL7 if you are using owncloud on EPEL6 - be aware when

[EPEL-devel] EPEL meeting 2016-05-12

Thank you all for your patience on my getting out these late agenda items. Proposed Agenda #startmeeting EPEL #meetingname EPEL #chair smooge nirik Evolution bstinson avij #topic aloha #topic Outstanding issues #info Orphans and removals #info EL-5/EL-6 build root changes via tibbs #info

[EPEL-devel] Re: EPEL meeting 2016-05-12

And it looks like I completely missed out that yesterday is Wednesday... and today is not Wednesday. So for next week's meeting.. the following agenda. [Or we can discuss on list.] On 12 May 2016 at 09:45, Stephen John Smoogen <smo...@gmail.com> wrote: > Thank you all for your patie

[EPEL-devel] Re: [EXCEPTION REQUEST] librepo/libsolv/hawkey override in EPEL7

On 9 May 2016 at 08:29, Stephen John Smoogen <smo...@gmail.com> wrote: > On 9 May 2016 at 02:38, Igor Gnatenko <ignate...@redhat.com> wrote: >> Hi all, >> >> Sorry for delay for writing this. We wanted to provide latest DNF >> stack in EPEL7 which means we

[EPEL-devel] Re: Problem with dnf in EPEL-7

On 7 May 2016 at 14:11, Kevin Fenzi <ke...@scrye.com> wrote: > On Sat, 7 May 2016 12:36:27 -0400 > Neal Gompa <ngomp...@gmail.com> wrote: > >> On Sat, May 7, 2016 at 10:23 AM, Stephen John Smoogen >> <smo...@gmail.com> wrote: >> > So I had someo

[EPEL-devel] Re: nodejs update

On 11 August 2016 at 07:43, Stephen Gallagher wrote: >> tl;dr Need to update nodejs, but can't decide if v4 or v6, >> v4: will update sooner, shorter support (2018-04-01) >> v6: longer support (2019-04-01), *might* break more things, >> won't be in stable sooner than

[EPEL-devel] Re: nodejs update

g to get the correct picture of the plan in my head . > - Original Message - > From: "Stephen John Smoogen" <smo...@gmail.com> > To: "EPEL Development List" <epel-devel@lists.fedoraproject.org> > Cc: "Zuzana Svetlikova" <zsvet...@redh

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPSCO meeting

I need to fix this sorry about that as it is a day late and an hour short. On 17 August 2016 at 15:00, wrote: > Dear all, > > You are kindly invited to the meeting: >EPSCO meeting on 2016-08-18 from 19:00:00 to 19:55:00 GMT > > > The meeting will be about: > Weekly EPEL

[EPEL-devel] Major updates to nagios and nrpe

With the help of several people, I have put in a new version of nagios and nrpe into epel-testing for EL-7. I am still trying to figure out some rpmspec file problems with EL-6 that are causing it not to work. nagios is now 4.2.4 changes include moving various control files from /var/log/nagios

[EPEL-devel] EPEL meetings (Next Meeting Feb 08 2017 18:00 UTC)

We normally have a EPEL Steering Committee meeting on Wednesday at 18:00 UTC in freenode's #fedora-meeting channel. However due to a slew of conferences for the next couple of weeks, it looks like a majority of committee members will either be travelling or unavailable. I would like to put the

[EPEL-devel] EPEL meeting Agenda 2017-02-15 1800 UTC

Report from Devconf/FOSDEM Ideas for the coming year Combining mailing lists Getting CentOS builds done in the next 3 months? -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

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

Good question. I will put it up in the next meeting to have them removed and possibly have the core package also removed. On 9 February 2017 at 17:54, Christopher wrote: > Are the frequent emails about these ones that have been in the testing repo > for over 2 years,

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

iliar with the EPEL testing process. Is there a good doc > which I can read and learn how to get involved? > > Thanks, > David > >> On Feb 10, 2017, at 8:20, Stephen John Smoogen <smo...@gmail.com> wrote: >> >> Good question. I will put it up in the next meeti

[EPEL-devel] Re: rethinking the epel testing

On 17 January 2017 at 12:07, Matthew Miller wrote: > On Tue, Jan 17, 2017 at 04:11:31PM +0100, Nikos Mavrogiannopoulos wrote: >> 1. The majority of people who use EPEL are not Fedora users. They are >> more likely to report a bug they encounter, in CentOS forums (or

[EPEL-devel] Re: EPEL-ANNOUNCE ansible1.9 retirement

I am -1 to obsoleting from the experience of what happened in the past with other deployment or configuration management systems do that. It will break large systems and it will break small systems and it won't 'fix' any systems that anyone will tell you about. So after an update all anyone will

[EPEL-devel] Re: Request: backwards incompatible bodhi update

EPEL Steeting Committee Meetings are held on Wednesdays at 1900 UTC. The next one should be on the 11th. On 5 August 2016 at 08:30, Randy Barlow wrote: > On Wed, 2016-07-27 at 17:12 -0400, Neal Gompa wrote: >> It makes sense to me to go ahead and upgrade it. I don't

[EPEL-devel] EPEL meeting

Agenda: - Review of major update to nagios by EPSCO. -- Smoogen will recuse himself because it is his package -- Need a review of changes by volunteer and members. - Mission/Vision Statement -- Started work on PRD and boy those things are hard. -- Stephen J Smoogen.

[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] Re: Adding the devtoolset repo for EPEL builds

On 31 August 2016 at 04:58, dani wrote: > > > On 29/08//2016 22:23, Jason L Tibbitts III wrote: >>> >>> "d" == dani writes: >> >> d> I think it is high time to rethink the single version of a package >> d> policy, and come up with some scheme that

[EPEL-devel] Re: Requirements for SRPM names

On 13 September 2016 at 14:13, Avram Lubkin wrote: > I'm looking for some clarification on the naming requirements for SRPMs. > > In the EPEL 7 in Python 3 Plan Draft [1], it specifies that SRPM names can't > conflict with RHEL SRPM names, but in the Limited Arch Packages

[EPEL-devel] Re: Requirements for SRPM names

On 13 September 2016 at 17:14, Avram Lubkin <av...@rockhopper.net> wrote: > On Tue, Sep 13, 2016 at 2:28 PM, Stephen John Smoogen <smo...@gmail.com> > wrote: >> >> >> The reasoning for needing a python3-foobaz is that we don't replace >> the python2 v

[EPEL-devel] Re: EPEL 7 Node.js Uplift

Will bring up at the meeting.. but assume this is approved. On 28 September 2016 at 11:45, Kevin Fenzi wrote: > On Wed, 28 Sep 2016 08:54:27 -0400 > Neal Gompa wrote: > > ...snip... > >> That's a lot of work for an update that's going to die off literally >>

[EPEL-devel] 2016-09-21 Meeting Cancelled

Many of the board members have conflicting problems needing to be worked on so we are going to cancel this weeks meeting. -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

On 24 August 2016 at 23:59, Dave Johansen wrote: > On Wed, Aug 24, 2016 at 5:28 PM, Kevin Fenzi wrote: >> >> On Wed, 24 Aug 2016 16:43:31 -0600 >> Dave Johansen wrote: >> >> > On Wed, Aug 24, 2016 at 4:22 PM, Kevin Fenzi

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

On 25 August 2016 at 02:14, dani wrote: > When I proposed importing gcc-5 to EPEL6 back in 04/2016 ( > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/F5JXEYPKQY77NRBCL4MNUBS3K2YYBBTU/ > ) the response was an unequivocal no, EPEL does

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

On 26 August 2016 at 12:58, Stephen John Smoogen <smo...@gmail.com> wrote: > On 26 August 2016 at 06:00, Daniel Letai <d...@letai.org.il> wrote: >> >> >> On 08/25/2016 11:40 PM, Kevin Fenzi wrote: >> >> Perhaps you could explain exactly what you wa

[EPEL-devel] Re: Adding the devtoolset repo for EPEL builds

On 25 August 2016 at 12:49, Stephen John Smoogen <smo...@gmail.com> wrote: > On 24 August 2016 at 23:59, Dave Johansen <davejohan...@gmail.com> wrote: >> On Wed, Aug 24, 2016 at 5:28 PM, Kevin Fenzi <ke...@scrye.com> wrote: >> >> I agree that how to hand

[EPEL-devel] Re: Bug in awscli-1.11.0-1.el7

On 25 October 2016 at 16:32, Ben Smith wrote: > After an upgrade to the current EPEL awcli, a system I'm working on broke. > There's a bug with downloading empty files that's been fixed in 1.11.1. We > verified that upgrading to awscli-1.11.2-1.el7 fixes the problem. > >

[EPEL-devel] Re: Django stable RPMs

On 8 November 2016 at 10:31, Brian Bouterse wrote: > I believe the future of Django in EPEL is a topic that is being discussed on > the EPSCO meetings last week and this week (18:00 UTC on Wednesdays in > #fedora-meeting, iirc). > > I'm hoping that even if a newer, 1.8 based

[EPEL-devel] Looking for testers for Nagios 4.2.2

Petaris and I put together an updated set of RPMs for nagios, nagios-plugins and nrpe that need testing. I have built them in a copr of https://copr.fedorainfracloud.org/coprs/smooge/Nagios_Update/repo/epel-7/smooge-Nagios_Update-epel-7.repo I know that currently these do not build for RHEL-6 or

[EPEL-devel] Re: Redis Version in EPEL 7

On 14 November 2016 at 20:49, Somers-Harris, David | David | OPS wrote: > Hi, > > I see that in EPEL7-release there is Redis 2.x and in EPEL7-testing there is > Redis 3.x > > Is the version for Redis in EPEL7 going to change soon? > Or will multiple versions

Planned Outage: General Services Environment - 2016-11-30 21:00 UTC

There will be an outage starting at 2016-11-30 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-30 21:00 UTC' Reason for outage: We have been in a freeze for the release of

Planned Outage: Staging Environment - 2016-11-28 21:00 UTC

There will be an outage starting at 2016-11-28 21:00 UTC, which will last approximately 4 hours. To convert UTC to your local time, take a look at https://fedoraproject.org/wiki/UTCHowto or run: date -d '2016-11-28 21:00 UTC' Reason for outage: We have been in a freeze for the release of

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPSCO meeting

Tomorrows meeting: python34 current status epel7/centOS 7.3 aarch64 is being built for RHEL-7.3 redis3.0 pushed to testing but no notice about major change ?? On 15 November 2016 at 13:00, wrote: > Dear all, > > You are kindly invited to the meeting: >EPSCO meeting on

[EPEL-devel] Re: Redis Version in EPEL 7

On 14 November 2016 at 20:49, Somers-Harris, David | David | OPS wrote: > Hi, > > I see that in EPEL7-release there is Redis 2.x and in EPEL7-testing there is > Redis 3.x > > Is the version for Redis in EPEL7 going to change soon? > Or will multiple versions

[EPEL-devel] Report: Package conflicts between EPEL and RHEL-7.3

This is my first pass at finding the conflicts with between EPEL-7 x86_64 and the RHEL repos 'rhel-7-server-extras-rpms', 'rhel-7-server-optional-rpms', 'rhel-7-server-rpms', 'rhel-ha-for-rhel-7-server-rpms'. There do not seem to be any places where EPEL packages would replace packages in those

[EPEL-devel] Re: MongoDB in EPEL7

On 1 November 2016 at 13:33, Tom Boutell wrote: > Sorry, I just saw the part about RHSCL. But that page says: > > "Community Project: Maintained by upstream communities of developers. The > software is cared for, but the developers make no commitments to update the >

[EPEL-devel] Re: MongoDB in EPEL7

On 1 November 2016 at 13:32, Tom Boutell wrote: > I think that if a CVE arrives that we can't easily address through a patch, > we have to be prepared to force an upgrade. Potentially "abandoning" a > package that has CVEs in the wild, in the hope people will read about an >

[EPEL-devel] Removing Django from EL6/7

tl;dr Web apps and frameworks are horrible for EPEL because they 'innovate' so quickly compared to multi-year support paths -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] RHEL-7.3 is out and synced

Red Hat Enterprise Linux 7.3 is now out. The builders should be seeing it either now or very soon. This may cause packages not to build or that current EPEL packages to be superfluous. We will make an accounting of duplicate packages and try to do a test rebuild of packages somewhere to see if

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPSCO meeting

Actually with people at LISA and PHX2 I was going to ask if people wanted to skip this weeks meeting. On 6 December 2016 at 13:00, wrote: > Dear all, > > You are kindly invited to the meeting: >EPSCO meeting on 2016-12-07 from 18:00:00 to 19:00:00 GMT >At

[EPEL-devel] Re: Nagios CVE

Can you look at https://copr.fedorainfracloud.org/coprs/smooge/Nagios_Update/ and try it on a test system? This changes various items and I need feedback before I push it into EPEL or try to fix it to work in Fedora. On 14 December 2016 at 13:03, Neil MacGregor

[EPEL-devel] No meeting today

I am sick and was not able to get an agenda working -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org

[EPEL-devel] Agenda for today

1. speexdsp problem https://bugzilla.redhat.com/show_bug.cgi?id=1396841 2. puppet in EPEL-6 3. other removals from EPEL-6 4. ... -- Stephen J Smoogen. ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to

[EPEL-devel] Re: [Fedocal] Reminder meeting : EPSCO meeting

OK I am going to cancel todays meeting. On 6 December 2016 at 13:01, Stephen John Smoogen <smo...@gmail.com> wrote: > Actually with people at LISA and PHX2 I was going to ask if people > wanted to skip this weeks meeting. > > On 6 December 2016 at 13:00, <smo...@gmail.co

[EPEL-devel] Re: Fedora EPEL-7 build with GCC-4.9?

On 22 March 2017 at 07:31, David Timms wrote: > My package needs: > build.log.gz: > checking for libudev.h... no > checking whether we are using gcc 4.9.0 or later... no > configure: error: Audacity requires at least GCC 4.9 > error: Bad exit status from

[EPEL-devel] Re: Pull request/Changes to CentOS Extras repo??

On 28 March 2017 at 05:41, Martin Juhl wrote: > Hi guys... > > I have some packages in the Extras repo, that I would like to be built for > python3 as well as python2... > > I can provide the changes for the spec files, but what is the official way to > commit changes / pull

[EPEL-devel] RHEL-5 is 10 years old today

According to wikipedia, on March 15, 2007 RHEL-5 was released. The builders seem to have gotten updated to RHEL-5 around March 31st... though packages were built in testing before then. -- Stephen J Smoogen. ___ epel-devel mailing list --

[EPEL-devel] EPEL-5 is End of Lifed

EPEL-5 has been end of lifed. The build system will no longer produce updates for the operating system and updates to the trees will no longer happen. The trees as they existed on 2017-03-31 have been archived to /pub/archive/epel/5/ and /pub/archive/epel/testing/5/ . On 2017-04-06, the mirror

[EPEL-devel] Re: python-mutagen treated as limited arch package?

Matej, it was agreed by EPSCO that the package should be allowed into the distribution using the same methods in the limited arch package. On 10 April 2017 at 18:05, Kevin Fenzi wrote: > On 04/10/2017 03:50 PM, Matej Cepl wrote: >> Hi, >> >> with

[EPEL-devel] EPEL Steering Committee Meeting Canceled for 2017-04-05

There will be no EPSCO meeting this week. Things that have happened since the last meeting: 1. EPEL-5 has been end of lifed with no builds still happening. 2. EPEL-5 has been archived over to /pub/archive/epel/5/ 3. EPEL-4 has been archived over to /pub/archive/epel/4/ 4. CentOS-6.9 has been

<    9   10   11   12   13   14   15   16   17   18   >