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
>> them into CBS as real builds.
>
> I realis
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 now, just create a `s
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 include
>> SCLs from CBS (cbs.centos.org,
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 `sig-sclo7-sclo-python` branch (we c
t.com]
Sent: Tuesday, July 11, 2017 4:45 AM
To: Davis, Daniel (NIH/NLM) [C]
Cc: sclorg@redhat.com
Subject: Re: [scl.org] Python "latest" SCLo
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’v
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. I noticed some talk of a community SCL for
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 SCL for a “latest” Python,
>> which would be
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 SCL for a “latest” Python,
> which would be a non-patched pure build of Python that is kept up-to-date b
Sent: Thursday, June 29, 2017 12:52 PM
To: Davis, Daniel (NIH/NLM) [C] ; 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 that
:* 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/
: [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 (NIH/NLM) [C] wrote:
I've
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, and
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 he
13 matches
Mail list logo
