Re: [scl.org] Python "latest" SCLo

2017-07-26 Thread Nick Coghlan
On Thu, Jul 13, 2017 at 5:18 PM, Nick Coghlan wrote: > On Wed, Jul 12, 2017 at 4:22 PM, Nick Coghlan wrote: >> I wasn't planning to publish the COPR builds anywhere other than COPR, >> they'd just be a place for me to tinker with things before pushing >>

Re: [scl.org] Python "latest" SCLo

2017-07-13 Thread Honza Horak
On 07/12/2017 08:22 AM, Nick Coghlan wrote: On Tue, Jul 11, 2017 at 11:39 PM, Honza Horak wrote: On 07/11/2017 10:44 AM, Nick Coghlan wrote: 1. Create a new sclo-python metapackage, using https://github.com/sclorg-distgit/rh-python35/tree/master as a starting point 2. For

Re: [scl.org] Python "latest" SCLo

2017-07-13 Thread Nick Coghlan
On Wed, Jul 12, 2017 at 4:22 PM, Nick Coghlan wrote: > On Tue, Jul 11, 2017 at 11:39 PM, Honza Horak wrote: >> This guide is actually not complete, as I've just realized -- copr is only >> one way to build SCLs for www.softwarecollections.org, but we can

Re: [scl.org] Python "latest" SCLo

2017-07-12 Thread Nick Coghlan
On Tue, Jul 11, 2017 at 11:39 PM, Honza Horak wrote: > On 07/11/2017 10:44 AM, Nick Coghlan wrote: >> 1. Create a new sclo-python metapackage, using >> https://github.com/sclorg-distgit/rh-python35/tree/master as a >> starting point >> 2. For now, just create a

Re: [scl.org] Python "latest" SCLo

2017-07-11 Thread Honza Horak
On 07/11/2017 10:44 AM, Nick Coghlan wrote: On Mon, Jul 3, 2017 at 3:47 PM, Nick Coghlan wrote: On Fri, Jun 30, 2017 at 1:24 AM, Davis, Daniel (NIH/NLM) [C] wrote: I’ve been lurking on this list for a while, and I wanted to bring myself up to date.

Re: [scl.org] Python "latest" SCLo

2017-07-11 Thread Nick Coghlan
On Mon, Jul 3, 2017 at 3:47 PM, Nick Coghlan wrote: > On Fri, Jun 30, 2017 at 1:24 AM, Davis, Daniel (NIH/NLM) [C] > wrote: >> I’ve been lurking on this list for a while, and I wanted to bring myself up >> to date. I noticed some talk of a community

Re: [scl.org] Python "latest" SCLo

2017-06-29 Thread Davis, Daniel (NIH/NLM) [C]
12:52 PM To: Davis, Daniel (NIH/NLM) [C] <daniel.da...@nih.gov>; sclorg@redhat.com Subject: Re: [scl.org] Python "latest" SCLo Yes, thanks Dan. Many security scanning tools look for the latest version and flag older versions as being a potential risk. I wanted to be sure th

Re: [scl.org] Python "latest" SCLo

2017-06-29 Thread Brian Gollaher
*To:* Davis, Daniel (NIH/NLM) [C] <daniel.da...@nih.gov>; sclorg@redhat.com *Subject:* Re: [scl.org] Python "latest" SCLo Hi Dan. May I ask a question? Is your security team looking for a fix to a specific security problem or CVE or are they asking that you run the latest version as

Re: [scl.org] Python "latest" SCLo

2017-06-29 Thread Davis, Daniel (NIH/NLM) [C]
sclorg@redhat.com Subject: Re: [scl.org] Python "latest" SCLo Hi Dan. May I ask a question? Is your security team looking for a fix to a specific security problem or CVE or are they asking that you run the latest version as a rule? thanks, Brian On 06/29/2017 11:24 AM, Davis, Daniel (NI

Re: [scl.org] Python "latest" SCLo

2017-06-29 Thread Brian Gollaher
Hi Dan. May I ask a question? Is your security team looking for a fix to a specific security problem or CVE or are they asking that you run the latest version as a rule? thanks, Brian On 06/29/2017 11:24 AM, Davis, Daniel (NIH/NLM) [C] wrote: I’ve been lurking on this list for a while,

[scl.org] Python "latest" SCLo

2017-06-29 Thread Davis, Daniel (NIH/NLM) [C]
I've been lurking on this list for a while, and I wanted to bring myself up to date. I noticed some talk of a community SCL for a "latest" Python, which would be a non-patched pure build of Python that is kept up-to-date by the community. Where is that at? Who is leading it? How can I