[scl.org] Python update request

Richard Hodgson richard at bricklane.com
Thu Apr 21 09:38:39 UTC 2016


Fair enough, re-raised there. Its
https://bugzilla.redhat.com/show_bug.cgi?id=1329132 if anyone is especially
interested.

thanks,
Richard



On 19 April 2016 at 20:58, Honza Horak <hhorak at redhat.com> wrote:

> Actually Dave was right, packages updates like your case are best to be
> tracked in RH Bugzilla, since RHEL is the primary focus for SCL and that is
> where it can be evaluated properly.
>
> Honza
>
> On 04/07/2016 01:52 PM, Richard Hodgson wrote:
>
>> Ah, thanks for the example ticket.
>>
>> I'll raise in the Centos buildsys project, as that seems to be where
>> everything is moving.
>>
>> Richard
>>
>> On 5 April 2016 at 16:35, Dave Johansen <davejohansen at gmail.com
>> <mailto:davejohansen at gmail.com>> wrote:
>>
>>     On Tue, Apr 5, 2016 at 7:13 AM, Richard Hodgson
>>     <richard at bricklane.com <mailto:richard at bricklane.com>> wrote:
>>
>>         Hello,
>>
>>         We use the python27 SCL that provides Python 2.7.8, which has
>>         worked brilliantly for some time on our application
>>         servers. Recently, we started seeing deprecation warnings from a
>>         Python module ("urllib3") related to SSL connections urging us
>>         to upgrade python to the latest 2.7.x release.
>>
>>         Whats the best way to request an updated version of an existing
>>         SCL package? Should I post here or raise a ticket somewhere in
>>         the Centos bug tracker?
>>
>>
>>     Opening a bugzilla worked in the past:
>>     https://bugzilla.redhat.com/show_bug.cgi?id=1167912
>>
>>
>>
>>
>> --
>> *Richard Hodgson*
>> Chief Technical Officer
>>
>>
>> bricklane.com <https://bricklane.com>
>>
>>
>> _______________________________________________
>> SCLorg mailing list
>> SCLorg at redhat.com
>> https://www.redhat.com/mailman/listinfo/sclorg
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/sclorg/attachments/20160421/0c18446c/attachment.htm>


More information about the SCLorg mailing list