From ncoghlan at redhat.com Mon Jul 3 05:47:07 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Mon, 3 Jul 2017 15:47:07 +1000 Subject: [scl.org] Python "latest" SCLo In-Reply-To: References: Message-ID: 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 by > the community. Where is that at? Who is leading it? That would be me, but it stalled while I was working on some Python 3.7 changes. Happily though, I have some time to spend on bootstrapping the "rolling Python" SCL this week, so I'm going to start working through the list of tasks at https://wiki.centos.org/SpecialInterestGroup/SCLo#head-b408f06ad89fd3a67686f755eafac7ce310ee081 (using the rh-python35 collection as a starting point) Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From ncoghlan at redhat.com Mon Jul 3 06:34:11 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Mon, 3 Jul 2017 16:34:11 +1000 Subject: [scl.org] CentOS build system sclo-sig application sent Message-ID: Hi folks, As mentioned in another thread, I'm finally getting started on bootstrapping a "rolling Python" SCL that follows the latest upstream releases (so it will follow 3.6 until the 3.7.0 release, then switch to following 3.7, etc, etc). Part of that involves officially signing up for SCLo SIG membership in the build system, so this is a note to say that: 1. I've applied for sclo-sig membership via accounts.centos.org 2. My account name is "ncoghlan" (but using my personal address rather than my RH one) 3. The purpose of the application is to set up a "sclo-python" community SCL that tracks the latest upstream stable release as described above At some point we may want to add a "sclo-python-preview" stream that includes the release candidates issued prior to upstream maintenance releases, and switches to the next maintenance branch once the first beta comes out, but if I/we do do anything like that, it would most likely be driven by the start of the 3.7 beta cycle rather than being something that gets done immediately. I'm starting the repo for this at https://github.com/ncoghlan/sclo-python/ (to be transferred to https://github.com/sclorg-distgit at a later date), and will chat to Tomas Orsava about how best to go about seeding that. Cheers, Nick. P.S. I'm starting to think it may actually make sense to start out with the 3.5 Red Hat SCL as a template, and then do a 3.5 -> 3.6 transition within the sclo-python stream to make it absolutely clear that when we say "rolling release, including major version upgrades" we really do mean "rolling release, including major version upgrades". Otherwise, regardless of what we say in the docs, I can see folks getting upset when the 3.6 -> 3.7 switch comes around and they happened to be relying on a previously deprecated feature that had finally been removed. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From perqvind at gmail.com Mon Jul 3 10:22:09 2017 From: perqvind at gmail.com (Per Qvindesland) Date: Mon, 3 Jul 2017 11:22:09 +0100 Subject: [scl.org] rh-php56 mcrypt module Message-ID: Hi List I am using rh-php56 on a cantos 7 box, but I need to install mcrypt but I see that it's not showing as available in yum list rh-php56\*, pecl only has a version for php7. Has anyone any hints of installing mcrypt module? Regards Per -------------- next part -------------- An HTML attachment was scrubbed... URL: From tgc at statsbiblioteket.dk Mon Jul 3 11:13:53 2017 From: tgc at statsbiblioteket.dk (Tom G. Christensen) Date: Mon, 3 Jul 2017 13:13:53 +0200 Subject: [scl.org] rh-php56 mcrypt module In-Reply-To: References: Message-ID: On 03/07/17 12:22, Per Qvindesland wrote: > Hi List > > I am using rh-php56 on a cantos 7 box, but I need to install mcrypt but > I see that it's not showing as available in yum list rh-php56\*, pecl > only has a version for php7. > > Has anyone any hints of installing mcrypt module? > Obligatory warning about mcrypt: https://blog.remirepo.net/post/2015/07/07/About-libmcrypt-and-php-mcrypt If you insist then here's where to get it: https://blog.remirepo.net/post/2017/02/23/Additional-PHP-packages-for-RHSCL -tgc From perqvind at gmail.com Mon Jul 3 11:31:31 2017 From: perqvind at gmail.com (Per Qvindesland) Date: Mon, 3 Jul 2017 12:31:31 +0100 Subject: [scl.org] rh-php56 mcrypt module In-Reply-To: References: Message-ID: Sweet many thanks, yeah I am not to crazy about it either but I am using simplesaml which requires mcrypt for https connections :( Per On Mon, Jul 3, 2017 at 12:13 PM, Tom G. Christensen wrote: > On 03/07/17 12:22, Per Qvindesland wrote: > >> Hi List >> >> I am using rh-php56 on a cantos 7 box, but I need to install mcrypt but I >> see that it's not showing as available in yum list rh-php56\*, pecl only >> has a version for php7. >> >> Has anyone any hints of installing mcrypt module? >> >> > Obligatory warning about mcrypt: > https://blog.remirepo.net/post/2015/07/07/About-libmcrypt-and-php-mcrypt > > If you insist then here's where to get it: > https://blog.remirepo.net/post/2017/02/23/Additional-PHP- > packages-for-RHSCL > > -tgc > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -------------- next part -------------- An HTML attachment was scrubbed... URL: From Fedora at FamilleCollet.com Mon Jul 3 12:41:05 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Mon, 3 Jul 2017 14:41:05 +0200 Subject: [scl.org] rh-php56 mcrypt module In-Reply-To: References: Message-ID: Le 03/07/2017 ? 13:31, Per Qvindesland a ?crit : > I am using simplesaml which requires mcrypt for https connections :( If your project use something which requires mcrypt, please file a upstream bug ;) BTW simplesaml doesn't seems to require mcrypt. Remi From perqvind at gmail.com Mon Jul 3 13:06:50 2017 From: perqvind at gmail.com (Per Qvindesland) Date: Mon, 3 Jul 2017 14:06:50 +0100 Subject: [scl.org] rh-php56 mcrypt module In-Reply-To: References: Message-ID: It does but there seem to be some work towards dropping the need for it going on, it's not my project :) once I had mcrypt installed it works as expected. On Mon, Jul 3, 2017 at 1:41 PM, Remi Collet wrote: > Le 03/07/2017 ? 13:31, Per Qvindesland a ?crit : > > I am using simplesaml which requires mcrypt for https connections :( > > If your project use something which requires mcrypt, > please file a upstream bug ;) > > BTW simplesaml doesn't seems to require mcrypt. > > > Remi > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ncoghlan at redhat.com Tue Jul 11 08:44:30 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Tue, 11 Jul 2017 18:44:30 +1000 Subject: [scl.org] Python "latest" SCLo In-Reply-To: References: Message-ID: 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 a non-patched pure build of Python that is kept up-to-date by >> the community. Where is that at? Who is leading it? > > That would be me, but it stalled while I was working on some Python > 3.7 changes. Happily though, I have some time to spend on > bootstrapping the "rolling Python" SCL this week, so I'm going to > start working through the list of tasks at > https://wiki.centos.org/SpecialInterestGroup/SCLo#head-b408f06ad89fd3a67686f755eafac7ce310ee081 > (using the rh-python35 collection as a starting point) So I finally started working on the technical aspects of this, and as near as I can figure out, what I'll need to do is: 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 can look at an sclo6 branch once 7 is working) 3. Edit https://github.com/ncoghlan/sclo-python/tree/sig-sclo7-sclo-python for the rh-python35 -> sclo-python name change 4. Start doing some test builds in COPR as per https://www.softwarecollections.org/en/docs/ In parallel with that: 4. Submit a buildsys request for an sclo-python tag that's similar to the existing rh-python35 one (akin to https://bugs.centos.org/view.php?id=9661 ) 5. Figure out what, if anything, needs to be done in terms of adding relevant branches to the other Python repos on https://github.com/sclorg-distgit 6. Actually start building real SCLs in the CentOS build system for publication to softwarecollections.org Cheers, Nick. P.S. Additional next step: provide feedback to the Fedora Modularity group on which aspects of this strike me as being the most annoyingly tedious, and what could potentially be done to make distro-submodule-based SCL definitions and updates less time consuming than the current process based directly on RPMs and dist-git :) -- Nick Coghlan Red Hat Platform Engineering, Brisbane From hhorak at redhat.com Tue Jul 11 13:39:03 2017 From: hhorak at redhat.com (Honza Horak) Date: Tue, 11 Jul 2017 15:39:03 +0200 Subject: [scl.org] Python "latest" SCLo In-Reply-To: References: Message-ID: <44a4a80d-2327-3282-e516-784aad7c6a09@redhat.com> 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 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? >> >> That would be me, but it stalled while I was working on some Python >> 3.7 changes. Happily though, I have some time to spend on >> bootstrapping the "rolling Python" SCL this week, so I'm going to >> start working through the list of tasks at >> https://wiki.centos.org/SpecialInterestGroup/SCLo#head-b408f06ad89fd3a67686f755eafac7ce310ee081 >> (using the rh-python35 collection as a starting point) > > So I finally started working on the technical aspects of this, and as > near as I can figure out, what I'll need to do is: > > 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 can look > at an sclo6 branch once 7 is working) > 3. Edit https://github.com/ncoghlan/sclo-python/tree/sig-sclo7-sclo-python > for the rh-python35 -> sclo-python name change > 4. Start doing some test builds in COPR as per > https://www.softwarecollections.org/en/docs/ 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, build by SCLo SIG) as well. We should fix this part of documentation, thanks for pointing to it.. > In parallel with that: > > 4. Submit a buildsys request for an sclo-python tag that's similar to > the existing rh-python35 one (akin to > https://bugs.centos.org/view.php?id=9661 ) I can help with requesting CBS stuff, I think we can request both and build el7 first.. existance of the tag el6 does not mean we need to ever release it.. if we don't want to from some reason.. The only thing we need to make clear is the naming -- sclo-python3 or sclo-python? From my PoV sclo-python3 better describes what is inside.. but maybe there are other opinions.. Honza > 5. Figure out what, if anything, needs to be done in terms of adding > relevant branches to the other Python repos on > https://github.com/sclorg-distgit > 6. Actually start building real SCLs in the CentOS build system for > publication to softwarecollections.org > > Cheers, > Nick. > > P.S. Additional next step: provide feedback to the Fedora Modularity > group on which aspects of this strike me as being the most annoyingly > tedious, and what could potentially be done to make > distro-submodule-based SCL definitions and updates less time consuming > than the current process based directly on RPMs and dist-git :) > > From daniel.davis at nih.gov Tue Jul 11 14:38:45 2017 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Tue, 11 Jul 2017 14:38:45 +0000 Subject: [scl.org] Python "latest" SCLo In-Reply-To: References: Message-ID: I will be able to provide testing, and I'll follow along. Your note about how fast it will move really points out that we need to learn how to do it ourselves, because we will want to move both fast and slow, at times. -----Original Message----- From: Nick Coghlan [mailto:ncoghlan at redhat.com] Sent: Tuesday, July 11, 2017 4:45 AM To: Davis, Daniel (NIH/NLM) [C] Cc: sclorg at 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?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? > > That would be me, but it stalled while I was working on some Python > 3.7 changes. Happily though, I have some time to spend on > bootstrapping the "rolling Python" SCL this week, so I'm going to > start working through the list of tasks at > https://wiki.centos.org/SpecialInterestGroup/SCLo#head-b408f06ad89fd3a > 67686f755eafac7ce310ee081 (using the rh-python35 collection as a > starting point) So I finally started working on the technical aspects of this, and as near as I can figure out, what I'll need to do is: 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 can look at an sclo6 branch once 7 is working) 3. Edit https://github.com/ncoghlan/sclo-python/tree/sig-sclo7-sclo-python for the rh-python35 -> sclo-python name change 4. Start doing some test builds in COPR as per https://www.softwarecollections.org/en/docs/ In parallel with that: 4. Submit a buildsys request for an sclo-python tag that's similar to the existing rh-python35 one (akin to https://bugs.centos.org/view.php?id=9661 ) 5. Figure out what, if anything, needs to be done in terms of adding relevant branches to the other Python repos on https://github.com/sclorg-distgit 6. Actually start building real SCLs in the CentOS build system for publication to softwarecollections.org Cheers, Nick. P.S. Additional next step: provide feedback to the Fedora Modularity group on which aspects of this strike me as being the most annoyingly tedious, and what could potentially be done to make distro-submodule-based SCL definitions and updates less time consuming than the current process based directly on RPMs and dist-git :) -- Nick Coghlan Red Hat Platform Engineering, Brisbane From ncoghlan at redhat.com Wed Jul 12 06:22:38 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Wed, 12 Jul 2017 16:22:38 +1000 Subject: [scl.org] Python "latest" SCLo In-Reply-To: <44a4a80d-2327-3282-e516-784aad7c6a09@redhat.com> References: <44a4a80d-2327-3282-e516-784aad7c6a09@redhat.com> Message-ID: 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 can look >> at an sclo6 branch once 7 is working) >> 3. Edit https://github.com/ncoghlan/sclo-python/tree/sig-sclo7-sclo-python >> for the rh-python35 -> sclo-python name change >> 4. Start doing some test builds in COPR as per >> https://www.softwarecollections.org/en/docs/ > > 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, build by SCLo SIG) as well. We should fix > this part of documentation, thanks for pointing to it.. 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. >> In parallel with that: >> >> 4. Submit a buildsys request for an sclo-python tag that's similar to >> the existing rh-python35 one (akin to >> https://bugs.centos.org/view.php?id=9661 ) > > I can help with requesting CBS stuff, I think we can request both and build > el7 first.. existance of the tag el6 does not mean we need to ever release > it.. if we don't want to from some reason.. I'm happy to publish both, I just figured it made sense to focus on EL7 first, since I've never been through this process before :) So the two pieces here would be: - my sig-sclo membership request is currently still pending in https://accounts.centos.org - we'll need to file a tag request once we agree on the name > The only thing we need to make clear is the naming -- sclo-python3 or > sclo-python? From my PoV sclo-python3 better describes what is inside.. but > maybe there are other opinions.. If there's ever a Python 4.0, I'd update the rolling SCL to track it rather than sticking with the last 3.x release, so I think "sclo-python" conveys that intent more clearly. I'm also assuming that as long as there's customer demand for them, RH will continue to provide the version specific "rh-pythonXY" SCLs (or something functionally equivalent), so there isn't going to be any great need to restrict the rolling SCL updates - folks will be able to move onto sclo-python if they want to get ahead of the rh-pythonXY streams for some reason, and then potentially drop back to the Red Hat ones if they want to stick with an older release for a while even after a new one becomes available. In Fedora Modularity [1,2] terms, I'm essentially seeing sclo-python as corresponding to a "latest" stream label, while the various rh-pythonXY SCLs would correspond to "X.Y" stream labels. Cheers, Nick. [1] https://docs.pagure.org/modularity/ [2] https://lists.fedoraproject.org/archives/list/devel at lists.fedoraproject.org/thread/AKSJ67CS5G7WBQQKO6OCIISC3ARSUG7L/ -- Nick Coghlan Red Hat Platform Engineering, Brisbane From Tim.Stalker at ucdenver.edu Wed Jul 12 16:35:11 2017 From: Tim.Stalker at ucdenver.edu (Stalker, Tim) Date: Wed, 12 Jul 2017 16:35:11 +0000 Subject: [scl.org] PHP 5.6 updates Message-ID: Checking to see if there is a schedule for updates to the rh-php56 version (5.6.25) and when updates may go forward. Thanks, Tim Stalker University of Colorado -------------- next part -------------- An HTML attachment was scrubbed... URL: From Fedora at FamilleCollet.com Thu Jul 13 04:45:46 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Thu, 13 Jul 2017 06:45:46 +0200 Subject: [scl.org] PHP 5.6 updates In-Reply-To: References: Message-ID: <0bcc2990-2d7f-fcd0-79dc-b4561adbe050@FamilleCollet.com> Le 12/07/2017 ? 18:35, Stalker, Tim a ?crit : > Checking to see if there is a schedule for updates to the rh-php56 version (5.6.25) and when updates may go forward. As for base packages, this is an official collection, so rh-php56-* packages are maintained by Red Hat. While sclo-php56-* are community packages What kind of update do you expect ? Should probably file a bug on RH bugzilla. Remi. From ncoghlan at redhat.com Thu Jul 13 07:18:05 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Thu, 13 Jul 2017 17:18:05 +1000 Subject: [scl.org] Python "latest" SCLo In-Reply-To: References: <44a4a80d-2327-3282-e516-784aad7c6a09@redhat.com> Message-ID: 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, build by SCLo SIG) as well. We should fix >> this part of documentation, thanks for pointing to it.. > > 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 realised I'm going to want a public development repo to hold any notes I make about the process, as well as any custom tools I build, so I've created that here: https://github.com/ncoghlan/pyscl-devel/ The identified steps for creating and publishing an initial version of sclo-python have been turned into an issue here: https://github.com/ncoghlan/pyscl-devel/issues/1 Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From msuchy at redhat.com Thu Jul 13 13:33:55 2017 From: msuchy at redhat.com (=?UTF-8?Q?Miroslav_Such=c3=bd?=) Date: Thu, 13 Jul 2017 15:33:55 +0200 Subject: [scl.org] Website outage Message-ID: <179fb1bb-f282-fde0-3bfa-c8d605172ce8@redhat.com> Hi, we are going to migrate website softwarecollection.org to new machine. It will get new IP as well. Therefore it may be unavailable in upcoming hours. The migration will start in few hours and I will let you know when it is over. Kind Regards Miroslav Suchy From Jaroslaw.Polok at cern.ch Thu Jul 13 16:36:37 2017 From: Jaroslaw.Polok at cern.ch (Jarek Polok) Date: Thu, 13 Jul 2017 18:36:37 +0200 Subject: [scl.org] New pythonXXmore collection(s) ? Message-ID: <0e99692f-bc9a-70f5-3265-b1ad1c4681aa@cern.ch> Hello all. For the needs of other project we did rebuild few more packages for python27 SCLo: python27-Cython python27-python-chardet python27-python-flask python27-python-requests python27-python-urllib3 python27-python-mock python27-python-tox python27-python-py python27-python-itsdangerous python27-python-backports python27-python-backports-ssl_match_hostname since these are already "SCL'ized" it should be easy to rebuild for other SCLo python versions too .. If there is some interest we could make these available to everybody as pythonXXmore collections for 6 and 7 ? (similar to phpXXmore collections) Your opinion ? Best Regards Jarek From Jaroslaw.Polok at cern.ch Thu Jul 13 16:40:00 2017 From: Jaroslaw.Polok at cern.ch (Jarek Polok) Date: Thu, 13 Jul 2017 18:40:00 +0200 Subject: [scl.org] How to get listed on softwarecollections.org ? Message-ID: <48d147fa-514f-fc89-b11a-faabeceab34d@cern.ch> Dear all, I'm the "guilty" for following SCLo's: http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-git25/ http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-git212/ http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-httpd24more/ http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-subversion19/ (also available for centos 6) How could I get these listed on www.softwarecollections.org ? Best Regards Jarek From tim.stalker at ucdenver.edu Thu Jul 13 18:12:09 2017 From: tim.stalker at ucdenver.edu (Tim Stalker) Date: Thu, 13 Jul 2017 12:12:09 -0600 Subject: [scl.org] SCLorg Digest, Vol 42, Issue 5 Message-ID: Updates to the base rh-php56 version, not the community libraries. Sent from my Verizon 4G LTE smartphone -------- Original message -------- From: sclorg-request at redhat.com Date: 7/13/17 10:00 AM (GMT-07:00) To: sclorg at redhat.com Subject: SCLorg Digest, Vol 42, Issue 5 Send SCLorg mailing list submissions to sclorg at redhat.com To subscribe or unsubscribe via the World Wide Web, visit https://www.redhat.com/mailman/listinfo/sclorg or, via email, send a message with subject or body 'help' to sclorg-request at redhat.com You can reach the person managing the list at sclorg-owner at redhat.com When replying, please edit your Subject line so it is more specific than "Re: Contents of SCLorg digest..." Today's Topics: ?? 1. PHP 5.6 updates (Stalker, Tim) ?? 2. Re: PHP 5.6 updates (Remi Collet) ?? 3. Re: Python "latest" SCLo (Nick Coghlan) ?? 4. Website outage (Miroslav Such?) ---------------------------------------------------------------------- Message: 1 Date: Wed, 12 Jul 2017 16:35:11 +0000 From: "Stalker, Tim" To: "sclorg at redhat.com" Subject: [scl.org] PHP 5.6 updates Message-ID: Content-Type: text/plain; charset="iso-8859-1" Checking to see if there is a schedule for updates to the rh-php56 version (5.6.25) and when updates may go forward. Thanks, Tim Stalker University of Colorado -------------- next part -------------- An HTML attachment was scrubbed... URL: ------------------------------ Message: 2 Date: Thu, 13 Jul 2017 06:45:46 +0200 From: Remi Collet To: sclorg at redhat.com Subject: Re: [scl.org] PHP 5.6 updates Message-ID: <0bcc2990-2d7f-fcd0-79dc-b4561adbe050 at FamilleCollet.com> Content-Type: text/plain; charset=utf-8 Le 12/07/2017 ? 18:35, Stalker, Tim a ?crit : > Checking to see if there is a schedule for updates to the rh-php56 version (5.6.25) and when updates may go forward. As for base packages, this is an official collection, so rh-php56-* packages are maintained by Red Hat. While sclo-php56-* are community packages What kind of update do you expect ? Should probably? file a bug on RH bugzilla. Remi. ------------------------------ Message: 3 Date: Thu, 13 Jul 2017 17:18:05 +1000 From: Nick Coghlan To: Honza Horak Cc: sclorg at redhat.com Subject: Re: [scl.org] Python "latest" SCLo Message-ID: Content-Type: text/plain; charset="UTF-8" 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, build by SCLo SIG) as well. We should fix >> this part of documentation, thanks for pointing to it.. > > 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 realised I'm going to want a public development repo to hold any notes I make about the process, as well as any custom tools I build, so I've created that here: https://github.com/ncoghlan/pyscl-devel/ The identified steps for creating and publishing an initial version of sclo-python have been turned into an issue here: https://github.com/ncoghlan/pyscl-devel/issues/1 Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane ------------------------------ Message: 4 Date: Thu, 13 Jul 2017 15:33:55 +0200 From: Miroslav Such? To: "sclorg at redhat.com" Subject: [scl.org] Website outage Message-ID: <179fb1bb-f282-fde0-3bfa-c8d605172ce8 at redhat.com> Content-Type: text/plain; charset=iso-8859-2; format=flowed Hi, we are going to migrate website softwarecollection.org to new machine. It will get new IP as well. Therefore it may be unavailable in upcoming hours. The migration will start in few hours and I will let you know when it is over. Kind Regards Miroslav Suchy ------------------------------ _______________________________________________ SCLorg mailing list SCLorg at redhat.com https://www.redhat.com/mailman/listinfo/sclorg End of SCLorg Digest, Vol 42, Issue 5 ************************************* -------------- next part -------------- An HTML attachment was scrubbed... URL: From hhorak at redhat.com Thu Jul 13 21:26:37 2017 From: hhorak at redhat.com (Honza Horak) Date: Thu, 13 Jul 2017 23:26:37 +0200 Subject: [scl.org] Python "latest" SCLo In-Reply-To: References: <44a4a80d-2327-3282-e516-784aad7c6a09@redhat.com> Message-ID: 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 `sig-sclo7-sclo-python` branch (we can look >>> at an sclo6 branch once 7 is working) >>> 3. Edit https://github.com/ncoghlan/sclo-python/tree/sig-sclo7-sclo-python >>> for the rh-python35 -> sclo-python name change >>> 4. Start doing some test builds in COPR as per >>> https://www.softwarecollections.org/en/docs/ >> >> 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, build by SCLo SIG) as well. We should fix >> this part of documentation, thanks for pointing to it.. > > 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. > >>> In parallel with that: >>> >>> 4. Submit a buildsys request for an sclo-python tag that's similar to >>> the existing rh-python35 one (akin to >>> https://bugs.centos.org/view.php?id=9661 ) >> >> I can help with requesting CBS stuff, I think we can request both and build >> el7 first.. existance of the tag el6 does not mean we need to ever release >> it.. if we don't want to from some reason.. > > I'm happy to publish both, I just figured it made sense to focus on > EL7 first, since I've never been through this process before :) > > So the two pieces here would be: > > - my sig-sclo membership request is currently still pending in > https://accounts.centos.org > - we'll need to file a tag request once we agree on the name > >> The only thing we need to make clear is the naming -- sclo-python3 or >> sclo-python? From my PoV sclo-python3 better describes what is inside.. but >> maybe there are other opinions.. > > If there's ever a Python 4.0, I'd update the rolling SCL to track it > rather than sticking with the last 3.x release, so I think > "sclo-python" conveys that intent more clearly. Ok, that makes sense to me, I'll ask for the tags/targets for "sclo-python" SCL if there are no objections about naming later this week. Honza > I'm also assuming that as long as there's customer demand for them, RH > will continue to provide the version specific "rh-pythonXY" SCLs (or > something functionally equivalent), so there isn't going to be any > great need to restrict the rolling SCL updates - folks will be able to > move onto sclo-python if they want to get ahead of the rh-pythonXY > streams for some reason, and then potentially drop back to the Red Hat > ones if they want to stick with an older release for a while even > after a new one becomes available. > > In Fedora Modularity [1,2] terms, I'm essentially seeing sclo-python > as corresponding to a "latest" stream label, while the various > rh-pythonXY SCLs would correspond to "X.Y" stream labels. > > Cheers, > Nick. > > [1] https://docs.pagure.org/modularity/ > [2] https://lists.fedoraproject.org/archives/list/devel at lists.fedoraproject.org/thread/AKSJ67CS5G7WBQQKO6OCIISC3ARSUG7L/ > From ncoghlan at redhat.com Fri Jul 14 02:53:53 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Fri, 14 Jul 2017 12:53:53 +1000 Subject: [scl.org] RPM list builder & RHSCL rebuild recipes Message-ID: In putting together the todo list for the sclo-python SCL, Red Hat's Python maintenance team pointed me towards some of the tools used to maintain the Red Hat SCLs: https://github.com/ncoghlan/pyscl-devel/issues/1#issuecomment-315037884 In particular, RPM List Builder automates running through a series of packages builds based on a YAML recipe file: https://github.com/sclorg/rpm-list-builder/blob/master/docs/users_guide.md That then allows the build sequence for an SCL (including any required bootstrapping builds) to be automated. For example, the Python 3.5 SCL build sequence: https://github.com/sclorg/rhscl-rebuild-recipes/blob/master/python.yml#L87 These aren't currently mentioned in the SCL guide or on the SCLo-SIG wiki, so I figured I'd start by posting a message about them here, and then after I have the sclo-python SCL up and running try to come up with some suitable documentation updates. Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From ncoghlan at redhat.com Fri Jul 14 02:55:22 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Fri, 14 Jul 2017 12:55:22 +1000 Subject: [scl.org] New pythonXXmore collection(s) ? In-Reply-To: <0e99692f-bc9a-70f5-3265-b1ad1c4681aa@cern.ch> References: <0e99692f-bc9a-70f5-3265-b1ad1c4681aa@cern.ch> Message-ID: On Fri, Jul 14, 2017 at 2:36 AM, Jarek Polok wrote: > If there is some interest we could make these available > to everybody as pythonXXmore collections for 6 and 7 ? > (similar to phpXXmore collections) > > Your opinion ? +1, sounds like a good idea to me. Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From msuchy at redhat.com Fri Jul 14 11:32:57 2017 From: msuchy at redhat.com (=?UTF-8?Q?Miroslav_Such=c3=bd?=) Date: Fri, 14 Jul 2017 13:32:57 +0200 Subject: [scl.org] Website outage In-Reply-To: <179fb1bb-f282-fde0-3bfa-c8d605172ce8@redhat.com> References: <179fb1bb-f282-fde0-3bfa-c8d605172ce8@redhat.com> Message-ID: <54b6f52c-9d33-2275-d481-cee8710c1a87@redhat.com> Dne 13.7.2017 v 15:33 Miroslav Such? napsal(a): > Hi, > we are going to migrate website softwarecollection.org to new machine. It will get new IP as well. Therefore it may be > unavailable in upcoming hours. The migration will start in few hours and I will let you know when it is over. > > Kind Regards > Miroslav Suchy The website is on the new machine. Sorry that it too long, but on the other side the downtime was minimal. Mirek From daniel.davis at nih.gov Fri Jul 14 15:12:51 2017 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Fri, 14 Jul 2017 15:12:51 +0000 Subject: [scl.org] RPM list builder & RHSCL rebuild recipes In-Reply-To: References: Message-ID: It might be nice to provide an sclo-python35 and sclo-python36 so that users such as we have an easier time not updating. I hope we will not for a long time be in the situation between python 2.7 and python 3, but it could happen between 36 and 37 for any of a number of reasons. However, that implies more work to get it set up. It becomes non-automated as 37 comes out. Thoughts? -----Original Message----- From: sclorg-bounces at redhat.com [mailto:sclorg-bounces at redhat.com] On Behalf Of Nick Coghlan Sent: Thursday, July 13, 2017 10:54 PM To: sclorg at redhat.com Subject: [scl.org] RPM list builder & RHSCL rebuild recipes In putting together the todo list for the sclo-python SCL, Red Hat's Python maintenance team pointed me towards some of the tools used to maintain the Red Hat SCLs: https://github.com/ncoghlan/pyscl-devel/issues/1#issuecomment-315037884 In particular, RPM List Builder automates running through a series of packages builds based on a YAML recipe file: https://github.com/sclorg/rpm-list-builder/blob/master/docs/users_guide.md That then allows the build sequence for an SCL (including any required bootstrapping builds) to be automated. For example, the Python 3.5 SCL build sequence: https://github.com/sclorg/rhscl-rebuild-recipes/blob/master/python.yml#L87 These aren't currently mentioned in the SCL guide or on the SCLo-SIG wiki, so I figured I'd start by posting a message about them here, and then after I have the sclo-python SCL up and running try to come up with some suitable documentation updates. Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane _______________________________________________ SCLorg mailing list SCLorg at redhat.com https://www.redhat.com/mailman/listinfo/sclorg From mguerett at redhat.com Fri Jul 14 20:02:23 2017 From: mguerett at redhat.com (Michael Guerette) Date: Fri, 14 Jul 2017 16:02:23 -0400 Subject: [scl.org] Fwd: softwarecollections.org down Message-ID: Can someone take a look at this? Thanks, Mike --------- Hi Mike, See this tweet: https://twitter.com/orediggerco/status/885891068511887362. It looks like softwarecollections.org no longer exists - do you know if that was intentional or was ever communicated? I expect I need to chase this further, so let me know who I should pester. Thanks! John -- -- Mike Guerette Red Hat Developer Program mguerett at redhat.comdevelopers.redhat.com @MikGue @RHdevelopers O 978-392-3154 <(978)%20392-3154> M 603-391-5858 <(603)%20391-5858> -------------- next part -------------- An HTML attachment was scrubbed... URL: From ncoghlan at redhat.com Mon Jul 17 05:00:15 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Mon, 17 Jul 2017 15:00:15 +1000 Subject: [scl.org] RPM list builder & RHSCL rebuild recipes In-Reply-To: References: Message-ID: On Sat, Jul 15, 2017 at 1:12 AM, Davis, Daniel (NIH/NLM) [C] wrote: > It might be nice to provide an sclo-python35 and sclo-python36 so that users such as we have an easier time not updating. Aye, I think that would be sensible, even though it's not something I'd personally want to work on in my own time. However, I think the most suitable model would be something similar to the way the community addons for PHP work, where the rh-pythonXY packages are still used as a base, with community managed addon streams being built around those, similar to the community addons for PHP that Remi publishes. That is, the way I'd see that working in terms of the way the underlying distros work: - sclo-python: Fedora equivalent (community defined) - rh-pythonXY (in RHSCL): RHEL equivalent (Red Hat defined) - rh-pythonXY (from SCLo): CentOS equivalent (still Red Hat defined) - sclo-pythonXY: EPEL equivalent (community defined) That approach *does* leave open the question around Red Hat's security policy for rh-pythonXY updates (which is currently backport-based, the same as RHEL, with rebasing to new upstream maintenance releases being the exception rather than the rule), but sclo-python will be able to fill the "always rebase" role for 3.6 until 3.7 comes out, which means we can postpone coming up with a different answer until we get closer to having an upstream 3.7.0 release to worry about (and even there we have options - we may decide that sclo-python shouldn't update until after 3.7.1 is out, for example). > I hope we will not for a long time be in the situation between python 2.7 and python 3, but it could happen between 36 and 37 for any of a number of reasons. However, that implies more work to get it set up. It becomes non-automated as 37 comes out. Yep, which is why I think we're going to need Red Hat's paid maintenance staff somewhere in the sustaining engineering path for the stable versions, similar to the way that CentOS is a RHEL rebuild that Fedora's EPEL can build on top of. That kind of work makes for a decent job, but a fairly lousy volunteer activity :) Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From pvalena at redhat.com Mon Jul 17 14:41:39 2017 From: pvalena at redhat.com (Pavel Valena) Date: Mon, 17 Jul 2017 10:41:39 -0400 (EDT) Subject: [scl.org] How to get listed on softwarecollections.org ? In-Reply-To: <48d147fa-514f-fc89-b11a-faabeceab34d@cern.ch> References: <48d147fa-514f-fc89-b11a-faabeceab34d@cern.ch> Message-ID: <1724464066.17187840.1500302499464.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Jarek Polok" > To: sclorg at redhat.com > Sent: Thursday, July 13, 2017 6:40:00 PM > Subject: [scl.org] How to get listed on softwarecollections.org ? > > Dear all, > > I'm the "guilty" for following SCLo's: > > http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-git25/ > http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-git212/ > http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-httpd24more/ > http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-subversion19/ Hello, you can create your own user(Fedora FAS is required; top right 'Log in' should suffice) to maintain it yourself. Alternatively one of SCLo SIG members[1] with access and some spare cycles can add those entries under the `sclo` user, in case you wan't the SCLs to be represented as a part of SCLo SIG[2]. Please let us know. Regards, Pavel [1] https://wiki.centos.org/SpecialInterestGroup/SCLo [2] https://accounts.centos.org/group/members/sig-sclo > > (also available for centos 6) > > How could I get these listed on www.softwarecollections.org ? > > Best Regards > > Jarek From Fedora at FamilleCollet.com Mon Jul 17 15:17:11 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Mon, 17 Jul 2017 17:17:11 +0200 Subject: [scl.org] New pythonXXmore collection(s) ? In-Reply-To: <0e99692f-bc9a-70f5-3265-b1ad1c4681aa@cern.ch> References: <0e99692f-bc9a-70f5-3265-b1ad1c4681aa@cern.ch> Message-ID: <0aa3b664-0fbf-02f4-5d11-ed25d5b7d9a3@FamilleCollet.com> Le 13/07/2017 ? 18:36, Jarek Polok a ?crit : > Hello all. > > For the needs of other project we did rebuild few more packages for > python27 SCLo: > > python27-Cython > python27-python-chardet > python27-python-flask > python27-python-requests > python27-python-urllib3 > python27-python-mock > python27-python-tox > python27-python-py > python27-python-itsdangerous > python27-python-backports > python27-python-backports-ssl_match_hostname > > since these are already "SCL'ized" it should be easy to > rebuild for other SCLo python versions too .. > > If there is some interest we could make these available > to everybody as pythonXXmore collections for 6 and 7 ? > (similar to phpXXmore collections)> > Your opinion ? > > Best Regards Sounds like a good idea. BTW, I think sclo-python## will be a better name (as we now have scl-php##, the php##more collections are pre-SCLo work, deprecated, and unmaintained). Remi From hhorak at redhat.com Wed Jul 19 10:23:39 2017 From: hhorak at redhat.com (Honza Horak) Date: Wed, 19 Jul 2017 12:23:39 +0200 Subject: [scl.org] New pythonXXmore collection(s) ? In-Reply-To: <0aa3b664-0fbf-02f4-5d11-ed25d5b7d9a3@FamilleCollet.com> References: <0e99692f-bc9a-70f5-3265-b1ad1c4681aa@cern.ch> <0aa3b664-0fbf-02f4-5d11-ed25d5b7d9a3@FamilleCollet.com> Message-ID: <03d7a59a-c5be-eea6-8574-9f9d631435d1@redhat.com> I'm +1 as well. Honza On 07/17/2017 05:17 PM, Remi Collet wrote: > Le 13/07/2017 ? 18:36, Jarek Polok a ?crit : >> Hello all. >> >> For the needs of other project we did rebuild few more packages for >> python27 SCLo: >> >> python27-Cython >> python27-python-chardet >> python27-python-flask >> python27-python-requests >> python27-python-urllib3 >> python27-python-mock >> python27-python-tox >> python27-python-py >> python27-python-itsdangerous >> python27-python-backports >> python27-python-backports-ssl_match_hostname >> >> since these are already "SCL'ized" it should be easy to >> rebuild for other SCLo python versions too .. >> >> If there is some interest we could make these available >> to everybody as pythonXXmore collections for 6 and 7 ? >> (similar to phpXXmore collections)> >> Your opinion ? >> >> Best Regards > > Sounds like a good idea. > > BTW, I think sclo-python## will be a better name (as we now have > scl-php##, the php##more collections are pre-SCLo work, deprecated, and > unmaintained). > > > Remi > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From tadej.j at nez.si Wed Jul 19 14:34:48 2017 From: tadej.j at nez.si (Tadej =?UTF-8?Q?Jane=C5=BE?=) Date: Wed, 19 Jul 2017 16:34:48 +0200 Subject: [scl.org] When will rh-postgresql94 SCL be updated in CentOS? Message-ID: <1500474888.6608.7.camel@nez.si> Hi! I have a fleet of CentOS and RHEL machines which use rh-postgresql94 SCL. I saw that RHEL machines got an update to version 9.4.12-1.el7, but the CentOS machines didn't. Searching the CBS, I found that version 9.4.9-1.el7 is the latest one: http://cbs.centos.org/koji/packageinfo?packageID=1695 Besides the obvious question stated in the subject, I would also kindly ask for answers to: 1. What is the current process of updates flowing from RHSCLs to Centos SCLs? 2. Where does softwarecollections.org fit into the picture? Thanks and regards, Tadej From Jaroslaw.Polok at cern.ch Wed Jul 26 09:43:57 2017 From: Jaroslaw.Polok at cern.ch (Jarek Polok) Date: Wed, 26 Jul 2017 11:43:57 +0200 Subject: [scl.org] New pythonXXmore collection(s) ? In-Reply-To: <0aa3b664-0fbf-02f4-5d11-ed25d5b7d9a3@FamilleCollet.com> References: <0e99692f-bc9a-70f5-3265-b1ad1c4681aa@cern.ch> <0aa3b664-0fbf-02f4-5d11-ed25d5b7d9a3@FamilleCollet.com> Message-ID: <9c048287-af59-18ae-a54e-0dc46e33c41c@cern.ch> > BTW, I think sclo-python## will be a better name (as we now have > scl-php##, the php##more collections are pre-SCLo work, deprecated, and > unmaintained). > Yes, indeed: packages / collections will be named sclo-pythonXX Thanks ! Jarek > > Remi > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From ncoghlan at redhat.com Wed Jul 26 11:34:25 2017 From: ncoghlan at redhat.com (Nick Coghlan) Date: Wed, 26 Jul 2017 21:34:25 +1000 Subject: [scl.org] Python "latest" SCLo In-Reply-To: References: <44a4a80d-2327-3282-e516-784aad7c6a09@redhat.com> Message-ID: 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 realised I'm going to want a public development repo to hold any > notes I make about the process, as well as any custom tools I build, > so I've created that here: https://github.com/ncoghlan/pyscl-devel/ Status update on this: - with some adjustments to the relevant spec files, I came up with an rpm-list-builder recipe that can bootstrap the whole rh-python35 SCL stack in a clean mock chroot in about an hour (depending on your system specs) - the README at https://github.com/ncoghlan/pyscl-devel/ covers how to run such a build yourself if you're so inclined As noted at https://github.com/ncoghlan/pyscl-devel/issues/1, the next steps will be to switch the built SCL name over to "sclo-python", and then get it building in COPR using actual bootstrap component releases rather than private RPM builds with tweaked release tags. I still have a PyCon Australia talk to finish, though, so I'm planning to take a break from working on this until after that's done. I'm definitely open to PRs if anyone wanted to take a look at what's involved in the rename in the meantime :) Cheers, Nick. -- Nick Coghlan Red Hat Platform Engineering, Brisbane From Jaroslaw.Polok at cern.ch Wed Jul 26 16:20:25 2017 From: Jaroslaw.Polok at cern.ch (Jarek Polok) Date: Wed, 26 Jul 2017 18:20:25 +0200 Subject: [scl.org] How to get listed on softwarecollections.org ? In-Reply-To: <1724464066.17187840.1500302499464.JavaMail.zimbra@redhat.com> References: <48d147fa-514f-fc89-b11a-faabeceab34d@cern.ch> <1724464066.17187840.1500302499464.JavaMail.zimbra@redhat.com> Message-ID: <94bbc645-76e3-bf4c-a4ab-8bfaf3bd73c2@cern.ch> On 07/17/2017 04:41 PM, Pavel Valena wrote: > ----- Original Message ----- >> From: "Jarek Polok" >> To: sclorg at redhat.com >> Sent: Thursday, July 13, 2017 6:40:00 PM >> Subject: [scl.org] How to get listed on softwarecollections.org ? >> >> Dear all, >> >> I'm the "guilty" for following SCLo's: >> >> http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-git25/ >> http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-git212/ >> http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-httpd24more/ >> http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-subversion19/ > Hello, > > you can create your own user(Fedora FAS is required; top right 'Log in' should suffice) to maintain it yourself. Alternatively one of SCLo SIG members[1] with access and some spare cycles can add those entries under the `sclo` user, in case you wan't the SCLs to be represented as a part of SCLo SIG[2]. > Thanks for info ! but it seems I could only add copr built collections there ? but these listed above are cbs - built ? Honza: I think it would be better if these are added under 'sclo' user ? Could you please do that ? Thanks ! Jarek > Please let us know. > > Regards, > Pavel > > [1] https://wiki.centos.org/SpecialInterestGroup/SCLo > [2] https://accounts.centos.org/group/members/sig-sclo > >> >> (also available for centos 6) >> >> How could I get these listed on www.softwarecollections.org ? >> >> Best Regards >> >> Jarek From hhorak at redhat.com Fri Jul 28 13:36:47 2017 From: hhorak at redhat.com (Honza Horak) Date: Fri, 28 Jul 2017 15:36:47 +0200 Subject: [scl.org] When will rh-postgresql94 SCL be updated in CentOS? In-Reply-To: <1500474888.6608.7.camel@nez.si> References: <1500474888.6608.7.camel@nez.si> Message-ID: <6f349714-e983-171d-ad01-e48a4e31d04f@redhat.com> On 07/19/2017 04:34 PM, Tadej Jane? wrote: > Hi! > > I have a fleet of CentOS and RHEL machines which use rh-postgresql94 > SCL. > > I saw that RHEL machines got an update to version 9.4.12-1.el7, but the > CentOS machines didn't. Hi Tadej, I've just started the builds, so they should get to the repos in couple of next days.. > Searching the CBS, I found that version 9.4.9-1.el7 is the latest one: > http://cbs.centos.org/koji/packageinfo?packageID=1695 > > Besides the obvious question stated in the subject, I would also kindly > ask for answers to: > 1. What is the current process of updates flowing from RHSCLs to Centos > SCLs? jstanek and myself are now the main "rebuilders", we have some tooling for taking the released sources and rebuilding in cbs.centos.org, but it's more ad-hoc action at this point. We're working on some better automation though. > 2. Where does softwarecollections.org fit into the picture? It currently serves as a catalog of collections, we don't rsync the packages any more, we just tell people what SCLs are available and how they can be enabled on RHEL and on CentOS, see for example: https://www.softwarecollections.org/en/scls/rhscl/rh-postgresql94/ Hope that answered your questions. Honza > Thanks and regards, > Tadej > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From hhorak at redhat.com Mon Jul 31 07:02:52 2017 From: hhorak at redhat.com (Honza Horak) Date: Mon, 31 Jul 2017 09:02:52 +0200 Subject: [scl.org] How to get listed on softwarecollections.org ? In-Reply-To: <94bbc645-76e3-bf4c-a4ab-8bfaf3bd73c2@cern.ch> References: <48d147fa-514f-fc89-b11a-faabeceab34d@cern.ch> <1724464066.17187840.1500302499464.JavaMail.zimbra@redhat.com> <94bbc645-76e3-bf4c-a4ab-8bfaf3bd73c2@cern.ch> Message-ID: On 07/26/2017 06:20 PM, Jarek Polok wrote: > On 07/17/2017 04:41 PM, Pavel Valena wrote: >> ----- Original Message ----- >>> From: "Jarek Polok" >>> To: sclorg at redhat.com >>> Sent: Thursday, July 13, 2017 6:40:00 PM >>> Subject: [scl.org] How to get listed on softwarecollections.org ? >>> >>> Dear all, >>> >>> I'm the "guilty" for following SCLo's: >>> >>> http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-git25/ >>> http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-git212/ >>> http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-httpd24more/ >>> http://mirror.centos.org/centos-7/7/sclo/x86_64/sclo/sclo-subversion19/ >> Hello, >> >> you can create your own user(Fedora FAS is required; top right 'Log in' should suffice) to maintain it yourself. Alternatively one of SCLo SIG members[1] with access and some spare cycles can add those entries under the `sclo` user, in case you wan't the SCLs to be represented as a part of SCLo SIG[2]. >> > > Thanks for info ! but it seems I could only add copr built collections > there ? but these listed above are cbs - built ? > > Honza: I think it would be better if these are added under 'sclo' user ? > Could you please do that ? Hm, having such 'sclo' user looks like good idea, so I created one and also pages for the four SCLs above: https://www.softwarecollections.org/en/scls/sclo/sclo-git25/ https://www.softwarecollections.org/en/scls/sclo/sclo-git212/ https://www.softwarecollections.org/en/scls/sclo/sclo-httpd24more/ https://www.softwarecollections.org/en/scls/sclo/sclo-subversion19/ (And I've added you as a collaborator, so you should be able to edit description, etc..) Does this look like a good way to go? Honza > Thanks ! > > Jarek > >> Please let us know. >> >> Regards, >> Pavel >> >> [1] https://wiki.centos.org/SpecialInterestGroup/SCLo >> [2] https://accounts.centos.org/group/members/sig-sclo >> >>> >>> (also available for centos 6) >>> >>> How could I get these listed on www.softwarecollections.org ? >>> >>> Best Regards >>> >>> Jarek >