buildsys August 2008

buildsys@lists.fedoraproject.org

14 participants
8 discussions

Supporting EPEL Builds in Koji
by Mike Bonnet 05 Jan '09

05 Jan '09

Hi. I've written up a proposal for a way to support EPEL builds in Koji. It's not the only way we could do this, but I think it's doable with a reasonable amount of effort, and has the side-effect of greatly simplifying the Koji setup process for a lot of people (by removing the need to bootstrap/import an entire distro of packages into your private Koji instance). You can view the proposal here: http://fedoraproject.org/wiki/Koji/EPELSupport It's fairly detailed regarding the data model changes necessary, so if you're not familiar with the Koji codebase you can skip those parts. Questions and comments welcome. Thanks, Mike

6 13

Yum Static Repos
by Brian Schubert 22 Oct '08

22 Oct '08

Hello, Is kojira capable of creating static repos such as those at http://koji.fedoraproject.org/static-repos/ or is this achieved through some other means? Either way, would anyone be able to instruct me as to how it's done? Thanks, Brian Schubert Open System Solutions Rutgers University

4 5

koji-1.2.6
by Mike McLean 03 Sep '08

03 Sep '08

It's been a long time since we posted a fresh tarball, so I just tagged and posted 1.2.6. Following is a summary of changes since 1.2.5. A couple of them /may/ cause some slight upgrade issues. - kojid no longer sleeps after taking a task. This shouldn't be too much of a problem, but it is a behaviour change and may affect your load distribution. - pathinfo.taskrelpath. The upload path for task workfiles has changed to avoid creating over-large directories. This may cause older clients to report broken urls. Updated clients, of course, will report the correct ones. - unified boolean option parsing in kojihub. This is a bugfix, but may expose configuration errors. - ServerOffline fault. This is a new fault code, and older clients will not be able to interpret it. Howevever, in the case where the exception is intended to be used this should be no worse than previous behavior. (mostly) full change summary: • don't sleep after taking a task • pathinfo.taskrelpath • unified waitrepo logic • scm user_common flag • shorter waitrepo timeout • support building from git subdirs • robust sessions for kojid ∘ new config options: retry_interval, max_retries, offline_retry, offline_retry_interval • authtype option for koji cli • top level quiet option for koji cli • select config file section based on invocation name • larger blocksize for uploads • prune-signed-copies improvements • saner duplicate filtering in list-pkgs • expand group deps in generated comps • several new options for download-build • wait-repo cli command • advertise help --admin • support db password auth in kojihub • listTagged/listTaggedRPMS by owner • handle importing an srpm for an existing build • unified boolean option parsing in kojihub • alias system.multiCall as system.multicall • ServerOffline exception ∘ raised when db connect fails ∘ also ServerOffline hub config option • fix Source: line in spec • package koji-gc (in -utils) • changed default config location for koji-gc • gc: fix age calculation for untagged builds • option to provide a ts for get_rpm_header • set rpmbuild_timeout of 24hours in mock configs • more robust ClientSession connections ∘ better retries ∘ retries for anonymous sessions ∘ special treatement for ServerOffline case ∘ don't mask real exceptions • use _callMethod in ClientSession.multiCall • larger default blocksize in uploadWrapper • automatically refresh stale db connections • kojira: don't throw an exception if a tag is renamed or deleted • add new session options for kojira: ∘ retry_interval, max_retries, offline_retry, offline_retry_interval • kojiweb: ∘ handle exceptions gracefully ∘ allow rss feed to filter by package name (specified with package=) ∘ allow listTagged* and readTagged* to filter by package owner name (specified with owner=) ∘ allow the builds page in the web UI to filter by package ID (specified with packageID=) ∘ only send the session cookie over a secure connection (patch from Toshio Kuratomi, with modifications) ∘ remove the KojiWebURL config option (no longer necessary) ∘ sort rpm listing on the buildinfo page by arch and -debuginfo ∘ add links to the headers on the info pages ∘ put identification information into the title on the *info pages ∘ change the title format to put the important bits first (format suggested by Will Woods) ∘ put the task label into the taskinfo header ∘ move the task ID into the main table

3 2

bodhi abuse?
by Michael Schwendt 31 Aug '08

31 Aug '08

https://admin.fedoraproject.org/updates/phpMyAdmin-2.11.9-1.fc8 [and several other updates] +1 dcottle - 2008-08-30 08:09:35 +1 acottle - 2008-08-30 08:11:54 +1 auscity - 2008-08-30 08:21:14 https://admin.fedoraproject.org/accounts/user/view/auscity (David Cottle) https://admin.fedoraproject.org/accounts/user/view/dcottle (David Cottle, email in aus-city domain) https://admin.fedoraproject.org/accounts/user/view/acottle Same name and domain in email address. If this is an attempt at trying to "autopush" updates faster via positive karma, stop this, please.

5 5

building from git using custom koji install
by jesus rodriguez 12 Aug '08

12 Aug '08

We've installed koji (1.2.5) on F8 and successfully got the buildroots generating and scratch builds of src.rpms working. I'm trying to build packages from our git repo. I gave it the url to our repo: git://git.fedorahosted.org/git?spacewalk.git#HEAD But it complains about not having a spec file. Which makes sense as there is no spec file at the top of the tree. The spec file I want to build is actually located in the web directory. http://tinyurl.com/65hs7b I've tried several versions of the url with no luck. It seems that koji expects the scm repository house a single package which is not the case for us. Has anyone else run into a similar situation? Is there a way to specify the subdirectory to look in after doing the git clone? -- jesus m. rodriguez | jesusr(a)redhat.com sr. software engineer | irc: zeus red hat network | 919.754.4413 (w) rhce # 805008586930012 | 919.623.0080 (c) +-------------------------------------------+ | "Those who cannot learn from history | | are doomed to repeat it." | | -- George Santayana | +-------------------------------------------+

5 11

[PATCH] make authtype a config option
by Dennis Gilmore 12 Aug '08

12 Aug '08

the attached patch adds a config option that can be in a config file or on the command line forcing the use of one authentication type. it is useful if a hub supports more than one authentication type. or using different hubs that support different authentications methods. Ive tested with noauth, kerberos, and ssl. Dennis

2 1

Kojihub xmlrpc log spewage
by Doug Ledford 08 Aug '08

08 Aug '08

Can anyone tell me how to make the postgresql code in the xmlrpc engine not spew all over my httpd error log? In less than 1 week I have in excess of 500MB of stuff like this: Execute operation completed in 0.0001 seconds fetchall operation completed in 0.0000 seconds SELECT tag_id FROM group_config WHERE create_event > 4160 OR revoke_event > 4160 Execute operation completed in 0.0002 seconds fetchall operation completed in 0.0000 seconds SELECT user_id,authtype,expired,start_time,update_time,master,exclusive,callnum FROM sessions WHERE id = 7475 AND key = '3-GvtCW6UIMQ17LbWlnlJ' AND hostip = '172.31.0.1' FOR UPDATE Execute operation completed in 0.0004 seconds fetchone operation completed in 0.0001 seconds SELECT name,status,usertype FROM users WHERE id=3 Execute operation completed in 0.0002 seconds fetchone operation completed in 0.0000 seconds UPDATE sessions SET update_time=NOW() WHERE id = 7475 Execute operation completed in 0.0002 seconds UPDATE sessions SET callnum=158074 WHERE id = 7475 Execute operation completed in 0.0002 seconds SELECT id, name, perm_id, arches, locked FROM tag_config JOIN tag ON tag_config.tag_id = tag.id WHERE tag_config.active = TRUE AND tag.name = 'dist-F9-SCM-build' Execute operation completed in 0.0004 seconds fetchall operation completed in 0.0000 seconds SELECT user_id,authtype,expired,start_time,update_time,master,exclusive,callnum FROM sessions WHERE id = 7475 AND key = '3-GvtCW6UIMQ17LbWlnlJ' AND hostip = '172.31.0.1' FOR UPDATE Execute operation completed in 0.0004 seconds fetchone operation completed in 0.0001 seconds SELECT name,status,usertype FROM users WHERE id=3 Execute operation completed in 0.0002 seconds fetchone operation completed in 0.0000 seconds UPDATE sessions SET update_time=NOW() WHERE id = 7475 Execute operation completed in 0.0002 seconds UPDATE sessions SET callnum=158075 WHERE id = 7475 Execute operation completed in 0.0002 seconds SELECT id, name, perm_id, arches, locked FROM tag_config JOIN tag ON tag_config.tag_id = tag.id WHERE tag_config.active = TRUE AND tag.name = 'dist-F10-SCM-build' Execute operation completed in 0.0004 seconds fetchall operation completed in 0.0000 seconds -- Doug Ledford <dledford(a)redhat.com> GPG KeyID: CFBFF194 http://people.redhat.com/dledford Infiniband specific RPMs available at http://people.redhat.com/dledford/Infiniband

