devel

devel@lists.centos.org

4 participants
4592 discussions

Self Introduction: tdawson
by Troy Dawson 25 Jan '16

25 Jan '16

Hi, My name is Troy Dawson. I've been working on the OpenShift project for over 4 years. Before that I was one of the main developers of Scientific Linux. I've been a Fedora packages for several years as well. I'd like to get OpenShift Origin into CentOS, as rpm's and docker images. Troy Dawson

1 0

Building powerpc-utils from git.centos.org
by Vit Ry 22 Jan '16

22 Jan '16

Hi all. I am trying to build powerpc-utils[1] on ppc64, but build fails with error: ... checking whether the linker accepts -pie... yes checking that generated files are newer than configure... done configure: creating ./config.status /bin/sh ./config.status config.status: creating Makefile config.status: creating powerpc-utils.spec config.status: executing depfiles commands Makefile:864: *** multiple target patterns. Stop. RPM build errors: ... as I investigate, the reason is SOURCES / powerpc-utils-1.2.15-man.patch [2] with line + man/lsprop.8:q \ I propose to fix it like s/lsprop.8:q/lsprop.8/ [1]: https://git.centos.org/summary/rpms!powerpc-utils [2]: https://git.centos.org/blob/rpms!powerpc-utils/262646878310d3ffa9acd72b995f… --- Regards, Vit Ry.

2 3

3.18.22 Kernel RPM Contribution to CentOS
by gayathri.madda＠wipro.com 19 Jan '16

19 Jan '16

Hi Team, As there was no official Linux kernel RPM (version 3.18.22) for CentOS 7 in any of their distribution versions, we have customized spec file for creating 3.18.22 kernel RPM for CentOS-7 Minimal version by taking 3.18.12 kernel spec file STEPS for Generating Kernel RPM 1. Downloaded the latest 3.18.22 kernel source code "linux-3.18.22.tar.gz<https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.18.22.tar.gz>" from https://www.kernel.org/pub/linux/kernel/v3.x/ 2. Customized the 3.18.12 kernel spec file w.r.t 3.18.22 kernel SPEC and created RPM for CentOS 7 Minimal Version Regards, Gayathri The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

4 3

Use of PTPd on CentOS 6
by Claudio Scordino 19 Jan '16

19 Jan '16

I need to create a reliable and accurate synchronization between two CentOS 6 machines connected through a direct Ethernet connection. I've seen that on Linux several implementation of the IEEE 1588 Precision Time Protocol (PTP) <https://en.wikipedia.org/wiki/Precision_Time_Protocol> exist: - PTPd <http://ptpd.sourceforge.net>: - Apparently, this is the original implentation - Apparently, it is still maintained <http://www.github.com/ptpd/ptpd> - PTPd2 <http://ptpd2.sourceforge.net>: - A new version meant to supersede the previous implementation - Apparently unmaintained - For CentOS 6, available only in the EPEL repositories - PTPv2d <http://code.google.com/p/ptpv2d>: - A further implementation - Unmaintained as well - linuxptp <http://linuxptp.sourceforge.net>: - A specific implementation for Linux - Maintained - Available on the CentOS repositories - Suggested by the RedHat documentation for both RedHat 6 <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/ht…> and RedHat 7 <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/ht…> My questions follow: - Why does the RedHat documentation suggest the use of linuxptp <https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/ht…> for RedHat 6 (based on Linux kernel 2.6) despite the linuxptp documentation says that a Linux kernel version 3.0 or newer is needed <http://linuxptp.sourceforge.net/> ? - Which are differences between PTPd2 and Linuxptp in terms of reliability and timing accuracy ? - Which one should I prefer on CentOS 6 and on CentOS 7, respectively ? - Why either PTPd2 and Linuxptp do not synchronize immediately and often need me to start/stop the service several times or manually change system time through date to make the machine synchronize ? Many thanks for any hint.

2 1

Introduction for SCLo SIG and PHP package - remi
by Remi Collet 19 Jan '16

19 Jan '16

Howdy, CentOS account (FAS) : remi PHP packages maintainer in various places. Goal: I'd like to build various additional packages for the various PHP SCL which are not available in upstream RHSCL. Those packages will use "sclo-php5#" prefix, but are really part of the (rh-)php5# collection, different prefix used to avoid user confusion. Notice: most of those, are already built in 'morephp5#' community repository. So I need CBS access to be able to build them. Remi.

1 1

Re: [CentOS-devel] 3.18.22 Kernel RPM Contribution to CentOS
by gayathri.madda＠wipro.com 19 Jan '16

19 Jan '16

Re-Sending the Mail .. Regards, Gayathri.M From: Gayathri Madda (WT01 - Digital Marketing) Sent: Tuesday, January 19, 2016 2:27 PM To: 'centos-devel(a)centos.org' <centos-devel(a)centos.org> Subject: 3.18.22 Kernel RPM Contribution to CentOS Hi Team, As there was no official Linux kernel RPM (version 3.18.22) for CentOS 7 in any of their distribution versions, we have customized spec file for creating 3.18.22 kernel RPM for CentOS-7 Minimal version by taking 3.18.12 kernel spec file STEPS for Generating Kernel RPM 1. Downloaded the latest 3.18.22 kernel source code "linux-3.18.22.tar.gz<https://www.kernel.org/pub/linux/kernel/v3.x/linux-3.18.22.tar.gz>" from https://www.kernel.org/pub/linux/kernel/v3.x/ 2. Customized the 3.18.12 kernel spec file w.r.t 3.18.22 kernel SPEC and created RPM for CentOS 7 Minimal Version Regards, Gayathri The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com

1 0

CentOS SCLo SIG sync-up meeting on #centos-devel (2016-01-13)
by Honza Horak 18 Jan '16

18 Jan '16

SCLo SIG meeting will be today at 16:00 UTC (11:00 EST, 17:00 Brno, 11:00 Boston, 0:00+1d Tokyo, 1:00+1d Brisbane) in #centos-devel on Freenode. = Topics = * devtoolset-4 rebuilding updates https://bugs.centos.org/view.php?id=10106 * review of how development of new scls is working rought proposal: building packages -> candidate -> sanity testing -> testing -> [wait till rhscl is released] -> tag released -> sign&release * Provides/Obsoletes to centos-release-scl * package for RHEL users that installs sclo packages above RHSCL Honza

2 2

Re: [CentOS-devel] [scl.org] Minutes from CentOS SCLo SIG sync-up meeting on #centos-devel (2016-01-13)
by Honza Horak 18 Jan '16

18 Jan '16

On 01/14/2016 07:35 AM, Nick Coghlan wrote: > On Thu, Jan 14, 2016 at 3:33 AM, Honza Horak <hhorak(a)redhat.com> wrote: >> #topic review of how development of new scls is working >> rought proposal: building packages -> candidate -> sanity testing -> >> testing -> [wait till rhscl is released] -> tag released -> sign&release >> - usual tagging process: tag -candidate -> [sanity testing] -> tag >> -testing -> [better testing] -> tag -released -> sign&release >> - how it will be done for collections that gonna be released in RHSCL in >> the future? >> - idea: such collections should stay in -testing until they are released >> in RHSCL -- bad idea? shout now. > > What's the scope of discussion here in terms of "sclo-*" SCLs and "rh-*" SCLs? > > For "sclo-*" SCLs, I'd expect the RHSCL release cycle to be entirely irrelevant. Yes, they may be theoretically influence in cases the sclo-* SCLs depend on some rh-* SCLs -- in that case their release is depended on RHSCL. > For "rh-*" SCLs, having them remain in -testing until the downstream > release (so they become generally available to RHEL & CentOS users at > the same time) seems reasonable. > > So if someone wanted to take an existing rh-* package and turn it into > an sclo-* package that could be updated independently of the RHSCL > release cycle, they'd be free to do that. Yes, in case someone would like to include different set of packages or deliver different version, then it effectively become a new SCL, that needs to be treated that way. Honza

1 0

CentOS ppc64le hypervisor support
by James Nash 15 Jan '16

15 Jan '16

