buildsys December 2012

buildsys@lists.fedoraproject.org

10 participants
5 discussions

Koji-1.7.1-1.fc17 repository toplink failure
by Anthony Joseph Messina 03 Jul '13

03 Jul '13

After upgrading to koji-1.7.1 on my private hub and builders, my builders are no longer able to use the repositories they create when building subsequent dependent packages. When attempting to install locally built packages, the following error is issued in the root.log: error was [Errno 2] Local file does not exist: /tmp/koji/tasks/9129/19129/repo_3627_premerge/toplink/packages/... The repos are created successfully: $ /usr/bin/createrepo -vd -o /tmp/koji/tasks/9129/19129/repo -i /mnt/koji/repos/f17-build/3627/x86_64/pkglist -g /mnt/koji/repos/f17- build/3627/groups/comps.xml --update --skip-stat /mnt/koji/repos/f17- build/3627/x86_64 Scanning old repo data Spawning worker 0 with 36 pkgs Worker 0: reading toplink/packages/dahdi-tools/2.6.1/3.fc17.1/x86_64/dahdi- tools-2.6.1-3.fc17.1.x86_64.rpm Worker 0: reading toplink/packages/dahdi-tools/2.6.1/3.fc17.1/x86_64/dahdi- tools-devel-2.6.1-3.fc17.1.x86_64.rpm Worker 0: reading toplink/packages/dahdi-tools/2.6.1/3.fc17.1/x86_64/dahdi- tools-libs-2.6.1-3.fc17.1.x86_64.rpm ... ... I believe the issue is related to the following commit: https://fedorahosted.org/koji/changeset/da6dd0b1832e9929565a1ab03ab844aaced… I'm not sure why when building packages, the builders are inserting '/tmp/koji/tasks/9129/19129/repo_3627_premerge/toplink' instead of topdir or topurl, such as '/mnt/koji' or 'http://example.com/kojifiles' Right now I'm working on selectively reverting that commit to see if I can build packages against other local packages. Any assistance is appreciated. Thanks. -Anthony -- Anthony - http://messinet.com - http://messinet.com/~amessina/gallery 8F89 5E72 8DF0 BCF0 10BE 9967 92DC 35DC B001 4A4E

4 13

[PATCH] Filter the comps file we write on our media based on the package set. (#878985)
by Bill Nottingham 30 Dec '12

30 Dec '12

Only include groups that are specified in the kickstart. Remove any environments that use groups not on the media. --- src/pypungi/__init__.py | 23 +++++++++++++++++++++-- 1 file changed, 21 insertions(+), 2 deletions(-) diff --git a/src/pypungi/__init__.py b/src/pypungi/__init__.py index 45689c5..9eb24d0 100644 --- a/src/pypungi/__init__.py +++ b/src/pypungi/__init__.py @@ -724,10 +724,29 @@ class Pungi(pypungi.PungiBase): ourcompspath = os.path.join(self.workdir, '%s-%s-comps.xml' % (self.config.get('pungi', 'name'), self.config.get('pungi', 'version'))) - ourcomps = open(ourcompspath, 'w') + # Filter out things we don't include + ourgroups = [] + for item in self.ksparser.handler.packages.groupList: + g = self.ayum.comps.return_group(item.name) + if g: + ourgroups.append(g.groupid) + allgroups = [g.groupid for g in self.ayum.comps.get_groups()] + for group in allgroups: + if group not in ourgroups: + self.logger.info('Removing extra group %s from comps file' % (group,)) + del self.ayum.comps._groups[group] + + groups = [g.groupid for g in self.ayum.comps.get_groups()] + envs = self.ayum.comps.get_environments() + for env in envs: + for group in env.groups: + if group not in groups: + self.logger.info('Removing incomplete environment %s from comps file' % (env,)) + del self.ayum.comps._environments[env.environmentid] + break + ourcomps = open(ourcompspath, 'w') ourcomps.write(self.ayum.comps.xml()) - ourcomps.close() # Disable this until https://bugzilla.redhat.com/show_bug.cgi?id=442097 is fixed. -- 1.8.0.1

4 5

F18 Pungi error: "could not find anaconda lang-table, exiting"
by Philip Rhoades 12 Dec '12

12 Dec '12

People, While trying to build rawhide with the attached kickstart file and: pungi -c system_config_kickstart.ks --nosource --force --ver=F18 --all-stages I get this error. It appears that this was a problem with F15/16 as well? I want to build a minimal F18 install CD (ie NOT a Live CD). Am I missing something? Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: phil(a)pricom.com.au

1 0

T-shooting Tips for a Failing Mock-init (code: QWERTY)
by Tweeks 06 Dec '12

06 Dec '12

Hey all, I probably banged my head with some of your in the #koji channel a couple of weeks ago on this.. but I never got it figured out. My work group was trying to set up a CI/CD Jenkings test & build server using Jenkins + Koji (all on one box) and ran into some probelms. Besides the documentation not exactly being well suited for SSL auth configs, we found that we could get everything working except the actual mock portion. The mock chroot seems to get mostly set up (packages installed by kojibuilder/kojid), but when the system tried to do the mock-init, it fails every time. We even tried following the #koji guys' suggestions of invoking mock manually from the command line like this: ============= # su - kojibuilder -bash-3.2$ mock -r koji/dist-c5-build-6-10 --init INFO: mock.py version 1.0.28 starting... State Changed: init plugins INFO: selinux enabled WARNING: selinux: 'yum' does not support '--setopt' option State Changed: start State Changed: lock buildroot State Changed: clean INFO: chroot (/var/lib/mock/dist-c5-build-6-10) unlocked and deleted State Changed: unlock buildroot State Changed: init State Changed: lock buildroot Mock Version: 1.0.28 INFO: Mock Version: 1.0.28 INFO: calling preinit hooks State Changed: running yum State Changed: unlock buildroot INFO: Installed packages: fd = None <--------- fd = 8 <-------- I added these to puython for t-shooting... fd = 10 <--------- Traceback (most recent call last): File "/usr/sbin/mock", line 866, in ? main(retParams) File "/usr/sbin/mock", line 738, in main chroot.init() File "<peak.util.decorators.rewrap wrapping mockbuild.backend.init at 0x012C89B0>", line 3, in init File "/usr/lib/python2.4/site-packages/mockbuild/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.4/site-packages/mockbuild/backend.py", line 258, in init self._show_installed_packages() File "/usr/lib/python2.4/site-packages/mockbuild/backend.py", line 553, in _show_installed_packages gid=self.chrootgid, File "/usr/lib/python2.4/site-packages/mockbuild/backend.py", line 489, in doChroot printOutput=printOutput, *args, **kargs) File "<peak.util.decorators.rewrap wrapping mockbuild.util.do at 0x0128A758>", line 3, in do File "/usr/lib/python2.4/site-packages/mockbuild/trace_decorator.py", line 70, in trace result = func(*args, **kw) File "/usr/lib/python2.4/site-packages/mockbuild/util.py", line 317, in do preexec_fn = preexec, File "/usr/lib64/python2.4/subprocess.py", line 550, in __init__ errread, errwrite) File "/usr/lib64/python2.4/subprocess.py", line 999, in _execute_child raise child_exception OSError: [Errno 2] No such file or directory ^^^^^^^^^^^^^^^ Anyone have some good t-shooting tips? BTW.. I'm just trying to build a RHEL zsh src RPM here. nothing fancy. Our system is CentOS 5.8 (a requirement), koji-1.7. Tweeks

2 3

koji-1.7.1
by Mike McLean 04 Dec '12

04 Dec '12

Koji 1.7.1 is tagged and posted. * Mon Nov 19 2012 Mike McLean <mikem at redhat.com> - 1.7.1-1 - improved upload mechanism - koji-shadow enhancements - handle multiple topurl values in kojid - fix form handling - mount all of /dev for image tasks - avoid error messages on canceled/reassigned tasks - handle unauthenticated case in moshimoshi - fix the tag_updates query in tag_changed_since_event - stop tracking deleted repos in kojira - don't die on malformed tasks - fix bugs in our relpath backport - avoid baseurl option in createrepo - message bus plugin: use timeout and heartbeat - add maven and win to the supported cli search types - remove latest-by-tag command - fix noreplace setting for web.conf - add sanity checks to regen-repo command - debuginfo and source options for regen-repo command - make taginfo command compatible with older koji servers A few entries deserve further explanation: 1) improved upload mechanism The new upload mechanism avoids the overhead of xmlrpc and base64 encoding. Depending on other factors this can make for a tremendous speed improvement. It also reduces cpu load on the hub. The boolean use_fast_upload config option for the cli and kojid controls whether the new mechanism is used. This defaults to True for kojid (which is assumed to be talking to a matching kojihub) and False for the cli (which might be talking to an older hub). 2) handle multiple topurl values in kojid You can now provide multiple topurl values in kojid.conf, e.g. topurl=http://hub.example.com/kojifiles http://hub2.example.com/kojifiles If you do, then kojid will generate multiple baseurls for the mock config files it generates. We do not (yet) do anything else with the extra topurl values. For other places where we use topurl, only the first matters.

2 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

buildsys December 2012