devel

devel@lists.centos.org

5 participants
4641 discussions

CBS/Infra Meeting 24-Nov-2014 14:00 UTC
by Brian Stinson 24 Nov '14

24 Nov '14

Greetings All! Every week we get together to talk about the status of the CentOS Community Build System[1]. We will be meeting on 24-Nov-2014 at 14:00 UTC in #centos-devel on freenode. Agenda: #info Topic: Status Updates #info Subtopic: Centralized Authentication[2] with IPA[3] #info Subtopic: Git Infrastructure - lookaside cache for uploading non-text sources for package building #info Subtopic: Koji/Repos - Version pinning on the builders - What else needs rebuilding? #info Subtopic: Centpkg[4] - Release process? #info Topic: Open Floor Cheers! Brian [1] http://cbs.centos.org/ [2] http://wiki.centos.org/InfraWiki/CentralizedAuth [3] http://www.freeipa.org/page/Main_Page [4] http://git.centos.org/summary/centpkg.git

2 1

Storage SIG Meeting notes 2014-11-21
by Karanbir Singh 24 Nov '14

24 Nov '14

hi, On Friday 21st Nov 2014, there was a short syncup re; CentOS Storage SIG and a status check highlights from this meeting: * Lala offering to take up slack since Patrick is busy and take over running meetings moving forward -- to propose a meeting date/time slot on centos-devel list -- to establish where the meeting to take place ( most people seem to like irc and therefore #centos-devel might be an option ) Status Checks: * gluster is ready to move into testing, BLOCKED ON: sign and release process being implemented * openafs is making progress, using Fedora COPR for builds. Lala to interface with Andrew and JBillings to get them setup with koji access --- for now, build via SRPMS since git -> koji is not quite 100% --- openafs also needs conversation and consideration around building kmod's for multiple kernel versions, and to build/rebuild on every kernel release ( speak to Thomas, Mike and buildsys group for feedback ) --- openafs is not tested client + server side, contributors feel there should be -some- testing on both sides before we pass along confidence in builds to users Other * SCST folks are keen to join the effort, KB to introduce them into group EOM -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

Based on CentOS source code, PowerPC 64 architecture of Linux OS and repository.
by youbest＠sina.com 24 Nov '14

24 Nov '14

I'm sorry, I forgot to write the mail title. I update attachment file, and download URL. ----- Original Message ----- From: <youbest(a)sina.com> To: "centos-devel" <centos-devel(a)centos.org> Subject: [CentOS-devel] epel-7-ppc64 Date: 2014-11-24 17:34 Hi, All My name is Sun Haiyong, you can call me "Haiyong", I recommend a CentOS code based on PPC64 (Big Endian) Install-system and software repository: (Install-DVD ISO) http://mirror.lemote.com/CPOS/images/CPOS-7-Installation-20141120-1.iso (software repository) http://mirror.lemote.com/CPOS/os/ This system is based on CentOS source code, code named “CPOS”, at present, it is not a distribution, its goal is to help the community to complete the transplantation and verification of CentOS PPC64 architecture, anyone can use it derectly or to make a CentOS for PPC64 system or to verify the support for CentOS code under the PPC64. The "CPOS" is not meant to replace CentOS with a distribution, on the contrary, CPOS hopes to help the CentOS community to accelerate the progress of PPC64 transplantation, and hope to promote the developments of PPC64 with the CentOS community together, now it is an averification system, focus on how to transplant PPC64, there may be "CentOS" the words in the system , but not mean to violate CentOS signs. This system has completed all the code provided in CentOS 7 compilation (except the part not compatible with the PPC64), all the compiled results are stored in the software repository, but also provide the Install-system of DVD ISO format, can be installed in the IBM PowerLinux series machines, has set the appropriate the installation source after installation, you can directly use the "yum" command to do the software installation, system is also based on PPC64 and parts library compatible with the 32 bit, can be used to verify the number in RHEL 7 (PPC64) of the third party software support. According to the CentOS 7 provides the code (http://vault.centos.org/7.0.1406/os/Source/SPackages/ ), the following is the progress of transplantation of CPOS: 1. No compiled software package(one package): Java-1.6.0-openjdk (now the system has been transplanted with java-1.7,temporarily not necessary) 2. PPC64 architecture is not compatible software package: biosdevname-0.5.0-10.el7.src.rpm crash-gcore-command-1.2.1-2.el7.src.rpm gnu-efi-3.0u-2.el7.src.rpm ipxe-20130517-5.gitc4bce43.el7.src.rpm latrace-0.5.11-5.el7.src.rpm libseccomp-2.1.1-2.el7.src.rpm memtest86+-4.20-12.el7.src.rpm mkbootdisk-1.5.5-11.el7.src.rpm open-vm-tools-9.4.0-3.el7.src.rpm pesign-0.109-6.el7.src.rpm seabios-1.7.2.2-12.el7.src.rpm sgabios-0.20110622svn-4.el7.src.rpm shim-0.7-5.el7.src.rpm shim-signed-0.7-5.2.el7.centos.2.src.rpm syslinux-4.05-8.el7.src.rpm tboot-1.7.4-1.el7.src.rpm x86info-1.30-6.el7.src.rpm xorg-x11-drv-intel-2.21.15-13.el7.src.rpm xorg-x11-drv-openchrome-0.3.3-6.el7.src.rpm xorg-x11-drv-vmmouse-13.0.0-10.el7.src.rpm xorg-x11-drv-vmware-13.0.1-7.el7.src.rpm 3. An increase of some PPC software package: yaboot, powerpc-util, ppc64-util and so on. Repositories support "mock" compiler environment, mock configuration file, see attachment file. Use “mock" build system 1. To prepare the mock environment yum install mock <copy mock configuration file to /etc/mock/> ln -sv epel-7-ppc64.cfg /etc/mock/default.cfg useradd <username> usermod -a -G mock <username> newgrp mock mock --init 2. Download the software source code package wget http://vault.centos.org/7.0.1406/os/Source/SPackages/zlib-1.2.7-13.el7.src.… 3. The use of mock compiler software package PPC64 mock --rebuild zlib-1.2.7-13.el7.src.rpm The default will generate the "cpos.ppc64.rpm" at the end of the file in /var/lib/mock/epel-7-ppc64/result, if you want to change to "centos.ppc64.rpm" at the end of the file, you canuse the following steps: wget http://mirror.lemote.com/CPOS/extras/centos-release-7-0.1406.el7.centos.2.3… mock --init --no-cleanup-after mock --remove cpos-release mock --install centos-release-7-0.1406.el7.centos.2.3.ppc64.rpm mock --install setup shadow-utils mock --cache-alterations --init --no-clean Again using the "mock --rebuild zlib-1.2.7-13.el7.src.rpm" can generate the "centos.ppc64.rpm" at the end of the file. Finally, welcome everybody to try it and communicate with me. Haiyong.Sun 2014-11-24_______________________________________________

1 0

epel-7-ppc64
by youbest＠sina.com 24 Nov '14

24 Nov '14

Hi, All My name is Sun Haiyong, you can call me "Haiyong", I recommend a CentOS code based on PPC64 (Big Endian) Install-system and software repository: (Install-DVD ISO) http://mirror.lemote.com/CPOS/images/CPOS-7-Installation-20141120-1.iso (software repository) http://mirror.lemote.com/CPOS/os/ This system is based on CentOS source code, code named “CPOS”, at present, it is not a distribution, its goal is to help the community to complete the transplantation and verification of CentOS PPC64 architecture, anyone can use it derectly or to make a CentOS for PPC64 system or to verify the support for CentOS code under the PPC64 . The "CPOS" is not meant to replace CentOS with a distribution, on the contrary, CPOS hopes to help the CentOS community to accelerate the progress of PPC64 transplantation, and hope to promote the developments of PPC64 with the CentOS community together, now it is an averification system, focus on how to transplant PPC64, there may be "CentOS" the words in the system , but not mean to violate CentOS signs. This system has completed all the code provided in CentOS 7 compilation (except the part not compatible with the PPC64), all the compiled results are stored in the software repository, but also provide the Install-system of DVD ISO format, can be installed in the IBM PowerLinux series machines, has set the appropriate the installation source after installation, you can directly use the "yum" command to do the software installation, system is also based on PPC64 and parts library compatible with the 32 bit, can be used to verify the number in RHEL 7 (PPC64) of the third party software support. According to the CentOS 7 provides the code (http://95.211.98.141/centos/7.0.1406/os/Source/SPackages/ ), the following is the progress of transplantation of CPOS: 1. No compiled software package(one package): Java-1.6.0-openjdk (now the system has been transplanted with java-1.7,temporarily not necessary) 2. PPC64 architecture is not compatible software package: biosdevname-0.5.0-10.el7.src.rpm crash-gcore-command-1.2.1-2.el7.src.rpm gnu-efi-3.0u-2.el7.src.rpm ipxe-20130517-5.gitc4bce43.el7.src.rpm latrace-0.5.11-5.el7.src.rpm libseccomp-2.1.1-2.el7.src.rpm memtest86+-4.20-12.el7.src.rpm mkbootdisk-1.5.5-11.el7.src.rpm open-vm-tools-9.4.0-3.el7.src.rpm pesign-0.109-6.el7.src.rpm seabios-1.7.2.2-12.el7.src.rpm sgabios-0.20110622svn-4.el7.src.rpm shim-0.7-5.el7.src.rpm shim-signed-0.7-5.2.el7.centos.2.src.rpm syslinux-4.05-8.el7.src.rpm tboot-1.7.4-1.el7.src.rpm x86info-1.30-6.el7.src.rpm xorg-x11-drv-intel-2.21.15-13.el7.src.rpm xorg-x11-drv-openchrome-0.3.3-6.el7.src.rpm xorg-x11-drv-vmmouse-13.0.0-10.el7.src.rpm xorg-x11-drv-vmware-13.0.1-7.el7.src.rpm 3. An increase of some PPC software package: yaboot, powerpc-util, ppc64-util and so on. Repositories support "mock" compiler environment, mock configuration file, see attchment file. Use “mock" build system 1. To prepare the mock environment yum install mock <copy mock configuration file to /etc/mock/> ln -sv epel-7-ppc64.cfg /etc/mock/default.cfg useradd <username> usermod -a -G mock <username> newgrp mock mock --init 2. Download the software source code package wget http://95.211.98.141/centos/7.0.1406/os/Source/SPackages/zlib-1.2.7-13.el7.… 3. The use of mock compiler software package PPC64 mock --rebuild zlib-1.2.7-13.el7.src.rpm The default will generate the "cpos.ppc64.rpm" at the end of the file in /var/lib/mock/epel-7-ppc64/result, if you want to change to "centos.ppc64.rpm" at the end of the file, you canuse the following steps: wget http://mirror.lemote.com/CPOS/extras/centos-release-7-0.1406.el7.centos.2.3… mock --init --no-cleanup-after mock --remove cpos-release mock --install centos-release-7-0.1406.el7.centos.2.3.ppc64.rpm mock --install setup shadow-utils mock --cache-alterations --init --no-clean Again using the "mock --rebuild zlib-1.2.7-13.el7.src.rpm" can generate the "centos.ppc64.rpm" at the end of the file. Finally, welcome everybody to try it and communicate with me. Haiyong.Sun 　　　　　　 2014-11-24

2 1

question on build system for Centos 7
by Dongwu Zeng 21 Nov '14

21 Nov '14

Hi all, I recently run into a problem while building a package in Centos 7. It seems that the problem is related with the type of file system being used. If the file system is ext4, then the problem doesn't show up. However, if the system uses XFS, then a test in the "%check" section fails. So I'm wondering what type of file system is used on build systems for Centos 7. Is it ext4 or xfs? Thanks. Dongwu

4 4

Fosdem 2015 Distro DevRoom CFP
by Karanbir Singh 21 Nov '14

21 Nov '14

Hi Guys, https://github.com/ixs/distributions-devroom/blob/master/README.md is now up, get submitting! - KB -- 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

2 1

Is CentOS SCL EL6 still updated?
by Jake Shipton 20 Nov '14

20 Nov '14

Hi all, Sorry to be a bug here and ask this. But I was just wondering if CentOS SCL for EL6 is still being updated? Just wondering because yesterday (The 17th) RedHat released a couple of security updates for MySQL 5.5 and MariaDB 5.5 and it would appear that C6 has yet to receive these updates, where as EL7 and EL5 did. Which makes me wonder if the SCL for C6 has been either discontinued or the update was simply forgotten/unnoticed or had build issues? Just curious mainly, if it is now discontinued I'll happily compile the update myself, if not I'll happily wait :-). Either way, I'd just like to know what's happening so I can make plans going forward on a couple of production machines. Anyhow, Thank you for your time. Note: Posted on -devel list as this really is a question more geared towards the CentOS team more so than it's users so the correct people see it. Kind Regards, Jake Shipton (JakeMS) GPG Key: 0xE3C31D8F GPG Fingerprint: 7515 CC63 19BD 06F9 400A DE8A 1D0B A5CF E3C3 1D8F Relevant RedHat Links: https://rhn.redhat.com/errata/RHSA-2014-1862.html https://rhn.redhat.com/errata/RHSA-2014-1860.html http://ftp.redhat.com/pub/redhat/linux/enterprise/6Workstation/en/RHSCL/SRP… http://ftp.redhat.com/pub/redhat/linux/enterprise/6Workstation/en/RHSCL/SRP…