Is there a list of "supported" methods for deployment of CentOS 7.2 on Power8? I know folks with VMs behind VIO servers with PowerVM. I understand VMs under PowerKVM with OPAL are also supported. Any ideas on bare metal CentOS under OPAL, Power8 with either latest firmware levels (FW840 or OP810)? Regards, James Nash jjnash(a)us.ibm.com Power Systems Strategic Initiatives Team > On Jan 12, 2016, at 7:01 AM, centos-devel-request(a)centos.org wrote: > > Send CentOS-devel mailing list submissions to > centos-devel(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos-devel > or, via email, send a message with subject or body 'help' to > centos-devel-request(a)centos.org > > You can reach the person managing the list at > centos-devel-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS-devel digest..." > > > Today's Topics: > > 1. Re: [CentOS-announce] Announcing release for MySQL 5.5 and > 5.6 on CentOS Linux 6 x86_64 SCL (Leon Fauster) > 2. Re: [CentOS-announce] Announcing release for MySQL 5.5 and > 5.6 on CentOS Linux 6 x86_64 SCL (Nico Kadel-Garcia) > 3. Re: CentOS Upgrade Tool (Ulrich Leodolter) > 4. Re: CentOS Upgrade Tool (Peter) > 5. Re: [CentOS-announce] Announcing release for MySQL 5.5 and > 5.6 on CentOS Linux 6 x86_64 SCL (Karanbir Singh) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 11 Jan 2016 16:18:50 +0100 > From: Leon Fauster <leonfauster(a)googlemail.com> > To: "The CentOS developers mailing list." <centos-devel(a)centos.org> > Subject: Re: [CentOS-devel] [CentOS-announce] Announcing release for > MySQL 5.5 and 5.6 on CentOS Linux 6 x86_64 SCL > Message-ID: <BA7034C8-B46D-4435-A2C8-8753D55F2187(a)googlemail.com> > Content-Type: text/plain; charset=us-ascii > > > Hi Honza, > >> Am 21.12.2015 um 17:20 schrieb Honza Horak <hhorak(a)redhat.com>: >> >> I am pleased to announce the immediate availability of versions 5.5 and 5.6 of the MySQL on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). >> >> QuickStart >> ---------- >> You can get started in three easy steps (example of MySQL 5.6): >> $ sudo yum install centos-release-scl >> $ sudo yum install rh-mysql56 >> $ scl enable rh-mysql56 bash > > > should centos-release-scl not have at least a "Obsoletes: centos-release-SCL" statement? > > http://mirror.centos.org/centos/6/extras/x86_64/Packages/centos-release-SCL… > vs > http://mirror.centos.org/centos/6/extras/x86_64/Packages/centos-release-scl… > > -- > LF > > > > > > ------------------------------ > > Message: 2 > Date: Mon, 11 Jan 2016 22:51:56 -0500 > From: Nico Kadel-Garcia <nkadel(a)gmail.com> > To: "The CentOS developers mailing list." <centos-devel(a)centos.org> > Subject: Re: [CentOS-devel] [CentOS-announce] Announcing release for > MySQL 5.5 and 5.6 on CentOS Linux 6 x86_64 SCL > Message-ID: > <CAOCN9ryRxxCm-Aw+1PMpKPA6hWfncSkoGV8Ed3b2D5Nn_JF6hw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > On Mon, Jan 11, 2016 at 10:18 AM, Leon Fauster > <leonfauster(a)googlemail.com> wrote: >> >> Hi Honza, >> >>> Am 21.12.2015 um 17:20 schrieb Honza Horak <hhorak(a)redhat.com>: >>> >>> I am pleased to announce the immediate availability of versions 5.5 and 5.6 of the MySQL on CentOS Linux 6 x86_64, delivered via a Software Collection (SCL) built by the SCLo Special Interest Group (https://wiki.centos.org/SpecialInterestGroup/SCLo). >>> >>> QuickStart >>> ---------- >>> You can get started in three easy steps (example of MySQL 5.6): >>> $ sudo yum install centos-release-scl >>> $ sudo yum install rh-mysql56 >>> $ scl enable rh-mysql56 bash >> >> >> should centos-release-scl not have at least a "Obsoletes: centos-release-SCL" statement? >> >> http://mirror.centos.org/centos/6/extras/x86_64/Packages/centos-release-SCL… >> vs >> http://mirror.centos.org/centos/6/extras/x86_64/Packages/centos-release-scl… > > And a "Provides: centos-release-SCL", for people like me with "mock" > configurations that used it. > > > ------------------------------ > > Message: 3 > Date: Tue, 12 Jan 2016 09:20:30 +0100 (CET) > From: Ulrich Leodolter <ulrich.leodolter(a)obvsg.at> > To: "The CentOS developers mailing list." <centos-devel(a)centos.org> > Subject: Re: [CentOS-devel] CentOS Upgrade Tool > Message-ID: > <1234403688.378.1ba2367a-42f9-46fa-878d-8dacc1c790c5.open-xchange(a)oxchange.obvsg.at> > > Content-Type: text/plain; charset=UTF-8 > > Hi, > >> Ken Dreyer <kdreyer(a)redhat.com> hat am 6. Januar 2016 um 17:49 geschrieben: >> >> >>> On Wed, Jan 6, 2016 at 7:24 AM, Bruno Martins <bruno.martins(a)rumos.pt> wrote: >>> I've used the tool with '--force' parameter and it upgraded just fine. Now >>> I'm having some side effects like: >>> "grep: error while loading shared libraries: libpcre.so.0: cannot open >>> shared object file: No such file or directory" >> >> I had a similar issue with grep when I upgraded my CentOS 6 home >> server to CentOS 7 last week. As explained elsewhere, the issue is >> that not all .el6 packages get upgraded. > > I have upgraded a couple of C6 machines last weeks, it works much better > with 7.2 now, at least the system boots and ssh works :) > > The grep issue can be fixed after upgrade very simply: > > $ yum downgrade grep > > BR > Ulrich > > > ------------------------------ > > Message: 4 > Date: Tue, 12 Jan 2016 21:47:59 +1300 > From: Peter <peter(a)pajamian.dhs.org> > To: centos-devel(a)centos.org > Subject: Re: [CentOS-devel] CentOS Upgrade Tool > Message-ID: <5694BDBF.1000309(a)pajamian.dhs.org> > Content-Type: text/plain; charset=windows-1252 > >> On 12/01/16 21:20, Ulrich Leodolter wrote: >> I have upgraded a couple of C6 machines last weeks, it works much better >> with 7.2 now, at least the system boots and ssh works :) >> >> The grep issue can be fixed after upgrade very simply: >> >> $ yum downgrade grep > > First off I *do not* support the use of the upgrade tool under any > circumstances, just in case I haven't made my position clear in the > past. That said, you'll probably do a more thorough job of fixing all > the mistakes made by the upgrade too if you follow it up with: > > yum distro-sync > > This should fix grep and any other package that is still left on the el6 > version. > > > Peter > > > ------------------------------ > > Message: 5 > Date: Tue, 12 Jan 2016 10:58:52 +0000 > From: Karanbir Singh <kbsingh(a)centos.org> > To: centos-devel(a)centos.org, Honza Horak <hhorak(a)redhat.com> > Subject: Re: [CentOS-devel] [CentOS-announce] Announcing release for > MySQL 5.5 and 5.6 on CentOS Linux 6 x86_64 SCL > Message-ID: <5694DC6C.9000600(a)centos.org> > Content-Type: text/plain; charset=windows-1252 > > On 12/01/16 03:51, Nico Kadel-Garcia wrote: >>> should centos-release-scl not have at least a "Obsoletes: centos-release-SCL" statement? >>> >>> http://mirror.centos.org/centos/6/extras/x86_64/Packages/centos-release-SCL… >>> vs >>> http://mirror.centos.org/centos/6/extras/x86_64/Packages/centos-release-scl… >> >> And a "Provides: centos-release-SCL", for people like me with "mock" >> configurations that used it. > > honza can shed a bit more light on this, but it was discussed before the > first SCL release - and it appeared to not be needed, as new users would > just migrate over. > > regards, > > -- > Karanbir Singh, Project Lead, The CentOS Project > +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS > GnuPG Key : http://www.karan.org/publickey.asc > > > ------------------------------ > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > > > End of CentOS-devel Digest, Vol 131, Issue 6 > ******************************************** >

5 7

Wiki Correction?
by Brian (bex) Exelbierd 13 Jan '16

13 Jan '16

On this page: https://wiki.centos.org/Cloud/AWS <https://wiki.centos.org/Cloud/AWS> Should this line, "All images have root logins which are enabled only via a ssh key." actually reference the fact that login is accomplished via the userid "centos" ? I'll fix it, if so. If not, then it must be from my use case. regards, bex -- Brian (bex) Exelbierd P: +1-919-414-8915 <tel:+1-919-414-8915> (US) | P: +420 606 055 877 <tel:+420%20606%20055%20877> (CZ) | E:bex@pobox.com <mailto:bex@pobox.com> (preferred) IM: Google: bcexelbi(a)gmail.com <mailto:bcexelbi@gmail.com> | QQ: 1927508627 <tel:1927508627> | Skype: bcexelbi | MSN: bex(a)pobox.com <mailto:bex@pobox.com> | WeChat: bcexelbi

3 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