From Fedora at FamilleCollet.com Fri Feb 3 08:39:50 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Fri, 3 Feb 2017 09:39:50 +0100 Subject: [scl.org] [SCLo SIG] new sclo-php* packages available for testing Message-ID: <35889955-09d5-9bec-3d9e-f886747d3554@FamilleCollet.com> Yet another package available in centos-sclo-sclo-testing "Provides a wrapper to the ImageMagick library." A stable version was just released with PHP 5 and 7 compatibility. For rh-php56 (updated from 3.3.0): * sclo-php56-php-pecl-imagick-3.4.3-1 For rh-php70 (new package): * sclo-php70-php-pecl-imagick-3.4.3-1 Notice: this extension uses system ImageMagick 6.7.8.9 (EL-7) or 6.7.2.7 (EL-6), so only feature available in these library versions will be available in the PHP extension. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo From cls at seawood.org Thu Feb 9 03:21:15 2017 From: cls at seawood.org (cls) Date: Wed, 8 Feb 2017 19:21:15 -0800 Subject: [scl.org] devtoolset toolchain shared libs (libstdc++,libgcc,etc) Message-ID: <2bffb8eb-e28f-3fdb-64fa-514c0bceeb94@seawood.org> Hi, It appears as though the devtoolset toolchain rpms do not come with a copy of the libstdc++ shared library nor a handful of other shared libraries usually provided by gcc. Comparing the SCL and non-SCL gcc.spec files, it's clear that someone deliberately removed those shared libs. Why is that? I didn't see any mention of this in the mailing list archives. I'm seeing a weird segfault during the destruction of a std::string derived-object that I do not see with the system compiler (gcc 4.8.5). I thought that it may have been a compiler error but then while debugging, I noticed that the c++ programs & libraries are linked against the system version of libstdc++.so.6 instead of the devtoolset-6 version. That seems like that could cause major problems. I'm using the pre-built devtoolset-6 from http://vault.centos.org/7.2.1511/sclo/x86_64/rh/devtoolset-6/ on CentOS 7.2.1511. I modified the boost package to build as part of the collection since it is highly dependent upon the toolchain. You can see the runtime dependency upon the system library below as well as the ld script that causes the system library to get referenced at link time. [build at cls-scelbuild-72 tmp]$ scl enable devtoolset-6 'ldd /opt/rh/devtoolset-6/root/usr/lib64/libboost_filesystem.so.1.53.0' linux-vdso.so.1 => (0x00007ffecfbbe000) libboost_system.so.1.53.0 => /opt/rh/devtoolset-6/root/usr/lib64/libboost_system.so.1.53.0 (0x00007f52ac67d000) libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f52ac365000) libm.so.6 => /lib64/libm.so.6 (0x00007f52ac063000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f52abe4d000) libc.so.6 => /lib64/libc.so.6 (0x00007f52aba8a000) /lib64/ld-linux-x86-64.so.2 (0x00007f52acab6000) [build at cls-scelbuild-72 tmp]$ find /opt/rh/devtoolset-6/root/ -name 'libstdc++*.so*' | grep -v gdb find: ?/opt/rh/devtoolset-6/root/root?: Permission denied /opt/rh/devtoolset-6/root/usr/lib/gcc/x86_64-redhat-linux/6.2.1/libstdc++.so /opt/rh/devtoolset-6/root/usr/lib/gcc/x86_64-redhat-linux/6.2.1/32/libstdc++.so [build at cls-scelbuild-72 tmp]$ cat /opt/rh/devtoolset-6/root/usr/lib/gcc/x86_64-redhat-linux/6.2.1/libstdc++.so /* GNU ld script Use the shared library, but some functions are only in the static library, so try that secondarily. */ OUTPUT_FORMAT(elf64-x86-64) INPUT ( /usr/lib64/libstdc++.so.6 -lstdc++_nonshared ) [build at cls-scelbuild-72 tmp]$ - cls From davejohansen at gmail.com Thu Feb 9 04:02:50 2017 From: davejohansen at gmail.com (Dave Johansen) Date: Wed, 8 Feb 2017 21:02:50 -0700 Subject: [scl.org] devtoolset toolchain shared libs (libstdc++, libgcc, etc) In-Reply-To: <2bffb8eb-e28f-3fdb-64fa-514c0bceeb94@seawood.org> References: <2bffb8eb-e28f-3fdb-64fa-514c0bceeb94@seawood.org> Message-ID: On Wed, Feb 8, 2017 at 8:21 PM, cls wrote: > Hi, > > It appears as though the devtoolset toolchain rpms do not come with a copy > of the libstdc++ shared library nor a handful of other shared libraries > usually provided by gcc. Comparing the SCL and non-SCL gcc.spec files, it's > clear that someone deliberately removed those shared libs. Why is that? I > didn't see any mention of this in the mailing list archives. > > I'm seeing a weird segfault during the destruction of a std::string > derived-object that I do not see with the system compiler (gcc 4.8.5). I > thought that it may have been a compiler error but then while debugging, I > noticed that the c++ programs & libraries are linked against the system > version of libstdc++.so.6 instead of the devtoolset-6 version. That seems > like that could cause major problems. > > I'm using the pre-built devtoolset-6 from http://vault.centos.org/7.2.15 > 11/sclo/x86_64/rh/devtoolset-6/ on CentOS 7.2.1511. I modified the boost > package to build as part of the collection since it is highly dependent > upon the toolchain. You can see the runtime dependency upon the system > library below as well as the ld script that causes the system library to > get referenced at link time. > > [build at cls-scelbuild-72 tmp]$ scl enable devtoolset-6 'ldd > /opt/rh/devtoolset-6/root/usr/lib64/libboost_filesystem.so.1.53.0' > linux-vdso.so.1 => (0x00007ffecfbbe000) > libboost_system.so.1.53.0 => /opt/rh/devtoolset-6/root/usr/ > lib64/libboost_system.so.1.53.0 (0x00007f52ac67d000) > libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f52ac365000) > libm.so.6 => /lib64/libm.so.6 (0x00007f52ac063000) > libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f52abe4d000) > libc.so.6 => /lib64/libc.so.6 (0x00007f52aba8a000) > /lib64/ld-linux-x86-64.so.2 (0x00007f52acab6000) > [build at cls-scelbuild-72 tmp]$ find /opt/rh/devtoolset-6/root/ -name > 'libstdc++*.so*' | grep -v gdb > find: ?/opt/rh/devtoolset-6/root/root?: Permission denied > /opt/rh/devtoolset-6/root/usr/lib/gcc/x86_64-redhat-linux/6. > 2.1/libstdc++.so > /opt/rh/devtoolset-6/root/usr/lib/gcc/x86_64-redhat-linux/6. > 2.1/32/libstdc++.so > [build at cls-scelbuild-72 tmp]$ cat /opt/rh/devtoolset-6/root/usr/ > lib/gcc/x86_64-redhat-linux/6.2.1/libstdc++.so > /* GNU ld script > Use the shared library, but some functions are only in > the static library, so try that secondarily. */ > OUTPUT_FORMAT(elf64-x86-64) > INPUT ( /usr/lib64/libstdc++.so.6 -lstdc++_nonshared ) > [build at cls-scelbuild-72 tmp]$ > One of the main selling points of the devtoolset is that it uses the libraries from the system and statically links in features that aren't available. That allows the binaries built with it to be used on other machines without needing to install devtoolset or any other additional dependencies. -------------- next part -------------- An HTML attachment was scrubbed... URL: From skanan at nutanix.com Fri Feb 10 15:20:04 2017 From: skanan at nutanix.com (Nick Kanakakorn) Date: Fri, 10 Feb 2017 15:20:04 +0000 Subject: [scl.org] your cert expired. Message-ID: <3B0DBC17-4506-4460-ACF8-6D628E32CC71@nutanix.com> Hi, Your cert using let?s encrypt expired. This caused yum install to fail. Could you renew your cert please ? wget https://www.softwarecollections.org/repos/rhscl/devtoolset-3/epel-6-x86_64/repodata/repomd.xml--2017-06-17 19:02:14-- https://www.softwarecollections.org/repos/rhscl/devtoolset-3/epel-6-x86_64/repodata/repomd.xml Resolving www.softwarecollections.org... 209.132.179.161 Connecting to www.softwarecollections.org|209.132.179.161|:443... connected. ERROR: cannot verify www.softwarecollections.org?s certificate, issued by ?/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3?: Issued certificate has expired. To connect to www.softwarecollections.org insecurely, use ?--no-check-certificate?. Thanks -Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From hhorak at redhat.com Mon Feb 13 15:48:19 2017 From: hhorak at redhat.com (Honza Horak) Date: Mon, 13 Feb 2017 16:48:19 +0100 Subject: [scl.org] your cert expired. In-Reply-To: <3B0DBC17-4506-4460-ACF8-6D628E32CC71@nutanix.com> References: <3B0DBC17-4506-4460-ACF8-6D628E32CC71@nutanix.com> Message-ID: Hi Nick, I see 04/29/2017 to be the expire date for the current cert. Your wget also works for me. In any case, getting the RPM files from softwarecollections.org (your link) for devtoolset-3 is the obsolete way, please, install the packages using the directions available at https://www.softwarecollections.org/en/scls/rhscl/devtoolset-3/ Honza On 02/10/2017 04:20 PM, Nick Kanakakorn wrote: > Hi, > > Your cert using let?s encrypt expired. This caused yum install to fail. > Could you renew your cert please ? > > wget > https://www.softwarecollections.org/repos/rhscl/devtoolset-3/epel-6-x86_64/repodata/repomd.xml--2017-06-17 > 19:02:14-- > https://www.softwarecollections.org/repos/rhscl/devtoolset-3/epel-6-x86_64/repodata/repomd.xml > Resolving www.softwarecollections.org... 209.132.179.161 > Connecting to www.softwarecollections.org|209.132.179.161|:443... connected. > ERROR: cannot verify www.softwarecollections.org?s certificate, issued > by ?/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3?: > Issued certificate has expired. > To connect to www.softwarecollections.org insecurely, use > ?--no-check-certificate?. > > Thanks > -Nick > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From dominic at cleal.org Mon Feb 13 15:46:22 2017 From: dominic at cleal.org (Dominic Cleal) Date: Mon, 13 Feb 2017 15:46:22 +0000 Subject: [scl.org] your cert expired. In-Reply-To: <3B0DBC17-4506-4460-ACF8-6D628E32CC71@nutanix.com> References: <3B0DBC17-4506-4460-ACF8-6D628E32CC71@nutanix.com> Message-ID: <7dac3b4f-e9f1-cd3f-d3b8-9d3a0a503fc1@cleal.org> On 10/02/17 15:20, Nick Kanakakorn wrote: > Your cert using let?s encrypt expired. This caused yum install to fail. > Could you renew your cert please ? > > wget > https://www.softwarecollections.org/repos/rhscl/devtoolset-3/epel-6-x86_64/repodata/repomd.xml--2017-06-17 > 19:02:14-- > https://www.softwarecollections.org/repos/rhscl/devtoolset-3/epel-6-x86_64/repodata/repomd.xml > Resolving www.softwarecollections.org... 209.132.179.161 > Connecting to www.softwarecollections.org|209.132.179.161|:443... connected. > ERROR: cannot verify www.softwarecollections.org?s certificate, issued > by ?/C=US/O=Let's Encrypt/CN=Let's Encrypt Authority X3?: > Issued certificate has expired. What is the supposed expiry date? From my location it's valid from 2017-01-29 to 2017-04-29, suggesting that perhaps your clock is incorrect. -- Dominic Cleal dominic at cleal.org From Fedora at FamilleCollet.com Tue Feb 14 11:07:44 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Tue, 14 Feb 2017 12:07:44 +0100 Subject: [scl.org] [SCLo SIG] updated sclo-php70-pecl-apcu packages available for testing In-Reply-To: <4d33a2fd-5fc4-4308-b869-64d3ec5e9ad7@FamilleCollet.com> References: <4d33a2fd-5fc4-4308-b869-64d3ec5e9ad7@FamilleCollet.com> Message-ID: Le 20/01/2017 ? 13:41, Remi Collet a ?crit : > For rh-php70: > > * sclo-php70-php-pecl-apcu-5.1.8-1.el6 > Pushed to stable From Fedora at FamilleCollet.com Tue Feb 14 11:09:57 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Tue, 14 Feb 2017 12:09:57 +0100 Subject: [scl.org] [SCLo SIG] new sclo-php* packages available for testing Message-ID: Yet another package available in centos-sclo-sclo-testing "PHP extension for interfacing with Redis" A stable version was recently released with PHP 5 and 7 compatibility. For rh-php56 * sclo-php56-php-pecl-redis-3.1.1-1 For rh-php70 * sclo-php70-php-pecl-redis-3.1.1-1 This extension is recommended by ownCloud for distributed cache. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo _______________________________________________ SCLorg mailing list SCLorg at redhat.com https://www.redhat.com/mailman/listinfo/sclorg From Fedora at FamilleCollet.com Wed Feb 15 16:09:19 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Wed, 15 Feb 2017 17:09:19 +0100 Subject: [scl.org] [SCLo SIG] new sclo-php* packages available for testing Message-ID: Additional packages available in centos-sclo-sclo-testing "PHP extension for interfacing with memcached" https://pecl.php.net/package/memcached "PHP extension for interfacing with MessagePack" https://pecl.php.net/package/msgpack For rh-php70 * sclo-php70-php-pecl-msgpack-2.0.2-1 * sclo-php70-php-pecl-memcached-3.0.2-1 (EL-7 only) Notice, from memcached upstream documentation: "Note that support for libmemcached 0.x series has been discontinued and the oldest actively tested version is 1.0.2. It is highly recommended to use version 1.0.18 of libmemcached." So not available for EL-6 (libmemcached 0.31) EL-7 have libmemcached 1.0.16 which is not really perfect. Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo From Fedora at FamilleCollet.com Mon Feb 20 16:29:11 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Mon, 20 Feb 2017 17:29:11 +0100 Subject: [scl.org] [SCLo SIG] new sclo-php* packages available for testing In-Reply-To: <35889955-09d5-9bec-3d9e-f886747d3554@FamilleCollet.com> References: <35889955-09d5-9bec-3d9e-f886747d3554@FamilleCollet.com> Message-ID: Le 03/02/2017 ? 09:39, Remi Collet a ?crit : > Yet another package available in centos-sclo-sclo-testing > > "Provides a wrapper to the ImageMagick library." > > A stable version was just released with PHP 5 and 7 compatibility. > > > For rh-php56 (updated from 3.3.0): > > * sclo-php56-php-pecl-imagick-3.4.3-1 > > For rh-php70 (new package): > > * sclo-php70-php-pecl-imagick-3.4.3-1 Pushed to stable. From jortel at redhat.com Mon Feb 27 21:09:33 2017 From: jortel at redhat.com (Jeff Ortel) Date: Mon, 27 Feb 2017 15:09:33 -0600 Subject: [scl.org] mongo26 Message-ID: <08e32aad-069d-c5b7-06b5-5b6c677b813b@redhat.com> Hello, I am with Satellite engineering and trying to determine if mongoDB 2.6 is available through SCL for EL6. Looking at the web[1], it appears it's available from Copr builds but not from the YUM repositories listed on that page. Also, I looked that the RH (stage) CDN and only find mongodb24-* in rhscl/ for both EL6 & 7. Can you help me resolve this? Thanks, Jeff [1] https://www.softwarecollections.org/en/scls/rhscl/rh-mongodb26/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 847 bytes Desc: OpenPGP digital signature URL: From mskalick at redhat.com Tue Feb 28 07:55:01 2017 From: mskalick at redhat.com (Marek =?ISO-8859-1?Q?Skalick=FD?=) Date: Tue, 28 Feb 2017 08:55:01 +0100 Subject: [scl.org] mongo26 In-Reply-To: <08e32aad-069d-c5b7-06b5-5b6c677b813b@redhat.com> References: <08e32aad-069d-c5b7-06b5-5b6c677b813b@redhat.com> Message-ID: <1488268501.2930.6.camel@redhat.com> Jeff Ortel p??e v Po 27. 02. 2017 v 15:09 -0600: > Hello, > > I am with Satellite engineering and trying to determine if mongoDB > 2.6 is available through SCL for EL6. > Looking at the web[1], it appears it's available from Copr builds but > not from the YUM repositories listed on > that page.??Also, I looked that the RH (stage) CDN and only find > mongodb24-* in rhscl/ for both EL6 & 7.??Can > you help me resolve this? Hi, it is available. It should be in RHEL and CentOS yum repositories too. The naming was changed, so collection name is rh-mongodb26 ("rh-" prefix was added). Does this help? Marek > > Thanks, > > Jeff > > > > [1] https://www.softwarecollections.org/en/scls/rhscl/rh-mongodb26/ > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg From jortel at redhat.com Tue Feb 28 13:56:26 2017 From: jortel at redhat.com (Jeff Ortel) Date: Tue, 28 Feb 2017 07:56:26 -0600 Subject: [scl.org] mongo26 In-Reply-To: <1488268501.2930.6.camel@redhat.com> References: <08e32aad-069d-c5b7-06b5-5b6c677b813b@redhat.com> <1488268501.2930.6.camel@redhat.com> Message-ID: <44e9f6f8-ddb5-9a02-5079-43884f66f49f@redhat.com> On 02/28/2017 01:55 AM, Marek Skalick? wrote: > Jeff Ortel p??e v Po 27. 02. 2017 v 15:09 -0600: >> Hello, >> >> I am with Satellite engineering and trying to determine if mongoDB >> 2.6 is available through SCL for EL6. >> Looking at the web[1], it appears it's available from Copr builds but >> not from the YUM repositories listed on >> that page. Also, I looked that the RH (stage) CDN and only find >> mongodb24-* in rhscl/ for both EL6 & 7. Can >> you help me resolve this? > > Hi, > it is available. It should be in RHEL and CentOS yum repositories too. > > The naming was changed, so collection name is rh-mongodb26 ("rh-" > prefix was added). Does this help? Yes. Found it on the CDN. The naming fooled me. Thanks! > > Marek > >> >> Thanks, >> >> Jeff >> >> >> >> [1] https://www.softwarecollections.org/en/scls/rhscl/rh-mongodb26/ >> >> _______________________________________________ >> SCLorg mailing list >> SCLorg at redhat.com >> https://www.redhat.com/mailman/listinfo/sclorg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 847 bytes Desc: OpenPGP digital signature URL: From jortel at redhat.com Tue Feb 28 14:05:46 2017 From: jortel at redhat.com (Jeff Ortel) Date: Tue, 28 Feb 2017 08:05:46 -0600 Subject: [scl.org] mongo26 In-Reply-To: <1488268501.2930.6.camel@redhat.com> References: <08e32aad-069d-c5b7-06b5-5b6c677b813b@redhat.com> <1488268501.2930.6.camel@redhat.com> Message-ID: <7e6512b0-176f-63c8-e30f-1a9867e0520a@redhat.com> On 02/28/2017 01:55 AM, Marek Skalick? wrote: > Jeff Ortel p??e v Po 27. 02. 2017 v 15:09 -0600: >> Hello, >> >> I am with Satellite engineering and trying to determine if mongoDB >> 2.6 is available through SCL for EL6. >> Looking at the web[1], it appears it's available from Copr builds but >> not from the YUM repositories listed on >> that page. Also, I looked that the RH (stage) CDN and only find >> mongodb24-* in rhscl/ for both EL6 & 7. Can >> you help me resolve this? > > Hi, > it is available. It should be in RHEL and CentOS yum repositories too. > > The naming was changed, so collection name is rh-mongodb26 ("rh-" > prefix was added). Does this help? Yes. Found it on the CDN. The naming fooled me. Thanks! > > Marek > >> >> Thanks, >> >> Jeff >> >> >> >> [1] https://www.softwarecollections.org/en/scls/rhscl/rh-mongodb26/ >> >> _______________________________________________ >> SCLorg mailing list >> SCLorg at redhat.com >> https://www.redhat.com/mailman/listinfo/sclorg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 847 bytes Desc: OpenPGP digital signature URL: From jortel at redhat.com Tue Feb 28 14:35:54 2017 From: jortel at redhat.com (Jeff Ortel) Date: Tue, 28 Feb 2017 08:35:54 -0600 Subject: [scl.org] mongo26 In-Reply-To: <1488268501.2930.6.camel@redhat.com> References: <08e32aad-069d-c5b7-06b5-5b6c677b813b@redhat.com> <1488268501.2930.6.camel@redhat.com> Message-ID: <87d9e34d-d387-ce77-172c-58bb8602c10c@redhat.com> On 02/28/2017 01:55 AM, Marek Skalick? wrote: > Jeff Ortel p??e v Po 27. 02. 2017 v 15:09 -0600: >> Hello, >> >> I am with Satellite engineering and trying to determine if mongoDB >> 2.6 is available through SCL for EL6. >> Looking at the web[1], it appears it's available from Copr builds but >> not from the YUM repositories listed on >> that page. Also, I looked that the RH (stage) CDN and only find >> mongodb24-* in rhscl/ for both EL6 & 7. Can >> you help me resolve this? > > Hi, > it is available. It should be in RHEL and CentOS yum repositories too. > > The naming was changed, so collection name is rh-mongodb26 ("rh-" > prefix was added). Does this help? Yes. Found it on the CDN. The name change fooled me. Thanks! > > Marek > >> >> Thanks, >> >> Jeff >> >> >> >> [1] https://www.softwarecollections.org/en/scls/rhscl/rh-mongodb26/ >> >> _______________________________________________ >> SCLorg mailing list >> SCLorg at redhat.com >> https://www.redhat.com/mailman/listinfo/sclorg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 847 bytes Desc: OpenPGP digital signature URL: From aawardhan at gmail.com Tue Feb 28 05:28:18 2017 From: aawardhan at gmail.com (Aawardhan Logandan) Date: Tue, 28 Feb 2017 10:58:18 +0530 Subject: [scl.org] How different is rh-postgresql94 from community Postgres 94? Message-ID: If my product is certified to run in Postgres 9.5 (tested in Cent OS), can I claim that it will work in rh-postgresql95? -------------- next part -------------- An HTML attachment was scrubbed... URL: