devel

devel@lists.centos.org

3 participants
4654 discussions

Re: [CentOS-devel] [CentOS] Firefox 60.0.1.0 ESR Progress?
by Phil Wyett 12 Jul '18

12 Jul '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 2018-07-11 at 13:36 -0500, Johnny Hughes wrote: > On 07/11/2018 08:28 AM, Phil Wyett wrote: > > On Wed, 2018-07-11 at 06:31 -0500, Johnny Hughes wrote: > > > On 07/09/2018 09:38 AM, Johnny Hughes wrote: > > > > On 07/06/2018 10:30 AM, Johnny Hughes wrote: > > > > > On 07/05/2018 02:27 PM, Phil Wyett wrote: > > > > > > On Thu, 2018-07-05 at 06:16 -0500, Johnny Hughes wrote: > > > > > > > On 07/03/2018 09:04 AM, Sean wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > <snip> > > > > > > > > > > > > > OK guys .. Firefox 60 is going to take some time .. likely more > > > > > > > for > > > > > > > CentOS-6 than CentOS-7. > > > > > > > They both (C6 and C7 versions) require many non OS tools to build. > > > > > > > For CentOS-7 .. we need the rust-toolset, llvm-toolset, and > > > > > > > devtoolset-7, to get the firefox to build. > > > > > > > > > > > > > > > > > > > > > > > > <snip> > > > > > > > > > > > > My current issue building the latest firefox is the required rust > > > > > > version. > > > > > > > > > > > > In the [sclo-rh] section of the epel-7 mock config I change line: > > > > > > > > > > > > includepkgs=devtoolset* > > > > > > > > > > > > to > > > > > > > > > > > > includepkgs=devtoolset* llvm-toolset* rust-toolset* > > > > > > > > > > > > Current rust is 1.20 and configure will stop asking for 1.24. > > > > > > > > > > > > > > > > indeed .. that is one issue. I am working on it .. we also have to do > > > > > i386 as that is released in the base OS .. so I have to get a working > > > > > devtoolset-7 for i386, ppc64, ppc as well .. and the latest rust and > > > > > the > > > > > latest llvm .. for i386, x86_64, ppc64le, ppc64, ppc, aarch64, armhfp > > > > > .. that is for C& > > > > > > > > > > I would just do x86_64 and i386 first, then the rest .. BUT .. since I > > > > > have to bootstrap the devtoolket and llvm and rust on c7 for i386 > > > > > anyway > > > > > .. also doig ti for the other arches does nto really add any more time > > > > > as the compiles are in parallel on different machines. > > > > > > > > > > Hopefully for C7 I will have updates by Monday > > > > > > > > > > For C6 .. I am going to need to rework rust, etc. .. that will take > > > > > longer .. rust requires python27 not python26 .. so lots of patches > > > > > are > > > > > going to be req'd for that. > > > > > > > > > > > > > This is a status update .. > > > > > > > > I now have the c7-devtoolkit-7 built for all arches (i386, x86_64, > > > > armhfp, aarch64, ppc64le, ppc64, ppc). > > > > > > > > I now have the c6-devtoolkit-7 built for all arches (i386. x86_64). > > > > > > > > I am in the process of building the latest llvm-toolkit and the > > > > rust-toolkit for CentOS 7 on all arches. (Both needed for firefox-60 on > > > > c7) > > > > > > > > I am in the process of figuring out all the changes needed to build the > > > > rust-toolkit for CentOS-6 as there is no released source code with the > > > > proper patches yet .. and it needs to be modified to build with the > > > > python used in EL6. > > > > > > > > So, hopefully very soon we will have all the required kits to build > > > > firefox for CentOS-7 .. CentOS-6 may be a bit longer. > > > > > > > Status currently is that I have a version built for CentOS-7 x86_64. > > > I am currently still building the require toolsets for i386 as > > > firefox.i686 is released as a multilib package in the x86_64 repo. > > > So, I can't release the x86_64 package without the i686 one. > > > You can download the x86_64 package manually if you don't want to wait > > > .. but I should have them both (i686 and x86_64) for CentOS-7 later today. > > > > > > The release of firefox will also include release of the scl toolsets for > > developers who modify and build for own needs? > > The SCL SIG releases SCLs and devtool sets // they are not part of the > OS, so no signed pieces will be released. > > I could put them on buildlogs for the el7 ones if there is interest. > > Hi Johnny, It would be good and appreciated if you could drop anything relevant on buildlogs. SCL Sig (on dev list), What is the ETA for releasing these updated packages by yourselves? Regards Phil - -- *** If this is a mailing list, I am subscribed, no need to CC me.*** Playing the game for the games sake. IRC: kathenas Web: https://kathenas.org Github: https://github.com/kathenas GitLab: https://gitlab.com/kathenas Twitter: kathenasorg GPG: A0C3 4C6A AC2B B8F4 F1E5 EDF4 333F 60DC B0B9 BB77 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJbRr/FAAoJEDM/YNywubt37ZAQAJZOzt/K0+wWoFh9dYXC/XDc 42+I1H8XLbZ1NbyXEowxFvz1dcgEG5kE4GOelm0ntxVIQShZwsSsnKUIAZ5zDqjE dy7jBIItVtnuy1cEup5mOcpbFsqNv2WVCc0DcUnttPbANj/Xuz6G+xOvB/haLm8X dfQIg5b6lRPp/dofezDlSod1IPTtri7gfV4HCsNldxY5pTzAwOfjP7Za8qOYHbzu oF9MV3P2LvFOLha9RqA7qUtvITIwmLwK49yknZ4LAo6thi6lzIyzsX4vZ93Ay6DE TVHOBkdOQSWRJMKjVYtmyw7fatwKmz136G31oOLI+EUSM7QaQY1yadJJlaogNY5R vFrGS2xHEp+anllacm6ZtiJDntMfpFvP6HpP0kQCB/t3nMWEhNVKWQyC/AkvK9MB jrUlrIqzCuRtE7+YClzLiH4b8PlJzOn1RakfuPkfGBciwBDOga415pfR62oUYqgH IiZslQAgTdQYEwzx13Pefa3Fnzz9JgbgqWJM85q86xRJ8Aexbt5pprMH2PUIq0EI Ca+h1w7k+lmiFvy+CKjkJLJVCFr/ONhKL0SjBkl/BiKdYXzsYBwdO5AuEU1KqAyP 0y3dMa98Gq0Pidldw3hZgVy1Tb4frUWGJPQmmTfONf47n/3URwkiV6B3la2Nmztx /b8HjS8Ad32FZtPdI4fW =sPBJ -----END PGP SIGNATURE-----

1 0

[Cloud SIG] Reminder meeting on Thursday 3pm UTC
by Haïkel 11 Jul '18

11 Jul '18

Hi, kind reminder that we will hold CentOS Cloud SIG meeting on #centos-devel on Freenode at 3pm UTC Regards, H.

1 0

NSS authentication issue in FIPS mode.
by Veetil, Vyshnav 11 Jul '18

11 Jul '18

Hi , In FIPS mode I was using "NSS FIPS 140-2 Certificate DB:mypassphrase" in /etc/ipsec.d/nsspassword and in my custom location. But it is failing with the below error in logs: Jun 27 12:36:11: authentication of "NSS FIPS 140-2 Certificate DB" failed Jun 27 12:36:11: FATAL: NSS initialization failure I was using CentOS Linux release 7.4.1708 (Core) with libreswan-3.20-3.el7.x86_64. Could you please help me to resolve this problem. Regards, Vyshnav

1 0

[SCLo SIG] new sclo-php*-php-pecl-redis4 packages available for testing
by Remi Collet 11 Jul '18

11 Jul '18

Yet another package available in centos-sclo-sclo-testing This extension provides an API for communicating with Redis servers. https://pecl.php.net/package/redis For rh-php71 (EL-7 only) * sclo-php71-php-pecl-redis4-4.1.0-1 For rh-php70 * sclo-php70-php-pecl-redis4-4.1.0-1 Notices: - this extension is already available, as sclo-php70-php-pecl-redis and sclo-php71-php-pecl-redis version 3.1.6. But as version 4 introduce some (minor) API changes, we choose to provide it as a separate package, giving users the choice to install v3 or v4. - both versions cannot be installed simultaneously. - new collections (e.g. PHP 7.2, 7.3, ...) will only provide the v4 package. - upstream Changelog: https://pecl.php.net/package-changelog.php?package=redis Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