2 5

mock x86_64 running pungi i368
by Phil Meyer 04 Aug '08

04 Aug '08

I have tried to be careful to run as specified. I attempted to go back through the mailing list, but nothing quite like this jumped out ... 2.6.25.11-97.fc9.x86_64 mock-0.9.9-1.fc9.noarch.rpm commands attempted: # mock -r fedora-devel-i386 --init # mock -r fedora-devel-i386 --no-clean --install pungi # cp dev-9 /var/lib/mock/fedora-rawhide-i386/root/tmp # mock -r fedora-devel-i386 --chroot "/usr/bin/pungi -c /tmp/dev-9 --ver=F9 --flavor=FJ --nosource" Result: Pungi.ERROR: Got an error from /usr/lib/anaconda-runtime/buildinstall Pungi.ERROR: error: db4 error(22) from dbenv->open: Invalid argument error: cannot open Packages index using db3 - Invalid argument (22) error: cannot open Packages database in /var/lib/rpm Traceback (most recent call last): File "/usr/bin/repoquery", line 853, in <module> main(sys.argv) File "/usr/bin/repoquery", line 750, in main repoq.doConfigSetup(fn=opts.conffile, debuglevel=initnoise, init_plugins=opts.plugins) File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 134, in doConfigSetup errorlevel=errorlevel) File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 182, in _getConfig self._conf = config.readMainConfig(startupconf) File "/usr/lib/python2.5/site-packages/yum/config.py", line 732, in readMainConfig yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg) File "/usr/lib/python2.5/site-packages/yum/config.py", line 802, in _getsysver idx = ts.dbMatch('provides', distroverpkg) TypeError: rpmdb open failed error: db4 error(22) from dbenv->open: Invalid argument error: cannot open Packages index using db3 - Invalid argument (22) error: cannot open Packages database in /var/lib/rpm Traceback (most recent call last): File "/usr/bin/yumdownloader", line 277, in <module> util = YumDownloader() File "/usr/bin/yumdownloader", line 42, in __init__ self.main() File "/usr/bin/yumdownloader", line 51, in main opts = self.doUtilConfigSetup() File "/usr/share/yum-cli/utils.py", line 69, in doUtilConfigSetup errorlevel=opts.errorlevel) File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 182, in _getConfig self._conf = config.readMainConfig(startupconf) File "/usr/lib/python2.5/site-packages/yum/config.py", line 732, in readMainConfig yumvars['releasever'] = _getsysver(startupconf.installroot, startupconf.distroverpkg) File "/usr/lib/python2.5/site-packages/yum/config.py", line 802, in _getsysver idx = ts.dbMatch('provides', distroverpkg) TypeError: rpmdb open failed

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

buildsys August 2008