devel

devel@lists.centos.org

4 participants
4677 discussions

yum-security and CentOS-5 / 6
by Karanbir Singh 04 Oct '12

04 Oct '12

hi Guys, with a bit of time opening up, I've gone back to looking at the yum-security issue and how we can address it ( i.e: atleast get the basics working ). I plan on doing the work in multiple stages as : step1: get a basic set of metadata online so that people can detect if an update is tag'd security, bugfix or enhancement step2: get some more metadata added in, with bug id's and cve's into that metadata step3: get everything rolled out by default on all centos installs and look at how external projects like spacewalk/pulp etc consume this metadata At the moment, I'm only thinking about things and trying to scope out the work. However, there is one issue that might be a spanner in the works based on how we have mirror.centos.org setup. What we have right now only provides for the <version>.<release> rpmset and updates but only in relation to that specific tree (eg. /6.3/ is what /6/ maps to at the moment ). Yum-security metadata in this repo would then only be relevant to the rpms contained in /6.3/, whatever repo they might be in - however, someone running 6.0 or 6.1. when checking for updates is likely to miss interim updates that were security tag'd at some release level or the other. One way to work around this would be to have yum consider all interim package metadata between installed.rpm and latest-in-repo.rpm ( which would then mean that we would need the yum-security metadata to contain all info for everything ever released ; isnt a problem as such ). Or we setup a repo that has everything ever released. This in turn has some serious caveats. Storage on every mirror being a good problem to start with - however, in limited tests it looks like yum will work with redirect, so while we would need the metadata to contain all packages, the physical packages can still be handed out from vault.centos.org, but that redirect foo needs some level of smartness on the mirror end; trivial to implement when we control the mirror.centos.org network, however a very large part of the mirror services are offloaded to external mirrors - hundreds of them. Its super tricky getting smartness onto each and every one of their machines. Thoughts, concerns, ideas ? There is no 'work' thats been done at this point on the problem, so we can take pretty much any course of action that seems sane. I feel its important that if we are going to provide a mechanism that people will then in turn rely on to get patch requirements for their machines, we need to make sure we have 100% coverage. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc

5 10

Test OpenStack Essex builds for CentOS
by Karanbir Singh 03 Oct '12

03 Oct '12

hi, http://people.centos.org/z00dax/openstack/essex/ repo file: http://people.centos.org/z00dax/openstack/essex/CentOS-OpenStack-Essex-test… These should be considered as testing packages and are based on the upstream Open Stack preview 1 rpms set. These rpms are also signed with the CentOS-6-Testing key and not the regular distro key. The .el6.alt distag indicates they were built on the Alt.BuildSys and not the primary system.[1] https://access.redhat.com/knowledge/docs/Red_Hat_OpenStack_Preview/ is perhaps the best place to go for a quick start process. The only major difference is section 1.1 of the docs, that explain howto get the rhn repo setup should be replaced by just downloading the above mentioned .repo file into /etc/yum.repos.d/ It takes about 15 minutes to walk through and the end result is a functional open stack install. If anyone wants to offer up some basic template images to use, please do so. I have not tested to see how these rpms are going to work with/conflict with the EPEL hosted openstack. Some feedback on that would be appreciated as well. - KB [1]: Lots more details on that over the next few weeks. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 9

Centos Test times
by Madhurranjan Mohaan 21 Sep '12

21 Sep '12

Hi, We were discussing build and test times on the IRC and one suggestion was to get information around tests and how much time its taking . Attached is a script used to run the tests and the final csv in descending order that gives you the tests and the time taken . Most of the time is taken by the installs . I've also included the csv which has errors when I ran these tests. These were run on a Centos 6 VM. This experiment didn't seem to use the nearest mirror. So for the next run, added the local mirror and the results are in the csv - "sorted_test_times_3_descending.csv" Suggestions to make this better would be great as well . thanks, Mamu

2 1

Re: [CentOS-devel] Shipping an EPEL release
by Christoph Galuschka 14 Sep '12

14 Sep '12

> > hi guys, > > One bit of feedback at LinuxCon this year from people was that we should > ship epel with a lower barrier to entry. And I have mixed feelings about > that. But I wanted to know what everyone else thinks about : > > 1) Shipping epel-release in CentOS-Extras, so its installable, usable > out of the box. > > 2) Shipping epel-release in the distro itself, with the epel repos's > enabled=false. This is the option that most people seem to want, but I > am least keen on. > > 3) do nothing, leave things as they are. > > Ofcourse, if we do either (1) or (2) we would need to set some sort of a > baseline standard that allows other repo's to be included as well ( as + > if they meet the baseline standard ) > I add EPEL to all C6 installations because there is a certain set of packages which I need from that repo. But this is done by a script which sord of customizes the C6 installation to my needs. So basically I'm fine doing this by hand. Long story short: options 3 and 1 (in this order) get my vote. To be honest I never thought about other repos being part of CentOS by default. Christoph

1 0

Re: [CentOS-devel] Shipping an EPEL release
by κiζs飛ゞ揚 13 Sep '12

13 Sep '12

You have been unsubscribed from the CentOS-devel mailing list !!! Why should that be? How do I send mail to everyone? ------------------ Original ------------------ From: "David Hrbáč"<david-lists(a)hrbac.cz>; Date: Fri, Sep 14, 2012 00:20 AM To: "centos-devel"<centos-devel(a)centos.org>; Subject: Re: [CentOS-devel] Shipping an EPEL release Dne 13.9.2012 17:32, Karanbir Singh napsal(a): > 3) do nothing, leave things as they are. > My vote. DH _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org http://lists.centos.org/mailman/listinfo/centos-devel

