[EPEL-devel] Fedora EPEL 6 updates-testing report
The following Fedora EPEL 6 Security updates need testing: Age URL 14 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-12f1eb1b1f tomcat-7.0.94-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing configsnap-0.17.1-1.el6 epson-inkjet-printer-escpr-1.6.41-1.1lsb3.2.el6 fuse3-3.6.1-2.el6 ocserv-0.12.4-1.el6 singularity-3.2.1-1.1.el6 vim-jellybeans-1.7-1.el6 Details about builds: configsnap-0.17.1-1.el6 (FEDORA-EPEL-2019-c3754a2823) Record and compare system state Update Information: Release 0.17.1 Release 0.17.0 ChangeLog: * Wed Jul 3 2019 Nick Rhodes - 0.17.1-1 - Convert relative basedir to absolute path (PR 103) * Sun Jun 16 2019 Nick Rhodes - 0.17.0-1 - Update diff function to use Popen.communicate() (PR 101) * Thu Jan 31 2019 Fedora Release Engineering - 0.16.2-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild epson-inkjet-printer-escpr-1.6.41-1.1lsb3.2.el6 (FEDORA-EPEL-2019-b5618c7054) Drivers for Epson inkjet printers Update Information: Update to 1.6.41, including more printer drivers. ChangeLog: * Wed Jul 3 2019 Susi Lehtola - 1:1.6.41-1.1lsb3.2 - Update to 1.6.41. * Thu Jan 31 2019 Fedora Release Engineering - 1:1.6.30-2.1lsb3.2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild * Tue Oct 9 2018 Susi Lehtola - 1:1.6.30-1.1lsb3.2 - Update to 1.6.30. * Thu Jul 12 2018 Fedora Release Engineering - 1:1.6.20-2.1lsb3.2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild References: [ 1 ] Bug #1569243 - The version in Fedora does not work with my printer https://bugzilla.redhat.com/show_bug.cgi?id=1569243 fuse3-3.6.1-2.el6 (FEDORA-EPEL-2019-3ae262c74f) File System in Userspace (FUSE) v3 utilities Update Information: Update to upstream 3.6.1 and newer version of pr #421 ChangeLog: * Wed Jul 3 2019 Dave Dykstra - 3.6.1-2 - Update to newer version of pr #421 - Disable building examples on el7 * Thu Jun 13 2019 Tom Callaway - 3.6.1-1 - Update to 3.6.1 References: [ 1 ] Bug #1720238 - fuse3-3.6.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=1720238 ocserv-0.12.4-1.el6 (FEDORA-EPEL-2019-6d43b6e26e) OpenConnect SSL VPN server Update Information: Update to upstream 0.12.4 release ChangeLog: * Wed Jul 3 2019 Nikos Mavrogiannopoulos - 0.12.4-1 - Update to upstream 0.12.4 release singularity-3.2.1-1.1.el6 (FEDORA-EPEL-2019-f4dc17dadf) Application and environment virtualization Update Information: Add patches for upstream PR #3456 and #3803 ChangeLog: * Wed Jul 3 2019 Dave Dykstra - 3.2.1-1.1 - Add patch for PR #3456 to make --home work with 'mount home = no' - Add patch for PR #3803 to make bind mounts from read-only filesystems work unprivileged vim-jellybeans-1.7-1.el6 (FEDORA-EPEL-2019-95a50303cf) A colorful, dark color scheme for Vim Update Information: Latest upstream ChangeLog: * Wed Jul 3 2019 Carl
[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 323 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 98 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294 cinnamon-3.6.7-5.el7 91 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-50a6a1ddfd afflib-3.7.18-2.el7 64 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80 python-gnupg-0.4.4-1.el7 62 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b bubblewrap-0.3.3-2.el7 34 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-fc63c75ab1 hostapd-2.8-1.el7 12 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-a7d80aae2a pdns-4.1.10-1.el7 5 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b94f559810 chromium-75.0.3770.100-2.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing configsnap-0.17.1-1.el7 epson-inkjet-printer-escpr-1.6.41-1.1lsb3.2.el7 fuse3-3.6.1-2.el7 ocserv-0.12.4-1.el7 python-texttable-1.6.2-1.el7 python-vpoller-0.7.3-4.el7 radare2-3.6.0-1.el7 singularity-3.2.1-1.1.el7 vim-jellybeans-1.7-1.el7 Details about builds: configsnap-0.17.1-1.el7 (FEDORA-EPEL-2019-86755d46f5) Record and compare system state Update Information: Release 0.17.1 Release 0.17.0 ChangeLog: * Wed Jul 3 2019 Nick Rhodes - 0.17.1-1 - Convert relative basedir to absolute path (PR 103) * Sun Jun 16 2019 Nick Rhodes - 0.17.0-1 - Update diff function to use Popen.communicate() (PR 101) * Thu Jan 31 2019 Fedora Release Engineering - 0.16.2-2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild epson-inkjet-printer-escpr-1.6.41-1.1lsb3.2.el7 (FEDORA-EPEL-2019-02487521f1) Drivers for Epson inkjet printers Update Information: Update to 1.6.41, including more printer drivers. ChangeLog: * Wed Jul 3 2019 Susi Lehtola - 1:1.6.41-1.1lsb3.2 - Update to 1.6.41. * Thu Jan 31 2019 Fedora Release Engineering - 1:1.6.30-2.1lsb3.2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild * Tue Oct 9 2018 Susi Lehtola - 1:1.6.30-1.1lsb3.2 - Update to 1.6.30. * Thu Jul 12 2018 Fedora Release Engineering - 1:1.6.20-2.1lsb3.2 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild References: [ 1 ] Bug #1569243 - The version in Fedora does not work with my printer https://bugzilla.redhat.com/show_bug.cgi?id=1569243 fuse3-3.6.1-2.el7 (FEDORA-EPEL-2019-3c24951b97) File System in Userspace (FUSE) v3 utilities Update Information: Update to upstream 3.6.1 and newer version of pr #421 ChangeLog: * Wed Jul 3 2019 Dave Dykstra - 3.6.1-2 - Update to newer version of pr #421 - Disable building examples on el7 * Thu Jun 13 2019 Tom Callaway - 3.6.1-1 - Update to 3.6.1 References: [ 1 ] Bug #1720238 - fuse3-3.6.1 is available https://bugzilla.redhat.com/show_bug.cgi?id=1720238 ocserv-0.12.4-1.el7 (FEDORA-EPEL-2019-73e3a8a924) OpenConnect SSL VPN server Update Information: Update to upstream 0.12.4 release ChangeLog: * Wed Jul 3 2019 Nikos Mavrogiannopoulos - 0.12.4-1 - Update to upstream 0.12.4 release python-texttable-1.6.2-1.el7 (FEDORA-EPEL-2019-77b47999fb) Python module to generate a formatted text table, using ASCII characters Update Information: * Fix auto-formatting NaN
[EPEL-devel] Re: Update on EPEL-8 Status
On 07/01/19 07:57, Stephen John Smoogen wrote: > # Update on EPEL-8 Status > > ## Why is EPEL-8 Taking So Long (tl;dr:) > > 1. Getting koji to work smoothly with modules has been hard. A multi-level > fix has had to be worked to get it working in staging. > * Needed a way to split out default modules to deal with koji merge > options. [Grobisplitter](https://github.com/puiterwijk/grobisplitter) was > written to do this > * [Koji](https://pagure.io/koji) needed further patching to deal with > src.rpms with same NVR but different targets (some python2 and python3 come > from same src.rpm but were built in different times). > * DNF reposync from RHEL-7 would delete the wrong files if you tried the > ``--newest`` (fixed.) > * DNF does not know how to reposync modules if it is not the local arch. > Code Ready Builder is not always in sync with packages in main trees. If you > need a -devel and it isn’t in CRB, then you have to wait until it is there to > build something. > 2. As a couple of fixes landed in mergerepo and koji, we are re-evaluating > how we do builds in the next stage of building. > > > ## Introduction > > In May of 2019, Red Hat released their 8.0 release of Red Hat Enterprise > Linux (RHEL). Usually, the Extra Packages for Enterprise Linux (EPEL) group > would have a beta available at that time or sooner. With RHEL-8, it has taken > a lot longer to get things rolling. > > ## Repository Changes > > EPEL packages are built inside of the Fedora Projects' build infrastructure. > This is done by downloading the packages from Red Hat's public Content > Delivery Network (CDN), and then having the Fedora artifact build system > (koji) use the release as an external build channel. Koji looks at packages > in a different way than other build commands like 'mock' do. Where mock is > meant to just build packages, koji is designed about auditing the entire > lifecycle of a package. In other words, if you want to know how a package in > Fedora 12 was built and all its children interacted over time in the > buildroots.. you can do that with enough work and the koji databases. With > mock you have a couple of log files which tell you what was pulled into a > buildroot but how those were built would require you finding their log files, > etc etc. A developer can also download those packages and look at them to see > what was in them and how they were built. > > The strength of koji is that you can have a credible chain of builds to know > where things came from. However this doesn't work too well with building > packages for EPEL where koji doesn't know where the RHEL kernel came from. > Koji uses mergerepo to look at the external packages provided, determines the > src.rpm they would come from and determines what the latest version it would > use from each. From this it creates a 'buildroot' which it will use to build > packages from. This has worked pretty well for building packages from > RHEL-5,6, and 7. The major downside has been where someone built a package > with the same src.rpm name which koji then decides is the master no matter if > a newer version shows up in RHEL. > > This all changed with modularity. Koji really only has a rudimentary idea of > rpms and repositories.. it has zero idea about modules and the rules it has > used to determine what an external package is are thrown out with modules. > > 1. Packages with different names may come with from the same src.rpm. In > RHEL-8 many python27 and python36 packages have the same parent src.rpm but > were in different build times. Koji's standard repo comparison mode will > choose one or the other. > 2. Packages may have the same names-version-releases but were built in > different module streams (say perl-5.26 and perl-5.24) Koji would then choose > a package depending on whatever had the largest src.rpm which meant it could > try to build a buildroot with perl-5.24 perl modules but perl-5.26 as the > master perl. > > If a developer uses mock to build a package with default repositories, mock > calls dnf which knows about modules and does the right thing. In the case > where you want it to do the 'wrong' thing you can also over-ride mock to do > that. With koji, further tools are needed to make this work. If you are > building a new module, then the Modular Build System (MBS) sits on top of > koji and tells koji what to do. It will look at the module yaml file and turn > on/off various modules so that it can build in what is needed. To build > non-modular packages, other fixes are needed. One of these is called > Ursa-Major which was a set of scripts to pull in needed data from a third > database and pull things in as needed. However, this was not adopted in > Fedora for general use so the EPEL group looked for something different. > > The temporary solution written by Patrick Uiterwijk is called grobisplitter > (https://github.com/puiterwijk/grobisplitter) which relies on the fact
[EPEL-devel] Updating of petsc/petsc4py/sundials/bionetgen on EPEL 7
Hi all. Following packages may be upgraded on EPEL 7: - Updates to PETSc-3.10.4 (1) (against current PETSc-3.9.3 (2)) - Update to petsc4py-3.10.1 (requires PETSc-3.10) - Update to sundials-4.1.0 (against current sundials-2 (3)) - Update to bionetgen-2.5.0 (it's now bundles/provides/requires a cvode2 module, so is independent by Sundials-3+) Please, test them: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1a18c3e4c6 Regarding all third party Copr projects (4), if these updates will be accepted, they will need to create their own sundials2 src-rpms or adapt current SRPMs to the newer Sundials-4*, i guess. (1) https://www.mcs.anl.gov/petsc/documentation/changes/310.html (2) https://www.mcs.anl.gov/petsc/documentation/changes/39.html (3) https://computation.llnl.gov/projects/sundials/release-history (4) https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-1a18c3e4c6#comment-968109 Regards. -- --- Antonio Trande Fedora Project mailto 'sagitter at fedoraproject dot org' GPG key: 0x6e0331dd1699e4d7 GPG key server: https://keys.fedoraproject.org/ signature.asc Description: OpenPGP digital signature ___ epel-devel mailing list -- epel-devel@lists.fedoraproject.org To unsubscribe send an email to epel-devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org
