From apurty at redhat.com Wed Apr 1 05:41:57 2020 From: apurty at redhat.com (Abhinay Purty) Date: Wed, 1 Apr 2020 11:11:57 +0530 Subject: [scl.org] Queries regarding nodejs 12 image In-Reply-To: References: Message-ID: Thanks for the update @Honza Horak . On Thu, Mar 26, 2020 at 7:18 PM Honza Horak wrote: > Version nodejs v12.16.1 is already available in the container, the > updated container was released few days back. > > Regards, > Honza > > On 3/25/20 7:14 AM, Abhinay Purty wrote: > > Hello, > > > > Any updates on the last 2 queries ? > > > > Thanks in advance. > > > > On Thu, Mar 19, 2020 at 4:46 PM Abhinay Purty > > wrote: > > > > @ Petr, Thanks for the update and opening up a ticket for the > > mentioned issue. > > > > On Thu, Mar 19, 2020 at 1:37 PM Petr Kubat > > wrote: > > > > Hi Abhinay, > > > > On 3/19/20 8:28 AM, Abhinay Purty wrote: > >> Hello Team, > >> > >> IHAC with a few queries. > >> > >> 1. Does the following images contain the security fixes that > >> is mentioned in > >> ' > https://nodejs.org/en/blog/vulnerability/february-2020-security-releases' > >> (CVE-2019-15604, CVE-2019-15605, CVE-2019-15606)? [*] > >> > https://access.redhat.com/containers/#/registry.access.redhat.com/ubi8/nodejs-12 > >> [*] > >> > https://access.redhat.com/containers/#/registry.access.redhat.com/rhel8/nodejs-12 > >> If I understand correctly, the latest version of those images > >> are built before security fixes CVE-2019-15604[1], > >> CVE-2019-15605[2], CVE-2019-15606[3] were released. [1] > >> https://access.redhat.com/security/cve/CVE-2019-15604 [2] > >> https://access.redhat.com/security/cve/CVE-2019-15605 [3] > >> https://access.redhat.com/security/cve/CVE-2019-15606 > > > > The released images seem to be affected by the CVEs mentioned, > > but do not show up as such in the catalog. This is a problem and > > I have opened up a ticket against container grading to check > > what went wrong: > > > https://projects.engineering.redhat.com/projects/GRADING/issues/GRADING-125 > > > > The CVEs will soon be fixed (I have checked fixed builds are > > present) once the following advisory gets pushed: > > https://errata.devel.redhat.com/advisory/52592 > > > > > >> 2. Is there any plans to release ubi8/nodejs-12 and > >> rhel8/nodejs-12 s2i builder images that would include current > >> LTS version of nodejs (12.16.1)? 3. Does the ubi8/nodejs-12 > >> and rhel8/nodejs-12 have vanilla installation of the nodejs > >> runtime? Or is the nodejs runtime in those images Red Hat's > >> own implementation of the nodejs runtime ? > > > > I will leave these two to be answered by nodejs maintainers > > (added to CC). > > > > Petr > > > >> > >> > >> -- > >> Regards, > >> > >> Abhinay Purty > >> > >> Associate Technical Support Engineer > >> > >> Red Hat India Pvt. Ltd. > >> > >> > >> > >> _______________________________________________ > >> SCLorg mailing list > >> SCLorg at redhat.com > >> https://www.redhat.com/mailman/listinfo/sclorg > > > > > > > > -- > > Regards, > > > > Abhinay Purty > > > > Associate Technical Support Engineer > > > > Red Hat India Pvt. Ltd. > > > > > > > > > > > > -- > > Regards, > > > > Abhinay Purty > > > > Associate Technical Support Engineer > > > > Red Hat India Pvt. Ltd. > > > > > > > > _______________________________________________ > > SCLorg mailing list > > SCLorg at redhat.com > > https://www.redhat.com/mailman/listinfo/sclorg > > > > -- Regards, Abhinay Purty Associate Technical Support Engineer Red Hat India Pvt. Ltd. -------------- next part -------------- An HTML attachment was scrubbed... URL: From quent.haas at gmail.com Thu Apr 9 13:22:33 2020 From: quent.haas at gmail.com (Nicholas Haas) Date: Thu, 9 Apr 2020 09:22:33 -0400 Subject: [scl.org] llvm-toolset-7.0 for ppc64le Message-ID: Greetings, I'm using CentOS 7 on a ppc64le (power9) system. While the x86-64 scl repository enabled by 'centos-release-scl' on x86-64 CentOS7 has the 'llvm-toolset-7.0' package, the repository for ppc64le based systems does not. Upstream supports ppc64le in their Developer Toolset series. Any chance of ppc64le being enabled for EL7 users in the future for llvm-toolset-7 or newer? Thanks References: SCL devtoolset 7 page: https://www.softwarecollections.org/en/scls/rhscl/llvm-toolset-7.0/ From giacomo.sanchietti at nethesis.it Fri Apr 10 07:54:48 2020 From: giacomo.sanchietti at nethesis.it (Giacomo Sanchietti) Date: Fri, 10 Apr 2020 09:54:48 +0200 Subject: [scl.org] CentOS 7.8.2003 and sclo-php72-php-pecl-imagic Message-ID: Hello, my name is Giacomo Sanchietti and I'm part of NethServer project which is based on CentOS. I've started testing the upgrade from 7.7.1908 to 7.8.2003 using CR repository, and I've found a little dependency issue. I hope this is the right place to report it, otherwise please point me to right direction. We have have a bunch of machines with the following packages installed: - sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 - sclo-php73-php-pecl-imagick-3.4.4-2.el7.x86_64 When updating with cr repository yum complains about ImageMagick (the same error applies also to php73): Error: Package: sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 (@centos-sclo-sclo) Requires: libMagickWand.so.5()(64bit) Removing: ImageMagick-6.7.8.9-18.el7.x86_64 (@base) libMagickWand.so.5()(64bit) Updated By: ImageMagick-6.9.10.68-3.el7.x86_64 (cr) Not found Maybe it's a just a matter to recompile the RPM with the new ImageMagick release? Thanks in advance From Fedora at famillecollet.com Fri Apr 10 08:27:27 2020 From: Fedora at famillecollet.com (Remi Collet) Date: Fri, 10 Apr 2020 10:27:27 +0200 Subject: [scl.org] CentOS 7.8.2003 and sclo-php72-php-pecl-imagic In-Reply-To: References: Message-ID: <90244142-4906-f8cb-42c4-fc059e5bbf5f@FamilleCollet.com> Hi, Le 10/04/2020 ? 09:54, Giacomo Sanchietti a ?crit?: > Hello, > my name is Giacomo Sanchietti and I'm part of NethServer project which > is based on CentOS. > > I've started testing the upgrade from 7.7.1908 to 7.8.2003 using CR > repository, and I've found a little dependency issue. I hope this is the > right place to report it, otherwise please point me to right direction. > > We have have a bunch of machines with the following packages installed: > - sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 > - sclo-php73-php-pecl-imagick-3.4.4-2.el7.x86_64 > > When updating with cr repository yum complains about ImageMagick (the > same error applies also to php73): > > Error: Package: sclo-php72-php-pecl-imagick-3.4.4-1.el7.x86_64 > (@centos-sclo-sclo) > ?????????? Requires: libMagickWand.so.5()(64bit) > ?????????? Removing: ImageMagick-6.7.8.9-18.el7.x86_64 (@base) > ?????????????? libMagickWand.so.5()(64bit) > ?????????? Updated By: ImageMagick-6.9.10.68-3.el7.x86_64 (cr) > ?????????????? Not found > > Maybe it's a just a matter to recompile the RPM with the new ImageMagick > release? Indeed. New build are done, and should be soon in "testing" repository I plan to push them in "stable" only after 7.8 official release. Remi > > Thanks in advance > > > _______________________________________________ > SCLorg mailing list > SCLorg at redhat.com > https://www.redhat.com/mailman/listinfo/sclorg > From giacomo.sanchietti at nethesis.it Fri Apr 10 10:59:35 2020 From: giacomo.sanchietti at nethesis.it (Giacomo Sanchietti) Date: Fri, 10 Apr 2020 12:59:35 +0200 Subject: [scl.org] CentOS 7.8.2003 and sclo-php72-php-pecl-imagic In-Reply-To: <90244142-4906-f8cb-42c4-fc059e5bbf5f@FamilleCollet.com> References: <90244142-4906-f8cb-42c4-fc059e5bbf5f@FamilleCollet.com> Message-ID: <619fee14-7d2a-b5e0-6272-5ae0ab2f8c74@nethesis.it> Hello, > New build are done, and should be soon in "testing" repository I confirm the problem is solved with packages from buildlogs.centos.org. Thank you for the quick fix! From jstanek at redhat.com Wed Apr 15 09:25:57 2020 From: jstanek at redhat.com (=?UTF-8?Q?Jan_Stan=c4=9bk?=) Date: Wed, 15 Apr 2020 11:25:57 +0200 Subject: [scl.org] llvm-toolset-7.0 for ppc64le In-Reply-To: References: Message-ID: Hi Nicolas, the llvm-toolset-7.0 is being built for ppc64le, and you should be able to consume the resulting RPMs from the testing repository (`centos-sclo-rh-testing`). The CentOS infrastructure is currently undergoing changes in the process of synchronizing packages from the build system to repositories, so I cannot give you a definite date when the RPMs will reach the stable repositories ? but it will hopefully not take long. Best regards, -- Jan Stan?k Software Engineer Red Hat EMEA jstanek at redhat.com IM: jstanek -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From james.flemer at ndpgroup.com Fri Apr 17 22:30:13 2020 From: james.flemer at ndpgroup.com (James Flemer) Date: Fri, 17 Apr 2020 16:30:13 -0600 Subject: [scl.org] [PATCH] Make rh-python36-python-pip use system ca cert trust (vs embedded) In-Reply-To: References: Message-ID: Hi All, I hope this is an appropriate channel for patch submissions. Here is a patch that mirrors the base "python3-pip" approach to use the system CA cert trust file, rather than the one that gets embedded into pip via the Requests/Certifi packages. This is preferable because it lets pip pickup locally administered CA trust (e.g. certs issued by an internal CA). This helps immensely when running a private secure pip/pypy repo! This should be testable by comparing the output of these two commands: scl enable rh-python36 'python -mpip._vendor.requests.certs' python3 -mpip._vendor.requests.certs The output if pip is using bundled certs is something like: /opt/rh/rh-python36/root/usr/lib/python3.6/site-packages/pip/_vendor/requests/cacert.pem versus system certs: /etc/pki/tls/certs/ca-bundle.crt A similar patch could probably be applied to prior SCL python (3.[345]). But I hope by getting it in 3.6, it will walk forward for 3.7+. The attached patch is public domain. attached: 0001-include-patch-from-python-pip-for-system-CA-cert-tru.patch Regards, James Flemer NDP 1909 26th Street, Suite 1E Boulder, Colorado 80302 Office: 720-897-7334 Cell: 970-217-3204 james.flemer at ndpgroup.com www.ndpgroup.com -- Confidential, proprietary, and/or privileged information may be contained in, and attached to, this message.? The information transmitted is intended only for the individual or entity to which it is addressed.? Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information in this transmission by persons or entities other than the intended recipient(s) is prohibited. If you received this transmission in error, please immediately contact the sender and delete the material from all computers. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-include-patch-from-python-pip-for-system-CA-cert-tru.patch Type: application/x-patch Size: 2733 bytes Desc: not available URL: From nmajorov at redhat.com Wed Apr 1 08:20:53 2020 From: nmajorov at redhat.com (Nikolaj Majorov) Date: Wed, 01 Apr 2020 08:20:53 -0000 Subject: [scl.org] s2i and podman Message-ID: Hi guys, does anybody can say if s2i image build tool can work only with podman ? it always required docker to run standalone. But how it works in openshift 4 ? with only cri-o support ? -- Beste Gr??e/Kind regards Nikolaj Majorov Middleware Domain Solution Architect Mobile: +41765351348 Mail: nmajorov at redhat.com Web: http://ch.redhat.com/ Red Hat Switzerland S?rl EUROPA ALLEE 41 8021 ZURICH --- Red Hat Tried. Tested. Trusted. http://www.redhat.com/en/about/trusted From Gunther.Vogel at ssw-trading.com Wed Apr 22 12:21:43 2020 From: Gunther.Vogel at ssw-trading.com (Gunther Vogel) Date: Wed, 22 Apr 2020 12:21:43 -0000 Subject: [scl.org] Status of devtoolset-9 for centos 6 Message-ID: Hi, are there plans for making official packages of devtoolset-9, in particular for centos 6? How mature are packages I get from centos-sclo-rh-testing, and will they continue to be available in the future? Can I do anything to help? Please accept my apologies if this is not the right mailing list. Regards, Gunther Vogel Lead Developer [ssw|trading] SSW-Trading GmbH Am Knick 4 22113 Oststeinbek, Germany T: +49 (0)40 607 708-342 F: +49 (0)40 607 708-198 E: gunther.vogel at ssw-trading.com Gesch?ftsf?hrer: Dr. Reto Gregory-Petersen, Jonas H?flich Gesellschaftssitz: Oststeinbek Registergericht: L?beck | Registernummer: HRB 7869HL -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 165 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 7240 bytes Desc: image002.jpg URL: From diego.abelenda at camptocamp.com Tue Apr 28 09:23:20 2020 From: diego.abelenda at camptocamp.com (Diego Abelenda) Date: Tue, 28 Apr 2020 09:23:20 -0000 Subject: [scl.org] Packages missing in SCLo Testing Repository on buildlogs Message-ID: <64613d85-3fa0-4d88-cdab-9ea8c3b9c29c@camptocamp.com> Hello, I am trying to sync SCLo Testing repository in Katello, to have a local mirror of the repository. And sadly Katello is unable to sync the repository because a number of packages are missing (I have contradictory error messages). Katello sync status is "New packages: 189 (187 MB). Failed to download 189 packages." and the Foreman Task error message is " An error occurred during the sync {"url"=>"https://buildlogs.centos.org/centos/7/sclo/x86_64/sclo/Packages/s/sclo-cassandra3-Cython-debuginfo-0.27.1-2.el7.x86_64.rpm", "errors"=>["Not Found"]} " Best regards, Diego Abelenda -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From bausonjc at ph.ibm.com Thu Apr 30 04:04:14 2020 From: bausonjc at ph.ibm.com (Jay Ar C Bauson - bausonjc@ph.ibm.com) Date: Thu, 30 Apr 2020 04:04:14 -0000 Subject: [scl.org] s2i php image Message-ID: <8b397d74a62944d2be8aa80ba5f06126@ph.ibm.com> Hi, I saw this email in `USING RED HAT SOFTWARE COLLECTIONS CONTAINER IMAGES` documentation. I would like to ask if it was intended that $_ENV are disabled for `registry.access.redhat.com/ubi8/php-73` The problem is that secrets are normally accessed via $_ENV and I am lost on how can I actually get or use my secrets iin my application. -------------- next part -------------- An HTML attachment was scrubbed... URL: