devel

devel@lists.centos.org

4 participants
4592 discussions

CentOS SCLo SIG sync-up meeting on #centos-devel (2015-07-08)
by Honza Horak 08 Jul '15

08 Jul '15

SCLo SIG meeting will be at 15: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 = * We have devtoolset-3-toolchain packages built in CBS * Consulting changes in tags structure in CBS * Layered Docker images based on the SCL packages * propose some other topics :) Honza

1 1

Including rkt in virt7 - yay/nay?
by Lokesh Mandvekar 07 Jul '15

07 Jul '15

Wondering if people would be ok with including rkt in virt7 SIG repos. some folks gave this a yay on IRC, but reaching out to the mailing list as well for more votes. rkt is _not_ in fedora yet and including it would also imply including systemd >= 220 in virt7 as it isn't present in base CentOS. All the gory detail around rkt packaging for fedora can be found here: https://github.com/coreos/rkt/issues/686 . The main pending issue that fedora won't agree to right now is RE: installing the stage1 rootfs tarball at rpm install time. WIP rpm files are here: https://github.com/fedora-cloud/rkt-rpm/ . I've been adding these to my copr repo here: https://copr.fedoraproject.org/coprs/lsm5/rkt/ . markllama and lalatenduM might have something to add to this. -- Lokesh Freenode, OFTC: lsm5 GPG: 0xC7C3A0DD

6 9

CBS/Infra Meeting 06-Jul-2015 14:00 UTC
by Brian Stinson 06 Jul '15

06 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All, It's time for another meeting to talk about the Community Build System[0]. We will meet in #centos-devel on irc.freenode.net Proposed Agenda: - - Status Updates: - General - Central Auth - - Upcoming Projects Cheers! Brian [0]: http://wiki.centos.org/HowTos/CommunityBuildSystem -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVmeTcAAoJEIMGvNKzCweMZycP/itrMrZdAEK7JYLqr9LjyYo7 IbZf22bAHPk1dEnOUNLc0nBqiL+unsJzmHItjdVudP9rCNo6DSalep5B4OCBV3Sr xgHcBc36Ff2GGBNvB/VXunPIWn2IKecnKYRyxQ2iQ0m2oCkDt/DT1U9X/+6MCyRH HlWNsVTd5npCe4am5mnqjMXh9ber8p9nQgpx3EyEivdw4oX2yohCAzGEC/bz2e9Y r8eCXpu2YKgaCN4GJzu5SmTQxM9kwrcGccA7gws2/9mKD5nFMwJpzAOCunD6/gwU F1yDvrwF7r/9MXVSNGzNSH9JZKgxvQNZstsdSHyJnD18CScWYlWOBRXCEMSFsBQV Y4zr6d13zhb8DnONnb1F28hXD+eFrq9c6Hre06CHL+2+wHnmgreDkDM261yroF3h UtaI5CLXbDIblNA+ape1TA7A0ArDBPx6rPJEGvfWnytjUIN40G3WMb09IzvJVQVq Sfo2yyvgRmWVW1SXgK+7RtIJR3xovu9UJU9gnc5YVhC5StMiozqABWgvHRlHyR/Y Xx4X4xkYM5yqZ0jUtmMB56MC4fnSSiE8B2PQRU149jpDsr+cXDzuWiJXGdJDe2R7 JbgrCSPR++YYXBmZ5GRd8ekNluFCSlzTK4jU36Eq2jB4b9UugvTOIX/KYJUsNiD/ sD+Ys6g11eNexVjQcHho =QRkG -----END PGP SIGNATURE-----

1 1

CentOS CLA (Contributor License Agreement)
by Fabian Arrotin 06 Jul '15

06 Jul '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, As it seems FAS (Fedora Account Ssytem) has been chosen as the central authentication system for CentOS.org infra, I'm now trying to find documentation around it .. One thing that I see is the CLA (default in Fedora, that each user must sign and agree with) so that means that for FAS we also need to have one. Has someone already looked at it and so what would be the CentOS CLA that we'll use when people will register/sign for a FAS account on centos.org ? - -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlWREFIACgkQnVkHo1a+xU73jwCdF8/yIovWYalefgwBmV7npnbs aDwAn0ka66T3xgC5OoziXEja5e4f8X99 =Kt+l -----END PGP SIGNATURE-----

10 23

help wanted RE: EL6/CentOS6 docker-io rpm maintenance
by Lokesh Mandvekar 02 Jul '15

02 Jul '15

So, there's a lot of demand to keep docker-io in top form on EL6 but we're kinda short-staffed as far as EL6 goes. I was wondering if we have dedicated EL6 users who'd like to help out with docker-io rpm updates and maintenance. It'd be great if you're a fedora packager already and I could add you as co-maintainer of the el6 branch. Even if you are _not_ a packager, but _know_ packaging or are willing to learn :), you could test el6 updates on your environment and send me patches to docker-io dist-git which I'd then build. And/or does CentOS want to entertain the idea of SIGs for CentOS 6 or would that be too much for just 1 package? -- Lokesh Freenode, OFTC: lsm5 GPG: 0xC7C3A0DD

3 6

Updates for CentOS 6 visual style
by Alain Reguera Delgado 01 Jul '15

01 Jul '15

Hello, There are some updates for CentOS 6 visual style available that I would like you to evaluate please. This, in order to determine whether they can be included in the next CentOS 6 ISOs. The changes implement the CentOS branding as described in http://wiki.centos.org/ArtWork/Brand and new background images illustrated in http://wiki.centos.org/ArtWork/Motifs/CentOS6/Sketch1 page (which also includes the RPM packages you need to install in order to implement the visual style changes in a CentOS 6 system). For a quick preview, see how the centos-indexhtml component will look like: - http://wiki.centos.org/ArtWork/Motifs/CentOS6/Sketch1?action=AttachFile&do=… - http://wiki.centos.org/ArtWork/Motifs/CentOS6/Sketch1?action=AttachFile&do=… Best regards, al.

1 0

Introduction
by Danilo Falcão 01 Jul '15

01 Jul '15

Hi guys I'm Danilo Falcão (fcon), a Sys Admin from Brazil and living in Germany. Recently I have joined Fedora QA & Infrastructure and now the CentOS project to work with Lokesh (lsm5) building RPMS for Docker and related packages. In the past years I've been working a lot with Virtualization (XEN and KVM mostly) and since Docker appeared I became a big fan of it. I'm also a Bash scripter and a Python Fabric lover. If there's anything I can help you guys with, just holla at me @ Freenode or drop an e-mail :) Cheers, Danilo

1 0

Re: [CentOS-devel] CentOS CLA (Contributor License Agreement)
by James B. Byrne 01 Jul '15

01 Jul '15

On Mon, June 29, 2015 11:47, Karanbir Singh wrote: > > 'evil' and 'nice' are both fairly subjective, so all were saying is > dont do anything illegal. I cant imagine the FPCA welcomes illegal > activity. > That entirely depends upon whose and which laws are being contravened. This is multinational forum. Countries differ considerably on what is considered illegal. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

1 0

[NFV SIG][CBS] Question building DPDK
by Joseph Gasparakis 27 Jun '15

27 Jun '15

