Language Selection

English French German Italian Portuguese Spanish

Announcing EPEL-8.0 Official Release

Filed under
Red Hat

The EPEL Steering Committee is pleased to announce that the initial EPEL-8 is ready for release. We would like to thank everyone in the community for helping us get the initial set of builds out to mirrors and to consumers worldwide. Special thanks go to Patrick Uiterwijk, Jeroen van Meeuwen, Robert Scheck, and many others in the community who helped in the last 6 months to get this release done.

EPEL-8.0 has packages for the x86_64, ppc64le, aarch64, and now the s390x platforms.
What is EPEL?

EPEL stands for Extra Packages for Enterprise Linux and is a subcommunity of the Fedora and CentOS projects aimed at bringing a subset of packages out of Fedora releases ready to be used and installed on various Red Hat Enterprise Linux (RHEL). It is not a complete rebuild of Fedora or even of previous EPEL releases. EPEL is also a community and not a product. As such we need community members to help get packages into the repository more than done in Fedora.

Read more

The full E-mail message

  • EPEL 8.0 released
    The EPEL Steering Committee is pleased to announce that the initial
    EPEL-8 is ready for release. We would like to thank everyone in the
    community for helping us get the initial set of builds out to mirrors
    and to consumers worldwide. Special thanks go to Patrick Uiterwijk,
    Jeroen van Meeuwen, Robert Scheck, and many others in the community
    who helped in the last 6 months to get this release done.
    
    EPEL-8.0 has packages for the x86_64, ppc64le, aarch64, and now the
    s390x platforms.
    
    ## What is EPEL?
    
    EPEL stands for Extra Packages for Enterprise Linux and is a
    subcommunity of the Fedora and CentOS projects aimed at bringing a
    subset of packages out of Fedora releases ready to be used and
    installed on various Red Hat Enterprise Linux (RHEL). It is not a
    complete rebuild of Fedora or even of previous EPEL releases. EPEL is
    also a community and not a product. As such we need community members
    to help get packages into the repository more than done in Fedora.
    
    If you are interested in getting a package into EPEL, contact the
    package maintainer through bugzilla. This way the request can be
    tracked, and if the primary maintainer is not interested in branching
    to EPEL, others can step in and do so. Optionally you can send a
    request to the epel-devel@lists.fedoraproject.org mailing list. If you
    do so, please include why the package is needed, to help other
    volunteers decide whether they can support it.
    
    ## What is new?
    
    ### Playground for Rawhide like things
    We have added an additional set of channels for EPEL-8 called
    playground. It is similar to Fedora Rawhide so packagers can work on
    versions of software that are too fast moving or will have large API
    changes compared to versions in the regular channel.
    
    To make this purpose transparent, when a package is built in epel8, it
    will normally also be built in epel8-playground. This is done via a
    packages.cfg file which lists the targets for fedpkg to build against.
    A successful package build will then go through two different paths:
    * epel8 package will go into bodhi to be put into epel8-testing
    * epel8-playground will bypass bodhi and go directly into
    epel8-playground the next compose.
    
    If a packager needs to focus only on epel8 or epel8-playground they
    can edit packages.cfg to change the target=epel8 epel8-playground to
    target=epel8.
    
    Packages in epel8-playground are intended to be used in the following manner:
    * To test out a new version of the package that might not be stable yet.
    * To test out new packaging of the package
    * To test a major version change of the package intended for the next
    EPEL-8 minor release.
    * To build a package that will never be stable enough for EPEL-8, but
    still could be useful to some.
    
    At minor RHEL releases (ie, 8.1, 8.2) people can pull in big changes
    from playground to the main EPEL-8 packages. Since people will be
    upgrading and paying more attention than usual anyhow at those points,
    it’s a great chance to do that change, but you can test beforehand in
    the playground to make sure these changes work.
    Consumers should be aware that packages in EPEL8-playground are
    without any Service Level Expectations. You may want to only cherry
    pick packages from the playground as needed.
    
    ### New Architecture: s390x
    
    We have added the s390x platform to builds. Some consumers have wanted
    this platform for many years but we did not have the time to integrate
    necessary changes. We have done this with EPEL-8, and hope to be able
    to do so for EPEL-7 if there are continued requests for it.
    
    ## What is next? (Why is it called EPEL-8.0?)
    The goal for EPEL-8.1 will be implementing modules into the
    repository, which allows builds for packages that depend on
    non-shipped devel packages. It also allows maintainers to supplement
    and replace other packages they could not under standard EPEL rules.
    
    ## Known Issues:
    1. EPEL-8.0 does not come with modules. Packages built for perl,
    python and other modules are only built against “default” modules. For
    example installing a perl library from EPEL will work with the
    perl-5.26 but not with the perl-5.24 module.
    2. RHEL-8.0 and RHEL-8.1 beta do not come with the same packages in
    all architectures. There are 720 ‘desktop’ packages which were only
    shipped for x86_64 and ppc64le. Packagers looking to deliver GNOME,
    KDE, or other platforms will need to exclude s390x and aarch64 at this
    time.
    3. The dnf in RHEL-8.1 beta does not work with the EPEL repository due
    to zchunk code. This has been opened as an upstream bug as
    https://bugzilla.redhat.com/show_bug.cgi?id=1719830
    4. Until modularity and module builds are implemented in EPEL, there
    will be many packages which can not be built for EPEL. This is mainly
    due to RHEL-8 not shipping many -devel packages and the need for us to
    rebuild those packages in a module to make those -devel available to
    build against. 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. Please list the package(s)
    which is blocked from being built because of its absence. We will
    collate these items into bugzilla tickets which will be reviewed by
    the Red Hat product groups to see if they will be added in future Code
    Ready Builder releases. Doing this will ensure that we do not have 70
    requests for foo-devel but can have one with all the packages needing
    it.
    5. /usr/bin/python does not exist in RHEL8. Developers should aim
    towards /usr/bin/python3 or /usr/bin/python2 and patch appropriately.
    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.
    6. 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.
    7. 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.
    8. While EL-8 comes with platform-python, it should NOT be used in
    Requires: unless absolutely necessary. python3 should be used instead.
    (Exceptions can be made but will be rare and need justification.)
      * Accepted exception: Use python3.6dist(coverage) instead of
    python3-coverage. This package is not shipped but is needed in %check
    code.
    10. 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 recommend strongly to only focus on python3 subpackages..
    11. RHEL-8 was built with packages which were not shipped. In general
    it is OK to branch these packages and build them in EPEL.
    12. systemd-rpm-macros is not a separate packages. If needed, used
    BuildRequires: systemd
    13. You will need to make sure you have a version of fedpkg greater
    than fedpkg-1.37-4 to work with both `epel8` and `epel8-playground`.
    Versions before that should work with just `epel8`.
    
    ## Developer requests for multiple branches
    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 package1 package2 package3 package4
    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 RHEL-8 packages missing -devel
    * libblueray-devel
    * liba52-devel
    * libXvMC-devel
    * libdvdnav-devel
    * gfbgraph-devel
    * libuv-devel
    * rest-devel
    * qgpgme-devel
    
    ## Definitions
    * 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.
    * Consumer. A person who has subscribed to EPEL for packages but is
    not a maintainer.
    * 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.
    
    
    