CentOS Dojo @ CERN: CFP closes this weekend
by Rich Bowen 10 Jul '18

10 Jul '18

This is your final reminder that the Call For Papers for the CentOS Dojo at CERN closes at midnight on Sunday, July 15th. (If you're one of those people that asks "which timezone", then perhaps you're putting it off too long! ;-) But, I believe it's CET.) http://cern.ch/centos <--- Event details and call for abstracts are here. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

New version of moodle container available on registry.centos.org
by Mohammed Ahmed 09 Jul '18

09 Jul '18

Hi, Announcing availability of Moodle[1] container[2] for moodle version 3.5 now available on registry.centos.org. [1] https://moodle.org/ [2] https://registry.centos.org/centos/moodle -- *Mohammed Zeeshan Ahmed* Associate Software Engineer, Redhat Developers Team (Devtools) http://mzee1000.io https://mojo.redhat.com/people/moahmed RED HAT | DIFFERENT FOR THE SAKE OF BETTER TECHNOLOGY Find out why every airline, telecom, commercial bank, healthcare, and financial data services company in the Fortune 500 relies on Red Hat. Trusted | Red Hat <https://www.redhat.com/en/about/trusted>

1 0

SIGs: Possibility to drop EOL content at 6.10 release time
by Anssi Johansson 02 Jul '18

02 Jul '18

RHEL 6.10 was released today and building CentOS 6.10 has just started. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org. SIGs should explicitly state which content they want copied over from 6.9 to 6.10. I'd imagine that for example openstack-juno could be dropped because it went EOL in 2015-12-07 (so actually prior to CentOS 6.8's release..). Is there some other content that could be dropped? If SIGs want to transfer some of their packages from 6.9 to 6.10, please let hughesjr know. You can probably simply reply to this message to let people know of your decision. Content to be transferred over to 6.10 can be specified either by directory name, or by individual package names. There are also various centos-release-* packages in extras, http://mirror.centos.org/centos/6.9/extras/x86_64/Packages/ , perhaps some of those could be trimmed as well. You should also communicate to your users in advance that the EOL packages will disappear, and if necessary, instruct them to migrate to a newer supported version. Having instructions for that procedure published somewhere would be nice. The old content under 6.9, including any EOL content, will be archived to vault.centos.org, and that content will be available in the vault indefinitely. The 6.9 directory on mirror.centos.org will be emptied some time after 6.10 is released. For reference and inspiration, here are some directories from mirror.centos.org, including both up-to-date content and potentially EOL content. SIGs should review the list to make sure these directories can be copied over to 6.10 when that time comes. Making the decisions now would save a bit of time at 6.10 release time. cloud/x86_64/openstack-juno cloud/x86_64/openstack-juno/common sclo/x86_64/rh/devassist09 sclo/x86_64/rh/devtoolset-3 sclo/x86_64/rh/devtoolset-4 sclo/x86_64/rh/devtoolset-6 sclo/x86_64/rh/devtoolset-7 sclo/x86_64/rh/git19 sclo/x86_64/rh/httpd24 sclo/x86_64/rh/mariadb55 sclo/x86_64/rh/maven30 sclo/x86_64/rh/mongodb24 sclo/x86_64/rh/mysql55 sclo/x86_64/rh/nginx16 sclo/x86_64/rh/nodejs010 sclo/x86_64/rh/perl516 sclo/x86_64/rh/php54 sclo/x86_64/rh/php55 sclo/x86_64/rh/postgresql92 sclo/x86_64/rh/python27 sclo/x86_64/rh/python33 sclo/x86_64/rh/rh-git29 sclo/x86_64/rh/rh-java-common sclo/x86_64/rh/rh-mariadb100 sclo/x86_64/rh/rh-mariadb101 sclo/x86_64/rh/rh-mariadb102 sclo/x86_64/rh/rh-maven33 sclo/x86_64/rh/rh-mongodb26 sclo/x86_64/rh/rh-mongodb30upg sclo/x86_64/rh/rh-mongodb32 sclo/x86_64/rh/rh-mongodb34 sclo/x86_64/rh/rh-mysql56 sclo/x86_64/rh/rh-mysql57 sclo/x86_64/rh/rh-nginx18 sclo/x86_64/rh/rh-nginx110 sclo/x86_64/rh/rh-nodejs4 sclo/x86_64/rh/rh-nodejs6 sclo/x86_64/rh/rh-passenger40 sclo/x86_64/rh/rh-perl520 sclo/x86_64/rh/rh-perl524 sclo/x86_64/rh/rh-php56 sclo/x86_64/rh/rh-php70 sclo/x86_64/rh/rh-postgresql94 sclo/x86_64/rh/rh-postgresql95 sclo/x86_64/rh/rh-postgresql96 sclo/x86_64/rh/rh-python34 sclo/x86_64/rh/rh-python35 sclo/x86_64/rh/rh-python36 sclo/x86_64/rh/rh-redis32 sclo/x86_64/rh/rh-ror41 sclo/x86_64/rh/rh-ror42 sclo/x86_64/rh/rh-ror50 sclo/x86_64/rh/rh-ruby22 sclo/x86_64/rh/rh-ruby23 sclo/x86_64/rh/rh-ruby24 sclo/x86_64/rh/rh-scala210 sclo/x86_64/rh/rh-thermostat16 sclo/x86_64/rh/rh-varnish4 sclo/x86_64/rh/ror40 sclo/x86_64/rh/ruby193 sclo/x86_64/rh/ruby200 sclo/x86_64/rh/thermostat1 sclo/x86_64/rh/v8314 sclo/x86_64/sclo/sclo-git25 sclo/x86_64/sclo/sclo-git212 sclo/x86_64/sclo/sclo-httpd24more sclo/x86_64/sclo/sclo-php54 sclo/x86_64/sclo/sclo-php55 sclo/x86_64/sclo/sclo-php56 sclo/x86_64/sclo/sclo-php70 sclo/x86_64/sclo/sclo-python27 sclo/x86_64/sclo/sclo-python34 sclo/x86_64/sclo/sclo-python35 sclo/x86_64/sclo/sclo-ror42 sclo/x86_64/sclo/sclo-subversion19 storage/x86_64/gluster-3.6 storage/x86_64/gluster-3.7 storage/x86_64/gluster-3.8 storage/x86_64/gluster-3.9 storage/x86_64/gluster-3.10 storage/x86_64/gluster-3.12 storage/x86_64/gluster-3.13 storage/x86_64/gluster-4.0 storage/x86_64/gluster-4.1 virt/x86_64/xen-44 virt/x86_64/xen-46 virt/x86_64/xen-48

3 4

6.10 status? (Writeup needed for Newsletter)
by Rich Bowen 02 Jul '18

02 Jul '18

Hi, folks, The July newsletter is almost ready to go out - final draft is here: https://wiki.centos.org/Newsletter/1802/ I would very much like to include a paragraph about the 6.10 release - when to expect it, what the highlights are, and anything else. I am looking for a volunteer to provide that paragraph, by close of business today, if at all possible. You can reply here, or send it directly to me off-list, as you prefer. Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Do we know the reason why this below listed CVEs will not be fixed For elfutils-libelf, elfutils-libs and elfutils pakages ?
by Veetil, Vyshnav 30 Jun '18

30 Jun '18

Do we know the reason why this below listed CVEs will not be fixed For elfutils-libelf,elfutils-libs and elfutils pakages ? 1.CVE-2017-7607 2.CVE-2017-7608 3.CVE-2017-7609 4.CVE-2017-7610 5.CVE-2017-7611 6.CVE-2017-7612 7.CVE-2017-7613

4 5

Joining CentOS Storage SIG
by Saravanakumar Arumugam 29 Jun '18

29 Jun '18

Hi, I would like to be part of CentOS Storage SIG. I am from GlusterFS background, but I can contribute to package other solutions too. It will be great if we can add documentation about running CentOS based storage containers (like gluster / ceph containers). I can contribute here as well. Thanks, Saravana

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel