devel

devel@lists.centos.org

4 participants
4677 discussions

[PATCH] Clean up temp src.rpm
by Pat Riehecky 11 Jun '14

11 Jun '14

From: Pat Riehecky <riehecky(a)fnal.gov> --- return_disttag.sh | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/return_disttag.sh b/return_disttag.sh index f7dc610..f850356 100755 --- a/return_disttag.sh +++ b/return_disttag.sh @@ -73,6 +73,9 @@ nvr1="${pkg%.src.rpm}" mydist="XXXjsdf9ur7qlkasdh4gygXXX" nvr2=$(rpm --define "dist $mydist" -q --specfile "SPECS/$packagename.spec" --qf '%{n}-%{v}-%{r}\n' 2>/dev/null | head -n 1) +# clean up SRPM, since it is only used for its name +rm -f ${nvr2} >/dev/null 2>&1 + #use our placeholder dist to split the nvr head=${nvr2%$mydist*} -- 1.7.1

3 5

[PATCH] Not all git.c.o repos have SOURCES dir
by Pat Riehecky 11 Jun '14

11 Jun '14

From: Pat Riehecky <riehecky(a)fnal.gov> I've found a few repos without a SOURCES directory. For example, kpatch source cannot be fetched without this patch. Pat Riehecky (1): Fixed so it works on kpatch golang-* get_sources.sh | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-)

2 4

Welcoming CERN Linux Distro team
by Karanbir Singh 11 Jun '14

11 Jun '14

Hi Everyone, We would like to welcome onboard the CERN Linux Distro team ( http://cern.ch/linux ) to the CentOS Core SIG. Thomas Oulevey and Jaroslaw 'Jarek' Polok are going to be bootstrapping the CentOS Community Buildsystem around Koji and helping run it going forward. The community buildsystem is going to be the central place for all source to binary builds used by all efforts other than CentOS Core ( for now ). The initial target is to get a test instance running in the coming weeks, and then work on the git.centos.org integration, with the aim of having the 'production' buildsys online soon. This is the build service that all SIG's and Core SIG builds will consume going forward ( with the exception of CentOS Linux, we have quite a bit of work to do before we can migrate that ). Communications on this effort will be on the centos-devel mailing list ( http://lists.centos.org/mailman/listinfo/centos-devel ) and on the #centos-devel irc channel on irc.freenode.net. Hardware resources for the effort have been identified, setup and access is being setup so things can start rolling fairly quickly. Mike McLean and Fabian Arrotin are going to be working with them. You can keep up with Jarek on his google+ page at https://plus.google.com/+JaroslawPolok/ and Thomas tweets at https://twitter.com/thomasnomas ; They both also contribute to the http://linux.web.cern.ch/linux/ blog. Please join me in welcoming Thomas and Jarek to the CentOS Project. - 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

6 5

Questions about the new git.centos.org repos
by Pat Riehecky 11 Jun '14

11 Jun '14

Now that there are repos up at git.centos.org, I was wondering if anyone had a python tool I could use to convert a repo back into a source RPM? Similarly, does anyone know how gitblit handles repo change notifications? I'd love to be notified of updates to some repos or their tags. A programmatic tool for gathering that information would work just as well... I'm not sure which would work better for my workflow. There's a fair chance at various intervals I'd be hitting the site somewhat hard, are there any instructions for mirroring all the parts necessary for package assembly? I'd rather beat up my local mirror than pick on the main page. Open to ideas, Pat -- Pat Riehecky Scientific Linux developer http://www.scientificlinux.org/

8 36

RHEL7 srpms
by Morten Stevens 10 Jun '14

10 Jun '14

Hi, I'm confused about this notice: http://ftp.redhat.com/redhat/linux/enterprise/7Server/en/os/README Current sources for Red Hat Enterprise Linux 7 have been moved to the following location: https://git.centos.org/project/rpms Does CentOS have a location to download all RHEL 7.x SRPMS directly without git? Best regards, Morten

7 6

RHEL 7 officially announced
by Timo Schöler 10 Jun '14

10 Jun '14

Great news. https://www.redhat.com/archives/rhelv5-announce/2014-June/msg00001.html Cheers, Timo

2 2

CentOS 7 Artwork
by Marcus Moeller 10 Jun '14

10 Jun '14

Hi all. Here is my proposal artwork for the upcoming CentOS 7 release. https://polybox.ethz.ch/public.php?service=files&t=b7bc0652a190725e39fe9558… https://polybox.ethz.ch/public.php?service=files&t=5b788217a30cb72953e64454… Greets Marcus

6 5

The CentOS Release Number Typography
by Alain Reguera Delgado 09 Jun '14

09 Jun '14

Hi, The CentOS Brand shown while CentOS 6 is booting up uses The CentOS Release Number on it. Could you please point out what is the typography used for the release number and, if possible, where it can be downloaded? Best Regards, al.

11 37

Re: [CentOS-devel] CentOS 7 and release numbering
by Philip Mather 08 Jun '14

08 Jun '14

Morning all, I have to concur with Trevor and Kay on a lot of points... > The more CentOS feels exactly like "RHEL - but without > support", the more people understand it and take stock. There's an inevitable amount of trepidation around any change in direction from a Community Project and the current changes for CentOS are pretty significant, it seems wise to keep a clear and distinct link between CentOS and RHEL to allay any such concerns. In any "What does this mean to us?" conversation it would be very soothing to be able to say something like "Well, we'll move from CentOS 6.$x to 7.$y and that will continue to maintain compatibility just as before but the community will also be doing $z as well etc...". > Seems better to work around issues with the RHEL versioning scheme than to & > If the SIGs need a versioning scheme for the layers on top of the base > o/s then the new naming scheme sounds good for those but the core o/s, I > believe, should stick with mirroring upstream release numbers. At $work we do actually use a %YYYY%MM postfix in our Spacewalk set-up to keep monthly snapshots and I think the idea in the abstract is a good one (although YYYYMM is specifically excluded from ISO8601 for clarity reasons). However we add the date ourselves "independently", is there any reason the SIGs couldn't use the -$TAG in the same way? Allowing the core to remain unambiguously equivalent. It might even allow different SIGs to try different formats/options, find the best and then transfer control of the -$TAG format back up-stream to the CentOS Project centrally if there's agreement and then around(?)-stream to RedHat themselves? It could save their support guys any confusion of the future RHEL9 with the truly legacy "Red Hat Linux 9", a point I vaguely remember someone mooting about 7. :^) -- Regards, Phil

1 0

brand hunting utility
by Kay Williams 05 Jun '14

05 Jun '14

I've written a small utility (brand-hunter.py) to help with tracking down branding issues. It does the following: * accepts a list of srpms to search (if no srpms are listed, all srpms are searched) * downloads the srpms from ftp.redhat.com (across all rhel7 srpm repos) * extracts srpm content, including any bz2 or gz tarfiles. * searches text files (in multiline mode) for the pattern '[Rh][Ee][Dd]\s?[Hh][Aa][Tt]' * searches for any binary files * writes a list of issues (by file and line) to an issues.txt file (per srpm) * writes a noissues.txt file listing any srpms for which no issues were found. If folks are interested, please let me know a location where I can make the utility available. I ran it across the first 100 srpms (by yum sort order) and found only 7 srpms with no issues: GreSQL-4.0-9.el7.src SOAPpy-0.11.6-17.el7.src akonadi-1.9.2-4.el7.src ant-antunit-1.2-10.el7.src aopalliance-1.0-8.el7.src apache-commons-exec-1.1-11.el7.src apache-parent-10-14.el7.src The other 93 files had a range of issues, the most common of which are - * Redhat.com email addresses in patch files or author lists * Red Hat copyright statements * Binary files (of any kind, right now the utility flags them all as potential issues) The utility can be made smarter, say to ignore srpms with only redhat email addresses or copyright statements. But exclusions like these would be want to be done on a case by case bases, I imagine. Kay

6 11

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