[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 112 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-6828 chicken-4.9.0.1-4.el6 94 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031 python-virtualenv-12.0.7-1.el6 88 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168 rubygem-crack-0.3.2-2.el6 20 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-8148 optipng-0.7.5-5.el6 20 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-8156 nagios-4.0.8-1.el6 8 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-68a2c2db36 python-pymongo-3.0.3-1.el6 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-d6cc67d0d6 opensmtpd-5.7.3p1-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing fprobe-ulog-1.2-2.el6 golang-github-AdRoll-goamz-0-0.2.gitf8c4952.el6 golang-googlecode-go-crypto-0-0.7.gitc57d4a7.el6 gparted-0.19.1-4.el6 layla-fonts-1.5-1.el6 python-debian-0.1.27-2.el6 Details about builds: fprobe-ulog-1.2-2.el6 (FEDORA-EPEL-2015-18cd799f6e) NetFlow probe Update Information: fprobe-ulog-1.2-2.el6 - Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild fprobe-ulog-1.2-2.el7 - Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild golang-github-AdRoll-goamz-0-0.2.gitf8c4952.el6 (FEDORA-EPEL-2015-0413ad71c5) Fork of the GOAMZ with additional functionality with DynamoDB Update Information: Add s3 package for openshift/origin First package for Fedora References: [ 1 ] Bug #1269571 - Tracker for golang-github-AdRoll-goamz https://bugzilla.redhat.com/show_bug.cgi?id=1269571 [ 2 ] Bug #1262714 - Review Request: golang-github-AdRoll-goamz - Fork of the GOAMZ with additional functionality with DynamoDB https://bugzilla.redhat.com/show_bug.cgi?id=1262714 golang-googlecode-go-crypto-0-0.7.gitc57d4a7.el6 (FEDORA-EPEL-2015-e6845acae3) Supplementary Go cryptography libraries Update Information: Fix sed for import path Update spec file to spec-2.0 References: [ 1 ] Bug #1231618 - Tracker for golang-googlecode-go-crypto https://bugzilla.redhat.com/show_bug.cgi?id=1231618 gparted-0.19.1-4.el6 (FEDORA-EPEL-2015-d2739dc541) Gnome Partition Editor Update Information: - Update to fix "one sector error" - Fixes #1269440 References: [ 1 ] Bug #1269440 - Fix off by one sector data corruption error in GParted < 0.21.0 https://bugzilla.redhat.com/show_bug.cgi?id=1269440 layla-fonts-1.5-1.el6 (FEDORA-EPEL-2015-1ef24fcd30) A collection of traditional Arabic fonts Update Information: Added numbers and symbol glyphs to the BasicArabic font file References: [ 1 ] Bug #1079090 - Review Request: layla-fonts - A collection of traditional Arabic fonts https://bugzilla.redhat.com/show_bug.cgi?id=1079090 python-debian-0.1.27-2.el6 (FEDORA-EPEL-2015-25c83db8f1) Modules for Debian-related data formats Update Information: support for xz ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
Re: [EPEL-devel] crlibm and libscs for EPEL 7?
On 10/9/2015 1:54 AM, Dominik 'Rathann' Mierzejewski wrote: You could ask to become the maintainer in EPEL: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer That looks like quite an involved process with an uncertain outcome ... The process may look involved at first, but it's usually not that much work after the initial formalities. Why do you think the outcome is uncertain? There are a lot of caveats listed in the requirements to be approved as a package maintainer after the initial formalities (some of which I started!). Finding a sponsor, contributing in "other ways" than just supporting the specific packages that I need. I don't want to commit to things I wouldn't be able to follow through on. Is that the only viable option at the moment? Adopt it myself? I'm afraid that's how it works for most packages. People who use the software and have the skills to maintain it usually do it. You can also pay someone to maintain it for you. ;) Don't have that ability (pay) in the position I'm in at my company, and realistically, I can just check the rpm I built into our ansible repository. Or rewrite my software to not use pyinterval. I've re-built/modified some rpm packages, but don't profess to be anywhere near an expert level. More in the amateur realm, but enough to modify an existing rpm to build on newer platforms or to swap out versions of source. I'll give it more consideration and get back to you. Rich ___ epel-devel mailing list epel-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/epel-devel