Now covered by Michael Larabel

  • EPEL 8.0 Is Now Ready To Offer Up More Packages To Red Hat Enterprise Linux 8 Users

    EPEL 8.0 is now ready for users of Red Hat Enterprise Linux 8 and the eventual CentOS 8 for complementing the standard repositories with extra packages for what is found in Fedora.

    The "Extra Packages for Enterprise Linux" continues providing a sub-set of Fedora's packages to RHEL/CentOS users. Just as they've done for prior RHEL series, EPEL 8.0 provides updated/additional packages for Red Hat Enterprise Linux 8.0 / CentOS 8.0 users.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

KDE Usability & Productivity: Week 85

I’m not dead yet! KDE’s new goal proposals have been announced, and the voting has started. But in the meantime, the Usability & Productivity initiative continues, and we’re onto week 85! Read more

Leftovers: Kate, Krita, UCLA Library and RcppExamples

  • Kate - Document Preview Plugin - Maintainer Wanted!

    At the moment the Document Preview plugin that e.g. allows to preview Markdown or other documents layout-ed via embedding a matching KPart is no longer maintained. If you want to step up and keep that plugin alive and kicking, now is your chance!

  • The Sprint

    Hi -)) haven’t posted for some time, because I was busy travelling and coding for the first half of the month. From Aug 5 to Aug 9, I went to the Krita Sprint in Deventer, Netherlands. According to Boud, I was the first person to arrive. My flight took a transit via Hong Kong where some flights were affected due to natural and social factors, but fortunately mine was not one of them. Upon arrival in Amsterdam I got a ticket for the Intercity to Deventer. Railway constructions made me take a transfer via Utrecht Centraal, but that was not a problem at all: the station has escalators going both up to the hall, and down to the platforms (in China you can only go to the hall by stairs or elevator (which is often crowded after you get off)). When I got out of Deventer Station, Boud immediately recognized me (how?!). It was early in the morning, and the street’s quietness was broken by the sound of me dragging my suitcase. Boud led me through Deventer’s crooked streets and alleys to his house. For the next two days people gradually arrived. I met my main mentor Dmitry (magician!) and his tiger, Sagoskatt, which I (and many others) have mistaken for a giraffe. He was even the voice actor for Sago. He had got quite a lot of insights into the code base (according to Boud, “80%”) and solved a number of bugs in Krita (but he said he introduced a lot of bugs, ha!). Also I met David Revoy (my favourite painter!), the author of Pepper and Carrot. And Tiar, our developer who started to work full-time on Krita this year; she had always been volunteering to support other Krita users and always on the IRC and Reddit. And two of other three GSoC students for the year: Blackbeard (just as his face) and Hellozee. Sh_zam could not come and lost communications due to political issues, which was really unfortunate (eh at least now he can be connected). It is feels so good to be able to see so many people in the community – they are so nice! And it is such an experience to hack in a basement church.

  • How UCLA Library preserves rare objects with open source

    The University of California, Los Angeles, (UCLA) Library houses a collection of millions of rare and unique objects, including materials dating from 3000 BCE, that could be damaged, destroyed, or otherwise threatened if they were displayed. To make these special collections widely available while keeping them secure, the UCLA Library has been modernizing its digital repository, which was established 15 years ago on now-outdated software. [...] Watch Jen's Lightning Talk to learn more about the UCLA Library's rare collections digitization project.

  • RcppExamples 0.1.9

    The RcppExamples package provides a handful of short examples detailing by concrete working examples how to set up basic R data structures in C++. It also provides a simple example for packaging with Rcpp.

Games: Smith and Winston, 7 Billion Humans Sale

Servers: Ampere Computing, SUSE and Red Hat

  • Ampere Computing Is Keeping Close Track Of The Linux Performance For Their ARM Servers

    Hardware vendor Ampere Computing with their impressive ARM servers is doing a great job on closely following their hardware's Linux performance as part of a rigorous continuous testing regiment or ensuring quality, compatibility, and stability while being fully-automated. Ampere Computing's Travis Lazar talked at this week's Linux Foundation events in San Diego over the importance of continuous regression testing for software and hardware development by talking about their internal workflow and software in place. Their internal system is the "Totally Automated Regression System" or TARS for short. TARS makes use of various open-source components including the Phoronix Test Suite and its vast collection of benchmarks for providing comprehensive test coverage plus Ampere's own "extensions" to the Phoronix Test Suite. TARS also incorporates the provisioning/configuration responsibilities as well as analysis of the data.

  • [SUSE] Learn how the Multimodal OS can benefit your organization.
  • From ProdOps to DevOps: Surviving and thriving

    For many of us in Production Operations (ProdOps), change is the enemy. If something changes, there is now an opportunity for things that were working just fine to experience problems. It is like a game of Jenga. When will the tower fall because a seemingly minor change unbalances the whole stack of pieces? ProdOps teams hate change so much, that countless frameworks have been invented to "manage" changes; in reality, these frameworks make the procedure for effecting a change so onerous that most people give up and accept the status quo. Actually, that statement is a bit unfair. These frameworks are an attempt to wrap planning and consensus around production changes, thus minimizing potential downtime caused by random or rogue changes (see Why the lone wolf mentality is a sysadmin mistake).

  • Meet Red Hat at VMworld

    As Red Hat’s Ashesh Badani said in his blog post about the reference architecture for OpenShift on VMware’s SDDC stack “… this is just the first step — Red Hat OpenShift 4 brings optimized installation capabilities to a variety of infrastructures and for this, the companies are working towards a VMware Validated Design. We are excited that VMware is working closely with Red Hat to deliver a simplified experience there in the coming months.”