From 16530d7f9e19f80646600507bb6854d64c0b1649 Mon Sep 17 00:00:00 2001 From: MSVSphere Packaging Team Date: Wed, 20 Mar 2024 01:58:26 +0300 Subject: [PATCH] import epel-release-8-19.el8 --- .epel-release.metadata | 0 .gitignore | 0 SOURCES/.cvsignore | 0 SOURCES/90-epel.preset | 9 + SOURCES/GPL | 347 +++++++++++++++++++++++++++++ SOURCES/README-epel-8-packaging.md | 164 ++++++++++++++ SOURCES/RPM-GPG-KEY-EPEL-8 | 28 +++ SOURCES/crb | 85 +++++++ SOURCES/epel-modular.repo | 33 +++ SOURCES/epel-next-testing.repo | 30 +++ SOURCES/epel-next.repo | 30 +++ SOURCES/epel-testing-modular.repo | 33 +++ SOURCES/epel-testing.repo | 30 +++ SOURCES/epel.repo | 30 +++ SPECS/epel-release.spec | 212 ++++++++++++++++++ 15 files changed, 1031 insertions(+) create mode 100644 .epel-release.metadata create mode 100644 .gitignore create mode 100644 SOURCES/.cvsignore create mode 100644 SOURCES/90-epel.preset create mode 100644 SOURCES/GPL create mode 100644 SOURCES/README-epel-8-packaging.md create mode 100644 SOURCES/RPM-GPG-KEY-EPEL-8 create mode 100755 SOURCES/crb create mode 100644 SOURCES/epel-modular.repo create mode 100644 SOURCES/epel-next-testing.repo create mode 100644 SOURCES/epel-next.repo create mode 100644 SOURCES/epel-testing-modular.repo create mode 100644 SOURCES/epel-testing.repo create mode 100644 SOURCES/epel.repo create mode 100644 SPECS/epel-release.spec diff --git a/.epel-release.metadata b/.epel-release.metadata new file mode 100644 index 0000000..e69de29 diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..e69de29 diff --git a/SOURCES/.cvsignore b/SOURCES/.cvsignore new file mode 100644 index 0000000..e69de29 diff --git a/SOURCES/90-epel.preset b/SOURCES/90-epel.preset new file mode 100644 index 0000000..b3f4e22 --- /dev/null +++ b/SOURCES/90-epel.preset @@ -0,0 +1,9 @@ +# Also see: +# https://fedoraproject.org/wiki/Starting_services_by_default +# +# https://bugzilla.redhat.com/show_bug.cgi?id=1901721 +enable x509watch.timer +# +# https://bugzilla.redhat.com/show_bug.cgi?id=1986205 +# +enable certbot-renew.timer diff --git a/SOURCES/GPL b/SOURCES/GPL new file mode 100644 index 0000000..3c10746 --- /dev/null +++ b/SOURCES/GPL @@ -0,0 +1,347 @@ +***************************************************************************** +The following copyright applies to the Red Hat Linux compilation and any +portions of Red Hat Linux it does not conflict with. Whenever this +policy does conflict with the copyright of any individual portion of Red Hat +Linux, it does not apply. + +***************************************************************************** + + GNU GENERAL PUBLIC LICENSE + Version 2, June 1991 + + Copyright (C) 1989, 1991 Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA + Everyone is permitted to copy and distribute verbatim copies + of this license document, but changing it is not allowed. + + Preamble + + The licenses for most software are designed to take away your +freedom to share and change it. By contrast, the GNU General Public +License is intended to guarantee your freedom to share and change free +software--to make sure the software is free for all its users. This +General Public License applies to most of the Free Software +Foundation's software and to any other program whose authors commit to +using it. (Some other Free Software Foundation software is covered by +the GNU Lesser General Public License instead.) You can apply it to +your programs, too. + + When we speak of free software, we are referring to freedom, not +price. Our General Public Licenses are designed to make sure that you +have the freedom to distribute copies of free software (and charge for +this service if you wish), that you receive source code or can get it +if you want it, that you can change the software or use pieces of it +in new free programs; and that you know you can do these things. + + To protect your rights, we need to make restrictions that forbid +anyone to deny you these rights or to ask you to surrender the rights. +These restrictions translate to certain responsibilities for you if you +distribute copies of the software, or if you modify it. + + For example, if you distribute copies of such a program, whether +gratis or for a fee, you must give the recipients all the rights that +you have. You must make sure that they, too, receive or can get the +source code. And you must show them these terms so they know their +rights. + + We protect your rights with two steps: (1) copyright the software, and +(2) offer you this license which gives you legal permission to copy, +distribute and/or modify the software. + + Also, for each author's protection and ours, we want to make certain +that everyone understands that there is no warranty for this free +software. If the software is modified by someone else and passed on, we +want its recipients to know that what they have is not the original, so +that any problems introduced by others will not reflect on the original +authors' reputations. + + Finally, any free program is threatened constantly by software +patents. We wish to avoid the danger that redistributors of a free +program will individually obtain patent licenses, in effect making the +program proprietary. To prevent this, we have made it clear that any +patent must be licensed for everyone's free use or not licensed at all. + + The precise terms and conditions for copying, distribution and +modification follow. + + GNU GENERAL PUBLIC LICENSE + TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION + + 0. This License applies to any program or other work which contains +a notice placed by the copyright holder saying it may be distributed +under the terms of this General Public License. The "Program", below, +refers to any such program or work, and a "work based on the Program" +means either the Program or any derivative work under copyright law: +that is to say, a work containing the Program or a portion of it, +either verbatim or with modifications and/or translated into another +language. (Hereinafter, translation is included without limitation in +the term "modification".) Each licensee is addressed as "you". + +Activities other than copying, distribution and modification are not +covered by this License; they are outside its scope. The act of +running the Program is not restricted, and the output from the Program +is covered only if its contents constitute a work based on the +Program (independent of having been made by running the Program). +Whether that is true depends on what the Program does. + + 1. You may copy and distribute verbatim copies of the Program's +source code as you receive it, in any medium, provided that you +conspicuously and appropriately publish on each copy an appropriate +copyright notice and disclaimer of warranty; keep intact all the +notices that refer to this License and to the absence of any warranty; +and give any other recipients of the Program a copy of this License +along with the Program. + +You may charge a fee for the physical act of transferring a copy, and +you may at your option offer warranty protection in exchange for a fee. + + 2. You may modify your copy or copies of the Program or any portion +of it, thus forming a work based on the Program, and copy and +distribute such modifications or work under the terms of Section 1 +above, provided that you also meet all of these conditions: + + a) You must cause the modified files to carry prominent notices + stating that you changed the files and the date of any change. + + b) You must cause any work that you distribute or publish, that in + whole or in part contains or is derived from the Program or any + part thereof, to be licensed as a whole at no charge to all third + parties under the terms of this License. + + c) If the modified program normally reads commands interactively + when run, you must cause it, when started running for such + interactive use in the most ordinary way, to print or display an + announcement including an appropriate copyright notice and a + notice that there is no warranty (or else, saying that you provide + a warranty) and that users may redistribute the program under + these conditions, and telling the user how to view a copy of this + License. (Exception: if the Program itself is interactive but + does not normally print such an announcement, your work based on + the Program is not required to print an announcement.) + +These requirements apply to the modified work as a whole. If +identifiable sections of that work are not derived from the Program, +and can be reasonably considered independent and separate works in +themselves, then this License, and its terms, do not apply to those +sections when you distribute them as separate works. But when you +distribute the same sections as part of a whole which is a work based +on the Program, the distribution of the whole must be on the terms of +this License, whose permissions for other licensees extend to the +entire whole, and thus to each and every part regardless of who wrote it. + +Thus, it is not the intent of this section to claim rights or contest +your rights to work written entirely by you; rather, the intent is to +exercise the right to control the distribution of derivative or +collective works based on the Program. + +In addition, mere aggregation of another work not based on the Program +with the Program (or with a work based on the Program) on a volume of +a storage or distribution medium does not bring the other work under +the scope of this License. + + 3. You may copy and distribute the Program (or a work based on it, +under Section 2) in object code or executable form under the terms of +Sections 1 and 2 above provided that you also do one of the following: + + a) Accompany it with the complete corresponding machine-readable + source code, which must be distributed under the terms of Sections + 1 and 2 above on a medium customarily used for software interchange; or, + + b) Accompany it with a written offer, valid for at least three + years, to give any third party, for a charge no more than your + cost of physically performing source distribution, a complete + machine-readable copy of the corresponding source code, to be + distributed under the terms of Sections 1 and 2 above on a medium + customarily used for software interchange; or, + + c) Accompany it with the information you received as to the offer + to distribute corresponding source code. (This alternative is + allowed only for noncommercial distribution and only if you + received the program in object code or executable form with such + an offer, in accord with Subsection b above.) + +The source code for a work means the preferred form of the work for +making modifications to it. For an executable work, complete source +code means all the source code for all modules it contains, plus any +associated interface definition files, plus the scripts used to +control compilation and installation of the executable. However, as a +special exception, the source code distributed need not include +anything that is normally distributed (in either source or binary +form) with the major components (compiler, kernel, and so on) of the +operating system on which the executable runs, unless that component +itself accompanies the executable. + +If distribution of executable or object code is made by offering +access to copy from a designated place, then offering equivalent +access to copy the source code from the same place counts as +distribution of the source code, even though third parties are not +compelled to copy the source along with the object code. + + 4. You may not copy, modify, sublicense, or distribute the Program +except as expressly provided under this License. Any attempt +otherwise to copy, modify, sublicense or distribute the Program is +void, and will automatically terminate your rights under this License. +However, parties who have received copies, or rights, from you under +this License will not have their licenses terminated so long as such +parties remain in full compliance. + + 5. You are not required to accept this License, since you have not +signed it. However, nothing else grants you permission to modify or +distribute the Program or its derivative works. These actions are +prohibited by law if you do not accept this License. Therefore, by +modifying or distributing the Program (or any work based on the +Program), you indicate your acceptance of this License to do so, and +all its terms and conditions for copying, distributing or modifying +the Program or works based on it. + + 6. Each time you redistribute the Program (or any work based on the +Program), the recipient automatically receives a license from the +original licensor to copy, distribute or modify the Program subject to +these terms and conditions. You may not impose any further +restrictions on the recipients' exercise of the rights granted herein. +You are not responsible for enforcing compliance by third parties to +this License. + + 7. If, as a consequence of a court judgment or allegation of patent +infringement or for any other reason (not limited to patent issues), +conditions are imposed on you (whether by court order, agreement or +otherwise) that contradict the conditions of this License, they do not +excuse you from the conditions of this License. If you cannot +distribute so as to satisfy simultaneously your obligations under this +License and any other pertinent obligations, then as a consequence you +may not distribute the Program at all. For example, if a patent +license would not permit royalty-free redistribution of the Program by +all those who receive copies directly or indirectly through you, then +the only way you could satisfy both it and this License would be to +refrain entirely from distribution of the Program. + +If any portion of this section is held invalid or unenforceable under +any particular circumstance, the balance of the section is intended to +apply and the section as a whole is intended to apply in other +circumstances. + +It is not the purpose of this section to induce you to infringe any +patents or other property right claims or to contest validity of any +such claims; this section has the sole purpose of protecting the +integrity of the free software distribution system, which is +implemented by public license practices. Many people have made +generous contributions to the wide range of software distributed +through that system in reliance on consistent application of that +system; it is up to the author/donor to decide if he or she is willing +to distribute software through any other system and a licensee cannot +impose that choice. + +This section is intended to make thoroughly clear what is believed to +be a consequence of the rest of this License. + + 8. If the distribution and/or use of the Program is restricted in +certain countries either by patents or by copyrighted interfaces, the +original copyright holder who places the Program under this License +may add an explicit geographical distribution limitation excluding +those countries, so that distribution is permitted only in or among +countries not thus excluded. In such case, this License incorporates +the limitation as if written in the body of this License. + + 9. The Free Software Foundation may publish revised and/or new versions +of the General Public License from time to time. Such new versions will +be similar in spirit to the present version, but may differ in detail to +address new problems or concerns. + +Each version is given a distinguishing version number. If the Program +specifies a version number of this License which applies to it and "any +later version", you have the option of following the terms and conditions +either of that version or of any later version published by the Free +Software Foundation. If the Program does not specify a version number of +this License, you may choose any version ever published by the Free Software +Foundation. + + 10. If you wish to incorporate parts of the Program into other free +programs whose distribution conditions are different, write to the author +to ask for permission. For software which is copyrighted by the Free +Software Foundation, write to the Free Software Foundation; we sometimes +make exceptions for this. Our decision will be guided by the two goals +of preserving the free status of all derivatives of our free software and +of promoting the sharing and reuse of software generally. + + NO WARRANTY + + 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY +FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN +OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES +PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED +OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF +MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS +TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE +PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, +REPAIR OR CORRECTION. + + 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING +WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR +REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, +INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING +OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED +TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY +YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER +PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE +POSSIBILITY OF SUCH DAMAGES. + + END OF TERMS AND CONDITIONS + + How to Apply These Terms to Your New Programs + + If you develop a new program, and you want it to be of the greatest +possible use to the public, the best way to achieve this is to make it +free software which everyone can redistribute and change under these terms. + + To do so, attach the following notices to the program. It is safest +to attach them to the start of each source file to most effectively +convey the exclusion of warranty; and each file should have at least +the "copyright" line and a pointer to where the full notice is found. + + + Copyright (C) + + This program is free software; you can redistribute it and/or modify + it under the terms of the GNU General Public License as published by + the Free Software Foundation; either version 2 of the License, or + (at your option) any later version. + + This program is distributed in the hope that it will be useful, + but WITHOUT ANY WARRANTY; without even the implied warranty of + MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + GNU General Public License for more details. + + You should have received a copy of the GNU General Public License along + with this program; if not, write to the Free Software Foundation, Inc., + 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA. + +Also add information on how to contact you by electronic and paper mail. + +If the program is interactive, make it output a short notice like this +when it starts in an interactive mode: + + Gnomovision version 69, Copyright (C) year name of author + Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. + This is free software, and you are welcome to redistribute it + under certain conditions; type `show c' for details. + +The hypothetical commands `show w' and `show c' should show the appropriate +parts of the General Public License. Of course, the commands you use may +be called something other than `show w' and `show c'; they could even be +mouse-clicks or menu items--whatever suits your program. + +You should also get your employer (if you work as a programmer) or your +school, if any, to sign a "copyright disclaimer" for the program, if +necessary. Here is a sample; alter the names: + + Yoyodyne, Inc., hereby disclaims all copyright interest in the program + `Gnomovision' (which makes passes at compilers) written by James Hacker. + + , 1 April 1989 + Ty Coon, President of Vice + +This General Public License does not permit incorporating your program into +proprietary programs. If your program is a subroutine library, you may +consider it more useful to permit linking proprietary applications with the +library. If this is what you want to do, use the GNU Lesser General +Public License instead of this License. diff --git a/SOURCES/README-epel-8-packaging.md b/SOURCES/README-epel-8-packaging.md new file mode 100644 index 0000000..91b2712 --- /dev/null +++ b/SOURCES/README-epel-8-packaging.md @@ -0,0 +1,164 @@ +# EPEL-8 Packaging Procedures + +## Introduction + +When a new Red Hat Enterprise Linux occurs, one of the steps to get +EPEL going for it is branching of various packages into new +namespace. The EPEL Steering Committee does not mass branch all +existing packages into the namespace because it has caused multiple +problems: + +1. The package maintainers did not want to support the package in the +newer version of EPEL. Package maintainers may only want to support +certain versions of Enterprise Linux or may want to wait until their +favourite derivative appears. + +2. The package does not work in the latest version of RHEL. With +multiple years between releases, software which worked on Fedora 18 +which would branch to EPEL-7 may not exist anymore with Fedora 28 and +EPEL-8 would need a completely different version. + +## Consumer request for packages + +People who are interested in getting packages into EPEL should contact +the package maintainer through +[bugzilla](https://bugzilla.redhat.com/). This allows for the requests +to be tracked and if the primary maintainer is not interested in +branching to EPEL, other ones can step in and do so. + +## EPEL Next + +EPEL packages are built against RHEL. EPEL Next is an additional repository +that allows package maintainers to alternatively build against CentOS Stream. +This is sometimes necessary when CentOS Stream contains an upcoming RHEL +library rebase, or if an EPEL package has a minimum version build requirement +that is already in CentOS Stream but not yet in RHEL. EPEL Next has its own +distgit branches, koji build targets, and bodhi releases. + +EPEL Next packages have `.next` appended to the disttag (e.g. a disttag of +`.el8.next` for epel8-next) to provide an upgrade path from an EPEL package +that was built from the same distgit commit. A package maintainer can rebuild +the same commit for both EPEL and EPEL Next and get two different NVRs in koji. +Within six months, the build requirement necessitating building in EPEL Next +should be in RHEL, and at that time the package maintainer can do a normal +release bump commit in the EPEL branch and get a newer NVR than both the +previous EPEL and EPEL Next packages. + +To get started with EPEL Next, request the corresponding branch for the EPEL +release you are targeting, e.g. request an epel8-next branch to rebuild an +epel8 package against CentOS Stream 8. Once the branch is created you can +merge commits from other branches and submit a build just like you would for +other EPEL or Fedora branches. + +## EPEL Playground + +EPEL Playground was shut down in January 2022 + +EPEL 8 Playground was a place that developers and maintainers could +"play around" with updated, or changed packages in epel. EPEL Playground +never really worked out and ended up being more burden than helpful. + +If developers or maintainers want something similar to EPEL Playground +we recommend Fedora COPR, which has availability for EPEL builds. + + +## Developer request for branching multiple packages + +Branching is handled the same way as requesting a branch using `fedpkg +request-branch`. A maintainer can request an epel8 branch using +`fedpkg request-branch epel8` which will create a ticket in +https://pagure.io/releng/fedora-scm-requests/issues and Release +Engineering will process these requests. + +To branch multiple packages please use this or a variant of this +script: + +``` +#!/usr/bin/sh +# Reminder to get an updated pagure token for releng tickets +# Usage: epel-8.sh foo bar goo blah blech +if [ $# -lt 1 ] +then + echo "At least one package name should be provided" +else + TMPDIR=`mktemp -d /tmp/epel8.XXXXXX` + pushd "$TMPDIR" + for pkg in "$@" + do + fedpkg clone "$pkg" + pushd "$pkg" + fedpkg request-branch epel8 + fedpkg request-branch epel8-playground + popd + done + rm -rfv "$TMPDIR" +fi +``` + +Releng will then work through the tickets in the system which is +adding branches to the PDC and src.fedoraproject.org. + + +## Known Issues + +1. /usr/bin/python does not exist. Choose ``/usr/bin/python3`` or +``/usr/bin/python2`` and patch appropriately. + +2. ``python2-sphinx`` is not shipped. Most packages should work with +python3-sphinx, and if it doesn't please open a bug. The python team +has been good about making fixes for this. + +3. When branching python packages, be aware that python in EL-8 is +python36 and not the version currently in rawhide. This has come up +with a couple of test packages where they assumed python37 or later. + +4. ``systemd-rpm-macros`` is not a separate packages. If needed, used +``BuildRequires: systemd`` + +5. While EL-8 comes with platform-python, it should NOT be used in +``Requires:`` unless absolutely neccessary. python3 should be used +instead. (Exceptions can be made but will be rare and need +justification.) + +**Accepted Exceptions:** +* Use python3.6dist(coverage) instead of python3-coverage. This + package is not shipped but is needed in %check code. + +6. Sometimes RHEL8 only has a python3 package for a dependency you +need for your build. (Example: python-bleach requires +python2-html5lib, but RHEL8 provides only python3-html5lib). For +EPEL-8.0 we only suggest one choice: + +* Choose not to have the python2 part of your package and patch + whatever to use python3. + +7. Python2 packages are discouraged. RHEL-8 will contain python2.7 +until probably the end of life of RHEL-7. However support upstream +will only be minimal. When modularity occurs, we suggest that you make +whatever python2 packages modules which can be pulled out when +RHEL-8.N no longer has python2. + +8. While a RHEL src.rpm might produce a -devel package, it may not +currently be in the build repository. When running into this please +open a ticket with https://pagure.io/epel/new_issue for us to put in a +request for it to be added to Red Hat's Code Ready Builder. After +modularity is enabled, changes to what is done will be needed. + +9. EPEL-8.0 may not work with the RHEL-8.1 beta. There seem to be +changes in dnf and zchunk which we have not worked out. This line will +be updated. + + +## Definitions + +1. Package maintainer. Person who has accepted responsibility to +package and maintain software in the Fedora Project ecosystem. The +main packager is usually someone focused on Fedora Linux, and +secondary packagers may be focused on particular use cases like EPEL. + +2. Consumer. A person who has subscribed to EPEL for packages but is +not a maintainer. + +3. PDC. Product Definition Center. A tool to help list the lifetime +and permissions that a product has so that branching and updates can +be better managed. diff --git a/SOURCES/RPM-GPG-KEY-EPEL-8 b/SOURCES/RPM-GPG-KEY-EPEL-8 new file mode 100644 index 0000000..30b69a6 --- /dev/null +++ b/SOURCES/RPM-GPG-KEY-EPEL-8 @@ -0,0 +1,28 @@ +-----BEGIN PGP PUBLIC KEY BLOCK----- + +mQINBFz3zvsBEADJOIIWllGudxnpvJnkxQz2CtoWI7godVnoclrdl83kVjqSQp+2 +dgxuG5mUiADUfYHaRQzxKw8efuQnwxzU9kZ70ngCxtmbQWGmUmfSThiapOz00018 ++eo5MFabd2vdiGo1y+51m2sRDpN8qdCaqXko65cyMuLXrojJHIuvRA/x7iqOrRfy +a8x3OxC4PEgl5pgDnP8pVK0lLYncDEQCN76D9ubhZQWhISF/zJI+e806V71hzfyL +/Mt3mQm/li+lRKU25Usk9dWaf4NH/wZHMIPAkVJ4uD4H/uS49wqWnyiTYGT7hUbi +ecF7crhLCmlRzvJR8mkRP6/4T/F3tNDPWZeDNEDVFUkTFHNU6/h2+O398MNY/fOh +yKaNK3nnE0g6QJ1dOH31lXHARlpFOtWt3VmZU0JnWLeYdvap4Eff9qTWZJhI7Cq0 +Wm8DgLUpXgNlkmquvE7P2W5EAr2E5AqKQoDbfw/GiWdRvHWKeNGMRLnGI3QuoX3U +pAlXD7v13VdZxNydvpeypbf/AfRyrHRKhkUj3cU1pYkM3DNZE77C5JUe6/0nxbt4 +ETUZBTgLgYJGP8c7PbkVnO6I/KgL1jw+7MW6Az8Ox+RXZLyGMVmbW/TMc8haJfKL +MoUo3TVk8nPiUhoOC0/kI7j9ilFrBxBU5dUtF4ITAWc8xnG6jJs/IsvRpQARAQAB +tChGZWRvcmEgRVBFTCAoOCkgPGVwZWxAZmVkb3JhcHJvamVjdC5vcmc+iQI4BBMB +AgAiBQJc9877AhsPBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAh6kWrL4bW +oWagD/4xnLWws34GByVDQkjprk0fX7Iyhpm/U7BsIHKspHLL+Y46vAAGY/9vMvdE +0fcr9Ek2Zp7zE1RWmSCzzzUgTG6BFoTG1H4Fho/7Z8BXK/jybowXSZfqXnTOfhSF +alwDdwlSJvfYNV9MbyvbxN8qZRU1z7PEWZrIzFDDToFRk0R71zHpnPTNIJ5/YXTw +NqU9OxII8hMQj4ufF11040AJQZ7br3rzerlyBOB+Jd1zSPVrAPpeMyJppWFHSDAI +WK6x+am13VIInXtqB/Cz4GBHLFK5d2/IYspVw47Solj8jiFEtnAq6+1Aq5WH3iB4 +bE2e6z00DSF93frwOyWN7WmPIoc2QsNRJhgfJC+isGQAwwq8xAbHEBeuyMG8GZjz +xohg0H4bOSEujVLTjH1xbAG4DnhWO/1VXLX+LXELycO8ZQTcjj/4AQKuo4wvMPrv +9A169oETG+VwQlNd74VBPGCvhnzwGXNbTK/KH1+WRH0YSb+41flB3NKhMSU6dGI0 +SGtIxDSHhVVNmx2/6XiT9U/znrZsG5Kw8nIbbFz+9MGUUWgJMsd1Zl9R8gz7V9fp +n7L7y5LhJ8HOCMsY/Z7/7HUs+t/A1MI4g7Q5g5UuSZdgi0zxukiWuCkLeAiAP4y7 +zKK4OjJ644NDcWCHa36znwVmkz3ixL8Q0auR15Oqq2BjR/fyog== +=84m8 +-----END PGP PUBLIC KEY BLOCK----- diff --git a/SOURCES/crb b/SOURCES/crb new file mode 100755 index 0000000..07941a2 --- /dev/null +++ b/SOURCES/crb @@ -0,0 +1,85 @@ +#!/bin/bash +# Enable / Disable / Status the codeready-builder(CRB) or equivalent repo. + +############### +# Show help +############### +usage() { + echo "Usage `basename $0` [ enable | disable | status ] " >&2 + echo >&2 + echo "Enable, Disable, or give the status of the CodeReady Builder (CRB) repo" >&2 + echo >&2 + echo "Options:" >&2 + echo " enable" >&2 + echo " Enable the CRB repo" >&2 + echo " disable" >&2 + echo " Disable the CRB repo" >&2 + echo " status" >&2 + echo " Show if rhe CRB repo is enabled or disabled" >&2 + echo " help" >&2 + echo " Show this options menu" >&2 + echo >&2 + popd &>/dev/null + exit 1 +} + + +# Show the status +show_status()( + # Determine if a version of CRB is enabled + crb_repo=$(dnf repolist | grep -i -e crb -e powertools -e codeready | grep -v -i -e debug -e source -e eus -e virt | awk '{print $1}') + if [ "${crb_repo}" == "" ] ; then + echo "CRB repo is disabled" + else + echo "CRB repo is enabled and named: ${crb_repo}" + fi +) + +# Enable or Disable the repo +enable_disable_repo(){ + command="$1" + # Determine which repo we need to change + crb_repo=$(dnf repolist --all | grep -i -e crb -e powertools -e codeready | grep -v -i -e debug -e source -e eus -e virt | awk '{print $1}') + + # Determine if we are on RHEL or not, then do the correct steps + source /etc/os-release + if [[ "${NAME}" =~ "Red Hat" ]] ; then + subscription-manager repos ${command} ${crb_repo} + else + # Determine if dnf-command(config-manager) is installed + if ! rpm -q --whatprovides 'dnf-command(config-manager)' > /dev/null 2>&1 ; then + echo "Error: Please run: dnf install 'dnf-command(config-manager)'" >&2 + echo " before trying to enable/disable the CRB repo." >&2 + echo "Aborting"'!' >&2 + exit 1 + fi + # Everything else uses dnf config-manager + dnf config-manager ${command} ${crb_repo} + fi +} + +############### +# Get our arguments +############### +key="$1" +case $key in +enable | --enable ) + echo "Enabling CRB repo" + enable_disable_repo --enable + show_status +;; +disable | --disable ) + echo "Disabling CRB repo" + enable_disable_repo --disable + show_status +;; +status | --status ) + show_status +;; +* ) + usage + exit 2 +;; +esac + +exit 0 diff --git a/SOURCES/epel-modular.repo b/SOURCES/epel-modular.repo new file mode 100644 index 0000000..d9d3ab6 --- /dev/null +++ b/SOURCES/epel-modular.repo @@ -0,0 +1,33 @@ +[epel-modular] +# This repo has been RETIRED, see https://pagure.io/epel/issue/198 for more details. +name=Extra Packages for Enterprise Linux Modular 8 - $basearch - RETIRED +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/8/Modular/$basearch +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-modular-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgcheck=1 +countme=1 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 + +[epel-modular-debuginfo] +# This repo has been RETIRED, see https://pagure.io/epel/issue/198 for more details. +name=Extra Packages for Enterprise Linux Modular 8 - $basearch - Debug - RETIRED +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/8/Modular/$basearch/debug +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-modular-debug-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 + +[epel-modular-source] +# This repo has been RETIRED, see https://pagure.io/epel/issue/198 for more details. +name=Extra Packages for Enterprise Linux Modular 8 - $basearch - Source - RETIRED +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place it's address here. +#baseurl=https://download.example/pub/epel/8/Modular/source/tree/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-modular-source-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 diff --git a/SOURCES/epel-next-testing.repo b/SOURCES/epel-next-testing.repo new file mode 100644 index 0000000..ce3dfbe --- /dev/null +++ b/SOURCES/epel-next-testing.repo @@ -0,0 +1,30 @@ +[epel-next-testing] +name=Extra Packages for Enterprise Linux 8 - Next - Testing - $basearch +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/testing/next/8/Everything/$basearch/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-testing-next-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgcheck=1 +countme=1 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 + +[epel-next-testing-debuginfo] +name=Extra Packages for Enterprise Linux 8 - Next - Testing - $basearch - Debug +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/testing/next/8/Everything/$basearch/debug/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-testing-next-debug-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 + +[epel-next-testing-source] +name=Extra Packages for Enterprise Linux 8 - Next - Testing - $basearch - Source +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place it's address here. +#baseurl=https://download.example/pub/epel/testing/next/8/Everything/source/tree/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-testing-next-source-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 diff --git a/SOURCES/epel-next.repo b/SOURCES/epel-next.repo new file mode 100644 index 0000000..f665d29 --- /dev/null +++ b/SOURCES/epel-next.repo @@ -0,0 +1,30 @@ +[epel-next] +name=Extra Packages for Enterprise Linux 8 - Next - $basearch +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/next/8/Everything/$basearch/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-next-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=1 +gpgcheck=1 +countme=1 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 + +[epel-next-debuginfo] +name=Extra Packages for Enterprise Linux 8 - Next - $basearch - Debug +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/next/8/Everything/$basearch/debug/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-next-debug-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 + +[epel-next-source] +name=Extra Packages for Enterprise Linux 8 - Next - $basearch - Source +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place it's address here. +#baseurl=https://download.example/pub/epel/next/8/Everything/source/tree/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-next-source-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 diff --git a/SOURCES/epel-testing-modular.repo b/SOURCES/epel-testing-modular.repo new file mode 100644 index 0000000..05d4dfe --- /dev/null +++ b/SOURCES/epel-testing-modular.repo @@ -0,0 +1,33 @@ +[epel-testing-modular] +# This repo has been RETIRED, see https://pagure.io/epel/issue/198 for more details. +name=Extra Packages for Enterprise Linux Modular 8 - Testing - $basearch - RETIRED +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/testing/8/Modular/$basearch +metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-modular-epel8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgcheck=1 +countme=1 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 + +[epel-testing-modular-debuginfo] +# This repo has been RETIRED, see https://pagure.io/epel/issue/198 for more details. +name=Extra Packages for Enterprise Linux Modular 8 - Testing - $basearch - Debug - RETIRED +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/testing/8/Modular/$basearch/debug +metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-modular-debug-epel8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 + +[epel-testing-modular-source] +# This repo has been RETIRED, see https://pagure.io/epel/issue/198 for more details. +name=Extra Packages for Enterprise Linux Modular 8 - Testing - $basearch - Source - RETIRED +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place it's address here. +#baseurl=https://download.example/pub/epel/testing/8/Modular/source/tree/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-modular-source-epel8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 diff --git a/SOURCES/epel-testing.repo b/SOURCES/epel-testing.repo new file mode 100644 index 0000000..5fd8943 --- /dev/null +++ b/SOURCES/epel-testing.repo @@ -0,0 +1,30 @@ +[epel-testing] +name=Extra Packages for Enterprise Linux 8 - Testing - $basearch +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/testing/8/Everything/$basearch +metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-epel8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgcheck=1 +countme=1 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 + +[epel-testing-debuginfo] +name=Extra Packages for Enterprise Linux 8 - Testing - $basearch - Debug +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/testing/8/Everything/$basearch/debug +metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-debug-epel8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 + +[epel-testing-source] +name=Extra Packages for Enterprise Linux 8 - Testing - $basearch - Source +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place it's address here. +#baseurl=https://download.example/pub/epel/testing/8/Everything/source/tree/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=testing-source-epel8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 diff --git a/SOURCES/epel.repo b/SOURCES/epel.repo new file mode 100644 index 0000000..f50e424 --- /dev/null +++ b/SOURCES/epel.repo @@ -0,0 +1,30 @@ +[epel] +name=Extra Packages for Enterprise Linux 8 - $basearch +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/8/Everything/$basearch +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=1 +gpgcheck=1 +countme=1 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 + +[epel-debuginfo] +name=Extra Packages for Enterprise Linux 8 - $basearch - Debug +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place its address here. +#baseurl=https://download.example/pub/epel/8/Everything/$basearch/debug +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-debug-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 + +[epel-source] +name=Extra Packages for Enterprise Linux 8 - $basearch - Source +# It is much more secure to use the metalink, but if you wish to use a local mirror +# place it's address here. +#baseurl=https://download.example/pub/epel/8/Everything/source/tree/ +metalink=https://mirrors.fedoraproject.org/metalink?repo=epel-source-8&arch=$basearch&infra=$infra&content=$contentdir +enabled=0 +gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-8 +gpgcheck=1 diff --git a/SPECS/epel-release.spec b/SPECS/epel-release.spec new file mode 100644 index 0000000..f807d54 --- /dev/null +++ b/SPECS/epel-release.spec @@ -0,0 +1,212 @@ +Name: epel-release +Version: 8 +Release: 19%{dist} +Summary: Extra Packages for Enterprise Linux repository configuration + +License: GPLv2 + +# This is a EPEL maintained package which is specific to +# our distribution. Thus the source is only available from +# within this srpm. +URL: http://download.fedoraproject.org/pub/epel +Source0: http://download.fedoraproject.org/pub/epel/RPM-GPG-KEY-EPEL-8 +Source1: GPL +Source2: README-epel-8-packaging.md +# EPEL default preset policy (borrowed from fedora's 90-default.preset) +Source3: 90-epel.preset + + +Source100: epel.repo +Source101: epel-testing.repo +Source102: epel-next.repo +Source103: epel-next-testing.repo +Source105: epel-modular.repo +Source106: epel-testing-modular.repo + +# Add epel crb repo +Source301: crb + +BuildArch: noarch +Requires: redhat-release >= %{version} +# epel-release is only for enterprise linux, not fedora +Conflicts: fedora-release +# crb needs config-manager to run +# But only recommend it, incase people do not need crb +Recommends: dnf-command(config-manager) +Recommends: (epel-next-release if centos-stream-release) + + +%description +This package contains the Extra Packages for Enterprise Linux (EPEL) repository +GPG key as well as configuration for yum. + + +%package -n epel-next-release +Summary: Extra Packages for Enterprise Linux Next repository configuration +Requires: %{name} = %{version}-%{release} + + +%description -n epel-next-release +This package contains the Extra Packages for Enterprise Linux (EPEL) Next +configuration for yum. + + +%prep +%setup -q -c -T +install -pm 644 %{SOURCE1} . +install -pm 644 %{SOURCE2} . + + +%install +#GPG Key +install -Dpm 644 %{SOURCE0} \ + %{buildroot}%{_sysconfdir}/pki/rpm-gpg/RPM-GPG-KEY-EPEL-%{version} + +# yum +install -dm 755 %{buildroot}%{_sysconfdir}/yum.repos.d +install -pm 644 %{SOURCE100} %{SOURCE101} %{SOURCE102} %{SOURCE103} %{SOURCE105} %{SOURCE106} \ + %{buildroot}%{_sysconfdir}/yum.repos.d +install -pm 644 -D %{SOURCE3} %{buildroot}%{_prefix}/lib/systemd/system-preset/90-epel.preset + +# Add epel crb repo +install -D -pm744 -t %{buildroot}%{_bindir} %{SOURCE301} + +%post +# Doing a check to see if crb is enabled is as hard and resource intense as enabling or disabling crb. +# So we will say crb is recommended, without first checking. But only on the initial install. +if [ "$1" -eq 1 ] ; then + echo "Many EPEL packages require the CodeReady Builder (CRB) repository." + echo "It is recommended that you run %{_bindir}/crb enable to enable the CRB repository." +fi + + +%files +%doc README-epel-8-packaging.md +%license GPL +%config(noreplace) %{_sysconfdir}/yum.repos.d/epel.repo +%config(noreplace) %{_sysconfdir}/yum.repos.d/epel-testing.repo +%config(noreplace) %{_sysconfdir}/yum.repos.d/epel-modular.repo +%config(noreplace) %{_sysconfdir}/yum.repos.d/epel-testing-modular.repo +%{_sysconfdir}/pki/rpm-gpg/* +%{_prefix}/lib/systemd/system-preset/90-epel.preset +%{_bindir}/crb + + +%files -n epel-next-release +%config(noreplace) %{_sysconfdir}/yum.repos.d/epel-next.repo +%config(noreplace) %{_sysconfdir}/yum.repos.d/epel-next-testing.repo + + +%changelog +* Wed Mar 20 2024 MSVSphere Packaging Team - 8-19 +- Rebuilt for MSVSphere 8.9 + +* Mon Apr 17 2023 Troy Dawson - 8-19 +- Tweak crb script, check os-release for RHEL (#2186721) + +* Thu Sep 29 2022 Carl George - 8-18 +- Disable epel-modular repo by default +- Mark all epel-modular repos as deprecated + +* Tue Aug 09 2022 Troy Dawson - 8-17 +- Tweak crb script, Recommends dnf-command(config-manager) (#2115602) + +* Thu Jun 30 2022 Troy Dawson - 8-16 +- Add crb script + +* Mon Mar 14 2022 Troy Dawson - 8-15 +- Remove the use of $releasever ( rhbz#1969500 ) + +* Fri Jan 28 2022 Troy Dawson - 8-14 +- Remove epel8-playground repo +- Update playground section in README-epel-8-packaging.md + +* Fri Sep 03 2021 Mohan Boddu - 8-13 +- Change the baseurl to point to source/tree for srpms + +* Fri Jul 30 2021 Kevin Fenzi - 8-12 +- Enable certbot-renew.timer ( rhbz#1986205 ) + +* Thu Jun 03 2021 Carl George - 8-11 +- Add epel-next-release subpackage + +* Sat Dec 05 2020 Kevin Fenzi - 8-10 +- Add x509watch.timer enabled by default. Fixes bug #1901721 + +* Sat Oct 31 2020 Kevin Fenzi - 8-9 +- Add countme feature for epel. Fixes bug #1825984 + +* Fri Dec 13 2019 Merlin Mathesius - 8-8%{dist} +- Add modular repos. + +* Thu Oct 10 2019 Stephen Smoogen - 8-7%{dist} +- Remove failovermethod from EPEL8 tree. It is no longer needed. + +* Mon Sep 16 2019 Stephen Smoogen - 8-6%{dist} +- Change gpg key to use -8 versus -$releasever. This fixes bash problem + +* Tue Aug 6 2019 Stephen Smoogen - 8-5%{dist} +- Fix playground release to have os/ on its name [Kevin Fenzi] +- Make sure all values of $release are $releasever + + +* Thu Aug 1 2019 Pablo Greco - 8-4 +- Use the correct var for dnf to expand +- Update playground source url +- Remove epel-modules repo +- Use https in baseurl + +* Thu Aug 1 2019 Stephen Smoogen - 8-3 +- Make sure that the key name is named correctly + +* Thu Aug 1 2019 Stephen Smoogen - 8-2 +- Make baseurl paths match dl.fedoraproject.org +- Add draft of epel8 packaging +- Fix docs + +* Thu Jul 18 2019 Stephen Smoogen - 8-1 +- Update for RHEL-8 +- Add playground repo data +- Clean out 90-epel.preset to make sure we dont override RHEL-8 items. Just add items in which EPEL needs. + +* Mon Oct 02 2017 Kevin Fenzi - 7-11 +- Add Conflicts on fedora-release to prevent people from installing on Fedora systems. Fixes bug #1497702 + +* Sat Jun 24 2017 Kevin Fenzi - 7-10 +- Change mirrorlist= in repo files to be metalink= (as thats what they are). Fixes bug #1451212 + +* Tue Dec 27 2016 Kevin Fenzi - 7-9 +- Add preset for drbdlinks package. Fixes bug #1405744 + +* Sat Jul 23 2016 Kevin Fenzi - 7-8 +- Drop duplicate libstoragemgmt from presets. Fixes bug #1358971 + +* Fri Jun 03 2016 Kevin Fenzi - 7-7 +- Drop initial-setup from presets. Fixes bug #1342511 + +* Wed Mar 30 2016 Jason L Tibbitts III - 7-6 +- Remove macros.epel; let epel-rpm-macros handle it instead. + +* Tue Nov 25 2014 Rex Dieter 7-5 +- fix typo in macros.epel + +* Fri Nov 21 2014 Rex Dieter 7-4 +- add systemd 90-epel.preset + +* Fri Nov 21 2014 Rex Dieter 7-3 +- implement %%epel macro + +* Tue Sep 02 2014 Kevin Fenzi 7-2 +- Make repo files config(noreplace). Fixes bug #1135576 + +* Thu Aug 28 2014 Dennis Gilmore - 7-1 +- enable gpg checking now we are out of beta + +* Wed Jun 18 2014 Kevin Fenzi 7-0.2 +- Drop unneeded up2date post/postun +- Fixed up description. +- Fixes bugs #1052434 and #1093918 + +* Mon Dec 16 2013 Dennis Gilmore - 7-0.1 +- initial epel 7 build. gpg cheking is disabled +