epel-devel November 2016

epel-devel@lists.fedoraproject.org

20 participants
84 discussions

wine 32
by ToddAndMargo 16 Jan '18

16 Jan '18

Hi Kevin and EPEL, Is there any sign of EPEL 7 support for Wine 32 yet? The lack of Wine 32 is keeping me on SL 6.6 and it is starting to drive me nuts! EPEL: think of the guilt you would feel if I get stuck in an insane asylums over the lack of wine 32 support! Seriously, the guilt would haunt you to the end of your days. Okay, maybe not, but still ... Many thanks, -T Hey, I had to try. If guilt doesn't work, I am really good at insincere compliments too. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Computers are like air conditioners. They malfunction when you open windows ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

6 12

Using devtoolset for EPEL builds
by Zuzana Svetlikova 03 Jan '18

03 Jan '18

Hi, I need/want/would like to build new node 6 for EL6, but gcc is too old. For that reason, I'd like to use devtoolset-4-gcc, but the build fails (obviously) because the package doesn't exist. So, is there a way to make that work somehow? I am not sure about enabling external repos during build, maybe someone will be wiser. Here's the build: http://koji.fedoraproject.org/koji/taskinfo?taskID=15970697 Zuzka

4 5

new DNF for everyone
by Honza Silhan 13 Feb '17

13 Feb '17

Hi, DNF is in EPEL for more than one year, unfortunately there was still the old DNF-0.6.4 version. Over that time in DNF were implemented a lot of great features and plenty of bugs have been fixed. DNF (especially its libraries) could not be updated in EPEL repository because of its policy. Now we have prepared fresh DNF-1.1.9 for RHEL 7 and CentOS 7 users in our COPR repository [1]. In order to install DNF follow the instructions here [2]. Honza [1] https://copr.fedorainfracloud.org/coprs/g/rpm-software-management/dnf-stack… [2] http://dnf.baseurl.org/2016/07/01/fresh-dnf-for-rhel-7-and-centos-7/

3 4

EPEL-ANNOUNCE Re: New rnapshot build for EPEL is testing
by James Hogarth 28 Dec '16

28 Dec '16

On 18 October 2016 at 06:26, Steven Roberts <strobert(a)strobe.net> wrote: > EPEL packages for a new rsnapshot version (1.4.2) have been built and > available in testing. > > There are many bug fixed in this release. From upstream the config file > should be comptabile with the existing 1.3.1 currently in EPEL. > > However given new upstream maintainer/hosting, it was about seven years > between upstream releases, and rsnapshot is used for things like > backups, we are taking extra caution with this release. > > So we are emailing this list to get extra notice and we are planning on > at least 4 weeks in testing and hoping to get some good testing and > karma reflected before moving to push to stable. > > the bugzilla bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1375289 > > the bodhi links for each EPEL version: > > EL5: > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-a017ef5480 > EL6: > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-5a39cec441 > EL7: > https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-91b8d9eccc > > Also, thanks to new co-maintener for the rsnapshot package James Hogarth > for getting the actually mods, builds put together. > As an update to the announcement, it's been noted in the Fedora users mailing list that the log file had a change of syntax at 1.3.2 (we were on 1.3.1) back in 2012 ... The logfile now has the timestamps in ISO 8601 format rather than apache-like so if any parsing or logstash tools are being used against the rsnapshot logs they will need to be updated to account for this _______________________________________________ epel-announce mailing list -- epel-announce(a)lists.fedoraproject.org To unsubscribe send an email to epel-announce-leave(a)lists.fedoraproject.org

1 1

Bug in rubygem-multipart-post package
by Richard Grainger 04 Dec '16

04 Dec '16

Hi I've posted a bug and patch for this package spec here: https://bugzilla.redhat.com/show_bug.cgi?id=1386644 No reply so far. Was that the right place to file the bug? Thanks in advance. Richard.

2 2

speexdsp update overwrites part of a RHEL 7 package
by Simone Caronni 01 Dec '16

01 Dec '16

