devel January 2015

devel@lists.centos.org

55 participants
48 discussions

cbs feature req: building embargoed content
by Karanbir Singh 12 Mar '15

12 Mar '15

hi guys, we need a way to build embargo'd content like reimzul's priv-build, that does not make stuff public till a specific date ( the actual push to public can be manual ); how would we achieve this on cbs ? I guess the git stuff is easier since it can just be a scratch build from srpm and people need not push the git content back to git.centos.org till embargo expiry. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

7 14

SIG repo layout and conflicts between projects within a SIG
by George Dunlap 10 Mar '15

10 Mar '15

At the moment, we're essentially using yum repos as the "patch" mechanism to CentOS Base: SIGs populate a repo with packages they want to add / override, and all other packages default to Base. The current setup is that every sig has exactly one production repo per CentOS version. Also, we seem to be wanting to see SIGs not as individual projects, but to make the 'G' an actual "group": so, for instance, the Virt SIG has both Xen and Docker, and we've recently approved oVirt. But there's a bit of a conflict here: what if one project in the SIG wants to use the package from Base, and another project in the SIG wants to use a custom-built package? Or what if both projects want to customize their packages in different ways? In particular: the Docker project in the Virt SIG wants to supply updated versions of Docker; but at the moment uses the kernel package from Base. The Xen project, on the other hand, needs to supply a different kernel package that has dom0 support enabled. Up until this point, this hasn't been an issue because I've been doing Xen development in virt6-testing, and Lokesh has been doing Docker development in virt7-testing. But I'm hoping to get Xen for CentOS 7 out soon, and I was just about to upload the Xen kernel to the CBS, when it occurred to me that if I did so, then everyone using the virt7-testing repo for Docker would suddenly get my updated kernel as well. So it seems we have a couple of ways to approach it. 1. Keep it one repo per SIG, and make all projects in a SIG sort out shared dependencies. 2. Allow one repo per *project* within a SIG (e.g., virt6-xen, virt7-docker) 3. Have some alternate way of doing a "patch", instead of repos. In the case of xen / docker, I haven't talked with Lokesh about this at all; it may be that he's fine with sharing a kernel with Xen. But it does increase the workload: now Lokesh needs to maintain the Docker side of the kernel, whereas before they could just rely on our upstream to do a lot of that testing. Furthermore, it increases the complexity of development and testing: before when doing kernel work, I could just test Xen; now the kernel needs to be tested by both Xen and Docker. And finally, now users of both projects get a kernel update whenever either one does. Which, of course, is pretty much the same as any other distro; but as a whole, at the moment at least, we have a lot less resources than any other distro our size and popularity. On the whole I'm inclined to prefer #2. Thoughts? -George

5 8

a kernel-cloud
by Karanbir Singh 18 Feb '15

18 Feb '15

In conversations, the idea of a trimmed down kernel for cloud images has come up repeatedly. I was wondering if anyone would like to help define what this might look like and then help maintain something of this nature for the CentOS Project ( ideally targetting CentOS-6 and 7 ). - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

5 6

Centos 7 - gnome-initial-setup with uid < 500
by Olivier Delhomme 12 Feb '15

12 Feb '15

Hi there, I install Centos 7 machines through kickstart + a post install script. I do not need the gnome-initial-setup to run at all. My post install script create a user and deletes the guest account. When the uid of the newly created user is > 500 everything is fine but when the uid is < 500 the gnome-initial-setup still shows up. Can anyone tell me how to disable/configure gnome-initial-setup for users with uid < 500 ? Cheers, Olivier DELHOMME.

3 7

CentOS Bug Tracker and ABRT
by Jakub Filak 04 Feb '15

04 Feb '15

Hello everyone, I want to briefly introduce myself. I am a Red Hat employee working on ABRT[1]. We have recently added support for CentOS on the ABRT server[2] and we would like continue in these integration efforts. First of all, I want to submit a pair of patches improving ABRT's UX on CentOS: - do not offer users to report to Red Hat Portal - offer users to send an email to upstream - stop wasting of resources by running sos, because its output is useless for CentOS users In the near future, we would like to integrate ABRT with CentOS Bug Tracker in the same way as ABRT integrates with Red Hat Bugzilla[3]. We are done with the analysis phase[4] and, now, we are working on a testsuite[5]. Unfortunately, MantisBT misses more advanced searching what prevents us from implementing a tool similar to one we have for Bugzilla. At least we need to search by DUPHASH (an unique identifier of a crash, something like tag). Would you be willing to run a MantisBT plugin adding the things we need, if we develop it? Best regards, Jakub http://wiki.centos.org/JakubFilak 1: https://github.com/abrt 2: https://abrt.fedoraproject.org/ 3: https://github.com/abrt/libreport/issues/272 4: https://github.com/abrt/libreport/wiki/MantisBT 5: https://github.com/abrt/abrt/tree/reporter-mantisbt

4 12

Xfce for CentOS group
by Anders F Björklund 02 Feb '15

02 Feb '15

Hi list! Since the Alternative Desktop SIG didn't happen, we thought we would make a more focused effort and improve the Xfce desktop environment experience on CentOS. That might end up being a dedicated CentOS SIG, or just a couple of improvements to the existing packages from EPEL. Once upon a time, or more precisely: back in the CentOS 5.0 days, Xfce 4.4 was available in Extras and it was a pretty simple install that just worked "out of the box". Now, there's the newer versions available via EPEL - but the experience is nowhere near painless... Going to try to meet up with other interested parties during FOSDEM, to see if we can't improve upon that and at least fix the low hanging issues. And get some better Xfce testing and feedback going, as well. A more long-term goal is make it an alternative to GNOME (Workstation). I've rounded up some of the issues, that currently exist: * The theme and icons are wrong, either missing or just ugly * The background image is wrong, ending up with a single color * X11 and Fonts are missing, so just adding the group doesn't work * Some bugs need backporting or fixing, like in Terminal or Xfwm. See http://afb.users.sourceforge.net/xfce/centos/centos-xfce.html Right now, one starts with a Minimal (or Server) install of CentOS. Then adds Base, X11 (including fonts), and finally Xfce (from EPEL). Once the aforementioned problems are taken care of, that should be it. Eventually, it might even end up being a "spin" or available image ? As mentioned earlier, here are the applicable versions of each: * CentOS 5 - Xfce 4.4 (in CentOS Extras) * CentOS 5 - Xfce 4.6 (based on Fedora 6) * CentOS 6 - Xfce 4.8 (based on Fedora 12) * CentOS 7 - Xfce 4.10 (based on Fedora 18) To replace GNOME PackageKit there's the Yum Extender, and to replace GDM there's LightDM (more work is needed, to make a CentOS-6 version). The GNOME icons and GNOME themes will probably "work" to start with, but one can probably improve upon that as well (as a lower priority). Something like http://afb.users.sourceforge.net/xfce/xfce-brave.png If you are interested in helping out with testing, packaging or developing (backporting, fixing the upstream issues, and so on) then please say so. I'll try to have some more detailed lists and updated packages with me, for the FOSDEM meetup in the weekend... * http://wiki.centos.org/Events/Fosdem2015 --anders

5 10

Where should golang-github-gorilla-mux live?
by Matthias Schroeder 02 Feb '15

02 Feb '15

Hi guys, I noticed that golang-github-gorilla-mux 0-0.15.git136d54f.el7_0 is in the ‘updates' and in the ‘extras' repo. Older versions where only in ‘extras’. Is that a conscious change of policy, or did something go wrong with the routing of that version? Cheers, Matthias - just curious

3 3

Port CloudSigma to CentOS's CloudInit
by Viktor Petersson 29 Jan '15

29 Jan '15

Hey guys, I had a conversation with Jim Perrin and Karanbir Singh about this and it should be relatively trivial. However, Jim suggested that we moved the discussion here. Here is the status today: * The CloudSigma provider for CloudInit is complete and is maintained by Canonical[1] and is included in (12.04 and forward) * Jim wrote a patch (attached). It isn't complete, but it is a start. * There is also a port to CoreOS (re-written in Go) [2] * Since I didn't write the code, I don't know of the exact workflow, but I think these are the relevant files: ** cloudinit/cs_utils.py ** cloudinit/sources/DataSourceCloudSigma.py ** tests/unittests/test_datasource/test_cloudsigma.py I'm involved with CloudSigma, and I'd be happy to sponsor anyone willing to take on the task of porting this with resources at CloudSigma for testing. Unfortunately, I don't have any internal resources to allocate towards this at this point, but I know that we have plenty of customers running CentOS that would love to see this happen. I'd also be happy with answering any questions and help with the QA of this. Thanks! [1] https://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cl… [2] https://github.com/coreos/coreos-cloudinit/issues/184

3 3

comps in SIG content repos
by Karanbir Singh 29 Jan '15

29 Jan '15

hi, thoughts around requiring SIG repos to carry a comps.xml file ? that will allow us to also have SIG repo configs be usable at install time and yum group operations to run on installed machines. regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

Proposal to Cancel the CBS/Infra Meeting on 02-Feb
by Brian Stinson 28 Jan '15

28 Jan '15

Hi All, Since quite a few of us will be traveling or recovering from Fosdem, I propose that we cancel the CBS meeting on Monday 02-Feb. If there are any discussion items, please send them to the centos-devel list. One item would be scheduling the next CBS meeting since I'm not sure of everyone's schedule over the next couple of weeks. Cheers! Brian -- Brian Stinson bstinson(a)ksu.edu | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2015