From daniel.davis at nih.gov Mon Jul 22 19:36:51 2019 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Mon, 22 Jul 2019 19:36:51 +0000 Subject: [scl.org] rh-python36 and sqlite version Message-ID: I recently noticed that Django 2.2 requires sqlite 3.8.3 or better. I first tried the Fedora 26 SRPM, and then the Fedora 23 SRPM. I needed to make one tweak to the later: https://github.com/danizen/sqlite-centos7 Problem with my method, which I long ago honed when shipping a custom appliance, is that it overlays the sqlite already on the system. Better to build a custom sqlite that will go into /opt/rh/rh-python36/root - can someone re-educate me on how to do this. I know that it is in wikis, but I'm an old dog who mostly does application software in Python/Django these days, except when I need to drop down to a lower level to help the systems guys understand what they need to do. Only now that I've convinced them to use RHSCL so heavily, I need to know how to augment the SCLs as well. Dan Davis, Systems/Applications Architect (Contractor), Office of Computer and Communications Systems, National Library of Medicine, NIH -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.davis at nih.gov Mon Jul 22 19:52:36 2019 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Mon, 22 Jul 2019 19:52:36 +0000 Subject: [scl.org] rh-python36 and sqlite version In-Reply-To: References: Message-ID: I've downloaded rh-python36-python-pymongo-3.5.1-1.el7.src.rpm and I see the macros in there. I've also installed rh-python36-scldevel, and I see what it defines. It looks like what I would want to do is to pass the correct macros into rpmbuild some of the time. rpmbuild -bc --define "%scl_python rh-python36 %scl_prefix_python rh-python36-" The changes should only be in the spec. file, which I've already pulled out. Can someone confirm? From: sclorg-bounces at redhat.com On Behalf Of Davis, Daniel (NIH/NLM) [C] Sent: Monday, July 22, 2019 3:37 PM To: sclorg at redhat.com Subject: [scl.org] rh-python36 and sqlite version I recently noticed that Django 2.2 requires sqlite 3.8.3 or better. I first tried the Fedora 26 SRPM, and then the Fedora 23 SRPM. I needed to make one tweak to the later: https://github.com/danizen/sqlite-centos7 Problem with my method, which I long ago honed when shipping a custom appliance, is that it overlays the sqlite already on the system. Better to build a custom sqlite that will go into /opt/rh/rh-python36/root - can someone re-educate me on how to do this. I know that it is in wikis, but I'm an old dog who mostly does application software in Python/Django these days, except when I need to drop down to a lower level to help the systems guys understand what they need to do. Only now that I've convinced them to use RHSCL so heavily, I need to know how to augment the SCLs as well. Dan Davis, Systems/Applications Architect (Contractor), Office of Computer and Communications Systems, National Library of Medicine, NIH -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.davis at nih.gov Mon Jul 22 20:13:34 2019 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Mon, 22 Jul 2019 20:13:34 +0000 Subject: [scl.org] rh-python36 and sqlite version In-Reply-To: References: Message-ID: This pretty much describes what I might wish to do, but I'd prefer to find the latest documentation. Will look to the SCL SIG for latest documentation. https://access.redhat.com/documentation/en-us/red_hat_software_collections/1/html/packaging_guide/sect-extending_the_python27_and_python33_software_collections From: sclorg-bounces at redhat.com On Behalf Of Davis, Daniel (NIH/NLM) [C] Sent: Monday, July 22, 2019 3:53 PM To: sclorg at redhat.com Subject: Re: [scl.org] rh-python36 and sqlite version I've downloaded rh-python36-python-pymongo-3.5.1-1.el7.src.rpm and I see the macros in there. I've also installed rh-python36-scldevel, and I see what it defines. It looks like what I would want to do is to pass the correct macros into rpmbuild some of the time. rpmbuild -bc --define "%scl_python rh-python36 %scl_prefix_python rh-python36-" The changes should only be in the spec. file, which I've already pulled out. Can someone confirm? From: sclorg-bounces at redhat.com > On Behalf Of Davis, Daniel (NIH/NLM) [C] Sent: Monday, July 22, 2019 3:37 PM To: sclorg at redhat.com Subject: [scl.org] rh-python36 and sqlite version I recently noticed that Django 2.2 requires sqlite 3.8.3 or better. I first tried the Fedora 26 SRPM, and then the Fedora 23 SRPM. I needed to make one tweak to the later: https://github.com/danizen/sqlite-centos7 Problem with my method, which I long ago honed when shipping a custom appliance, is that it overlays the sqlite already on the system. Better to build a custom sqlite that will go into /opt/rh/rh-python36/root - can someone re-educate me on how to do this. I know that it is in wikis, but I'm an old dog who mostly does application software in Python/Django these days, except when I need to drop down to a lower level to help the systems guys understand what they need to do. Only now that I've convinced them to use RHSCL so heavily, I need to know how to augment the SCLs as well. Dan Davis, Systems/Applications Architect (Contractor), Office of Computer and Communications Systems, National Library of Medicine, NIH -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.davis at nih.gov Mon Jul 22 20:17:34 2019 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Mon, 22 Jul 2019 20:17:34 +0000 Subject: [scl.org] rh-python36 and sqlite version In-Reply-To: References: Message-ID: Finally got it. Please forgive my long emails: https://www.softwarecollections.org/en/docs/guide/#sect-Building_a_Software_Collection_Locally rpmbuild -ba python-pymongo.spec --define 'scl rh-python36' From: sclorg-bounces at redhat.com On Behalf Of Davis, Daniel (NIH/NLM) [C] Sent: Monday, July 22, 2019 4:14 PM To: sclorg at redhat.com Subject: Re: [scl.org] rh-python36 and sqlite version This pretty much describes what I might wish to do, but I'd prefer to find the latest documentation. Will look to the SCL SIG for latest documentation. https://access.redhat.com/documentation/en-us/red_hat_software_collections/1/html/packaging_guide/sect-extending_the_python27_and_python33_software_collections From: sclorg-bounces at redhat.com > On Behalf Of Davis, Daniel (NIH/NLM) [C] Sent: Monday, July 22, 2019 3:53 PM To: sclorg at redhat.com Subject: Re: [scl.org] rh-python36 and sqlite version I've downloaded rh-python36-python-pymongo-3.5.1-1.el7.src.rpm and I see the macros in there. I've also installed rh-python36-scldevel, and I see what it defines. It looks like what I would want to do is to pass the correct macros into rpmbuild some of the time. rpmbuild -bc --define "%scl_python rh-python36 %scl_prefix_python rh-python36-" The changes should only be in the spec. file, which I've already pulled out. Can someone confirm? From: sclorg-bounces at redhat.com > On Behalf Of Davis, Daniel (NIH/NLM) [C] Sent: Monday, July 22, 2019 3:37 PM To: sclorg at redhat.com Subject: [scl.org] rh-python36 and sqlite version I recently noticed that Django 2.2 requires sqlite 3.8.3 or better. I first tried the Fedora 26 SRPM, and then the Fedora 23 SRPM. I needed to make one tweak to the later: https://github.com/danizen/sqlite-centos7 Problem with my method, which I long ago honed when shipping a custom appliance, is that it overlays the sqlite already on the system. Better to build a custom sqlite that will go into /opt/rh/rh-python36/root - can someone re-educate me on how to do this. I know that it is in wikis, but I'm an old dog who mostly does application software in Python/Django these days, except when I need to drop down to a lower level to help the systems guys understand what they need to do. Only now that I've convinced them to use RHSCL so heavily, I need to know how to augment the SCLs as well. Dan Davis, Systems/Applications Architect (Contractor), Office of Computer and Communications Systems, National Library of Medicine, NIH -------------- next part -------------- An HTML attachment was scrubbed... URL: From Fedora at FamilleCollet.com Tue Jul 23 08:13:43 2019 From: Fedora at FamilleCollet.com (Remi Collet) Date: Tue, 23 Jul 2019 10:13:43 +0200 Subject: [scl.org] [SCLo SIG] new sclo-php*-php-pecl-redis5 packages available for testing Message-ID: <5e4b22ce-9fc7-9d7a-748d-79819b64895f@FamilleCollet.com> Yet another package available in centos-sclo-sclo-testing This extension provides an API for communicating with Redis servers. https://pecl.php.net/package/redis For rh-php72 (EL-7 only) * sclo-php72-php-pecl-redis5-5.0.1-1 For rh-php71 (EL-7 only) * sclo-php71-php-pecl-redis5-5.0.1-1 For rh-php70 * sclo-php70-php-pecl-redis5-5.0.1-1 Notices: - this extension is already available, as sclo-php7#-php-pecl-redis (version 3.1.6) ? and php7#-php-pecl-redis4 version 4.3.0. But as version 5 ? introduce some API changes, we choose to provide it as a ? separate package, giving users the choice to install v3, v4 or v5 - both versions cannot be installed simultaneously. - new collections (e.g. PHP 7.3, 7.4...) will only provide the v5 package. - upstream Changelog: https://pecl.php.net/package-changelog.php?package=redis Remi. P.S.1: https://wiki.centos.org/SpecialInterestGroup/SCLo P.S.2: you can follow activity on sclo-php* packages on https://blog.remirepo.net/post/2017/02/23/Additional-PHP-packages-for-RHSCL From jstanek at redhat.com Thu Jul 25 12:18:33 2019 From: jstanek at redhat.com (=?UTF-8?Q?Jan_Stan=c4=9bk?=) Date: Thu, 25 Jul 2019 14:18:33 +0200 Subject: [scl.org] Staging environment for softwarecollections.org now available Message-ID: <35e46fc8-4e63-f62b-6713-62a022459c43@redhat.com> I'm pleased to announce that a testing/staging environment for the softwarecollections.org web{site,app} is now available for testing at https://stage.softwarecollections.org. This is a part of a migration of the site to OpenShift hosting. The staging environment runs in OpenShift, and I would be glad for any reports of issues, especially the ones that are not manifesting on the production instance. If no major issues will be reported, the production instance will be migrated to OpenShift as well in a few weeks. Have a nice day! -- Jan Stan?k Associate Software Engineer Red Hat EMEA jstanek at redhat.com IM: jstanek -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From pvalena at redhat.com Thu Jul 25 12:47:51 2019 From: pvalena at redhat.com (Pavel Valena) Date: Thu, 25 Jul 2019 08:47:51 -0400 (EDT) Subject: [scl.org] Staging environment for softwarecollections.org now available In-Reply-To: <35e46fc8-4e63-f62b-6713-62a022459c43@redhat.com> References: <35e46fc8-4e63-f62b-6713-62a022459c43@redhat.com> Message-ID: <384917407.3050796.1564058871513.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Jan Stan?k" > To: sclorg at redhat.com > Sent: Thursday, July 25, 2019 2:18:33 PM > Subject: [scl.org] Staging environment for softwarecollections.org now available > > I'm pleased to announce that a testing/staging environment for the > softwarecollections.org web{site,app} is now available for testing > at https://stage.softwarecollections.org. > > This is a part of a migration of the site to OpenShift hosting. > The staging environment runs in OpenShift, and I would be glad for any > reports of issues, especially the ones that are not manifesting on the > production instance. If no major issues will be reported, the production > instance will be migrated to OpenShift as well in a few weeks. > There are no collections listed, right? https://stage.softwarecollections.org/en/scls/?search=ruby&policy=&repo=&order_by=-create_date&per_page=10 => empty Login went fine. Pavel > Have a nice day! > -- > Jan Stan?k > Associate Software Engineer > Red Hat EMEA > jstanek at redhat.com IM: jstanek From jstanek at redhat.com Thu Jul 25 14:07:49 2019 From: jstanek at redhat.com (=?UTF-8?Q?Jan_Stan=c4=9bk?=) Date: Thu, 25 Jul 2019 16:07:49 +0200 Subject: [scl.org] Staging environment for softwarecollections.org now available In-Reply-To: <384917407.3050796.1564058871513.JavaMail.zimbra@redhat.com> References: <35e46fc8-4e63-f62b-6713-62a022459c43@redhat.com> <384917407.3050796.1564058871513.JavaMail.zimbra@redhat.com> Message-ID: Yes, the collection database is empty (for now). I could clone the production one, but then I *will* be confused if I am on the production or staging instance. I would prefer that obviously testing collections would be added manually ? if I find some spare time, I will add a few myself. -- Jan Stan?k Associate Software Engineer Red Hat EMEA jstanek at redhat.com IM: jstanek -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From nstephan at redhat.com Tue Jul 9 21:08:07 2019 From: nstephan at redhat.com (Nate Stephany) Date: Tue, 09 Jul 2019 21:08:07 -0000 Subject: [scl.org] ubi7/php-72 image Message-ID: Hi, I was working with this image a couple of weeks ago and the size was around 600MB. I pulled it today to test my lab and all of the sudden it is over 2.6GB. Is there a reason why it grew that much? These are both based on the RHEL7 UBI and I wouldn't expect them to change that much between releases. The differences and version are below: [root at bastion 0 ~]# podman pull registry.redhat.io/ubi7/php-72:1-23.1560797457 Trying to pull registry.redhat.io/ubi7/php-72:1-23.1560797457...Getting image source signatures Copying blob 18f0f6de4601 done Copying blob db1d55616933 done Copying blob d09f4fbfc5a9 done Copying blob a598637d25fc done Copying blob c6e3f631f202 done Copying config 48da8ea31a done Writing manifest to image destination Storing signatures 48da8ea31a554bfd804268cbaa247586ed491c14a1ce24091b2c74b864f2aa33 [root at bastion 0 ~]# podman images REPOSITORY TAG IMAGE ID CREATED SIZE registry.redhat.io/ubi7/php-72 1-23.1560797457 48da8ea31a55 3 weeks ago 602 MB [root at bastion 0 ~]# podman pull registry.redhat.io/ubi7/php-72:1-23.1561731149 Trying to pull registry.redhat.io/ubi7/php-72:1-23.1561731149...Getting image source signatures Copying blob a4d9907173f4 done Copying blob dcc691b92f82 done Copying blob 9e004f5a47a5 done Copying blob 1d72f48b3d14 done Copying blob 506b188c0abe done Copying config f10275bf3c done Writing manifest to image destination Storing signatures f10275bf3caf611e2cf4337920e3ad336ccee7c7e3e5708ff674c8039e3cd2f0 [root at bastion 0 ~]# podman images REPOSITORY TAG IMAGE ID CREATED SIZE registry.redhat.io/ubi7/php-72 1-23.1561731149 f10275bf3caf 11 days ago 2.64 GB registry.redhat.io/ubi7/php-72 1-23.1560797457 48da8ea31a55 3 weeks ago 602 MB -- NATE STEPHANY OPENSHIFT SOLUTION ARCHITECT, GPTE, RHCA Red Hat North America nate at redhat.com T: +1-650-254-4067 M: +1-813-391-7178 TRIED. TESTED. TRUSTED. -------------- next part -------------- An HTML attachment was scrubbed... URL: