devel

devel@lists.centos.org

4 participants
4606 discussions

adding jenkins triggers from cbs build runs
by Karanbir Singh 19 May '15

19 May '15

hi, Is there anyway to add jenkins job triggers based on new package builds from cbs.centos.org ? I thought it might be just as simple as tracking the repomd.xml file under cbs.centos.org/repos/<intended repo>/os/repodata - but that file is redone every hour, regardless of new builds or not. is there another way to track these ? rather than having to write a koji plugin ? -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 4

CentOS SCLo SIG sync-up meeting on #centos-devel (2015-05-20) half hour earlier
by Honza Horak 19 May '15

19 May '15

Since I'm available only until 15:30 UTC, I tried to schedule the meeting a half hour earlier, hopefully it will work somehow.. SCLo SIG meeting will be at 14:30 UTC (10:30 EST, 16:30 Brno, 10:30 Boston, 11:30 Tokyo, 0:30+1d Brisbane) in #centos-devel on Freenode. = Topics = * sync-up on current status (centpkg) * how can we help with centpkg hacking? * how to rebuild maven30 and rh-java-common collections in CBS Honza

1 0

Patch for libreport
by Matej Habrnal 19 May '15

19 May '15

Hi, I've created a new patch for libreport on CentOS-7 which fixes the following bug: https://bugs.centos.org/view.php?id=8422 The patch adds workflow for reporting AVCs problems to bugs.centos.org I tested the AVC reporting on testing instance of bugs.centos.org. You can look at them on testing bugs.centos.org, their IDs are 8007 and 8008. Regards Matej ABRT team

1 0

[NFV SIG]Generate the first NFV SIG rpm?
by Gasparakis, Joseph 18 May '15

18 May '15

Hi all, It has been a while since our kick off meeting and without much activity, so I was feeling adventurous this morning and thought of giving a first try to deliver a DPDK rpm for the NFV SIG. Does this seem reasonable and if so where do I start? Thanks Joseph -- Joseph Gasparakis Software Engineer Network Platform Group Software Defined Networking Division

4 5

Release of CentOS-7 (alpha candidate) for AArch64 platforms
by Jim Perrin 11 May '15

11 May '15

We are pleased to announce the public alpha release of CentOS Linux 7 for AArch64 compatible hardware. This is the initial alpha release based on CentOS Linux 7 1503 ( Rebuilt from Red Hat Enterprise Linux 7.1 sources ), with architecture and modifications patching as necessary. Because this hardware is very new and support for it is still evolving, there is no expectation for kernel ABI compatibility. Additionally, until the alpha period ends both the OS repository and the Updates repository are subject to change. This release was built on an X-Gene system from Applied Micro. We are working to test against other platforms to ensure broad compatibility. ======== Download You can find the install tree and repositories at http://buildlogs.centos.org/centos/7/os/aarch64/ While the build is in alpha, we are not releasing full isos as you would traditionally find with the x86_64 builds. Please use the boot.iso which has been pre-configured for a network install, or pxe from a locally hosted mirror of the installation tree. We plan to make disk images available soon to help vendors bootstrap their platforms. ============ Installation Installation guides and documentation will be provided via the CentOS wiki, at http://wiki.centos.org/SpecialInterestGroup/AltArch/AArch64 Because several packages are not yet available, the group information has been reduced and the only available installation option is 'minimal'. If you perform kickstart based installs, please note the only available group is currently 'Core'. We will improve upon this throughout the alpha process. ============ Contributing The AArch64 effort is meant to be a community effort as part of the AltArch SIG (http://wiki.centos.org/SpecialInterestGroup/AltArch) and we welcome enthusiasts and vendors to contribute patches, fixes, documentation, etc. In the AArch64 Extras repository, we have provided the mock package and dependencies so that community members can more easily contribute, as well as testing their own builds locally. Please submit patches, fixes, etc to the Arm-Dev list (http://lists.centos.org/mailman/listinfo/arm-dev) for discussion and acceptance. We encourage vendors to come and join this effort, we have a lose organization focused on the alternative architectures build process and welcome interaction at the group level. Please get in touch with me (jperrin(a)centos.org) or K Singh ( kbsingh(a)centos.org ) to find out more details. The wider CentOS Ecosystem is also welcome to engage with us, both at the project and code level. If you are working with a project that interfaces, manages or develops on top of CentOS, specially in the virtualization, cloud, container and infrastructure management areas - we would love to have you guys get involved. While we don't have a lot of resources, we are working with a few vendors to build up a community resource pool that we would encourage other projects to share their development, testing and delivery around CentOS Linux for aarch64. In the next few days, we'll be adding a branch to git for modified packages so that patches are available to the community, as well as providing a repository for the debug-info packages. ================================== Coming Soon // Future Improvements * Rebase to 4.1rc kernel * Improve package and group availability * Add additional hardware support * Disk images to support install via dd -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

1 0

[SIG Hardening] hardening classes
by Tim 11 May '15

11 May '15

Hi all, I know this SIG is still founding, but I like to discuss classes of hardening. I imagine security assessment classes (SAC) like: SAC1: low SAC2: middle SAC3: high SAC4: very high Every selective measure (e.g. disabling user list) could be put into these classes where every class depends on the underlying one (2 on 1, 3 on 2, etc.) What's your opinion? Regards Tim

6 13

Proposal to cancel the CBS meeting scheduled for 11-May-2015
by Brian Stinson 10 May '15

10 May '15

Hi Folks, Since there's not anything that needs urgent discussion, and since I'll be travelling for much of the day on Monday I propose we cancel this week's CBS/Infra meeting. If there are topics that need action, please reply here and we can handle them on-list. Hope you're all having a great weekend! Brian -- Brian Stinson brian(a)bstinson.com | IRC: bstinson | Bitbucket/Twitter: bstinsonmhk

2 1

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

Fwd: [Cloud SIG] BOF/Meetup space at Summit?
by Rich Bowen 08 May '15

08 May '15

FYI, the RDO project has been assigned a slot for our BoF session. It will be Thursday, 9:50am - 10:30am, and is listed in the schedule at https://www.openstack.org/summit/vancouver-2015/schedule/ Note that this is during regular conference sessions, so be sure to check that time period on the schedule, and try to make it to this event if at all possible. The agenda for the event is at https://etherpad.openstack.org/p/RDO_Vancouver and includes discussion of our participation in the CentOS Cloud SIG. Thanks! -------- Forwarded Message -------- ... May 7, 10:17 Hi Rich, Thanks! Your BoF session will be on Thursday from 9:50am - 10:30am in East Building, Room 10. This session will be added to the official schedule in the next couple of days.

3 2

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

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