devel

devel@lists.centos.org

11 participants
4618 discussions

[PATCH 0/3] Mostly patches adding show_possible_srpms.sh
by Pat Riehecky 17 Jun '14

17 Jun '14

From: Pat Riehecky <riehecky(a)fnal.gov> I was looking for some automated tooling to determine what SRPMS can be generated by a given git repo. Since none was out there, I've tossed this together. Pat Riehecky (3): Minor updates to some doc, nothing of real interest Added script to show srpms contained within a given repo Added switches for setting branch to check, alas I've no idea how to do this return_disttag.sh | 3 +- show_possible_srpms.sh | 121 ++++++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 123 insertions(+), 1 deletions(-) create mode 100755 show_possible_srpms.sh

3 9

Atomic build for CentOS7qa tree
by Karanbir Singh 17 Jun '14

17 Jun '14

hi, Just wondering if anyone has had a stab at an rpm-ostree build + atomic host from the content hosted in centos7qa tree's. Will need to find docker, but that can come from EPEL7 ( or for now, step1, just an atomic host might be a good start ). - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 4

Branding and change requests : workflow
by Karanbir Singh 17 Jun '14

17 Jun '14

hi, There still seems to be some level of ambiguity as to how we are doing the change requests, rebuild requests and change requests so I wanted to get a short summary on the list and we can pickup details where needed. For anything that anyone sees that needs a change : file an issue report at bugs.centos.org; this is most important. Then see if you can also propose a patch. In order to propose a patch you need to run through a few steps( in this example assuming we want to patch httpd ): $ git clone https://git.centos.org/git/centos-git-common.git $ git clone https://git.centos.org/git/rpms/httpd.git $ cd httpd $ git branch -a $ git checkout c7 $ bash ../centos-git-common/get_sources.sh $ git rev-parse HEAD > `whoami`.start-point $ bash ../centos-git-common/rpm-tree-prep.sh At this point you should be good to make changes to SPECS/ SOURCES/ and BUILD/package-name ( note that the rpm-tree-prep.sh script will setup a __orig dir for you to build patches against. once you have the content ready, git commit the changes, in multiple commits, to have a complete, but as small as possible, change in one commit. Eg. if you are fixing 5 things, ideally end up with 5 commits. Also, if you are adding content, to replace something else that is going away, make sure you have the delete and addition in the same commit. Eg. replacing xulrunner-redhat-prefs.js with xulrunner-centos-prefs.js - add the git rm and git add into the same commit. Once you are happy with the state of play, go back to the root of the git repo, and : $ git format-patch $(cat `whoami`.start-point) this will leave behind files, one per commit that you made, in the format : NNNN-<commit summary>.patch : these are the files you need to attach to bugs.centos.org; these files contain your user metadata as well, and can then be applied as is. So you get credit for the changes, and we are able to replay exactly the change you had in mind. NOTES: CentOS patches added to the SPEC file should be named : <packagename>-CentOS-<change being made>.patch When added to the spec file, its a good practise to skip a few hundred spots on the patch list. Eg. if the spec has no patches, then start the CentOS patches at Patch1000 onward. If the spec already has patches, then skip a large number. This is just so we dont have ( or are less likely to have ) Patch number conflict with upstream changes in the life of CentOS-7 lets get patching, todays build is definitely on. -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

5 7

RHEL7 crashes on IBM Intellistation Power 285 (Power5+)
by Timo Schöler 17 Jun '14

17 Jun '14

Hi, as I'm messing around with upstream's installer, I see that it crashes on my Intelli: https://drive.google.com/file/d/0B6Xv-IAqdukmd3luaE5EODYwY2c/edit?usp=shari… The machine is in perfect condition, Fedora 20 (Heisenbug) runs like a charm. However, I don't even find detailed information on whether RHEL7 supports this hardware or not. Cheers, Timo

2 2

centos-logos package
by Jim Perrin 17 Jun '14

17 Jun '14

Right now within the centos-logos package, we have: Anaconda: - Theme from Tuomas - banners from Alain Backgrounds: - Backgrounds from Tuomas - Backgrounds from Alain - Backgrounds from Marcus At some point tomorrow KB will have the updated centos-logos package imported into git, so we'll all have a common base to work from. Until then, the src.rpm for the working package can be found at http://buildlogs.centos.org/c7.00.04/centos-logos/20140613160840/70.0.4-1.e… I'd like to see if we can align the blues used in Tuomas's anaconda theme and the blues used in Alain's anaconda banners so that the installer has a more unified feel to it. I'll leave it to the two of you to figure out how best to address that. I'd also like to get everyone's opinions on the 'default' desktop background. They're all quite good, including a rotating set that will vary throughout the day. Marcus, I'm reasonably certain I gave your two background submissions terrible names. Please tell me if you'd like them corrected to something a bit more appropriate. If anyone has other suggestions for the look and feel of the distro as it applies to the -logos package, now is the time to provide both voice and/or changes. Patches sound be submitted either to the mailing list, or attached to a ticket at bugs.centos.org -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

1 0

Nightly build cut offs
by Karanbir Singh 16 Jun '14

16 Jun '14

hi So going to cut off at 20:00 UTC nightly for the CentOS-7 build runs. Anything in there by then should be built and included. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

1 0

CentOS 7 Public QA Release Beginner's Question
by Bob Lightfoot 16 Jun '14

16 Jun '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/14/2014 08:00 AM, centos-devel-request(a)centos.org wrote: > Date: Fri, 13 Jun 2014 11:22:07 -0700 From: Jeff Sheltren > <jeff(a)tag1consulting.com> Subject: [CentOS-devel] CentOS 7 Public > QA Release To: "The CentOS developers mailing list." > <centos-devel(a)centos.org> Message-ID: > <CANcQTLpGzGE-cECueNTD80oseeXp8F18hR4O73V37mSsZ-XOCQ(a)mail.gmail.com> > > Content-Type: text/plain; charset="utf-8" > > We are happy to announce the immediate availability of the first > CentOS 7 QA Release. > > !!! This is a QA release only and not the final CentOS 7 release > !!! > > In the past, CentOS QA testing has been performed by a small group > of people within the CentOS community. We are happy that we are now > able to open this up to the wider community to get early feedback > and bug reports prior to the 7 release. > > CentOS 7 QA release is available for download at: > > http://buildlogs.centos.org/ > > We are first populating individual RPMs in their respective build > directories. Once we have a working base install tree, it will be > made available at the same URL. > > Please note the following: - This is NOT the final CentOS 7 > release. Packages, ISOs, and install media *will* change between > this release and the final 7 release. - The packages posted at the > above URL will likely be updated in-place before the final > release. - Things may be broken! Don't install this on your > production servers. Consider it a beta/preview release. - Help us > make the 7 release better by reporting bugs at > http://bugs.centos.org - This is not an officially supported > release. If you have questions, aren't sure if you've found a bug, > etc., please ask in #centos-devel on Freenode, or email the > centos-devel email list. - Packages in the QA release are *not* > GPG-signed. The final 7 release will contain GPG-signed packages as > usual. - Upgrading from the QA release to the final 7 release may > be possible, but it's not supported or documented in any way. > Expect that you will need to re-install when 7 final is released. > > We appreciate any and all bug reports at http://bugs.centos.org > (please also check upstream bugzilla.redhat.com and link to those > bugs when filing a new CentOS issue), and assistance with the > "Branding Hunt" (see > http://lists.centos.org/pipermail/centos-devel/2014-June/010411.html) > > > https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux… > > contains a list of known issues at the time of the upstream release. > > Currently, we only have RPM packages online, but will be bringing > installable media online as soon as we have it ready. > > Again, this is NOT a final release. It may harm nearby puppies, > kittens, or other (cute) animals and/or servers. This is our first > attempt at opening up CentOS to the wider community, so please bear > with us as we work through any issues that arise with the process. > As always, feedback is welcome on the email list or on IRC > (#centos-devel on Freenode). > > Thanks, and enjoy the release! -Jeff Sheltren on behalf of the > CentOS QA Team -------------- next part -------------- An HTML > attachment was scrubbed... URL: > http://lists.centos.org/pipermail/centos-devel/attachments/20140613/361ee8d… > Dear Devs: Looks like a great lot of work, so thanks for the effort. As a Fedora Testor I am puzzled somewhat though. Is there available reading material and such as how I would go about using these rpm with a qemu/kvm for testing without having the installer available yet? Obviously I can test the install media when it exists just like I do for Fedora, but using these trees of rpms is a new skill I am hoping to add. Don't want to bog anyone down with explaining it in detail, as I don't mind reading and teaching myself, just need pointed where to look. Sincerely, Bob Lightfoot, Fedora Project QA Team Member & Centos User -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTnD/wAAoJEKqgpLIhfz3X3R0IAI/VxHJCR6wVVW4WPRJ+79VC FiaLjEcbcRbZVRb7oX9v2XCj0H2dGaA8YxUKA8OA+HDHG+5/+4OMp9hFiLvukrYy oeXKJbExM6r1tWRL9SuDET3+OgKW0YKCV45oKrm8/zwkiw2lmiGuHAACZsxkkoRt o7+BzLowJ72zz0JUJ+PcV1Oe7eN1oLn4x8tnDpA6owSWUTYvJNAaE/UWU4hnaPZ7 IT5ci8vFDrUV3iLdVmrfrILoV6N9SnftZWtCv/9sSA2XTvLXGrII16ioraNILNCg v4SYpiUo+yT+iw9S/uguf9A8ydNndRolvhTUPJCea+plSWfsA9Qpj2vnViM3obI= =fhEN -----END PGP SIGNATURE-----

5 4

CentOS 7 (pre-release) tree available for testing
by Fabian Arrotin 16 Jun '14

16 Jun '14

Following our previous post, we are pleased to announced that the first (pre-release) CentOS 7rc tree is pushed. As a reminder, you can find it at the following location : http://buildlogs.centos.org/centos/7/os/x86_64-20140614/ If you want to use it, you need to use the boot.iso media (found under the images directory) , start a netinstall and point to the mentioned repository (or use the pxe vmlinuz/initrd.img files) We plan on also having a symbolic link called "latest", as we'll probably have a new tree on a daily basis (until we're happy and will have a final release) Some points to keep in mind : * Those packages aren't signed (as announced, and that will be fixed the final centos-release package) * There is no included yum config (but you can configure that and point to the above repository , and that will be fixed the final centos-release package ) * EFI should work, but not Secureboot Happy testing and don't forget to give us feedback ! (on the centos-devel list, or #centos-devel irc channel, and bugs found reported on http://bugs.centos.org) -- Fabian Arrotin gpg key: 56BEC54E | twitter: @arrfab

6 11

CentOS 7 Branding Hunt Patch for redhat-bookmarks
by Brian Stinson 14 Jun '14

14 Jun '14

Attached is a patch to the default bookmarks (used when building Firefox and others). I used the bookmarks present in CentOS 6. -- Brian Stinson bstinson(a)ksu.edu

2 1

[PATCH] handle detached HEAD in get_sources and more
by Mike McLean 13 Jun '14

13 Jun '14

This patch handles the detached HEAD case, by using git branch --contains HEAD to get the branch (or a list of possible branches). It also adds a option to specify the branch in case this logic fails. Also there is an option to override the base source url for downloading. While I was at it, I adjusted some checks so that the script will run even if the name of the checkout directory is not $packagename.

3 4

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