From cfoskin at redhat.com Tue Nov 21 09:26:56 2017 From: cfoskin at redhat.com (Colum Foskin) Date: Tue, 21 Nov 2017 09:26:56 +0000 Subject: [scl.org] Upgrading mysql-container image 5.6 -> 5.7 Message-ID: Hi, I am looking for advice on what would be the best approach to upgrading an existing sclorg 5.6 mysql pod on openshift to the 5.7 image provided. I have built the 5.7 image and updated the deployment config to use this image but i am seeing a lot of errors in the logs which seem to be due to incompatible data with the newer version and it recommends to run the mysql_binary to resolve which I dont think is practical when trying to upgrade a running pod. Any advise or help would be appreciated on how this should be approached using the sclorg images. Thanks! Colum Foskin. -- Colum Foskin ASSOCIATE SOFTWARE ENGINEER Red Hat Communications House, Cork Road Waterford City, Ireland X91NY33 cfoskin at redhat.com IM: cfoskin -------------- next part -------------- An HTML attachment was scrubbed... URL: From jiri.novak at ghorland.net Wed Nov 22 13:45:55 2017 From: jiri.novak at ghorland.net (Jiri Novak) Date: Wed, 22 Nov 2017 14:45:55 +0100 Subject: [scl.org] rh-python36-build alternative in rhel Message-ID: Hello, I'm currently trying to port python app to use rh-python36 SCL (built using mock+rpmbuild), I've managed to make it build correctly in the scl paths (and using python3 for the packages that need it during build) if I install rh-python36-build from centos to the mock root. Is there a way to do this with rhel packages too? The issue is that without it, %{scl} in specfile is not populated, with it, it's properly set to rh-python36. Should I pass the value in different manner than in centos? or what might I be doing wrong? for reference, scl-utils-build and rh-python36-scldevel are installed, but that's not enough. Thanks, Gh. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 866 bytes Desc: OpenPGP digital signature URL: From stefanrin at gmail.com Wed Nov 22 13:49:43 2017 From: stefanrin at gmail.com (Stefan Ring) Date: Wed, 22 Nov 2017 14:49:43 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: Message-ID: On Wed, Nov 22, 2017 at 2:45 PM, Jiri Novak wrote: > Hello, > > I'm currently trying to port python app to use rh-python36 SCL (built > using mock+rpmbuild), I've managed to make it build correctly in the scl > paths (and using python3 for the packages that need it during build) if > I install rh-python36-build from centos to the mock root. > Is there a way to do this with rhel packages too? Do what? > The issue is that > without it, Without what? > %{scl} in specfile is not populated, with it, it's properly > set to rh-python36. Should I pass the value in different manner than in > centos? or what might I be doing wrong? I have no idea what you are trying to achieve. From mskalick at redhat.com Wed Nov 22 14:27:30 2017 From: mskalick at redhat.com (Marek =?ISO-8859-1?Q?Skalick=FD?=) Date: Wed, 22 Nov 2017 15:27:30 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: Message-ID: <1511360850.9347.8.camel@redhat.com> Jiri Novak p??e v St 22. 11. 2017 v 14:45 +0100: > Hello, > > I'm currently trying to port python app to use rh-python36 SCL (built > using mock+rpmbuild), I've managed to make it build correctly in the > scl > paths (and using python3 for the packages that need it during build) > if > I install rh-python36-build from centos to the mock root. > Is there a way to do this with rhel packages too? The issue is that > without it, %{scl} in specfile is not populated, with it, it's > properly > set to rh-python36. Should I pass the value in different manner than > in > centos? or what might I be doing wrong? > You have to create new collection which depends on rh-python36 (-build subpackage of your SCL will require rh-python36-scldevel) Take a look at SCL Packaging guidelines: https://www.softwarecollections.org/en/docs/guide/#sect-Extending_the_p ython27_and_rh-python35_Software_Collections > for reference, scl-utils-build and rh-python36-scldevel are > installed, > but that's not enough. > > Thanks, > Gh. > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg From jiri.novak at ghorland.net Wed Nov 22 15:07:33 2017 From: jiri.novak at ghorland.net (Jiri Novak) Date: Wed, 22 Nov 2017 16:07:33 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: Message-ID: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> Hi, the issue is that I don't have the rh-python36-build in rhel (satellite) and I didn't manage to find it on rhel site, so I assume it doesn't exist and should be replaced somehow. It doesn't sound right to install it via wget && rpm -i from centos. Or am I wrong and it is somewhere? if yes, which repo? Dependence only on rh-python36 is not enough as it is built for python 2.7 instead, the scl related macros are not working without rh-python36-build Thanks, Gh. Stefan Ring wrote: > On Wed, Nov 22, 2017 at 2:45 PM, Jiri Novak wrote: >> Hello, >> >> I'm currently trying to port python app to use rh-python36 SCL (built >> using mock+rpmbuild), I've managed to make it build correctly in the scl >> paths (and using python3 for the packages that need it during build) if >> I install rh-python36-build from centos to the mock root. >> Is there a way to do this with rhel packages too? > Do what? > >> The issue is that >> without it, > Without what? > >> %{scl} in specfile is not populated, with it, it's properly >> set to rh-python36. Should I pass the value in different manner than in >> centos? or what might I be doing wrong? > I have no idea what you are trying to achieve. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 866 bytes Desc: OpenPGP digital signature URL: From pvalena at redhat.com Wed Nov 22 15:20:09 2017 From: pvalena at redhat.com (Pavel Valena) Date: Wed, 22 Nov 2017 10:20:09 -0500 (EST) Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> Message-ID: <42180558.21814059.1511364009422.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Jiri Novak" > To: sclorg at redhat.com > Sent: Wednesday, November 22, 2017 4:07:33 PM > Subject: Re: [scl.org] rh-python36-build alternative in rhel > > Hi, > > the issue is that I don't have the rh-python36-build in rhel (satellite) > and I didn't manage to find it on rhel site, so I assume it doesn't > exist and should be replaced somehow. > It doesn't sound right to install it via wget && rpm -i from centos. > Or am I wrong and it is somewhere? if yes, which repo? I'm not sure about the repo, as AFAIR it's not shipped, so probably some internal compose only. In the meantime, you can check it here: https://brewweb.engineering.redhat.com/brew/rpminfo?rpmID=4714375 Pavel > > Dependence only on rh-python36 is not enough as it is built for python > 2.7 instead, the scl related macros are not working without > rh-python36-build > > Thanks, > Gh. > > > Stefan Ring wrote: > > On Wed, Nov 22, 2017 at 2:45 PM, Jiri Novak > > wrote: > >> Hello, > >> > >> I'm currently trying to port python app to use rh-python36 SCL (built > >> using mock+rpmbuild), I've managed to make it build correctly in the scl > >> paths (and using python3 for the packages that need it during build) if > >> I install rh-python36-build from centos to the mock root. > >> Is there a way to do this with rhel packages too? > > Do what? > > > >> The issue is that > >> without it, > > Without what? > > > >> %{scl} in specfile is not populated, with it, it's properly > >> set to rh-python36. Should I pass the value in different manner than in > >> centos? or what might I be doing wrong? > > I have no idea what you are trying to achieve. > From pvalena at redhat.com Wed Nov 22 15:23:13 2017 From: pvalena at redhat.com (Pavel Valena) Date: Wed, 22 Nov 2017 10:23:13 -0500 (EST) Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: <42180558.21814059.1511364009422.JavaMail.zimbra@redhat.com> References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <42180558.21814059.1511364009422.JavaMail.zimbra@redhat.com> Message-ID: <1909596823.21814318.1511364193623.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Pavel Valena" > To: "Jiri Novak" > Cc: sclorg at redhat.com > Sent: Wednesday, November 22, 2017 4:20:09 PM > Subject: Re: [scl.org] rh-python36-build alternative in rhel > > ----- Original Message ----- > > From: "Jiri Novak" > > To: sclorg at redhat.com > > Sent: Wednesday, November 22, 2017 4:07:33 PM > > Subject: Re: [scl.org] rh-python36-build alternative in rhel > > > > Hi, > > > > the issue is that I don't have the rh-python36-build in rhel (satellite) > > and I didn't manage to find it on rhel site, so I assume it doesn't > > exist and should be replaced somehow. > > It doesn't sound right to install it via wget && rpm -i from centos. > > Or am I wrong and it is somewhere? if yes, which repo? > > I'm not sure about the repo, as AFAIR it's not shipped, so probably some > internal compose only. > In the meantime, you can check it here: > > https://brewweb.engineering.redhat.com/brew/rpminfo?rpmID=4714375 Sorry, that's supposed you have access for it. Otherwise IDK. Pavel > > Pavel > > > > > Dependence only on rh-python36 is not enough as it is built for python > > 2.7 instead, the scl related macros are not working without > > rh-python36-build > > > > Thanks, > > Gh. > > > > > > Stefan Ring wrote: > > > On Wed, Nov 22, 2017 at 2:45 PM, Jiri Novak > > > wrote: > > >> Hello, > > >> > > >> I'm currently trying to port python app to use rh-python36 SCL (built > > >> using mock+rpmbuild), I've managed to make it build correctly in the scl > > >> paths (and using python3 for the packages that need it during build) if > > >> I install rh-python36-build from centos to the mock root. > > >> Is there a way to do this with rhel packages too? > > > Do what? > > > > > >> The issue is that > > >> without it, > > > Without what? > > > > > >> %{scl} in specfile is not populated, with it, it's properly > > >> set to rh-python36. Should I pass the value in different manner than in > > >> centos? or what might I be doing wrong? > > > I have no idea what you are trying to achieve. > > > From mskalick at redhat.com Wed Nov 22 15:37:32 2017 From: mskalick at redhat.com (Marek =?ISO-8859-1?Q?Skalick=FD?=) Date: Wed, 22 Nov 2017 16:37:32 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> Message-ID: <1511365052.9347.10.camel@redhat.com> Packages in collections with rh- prefix are part of RHSCL product and developed by RedHat. So no modification (adding new packages) should be done to these collections - it could cause confusion. So solution to your problem is to create new collection. And -build package of this your new collection will set env right that new packages you want to build will have right %scl macro,... and will use right python and so on. Jiri Novak p??e v St 22. 11. 2017 v 16:07 +0100: > Hi, > > the issue is that I don't have the rh-python36-build in rhel > (satellite) > and I didn't manage to find it on rhel site, so I assume it doesn't > exist and should be replaced somehow. > It doesn't sound right to install it via wget && rpm -i from centos. > Or am I wrong and it is somewhere? if yes, which repo? > > Dependence only on rh-python36 is not enough as it is built for > python > 2.7 instead, the scl related macros are not working without > rh-python36-build > > Thanks, > Gh. > > > Stefan Ring wrote: > > On Wed, Nov 22, 2017 at 2:45 PM, Jiri Novak > t> wrote: > > > Hello, > > > > > > I'm currently trying to port python app to use rh-python36 SCL > > > (built > > > using mock+rpmbuild), I've managed to make it build correctly in > > > the scl > > > paths (and using python3 for the packages that need it during > > > build) if > > > I install rh-python36-build from centos to the mock root. > > > Is there a way to do this with rhel packages too? > > > > Do what? > > > > > The issue is that > > > without it, > > > > Without what? > > > > > %{scl} in specfile is not populated, with it, it's properly > > > set to rh-python36. Should I pass the value in different manner > > > than in > > > centos? or what might I be doing wrong? > > > > I have no idea what you are trying to achieve. > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg From jiri.novak at ghorland.net Wed Nov 22 16:10:45 2017 From: jiri.novak at ghorland.net (Jiri Novak) Date: Wed, 22 Nov 2017 17:10:45 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: <1511365052.9347.10.camel@redhat.com> References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> Message-ID: <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> Hi, I've narrowed it down to what I need to place the packages in /opt/rh instead if the /usr/lib/python2.7 %define scl rh-python36 %define scl_package_override() %{expand:%{?python36_os_install_post:%global __os_install_post %python36_os_install_post} %global __python_requires %python36_python_requires %global __python_provides %python36_python_provides %global __python3 %python36__python3 %global __python %python36__python3 } as for what you say, for example, if I have a python library, that needs to be accessible when using rh-python36, it should be some xxx-python36-libname and activated at the same time? or how this should be handled? the next is the application itself, using rh-python36 and the xxx-python36-libname, that for sure can be separately and run with just scl enable rh-python36 python3 somepath, so maybe using two scls instead of one? Thanks, Gh. Marek Skalick? wrote: > Packages in collections with rh- prefix are part of RHSCL product and > developed by RedHat. So no modification (adding new packages) should be > done to these collections - it could cause confusion. > > So solution to your problem is to create new collection. And -build > package of this your new collection will set env right that new > packages you want to build will have right %scl macro,... and will use > right python and so on. > > Jiri Novak p??e v St 22. 11. 2017 v 16:07 +0100: >> Hi, >> >> the issue is that I don't have the rh-python36-build in rhel >> (satellite) >> and I didn't manage to find it on rhel site, so I assume it doesn't >> exist and should be replaced somehow. >> It doesn't sound right to install it via wget && rpm -i from centos. >> Or am I wrong and it is somewhere? if yes, which repo? >> >> Dependence only on rh-python36 is not enough as it is built for >> python >> 2.7 instead, the scl related macros are not working without >> rh-python36-build >> >> Thanks, >> Gh. >> >> >> Stefan Ring wrote: >>> On Wed, Nov 22, 2017 at 2:45 PM, Jiri Novak >> t> wrote: >>>> Hello, >>>> >>>> I'm currently trying to port python app to use rh-python36 SCL >>>> (built >>>> using mock+rpmbuild), I've managed to make it build correctly in >>>> the scl >>>> paths (and using python3 for the packages that need it during >>>> build) if >>>> I install rh-python36-build from centos to the mock root. >>>> Is there a way to do this with rhel packages too? >>> Do what? >>> >>>> The issue is that >>>> without it, >>> Without what? >>> >>>> %{scl} in specfile is not populated, with it, it's properly >>>> set to rh-python36. Should I pass the value in different manner >>>> than in >>>> centos? or what might I be doing wrong? >>> I have no idea what you are trying to achieve. >> >> _______________________________________________ >> 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: 866 bytes Desc: OpenPGP digital signature URL: From jiri.novak at ghorland.net Tue Nov 28 12:47:29 2017 From: jiri.novak at ghorland.net (Jiri Novak) Date: Tue, 28 Nov 2017 13:47:29 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> Message-ID: Hi, according to this ( https://developers.redhat.com/blog/2014/12/04/add-packages-to-python-2-7-software-collection/ ), I'm trying to create my own extension of the rh-python36, though doesn't build: + '[' '%{buildarch}' = noarch ']' + QA_CHECK_RPATHS=1 + case "${QA_CHECK_RPATHS:-}" in + /usr/lib/rpm/check-rpaths + /usr/lib/rpm/check-buildroot + '%{rh-python36_os_install_post}' /var/tmp/rpm-tmp.k3bzOV: line 316: fg: no job control error: Bad exit status from /var/tmp/rpm-tmp.k3bzOV (%install) most probably because the variables are not expanded? What did I miss? Specfile for refenrence in attachement. also, just to confirm, is this the right way to create those packages and make the applications depend on this scl, right? Thanks in advance, Gh. Jiri Novak wrote: > Hi, I've narrowed it down to what I need to place the packages in > /opt/rh instead if the /usr/lib/python2.7 > > %define scl rh-python36 > %define scl_package_override() > %{expand:%{?python36_os_install_post:%global __os_install_post > %python36_os_install_post} > %global __python_requires %python36_python_requires > %global __python_provides %python36_python_provides > %global __python3 %python36__python3 > %global __python %python36__python3 > } > > as for what you say, for example, if I have a python library, that needs > to be accessible when using rh-python36, it should be some > xxx-python36-libname and activated at the same time? or how this should > be handled? > the next is the application itself, using rh-python36 and the > xxx-python36-libname, that for sure can be separately and run with just > scl enable rh-python36 python3 somepath, so maybe using two scls instead > of one? > > Thanks, > Gh. > > > Marek Skalick? wrote: >> Packages in collections with rh- prefix are part of RHSCL product and >> developed by RedHat. So no modification (adding new packages) should be >> done to these collections - it could cause confusion. >> >> So solution to your problem is to create new collection. And -build >> package of this your new collection will set env right that new >> packages you want to build will have right %scl macro,... and will use >> right python and so on. >> >> Jiri Novak p??e v St 22. 11. 2017 v 16:07 +0100: >>> Hi, >>> >>> the issue is that I don't have the rh-python36-build in rhel >>> (satellite) >>> and I didn't manage to find it on rhel site, so I assume it doesn't >>> exist and should be replaced somehow. >>> It doesn't sound right to install it via wget && rpm -i from centos. >>> Or am I wrong and it is somewhere? if yes, which repo? >>> >>> Dependence only on rh-python36 is not enough as it is built for >>> python >>> 2.7 instead, the scl related macros are not working without >>> rh-python36-build >>> >>> Thanks, >>> Gh. >>> >>> >>> Stefan Ring wrote: >>>> On Wed, Nov 22, 2017 at 2:45 PM, Jiri Novak >>> t> wrote: >>>>> Hello, >>>>> >>>>> I'm currently trying to port python app to use rh-python36 SCL >>>>> (built >>>>> using mock+rpmbuild), I've managed to make it build correctly in >>>>> the scl >>>>> paths (and using python3 for the packages that need it during >>>>> build) if >>>>> I install rh-python36-build from centos to the mock root. >>>>> Is there a way to do this with rhel packages too? >>>> Do what? >>>> >>>>> The issue is that >>>>> without it, >>>> Without what? >>>> >>>>> %{scl} in specfile is not populated, with it, it's properly >>>>> set to rh-python36. Should I pass the value in different manner >>>>> than in >>>>> centos? or what might I be doing wrong? >>>> I have no idea what you are trying to achieve. >>> _______________________________________________ >>> SCLorg mailing list >>> SCLorg at redhat.com >>> https://www.redhat.com/mailman/listinfo/sclorg > -------------- next part -------------- #define name of the scl %global scl test-python36 %scl_package %scl # Defaults for the values for the python27 Software Collection. These # will be used when python27-scldevel is not in the buildroot %{!?scl_python:%global scl_python rh-python36} %{!?scl_prefix_python:%global scl_prefix_python %{scl_python}-} # Only for this build, we need to override default __os_install_post, because # the default one would find /opt/.../lib/python2.7/ and rpmbuild would # try to bytecompile with the system /usr/bin/python2.7 (which doesn't exist) %global __os_install_post %{%{scl_python}_os_install_post} # Similarly, override __python_requires for automatic dependency generator %global __python_requires %{%{scl_python}_python_requires} # The directory for site packages for this Software Collection %global test_python36_sitelib %(echo %{python36python_sitelib} | sed 's|%{scl_python}|%{scl}|') Summary: Package that installs %scl Name: %scl_name Version: 1 Release: 1%{?dist} License: GPLv2+ BuildRequires: scl-utils-build # Always make sure that there is the rh-python36-sclbuild # package in the buildroot BuildRequires: %{scl_prefix_python}scldevel # Require rh-python36-python-devel, we will need macros from that package BuildRequires: %{scl_prefix_python}python-devel Requires: %{scl_prefix}python-versiontools %description This is the main package for %scl Software Collection. %package runtime Summary: Package that handles %scl Software Collection. Requires: scl-utils Requires: %{scl_prefix_python}runtime %description runtime Package shipping essential scripts to work with %scl Software Collection. %package build Summary: Package shipping basic build configuration Requires: scl-utils-build # Require rh-python36-scldevel so that there is always access # to the %%scl_python and %%scl_prefix_python macros in builds for this Software # Collection Requires: %{scl_prefix_python}scldevel %description build Package shipping essential configuration macros to build %scl Software Collection. %prep %setup -c -T %install %scl_install # Create the enable scriptlet that: # - Adds an additional load path for the Python interpreter. # - Runs scl_source so that you can run: # scl enable test-python36 "bash" # instead of: # scl enable rh-python36 test-python36 "bash" cat >> %{buildroot}%{_scl_scripts}/enable << EOF . scl_source enable %{scl_python} export PYTHONPATH=%{test_python36_sitelib}${PYTHONPATH:+:${PYTHONPATH}} EOF mkdir -p %{buildroot}%{test_python36_sitelib} # - Enable Software Collection-specific bytecompilation macros from # the rh-python36-python-devel package. # - Also override the %%python_sitelib macro to point to the test-python36 Software # Collection. # - If you plan to add some architecture-dependent packages, you will also need to override # the %%python_sitearch macro. cat >> %{buildroot}%{_root_sysconfdir}/rpm/macros.%{scl}-config << EOF %%scl_package_override() %%{expand:%{?python36_os_install_post:%%global __os_install_post %%python36_os_install_post} %%global __python_requires %%python36_python_requires %%global __python_provides %%python36_python_provides %%global __python %python36__python3 %%global __python3 %python36__python3 %%global python_sitelib %test_python36_sitelib %%global python3_sitelib %test_python36_sitelib } EOF %files %files runtime %scl_files %scl_files %test_python36_sitelib %files build %{_root_sysconfdir}/rpm/macros.%{scl}-config -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 866 bytes Desc: OpenPGP digital signature URL: From stefanrin at gmail.com Tue Nov 28 13:07:31 2017 From: stefanrin at gmail.com (Stefan Ring) Date: Tue, 28 Nov 2017 14:07:31 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> Message-ID: On Tue, Nov 28, 2017 at 1:47 PM, Jiri Novak wrote: > Hi, > > according to this ( > https://developers.redhat.com/blog/2014/12/04/add-packages-to-python-2-7-software-collection/ > ), I'm trying to create my own extension of the rh-python36, though > doesn't build: > > + '[' '%{buildarch}' = noarch ']' > + QA_CHECK_RPATHS=1 > + case "${QA_CHECK_RPATHS:-}" in > + /usr/lib/rpm/check-rpaths > + /usr/lib/rpm/check-buildroot > + '%{rh-python36_os_install_post}' > /var/tmp/rpm-tmp.k3bzOV: line 316: fg: no job control > error: Bad exit status from /var/tmp/rpm-tmp.k3bzOV (%install) > > most probably because the variables are not expanded? > What did I miss? Specfile for refenrence in attachement. What is this spec file? It looks awfully complicated. I'm getting you want to build something against rh-python36. Why don't you take an existing package, let?s say, rh-python36-python-six, and adapt it? From jiri.novak at ghorland.net Tue Nov 28 13:40:52 2017 From: jiri.novak at ghorland.net (Jiri Novak) Date: Tue, 28 Nov 2017 14:40:52 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> Message-ID: <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> Hi I need to add more libraries to rh-python36, which would require using rh-python36-build package and I've been told it is wring and I should do my own SCL. then I need to make the application use the extended SCL with added libraries. Just running it agains rh-python36 is not enough because of missing dependencies :( The specfile should create packages test-python36-build and test-python36-runtime as a collection that extends rh-python36 Gh. Stefan Ring wrote: > On Tue, Nov 28, 2017 at 1:47 PM, Jiri Novak wrote: >> Hi, >> >> according to this ( >> https://developers.redhat.com/blog/2014/12/04/add-packages-to-python-2-7-software-collection/ >> ), I'm trying to create my own extension of the rh-python36, though >> doesn't build: >> >> + '[' '%{buildarch}' = noarch ']' >> + QA_CHECK_RPATHS=1 >> + case "${QA_CHECK_RPATHS:-}" in >> + /usr/lib/rpm/check-rpaths >> + /usr/lib/rpm/check-buildroot >> + '%{rh-python36_os_install_post}' >> /var/tmp/rpm-tmp.k3bzOV: line 316: fg: no job control >> error: Bad exit status from /var/tmp/rpm-tmp.k3bzOV (%install) >> >> most probably because the variables are not expanded? >> What did I miss? Specfile for refenrence in attachement. > What is this spec file? It looks awfully complicated. > > I'm getting you want to build something against rh-python36. Why don't > you take an existing package, let?s say, rh-python36-python-six, and > adapt it? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 866 bytes Desc: OpenPGP digital signature URL: From jiri.novak at ghorland.net Tue Nov 28 14:40:40 2017 From: jiri.novak at ghorland.net (Jiri Novak) Date: Tue, 28 Nov 2017 15:40:40 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> Message-ID: <3018fdf9-71b8-a331-93af-da025f890125@ghorland.net> Hi, pip is not preffered way for production deployments here. I'll keep it as last resort (maybe even after adding the libraries into rh-python36 collection which is bad :)) But generally, if I want to create a dependent SCL, I obviously miss some macros or something in the specfile. thanks, Gh. Davis, Daniel (NIH/NLM) [C] wrote: > Jiri, if you mean Python packages, I do it this way (for a designated > owner account): > > scl enable rh-python36 bash > pip install --user lxml > > Above, lxml is an example package. > > Also consider whether you want Python 36 binary extensions to always > be available. You can create a file in /etc/ld.so.conf.d that does > that - SCLs don't do that to be safe about what else is on the box, > but for your own boxes why not. > > Buried in ansible code, you can see this in action at > https://GitHub.com/NLM-OCCS/occsab-python > > > > > Sent with BlackBerry Work (www.blackberry.com) > ------------------------------------------------------------------------ > *From: *Jiri Novak > *Sent: *Nov 28, 2017 5:41 AM > *To: *Stefan Ring > *Cc: *sclorg at redhat.com > *Subject: *Re: [scl.org] rh-python36-build alternative in rhel > > Hi > > I need to add more libraries to rh-python36, which would require using > rh-python36-build package and I've been told it is wring and I should do > my own SCL. > > then I need to make the application use the extended SCL with added > libraries. > > Just running it agains rh-python36 is not enough because of missing > dependencies :( > > The specfile should create packages test-python36-build and > test-python36-runtime as a collection that extends rh-python36 > > Gh. > > Stefan Ring wrote: > > On Tue, Nov 28, 2017 at 1:47 PM, Jiri Novak > wrote: > >> Hi, > >> > >> according to this ( > >> > https://developers.redhat.com/blog/2014/12/04/add-packages-to-python-2-7-software-collection/ > >> ), I'm trying to create my own extension of the rh-python36, though > >> doesn't build: > >> > >> + '[' '%{buildarch}' = noarch ']' > >> + QA_CHECK_RPATHS=1 > >> + case "${QA_CHECK_RPATHS:-}" in > >> + /usr/lib/rpm/check-rpaths > >> + /usr/lib/rpm/check-buildroot > >> + '%{rh-python36_os_install_post}' > >> /var/tmp/rpm-tmp.k3bzOV: line 316: fg: no job control > >> error: Bad exit status from /var/tmp/rpm-tmp.k3bzOV (%install) > >> > >> most probably because the variables are not expanded? > >> What did I miss? Specfile for refenrence in attachement. > > What is this spec file? It looks awfully complicated. > > > > I'm getting you want to build something against rh-python36. Why don't > > you take an existing package, let?s say, rh-python36-python-six, and > > adapt it? > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 866 bytes Desc: OpenPGP digital signature URL: From stefanrin at gmail.com Tue Nov 28 23:10:25 2017 From: stefanrin at gmail.com (Stefan Ring) Date: Wed, 29 Nov 2017 00:10:25 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> Message-ID: On Tue, Nov 28, 2017 at 2:40 PM, Jiri Novak wrote: > Hi > > I need to add more libraries to rh-python36, which would require using > rh-python36-build package and I've been told it is wring and I should do > my own SCL. > > then I need to make the application use the extended SCL with added > libraries. > > Just running it agains rh-python36 is not enough because of missing > dependencies :( > > The specfile should create packages test-python36-build and > test-python36-runtime as a collection that extends rh-python36 Is this even possible? If your collection is called test-python36, it will live in another directory hierarchy than rh-python36 and will not be able to access the packages from there. I think you're in for a world of pain. You can of course start a new collection by renaming everything in the rh-python36 package sources, picking up just the packages you need, thus creating a new, derived collection. From jiri.novak at ghorland.net Wed Nov 29 09:16:17 2017 From: jiri.novak at ghorland.net (Jiri Novak) Date: Wed, 29 Nov 2017 10:16:17 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> Message-ID: Stefan Ring wrote: > On Tue, Nov 28, 2017 at 2:40 PM, Jiri Novak wrote: >> Hi >> >> I need to add more libraries to rh-python36, which would require using >> rh-python36-build package and I've been told it is wring and I should do >> my own SCL. >> >> then I need to make the application use the extended SCL with added >> libraries. >> >> Just running it agains rh-python36 is not enough because of missing >> dependencies :( >> >> The specfile should create packages test-python36-build and >> test-python36-runtime as a collection that extends rh-python36 > Is this even possible? If your collection is called test-python36, it > will live in another directory hierarchy than rh-python36 and will not > be able to access the packages from there. I think you're in for a > world of pain. > > You can of course start a new collection by renaming everything in the > rh-python36 package sources, picking up just the packages you need, > thus creating a new, derived collection. Hi, from what I know until now, it should be, but I might be wrong. What else is the right way to make RPM adding more libraries available when in scl enable rh-python36 bash? Thanks, Gh. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 866 bytes Desc: OpenPGP digital signature URL: From stefanrin at gmail.com Wed Nov 29 09:28:09 2017 From: stefanrin at gmail.com (Stefan Ring) Date: Wed, 29 Nov 2017 10:28:09 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> Message-ID: > What else is the right way to make RPM adding more libraries available > when in scl enable rh-python36 bash? Create your own mirror of rh-python36 and just add your packages to it? From jiri.novak at ghorland.net Wed Nov 29 10:12:40 2017 From: jiri.novak at ghorland.net (Jiri Novak) Date: Wed, 29 Nov 2017 11:12:40 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> Message-ID: Stefan Ring wrote: >> What else is the right way to make RPM adding more libraries available >> when in scl enable rh-python36 bash? > Create your own mirror of rh-python36 and just add your packages to it? Sounds like dirty hack as rh-python36-build was intentionally not shipped in rhel. or by mirror you mean to rename it to xxx-python36 and rebuild all packages I need? I currently managed to find specfiles that generate rh-python36-build and I'll try to make the xxx-python36 copy and if that works, try to make it depend on rh-python36, we'll see if that works or not. Thanks, Gh. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 866 bytes Desc: OpenPGP digital signature URL: From stefanrin at gmail.com Wed Nov 29 10:55:04 2017 From: stefanrin at gmail.com (Stefan Ring) Date: Wed, 29 Nov 2017 11:55:04 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> Message-ID: On Wed, Nov 29, 2017 at 11:12 AM, Jiri Novak wrote: > Stefan Ring wrote: >>> What else is the right way to make RPM adding more libraries available >>> when in scl enable rh-python36 bash? >> Create your own mirror of rh-python36 and just add your packages to it? > Sounds like dirty hack as rh-python36-build was intentionally not > shipped in rhel. or by mirror you mean to rename it to xxx-python36 and > rebuild all packages I need? No, I mean a real mirror that carries all the original packages, to which you can also add your own. From Fedora at FamilleCollet.com Wed Nov 29 14:13:54 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Wed, 29 Nov 2017 15:13:54 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> Message-ID: <11f16326-ce1d-66f4-a25b-9c59ca0db1a4@FamilleCollet.com> I think there some confusion here. The simple way to build additional package for an existing collection is to install the -build package in the buildroot, which provides the "overrides" stuff for needed macros. This is exactly what is done by the SCLo SIG Examples: * sclo-php71 (additional packages for rh-php71) => https://cbs.centos.org/koji/packages?tagID=1019 * sclo-python35 (additional packages for rh-python35) => https://cbs.centos.org/koji/packages?tagID=1283 And for now, this is the simplest way to do it BUT: -build is only available in CentOS repository, not in RHSCL. Remi. P.S. spec file hosted on https://github.com/sclorg-distgit/ From jiri.novak at ghorland.net Wed Nov 29 14:35:49 2017 From: jiri.novak at ghorland.net (Jiri Novak) Date: Wed, 29 Nov 2017 15:35:49 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: <11f16326-ce1d-66f4-a25b-9c59ca0db1a4@FamilleCollet.com> References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> <11f16326-ce1d-66f4-a25b-9c59ca0db1a4@FamilleCollet.com> Message-ID: <452f03cf-ae4c-1d16-3a3f-1e140384661e@ghorland.net> Hi, yes, the only way I managed to build so far was in the begining by copying rh-python36-build from centos to my own repo. Which seems to be wrong according to redhat, but I start to think its the only way :) I've managed to make some dummy scl extending rh-python36 but still a lot paths is somewhere derived from that and I have no idea where from :/ will take ages to make it properly. the sclo packages will also write itself into /opt/rh/rh-python36/something, right? Thanks, Gh. Remi Collet wrote: > I think there some confusion here. > > The simple way to build additional package for an existing collection is > to install the -build package in the buildroot, which provides the > "overrides" stuff for needed macros. > > This is exactly what is done by the SCLo SIG > > Examples: > > * sclo-php71 (additional packages for rh-php71) > => https://cbs.centos.org/koji/packages?tagID=1019 > > * sclo-python35 (additional packages for rh-python35) > => https://cbs.centos.org/koji/packages?tagID=1283 > > > And for now, this is the simplest way to do it > > BUT: -build is only available in CentOS repository, not in RHSCL. > > > > Remi. > > > P.S. spec file hosted on https://github.com/sclorg-distgit/ > > _______________________________________________ > 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: 866 bytes Desc: OpenPGP digital signature URL: From Fedora at FamilleCollet.com Wed Nov 29 14:54:00 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Wed, 29 Nov 2017 15:54:00 +0100 Subject: [scl.org] rh-python36-build alternative in rhel In-Reply-To: <452f03cf-ae4c-1d16-3a3f-1e140384661e@ghorland.net> References: <1727e127-dcf7-b377-ad2a-7cf072a3747d@ghorland.net> <1511365052.9347.10.camel@redhat.com> <26fd092d-2002-d10c-f31e-613ae6288094@ghorland.net> <6a39416a-d3e8-cf74-5f35-e77c2ea75ce8@ghorland.net> <11f16326-ce1d-66f4-a25b-9c59ca0db1a4@FamilleCollet.com> <452f03cf-ae4c-1d16-3a3f-1e140384661e@ghorland.net> Message-ID: Hi, Le 29/11/2017 ? 15:35, Jiri Novak a ?crit?: > the sclo packages will also write itself into > /opt/rh/rh-python36/something, right? $ rpm -qlp sclo-python35-python-bottle-0.12.9-5.el7.noarch.rpm /opt/rh/rh-python35/root/usr/lib/python3.5/site-packages/__pycache__ /opt/rh/rh-python35/root/usr/lib/python3.5/site-packages/__pycache__/bottle.cpython-35.opt-1.pyc /opt/rh/rh-python35/root/usr/lib/python3.5/site-packages/__pycache__/bottle.cpython-35.pyc ... So: Yes. Remi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 283 bytes Desc: OpenPGP digital signature URL: From ykoer at redhat.com Thu Nov 9 16:34:37 2017 From: ykoer at redhat.com (=?UTF-8?Q?Yusuf_K=c3=b6r?=) Date: Thu, 09 Nov 2017 16:34:37 -0000 Subject: [scl.org] rhscl/httpd-24-rhel7 Message-ID: Hi, I am currently working on ambassadors project which will run on Openshift. We are also using rhscl/httpd-24-rhel7 image. Is there a documentation how I can enable SSL? This didn't really help https://access.redhat.com/documentation/en-us/red_hat_software_collections/2/html/using_red_hat_software_collections_container_images/daemon-images#description-9 I put a conf file with all the SSL configuration into /opt/app-root/etc/httpd.d, but it is not used. Thanks a lot Yusuf From pvalena at redhat.com Wed Nov 29 17:13:08 2017 From: pvalena at redhat.com (Pavel Valena) Date: Wed, 29 Nov 2017 12:13:08 -0500 (EST) Subject: [scl.org] rhscl/httpd-24-rhel7 In-Reply-To: References: Message-ID: <1708096596.23044549.1511975588112.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: "Yusuf K?r" > To: sclorg at redhat.com > Sent: Thursday, November 9, 2017 5:34:31 PM > Subject: [scl.org] rhscl/httpd-24-rhel7 > > Hi, > > I am currently working on ambassadors project which will run on > Openshift. We are also using rhscl/httpd-24-rhel7 image. Is there a > documentation how I can enable SSL? > > This didn't really help > https://access.redhat.com/documentation/en-us/red_hat_software_collections/2/html/using_red_hat_software_collections_container_images/daemon-images#description-9 > > I put a conf file with all the SSL configuration into > /opt/app-root/etc/httpd.d, but it is not used. The service is exposed on 8443 by default: ``` >> oc new-app centos/httpd-24-centos7~https://github.com/openshift/httpd-ex --> Found Docker image cc5566b (7 days old) from Docker Hub for "centos/httpd-24-centos7" Apache httpd 2.4 ---------------- Apache httpd 2.4 available as docker container, is a powerful, efficient, and extensible web server. Apache supports a variety of features, many implemented as compiled modules which extend the core functionality. These can range from server-side programming language support to authentication schemes. Virtual hosting allows one Apache installation to serve many different Web sites. Tags: builder, httpd, httpd24 * An image stream will be created as "httpd-24-centos7:latest" that will track the source image * A source build using source code from https://github.com/openshift/httpd-ex will be created * The resulting image will be pushed to image stream "httpd-ex:latest" * Every time "httpd-24-centos7:latest" changes a new build will be triggered * This image will be deployed in deployment config "httpd-ex" * Ports 8080/tcp, 8443/tcp will be load balanced by service "httpd-ex" ``` You just need to set up a proper route. You'll can also use './httpd-cfg' folder to add more config files. For more info about the container, please check [1]. Regards, Pavel [1] https://github.com/sclorg/httpd-container/tree/master/2.4 > > > Thanks a lot > Yusuf > From matt at khoza.com Wed Nov 29 20:24:01 2017 From: matt at khoza.com (Matt Simonsen) Date: Wed, 29 Nov 2017 12:24:01 -0800 Subject: [scl.org] Updated rh-php70 packages Message-ID: <9920e9f9-a30d-6a3c-e6db-b2ec17af321d@khoza.com> It appears that rh-php70 packages are quite out of date (php 7.0.10) Is there no maintainer to update these?? I understand timely updates are not promised, so I'm looking at building my own. Is there any public documentation and/or a SPEC file that I could use to start on making my own packages? If there's a way to contribute these packages back to the community I'd be willing to do this too. Or is there a better way to run multiple PHP versions on a single server? I'm open to other suggestions. Thank you all, Matt From Fedora at FamilleCollet.com Thu Nov 30 06:04:22 2017 From: Fedora at FamilleCollet.com (Remi Collet) Date: Thu, 30 Nov 2017 07:04:22 +0100 Subject: [scl.org] Updated rh-php70 packages In-Reply-To: <9920e9f9-a30d-6a3c-e6db-b2ec17af321d@khoza.com> References: <9920e9f9-a30d-6a3c-e6db-b2ec17af321d@khoza.com> Message-ID: Le 29/11/2017 ? 21:24, Matt Simonsen a ?crit?: > It appears that rh-php70 packages are quite out of date (php 7.0.10) This package are part of RHSCL and thus maintained by Red Hat as other products (e.g. RHEL) See: https://access.redhat.com/security/updates/backporting/ Going through the standard RH support process, you can ask for a update, but can't say if this will be accepted. Well SCL are a bit different as "rebase" (version update) are a bit more frequent there. Else, I see 2 way to use a more recent version 1/ Use rh-php71 instead 2/ Use php70 SCL from my repository which was used as base for rh-php70 but which is updated on each upstream version (7.0.26 for now) See https://rpms.remirepo.net/wizard/ (Type of installation = Multiple versions = SCL) Remi > Is there no maintainer to update these?? I understand timely updates are > not promised, so I'm looking at building my own. > > Is there any public documentation and/or a SPEC file that I could use to > start on making my own packages? If there's a way to contribute these > packages back to the community I'd be willing to do this too. > > Or is there a better way to run multiple PHP versions on a single > server? I'm open to other suggestions. > > Thank you all, > > Matt > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg From matt at khoza.com Thu Nov 30 20:04:53 2017 From: matt at khoza.com (Matt Simonsen) Date: Thu, 30 Nov 2017 12:04:53 -0800 Subject: [scl.org] Updated rh-php70 packages (solved) In-Reply-To: References: <9920e9f9-a30d-6a3c-e6db-b2ec17af321d@khoza.com> Message-ID: <8d663ecb-0cb4-d383-c100-3d2af2240872@khoza.com> On 11/29/2017 10:04 PM, Remi Collet wrote: > Else, I see 2 way to use a more recent version > > 1/ Use rh-php71 instead > > 2/ Use php70 SCL from my repository which was used as base for rh-php70 > but which is updated on each upstream version (7.0.26 for now) > > See https://rpms.remirepo.net/wizard/ > (Type of installation = Multiple versions = SCL) Thank you for clarifying. I will be using your repo, this is very helpful information. Matt