devel March 2015

devel@lists.centos.org

63 participants
61 discussions

Start a nNew thread

(no subject)
by Rupesh Dubey 18 Mar '15

18 Mar '15

1 0

Storage SIG Meeting 13-March-2015 15:30 UTC
by Lalatendu Mohanty 18 Mar '15

18 Mar '15

Greetings All! Time for a Storage SIG meeting [1] ( We are following a bi-weekly schedule) . We will be meeting in #centos-devel on Freenode. Agenda: #info Topic: Action items from previous meeting #info Topic: Status Updates #info Subtopic: GlusterFS #info Subtopic: OpenAFS #info Subtopic: Ceph #info Subtopic: SCST #info Open Floor Thanks, Lala

2 4

CBS build tags and git branches names for SCL
by Honza Horak 17 Mar '15

17 Mar '15

I'm about to submit a couple of requests into bugs.c.o to create necessary infrastructure for collections from RHSCL-1.2 at least. But first I want to make sure about the tag and branches names. Currently we have some testing build tags: scl6-el6-mariadb100-build scl7-el7-mariadb100-build and branches in dist-git (in sclo project): scl-mariadb100-el6 scl-mariadb100-el7 And the SIG has codename 'sclo'.. So, it's kind of messy already in the beginning :) Thinking about keeping it simple and uniform, what about this way: Keep 'sclo' as SIG codename to indicate it's combination of SCL on openness :) CBS build tags in format like: sclo6-mariadb100-build sclo7-mariadb100-build and branches in dist-git (in both sclo and rpms projects): sclo6-mariadb100 sclo7-mariadb100 This mail is to check whether we're fine to go this way or if there are some limitations we need to follow. dist-git and CBS gurus, please, provide your PoV. Thanks! Honza

6 16

CentOS SCLo SIG sync-up meeting on #centos-devel (2015-03-18)
by Honza Horak 17 Mar '15

17 Mar '15

WG meeting will be at 16:00 UTC (12:00 EST, 17:00 Brno, 12:00 Boston, 1:00+1d Tokyo, 2:00+1d Brisbane) in #centos-devel on Freenode. = Topics = * temporary solution before authtag is ready as proposed at [1], based on the yesterday's hangout [2] * other workflow issues consulting [3] [1] http://lists.centos.org/pipermail/centos-devel/2015-March/013029.html [2] https://www.youtube.com/watch?v=unOKuq7r9lg [3] https://www.redhat.com/archives/sclorg/2015-March/msg00030.html Honza

1 0

What can SCLo SIG do without authtag
by Honza Horak 17 Mar '15

17 Mar '15

This is more or less a stream of my thoughts, as a respond to the yesterdays' CBS hangout [1] which was dedicated to git/cbs issues and design. I've been thinking what the things mentioned on the hangout mean for SCLo SIG, especially that the authtag thing (which implies working lookaside cache except other stuff if I'm not mistaken) is not ready yet, since it needs to be done rather properly than doing it twice (which seems correct). Thus, SIG-maintained lookaside cache under rpms/ won't work for some time still and we're not able to build already released RHSCL content ourselves (in the rpms/ project). So, what can we do even right now, without authtag working? Just to sum it up, what are our options right now: * git access under sclo/ project works for all SCLo SIG members * we can use Fedora's lookaside cache for creating SRPMs, since pretty much all the SCL packages are in the Fedora already * building RHSCL 1.2 packages from SRPM is not possible, since we'd block that NVR for future builds from SCM (we don't want to cause the duplicate NVR issue in koji). Thus, we need to use another disttag --> build into SCL future only as described at [2]? Anyway, if we had the packages ready in sclo/ witch tarballs in fedora only -- could someone from CentOS power men do the import into rpms/? If so, what about bootstraping in this case? Maybe we can come up with some cookbook for packages rebuilds, that would be parseable by a tool; that tool would create srpm from sclo/ project (specific hash may be given so we may build one package twice because to bootstrap) and import it and build within rpms/ project.. That should allow us to build RHSCL-1.2 packages without having commit rights in rpms/.. [1] https://www.youtube.com/watch?v=unOKuq7r9lg [2] https://www.redhat.com/archives/sclorg/2015-March/msg00030.html Honza

1 0

CBS Google Hangout 16-Mar-2015 14:00 UTC - SIG workflows!
by Brian Stinson 16 Mar '15

16 Mar '15

Hi All, For our 16-Mar meeting, I thought we could do our format a little differently. We will post a link to the Google Hangout to this thread once the details are finished. One thing I'd like us to talk through is the contribution process from New User to Released Components. SIGs: we would like for this discussion to be driven by your real-life processes so please bring questions, comments, suggestions Hope to see you all there! Brian -- Brian Stinson bstinson(a)ksu.edu | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk

12 15

No CentOS SCLo SIG meeting today by hhorak
by Honza Horak 16 Mar '15

16 Mar '15

Guys, I'm very sorry, especially for the late announcement, but I'm not able to hold today's SCLo SIG meeting.. Honza

2 2

docker 1.5 in virt7-testing
by Karanbir Singh 13 Mar '15

13 Mar '15

hi guys, docker 1.5 is now in virt7-testing repos, please test and feedback so we can move to release.. thanks lokesh! - KB -- 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

3 3

Anaconda CentOS 7 error points to Red Hat
by Gianluca Cecchi 12 Mar '15

12 Mar '15

Hello, I'm playing with a CentOS 7 iso (CentOS-7.0-1406-x86_64-DVD.iso) in Oracle VM, configuring the virtual machine as PVHVM. When starting a graphic installation the VM gets a blocking error (a text install completes ok instead). Apart from debugging the probable reason of graphic driver, taht I'll investigate later, I see that the anaconda error debug page contains: Report a bug to Red Hat Customer Portal that should be changed in my opinion. See: https://drive.google.com/file/d/0BwoPbcrMv8mvbTVEN3FYRWJ0dFh4WFVGeWs2ZjE1SF… Donna if already fixed in follwing ISOs. Gianluca

1 0

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel March 2015