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

2019-03-28 Thread updates 
The following Fedora EPEL 6 Security updates need testing:
 Age  URL
 104  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-b7556983e8   
tomcat-7.0.92-1.el6
  28  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-06b243cced   
guacamole-server-1.0.0-1.el6
   8  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-b4ada0648b   
putty-0.71-1.el6
   7  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-62f9745b71   
drupal7-7.65-1.el6
   5  https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-13e2a65b5e   
wordpress-5.1.1-4.el6


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

mbedtls-2.7.10-1.el6

Details about builds:



 mbedtls-2.7.10-1.el6 (FEDORA-EPEL-2019-8858606f5d)
 Light-weight cryptographic and SSL/TLS library

Update Information:

- Update to 2.7.10  Release notes: https://tls.mbed.org/tech-
updates/releases/mbedtls-2.16.1-and-2.7.10-released

ChangeLog:

* Thu Mar 28 2019 Morten Stevens  - 2.7.10-1
- Update to 2.7.10


___
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: EPEL-ANNOUNCE EPEL: Python34 moving to Python36

2019-03-28 Thread Kevin Fenzi 
On 3/28/19 4:39 PM, Miro Hrončok wrote:
> On 28. 03. 19 21:54, Tuomo Soini wrote:
>> On Thu, 28 Mar 2019 13:22:26 +0100
>> Miro Hrončok  wrote:
>>
>>>
>>> A PR is at https://src.fedoraproject.org/rpms/python36/pull-request/27
>>
>>> I'm still not sure about how it will behave. We should probably test
>>> it.
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1687196
>>
>> Check my bug report first. You only need obsoletes in one place and
>> there was my suggested patch which was not good enough for some, but it
>> i a lot better than suggested change from Conflicts to Obsoletes all
>> over.
> 
> I don't understand why the obsoletes all over are any worse than just one.

In this case it's likely more what we want anyhow, as we want people to
move off the python34 packages. I don't think we want to keep them
around and supporting them forever. Obsoletes on everything will remove
the old python34 (and not pull in the new one) unless there's something
installed that actually needs python34.

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: EPEL-ANNOUNCE EPEL: Python34 moving to Python36

2019-03-28 Thread Miro Hrončok 

On 28. 03. 19 21:54, Tuomo Soini wrote:

On Thu, 28 Mar 2019 13:22:26 +0100
Miro Hrončok  wrote:



A PR is at https://src.fedoraproject.org/rpms/python36/pull-request/27



I'm still not sure about how it will behave. We should probably test
it.


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

Check my bug report first. You only need obsoletes in one place and
there was my suggested patch which was not good enough for some, but it
i a lot better than suggested change from Conflicts to Obsoletes all
over.


I don't understand why the obsoletes all over are any worse than just one.

--
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: EPEL-ANNOUNCE EPEL: Python34 moving to Python36

2019-03-28 Thread Tuomo Soini 
On Thu, 28 Mar 2019 13:22:26 +0100
Miro Hrončok  wrote:

> 
> A PR is at https://src.fedoraproject.org/rpms/python36/pull-request/27

> I'm still not sure about how it will behave. We should probably test
> it.

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

Check my bug report first. You only need obsoletes in one place and
there was my suggested patch which was not good enough for some, but it
i a lot better than suggested change from Conflicts to Obsoletes all
over.


-- 
Tuomo Soini 
Foobar Linux services
+358 40 5240030
Foobar Oy 
___
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: EPEL-ANNOUNCE EPEL: Python34 moving to Python36

2019-03-28 Thread Kevin Fenzi 
On 3/28/19 5:22 AM, Miro Hrončok wrote:
> 
> A PR is at https://src.fedoraproject.org/rpms/python36/pull-request/27
> 
> I'm still not sure about how it will behave. We should probably test it.

I just did a bunch of testing and the Obsoletes works great.

It does mean if someone has only packages that depend on
/usr/bin/python3 and has python34 installed for that, on upgrade they
will get just python36 and no python34. However, I think thats fine.

If they have other things that depend on 34 (the abi, or libs or the
like), they will get python36 and the updated python34 that doesn't
provide /usr/bin/python3.

I'm +1 to add this to the update and give it some more baking time.

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: EPEL-ANNOUNCE EPEL: Python34 moving to Python36

2019-03-28 Thread Neal Gompa 
On Thu, Mar 28, 2019 at 8:22 AM Miro Hrončok  wrote:
>
> On 26. 03. 19 1:51, Miro Hrončok wrote:
> > On 25. 03. 19 18:56, Kevin Fenzi wrote:
> >> Just make python36 obsolete the old version of python34 that had
> >> /usr/bin/python3. This causes yum to install the new python34 and pull
> >> in python36 for /usr/bin/python3.
> >
> > If that works, we are good. Does it really behave like that with plain 
> > upgrade?
> > E.g. without specifying what to upgrade?
> >
> > I thought that obsoleting old py34 can do one of the following:
> >
> > A) python34 gets queued for upgrading first, there is no more old python34 
> > to be
> > obsoleted by python36, python36 isn't installed.
> >
> > B) python36 gets queued for obsoleting old python34 first, python34 gets 
> > queued
> > for removing instead of updating, there is more pytho34 to be updated.
> >
> > C) what you said.
> >
> > If C) is the guaranteed behavior, I guess we are good to do this.
> >
> >> It does mean people with 3rd party software are now using python36
> >> instead of 34, but if they only speficied /usr/bin/python3, it should
> >> just run with any python3 version right?
> >
> > As long as they are only using standard library, yes. Otherwise there might 
> > be
> > problems. However that was anticipated.
>
> A PR is at https://src.fedoraproject.org/rpms/python36/pull-request/27
>
> I'm still not sure about how it will behave. We should probably test it.
>

Obsoletes means that the old package will get removed as part of the
upgrade. Conflicts means that yum has to figure out a way to keep it.
That's the difference.



-- 
真実はいつも一つ！/ Always, there's only one truth!
___
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