Hello, a package entered stable that overwrites part of a RHEL 7 package. The bug is here: https://bugzilla.redhat.com/show_bug.cgi?id=1396841 As originally reported, the contributor has not replied in 10 days so I'm reporting the thing here. I would consider this an urgent bug; as it's impossible to compile against RHEL 7 speex/speexdsp packages anymore. For example VLC 2.2 does not compile, you need to exclude the updated speexdsp packages. What is the next step here? Thanks & regards, --Simone -- You cannot discover new oceans unless you have the courage to lose sight of the shore (R. W. Emerson). http://xkcd.com/229/ http://negativo17.org/

2 1

Help with resurrect two Orphans/Retired packages
by Mattias Ryrlén 01 Dec '16

01 Dec '16

Hi, I'm quite new to this and wonder how we can proceed to get two packages back to epel6 that got deleted due to flagged as orphaned this night 24/11 The packages i am talking about: * rubygem(uuidtools) * rubygem(aws-sdk) (requires rubygem(uuidtools)) -- Vänliga hälsningar / Best Regards Mattias Ryrlén __________________________ op5 AB Första Långgatan 19 SE-413 27 Göteborg Mobil: +46 735-17 70 99 Support: +46 31-774 09 24 www.op5.com

2 1

Agenda for today
by Stephen John Smoogen 30 Nov '16

30 Nov '16

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.

1 0

Orphaned Packages in epel5 (2016-11-30)
by Till Maas 30 Nov '16

30 Nov '16

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 you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Package (co)maintainers Status Change =========================================================================== js-jquery orphan, ctubbsii, group::nodejs-sig, 5 weeks ago jamielinux, patches js-jquery1 orphan, ctubbsii, group::nodejs-sig, 5 weeks ago jamielinux, patches kompose orphan 0 weeks ago python-keyring orphan, ctubbsii, rtnpro 1 weeks ago unetbootin orphan, callkalpa 5 weeks ago The following packages require above mentioned packages: Affected (co)maintainers callkalpa: unetbootin ctubbsii: js-jquery, js-jquery1, python-keyring group::nodejs-sig: js-jquery, js-jquery1 jamielinux: js-jquery, js-jquery1 patches: js-jquery, js-jquery1 rtnpro: python-keyring Orphans (5): js-jquery js-jquery1 kompose python-keyring unetbootin Orphans (dependend on) (0): Orphans (epel5) for at least 6 weeks (dependend on) (0): Orphans (epel5)(not depended on) (5): js-jquery js-jquery1 kompose python-keyring unetbootin Orphans (epel5) for at least 6 weeks (not dependend on) (0): Not found in repo (epel5) (4): js-jquery js-jquery1 kompose python-keyring -- The script creating this output is run and developed by Fedora Release Engineering. Please report issues at its trac instance: https://fedorahosted.org/rel-eng/ The sources of this script can be found at: https://pagure.io/releng/blob/master/f/scripts/find_unblocked_orphans.py

1 0

Orphaned Packages in epel7 (2016-11-30)
by Till Maas 30 Nov '16

30 Nov '16

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 you received this mail directly you (co)maintain one of the affected packages or a package that depends on one. Please adopt the affected package or retire your depending package to avoid broken dependencies, otherwise your package will be retired when the affected package gets retired. Package (co)maintainers Status Change ========================================================================= firehol orphan, cicku, error 5 weeks ago python-django-profile orphan, bkabrda, cstratak, mrunge 2 weeks ago The following packages require above mentioned packages: Affected (co)maintainers bkabrda: python-django-profile cicku: firehol cstratak: python-django-profile error: firehol mrunge: python-django-profile Orphans (2): firehol python-django-profile Orphans (dependend on) (0): Orphans (epel7) for at least 6 weeks (dependend on) (0): Orphans (epel7)(not depended on) (2): firehol python-django-profile Orphans (epel7) for at least 6 weeks (not dependend on) (0): Not found in repo (epel7) (1): python-django-profile -- The script creating this output is run and developed by Fedora Release Engineering. Please report issues at its trac instance: https://fedorahosted.org/rel-eng/ The sources of this script can be found at: https://pagure.io/releng/blob/master/f/scripts/find_unblocked_orphans.py

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

epel-devel November 2016