{"id":27001,"date":"2016-11-28T22:39:58","date_gmt":"2016-11-28T20:39:58","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=27001"},"modified":"2016-11-28T22:39:58","modified_gmt":"2016-11-28T20:39:58","slug":"epel-the-effort-behind-the-scenes","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2016\/11\/28\/epel-the-effort-behind-the-scenes\/","title":{"rendered":"EPEL : the effort behind the scenes"},"content":{"rendered":"\n

Catching up with recent news, I came across this blog<\/a> post by Stephen John Smoogen in Fedora People<\/a>, where he explains the reason for the recent disappearance of the Puppet package from the Extra Packages for Enterprise Linux<\/a> (EPEL 6) repository:<\/p>\n

This week various people using EPEL on RHEL and CentOS 6 have found that the puppet package is no longer provided by EPEL. The reason for this is due to the way EPEL packages are built and kept inside the repository. A package needs a sponsor so that we can hopefully get bug fixes and security updates to it. In the case of puppet this package is sponsored by the user kanarip. However, most packages aren’t whole pieces, they rely on other software.. in this case the package puppet relies on a lot of different ruby gems of which one of them was called ruby-shadow. This package was orphaned 30 weeks ago and while it did have other people watching it, none of them took over the package.<\/p>\n

[…]<\/p>\n

Last week a large cleanup was done to clean out orphaned packages from EPEL which removed ruby-shadow. Once that was removed, then all of the other packages depending on ruby-shadow were also removed. Today various people reinstalling systems found puppet wasn’t around and came onto #epel to ask.. which seems to have gotten the packages responsored and hopefully they will be back in the EPEL release in a day or so.<\/p>\n

This problem has been happening a lot lately. I think it shows quite a few problems with how EPEL is set up and managed. For this, I take responsibility as I said I would try to clean it up after FOSDEM 2016 and it is still happening.<\/p><\/blockquote>\n

Unpleasant annoyance that shouldn’t have happened, right? \u00a0Well, yes, maybe.<\/p>\n

Software is a complex matter, whether you are designing, developing, testing, or distributing it. \u00a0So things do go wrong sometimes. \u00a0And that was something I wanted to focus on for a second.<\/p>\n

Forget the actual designing, developing, testing and documenting the software. \u00a0Forget all the infrastructure behind such a vital part of the Linux ecosystem as EPEL. \u00a0Just think of this single issue for a moment. \u00a0Once again:<\/p>\n

A package needs a sponsor so that we can hopefully get bug fixes and security updates to it.<\/p><\/blockquote>\n

So what, I hear you say. \u00a0Well, let’s take a closer look. \u00a0EPEL provides packages for multiple versions of the distribution, hardware platforms and so on. \u00a0Let’s just look at the EPEL 6 for x86_64<\/a>\u00a0(to keep things simple). \u00a0That looks like a lot of packages, doesn’t it?. \u00a0How many? At the time of this writing, from a random mirror that I got:<\/p>\n

\r\nwget -q -O - http:\/\/download.fedoraproject.org\/pub\/epel\/6\/x86_64\/ | grep -c 'unknown.gif'\r\n12129\r\n<\/pre>\n
Yup. That’s 12,129 packages! \u00a0And each one of those has at least one developer behind it, to sponsor. \u00a0Some of those amazing people obviously maintain more than one package. Some packages are maintained by multiple people. \u00a0All of them are working hard behind the scenes for you and me to have an easy and stable access to a whole lot of software. \u00a0Here is a quote from the FAQ<\/a> which is smoked and marinated in all that effort:<\/p>\n
Software packages in EPEL are maintained on a voluntary basis. If you to want ensure that the packages you want remain available, get involved directly in the EPEL effort. More experienced maintainers help review your packages and you learn about packaging. If you can, get your packaging role included as part of your job description; EPEL has written a generic description that you can use as the basis for adding to a job description.<\/p>\n
We do our best to make this a healthy project with many contributors who take care of the packages in the repository, and the repository as a whole, for all releases until RHEL closes support for the distribution version the packages were built for. That is ten years after release (currently) — a long time frame, and we know a lot can happen in ten years. Your participation is vital for the success of this project.<\/p><\/blockquote>\n
I don’t know about you, but for me, this is absolutely mind-blowing. \u00a0So I just wanted to take this opportunity to say thank you to all the brilliant people behind the scenes, who are often invisible, yet indispensable for the continuous success of Open Source software in general, and Linux in particular.<\/p>\n
You guys rock!<\/p>\n\n","protected":false},"excerpt":{"rendered":"\n
Catching up with recent news, I came across this blog post by Stephen John Smoogen in Fedora People, where he explains the reason for the recent disappearance of the Puppet package from the Extra Packages for Enterprise Linux (EPEL 6) repository: This week various people using EPEL on RHEL and CentOS 6 have found that … Continue reading EPEL : the effort behind the scenes<\/span><\/a><\/p>\n\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"EPEL : the effort behind the scenes #OpenSource #Linux #EPEL #Fedora #CentOS #RedHat","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"_links_to":"","_links_to_target":""},"categories":[1,6,62],"tags":[3246,2351,2912,2157],"keyring_services":[],"class_list":["post-27001","post","type-post","status-publish","format-standard","hentry","category-general","category-linux","category-technology","tag-centos-linux","tag-fedora-linux","tag-open-source","tag-red-hat-linux"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":26860,"url":"https:\/\/mamchenkov.net\/wordpress\/2016\/11\/08\/install-ansible-2-0-on-amazon-ami\/","url_meta":{"origin":27001,"position":0},"title":"Install Ansible 2.0+ on Amazon AMI","author":"Leonid Mamchenkov","date":"November 8, 2016","format":false,"excerpt":"Today, while upgrading some of my Ansible roles I've hit the problem. \u00a0Some of the newer roles require Ansible 2.0. \u00a0My Amazon AMI machine that runs the playbooks was still on version 1.9. \u00a0EPEL repository doesn't seem to have the newer Ansible version yet. \u00a0Gladly, Google brough in this StackOverflow\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":22791,"url":"https:\/\/mamchenkov.net\/wordpress\/2014\/11\/03\/fpm-build-packages-for-multiple-platforms-deb-rpm-etc-with-great-ease-and-sanity\/","url_meta":{"origin":27001,"position":1},"title":"fpm – build packages for multiple platforms (deb, rpm, etc) with great ease and sanity","author":"Leonid Mamchenkov","date":"November 3, 2014","format":"link","excerpt":"fpm -\u00a0Effing package management! Build packages for multiple platforms (deb, rpm, etc) with great ease and sanity.","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":24075,"url":"https:\/\/mamchenkov.net\/wordpress\/2015\/05\/08\/do-not-use-amazon-linux\/","url_meta":{"origin":27001,"position":2},"title":"Do Not Use Amazon Linux","author":"Leonid Mamchenkov","date":"May 8, 2015","format":false,"excerpt":"I came across \"Do Not Use Amazon Linux\" opinion on Ex Ratione. \u00a0I have to say that I mostly agree with it. \u00a0When I initially started using Amazon Web Services, I assumed (due to time constraints mostly) that Amazon Linux was a close derivative of CentOs and I opted for\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":25986,"url":"https:\/\/mamchenkov.net\/wordpress\/2016\/04\/01\/first-attempt-at-ansible\/","url_meta":{"origin":27001,"position":3},"title":"First attempt at Ansible","author":"Leonid Mamchenkov","date":"April 1, 2016","format":false,"excerpt":"After all the reading about Ansible that I've done yesterday, I woke up today with a strong will to try it out. \u00a0Running a few \"hello world\" examples wasn't illustrative enough, so I decided to migrate my dotfiles repository from Puppet to Ansible. \u00a0This would provide just enough complexity to\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":27134,"url":"https:\/\/mamchenkov.net\/wordpress\/2016\/12\/15\/centos-7-3-released\/","url_meta":{"origin":27001,"position":4},"title":"CentOS 7.3 released","author":"Leonid Mamchenkov","date":"December 15, 2016","format":false,"excerpt":"CentOS 7.3 was released rather quietly a couple of days ago. \u00a0Or maybe it wasn't quietly, but I still somehow missed it. \u00a0Here is a list of major changes: Since release 1503 (abrt>= 2.1.11-19.el7.centos.0.1) CentOS-7 can report bugs directly to bugs.centos.org. Various new packages include among others: python-gssapi, python-netifaces, mod_auth_openidc,\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":18311,"url":"https:\/\/mamchenkov.net\/wordpress\/2013\/06\/04\/the-future-of-package-management-in-fedora\/","url_meta":{"origin":27001,"position":5},"title":"The future of package management in Fedora","author":"Leonid Mamchenkov","date":"June 4, 2013","format":"link","excerpt":"The future of package management in Fedora It's nice to see there is hope for a better package management in Fedora... YUM upstream will soon be considered deprecated, and we will move into a DNF\/hawkey\/librepo-based future. This includes PackageKit. I\u2019m going to be building a hawkey based backend with help\u2026","rel":"","context":"In "All"","block_context":{"text":"All","link":"https:\/\/mamchenkov.net\/wordpress\/category\/general\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_sharing_enabled":true,"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts\/27001","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/comments?post=27001"}],"version-history":[{"count":0,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/posts\/27001\/revisions"}],"wp:attachment":[{"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/media?parent=27001"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/categories?post=27001"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/tags?post=27001"},{"taxonomy":"keyring_services","embeddable":true,"href":"https:\/\/mamchenkov.net\/wordpress\/wp-json\/wp\/v2\/keyring_services?post=27001"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}