[EPEL-devel] Fedora EPEL 6 updates-testing report

2019-05-02 Thread updates
The following Fedora EPEL 6 Security updates need testing:
 Age  URL
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bd4638e5a3   
libmediainfo-18.12-3.el6
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-009f5f140b   
php-horde-horde-5.2.21-1.el6
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b9ea566899   
php-horde-turba-4.2.24-1.el6
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-e406623fec   
bird-1.6.6-1.el6
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dc3342b950   
drupal7-7.66-1.el6


The following builds have been pushed to Fedora EPEL 6 updates-testing

csdiff-1.6.1-1.el6
holland-1.1.15-2.el6
python-mitogen-0.2.6-2.el6

Details about builds:



 csdiff-1.6.1-1.el6 (FEDORA-EPEL-2019-a122edd205)
 Non-interactive tools for processing code scan results in plain-text

Update Information:

- update to latest upstream release - make pycsdiff build with Python 3.8
(#1705427)

ChangeLog:

* Thu May  2 2019 Kamil Dudka  1.6.1-1
- make pycsdiff build with Python 3.8 (#1705427)
- update to latest upstream release

References:

  [ 1 ] Bug #1705427 - csdiff FTBFS with Python 3.8
https://bugzilla.redhat.com/show_bug.cgi?id=1705427




 holland-1.1.15-2.el6 (FEDORA-EPEL-2019-69c733d224)
 Pluggable Backup Framework

Update Information:

upstream 1.1.15, add dependencies for holland-mysql to relevant subpackages

ChangeLog:

* Thu May  2 2019 Pete Travis  - 1.1.15-2
- add dependencies for holland-mysql to relevant subpackages
* Thu May  2 2019 Pete Travis  - 1.1.15-1
- Latest upstream

References:

  [ 1 ] Bug #1701580 - holland-1.1.15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1701580
  [ 2 ] Bug #1703567 - Subpackage missing dependencies
https://bugzilla.redhat.com/show_bug.cgi?id=1703567




 python-mitogen-0.2.6-2.el6 (FEDORA-EPEL-2019-d4de14e7d9)
 Distributed self-replicating programs in Python

Update Information:

- Improve patch0    Initial package

References:

  [ 1 ] Bug #1705264 - Review Request: python-mitogen - Distributed 
self-replicating programs in Python
https://bugzilla.redhat.com/show_bug.cgi?id=1705264


___
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org


[EPEL-devel] Fedora EPEL 7 updates-testing report

2019-05-02 Thread updates
The following Fedora EPEL 7 Security updates need testing:
 Age  URL
 261  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-3c9292b62d   
condor-8.6.11-1.el7
  69  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f8311ec8a2   
tor-0.3.5.8-1.el7
  37  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d2c1368294   
cinnamon-3.6.7-5.el7
  29  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-50a6a1ddfd   
afflib-3.7.18-2.el7
  10  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-7fc4459823   
libmediainfo-18.12-3.el7
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-f05ef50515   
php-horde-horde-5.2.21-1.el7
   9  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-add436bec5   
php-horde-turba-4.2.24-1.el7
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-d28d3135da   
python36-3.6.8-1.el7
   3  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-c499781e80   
python-gnupg-0.4.4-1.el7
   2  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-de28ce6966   
drupal7-7.66-1.el7
   1  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-bc0182548b   
bubblewrap-0.3.3-2.el7


The following builds have been pushed to Fedora EPEL 7 updates-testing

csdiff-1.6.1-1.el7
engauge-digitizer-11.2-1.el7
fuse3-3.4.2-6.el7
holland-1.1.15-2.el7
openkim-models-2019.03.31-2.el7
python-mitogen-0.2.6-2.el7

Details about builds:



 csdiff-1.6.1-1.el7 (FEDORA-EPEL-2019-5533a53842)
 Non-interactive tools for processing code scan results in plain-text

Update Information:

- update to latest upstream release - make pycsdiff build with Python 3.8
(#1705427)

ChangeLog:

* Thu May  2 2019 Kamil Dudka  1.6.1-1
- make pycsdiff build with Python 3.8 (#1705427)
- update to latest upstream release

References:

  [ 1 ] Bug #1705427 - csdiff FTBFS with Python 3.8
https://bugzilla.redhat.com/show_bug.cgi?id=1705427




 engauge-digitizer-11.2-1.el7 (FEDORA-EPEL-2019-febbbc0d7a)
 Convert graphs or map files into numbers

Update Information:

- Release 11.2

ChangeLog:

* Thu May  2 2019 Antonio Trande  - 1:11.2-1
- Release 11.2




 fuse3-3.4.2-6.el7 (FEDORA-EPEL-2019-0f408e00c0)
 File System in Userspace (FUSE) v3 utilities

Update Information:

Add fuse3 to epel7

References:

  [ 1 ] Bug #1696454 - Please include fuse3 and fuse3-libs in EPEL
https://bugzilla.redhat.com/show_bug.cgi?id=1696454




 holland-1.1.15-2.el7 (FEDORA-EPEL-2019-d616a6e03a)
 Pluggable Backup Framework

Update Information:

upstream 1.1.15, add dependencies for holland-mysql to relevant subpackages

ChangeLog:

* Thu May  2 2019 Pete Travis  - 1.1.15-2
- add dependencies for holland-mysql to relevant subpackages
* Thu May  2 2019 Pete Travis  - 1.1.15-1
- Latest upstream

References:

  [ 1 ] Bug #1703567 - Subpackage missing dependencies
https://bugzilla.redhat.com/show_bug.cgi?id=1703567
  [ 2 ] Bug #1701580 - holland-1.1.15 is available
https://bugzilla.redhat.com/show_bug.cgi?id=1701580




 openkim-models-2019.03.31-2.el7 (FEDORA-EPEL-2019-f1b06ed568)
 Open Knowledgebase of Interatomic Models

Update Information:

Initial import

References:

  [ 1 ] Bug #1703235 - Review Request: openkim-models - Open Knowledgebase of 
Interatomic Models

[EPEL-devel] Re: What happened to the 'python34-pycurl' and 'python34-mysql' packages?

2019-05-02 Thread Fred Gleason
On Thu, 2019-05-02 at 11:42 -0700, Kevin Fenzi wrote:
> Well, you can specify directly /usr/bin/python3.4 if you need
> specifially python3.4.

Yes, that is what I've started doing. Effectively, we've pinned it to
3.4.


>  If you only specified 'python3' in theory either
> one should work for that.

Unfortunately, that breaks if the local user has created modules of his
own --i.e. not under management by rpm(8)-- and placed them in
'%{_libdir}/python3.4/'. That's actually a pretty common scenario in
our use case!

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|
___
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://getfedora.org/code-of-conduct.html
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: What happened to the 'python34-pycurl' and 'python34-mysql' packages?

2019-05-02 Thread Kevin Fenzi
On 5/2/19 11:28 AM, Fred Gleason wrote:
> On Thu, 2019-05-02 at 10:26 -0700, Kevin Fenzi wrote:
>> Sorry this is all so confusing. ;(
> 
> Life can be complicated at times!  :)
> 
> I admit that the way this Python 3.4 => 3.6 update worked suprised me.
> I have binary packages that depend on several python34-* packages. The
> update broke those in a couple of ways; not only by the disappearance
> of the pycurl and mysql pieces, but by the fact that '/usr/bin/python3'
> got changed to point to '/usr/bin/python3.6' rather than
> '/usr/bin/python3.4'.
> 
> What is best practice for specifying Python dependencies so that they
> will survive this sort of thing?

Well, you can specify directly /usr/bin/python3.4 if you need
specifially python3.4. If you only specified 'python3' in theory either
one should work for that.

kevin




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://getfedora.org/code-of-conduct.html
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: What happened to the 'python34-pycurl' and 'python34-mysql' packages?

2019-05-02 Thread Fred Gleason
On Thu, 2019-05-02 at 10:26 -0700, Kevin Fenzi wrote:
> Sorry this is all so confusing. ;(

Life can be complicated at times!  :)

I admit that the way this Python 3.4 => 3.6 update worked suprised me.
I have binary packages that depend on several python34-* packages. The
update broke those in a couple of ways; not only by the disappearance
of the pycurl and mysql pieces, but by the fact that '/usr/bin/python3'
got changed to point to '/usr/bin/python3.6' rather than
'/usr/bin/python3.4'.

What is best practice for specifying Python dependencies so that they
will survive this sort of thing?

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|
___
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://getfedora.org/code-of-conduct.html
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: What happened to the 'python34-pycurl' and 'python34-mysql' packages?

2019-05-02 Thread Fred Gleason
On Thu, 2019-05-02 at 19:23 +0200, Miro Hrončok wrote:

> File RFE bugzillas against python3-mysql:

Done.

https://bugzilla.redhat.com/show_bug.cgi?id=1705679


> Or/and python3-pycurl:

https://bugzilla.redhat.com/show_bug.cgi?id=1705680

Thanks.

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|
___
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://getfedora.org/code-of-conduct.html
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: What happened to the 'python34-pycurl' and 'python34-mysql' packages?

2019-05-02 Thread Todd Zullinger
Hi,

Fred Gleason wrote:
> On Wed, 2019-05-01 at 16:17 -0700, Kevin Fenzi wrote:
>> Can you please refile that as two bugs? On python3-pycurl and
>> python3-mysql?
>> 
>> The python34 component is only for python34 itself, you will need to
>> get
>> those other two packages to fix things.
> 
> I did attempt this initially, but the 'Component' field refuses to
> accept 'python34-mysql' or 'python34-pycurl' as a valid value. What
> should the proper value there be?

The source packages for the python3X-* packages are
generally python3-* and those are what are used in the
bugzilla component field.

So these should be under python3-mysql and python3-pycurl,
respectively (which looks like what Kevin suggested :) ).

-- 
Todd


signature.asc
Description: PGP 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://getfedora.org/code-of-conduct.html
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: What happened to the 'python34-pycurl' and 'python34-mysql' packages?

2019-05-02 Thread Kevin Fenzi
On 5/2/19 10:10 AM, Fred Gleason wrote:
> On Wed, 2019-05-01 at 16:17 -0700, Kevin Fenzi wrote:
>> Can you please refile that as two bugs? On python3-pycurl and
>> python3-mysql?
>>
>> The python34 component is only for python34 itself, you will need to
>> get
>> those other two packages to fix things.
> 
> I did attempt this initially, but the 'Component' field refuses to
> accept 'python34-mysql' or 'python34-pycurl' as a valid value. What
> should the proper value there be?

python3-mysql and python3-pycurl

Those source packages make (currently) the python36-mysql and
python36-pycurl binary packages.

Sorry this is all so confusing. ;(

kevin



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://getfedora.org/code-of-conduct.html
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: What happened to the 'python34-pycurl' and 'python34-mysql' packages?

2019-05-02 Thread Miro Hrončok

On 02. 05. 19 19:10, Fred Gleason wrote:

On Wed, 2019-05-01 at 16:17 -0700, Kevin Fenzi wrote:

Can you please refile that as two bugs? On python3-pycurl and
python3-mysql?

The python34 component is only for python34 itself, you will need to
get
those other two packages to fix things.


I did attempt this initially, but the 'Component' field refuses to
accept 'python34-mysql' or 'python34-pycurl' as a valid value. What
should the proper value there be?


From my previous e-mail:

File RFE bugzillas against python3-mysql:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL=epel7=python3-mysql

Or/and python3-pycurl:

https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora%20EPEL=epel7=python3-pycurl

--
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://getfedora.org/code-of-conduct.html
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: What happened to the 'python34-pycurl' and 'python34-mysql' packages?

2019-05-02 Thread Fred Gleason
On Wed, 2019-05-01 at 16:17 -0700, Kevin Fenzi wrote:
> Can you please refile that as two bugs? On python3-pycurl and
> python3-mysql?
> 
> The python34 component is only for python34 itself, you will need to
> get
> those other two packages to fix things.

I did attempt this initially, but the 'Component' field refuses to
accept 'python34-mysql' or 'python34-pycurl' as a valid value. What
should the proper value there be?

Cheers!


|-|
| Frederick F. Gleason, Jr. | Chief Developer |
|   | Paravel Systems |
|-|
| A room without books is like a body without a soul. |
| |
| -- Cicero   |
|-|
___
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://getfedora.org/code-of-conduct.html
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: EPEL7: Adapting %python_provide to provide python3- for python36-

2019-05-02 Thread Miro Hrončok

On 30. 04. 19 10:50, Miro Hrončok wrote:

On 25. 04. 19 16:43, Miro Hrončok wrote:

On 24. 04. 19 12:23, Miro Hrončok wrote:

Hey,

since the plan is to have some python3-... packages in RHEL proper, should we 
adapt the %python_provide macro to provide python3-... when it gets 
python36-...?


%{python_provide python36-foo} currently does nothing.
I propose to change it to do: Provides: python3-foo = %{version}-%{release}.

Note: %{python_provide python2-foo} currently adds obsoletes, let's not add 
them for the python36 case (there is nothing to obsolete here, quite the 
opossite - python3-foo from RHEL would in theory obsolete python36-foo from 
EPEL).


Arguably, this discussion should have happened before we did the mass rebuild 
for 3.4 -> 3.6 transition, however I don't consider such provides essential. 
The idea is to change the macro, but don't mass rebuild - instead start 
providing the provides gradually.


Note that not all EPEL7 Python 3 packages use this macro, but many do.


A PR is here:

https://src.fedoraproject.org/rpms/python-rpm-macros/pull-request/18

I'd appreciate feedback from EPEL packagers.


Update: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-dad4eed6b7
Override: https://bodhi.fedoraproject.org/overrides/python-rpm-macros-3-24.el7


Note that it currently only works for Python 3 only SRPMS as python-devel from 
RHEL7 overrides the macro with its original version. We plan to change the macro 
on RHEL7 side as well, but (business as usual) we cannot do it right away.


--
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://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org