April 2015 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

The CentOS Project Visual Identity Structure
by Alain Reguera Delgado 08 May '15

08 May '15

Hello Everyone, I am wondering if we could have a talk about CentOS visual identity, so to consolidate the path to follow and coordinate further efforts in this matter. There are two points I would like to call attention to. The first one is the visual structure of CentOS Project (see http://wiki.centos.org/ArtWork/Identity) The second one is the CentOS Project logo (see http://wiki.centos.org/ArtWork/Brand/Logo) In the very specific case of CentOS Logo it is necessary to note that it is being used in different manners in official places. This affects the strength of the CentOS brand. For example, consider the construction described in the wiki page above and the logos shown in wiki.centos.org, bugs.centos.org and mirror.centos.org sites. Although they are similar they aren't exactly the same. The construction I propose in the wiki is based on the CentOS logo published in the sources of CentOS 5. In these files, the CentOS logo is entirely plain and does not have any ornament (like shadow or bright) on it. I am planning to put ready-to use CentOS logos files in SVG format in the wiki and I would like you to express your opinion in the correct CentOS logo that should be used so we can unify this and give more strength to CentOS Project visual identity. Best Regards, al.

3 5

Signed repomd.xml.asc files for CentOS-6 and CentOS-7 (testing)
by Johnny Hughes 08 May '15

08 May '15

We are looking at the possibility of providing signed repomd.xml.asc files for all CentOS controlled repos for CentOS-6 and CentOS-7. I have created an update repository for CentOS-6 and CentOS-7 for testing. They are not going to be maintained current (and are already a couple of updates behind) and should *NOT* be used in production ... but if we can get some people to test these on some testing platforms that would be great: http://dev.centos.org/centos/6/updates/x86_64/ http://dev.centos.org/centos/7/updates/x86_64/ Basically, to use signed metadata for these testing repos, you would need to modify the /etc/yum.repos.d/CentOS-Base.repo and do the following to the 'updates' section: 1. Remark out the current mirrorlist and/or baseurl statements. 2 Add the following: For CentOS-6: repo_gpgcheck=1 baseurl=http://dev.centos.org/centos/6/updates/x86_64/ For CentOS-7: repo_gpgcheck=1 baseurl=http://dev.centos.org/centos/7/updates/x86_64/ ================================ *DO NOT USE THESE REPOS FOR UPDATES LONG TERM, THEY ARE FOR TESTING ONLY* ================================ One thing we would like to figure out (and then tes)t is the ability to somehow get this key to be added automatically via a kick start so that one can use signed metadata for unattended installs. Without testing and feedback, and possibly key auto import capability, this proposal will likely go nowhere .. so if this is a feature that you want, please test and provide feedback and help us find a solution for auto import of the yum key. Thanks, Johnny Hughes

4 7

Building a downstream CentOS Atomic Host
by Karanbir Singh 07 May '15

07 May '15

Hi, One of the things that the Atomic SIG will attempt to do is build a downstream CentOS Atomic host, that is modelled on the RHEL Atomic host. Most code and info needed for this is now available, and its a good point to think about the build, release process. I've attached a map of what that might look like. Think of it as a proposal. Some of the things that are marked with red stars are things that we will try and help, from the Core SIG, to get this process onramped - but largely we are looking at community and SIG involvement here with the aim that the entire process can be offload ( taken over ? ) but the community. This process proposed here very closely maps to the Core CentOS Linux process. I would very much like to hear comments and thoughts around this from everyone on centos-devel, specially around areas where people can help. 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

9 29

moving from gitorious
by Karanbir Singh 07 May '15

07 May '15

Hi, We have some of our content currently hosted on gitorious.org that we mirror from git.centos.org - the intention being that git.centos.org is still the authority, but people can use the easier contribution path at gitorious to build karma and then get direct git commit access at git.centos.org since gitorious is going away, what are everyone's thoughts to consolidating all of this external contribution path on github.com/CentOS - we already host a bunch of content there. 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

10 17

Fixing up Xfce for CentOS 7
by Toni Spets 01 May '15

01 May '15

Hello list, I've been in contact with Anders F Björklund (afb) earlier this week regarding the state of Xfce on CentOS 7 and in general in any supported EPEL release. What we discussed was what he has done in the past for his personal use and what are the things we would both agree on that should get some attention to make the experience better. Here are some initial things that we think are critical (give or take, Anders has his own list): 1. Packaging issues - comp group @xfce-desktop doesn't depend on @X Window System so it doesn't really work and has some wrong packages and some missing - @xfce-desktop depends on gdm instead of lightdm, we think it should do that instead - dejavu sans fonts are not a dependency and fonts are broken because of that - gtk-xfce-engine package is missing (EPEL7) 2. Branding issues - "Default" appearance theme is missing (requires gtk-xfce-engine, request sent to EPEL) - default background is blank (broken Fedora branding, patch submitted) - default icon set is wrong and broken (should be GNOME because "Fedora" doesn't exist on RHEL, patch submitted) There are more, but these are one of the first usability issues that you would hit when installing Xfce from EPEL 7. I have submitted bug reports with proposed fixes for the background issue, default theming issue and missing gtk-xfce-engine package: https://bugzilla.redhat.com/show_bug.cgi?id=1200988 https://bugzilla.redhat.com/show_bug.cgi?id=1200992 https://bugzilla.redhat.com/show_bug.cgi?id=1201124 Now, getting EPEL fixed up would be in general a good effort since it's shared between all derivatives of RHEL/CentOS and more people will get the base benefits. That said, there are two ways this SIG could be constructed: a) shim wrapper around EPEL to create a spin and possibly add some CentOS specific branding, give EPEL maintainer all the help we can to get the packages working, try push most if not all packaging work to EPEL b) completely replace EPEL by our own repo which has all the Xfce packages and anything we would want The A option depends on if the maintainer is willing to let us help as much as we want and would accept some of the changes we'd need. It would also imply the current EPEL maintainer(s) would continue maintaining and be our upstream or someone would join the EPEL folks as co-maintainers. The amount of initial work would be minimal compared to doing everything custom and as I said before, it benefits every RHEL derivative, including RHEL itself. We still need some SIG specific packages like CentOS specific branding and possibly our own default panel layout so it's not all upstream work. This approach might also be tad slower because we have an upstream and all packaging stuff except barnding would go through them. The B option gives us more power and could speed up the process a lot. We can select and backport the set of Xfce packages as fast as we can.Karanbin Singh was kind enough to provide some info about how CentOS SIGs work and what resources would be available (automatic builds, official SIG repos etc.) so all the backend stuff is there waiting to be untilized for this kind of SIG. However, this approach would be very CentOS specific and would require the SIG to be fairly active in maintaining the packages when our upstream (the Xfce project) makes point releases. I can say upfront that person wouldn't be me, so if someone is up to this after the initial sprint of work has ended, that would be something to consider. One more very important thing to note is that EPEL 7 is set to Xfce 4.10 and 4.12 just came fresh out of the oven. If we do A, I'm fairly sure we would need to stick with 4.10 unless the maintainer feels 4.12 upgrade would be possible, then it's a win for option A. The maintainer (or one of them) also maintains a 4.12 copr for F20 so I strongly believe he knows much more about Xfce packaging than me for one. If we do option B we could scrap 4.10 immediately and package 4.12. There is no reason to use 4.10 as a SIG would be the perfect place to get more up-to-date experience on top of stable core. I'm up for either one, it's up to what you other people would see as being more useful. Maybe both if there is enough interest? Fix EPEL for the greater good and still have our own SIG 4.12 stuff on top of it for CentOS only. Anyone into this except me and Anders? Ideas, suggestions? -- Toni Spets

8 16

GSoC projects and SIG meetings
by Karanbir Singh 01 May '15

01 May '15

hi, All the GSoC stuff going through should map to a SIG ( or in some cases multiple ones ) - it would be great to see the GSoC students come along and interface with the SIG's, and maybe do updates on progress at the SIG Meetings. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 4

RH patches v/s vanilla docker in CentOS
by Lokesh Mandvekar 30 Apr '15

30 Apr '15

I'm hoping to reach a decision on how we handle docker rpms (vanilla +/- rh patches) There's the default docker that CentOS gets in extras from RHEL which comes with RH patches (of course). But this kinda comes quite a bit after upstream docker releases. Next up is 'docker' in virt SIG which usually tracks upstream releases. Would people prefer this build be vanilla upstream or with RH patches included. Then there is 'docker-master' in virt SIG which is a daily rebuild of docker upstream master branch + redhat patches. We could either: a) ship 'docker' in virt SIG with RH patches and also provide a 'docker-upstream' which is a vanilla upstream package b) ship 'docker' in virt SIG without any RH patches and provide a 'docker-redhat' with RH patches c) ...anything else?? Comments? -- Lokesh Freenode, OFTC: lsm5 GPG: 0xC7C3A0DD

8 18

[SIG Harden] Personal goals
by leam hall 29 Apr '15

29 Apr '15

My personal project goal is to work on scripts and Puppet content to meet STIG requirements. I'm not really talented enough to putz around with the kernel stuff but don't object if others do. Leam -- Mind on a Mission <http://leamhall.blogspot.com/>

4 9

[Cloud SIG] RDO/OpenStack test day, May 5th, 6th
by Rich Bowen 29 Apr '15

29 Apr '15

For those that are interested in the progress of the RDO OpenStack packaging effort, we'll be having an RDO test day May 5th and 6th (48 hours, so that folks from every timezone have a chance to participate at some point). We'll be testing the RDO packages of the Kilo release. We'd appreciate it if you can find an hour or two some time in that window to come help us out. Links: Main info: https://www.rdoproject.org/RDO_test_day_Kilo Test scenarios: https://www.rdoproject.org/RDO_test_day_Kilo_RC_milestone_test_cases Live discussion on #rdo (Freenode IRC). Async discussion on rdo-list http://www.redhat.com/mailman/listinfo/rdo-list -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

Using gcc -fsanitize=thread on C7
by Fred Smith 28 Apr '15

28 Apr '15

Hi all! I'm attempting to use the thread sanitizer (in gcc 4.8.x) on a multi threaded program. When I run the program I get a lot of terse output from the thread sanitizer, much of which refers to hits inside libtsan, libc, and libcrypto. I'm trying to find the debuginfo for those libraries with the hope that will allow human-readable info in that output. But so far I've not found anything that looks like the right stuff. Suggestions, anyone? Thanks! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- The eyes of the Lord are everywhere, keeping watch on the wicked and the good. ----------------------------- Proverbs 15:3 (niv) -----------------------------

2 1

Fwd: RDO (Cloud SIG) meetup at OpenStack Summit
by Rich Bowen 28 Apr '15

28 Apr '15

FYI, for those of you who care about the Cloud SIG, and will be at the OpenStack Summit in Vancouver next month. -------- Forwarded Message -------- Subject: [Rdo-list] RDO meetup at OpenStack Summit Date: Mon, 27 Apr 2015 16:58:15 -0400 From: Rich Bowen <rbowen(a)redhat.com> To: rdo-list(a)redhat.com <rdo-list(a)redhat.com> I am still working on getting a room for an RDO meetup at OpenStack Summit, but I wanted to go ahead and get this out there to start collecting agenda of what people want to discuss and/or work on at that meetup. I've put up an etherpad at https://etherpad.openstack.org/p/RDO_Vancouver where we can start collect those ideas, and where I will post times/locations once I get them. Thanks -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://rdoproject.org/

1 0

CentOS7 Vagrant box with container runtime and tools
by Lalatendu Mohanty 28 Apr '15

28 Apr '15

Hi All, This is my first attempt to create a CentOS7 Vagrant box using CBS (CentOS build system). The idea is to create a Vagrant image which can used as development box for packaging applications in CentOS Linux containers. This Vagrant box will also have required Linux container tools (e.g. atomic command line, k8ns, etcd). If you want to see any tool in this Vagrant box, let me know. The present build includes Docker. The scratch build is at http://cbs.centos.org/koji/taskinfo?taskID=10480 Here are steps how you can quickly test the image. I am looking for feedback on the same. More detailed information is present in the github project [1] . I have used Fedora21 to set-up Vagrant with libvirt/KVM backend. There is a effort going on to provide Vagrant packages on CentOS too as now it is not available through CentOS core. #Setting up Vagrant on Fedora 21 $yum/dnf install -y vagrant-libvirt vagrant #Running the Vagrant box with Vagrant and libvirt I have also uploaded the images in https://atlas.hashicorp.com/lalatendum/boxes/centos7-docker Step-1 : Initialising a new Vagrant environment by creating a Vagrantfile vagrant init lalatendum/centos7-docker Step-2 : To start the vagrant image and ssh in to it, please run following command vagrant up vagrant ssh vagrant ssh should take you inside of the Vagrant box #To destroy the Vagrant box vagrant destroy #Running docker inside the Vagrant box Inside the vagrant box, you should be run docker containers Example: (following commands should be run inside the Vagrant box) docker pull centos docker run -t -i centos /bin/bash [1] https://github.com/LalatenduMohanty/centos7-container-app-vagrant-box Thanks, Lala

2 1

Possible 7.1 Install Bug
by Kirk Bocek 27 Apr '15

27 Apr '15

Hope I'm not spamming the devs here, but I've got what really feels like a bug with the installer here. I've got a new SuperMicro X10-DRI motherboard with a 3Ware 9750 raid card that hangs during installation of 7.1. If I pull the card, the installer proceeds normally. CentOS 6.6 installs without error on this hardware so I know the hardware is working. I've documented this here: https://www.centos.org/forums/viewtopic.php?f=49&t=52231 If there is more information I can provide, please let me know. Kirk Bocek

1 0

Upstream for dist-git [RFC]
by Miroslav Suchý 27 Apr '15

27 Apr '15

Hi, Adam Samalík took dist-git files from fedora-infra ansible.git. He separated what belongs to dist-git itself and what is Fedora specific and with cooperation of Dan Mach and Palo Babincak he created upstream for dist-git: https://github.com/release-engineering/dist-git This is Fedora version of dist-git and already have passed first round of comments in fedora-infra. The changes from ansible.git version are described here: https://github.com/release-engineering/dist-git/blob/master/changes.txt and he extracted some code to be configuration driven: https://github.com/release-engineering/dist-git/blob/master/configs/dist-gi… I know that CentOS is one of the user of dist-git. It would be nice if you can contribute your changes to dist-git to this upstream and eventually use dist-git rpm package - it passed through package review in Fedora just now. Future plans: 1) Listen to your initial feedback and do alternations according to your feedback. 2) Change Fedora dist-git server to use this package. .... 5) Enjoy the benefits of common upstream. -- Miroslav Suchy, RHCA Red Hat, Senior Software Engineer, #brno, #devexp, #fedora-buildsys

2 1

confd spec file
by stephan schultchen 27 Apr '15

27 Apr '15

Hey CentOS fellows, i have created confd spec for centos 7, that is more or less based on the etcd spec file found on cbs ( http://cbs.centos.org/koji/packageinfo?packageID=102) that i would like to contribute. I guess it would fit nicely to the SIGs that etcd is part off. What are the steps to take to get the spec reviewed and added to these SIGs? Cheers, schlitzer

1 0

CBS/Infra Meeting 27-Apr-2015 14:00 UTC
by Brian Stinson 27 Apr '15

27 Apr '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi All! It's time for another meeting to discuss the Community Build System. We will be meeting in #centos-devel on Freenode. Here's our Agenda: #info Topic: Quick Updates #info Topic: Central Authentication #info Topic: Open Floor See you there! Brian - -- Brian Stinson brian(a)bstinson.com | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJVPYx/AAoJEIMGvNKzCweMUAcP/3XWzoMuE0YCHJZE1RnOmPxq LM8IOtiWqoRkH2kpvmxsaNiOdW1xuEC/oMIwzCzVdYIGOeb4m2rGO6fJqNpor3SE M8JizlzX/siBHpDvJrNfElbKUbwdzqxdOJQYbNo1jUVECimGtko4Vmhgb3fYXJr0 xDbqU/qqVBiVgZWHFcjBabK7GUE/JV61JLxgt7Ttnt4Uc+q+N8bFf533JjgEhRz7 BseYRH8s6EDGpqwunBmoTDSj64lEP2r2ceLmSC+YiOTeCP9GfP0u9cWOlpx8szRs jqVZ1w7b/MSGN9FJLvR3eGA4Dfh0fzuI5L8qf/KutlGc8uA+/q5Xv4Jd/twkGZli iHtfltwkJUXxL8TcwEe05D6doImjnvnJHhVdtfk8L/PXap9/0KJmfiMm5YEdaX9q 6Fofm+HFs9tOvjDV7h899yIIqtoF0XbDftKTQAVPM0bQZalgaswT86hBlk357DDq ffMdKrltdm4nWAhsCdtUmhGVUD7B+4kK7Yg86VFp89ghqDt1Rj6k4JneVd27wE7M CS5O3PWojKlgZ1MdQSAB0bgI9IpsvJ1p4XEO7TVFZqx9rocrNDvqTa1MHUsE9Tu5 MR9m/4GLl2BKjHUWfCd4MO0paODux0KfDcGUNSpecf2BN/A/hDJ+djNNx9SIKUcy PD50QMjYZcqhvO+hsdtr =ri6T -----END PGP SIGNATURE-----

1 0

CentOS - SIG Hardening
by Earl A Ramirez 22 Apr '15

22 Apr '15

Dear CentOS Development Team, I am interested in starting a new SIG or merging with the ‘Hardening’ SIG, I didn’t find sufficient information about the hardening SIG. I have been on the mailing list for some years and I have noticed a number of concerns with regards to security, e.g. the default sshd_config, gnome user list and more. My goal is to use the base and modify the OS with these changes and make it available for the CentOS community, I will mention this on the mailing list to get the community feedback so that they can have an opportunity to contribute, and more importantly get an OS that meets their needs, with regards to their security concerns. I’m not too familiar with the CentOS build system, however I started to read up on it and practice to get a feel on things. Some of the things that I will like to change are as follow: SSH: disable root (uncomment 'PermitRootLogin' and change to no) enable 'strictMode' modify 'MaxAuthTries' modify 'ClientAliveInterval' modify 'ClientAliveCountMax' Gnome: disable Gnome user list Console: Remove reboot, halt poweroff from /etc/security/console.app Looking forward for your response on how can I proceed with this? -- Kind Regards Earl Ramirez

5 12

Re: [CentOS-devel] CentOS - SIG Hardening
by James B. Byrne 22 Apr '15

22 Apr '15

Earl A Ramirez earlaramirez at gmail.com Mon Apr 13 11:24:27 UTC 2015 > I am interested in starting a new SIG or merging with the > Hardening SIG, I didnt find sufficient information about > the hardening SIG. I have been on the mailing list for some > years and I have noticed a number of concerns with regards > to security, e.g. the default sshd_config, gnome user list > and more. I will participate; given that the SIG is established. -- *** E-Mail is NOT a SECURE channel *** 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

Probably no CentOS SCLo SIG sync-up meeting (2015-04-22)
by Honza Horak 22 Apr '15

22 Apr '15

Unfortunately, I've just learnt can't make it for today's 3 UTC sync-up meeting, so unless anybody else is volunteering to chair it after such a short notice, we can skip and talk on IRC/ML. Just for getting some update, we've just had an earlier talk about tags for SCL, cleared up few things and agreed to continue with further discussions about tags/branches on IRC. Honza

1 0

bugs.centos.org summary posted
by Karanbir Singh 22 Apr '15

22 Apr '15

hi I guess this is more for Jim / Ralph : but is there anyway to get mantis to send out an email nightly, with a list of 'new' bugs reported during the last 24 hrs ? Additional win if we can also get a list of bugs that have had no activity for > 60 days and are not in status: Feedback Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

Atomic devel builds automation
by Karanbir Singh 21 Apr '15

21 Apr '15

hi, The Atomic devel builds are now running from cron again, after a 2 week lag, they now run every 12 hours, midnight and midday UTC. These builds now also run with a complete toolchain update taking place before the build gets run. The build script is now in git itself : https://github.com/CentOS/sig-atomic-buildscripts/blob/master/build_ostree_… and the cron worker will git pull, before running this, so updates are consumed immediately. That does make line 10 to 12 of this script completely redundant, but I've left it in as an indicator. Build runs are logged at : http://buildlogs.centos.org/centos/7/atomic/x86_64/Builds/ And the ostree repo remains at : http://buildlogs.centos.org/centos/7/atomic/x86_64/repo/ Once the installer image starts building, we can push that to http://buildlogs.centos.org/centos/7/atomic/x86_64/ which would in turn allow the vagrant and image builds to also run. Regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 5

summary for tags/branches in SCLo SIG
by Honza Horak 20 Apr '15

20 Apr '15

Hi guys, few days back we talked about tags and branches names on the SCLo meeting and I found out that I missed the important CBS meeting [1].. which I'm sorry.. Anyway, we ended with things in our heads but I can't find anything written, so I tried to summarize what should be the result (as I understood it) and would like to ask for correction if I failed to get it... I realize that rh-mariadb100 confuses people, because it includes rh- in the name, but for tags/branches names it is nothing more than part of the collection name. If the dash is an issue, then we may use underscore (rh_mariadb100) or just rhmariadb100 if necessary for tags/branches, but mariadb100 alone is simply not correct. What is more, not all collections in RHSCL have rh- prefix (existing collections) although the new collections should have it in the future. Anyway, I rather took another collection (that doesn't use rh- prefix) to not complicate it even more and the bellow are examples of two collections within SCLo -- one that *is part of RHSCL* (mariadb55) and one that is only part of SCLo (mariadb55extra; could include packages that extend mariadb55 collection for example), which *is not part* of RHSCL. final tags (and repositories) for non-RHSCL collections (include also packages from rhscl repos bellow): sclo6-sclo-release sclo6-sclo-candidate sclo6-sclo-testing sclo7-sclo-release sclo7-sclo-candidate sclo7-sclo-testing final tags (and repositories) for RHSCL collections (separate in order to allow using the sclo- repositories together with RH's rhscl channel, the same as epel is used): sclo6-rhscl-release sclo6-rhscl-candidate sclo6-rhscl-testing sclo7-rhscl-release sclo7-rhscl-candidate sclo7-rhscl-testing build tags: sclo6-el6-mariadb55extra-sclo-build sclo7-el7-mariadb55extra-sclo-build sclo6-el6-mariadb55-rhscl-build sclo7-el7-mariadb55-rhscl-build (el6- and el7- part used for keeping the disttag in the name as agreed from the beginning for all SIGs -- that was mentioned as a requirement before already) build targets: sclo6-el6-mariadb55extra-sclo sclo7-el7-mariadb55extra-sclo sclo6-el6-mariadb55-rhscl sclo7-el7-mariadb55-rhscl git branches under sclo/ project: sclo6-mariadb55extra-sclo sclo7-mariadb55extra-sclo sclo6-mariadb55-rhscl sclo7-mariadb55-rhscl git branches under rpms/ project: sclo6-mariadb55extra-sclo sclo7-mariadb55extra-sclo sclo6-mariadb55-rhscl sclo7-mariadb55-rhscl Are we on the same page with the schema above? [1] http://www.centos.org/minutes/2015/april/centos-devel.2015-04-13-14.01.log.… Honza

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel April 2015