devel

devel@lists.centos.org

5 participants
4641 discussions

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

CentOS Cloud SIG meeting notes
by Rich Bowen 18 Jun '15

18 Jun '15

===================== #centos-devel Meeting ===================== Meeting started by rbowen at 15:05:53 UTC. The full logs are available at centos-devel/2015/centos-devel.2015-06-18-15.05.log.html . Meeting summary --------------- * CentOS Cloud SIG (rbowen, 15:06:00) * Roll Call (rbowen, 15:06:31) * GSoC Update (rbowen, 15:08:03) * ACTION: tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. (tmrts, 15:12:11) * LINK: https://github.com/TamerTas/cloud-init (tmrts, 15:12:25) * ACTION: tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. (tmrts, 15:13:31) * LINK: https://github.com/TamerTas/cloud-init (tmrts, 15:13:38) * Action items (rbowen, 15:24:56) * LINK: http://seven.centos.org/2015/06/introduction-to-cloud-sig-talk-in-fudcon-pu… (rbowen, 15:27:08) * ACTION: rbowen will write posts about "big tent" on seven.centos.org (rbowen, 15:28:03) * Packaging/CI update (rbowen, 15:28:25) * Open Floor (rbowen, 15:32:23) * LINK: https://github.com/apevec/centos-release-openstack/ <= this is the content of our release package (number80, 15:41:43) Meeting ended at 15:52:46 UTC. Action Items ------------ * tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. * tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. * rbowen will write posts about "big tent" on seven.centos.org Action Items, by person ----------------------- * rbowen * rbowen will write posts about "big tent" on seven.centos.org * tmrts * tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. * tmrts I plan that next week network configuration, RESTful client and systemd configuration(start-up services) will be over. * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * rbowen (50) * number80 (31) * dneary (23) * tmrts (18) * kbsingh (16) * kushal (12) * asad_ (9) * centbot (3) -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

Office Hours / Happy hours
by Karanbir Singh 18 Jun '15

18 Jun '15

hi, Over the last couple of months, an increasing number of people have been getting in touch with me to ask about various things in the project and also to find out how they can get started contributing to the project. So what I'd like to do is start up a set of office-hours slots in a week where I will make myself available on irc, phone, web ( hangout ? ) and anyone can come along for a chat. I shall also try and have other people come along and join in from the existing contributors pool. To start things off, I am going to be available on all Thursdays: - 08:30-09:00 am UTC (9:30am London, 2:00pm, India, 4:30pm Singapore) - 04:00-04:30 pm UTC (5:00pm London, 12noon Eastern, 9am Pacific ) During this time, you can find me on #centos-devel irc.freenode.net ( as 'kbsingh'), and you can also call me on the phone at +44 207 009 4455. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

5 15

[PATCH/cbs-tools] create_sig script: Loop through all koji permissions
by Brian Stinson 17 Jun '15

17 Jun '15

A user may have multiple permissions in addition to admin. This patch looks through all permissions in case admin is not the only permission assigned to a user. --- scripts/create_sig.sh | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/scripts/create_sig.sh b/scripts/create_sig.sh index 349c01b..281500d 100755 --- a/scripts/create_sig.sh +++ b/scripts/create_sig.sh @@ -81,7 +81,14 @@ fi # Check if user is allowed to send command to koji and has 'admin' permission KOJI=`which koji` PERM=`$KOJI list-permissions --mine` -if [ "$PERM" != "admin" ] +ADMIN=false + +for P in $PERM +do + [[ $P == 'admin' ]] && ADMIN=true; break +done + +if [ "$ADMIN" != true ] then echo "[ERROR] Koji misconfigure/missing admin privilege for creating SIG tags" exit 1 -- 1.8.3.1

1 0

[CI] Short scheduled Jenkins restart between 15:00 and 16:00 UTC
by Brian Stinson 17 Jun '15

17 Jun '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Folks, We are working on adding a few plugins to Jenkins and we need to schedule a very short reboot (we are expecting it to take less than 30 seconds) sometime between 15:00 and 16:00 UTC. The reboot will happen in that window as soon as the currently running jobs finish. If you have any questions, please send email to ci(a)centos.org Cheers! Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVgYKJAAoJEIMGvNKzCweM3s4P/1MYqpJGPjzXrLaCJDxZXYVg Ebrknsbl/sfXIEsbS3lXqfEPhaRvhghLawG+oNN9EKiaEUe9ETEAWtKnLOBQvH3A gxgxnNDoLsK+aBAL2IaRnJDFE0Pm5sh6u6tSkziZdczARvaoffAuNeYfW3FdtTxI VdTbz2o7EsPNaudYDdH1LO1LytnloW3z4GJxkyy4CaV3IOuJF+m35fOLK0qxqQKU MZ9F7oyGgXHWJKrpklC+GxuUufylXj6S0QW38+NgxeRA0L4v/TNmoM9nfAQCaMR5 FL4mn15no96sXBV1yAJ46mOVeij5EBLYGancc5alHeN5eDRhOl7dVUmbw/311BwI n3e+GC4ZKxK1Wn7N/nS1l0OLf+2nO0QU0VOfPqj0PizWxXzJV5kCYsHC10Y7uExH ZtPwSVgtZ8hAmP455SjfD3HvbkHUK11ors8IIg1Wa+WAxQFqVqR/W19S0Z6/fwKf l9nXtd3uWy9Z/GavO/TKxOQ605c66gIbksuFh13XwgtVEcBgDOI9/qM+Jy7BB/AA iMCgkXgxVMJ0F530fzGmCO3RT2KGmqgHHmfaathd3gHIEUJyETITwk5DfCIgou5G N+LVm6/kLn8LH7g27zud1H1OhxpInzEw65eXR+jSiDUbfXgBobS9vZZRT23pN6VQ xdE8lmjB0u5e1dyF4300 =pX6g -----END PGP SIGNATURE-----

1 2

Kubernetes package new build tag
by Navid Shaikh 17 Jun '15

17 Jun '15

Hi, There was a discussion to move kubernetes package under virt7-docker-*, earlier the kubernetes used to get updated under virt7-testing tag. Added the package in `virt7-docker-common-testing` tag, and tried building it for target `virt7-docker-common-el7`, however it failed with error: 15144 build (virt7-docker-common-el7, kubernetes-0.19.0-0.4.gita8269e3.el7.src.rpm): FAILED: BuildError: package kubernetes not in list for tag virt7-docker-common-candidate Then, I added the package in tag `virt7-docker-common-candidate` and the build [1] is green. I could see the built packages in repo `virt7-docker-common-candidate` [2]. Is kubernetes package populated in correct repo? I was expecting it go in testing repo `virt7-docker-common-testing` [3] first. Please correct me if I am missing something here. [1] http://cbs.centos.org/koji/buildinfo?buildID=1330 [2] http://cbs.centos.org/repos/virt7-docker-common-candidate/x86_64/os/Package… [3] http://cbs.centos.org/repos/virt7-docker-common-testing/x86_64/os/Packages/ -- Navid

2 1

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