Hi all, I have some questions as this is the first time I am using CBS :-) First of all I have done all the prework on my .koji directory and I have verified I can build: <snap> [jgaspara@jg-vm ~]$ koji list-permissions --mine build </snap> I am trying to build DPDK 2.0 (commit id 493db80afd) and I (believe I) have successfully created a dpdk package for nfv7-opnfv-arno-[testing|release]: <snap> [jgaspara@jg-vm ~]$ koji add-pkg --owner "jgasparakis" nfv7-opnfv-arno-testing dpdk [jgaspara@jg-vm ~]$ koji add-pkg --owner "jgasparakis" nfv7-opnfv-arno-release dpdk </snap> Then, I suppose I need to kick off a git build, but it seems like I need to somehow add the DPDK git tree to the permitted SCMs for CBS: <snap> [jgaspara@jg-vm ~]$ koji build nfv7-opnfv-arno-el7 "git+http://dpdk.org/git/dpdk?#493db80afd009eea35ee7d95ad4aba49df5113a3" Created task: 15451 Task info: http://cbs.centos.org/koji/taskinfo?taskID=15451 Watching tasks (this may be safely interrupted)... 15451 build (nfv7-opnfv-arno-el7, /git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3): open (x86_64-2.cbs.centos.org) 15452 buildSRPMFromSCM (/git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3): free 15451 build (nfv7-opnfv-arno-el7, /git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3): open (x86_64-2.cbs.centos.org) -> FAILED: BuildError: dpdk.org:/git/dpdk is not in the list of allowed SCMs 1 free 0 open 0 done 1 failed 15452 buildSRPMFromSCM (/git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3): free -> FAILED: BuildError: dpdk.org:/git/dpdk is not in the list of allowed SCMs 0 free 0 open 0 done 2 failed 15451 build (nfv7-opnfv-arno-el7, /git/dpdk:493db80afd009eea35ee7d95ad4aba49df5113a3) failed </snap> Am I right? If so can someone please change permissions for the repo or let me know how I can add the repo to the allowed ones? If not can you point me to what I am doing wrong? :-) Again, the DPDK repo is http://dpdk.org/git/dpdk, the commit id that matches tag v2.0.0 is 493db80afd009eea35ee7d95ad4aba49df5113a3 and the spec file lives in pkg/dpdk.spec. I am assuming CBS will pick it up and create the rpm based on that spec file. Thanks! Joseph

2 2

c7-power64 proof of concept
by James O'Connor 25 Jun '15

25 Jun '15

I realize the altarch-power64 SIG is not officially established, but I want to share some technical progress. I created a private c7-power64 koji hub/builder environment using a pair of Fedora 22 PowerKVM guests. One guest is running Fedora 22 ppc64 and serving as a ppc/ppc64 koji builder. The second guest is running Fedora 22 ppc64le and serving as a ppc64le koji builder, koji hub, postgresql and httpd server. A pair of koji builders (ppc64, ppc64le) could be setup to integrate with cbs.centos.org instead of creating a separate koji hub. I created a c7-power64-build tag that contains arches "ppc64 ppc64le" and I am using Fedora 22 external koji repositories to serve as a build backstop until enough c7-power64 rpms are built. I am currently building with src rpms from http://vault.centos.org/7.1.1503/os/Source/SPackages/ although some ppc64le specific patches will need to be pulled from the c7-ppc64le branch on git.centos.org $ koji taginfo c7-power64-build Tag: c7-power64-build [2] Arches: ppc64 ppc64le Groups: build, srpm-build This tag is a buildroot for one or more targets Current repo: repo#16: 2015-06-24 18:16:29.668635 Targets that build from this tag: c7-power64 External repos: 10 f22-ppc64 (http://c7-ppc64.localnet/mirror/f22/ppc64/os/) 15 f22-ppc64le (http://c7-ppc64le.localnet/mirror/f22/ppc64le/os/) Inheritance: 0 .... c7-power64 [1] Next steps involve resolving some toolchain hiccups. c7 binutils fails to build with Fedora 22 gcc-5.1 and c7 gcc.ppc64 fails to build because Fedora 22 doesn’t have a 32-bit libc.so.6 needed for multilib gcc. To preserve the RHEL 7 ppc/ppc64 multilib environment a few interim c7 gcc/glibc builds will be needed. Happy to share any configuration steps or help do the work on official CentOS infrastructure as we move forward with an altarch-power64 SIG.

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