From isdtor at gmail.com Fri Oct 4 14:22:00 2019 From: isdtor at gmail.com (isdtor) Date: Fri, 4 Oct 2019 15:22:00 +0100 Subject: [scl.org] Rebuilding sclo packages in mock Message-ID: <20191004142200.GA57409@localhost.localdomain> Hi all, I have a problem similar or at least related to https://www.redhat.com/archives/sclorg/2016-May/msg00020.html except I'm trying to do it all in mock. There's a custom config file with config_opts['chroot_setup_cmd'] = 'install @buildsys scl-utils-build httpd24-build shadow-utils' and the command I'm running to just rebuild this package is mock -r scl-6-x86_64 -D "scl httpd24" httpd24-1.1-18.el6.src.rpm with the result ... Start: build setup for httpd24-1.1-18.el6.src.rpm ERROR: Exception(httpd24-1.1-18.el6.src.rpm) Config(scl-6-x86_64) 0 minutes 31 seconds INFO: Results and/or logs in: /var/lib/mock/scl-6-x86_64/result Traceback (most recent call last): File "/usr/libexec/mock/mock", line 886, in main() File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 89, in trace result = func(*args, **kw) File "/usr/libexec/mock/mock", line 701, in main run_command(options, args, config_opts, commands, buildroot, state) File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 89, in trace result = func(*args, **kw) File "/usr/libexec/mock/mock", line 783, in run_command do_rebuild(config_opts, commands, buildroot, args) File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 89, in trace result = func(*args, **kw) File "/usr/libexec/mock/mock", line 520, in do_rebuild post=post_build, clean=clean) File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 89, in trace result = func(*args, **kw) File "/usr/libexec/mock/mock", line 465, in rebuild_generic ret = cmd(item) File "/usr/libexec/mock/mock", line 501, in build check=config_opts['check']) File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 89, in trace result = func(*args, **kw) File "/usr/lib/python2.6/site-packages/mockbuild/backend.py", line 210, in build self.install_srpm(srpm) File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 89, in trace result = func(*args, **kw) File "/usr/lib/python2.6/site-packages/mockbuild/backend.py", line 386, in install_srpm nspawn_args=self.config['nspawn_args']) File "/usr/lib/python2.6/site-packages/mockbuild/buildroot.py", line 190, in doChroot env=env, shell=shell, *args, **kargs) File "/usr/lib/python2.6/site-packages/mockbuild/trace_decorator.py", line 89, in trace result = func(*args, **kw) File "/usr/lib/python2.6/site-packages/mockbuild/util.py", line 532, in do preexec_fn=preexec, File "/usr/lib64/python2.6/subprocess.py", line 642, in __init__ errread, errwrite) File "/usr/lib64/python2.6/subprocess.py", line 1234, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory It is not clear which file or directory is missing and the chroot result logs aren't very clear either but this log DEBUG util.py:439: No Packages marked for Update DEBUG util.py:577: Child return code was: 0 DEBUG util.py:122: touching file: /var/lib/mock/scl-6-x86_64/root/.initialized DEBUG util.py:598: child environment: None DEBUG util.py:522: Executing command: ['/bin/rpm', '-Uvh', '--nodeps', '/builddir/build/originals/httpd24-1.1-18.el6.src.rpm'] with env {'LANG': 'C', 'TERM': 'vt100', 'SHELL': '/bin/bash', 'HOSTNAME': 'mock', 'PROMPT_COMMAND': 'printf "\\033]0;\\007"', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin', 'PS1': ' \\s-\\v\\$ '} and shell False DEBUG util.py:188: kill orphans DEBUG util.py:598: child environment: None DEBUG util.py:522: Executing command: ['/bin/umount', '-n', '/var/lib/mock/scl-6-x86_64/root/proc/filesystems'] with env {'LANG': 'C', 'TERM': 'vt100', 'SHELL': '/bin/sh', 'HOSTNAME': 'mock', 'HOME': '/builddir', 'PATH': '/usr/bin:/bin:/usr/sbin:/sbin'} and shell False DEBUG util.py:577: Child return code was: 0 makes me think that the rpm command fails - /builddir/build/originals/httpd24-1.1-18.el6.src.rpm exists, but it evidently hasn't been unpacked. Adding python to the chroot setup leads to the same error. I am able to rebuild these packages as root, outside mock. From stefanrin at gmail.com Fri Oct 4 18:11:33 2019 From: stefanrin at gmail.com (Stefan Ring) Date: Fri, 4 Oct 2019 20:11:33 +0200 Subject: [scl.org] Rebuilding sclo packages in mock In-Reply-To: <20191004142200.GA57409@localhost.localdomain> References: <20191004142200.GA57409@localhost.localdomain> Message-ID: On Fri, Oct 4, 2019 at 4:26 PM isdtor wrote: > > Hi all, > > I have a problem similar or at least related to > https://www.redhat.com/archives/sclorg/2016-May/msg00020.html > except I'm trying to do it all in mock. > > There's a custom config file with > > config_opts['chroot_setup_cmd'] = 'install @buildsys scl-utils-build httpd24-build shadow-utils' > > and the command I'm running to just rebuild this package is > > mock -r scl-6-x86_64 -D "scl httpd24" httpd24-1.1-18.el6.src.rpm No idea, works for me on CentOS 6 (mock-1.2.21-1.el6). From pkubat at redhat.com Mon Oct 7 09:19:46 2019 From: pkubat at redhat.com (Petr Kubat) Date: Mon, 7 Oct 2019 11:19:46 +0200 Subject: [scl.org] ubi7/php-72 image In-Reply-To: References: Message-ID: <864928c1-6804-2d5a-d223-d9f2fed834a5@redhat.com> Hi Nate, sorry for the late reply, I only got your mail from the ML now (likely due to some manual message review?). You are correct, we have observed bigger image sizes around the time your mail was sent. This was caused by a bug in the build process - the yum cache was not properly cleaned for all repositories, only for enabled ones. This has since be fixed and image sizes are back to normal. Petr On 7/9/19 11:07 PM, Nate Stephany wrote: > 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. > > > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg -------------- next part -------------- An HTML attachment was scrubbed... URL: From viscapi at cines.fr Fri Oct 11 09:22:46 2019 From: viscapi at cines.fr (viscapi at cines.fr) Date: Fri, 11 Oct 2019 11:22:46 +0200 (CEST) Subject: [scl.org] SCL and Ansible ? Message-ID: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> Dear all, Silly question: is there a way to call "scl enable" from within an Ansible role ? So far we've been trying the command, shell and scripts modules, but to no avail... https://docs.ansible.com/ansible/latest/modules/command_module.html#command-module https://docs.ansible.com/ansible/latest/modules/shell_module.html#shell-module https://docs.ansible.com/ansible/latest/modules/script_module.html#script-module Here are some failed attempts: - name: Start using the software collection for maven shell: scl_enabled rh-maven35 register: swap_exists ignore_errors: true #script: test.sh # shell: scl enable /etc/scl/conf//opt/rh/rh-maven35 bash && echo toto #shell: /usr/bin/scl enable rh-maven35 bash # args: # warn: yes # chdir: "{{ path_to_pastis }}" #easy_install: # name: scl # args: # executable: "/usr/bin/scl enable rh-maven35 bash" # command: | # /usr/bin/scl enable rh-maven35 bash #bash # shell: | # scl enable rh-maven35 bash #bash # args: # executable: /bin/bash I think the root issue is that, as far as I understand, "scl enable" starts a new shell and sources environment variables in there, while Ansible is still waiting for some RC in the parent shell. Thus Ansible is not really failing, but just keeps on waiting for ever... Any help would be greatly appreciated. Best regards, Samuel from CINES https://www.cines.fr/en/ -- Samuel VISCAPI +33(0)4 67 14 14 36 viscapi at cines.fr IM: sviscapi (Skype) From pvalena at redhat.com Fri Oct 11 11:32:07 2019 From: pvalena at redhat.com (Pavel Valena) Date: Fri, 11 Oct 2019 07:32:07 -0400 (EDT) Subject: [scl.org] SCL and Ansible ? In-Reply-To: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> References: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> Message-ID: <692220636.3576714.1570793527522.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: viscapi at cines.fr > To: sclorg at redhat.com > Cc: "caux" > Sent: Friday, October 11, 2019 11:22:46 AM > Subject: [scl.org] SCL and Ansible ? > > Dear all, > > Silly question: is there a way to call "scl enable" from within an Ansible > role ? > > So far we've been trying the command, shell and scripts modules, but to no > avail... > > https://docs.ansible.com/ansible/latest/modules/command_module.html#command-module > https://docs.ansible.com/ansible/latest/modules/shell_module.html#shell-module > https://docs.ansible.com/ansible/latest/modules/script_module.html#script-module > > Here are some failed attempts: > > - name: Start using the software collection for maven > shell: scl_enabled rh-maven35 > register: swap_exists > ignore_errors: true > #script: test.sh > # shell: scl enable /etc/scl/conf//opt/rh/rh-maven35 bash && echo toto > #shell: /usr/bin/scl enable rh-maven35 bash > # args: > # warn: yes > # chdir: "{{ path_to_pastis }}" > #easy_install: > # name: scl > # args: > # executable: "/usr/bin/scl enable rh-maven35 bash" > # command: | > # /usr/bin/scl enable rh-maven35 bash > #bash > # shell: | > # scl enable rh-maven35 bash > #bash > # args: > # executable: /bin/bash Hello, I'm no ansible expert, but couldn't you run the command you wan't like so: shell: /usr/bin/scl enable rh-maven35 -- /path/to/prog/or/scriplet arguments... Alternatively, though unsupported probably, you could try `. scl_source`; f.e.: ``` $ ruby -v ; . scl_source enable rh-ruby25 ; ruby -v ruby 2.0.0p648 (2015-12-16) [x86_64-linux] ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux] ``` HIH, Pavel > > I think the root issue is that, as far as I understand, "scl enable" starts a > new shell and sources environment variables in there, while Ansible is still > waiting for some RC in the parent shell. Thus Ansible is not really failing, > but just keeps on waiting for ever... > > Any help would be greatly appreciated. > > Best regards, > > Samuel from CINES > > https://www.cines.fr/en/ > > -- > > Samuel VISCAPI > > +33(0)4 67 14 14 36 > viscapi at cines.fr > IM: sviscapi (Skype) > -- Pavel Valena Software Engineer, Red Hat Brno, Czech Republic From ehripko at bloomberg.net Thu Oct 10 09:40:55 2019 From: ehripko at bloomberg.net (Eric Hripko (BLOOMBERG/ LONDON)) Date: Thu, 10 Oct 2019 09:40:55 -0000 Subject: [scl.org] =?utf-8?q?Python3=2E7_in_Software_Collections?= Message-ID: <5D9EFCA700A000D80039024F_0_14572@msllnjpmsgsv06> Hi folks, First of all, thank you for this project - it's really awesome and helpful! I've checked the catalogue and it looks like the latest Python version supported by Software Collections is 3.6. Is there any chance Software Collections will start supporting Python3.7? Are there any known blockers I can help removing to enable this? Please let me know. Thanks again, Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From robwiss at gmail.com Fri Oct 11 13:33:18 2019 From: robwiss at gmail.com (Rob Wissmann) Date: Fri, 11 Oct 2019 09:33:18 -0400 Subject: [scl.org] SCL and Ansible ? In-Reply-To: <692220636.3576714.1570793527522.JavaMail.zimbra@redhat.com> References: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> <692220636.3576714.1570793527522.JavaMail.zimbra@redhat.com> Message-ID: Pavel's approach should work fine. Here are two other approaches I've seen used. 1. Run a playbook that installs the enable script (/opt/rh/devtoolset-8/enable) into /etc/profile.d. Then, in another playbook do the stuff you want to do. The second playbook will run as a new ssh login which means it will pick up the enable actions from the /etc/profile.d/ script. If you do this, you also need to fix the devtoolset sudo script because it's broken and doesn't properly forward arguments to the actual sudo program. I have a working version. 2. Install the devtoolset tools you want then configure the system using the "alternatives" program to make it so that the devtoolset versions are the ones that are run. The ansible module for alternatives doesn't work great though. Specifically, it won't update the settings once they've been set, or if it does, I couldn't easily figure out how. On Fri, Oct 11, 2019 at 7:35 AM Pavel Valena wrote: > ----- Original Message ----- > > From: viscapi at cines.fr > > To: sclorg at redhat.com > > Cc: "caux" > > Sent: Friday, October 11, 2019 11:22:46 AM > > Subject: [scl.org] SCL and Ansible ? > > > > Dear all, > > > > Silly question: is there a way to call "scl enable" from within an > Ansible > > role ? > > > > So far we've been trying the command, shell and scripts modules, but to > no > > avail... > > > > > https://docs.ansible.com/ansible/latest/modules/command_module.html#command-module > > > https://docs.ansible.com/ansible/latest/modules/shell_module.html#shell-module > > > https://docs.ansible.com/ansible/latest/modules/script_module.html#script-module > > > > Here are some failed attempts: > > > > - name: Start using the software collection for maven > > shell: scl_enabled rh-maven35 > > register: swap_exists > > ignore_errors: true > > #script: test.sh > > # shell: scl enable /etc/scl/conf//opt/rh/rh-maven35 bash && echo toto > > #shell: /usr/bin/scl enable rh-maven35 bash > > # args: > > # warn: yes > > # chdir: "{{ path_to_pastis }}" > > #easy_install: > > # name: scl > > # args: > > # executable: "/usr/bin/scl enable rh-maven35 bash" > > # command: | > > # /usr/bin/scl enable rh-maven35 bash > > #bash > > # shell: | > > # scl enable rh-maven35 bash > > #bash > > # args: > > # executable: /bin/bash > > Hello, > > I'm no ansible expert, but couldn't you run the command you wan't like so: > > shell: /usr/bin/scl enable rh-maven35 -- /path/to/prog/or/scriplet > arguments... > > > Alternatively, though unsupported probably, you could try `. scl_source`; > f.e.: > > ``` > $ ruby -v ; . scl_source enable rh-ruby25 ; ruby -v > ruby 2.0.0p648 (2015-12-16) [x86_64-linux] > ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux] > > ``` > > HIH, > Pavel > > > > > I think the root issue is that, as far as I understand, "scl enable" > starts a > > new shell and sources environment variables in there, while Ansible is > still > > waiting for some RC in the parent shell. Thus Ansible is not really > failing, > > but just keeps on waiting for ever... > > > > Any help would be greatly appreciated. > > > > Best regards, > > > > Samuel from CINES > > > > https://www.cines.fr/en/ > > > > -- > > > > Samuel VISCAPI > > > > +33(0)4 67 14 14 36 > > viscapi at cines.fr > > IM: sviscapi (Skype) > > > > -- > Pavel Valena > Software Engineer, Red Hat > Brno, Czech Republic > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel.davis at nih.gov Fri Oct 11 14:47:35 2019 From: daniel.davis at nih.gov (Davis, Daniel (NIH/NLM) [C]) Date: Fri, 11 Oct 2019 14:47:35 +0000 Subject: [scl.org] SCL and Ansible ? In-Reply-To: References: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> <692220636.3576714.1570793527522.JavaMail.zimbra@redhat.com> Message-ID: If you want scl enable to effect the ansible process itself, you could write a python function that parses the enable script using shutil and then sets the environment variables on os.environ. Then, expose this as an ansible plugin. From: sclorg-bounces at redhat.com On Behalf Of Rob Wissmann Sent: Friday, October 11, 2019 9:33 AM To: Pavel Valena Cc: caux ; sclorg at redhat.com Subject: Re: [scl.org] SCL and Ansible ? Pavel's approach should work fine. Here are two other approaches I've seen used. 1. Run a playbook that installs the enable script (/opt/rh/devtoolset-8/enable) into /etc/profile.d. Then, in another playbook do the stuff you want to do. The second playbook will run as a new ssh login which means it will pick up the enable actions from the /etc/profile.d/ script. If you do this, you also need to fix the devtoolset sudo script because it's broken and doesn't properly forward arguments to the actual sudo program. I have a working version. 2. Install the devtoolset tools you want then configure the system using the "alternatives" program to make it so that the devtoolset versions are the ones that are run. The ansible module for alternatives doesn't work great though. Specifically, it won't update the settings once they've been set, or if it does, I couldn't easily figure out how. On Fri, Oct 11, 2019 at 7:35 AM Pavel Valena > wrote: ----- Original Message ----- > From: viscapi at cines.fr > To: sclorg at redhat.com > Cc: "caux" > > Sent: Friday, October 11, 2019 11:22:46 AM > Subject: [scl.org] SCL and Ansible ? > > Dear all, > > Silly question: is there a way to call "scl enable" from within an Ansible > role ? > > So far we've been trying the command, shell and scripts modules, but to no > avail... > > https://docs.ansible.com/ansible/latest/modules/command_module.html#command-module > https://docs.ansible.com/ansible/latest/modules/shell_module.html#shell-module > https://docs.ansible.com/ansible/latest/modules/script_module.html#script-module > > Here are some failed attempts: > > - name: Start using the software collection for maven > shell: scl_enabled rh-maven35 > register: swap_exists > ignore_errors: true > #script: test.sh > # shell: scl enable /etc/scl/conf//opt/rh/rh-maven35 bash && echo toto > #shell: /usr/bin/scl enable rh-maven35 bash > # args: > # warn: yes > # chdir: "{{ path_to_pastis }}" > #easy_install: > # name: scl > # args: > # executable: "/usr/bin/scl enable rh-maven35 bash" > # command: | > # /usr/bin/scl enable rh-maven35 bash > #bash > # shell: | > # scl enable rh-maven35 bash > #bash > # args: > # executable: /bin/bash Hello, I'm no ansible expert, but couldn't you run the command you wan't like so: shell: /usr/bin/scl enable rh-maven35 -- /path/to/prog/or/scriplet arguments... Alternatively, though unsupported probably, you could try `. scl_source`; f.e.: ``` $ ruby -v ; . scl_source enable rh-ruby25 ; ruby -v ruby 2.0.0p648 (2015-12-16) [x86_64-linux] ruby 2.5.5p157 (2019-03-15 revision 67260) [x86_64-linux] ``` HIH, Pavel > > I think the root issue is that, as far as I understand, "scl enable" starts a > new shell and sources environment variables in there, while Ansible is still > waiting for some RC in the parent shell. Thus Ansible is not really failing, > but just keeps on waiting for ever... > > Any help would be greatly appreciated. > > Best regards, > > Samuel from CINES > > https://www.cines.fr/en/ > > -- > > Samuel VISCAPI > > +33(0)4 67 14 14 36 > viscapi at cines.fr > IM: sviscapi (Skype) > -- Pavel Valena Software Engineer, Red Hat Brno, Czech Republic _______________________________________________ SCLorg mailing list SCLorg at redhat.com https://www.redhat.com/mailman/listinfo/sclorg -------------- next part -------------- An HTML attachment was scrubbed... URL: From phracek at redhat.com Mon Oct 14 08:36:53 2019 From: phracek at redhat.com (Petr Hracek) Date: Mon, 14 Oct 2019 10:36:53 +0200 Subject: [scl.org] SCL and Ansible ? In-Reply-To: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> References: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> Message-ID: Hi Samuel, I have been writing a couple of ansible-playbooks but did not try it with SCL. You playbook w/o comments look good. But I don't understand the scenario. How do you run the ansible-playbook? >From container or from shell? Can you please give a reproducer steps, so I can analyze it? Greetings Petr p? 11. 10. 2019 v 11:23 odes?latel napsal: > Dear all, > > Silly question: is there a way to call "scl enable" from within an Ansible > role ? > > So far we've been trying the command, shell and scripts modules, but to no > avail... > > > https://docs.ansible.com/ansible/latest/modules/command_module.html#command-module > > https://docs.ansible.com/ansible/latest/modules/shell_module.html#shell-module > > https://docs.ansible.com/ansible/latest/modules/script_module.html#script-module > > Here are some failed attempts: > > - name: Start using the software collection for maven > shell: scl_enabled rh-maven35 > register: swap_exists > ignore_errors: true > #script: test.sh > # shell: scl enable /etc/scl/conf//opt/rh/rh-maven35 bash && echo toto > #shell: /usr/bin/scl enable rh-maven35 bash > # args: > # warn: yes > # chdir: "{{ path_to_pastis }}" > #easy_install: > # name: scl > # args: > # executable: "/usr/bin/scl enable rh-maven35 bash" > # command: | > # /usr/bin/scl enable rh-maven35 bash > #bash > # shell: | > # scl enable rh-maven35 bash > #bash > # args: > # executable: /bin/bash > > I think the root issue is that, as far as I understand, "scl enable" > starts a new shell and sources environment variables in there, while > Ansible is still waiting for some RC in the parent shell. Thus Ansible is > not really failing, but just keeps on waiting for ever... > > Any help would be greatly appreciated. > > Best regards, > > Samuel from CINES > > https://www.cines.fr/en/ > > -- > > Samuel VISCAPI > > +33(0)4 67 14 14 36 > viscapi at cines.fr > IM: sviscapi (Skype) > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -- Petr Hracek email: phracek at redhat.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From viscapi at cines.fr Tue Oct 15 12:17:15 2019 From: viscapi at cines.fr (viscapi at cines.fr) Date: Tue, 15 Oct 2019 14:17:15 +0200 (CEST) Subject: [scl.org] SCL and Ansible ? In-Reply-To: References: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> Message-ID: <58693694.14078774.1571141835599.JavaMail.zimbra@cines.fr> Hi all, @Petr: we are running the playbook from the shell. Launching "scl enable" through the shell / command / script modules doesn't work AFAIK (Ansible never returns). Last week I tried sourcing /opt/rh/rh-maven35/enable, and it seems to be roughly equivalent to running "scl enable". Thus I compared the environment variables before and after sourcing that file, and came up with this: - name: check version maven command: /opt/rh/rh-maven35/root/usr/bin/mvn --version environment: MANPATH: "/opt/rh/rh-maven35/root/usr/share/man" JAVACONFDIRS: "/opt/rh/rh-maven35/root/etc/java" XDG_CONFIG_DIRS: "/opt/rh/rh-maven35/root/etc/xdg:/etc/xdg" PATH: "/opt/rh/rh-maven35/root/usr/bin:{{ ansible_env.PATH }}" PYTHONPATH: "/opt/rh/rh-maven35/root/usr/lib/python2.7/site-packages" XDG_DATA_DIRS: "/opt/rh/rh-maven35/root/usr/share:/usr/local/share:/usr/share" register: version - debug: msg: '{{ version }}' And the output reads as follows: TASK [scl-test : debug] ******************************************************** ok: [sandbox55-adm.cines.fr] => { "msg": { "changed": true, "cmd": [ "/opt/rh/rh-maven35/root/usr/bin/mvn", "--version" ], "delta": "0:00:01.864600", "end": "2019-10-15 12:15:03.549450", "failed": false, "rc": 0, "start": "2019-10-15 12:15:01.684850", "stderr": "", "stderr_lines": [], "stdout": "\u001b[1mApache Maven 3.5.0 (Red Hat 3.5.0-4.3)\u001b[m\nMaven home: /opt/rh/rh-maven35/root/usr/share/maven\nJava version: 1.8.0_222, vendor: Oracle Corporation\nJava home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64/jre\nDefault locale: fr_FR, platform encoding: UTF-8\nOS name: \"linux\", version: \"3.10.0-1062.1.1.el7.x86_64\", arch: \"amd64\", family: \"unix\"", "stdout_lines": [ "\u001b[1mApache Maven 3.5.0 (Red Hat 3.5.0-4.3)\u001b[m", "Maven home: /opt/rh/rh-maven35/root/usr/share/maven", "Java version: 1.8.0_222, vendor: Oracle Corporation", "Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64/jre", "Default locale: fr_FR, platform encoding: UTF-8", "OS name: \"linux\", version: \"3.10.0-1062.1.1.el7.x86_64\", arch: \"amd64\", family: \"unix\"" ] } } Looks like I can run Maven 3.5 with the correct environment variables that way. The problem is that this workaround just doesn't scale, as we'd have to analyse the "enable" script coming with every SCL package. At first I thought I could just store the contents of that script in an Ansible variable and pipe it to some Ansible filters ( | to_yaml for example), hoping it would automagically turn my Bash variables into Ansible variables... https://docs.ansible.com/ansible/latest/user_guide/playbooks_filters.html I was obviously wrong... Opinions are welcome :) Cheers, Samuel -- Samuel VISCAPI +33(0)4 67 14 14 36 viscapi at cines.fr IM: sviscapi (Skype) ----- Mail original ----- De: "Petr Hracek" ?: "viscapi" Cc: "sclorg" , "caux" Envoy?: Lundi 14 Octobre 2019 10:36:53 Objet: Re: [scl.org] SCL and Ansible ? Hi Samuel, I have been writing a couple of ansible-playbooks but did not try it with SCL. You playbook w/o comments look good. But I don't understand the scenario. How do you run the ansible-playbook? >From container or from shell? Can you please give a reproducer steps, so I can analyze it? Greetings Petr p? 11. 10. 2019 v 11:23 odes?latel napsal: > Dear all, > > Silly question: is there a way to call "scl enable" from within an Ansible > role ? > > So far we've been trying the command, shell and scripts modules, but to no > avail... > > > https://docs.ansible.com/ansible/latest/modules/command_module.html#command-module > > https://docs.ansible.com/ansible/latest/modules/shell_module.html#shell-module > > https://docs.ansible.com/ansible/latest/modules/script_module.html#script-module > > Here are some failed attempts: > > - name: Start using the software collection for maven > shell: scl_enabled rh-maven35 > register: swap_exists > ignore_errors: true > #script: test.sh > # shell: scl enable /etc/scl/conf//opt/rh/rh-maven35 bash && echo toto > #shell: /usr/bin/scl enable rh-maven35 bash > # args: > # warn: yes > # chdir: "{{ path_to_pastis }}" > #easy_install: > # name: scl > # args: > # executable: "/usr/bin/scl enable rh-maven35 bash" > # command: | > # /usr/bin/scl enable rh-maven35 bash > #bash > # shell: | > # scl enable rh-maven35 bash > #bash > # args: > # executable: /bin/bash > > I think the root issue is that, as far as I understand, "scl enable" > starts a new shell and sources environment variables in there, while > Ansible is still waiting for some RC in the parent shell. Thus Ansible is > not really failing, but just keeps on waiting for ever... > > Any help would be greatly appreciated. > > Best regards, > > Samuel from CINES > > https://www.cines.fr/en/ > > -- > > Samuel VISCAPI > > +33(0)4 67 14 14 36 > viscapi at cines.fr > IM: sviscapi (Skype) > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -- Petr Hracek email: phracek at redhat.com From pvalena at redhat.com Tue Oct 15 13:02:54 2019 From: pvalena at redhat.com (Pavel Valena) Date: Tue, 15 Oct 2019 09:02:54 -0400 (EDT) Subject: [scl.org] SCL and Ansible ? In-Reply-To: <58693694.14078774.1571141835599.JavaMail.zimbra@cines.fr> References: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> <58693694.14078774.1571141835599.JavaMail.zimbra@cines.fr> Message-ID: <1897630456.3866993.1571144574239.JavaMail.zimbra@redhat.com> ----- Original Message ----- > From: viscapi at cines.fr > To: "Petr Hracek" > Cc: "caux" , "sclorg" > Sent: Tuesday, October 15, 2019 2:17:15 PM > Subject: Re: [scl.org] SCL and Ansible ? > > Hi all, > > @Petr: we are running the playbook from the shell. Launching "scl enable" > through the shell / command / script modules doesn't work AFAIK (Ansible > never returns). Last week I tried sourcing /opt/rh/rh-maven35/enable, and it > seems to be roughly equivalent to running "scl enable". Thus I compared the > environment variables before and after sourcing that file, and came up with > this: Hello, sorry to repeat myself, but couldn't you simply run the following? ``` command: scl enable rh-maven35 -- maven --version ``` If it fails, what's the output? Alternatively, could you change the shell used to run a custom one, like we do in container images? https://github.com/sclorg/s2i-base-container/blob/master/core/Dockerfile#L35 https://github.com/sclorg/s2i-ruby-container/blob/master/2.5/root/opt/app-root/etc/scl_enable Cheers, Pavel > > - name: check version maven > command: /opt/rh/rh-maven35/root/usr/bin/mvn --version > environment: > MANPATH: "/opt/rh/rh-maven35/root/usr/share/man" > JAVACONFDIRS: "/opt/rh/rh-maven35/root/etc/java" > XDG_CONFIG_DIRS: "/opt/rh/rh-maven35/root/etc/xdg:/etc/xdg" > PATH: "/opt/rh/rh-maven35/root/usr/bin:{{ ansible_env.PATH }}" > PYTHONPATH: "/opt/rh/rh-maven35/root/usr/lib/python2.7/site-packages" > XDG_DATA_DIRS: > "/opt/rh/rh-maven35/root/usr/share:/usr/local/share:/usr/share" > register: version > > - debug: > msg: '{{ version }}' > > And the output reads as follows: > > TASK [scl-test : debug] > ******************************************************** > ok: [sandbox55-adm.cines.fr] => { > "msg": { > "changed": true, > "cmd": [ > "/opt/rh/rh-maven35/root/usr/bin/mvn", > "--version" > ], > "delta": "0:00:01.864600", > "end": "2019-10-15 12:15:03.549450", > "failed": false, > "rc": 0, > "start": "2019-10-15 12:15:01.684850", > "stderr": "", > "stderr_lines": [], > "stdout": "\u001b[1mApache Maven 3.5.0 (Red Hat > 3.5.0-4.3)\u001b[m\nMaven home: > /opt/rh/rh-maven35/root/usr/share/maven\nJava version: 1.8.0_222, > vendor: Oracle Corporation\nJava home: > /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64/jre\nDefault > locale: fr_FR, platform encoding: UTF-8\nOS name: \"linux\", > version: \"3.10.0-1062.1.1.el7.x86_64\", arch: \"amd64\", family: > \"unix\"", > "stdout_lines": [ > "\u001b[1mApache Maven 3.5.0 (Red Hat 3.5.0-4.3)\u001b[m", > "Maven home: /opt/rh/rh-maven35/root/usr/share/maven", > "Java version: 1.8.0_222, vendor: Oracle Corporation", > "Java home: > /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64/jre", > "Default locale: fr_FR, platform encoding: UTF-8", > "OS name: \"linux\", version: \"3.10.0-1062.1.1.el7.x86_64\", > arch: \"amd64\", family: \"unix\"" > ] > } > } > > Looks like I can run Maven 3.5 with the correct environment variables that > way. The problem is that this workaround just doesn't scale, as we'd have to > analyse the "enable" script coming with every SCL package. At first I > thought I could just store the contents of that script in an Ansible > variable and pipe it to some Ansible filters ( | to_yaml for example), > hoping it would automagically turn my Bash variables into Ansible > variables... > > https://docs.ansible.com/ansible/latest/user_guide/playbooks_filters.html > > I was obviously wrong... > > Opinions are welcome :) > > Cheers, Samuel > > -- > > Samuel VISCAPI > > +33(0)4 67 14 14 36 > viscapi at cines.fr > IM: sviscapi (Skype) > > ----- Mail original ----- > De: "Petr Hracek" > ?: "viscapi" > Cc: "sclorg" , "caux" > Envoy?: Lundi 14 Octobre 2019 10:36:53 > Objet: Re: [scl.org] SCL and Ansible ? > > Hi Samuel, > > I have been writing a couple of ansible-playbooks but did not try it with > SCL. > You playbook w/o comments look good. > > But I don't understand the scenario. > How do you run the ansible-playbook? > >From container or from shell? > > Can you please give a reproducer steps, so I can analyze it? > > Greetings > Petr > > > p? 11. 10. 2019 v 11:23 odes?latel napsal: > > > Dear all, > > > > Silly question: is there a way to call "scl enable" from within an Ansible > > role ? > > > > So far we've been trying the command, shell and scripts modules, but to no > > avail... > > > > > > https://docs.ansible.com/ansible/latest/modules/command_module.html#command-module > > > > https://docs.ansible.com/ansible/latest/modules/shell_module.html#shell-module > > > > https://docs.ansible.com/ansible/latest/modules/script_module.html#script-module > > > > Here are some failed attempts: > > > > - name: Start using the software collection for maven > > shell: scl_enabled rh-maven35 > > register: swap_exists > > ignore_errors: true > > #script: test.sh > > # shell: scl enable /etc/scl/conf//opt/rh/rh-maven35 bash && echo toto > > #shell: /usr/bin/scl enable rh-maven35 bash > > # args: > > # warn: yes > > # chdir: "{{ path_to_pastis }}" > > #easy_install: > > # name: scl > > # args: > > # executable: "/usr/bin/scl enable rh-maven35 bash" > > # command: | > > # /usr/bin/scl enable rh-maven35 bash > > #bash > > # shell: | > > # scl enable rh-maven35 bash > > #bash > > # args: > > # executable: /bin/bash > > > > I think the root issue is that, as far as I understand, "scl enable" > > starts a new shell and sources environment variables in there, while > > Ansible is still waiting for some RC in the parent shell. Thus Ansible is > > not really failing, but just keeps on waiting for ever... > > > > Any help would be greatly appreciated. > > > > Best regards, > > > > Samuel from CINES > > > > https://www.cines.fr/en/ > > > > -- > > > > Samuel VISCAPI > > > > +33(0)4 67 14 14 36 > > viscapi at cines.fr > > IM: sviscapi (Skype) > > > > _______________________________________________ > > SCLorg mailing list > > SCLorg at redhat.com > > https://www.redhat.com/mailman/listinfo/sclorg > > > > > -- > Petr Hracek > email: phracek at redhat.com > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -- Pavel Valena Software Engineer, Red Hat Brno, Czech Republic From viscapi at cines.fr Tue Oct 15 13:30:53 2019 From: viscapi at cines.fr (viscapi at cines.fr) Date: Tue, 15 Oct 2019 15:30:53 +0200 (CEST) Subject: [scl.org] SCL and Ansible ? In-Reply-To: <1897630456.3866993.1571144574239.JavaMail.zimbra@redhat.com> References: <537260429.376722.1570785766366.JavaMail.zimbra@cines.fr> <58693694.14078774.1571141835599.JavaMail.zimbra@cines.fr> <1897630456.3866993.1571144574239.JavaMail.zimbra@redhat.com> Message-ID: <1872492207.14143992.1571146253465.JavaMail.zimbra@cines.fr> Hi Pavel, Sorry for the late reply. Your suggestion is indeed working :) TASK [scl-test : debug] ******************************************************** ok: [sandbox55-adm.cines.fr] => { "msg": { "changed": true, "cmd": [ "scl", "enable", "rh-maven35", "--", "mvn", "--version" ], "delta": "0:00:00.578223", "end": "2019-10-15 15:28:40.646710", "failed": false, "rc": 0, "start": "2019-10-15 15:28:40.068487", "stderr": "", "stderr_lines": [], "stdout": "\u001b[1mApache Maven 3.5.0 (Red Hat 3.5.0-4.3)\u001b[m\nMaven home: /opt/rh/rh-maven35/root/usr/share/maven\nJava version: 1.8.0_222, vendor: Oracle Corporation\nJava home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64/jre\nDefault locale: fr_FR, platform encoding: UTF-8\nOS name: \"linux\", version: \"3.10.0-1062.1.1.el7.x86_64\", arch: \"amd64\", family: \"unix\"", "stdout_lines": [ "\u001b[1mApache Maven 3.5.0 (Red Hat 3.5.0-4.3)\u001b[m", "Maven home: /opt/rh/rh-maven35/root/usr/share/maven", "Java version: 1.8.0_222, vendor: Oracle Corporation", "Java home: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64/jre", "Default locale: fr_FR, platform encoding: UTF-8", "OS name: \"linux\", version: \"3.10.0-1062.1.1.el7.x86_64\", arch: \"amd64\", family: \"unix\"" ] } } Thanks a lot for your help ! Cheers, Samuel -- Samuel VISCAPI +33(0)4 67 14 14 36 viscapi at cines.fr IM: sviscapi (Skype) ----- Mail original ----- De: "Pavel Valena" ?: "viscapi" Cc: "Petr Hracek" , "caux" , "sclorg" Envoy?: Mardi 15 Octobre 2019 15:02:54 Objet: Re: [scl.org] SCL and Ansible ? ----- Original Message ----- > From: viscapi at cines.fr > To: "Petr Hracek" > Cc: "caux" , "sclorg" > Sent: Tuesday, October 15, 2019 2:17:15 PM > Subject: Re: [scl.org] SCL and Ansible ? > > Hi all, > > @Petr: we are running the playbook from the shell. Launching "scl enable" > through the shell / command / script modules doesn't work AFAIK (Ansible > never returns). Last week I tried sourcing /opt/rh/rh-maven35/enable, and it > seems to be roughly equivalent to running "scl enable". Thus I compared the > environment variables before and after sourcing that file, and came up with > this: Hello, sorry to repeat myself, but couldn't you simply run the following? ``` command: scl enable rh-maven35 -- maven --version ``` If it fails, what's the output? Alternatively, could you change the shell used to run a custom one, like we do in container images? https://github.com/sclorg/s2i-base-container/blob/master/core/Dockerfile#L35 https://github.com/sclorg/s2i-ruby-container/blob/master/2.5/root/opt/app-root/etc/scl_enable Cheers, Pavel > > - name: check version maven > command: /opt/rh/rh-maven35/root/usr/bin/mvn --version > environment: > MANPATH: "/opt/rh/rh-maven35/root/usr/share/man" > JAVACONFDIRS: "/opt/rh/rh-maven35/root/etc/java" > XDG_CONFIG_DIRS: "/opt/rh/rh-maven35/root/etc/xdg:/etc/xdg" > PATH: "/opt/rh/rh-maven35/root/usr/bin:{{ ansible_env.PATH }}" > PYTHONPATH: "/opt/rh/rh-maven35/root/usr/lib/python2.7/site-packages" > XDG_DATA_DIRS: > "/opt/rh/rh-maven35/root/usr/share:/usr/local/share:/usr/share" > register: version > > - debug: > msg: '{{ version }}' > > And the output reads as follows: > > TASK [scl-test : debug] > ******************************************************** > ok: [sandbox55-adm.cines.fr] => { > "msg": { > "changed": true, > "cmd": [ > "/opt/rh/rh-maven35/root/usr/bin/mvn", > "--version" > ], > "delta": "0:00:01.864600", > "end": "2019-10-15 12:15:03.549450", > "failed": false, > "rc": 0, > "start": "2019-10-15 12:15:01.684850", > "stderr": "", > "stderr_lines": [], > "stdout": "\u001b[1mApache Maven 3.5.0 (Red Hat > 3.5.0-4.3)\u001b[m\nMaven home: > /opt/rh/rh-maven35/root/usr/share/maven\nJava version: 1.8.0_222, > vendor: Oracle Corporation\nJava home: > /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64/jre\nDefault > locale: fr_FR, platform encoding: UTF-8\nOS name: \"linux\", > version: \"3.10.0-1062.1.1.el7.x86_64\", arch: \"amd64\", family: > \"unix\"", > "stdout_lines": [ > "\u001b[1mApache Maven 3.5.0 (Red Hat 3.5.0-4.3)\u001b[m", > "Maven home: /opt/rh/rh-maven35/root/usr/share/maven", > "Java version: 1.8.0_222, vendor: Oracle Corporation", > "Java home: > /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.222.b10-1.el7_7.x86_64/jre", > "Default locale: fr_FR, platform encoding: UTF-8", > "OS name: \"linux\", version: \"3.10.0-1062.1.1.el7.x86_64\", > arch: \"amd64\", family: \"unix\"" > ] > } > } > > Looks like I can run Maven 3.5 with the correct environment variables that > way. The problem is that this workaround just doesn't scale, as we'd have to > analyse the "enable" script coming with every SCL package. At first I > thought I could just store the contents of that script in an Ansible > variable and pipe it to some Ansible filters ( | to_yaml for example), > hoping it would automagically turn my Bash variables into Ansible > variables... > > https://docs.ansible.com/ansible/latest/user_guide/playbooks_filters.html > > I was obviously wrong... > > Opinions are welcome :) > > Cheers, Samuel > > -- > > Samuel VISCAPI > > +33(0)4 67 14 14 36 > viscapi at cines.fr > IM: sviscapi (Skype) > > ----- Mail original ----- > De: "Petr Hracek" > ?: "viscapi" > Cc: "sclorg" , "caux" > Envoy?: Lundi 14 Octobre 2019 10:36:53 > Objet: Re: [scl.org] SCL and Ansible ? > > Hi Samuel, > > I have been writing a couple of ansible-playbooks but did not try it with > SCL. > You playbook w/o comments look good. > > But I don't understand the scenario. > How do you run the ansible-playbook? > >From container or from shell? > > Can you please give a reproducer steps, so I can analyze it? > > Greetings > Petr > > > p? 11. 10. 2019 v 11:23 odes?latel napsal: > > > Dear all, > > > > Silly question: is there a way to call "scl enable" from within an Ansible > > role ? > > > > So far we've been trying the command, shell and scripts modules, but to no > > avail... > > > > > > https://docs.ansible.com/ansible/latest/modules/command_module.html#command-module > > > > https://docs.ansible.com/ansible/latest/modules/shell_module.html#shell-module > > > > https://docs.ansible.com/ansible/latest/modules/script_module.html#script-module > > > > Here are some failed attempts: > > > > - name: Start using the software collection for maven > > shell: scl_enabled rh-maven35 > > register: swap_exists > > ignore_errors: true > > #script: test.sh > > # shell: scl enable /etc/scl/conf//opt/rh/rh-maven35 bash && echo toto > > #shell: /usr/bin/scl enable rh-maven35 bash > > # args: > > # warn: yes > > # chdir: "{{ path_to_pastis }}" > > #easy_install: > > # name: scl > > # args: > > # executable: "/usr/bin/scl enable rh-maven35 bash" > > # command: | > > # /usr/bin/scl enable rh-maven35 bash > > #bash > > # shell: | > > # scl enable rh-maven35 bash > > #bash > > # args: > > # executable: /bin/bash > > > > I think the root issue is that, as far as I understand, "scl enable" > > starts a new shell and sources environment variables in there, while > > Ansible is still waiting for some RC in the parent shell. Thus Ansible is > > not really failing, but just keeps on waiting for ever... > > > > Any help would be greatly appreciated. > > > > Best regards, > > > > Samuel from CINES > > > > https://www.cines.fr/en/ > > > > -- > > > > Samuel VISCAPI > > > > +33(0)4 67 14 14 36 > > viscapi at cines.fr > > IM: sviscapi (Skype) > > > > _______________________________________________ > > SCLorg mailing list > > SCLorg at redhat.com > > https://www.redhat.com/mailman/listinfo/sclorg > > > > > -- > Petr Hracek > email: phracek at redhat.com > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > -- Pavel Valena Software Engineer, Red Hat Brno, Czech Republic From jstanek at redhat.com Tue Oct 29 13:22:21 2019 From: jstanek at redhat.com (=?UTF-8?Q?Jan_Stan=c4=9bk?=) Date: Tue, 29 Oct 2019 14:22:21 +0100 Subject: [scl.org] Community (sclo-) collections on alternate architectures Message-ID: <5e4c178e-ec57-efed-78f5-dde1a2a00bd8@redhat.com> Hello everyone! It has recently been brought to my attention that we have no sclo-prefixed collection synchronized on mirrors for alternate architectures ? only on x86_64. I went through several sclo- collections and it seems this could be caused by not having any builds of them since the alternate architectures were enabled in CBS. I already spoke with Remi Collet (CC'd) about his PHP collections and he agreed to have them rebuilt and synchronized to the aarch64 and ppc64le architectures as well. What about the others? If you maintain a (released) sclo- collection, would you be willing to rebuild it for the alternate architectures? Nothing major should be required, apart from (re-)bulding the collection packages in the correct order (since for the altarchs, the collection needs to be bootstrapped if necessary). I would be more than happy to lend you my aid, should you need it. Looking forward to your responses and comments! -- Jan Stan?k Associate Software Engineer Red Hat EMEA jstanek at redhat.com IM: jstanek