From Fedora at FamilleCollet.com Fri Nov 4 15:52:37 2016 From: Fedora at FamilleCollet.com (Remi Collet) Date: Fri, 4 Nov 2016 16:52:37 +0100 Subject: [scl.org] [SCLo SIG] new rh-php* packages available for testing Message-ID: <600e2841-fd06-134e-afda-73d54c08ffe0@FamilleCollet.com> Available in centos-sclo-rh-testing * rh-php56 collection have been updated to PHP 5.6.25 * rh-php70 new collection, provides PHP 7.0.10 These packages are the same that in RHSCL 2.3.0-beta. http://developers.redhat.com/blog/2016/10/20/red-hat-software-collections-2-3-beta/ Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo From Fedora at FamilleCollet.com Fri Nov 4 15:56:57 2016 From: Fedora at FamilleCollet.com (Remi Collet) Date: Fri, 4 Nov 2016 16:56:57 +0100 Subject: [scl.org] [SCLo SIG] new sclo-php56-php-pecl-mongodb packages available for testing Message-ID: <0f441ef1-e40e-c1aa-32d5-884e0d520ac6@FamilleCollet.com> Available in centos-sclo-sclo-testing * sclo-php56-php-pecl-mongodb This new extension allow to work with MondoDB server https://pecl.php.net/package/mongodb The old "mongo" extension is considered as deprecated, and will not be adpated for PHP 7. The new "mongodb" extension is recommended for new project, and is already compatible with PHP 5 and 7. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo _______________________________________________ CentOS-devel mailing list CentOS-devel at centos.org https://lists.centos.org/mailman/listinfo/centos-devel From Fedora at FamilleCollet.com Mon Nov 7 06:30:56 2016 From: Fedora at FamilleCollet.com (Remi Collet) Date: Mon, 7 Nov 2016 07:30:56 +0100 Subject: [scl.org] [SCLo SIG] new sclo-php70-* packages available for testing Message-ID: <4e0145b3-147b-5c18-681e-809366f29b2e@FamilleCollet.com> Available in centos-sclo-sclo-testing * sclo-php70-php-pecl-apcu * sclo-php70-php-pecl-apfd * sclo-php70-php-pecl-http * sclo-php70-php-pecl-mongodb * sclo-php70-php-pecl-propro * sclo-php70-php-pecl-raphf * sclo-php70-php-pecl-uploadprogress * sclo-php70-php-pecl-xdebug These packages provide additional extensions for the new rh-php70 collection available in centos-sclo-rh-testing More packages will come later, according to user requests. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo From zsvetlik at redhat.com Tue Nov 8 14:40:25 2016 From: zsvetlik at redhat.com (Zuzana Svetlikova) Date: Tue, 8 Nov 2016 09:40:25 -0500 (EST) Subject: [scl.org] Rolling release naming In-Reply-To: <1227255974.9879246.1478615172985.JavaMail.zimbra@redhat.com> Message-ID: <1745986991.9882816.1478616025510.JavaMail.zimbra@redhat.com> Currently, we chose the name of the collection by the version of the software we're packaging (rh-python35, sclo-php56 etc). I'd like to have a collection, that would be "rolling release" and for that reason I cannot use the version naming (nodejs releases major version every ~6 months). I could use something like sclo-nodejs-current, but that would result in terribly long package names that I'd like to avoid. Does anyone have any good ideas how to name such collection? Thanks Zuzka From briang at redhat.com Tue Nov 8 14:51:45 2016 From: briang at redhat.com (Brian Gollaher) Date: Tue, 8 Nov 2016 09:51:45 -0500 Subject: [scl.org] Rolling release naming In-Reply-To: <1745986991.9882816.1478616025510.JavaMail.zimbra@redhat.com> References: <1745986991.9882816.1478616025510.JavaMail.zimbra@redhat.com> Message-ID: First question is why do you need a rolling name? And will it meet the general naming requirements for RHSCL? Naming SCLs was a difficult process that took a few years with lots of customer involvement to get right. My understanding is that there are incompatibilities with node.js releases that may cause a yum update to break user apps. Is that correct? Brian On 11/08/2016 09:40 AM, Zuzana Svetlikova wrote: > Currently, we chose the name of the collection by the version > of the software we're packaging (rh-python35, sclo-php56 etc). > > I'd like to have a collection, that would be "rolling release" > and for that reason I cannot use the version naming (nodejs > releases major version every ~6 months). > I could use something like sclo-nodejs-current, but that would > result in terribly long package names that I'd like to avoid. > > Does anyone have any good ideas how to name such collection? > > Thanks > > Zuzka > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg -- Brian Gollaher Red Hat Platform Product Management Phone: 978 392-3173 Cell: 508 740-6549 briang at redhat.com From ppisar at redhat.com Tue Nov 8 15:00:44 2016 From: ppisar at redhat.com (Petr Pisar) Date: Tue, 8 Nov 2016 16:00:44 +0100 Subject: [scl.org] Rolling release naming In-Reply-To: <1745986991.9882816.1478616025510.JavaMail.zimbra@redhat.com> References: <1227255974.9879246.1478615172985.JavaMail.zimbra@redhat.com> <1745986991.9882816.1478616025510.JavaMail.zimbra@redhat.com> Message-ID: <20161108150043.GA2339@dhcp-0-146.brq.redhat.com> On Tue, Nov 08, 2016 at 09:40:25AM -0500, Zuzana Svetlikova wrote: > Currently, we chose the name of the collection by the version > of the software we're packaging (rh-python35, sclo-php56 etc). > > I'd like to have a collection, that would be "rolling release" > and for that reason I cannot use the version naming (nodejs > releases major version every ~6 months). > I could use something like sclo-nodejs-current, but that would > result in terribly long package names that I'd like to avoid. > > Does anyone have any good ideas how to name such collection? > Gentoo uses "9999" (or any long enough sequence of 9's) version for packages following latest upstream commit. I.e. sclo-nodejs-9999. But you are going to package proper releases with proper versions. Is your problem only that it's inconvinent for your to update the version string and reuild all packages? Will be the old package work with the new interpreter without rebuilding them? Maybe using no version string would the best one. Simply sclo-nodejs. Or if you insist on a version string what about sclo-nodejs-latest? (But that commits you into following upstream very closely. Nobody wants latest version that isn't latest.) -- Petr -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: not available URL: From gothicx at outlook.com Wed Nov 9 10:49:35 2016 From: gothicx at outlook.com (Marco Rodrigues) Date: Wed, 9 Nov 2016 10:49:35 +0000 Subject: [scl.org] Package request: freeradius 3.0.16 + PostgreSQL 9.5 support Message-ID: Hello everyone, I'm not sure if this is the right place to do this kind of request, but it would be good to have in RHSCL the latest version of freeradius with PostgreSQL 9.5 support as rpm. Thank you. Best regards. -- Marco Rodrigues -------------- next part -------------- An HTML attachment was scrubbed... URL: From norbert.jakubczak at gmail.com Wed Nov 2 23:46:19 2016 From: norbert.jakubczak at gmail.com (Norbi X) Date: Thu, 3 Nov 2016 00:46:19 +0100 Subject: [scl.org] php v7.X from SCL Message-ID: Hello Any idea when PHP v7.X will be available from softwarecollections.org project for RHEL6 ? -- -- Best Regards / Pozdrawiam Norbert Jakubczak -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbukatov at redhat.com Tue Nov 8 16:52:32 2016 From: mbukatov at redhat.com (Martin Bukatovic) Date: Tue, 8 Nov 2016 17:52:32 +0100 Subject: [scl.org] missing or deprecated description of rh-python35 Message-ID: <346754f0-041f-7615-23e8-ff8951ff2b81@redhat.com> Dear all, I'm not sure if this is the best place to discuss this issue, but I hope that I will be directed to better place if needed. I noticed that there are few differences between rh-python34 and rh-python35 software collections as listed on softwarecollections.org web site, see: * https://www.softwarecollections.org/en/scls/rhscl/rh-python34/ * https://www.softwarecollections.org/en/scls/rhscl/rh-python35/ Collection rh-python34: * is provided in both el6 and el7 versions * related copr projects (rhscl/rh-python34-el{6,7}) are linked * related collections are linked: Apache HTTP Server 2.4 While collection rh-python35: * only el7 version is provided * no link to copr builds * no related collections mentioned This seems to be caused by the fact that rh-python35 collection is build in cbs koji instead: https://cbs.centos.org/koji/packageinfo?packageID=2504 Would it make sense to add the following to rh-python35 page? * link to both el6 and el7 versions * link to koji build * link to related collections (if any) Thank you -- Martin Bukatovic USM QE team From Fedora at FamilleCollet.com Thu Nov 10 13:43:29 2016 From: Fedora at FamilleCollet.com (Remi Collet) Date: Thu, 10 Nov 2016 14:43:29 +0100 Subject: [scl.org] php v7.X from SCL In-Reply-To: References: Message-ID: <2a6ac570-6f29-9d05-5aea-63a4766b00bd@FamilleCollet.com> Le 03/11/2016 ? 00:46, Norbi X a ?crit : > Hello > > Any idea when PHP v7.X will be available from softwarecollections.org > project for RHEL6 ? I don't plan to build any new collection in softwarecollections.org. rh-php70 is part of RHSCL-2.3beta, so already available to RHEL-6 users. also available in centos-sclo-rh-testing for CentOS users. Remi. > -- > -- > Best Regards / Pozdrawiam > > Norbert Jakubczak > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From Fedora at FamilleCollet.com Sat Nov 12 08:37:42 2016 From: Fedora at FamilleCollet.com (Remi Collet) Date: Sat, 12 Nov 2016 09:37:42 +0100 Subject: [scl.org] [SCLo SIG] new sclo-php* packages available for testing Message-ID: <4024fa68-f81e-90f9-9039-d632c85e50ba@FamilleCollet.com> Yet another set of small packages available in centos-sclo-sclo-testing For rh-php56: * sclo-php56-php-pecl-lzf-1.6.5-1 * sclo-php56-php-pecl-selinux-0.4.1-1 * sclo-php56-php-pecl-uuid-1.0.4-1 * sclo-php56-php-pecl-xattr-1.3.0-1 For rh-php70: * sclo-php70-php-pecl-apcu-bc-1.0.3-1 * sclo-php70-php-pecl-lzf-1.6.5-1 * sclo-php70-php-pecl-selinux-0.4.1-1 * sclo-php70-php-pecl-uuid-1.0.4-1 * sclo-php70-php-pecl-xattr-1.3.0-1 More packages will come later, according to user requests. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo From hhorak at redhat.com Mon Nov 21 22:11:11 2016 From: hhorak at redhat.com (Honza Horak) Date: Mon, 21 Nov 2016 23:11:11 +0100 Subject: [scl.org] New SCL packages for CentOS available for testing Message-ID: RHSCL 2.3, which was released recently [1], includes several new collections. SRPMs were taken and rebuilt for CentOS users in cbs.centos.org by SCLo SIG group. The packages are now available in the testing repositories via e.g.: sudo yum install centos-release-scl sudo yum-config-manager --enable centos-sclo-rh-testing sudo yum install rh-mysql57 --nogpgcheck The following collections are now available for testing: devtoolset-6 rh-git29 rh-mysql57 rh-perl524 rh-php70 rh-redis32 They will be soon moved to mirrors, but in case there are some issues, let us know on sclorg at redhat.com. Please, mind, that these packages are not meant to be used on RHEL. On RHEL, you can acquire the packages following the documentation at [1]. We still haven't finished rebuilding of the following two new SCLs that are part of RHSCL 2.3: rh-thermostat16 rh-eclipse46 [1] https://access.redhat.com/documentation/en-US/Red_Hat_Software_Collections/2/html-single/2.3_Release_Notes/ Regards, Honza From lfarkas at lfarkas.org Tue Nov 22 09:53:26 2016 From: lfarkas at lfarkas.org (Farkas Levente) Date: Tue, 22 Nov 2016 10:53:26 +0100 Subject: [scl.org] [CentOS-devel] New SCL packages for CentOS available for testing In-Reply-To: References: Message-ID: On Mon, Nov 21, 2016 at 11:11 PM, Honza Horak wrote: > We still haven't finished rebuilding of the following two new SCLs that > are part of RHSCL 2.3: > > rh-thermostat16 > rh-eclipse46 > what is the estimated plan for these repos? thanks. -- Levente "Si vis pacem para bellum!" -------------- next part -------------- An HTML attachment was scrubbed... URL: From msuchy at redhat.com Wed Nov 23 16:10:30 2016 From: msuchy at redhat.com (=?UTF-8?Q?Miroslav_Such=c3=bd?=) Date: Wed, 23 Nov 2016 17:10:30 +0100 Subject: [scl.org] Planned outage of www.softwarecollections.org Message-ID: <083c901b-2371-3562-e7e4-8978f83a1715@redhat.com> There will be an outage starting at 2016-11-28 07:00 UTC, which will last approximately 1 hour. Reason for outage: Upgrade of underlying OS. Affected Services: www.softwarecollections.org -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys From nboldt at redhat.com Thu Nov 24 18:10:42 2016 From: nboldt at redhat.com (Nick Boldt) Date: Thu, 24 Nov 2016 13:10:42 -0500 Subject: [scl.org] ACTION REQUIRED: convention for labelling an RPM as "Technology Preview" within an SCL collection In-Reply-To: References: Message-ID: Please disregard this query. Martha has clarified via another channel that we don't need to do anything in the yum repo or the rpm's metadata, as long as release notes & marketing materials clearly identify the rpm as Technology Preview. Thanks & apologies for the spam, Nick On Thu, Nov 24, 2016 at 12:36 PM, Nick Boldt wrote: > In RHDEVDOCS-120 [1], I asked what we should do to label the new Red > Hat JBoss Developer Studio rpm package as a Technology Preview. > > This RPM is being released in concert with the upcoming RH SCL 2.3 > release, but will be available for install from a separate yum repo > such as this site [2]. > > Robert suggested I ask you for advice. > > [1] https://issues.jboss.org/browse/RHDEVDOCS-120?focusedCommentId=13327430&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13327430 > [2] https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/ > > Details in the above JIRA. > > I'm happy to make changes to the RPM metadata and the HTML page, but I > need to do *so before EOD today*, as we're already into code freeze > and I plan to build the final bits tonight & sign them tomorrow. > > Thanks in advance, > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com From Clem.Flory at Cerner.com Tue Nov 22 17:55:36 2016 From: Clem.Flory at Cerner.com (Flory,Clem) Date: Tue, 22 Nov 2016 17:55:36 -0000 Subject: [scl.org] Broken URLs Message-ID: <897743E8-B1A2-4006-8634-C1A65907AFF0@contoso.com> We use Software Collections in our build system, to install Python 2.7 on RHEL. This morning, our builds stopped working, due to the Python URL returning a 404 error - https://www.softwarecollections.org/en/scls/rhscl/python27/epel-6-x86_64/download/rhscl-python27-epel-6-x86_64.noarch.rpm. Is there any way to get this URL working again? We are using Chef Enterprise, with the poise-python cookbook, which uses Software Collections to install Python. Let me know if you need any more information. Thanks, Clem Flory Software Architect, Lights On Network clem.flory at cerner.com | www.cerner.com CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. -------------- next part -------------- An HTML attachment was scrubbed... URL: From tobi at tobipage.de Wed Nov 16 08:19:47 2016 From: tobi at tobipage.de (Tobias Bergmann) Date: Wed, 16 Nov 2016 08:19:47 -0000 Subject: [scl.org] Support and update life cycle Message-ID: <3e98b2c0-7390-3d80-7769-31f082f0ec1f@tobipage.de> Hi, I am using redhat el because I know there will be updates for ~10 years instead of just ~5 years with other distributions. That makes it much easier to handle 50 and more servers over the years. My main issue with redhat el is that the php is already too old when you install a fresh newest redhat el 7. There are a lot of repositories that make it easy to install a newer php on redhat el 7 and with sclorg I think I found a clean and relyable one. But there still is a concern. If I install a newer php with sclorg repository now will there still be security updates in 10 years? It doesn't make sense to use a linux distributions because of 10 years of updates when the php doesn't get updates as long. The system won't be safe with an old php. So the question is: Will there be updates of sclorg packages as long as the main version of redhat el gets updates? Best Regards Tobi