1 0

Re: [CentOS-devel] Shipping an EPEL release
by κiζs飛ゞ揚 13 Sep '12

13 Sep '12

Who are you? publishers？ ------------------ Original ------------------ From: "Karanbir Singh"<mail-lists(a)karan.org>; Date: Thu, Sep 13, 2012 11:32 PM To: "The CentOS developers mailing list."<centos-devel(a)centos.org>; Subject: [CentOS-devel] Shipping an EPEL release hi guys, One bit of feedback at LinuxCon this year from people was that we should ship epel with a lower barrier to entry. And I have mixed feelings about that. But I wanted to know what everyone else thinks about : 1) Shipping epel-release in CentOS-Extras, so its installable, usable out of the box. 2) Shipping epel-release in the distro itself, with the epel repos's enabled=false. This is the option that most people seem to want, but I am least keen on. 3) do nothing, leave things as they are. Ofcourse, if we do either (1) or (2) we would need to set some sort of a baseline standard that allows other repo's to be included as well ( as + if they meet the baseline standard ) regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel(a)centos.org http://lists.centos.org/mailman/listinfo/centos-devel

1 0

Updating The CentOS Artwork Repository
by Alain Reguera Delgado 30 Aug '12

30 Aug '12

hi Guys, I already began to download a working copy of The CentOS Artwork Repository with the intention of committing up the changes I've been working on through these last 3 years and this way, put in place all the information you need to test, verify and validate the work. I'm using a slow commutated connection with an average speed of 5KB/s but things are going on. I think the new directory structure should be online to the end of this month, if everything goes as planned so far. The CentOS Artwork Repository has changed significantly from that version currently online to that one I pretend to share this month. The directory structure currently online suffered significant changes as to be completely replaced. A preview of the new directory structure I want to share is in the following file: http://wiki.centos.org/AlainRegueraDelgado?action=AttachFile&do=get&target=… I would like to know what do we do with the old directory structure currently available online (https://projects.centos.org/svn/artwork/)? Do we remove it completely in the sake of the new one, or do we preserve it in some other place (maybe under tags/)? ... Once all the information be online and ready to be used, my plan is to update the wiki page (http://wiki.centos.org/ArtWork) to introduce the changes and the steps you need to follow in order to test the new directory structure of The CentOS Artwork Repository. This info might probably answer some of the questions laying around. Best Regards, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

2 3

Image rendition fails when preparing the workstation?
by Alain Reguera Delgado 29 Aug '12

29 Aug '12

hi Guys, There was a problem with some old design models inside The CentOS Artwork Repository which prevented centos-art.sh script from rendering images at preparation process. The exact problem was given because of a wrong path inside those old design models, specifically when centos-art.sh script verified them. This problem was fixed and you should be able to render images right away, after updating your working copy of The CentOS Artwork Repository. Other changes were also committed. The exact changes can be found at: https://projects.centos.org/trac/artwork/timeline Best regards, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

1 0

CentOS 6.3 versions for upstart different between i386 and x86_64
by Greg Snyder 29 Aug '12

29 Aug '12

It looks like there are currently different versions on CentOS 6.3 for the upstart RPM between i386 and x86_64: http://mirror.centos.org/centos-6/6.3/os/i386/Packages/upstart-0.6.5-10.el6… http://mirror.centos.org/centos-6/6.3/os/x86_64/Packages/upstart-0.6.5-12.e… I'm not seeing any trouble as a result of this, but wanted to call it out. The current i386 RPM seems to be what CentOS 6.2 had. The upstream announcement http://rhn.redhat.com/errata/RHBA-2012-0863.html , from 2012-06-20, is for the upgrade from upstart-0.6.5-10.el6 to upstart-0.6.5-12 . Thanks, Greg

2 1

Testing The CentOS Artwork Repository
by Alain Reguera Delgado 27 Aug '12

27 Aug '12

hi Guys, The CentOS Artwork Repository has been updated and needs to be tested by The CentOS Community. To test The CentOS Artwork Repository, you need to: 1. Follow the steps described in the page http://wiki.centos.org/ArtWork to configure your workstation and your working copy. 2. Read the documentation at `trunk/Manuals/Tcar-ug/tcar-ug-xhtml/index.html' to get a background information about the production environment your working copy is and how you can make use of it. 3. Explore the directory structure and play with centos-art.sh script. Specifically with functionalities like render, help and locale. This functionalities are described in the documentation named before. The source code of these functionalities is also available at trunk/Scripts/Bash/Functions, in case you are interested to contribute. The present state (revision 880) of The CentOS Artwork Repository published at https://projects.centos.org/svn/artwork is still an ongoing work and needs much more attention. So, if you consider that something must be improved or isn't working as expected, please send an e-mail to centos-devel(a)centos.org describing what you've found. Likewise if you find your self in trouble performing any of the previous steps, send an e-mail to centos-devel(a)centos.org to find answers. Personally, I'm very interested about the community needs and wishes related to the creation of a consistent visual identity for The CentOS Project that can be refreshed/updated each time a new major release of The CentOS Distribution be published. Initially it may not be possible to satisfy everything immediately but knowing such information will help us to identify and give priority to those areas with higher demand and, this way, work on the routes that will help us to get there, where we want to be. Best regards, -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel