devel

devel@lists.centos.org

10 participants
4617 discussions

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

Weird Qt painting bug on CentOS7
by Justin Clift 22 Jun '15

22 Jun '15

With the upstream DB4S project (previously known as SQLite Browser), we've had a bug reported filed of a weird Qt painting problem... which only happens on CentOS 7: https://github.com/sqlitebrowser/sqlitebrowser/issues/354#issuecomment-1117… The direct sceenshot here: https://cloud.githubusercontent.com/assets/1067355/8144743/f944b27e-11e3-11… In the field names (middle section, not bottom section), the new name "XX" is overwriting the old name "Field1". On other OS, and other Linux distro's, the "Field1" text has been correctly wiped already so only shows "XX". Has anyone seen anything like this before, or know how we should figure out what's going wrong? Regards and best wishes, Justin Clift -- GlusterFS - http://www.gluster.org An open source, distributed file system scaling to several petabytes, and handling thousands of clients. My personal twitter: twitter.com/realjustinclift

2 1

"Rebuild" images ready for testing
by Joe Brockmeier 21 Jun '15

21 Jun '15

Good News, Everybody! KB let me know today that we've got some images of the rebuild of RHEL Atomic Host ready to test. You can find images here: http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/ This includes 2 flavors of Vagrant box (libvirt/KVM and VirtualBox), a qcow2 image, and ISO image suitable for installing onto bare metal or other environments. We've done some preliminary testing but more is needed. We're hoping to announce next week, so I'd invite all interested parties to test these and let us know if you find any anomalies. Best, jzb -- Joe Brockmeier | Open Source and Standards (OSAS) jzb(a)redhat.com | http://community.redhat.com/ Twitter: @jzb | http://projectatomic.io/

4 6

Finished a prototype of GSoC project: Implement a new doc toolchain
by Lei Yang 20 Jun '15

20 Jun '15

Hi, Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute. This is the workflow of the prototype: 1. Contributor creates a new pull request on GitHub 2. A corresponding issue is automatically created on Pagure 3. Staff and contributor discuss on Pagure 4. When the pull request can be accepted, it is marked as “fixed”, and the pull request on github is automatically merged 5. New change is synced to Pagure (doc website will update according to Pagure repo, to be implemented later) We have made a prototype performing the steps above, and is now running ;) Next we plan to integrate a CI so the doc can be built in real time and ready for staff to review. Could you please give us some suggestions about the workflow above and about the toolchain? The original GSoC idea can be found here: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain <http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain> We use Pagure as a part of the toolchain. Pagure is an excellent git-centered forge created by Pierre-Yves Chibon <pingou(a)pingoured.fr <mailto:pingou@pingoured.fr>>. Currently Pagure is in its early stage and the APIs and web hooks are changing and improving. We are working closely with Pierre to better integrate Pagure into the toolchain. In the future we plan to sync complete pull request so that discussion can happen either on github or Paugre, and contributor doesn’t need to leave github in the whole process, which lowers the barrier of contributing a lot. To test it, you may create a PR on github. A corresponding issue will be created automatically on Pagure, so you may go to Pagure.io to check it. If you want to merge the PR, change the status of issue from Open to Fixed on Pagure (need admin access to the repo, if you want to test this part, please email me or Kunaal <kunaalus(a)gmail.com <mailto:kunaalus@gmail.com>> so we can add you as admin). Once the issue is marked as Fixed, the PR on github will be merged. GitHub repo link: https://github.com/yangl1996/doc-test <https://github.com/yangl1996/doc-test> Pagure repo link: https://pagure.io/docs-test <https://pagure.io/docs-test> The syncing tool is a prototype and is a basic part of the toolchain. Please tell us what you think about the workflow, the syncing tool and the idea. Thank you in advance :) Also, we are not very sure whether running a Pagure instance will add much workload to sys admin team. What’s your idea? Thanks! Regards, Lei

1 0

Re: [CentOS-devel] [atomic-devel] "Rebuild" images ready for testing
by Karanbir Singh 18 Jun '15

18 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/06/15 22:57, James wrote: > On Thu, Jun 18, 2015 at 4:49 PM, Joe Brockmeier <jzb(a)redhat.com> > wrote: >> KB let me know today that we've got some images of the rebuild of >> RHEL Atomic Host ready to test. >> >> You can find images here: >> >> http://buildlogs.centos.org/centos/7/atomic-host/x86_64/images/ > > > RHEL or CentOS ? > > The CentOS Atomic Host is a downstream rebuild of the RHEL Atomic Host. These are images of the CentOS Atomic Host. 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJVg0qZAAoJEI3Oi2Mx7xbteYYH/RtSt0JGUJKTUwU4HfRMRxBO pt/RwKAjdeLVU+ZD2Zg7vy12X1YEsrjcxlYzLw4usnNtyBa6rpgHZ/DFGoP85BCX cr0BKXjT4QrK02urlX4GndnST84jcYZYEl/WvpNIK2VfvPtSwRSxLqsaqqMWVHq9 psy0B0vP+thQrdFEd0DKg9xuEMu2HKUXQyYS4Tz4Rs2aOkknEVuM5lcHScL8+/OK 58FuDvAX9b3NITpPtEup4hyhuBM7/HUtoLlpr0uYNwBjnWQpws9S4Og+EsKj7BPK XLUIqrqReQSTkUzzVlFSFygR+DRhLvOzQoBHpolpkWuoHZzH1Iibua/okkrm9yA= =I/mK -----END PGP SIGNATURE-----

1 0

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