[EPEL-devel] Fedora EPEL 7 updates-testing report
The following Fedora EPEL 7 Security updates need testing: Age URL 345 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d condor-8.6.11-1.el7 121 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294 cinnamon-3.6.7-5.el7 87 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80 python-gnupg-0.4.4-1.el7 84 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b bubblewrap-0.3.3-2.el7 56 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-fc63c75ab1 hostapd-2.8-1.el7 21 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-12067fc897 dosbox-0.74.3-2.el7 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-487a6fb279 knot-2.8.2-1.el7 knot-resolver-4.1.0-1.el7 13 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-aabd063c30 squirrelmail-1.4.23-1.el7.20190710 9 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-931a6c5c69 chromium-75.0.3770.100-3.el7 2 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ef655ec55e proftpd-1.3.5e-5.el7 The following builds have been pushed to Fedora EPEL 7 updates-testing holland-1.1.18-1.el7 lua-dbi-0.7.2-1.el7 percolator-3.03-1.el7 Details about builds: holland-1.1.18-1.el7 (FEDORA-EPEL-2019-cd5d60442b) Pluggable Backup Framework Update Information: Latest upstream. ChangeLog: * Thu Jul 25 2019 Sam P - 1.1.18-1 - Latest upstream * Tue Jun 4 2019 Carl George - 1.1.16-1 - Latest upstream References: [ 1 ] Bug #1728363 - holland-1.1.17 is available https://bugzilla.redhat.com/show_bug.cgi?id=1728363 lua-dbi-0.7.2-1.el7 (FEDORA-EPEL-2019-b77a666f2c) Database interface library for Lua Update Information: LuaDBI 0.7.2 * DB2: Fix compilation failure in DB2 driver * Postgres: Fix Postgres driver memory leak * MySQL: Remove usage of deprecated APIs * Oracle: Add support for UTF-8, server ping, and RAC/TAF for clustering/failover * SQLite3: Add support for connection flags LuaDBI 0.7.1 * Multiple bugfixes and improvements (including significant performance enhancements) to the Oracle backend * Fix a crash in the Postgres backend LuaDBI 0.6 ==* Now supports Lua 5.1 through 5.3. * Basic unit tests, quite a few bugs fixed. * Addition of `last_id()` on connection objects, for MySQL and Sqlite3 drivers ChangeLog: * Thu Jul 25 2019 Robert Scheck 0.7.2-1 - Upgrade to 0.7.2 * Thu Jul 25 2019 Fedora Release Engineering - 0.5-22 - Rebuilt for https://fedoraproject.org/wiki/Fedora_31_Mass_Rebuild * Fri Feb 1 2019 Fedora Release Engineering - 0.5-21 - Rebuilt for https://fedoraproject.org/wiki/Fedora_30_Mass_Rebuild * Fri Jul 13 2018 Fedora Release Engineering - 0.5-20 - Rebuilt for https://fedoraproject.org/wiki/Fedora_29_Mass_Rebuild * Thu Feb 8 2018 Fedora Release Engineering - 0.5-19 - Rebuilt for https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild * Thu Sep 21 2017 Robert Scheck 0.5-18 - Build against mariadb-connector-c-devel rather mysql-devel for Fedora >= 28 (#1493634, thanks to Michal Schorm) * Thu Aug 3 2017 Fedora Release Engineering - 0.5-17 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Binutils_Mass_Rebuild * Wed Jul 26 2017 Fedora Release Engineering - 0.5-16 - Rebuilt for https://fedoraproject.org/wiki/Fedora_27_Mass_Rebuild * Fri Feb 10 2017 Fedora Release Engineering - 0.5-15 - Rebuilt for https://fedoraproject.org/wiki/Fedora_26_Mass_Rebuild * Thu Feb 4 2016 Fedora Release Engineering - 0.5-14 - Rebuilt for https://fedoraproject.org/wiki/Fedora_24_Mass_Rebuild * Sun Jun 21 2015 Robert Scheck 0.5-13 - Really build -compat subpackage against compat-lua (#1232688) * Wed Jun 17 2015 Fedora Release Engineering - 0.5-12 - Rebuilt for https://fedoraproject.org/wiki/Fedora_23_Mass_Rebuild percolator-3.03-1.el7 (FEDORA-EPEL-2019-160e89fe9a) Software for postprocessing of shotgun proteomics data Update Information: - Release 3.03 ChangeLog: * Thu Jul
[EPEL-devel] Re: Python 3 packages to be removed form EPEL 7 (provided by RHEL 7)
On 25. 07. 19 14:51, Stephen John Smoogen wrote:
Yes your assumption is correct. Koji uses src.rpm names to determine what it
pulls into a buildroot. That means that the python34 items need to have
non-conflicting names with the python3 ones shipped by upstream.. or we will
just start building with python34 or worse.
I've already prepared python34-setuptools:
https://src.fedoraproject.org/rpms/python3-setuptools/pull-request/4
https://bugzilla.redhat.com/show_bug.cgi?id=1733190
And python2-wheel:
https://src.fedoraproject.org/rpms/python-wheel/pull-request/10
https://bugzilla.redhat.com/show_bug.cgi?id=1733193
I'm waiting for the name suggestion for python{2,34}-pip.
> Would it make sense to just retire python34 completely from EPEL at the 7.7
> release date?
Python 3.4 is upstream unsupported, so getting rid of it sooner than later is
probably a good idea. However, I suggest to keep it around until EL6 is EOL.
--
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 packages to be removed form EPEL 7 (provided by RHEL 7)
On Tue, Jul 16, 2019, 3:48 PM Miro Hrončok wrote: > Hey, > > when RHEL 7.7 will be released, the following new components/packages will > be > provided (assuming from 7.7 beta): > > python3 - the Python 3.6 package > > > This new RHEL7 component builds several subpackages, all obsoleting the > subpackages of epel7 python36 package. > We will simply retire python36 from epel7. > > python-rpm-macros > = > > This new RHEL7 component is a drop-in replacement of python-rpm-macros > from > epel7, we will simply retire the package. python-epel-rpm-macros already > provide > the necessary macros for python34 in epel7. > > python3-setuptools > == > > This new RHEL7 component produces the python3-setuptools package that > obsoletes > the python36-setuptools package (built from the python3-setuptools epel7 > component). > > We cannot simply retire python3-setuptools from epel7, as it also builds > python34-setuptools in epel7 and there is no replacement for that in RHEL7. > > Easiest thing would be to stop building python36-setuptools and only keep > python34-setuptools in epel7, however IIRC we cannot have the same > component > name as in RHEL. If that is indeed the case, python3-setuptools needs to > be > retired and a new python34-setuptools component needs to be created in > epel7. Is > my assumption correct? > > python-pip > == > > This new RHEL7 component produces the python3-pip package that obsoletes > the > python36-pip package (built from the python-pip epel7 component). > > The python-pip epel7 component also produces python34-pip and python2-pip > (neither available in RHEL 7.7). > > If my previous assumption about components with RHEL names is correct, we > need 1 > or 2 new components for python34-pip and python2-pip - either we have each > in a > separate component or we create a new component that builds both (called > python-pip-epel maybe?). > > python-wheel > > > This new RHEL7 component produces the python3-wheel package. > > The python-wheel epel7 component produced python-wheel package (Python 2). > > The epel7 package was adapted to produce python2-wheel and python36-wheel, > however there was no successful build of this in epel7. > > If my previous assumption about components with RHEL names is correct, > we need to add a new python2-wheel component to epel7. > > > > Are my assumptions correct? > > If we indeed need new packages/components, I can help to create them, but > I do > not intent to maintain them. Any takers? > > -- > 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 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 packages to be removed form EPEL 7 (provided by RHEL 7)
On Thu, 25 Jul 2019 at 08:46, Stephen John Smoogen wrote: > > > On Thu, 25 Jul 2019 at 08:21, Miro Hrončok wrote: > >> On 17. 07. 19 0:00, Miro Hrončok wrote: >> > ...we need 1 or 2 new components for python34-pip and python2-pip - >> either >> > we have each in a separate component or we create a new component that >> > builds both (called python-pip-epel maybe?). >> >> What is the advice here? If I want it to be just one package, what shall >> be its >> name? >> >> > > Sorry, I completely missed that there were points you needed answers on. > Are there any others in the proposal we need to focus on? > > > And there are clearly multiple based around this one: however IIRC we cannot have the same component name as in RHEL. If that is indeed the case, python3-setuptools needs to be retired and a new python34-setuptools component needs to be created in epel7. Is my assumption correct? Yes your assumption is correct. Koji uses src.rpm names to determine what it pulls into a buildroot. That means that the python34 items need to have non-conflicting names with the python3 ones shipped by upstream.. or we will just start building with python34 or worse. Would it make sense to just retire python34 completely from EPEL at the 7.7 release date? > > > -- > Stephen J Smoogen. > > -- 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 packages to be removed form EPEL 7 (provided by RHEL 7)
On Thu, 25 Jul 2019 at 08:21, Miro Hrončok wrote: > On 17. 07. 19 0:00, Miro Hrončok wrote: > > ...we need 1 or 2 new components for python34-pip and python2-pip - > either > > we have each in a separate component or we create a new component that > > builds both (called python-pip-epel maybe?). > > What is the advice here? If I want it to be just one package, what shall > be its > name? > > Sorry, I completely missed that there were points you needed answers on. Are there any others in the proposal we need to focus on? > -- > 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 packages to be removed form EPEL 7 (provided by RHEL 7)
On 17. 07. 19 0:00, Miro Hrončok wrote: ...we need 1 or 2 new components for python34-pip and python2-pip - either we have each in a separate component or we create a new component that builds both (called python-pip-epel maybe?). What is the advice here? If I want it to be just one package, what shall be its name? -- 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
