[EPEL-devel] Fedora EPEL 8 updates-testing report
The following builds have been pushed to Fedora EPEL 8 updates-testing aom-1.0.0-8.20190810git9666276.el8 drbdlinks-1.28-7.el8 libmodplug-0.8.9.0-9.el8 pdns-4.1.13-1.el8 python-bsddb3-6.2.6-5.el8 python-pymilter-1.0.4-3.el8 squidGuard-1.4-35.el8 tcpreplay-4.3.2-2.el8 ufw-0.35-14.el8 xorgxrdp-0.2.10-4.el8 xrdp-0.9.10-3.el8 zvbi-0.2.35-9.el8 Details about builds: aom-1.0.0-8.20190810git9666276.el8 (FEDORA-EPEL-2019-a27847dadb) Royalty-free next-generation video format Update Information: Update to commit 9666276accea505cd14cbcb9e3f7ff5033da9172 References: [ 1 ] Bug #1558224 - Review Request: aom - Royalty-free next-generation video format https://bugzilla.redhat.com/show_bug.cgi?id=1558224 drbdlinks-1.28-7.el8 (FEDORA-EPEL-2019-7569d7857c) Program for managing links into a DRBD shared partition Update Information: The drbdlinks program manages links into a DRBD partition which is shared among several machines. A simple configuration file, `/etc/drbdlinks.conf`, specifies the links. This can be used to manage e.g. links for `/etc/httpd`, `/var/lib/pgsql` and other system directories that need to appear as if they are local to the system when running applications after the drbd shared partition has been mounted. When running drbdlinks with `start` as the mode, drbdlinks will rename the existing files/directories and then make symbolic links into the DRBD partition, `stop` does the reverse. By default, rename appends `.drbdlinks` to the name, but this can be overridden. An init script is included which runs `stop` before heartbeat starts, and after heartbeat stops. This is done to try to ensure that when the shared partition isn't mounted, the links are in their normal state. References: [ 1 ] Bug #1737964 - drbdlinks depends on Python 2 https://bugzilla.redhat.com/show_bug.cgi?id=1737964 libmodplug-0.8.9.0-9.el8 (FEDORA-EPEL-2019-ebaf5c08ad) Modplug mod music file format library Update Information: - New package References: [ 1 ] Bug #1739156 - libmodplug for EPEL8 https://bugzilla.redhat.com/show_bug.cgi?id=1739156 pdns-4.1.13-1.el8 (FEDORA-EPEL-2019-89a0da3a65) A modern, advanced and high performance authoritative-only nameserver Update Information: - Update to 4.1.13 The PowerDNS Nameserver is a modern, advanced and high performance authoritative-only nameserver. It is written from scratch and conforms to all relevant DNS standards documents. Furthermore, PowerDNS interfaces with almost any database. python-bsddb3-6.2.6-5.el8 (FEDORA-EPEL-2019-b8a583cb1e) Python 3 bindings for Berkeley DB Update Information: Rebuild for EPEL 8. References: [ 1 ] Bug #1738715 - Please build python-bsddb3 for EPEL 8 https://bugzilla.redhat.com/show_bug.cgi?id=1738715 python-pymilter-1.0.4-3.el8 (FEDORA-EPEL-2019-2b476a55b9) Python interface to sendmail milter API Update Information: Untested as I haven't figured out how to apply developer subscription to my rhel8 vm. References: [ 1 ] Bug #1738718 - Please build python-pymilter for EPEL 8 https://bugzilla.redhat.com/show_bug.cgi?id=1738718
[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem
On Sat, 10 Aug 2019 at 17:12, Miro Hrončok wrote: > On 10. 08. 19 21:23, Miro Hrončok wrote: > > While I really tried to do my best, it seems that I broke CentOS by > retiring > > python36. Should it be unretired? Or is it reasonable to say: Please > wait for > > CentOS 7.7? > > > > https://bugzilla.redhat.com/show_bug.cgi?id=1739804 > > If any EPEL expert thinks the package should be unretired for now, please > do so. > > Miro, please unretire the packages for the 2-3 weeks til CentOS 7.7 is out in the CR repo. My apologies for not thinking of this when you were mentioning things yesterday. I do not have the rights to unretire things so will need to get in touch with Mohan/Kevin/Mizdebsk on what to do. > > Also after retiring python-rpm-macros, Koji doesn't seem to see the RHEL > one. Is > > there any action to take? > > > > > https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/UKHD6IXORQ6RNNL4JZ67PGQHOMIBVUZZ/ > > > > > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > 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 > -- Stephen J Smoogen. ___ 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
[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem
Robert-André Mauchin wrote: > How long would that wait be? > RHEL7.7 is only 4 days old. Everyone running CentOS should be planning their patching cycles around the lull between a brand new RHEL Update and the CentOS build/catch-up. - bjs ___ 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
[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem
On Saturday, 10 August 2019 21:23:55 CEST Miro Hrončok wrote: > While I really tried to do my best, it seems that I broke CentOS by retiring > python36. Should it be unretired? Or is it reasonable to say: Please wait > for CentOS 7.7? > How long would that wait be? ___ 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
[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem
On 10. 08. 19 21:23, Miro Hrončok wrote: While I really tried to do my best, it seems that I broke CentOS by retiring python36. Should it be unretired? Or is it reasonable to say: Please wait for CentOS 7.7? https://bugzilla.redhat.com/show_bug.cgi?id=1739804 If any EPEL expert thinks the package should be unretired for now, please do so. Also after retiring python-rpm-macros, Koji doesn't seem to see the RHEL one. Is there any action to take? https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/UKHD6IXORQ6RNNL4JZ67PGQHOMIBVUZZ/ -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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
[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem
Stephen John Smoogen wrote: > This was the purpose of the various branching proposals. The main issue > there are > not enough time/manpower resources to make any of the proposals work as it > needs > build system changes, a full time release manager and packagers who want to > deal with it. > In the end though this is a volunteer project done on the side by various > people in the > Fedora community. If we were to move this elsewhere, it would still be a > volunteer activity. > I wish I had a better answer but after seeing us break the world every > RHEL-X.Y release.. I don't. > Indeed, it's a thankless job. Sincerely, keep up the good work, and that goes for all maintainers too. I've always advised those running 'downstream' versions wait to update until they are on the same, new 'Update' after any new RHEL release. It's a good rule to follow -- e.g., RHEL 7.7 just came out. - "Still lurking" bjs P.S. For those that don't know, starting a good 7 years ago I brought up the increasing 'breakage' with RHEL as Fedora EPEL build various packages for CentOS because CentOS rebuilding various RHEL add-ons. Simply put, at a half-dozen major Red Hat accounts, I had to warn EPEL would now conflict in various ways outside of the very RHEL core, so RHEL systems couldn't be subscribed to it, and each EPEL package needed to be vetted into an internal channel/repo (e.g., Satellite) before even considering deployment. I also worked with both Red Hat GLS as well as Partners over the next 18 months to tell them to yank all sections regarding EPEL from Training, Enablement and other documentation, as only core RHEL compatibility was the goal, not all of RHEL. So at that time I suggested the idea of forking into Emerging Technologies for Enterprise Linux (ETEL) from EPEL. That way, people who wanted newer Fedora stuff or, in the case of CentOS not rebuilding various Enterprise add-ons available for RHEL, or even newer versions of packages in RHEL add-ons, would have a separate repo from EPEL that was never supposed to conflict. As Stephen, Kevin and others others pointed out for that to happen, increases of resources and volunteer hours would have to happen. And that's just the reality. Not everyone is going to be made happy, given the constraints. So we should all appreciate what we have. I'm just glad EPEL still focuses on at least core RHEL. ___ 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
[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem
On Sat, 10 Aug 2019 at 16:18, Andrew C Aitchison wrote: > On Sat, 10 Aug 2019, Richard Grainger wrote: > > >> On 10 Aug 2019, at 20:23, Miro HronÄ ok wrote: > >> > >> While I really tried to do my best, it seems that I broke CentOS by > >> retiring python36. Should it be unretired? Or is it reasonable to > >> say: Please wait for CentOS 7.7? > > > > This is why I believe we need a “CentOS-EPEL†repo that mirrors EPEL > > generally, but that is frozen in the period between a RHEL and > > CentOS release. > > The same could be said for a Scientific-Linux-EPEL. > Would it be clearer to have an EPEL7.6 and an EPEL7.7 ? > This was the purpose of the various branching proposals. The main issue there are not enough time/manpower resources to make any of the proposals work as it needs build system changes, a full time release manager and packagers who want to deal with it. In the end though this is a volunteer project done on the side by various people in the Fedora community. If we were to move this elsewhere, it would still be a volunteer activity. I wish I had a better answer but after seeing us break the world every RHEL-X.Y release.. I don't. -- Stephen J Smoogen. ___ 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
[EPEL-devel] Re: Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem
> On 10 Aug 2019, at 20:23, Miro Hrončok wrote: > > While I really tried to do my best, it seems that I broke CentOS by retiring > python36. Should it be unretired? Or is it reasonable to say: Please wait for > CentOS 7.7? This is why I believe we need a “CentOS-EPEL” repo that mirrors EPEL generally, but that is frozen in the period between a RHEL and CentOS release. ___ 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
[EPEL-devel] Python 3.6: RHEL 7.7 vs. CentOS 7.6 EPEL7 retirement problem
While I really tried to do my best, it seems that I broke CentOS by retiring python36. Should it be unretired? Or is it reasonable to say: Please wait for CentOS 7.7? https://bugzilla.redhat.com/show_bug.cgi?id=1739804 Also after retiring python-rpm-macros, Koji doesn't seem to see the RHEL one. Is there any action to take? https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/UKHD6IXORQ6RNNL4JZ67PGQHOMIBVUZZ/ -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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
[EPEL-devel] Re: Missing python-rpm-macros>3.30 on EPEL7 ppc64le
The package are correctly retired, but the ones from RHEL are not available, which breaks building for EPEL7: https://kojipkgs.fedoraproject.org//work/tasks/9826/36909826/mock_output.log Error: Package: epel-rpm-macros-7-20.noarch (build) Requires: python-srpm-macros Error: Package: epel-rpm-macros-7-20.noarch (build) Requires: python2-rpm-macros You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest Error: Package: epel-rpm-macros-7-20.noarch (build) Requires: python-rpm-macros Does something need to be one Koji side? ___ 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
[EPEL-devel] Re: Missing python-rpm-macros>3.30 on EPEL7 ppc64le
On 10. 08. 19 11:53, Antonio Trande wrote: When will it happen? I did that right after that e-mail: https://src.fedoraproject.org/rpms/python-rpm-macros/c/b6f2fa0c7616565c964e5c72ecfddb6e712c2266?branch=epel7 If ti doesn't work, maybe some Koji admins need to do stuff? Or it just takes a while? -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ 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
[EPEL-devel] Re: Missing python-rpm-macros>3.30 on EPEL7 ppc64le
When will it happen? On 09/08/19 15:39, Miro Hrončok wrote: > > Will do. I was waiting for the release to happen. > -- --- Antonio Trande Fedora Project mailto 'sagitter at fedoraproject dot org' GPG key: 0x6e0331dd1699e4d7 GPG key server: https://keys.openpgp.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