2 4

Importing of of CentOS-6 SRPMS for git.centos.org
by Johnny Hughes 19 Nov '14

19 Nov '14

As was discussed before, CentOS-6 SRPMS are going to be imported into git.centos.org as well and will be processed like CentOS-7 ones are now. We want to bring everything in from 6.0 initial and through 6.4+updates initially, then we will do 6.5+updates (as that is changing right now). So, I have created a 6.0 to 6.4 set of lists. These lists live at this location: http://people.centos.org/hughesjr/EL6-Import/ The two lists so far are: EL6-non-mod-SRPMS-sorted.txt centos-6-srpms-modified.txt 1. The EL6-non-mod-SRPMS-sorted.txt is all SRPMS used in CentOS-6 in their unmodified form. The order they appear in the file is the order they will be imported into git. What is important for history is that (for each NAME) they are imported in the correct order, so from 6.0 through 6.4+updates, the order of packages used in CentOS-6 for 389-ds-base would be: 389-ds-base-1.2.8.2-1.el6.src.rpm 389-ds-base-1.2.8.2-1.el6_1.3.src.rpm 389-ds-base-1.2.9.14-1.el6.src.rpm 389-ds-base-1.2.9.14-1.el6_2.2.src.rpm 389-ds-base-1.2.10.2-15.el6.src.rpm 389-ds-base-1.2.10.2-18.el6_3.src.rpm 389-ds-base-1.2.10.2-20.el6_3.src.rpm 389-ds-base-1.2.11.15-11.el6.src.rpm 389-ds-base-1.2.11.15-12.el6_4.src.rpm 389-ds-base-1.2.11.15-14.el6_4.src.rpm 389-ds-base-1.2.11.15-20.el6_4.src.rpm 389-ds-base-1.2.11.15-22.el6_4.src.rpm All of these packages will come from ftp.redhat.com and be imported. =========================================== 2. Next is the centos-6-srpms-modified.txt file .. that actually contains a list (in the order they will be imported) of all source packages modified for CentOS-6 (again 6.0 to 6.4+updates) and their RHEL counterparts. All packages without a .centos. in the name will come from ftp.redhat.com, all packages with a centos in the name will come from vault.centos.org and the order should alternate so that we have RHEL package and then CentOS Package, then repeat for each NAME for an SRPM. So, for example, for anaconda, it would be: anaconda-13.21.82-1.el6.src.rpm anaconda-13.21.82-1.el6.centos.1.src.rpm anaconda-13.21.117-1.el6.src.rpm anaconda-13.21.117-1.el6.centos.src.rpm anaconda-13.21.149-1.el6.src.rpm anaconda-13.21.149-1.el6.centos.src.rpm anaconda-13.21.176-1.el6_3.src.rpm anaconda-13.21.176-1.el6.centos.src.rpm anaconda-13.21.195-1.el6.src.rpm anaconda-13.21.195-1.el6.centos.1.src.rpm =========================================== 3. I will be creating a 3rd list (not yet done) of the kernel packages since we actually have the 'exact same' ENVR for kernel packages as RHEL in CentOS so that 3rd party kernel drivers work for the boot isos. That list will be added sometime today. =========================================== What I would like for some one (as many as will do it :D) to verify that importing things in this order into git will result in the proper git tree for each 'name' package ... so the above 389-ds-base will produce chronological order imports ... same for anaconda in #2 ... with the added desire to get RHEL then CentOS packges in the correct order. You can see the names of the SRPMs in every CentOS release in vault.centos.org/6.0 through 6.4 .. we are concerned about os/ and updates/ SRPMS. Does this make sense, and are there any errors in the lists?

6 14

Fwd: [atomic-devel] recommending Flannel (w/ vxlan backend) for atomic -- thoughts?
by Joe Brockmeier 19 Nov '14

19 Nov '14

Upstream discussion to try to figure out which tool to use to set up networks for Atomic/Docker. Thoughts, comments, suggestions? -------- Forwarded Message -------- Subject: [atomic-devel] recommending Flannel (w/ vxlan backend) for atomic -- thoughts? Date: Tue, 18 Nov 2014 14:36:03 -0500 From: John W. Linville <linville(a)redhat.com> To: atomic-devel(a)projectatomic.io Greetings, Internally we've been doing a little looking at projects for setting-up overlay networks between minions in a Kubernetes cluster. One of the most interesting options has been Flannel (formerly Rudder). Flannel requires minimal configuration to slice a large subnet into a series of smaller subnets, one per minion running flanneld. Flannel uses a configuration stored as a JSON file in etcd. The JSON configuration looks a bit like this: { "Network": "192.168.88.0/24", "SubnetLen": 28, "Backend": { "Type": "vxlan" } } The above configuration would allow up to 16 minions to each allocate a /28 subnet for use by their local docker daemon. (Larger or smaller subnets are, of course, a simple matter of configuration.) The local configuration information is written by flanneld to a file under /var/run, and the info is used to pass the --bip option to docker so that it configures its docker0 bridge appropriately. Beyond that, the vxlan backend for flanneld on each minion creates a vxlan tunnel endpoint and configures it to use the DOVE extensions for routing. The route to the larger (e.g. /24) subnet points at the vxlan interface, so traffic to other minions is directed through it. Such traffic triggers L2MISS and L3MISS messages that are handled by flanneld, directing traffic to the appropriate minions. The result is a vxlan-based overlay network that enables connectivity between all the minions (and their pods) with a minimal amount of configuration required. This seems like a powerful and usable means to enable this communication. Given the description above (and whatever other sources you might have at your disposal), does anyone have any objections to using this as a default Kubernetes networking solution in Atomic? Or any questions about the use of Flannel in general? Thanks, John -- John W. Linville Hope is a good breakfast, but it is a linville(a)redhat.com bad supper. -- Sir Francis Bacon -- Joe Brockmeier | Principal Cloud & Storage Analyst jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://dissociatedpress.net/

1 0

Missing upstream EL5 SRPMS
by Orion Poplawski 18 Nov '14

18 Nov '14

I'm trying to build a patched version of the firefox-31.1.0-6.el5.src.rpm package for EL5, and am getting the following missing deps: DEBUG util.py:283: Error: No Package found for hunspell-devel DEBUG util.py:283: Error: No Package found for libvpx-devel >= 1.3.0 DEBUG util.py:283: Error: No Package found for system-bookmarks And indeed I cannot find any of those packages at http://ftp.redhat.com/pub/redhat/linux/enterprise/5Server/en/os/SRPMS/ (or 5client). I realize this is more of an upstream issue, but was hoping somebody here would have some insight from trying to build that for CentOS. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 http://www.nwra.com

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