External RHEL build repo
by Michael Cronenworth
Is it possible to add a external build repo with RHEL 5 packages? I see
koji.fp.o has a special setup to allow this, which I tried and failed to
use. Is it possible to use my existing RHEL subscription to allow access
somehow?
Thanks,
Michael
13 years, 8 months
Proposal: move comps to fedorahosted git
by Bill Nottingham
I'd like to propose moving comps to fedorahosted git.
Why? Because CVS is a pain.
I can work on fixing the automated releng tasks that use comps.
What I'd like to know is if doing this at some point over the
next few weeks (say, post-Alpha) would be a problem for people.
If it is, we can push it off until after F13 ships.
Bill
13 years, 9 months
koji chain-build usage
by Doug Reiland
Sorry for the previous email, it got sent while editing
In koji-cli in handle_chain_build:
elif '://' in src:
# quick check that src might be a url
build_level.append(src)
elif '/' not in src and not src.endswith('.rpm') and
len(src.split('-')) >= 3:
# quick check that it looks like a N-V-R
build_level.append(src)
should it be:
elif '://' in src:
# quick check that src might be a url
build_level.append(src)
elif '/' not in src and src.endswith('.rpm') and
len(src.split('-')) >= 3:
# quick check that it looks like a N-V-R
build_level.append(src)
I attempted to koji chain-build a couple of srpms for testing, but
task is just sitting on "waitrepo".
Also, I noticed it doesn't upload srpms so what is the BKM? do you
import, then chain-build?
13 years, 9 months
buildcapacity - # of builders
by Doug Reiland
Does it make any sense of run more one builder on a system or do you just control via host.capacity in the database?
On every package build completion does it trigger a createrepo event?
Are my package builds serialized between createrepos?
Thanks
13 years, 9 months
koji chain-build usage
by Doug Reiland
I am wondering how to use koji cli with chain-build and srpms.
First, might this be a bug in koji-cli
In handle_chain_build:
13 years, 9 months
local koji server - packages repository
by Doug Reiland
I am seeing my builds fail where it knows to pull a previous rpm
locally because it has already built it.
For example, I built kernel.
Now I try to build zlib, and from mock's root.log:
xz-lzma-compat i686 4.999.9-0.2.beta.20091007git.fc12 build 15 k
DEBUG util.py:256: zlib i686 1.2.3-23.fc12
build 69 k
DEBUG util.py:256: Transaction Summary
DEBUG util.py:256:
================================================================================
DEBUG util.py:256: Install 102 Package(s)
DEBUG util.py:256: Upgrade 0 Package(s)
DEBUG util.py:256: Total download size: 78 M
DEBUG util.py:256:
http://localhost/koji/packages/kernel/2.6.31.5/127.fc12/i386/kernel-heade...:
[Errno 14] HTTP Error 403 :
http://localhost/koji/packages/kernel/2.6.31.5/127.fc12/i386/kernel-heade...
DEBUG util.py:256: Trying other mirror.
DEBUG util.py:256: Error Downloading Packages:
DEBUG util.py:256: kernel-headers-2.6.31.5-127.fc12.i386: failed to
retrieve kernel-headers-2.6.31.5-127.fc12.i386.rpm from build
DEBUG util.py:256: error was [Errno 14] HTTP Error 403 :
http://localhost/koji/packages/kernel/2.6.31.5/127.fc12/i386/kernel-heade...
DEBUG util.py:319: Child returncode was: 1
I am confused about where this is coming from and if koji serves those
web pages:
My directory is /mnt/koji
>From kojid/kojid.conf: pkgurl=http://localhost/koji/packages
>From /etc/httpd/conf.d/kojiweb.conf:
PythonOption KojiPackagesURL http://localhost/mnt/koji/packages
Any ideas?
13 years, 9 months
mock: chroot proc busy when unmounting
by Alan Franzoni
Hello, I'm experiencing a rather strange error with mock. This happens
almost every time, hence I'd like to find out what's happening.
Build host machine: Fedora 12, 64 bit
Build target: Centos 5 64 bit, using some additional repos in the
config, otherwise the config is the stock epel-5-x86_64.cfg
Mock version: 1.0.2
Running mock as root.
After building (either with success or without) I get this problem:
DEBUG: Executing command: umount -n
/var/lib/mock/rhel5-unstable-x86_64/root/proc
DEBUG: umount: /var/lib/mock/rhel5-unstable-x86_64/root/proc: device is
busy.
DEBUG: (In some cases useful info about processes that use
DEBUG: the device is found by lsof(8) or fuser(1))
I tried modifying mock's backend.py in order to run lsof before and
after running umount and grepping for proc, but without success - there
seems to be no open file there. I tried running orphanskill before
umounting, I tried sleeping before umount, but nothing changed.
While that error has no great impact, that one and some subsequent
(involving some failing chattr calls) really get my build logs messed up
and hard to crawl when something goes wrong.
Has anybody had similar issues? Can I provide you with any other useful
debugging data?
--
Alan Franzoni
contact me at public(a)[mysurname].eu
13 years, 9 months
workflow help
by Doug Reiland
I am trying to get my hands around koji.
I have setup a local koji server. I have followed examples on setting up tags/groups.
I have dist-f12 and dist-f12-build
I have linked dist-f12-build to external repos in mirrors.kernel.org.
- what does this do you me? I this just the place where any rpm needed to satisfy a build request get pulled from?
I regen-repo and everything I think is ok, so far.
For testing, I download the src rpm for bc.
I did koji import dist-f12 bc*src.rpm
via web interface, it looks ok.
Why does this show up as a build? The bc package shows up under builds. I guess a build is any rpm, src or binary correct?
How do I trigger a build of this rpm?
koji build dist-f12 bc*src*rpm - complains has it tries to do an import again.
Using --scratch option works or doesn't fail. but I don't know what that does.
How do I just say build everything under a tag, for example dist-f12?
Is there a I way to trigger this via web interface?
How does a user, via koji cli, checkout src package, make changes, checkin, build, ...?
Thanks!
Doug
13 years, 9 months
mock: chroot proc busy when unmounting
by Alan Franzoni
Sorry if any of you is getting duplicate messages, it seems I had sent
the previous one to an old list address. I'm recollecting the issue here.
----
Hello, I'm experiencing a rather strange error with mock. This happens
almost every time, hence I'd like to find out what's happening.
Build host machine: Fedora 12, 64 bit
Build target: Centos 5 64 bit, using some additional repos in the
config, otherwise the config is the stock epel-5-x86_64.cfg
Mock version: 1.0.2
Running mock as root.
After building (either with success or without) I get this problem:
DEBUG: Executing command: umount -n
/var/lib/mock/rhel5-unstable-x86_64/root/proc
DEBUG: umount: /var/lib/mock/rhel5-unstable-x86_64/root/proc: device is
busy.
DEBUG: (In some cases useful info about processes that use
DEBUG: the device is found by lsof(8) or fuser(1))
I tried modifying mock's backend.py in order to run lsof before and
after running umount and grepping for proc, but without success - there
seems to be no open file there. I tried running orphanskill before
umounting, I tried sleeping before umount, but nothing changed.
While that error has no great impact, that one and some subsequent
(involving some failing chattr calls) really get my build logs messed up
and hard to crawl when something goes wrong.
I tried catting /proc/mounts as well and I discovered this nested mount
under proc in the chroot:
none on /var/lib/mock/rhel5-unstable-x86_64/root/proc/sys/fs/binfmt_misc
type binfmt_misc (rw)
Adding it to umountCmds fixed my issue.
This doesn't seem to get mounted explicitly by mock, hence I think it's
something happening inside the chroot that triggers its mount? I'm not
really an expert in rhel/fedora internals, any clue?
--
Alan Franzoni
contact me at public(a)[mysurname].eu
13 years, 9 months
Re: local koji server - creating certificates
by Doug Reiland
>Could you show exactly what commands you're running?
>
>You should not be trying to make multiple certificates with the same
>common name. The CN is the default field used as the Koji "username",
>and must be unique per user, service, and build host. Sharing the same
>certificate (or different certs with the same CN) will not work.
I got past the problem. The documentation was misleading to me. I saw
the examples/scripts and looked at the index.txt there to get a feel
for what is really expected.
Also, a bit misleading is the /etc/koji-hub/hub.conf. The ProxyDNS has
to be an exact match for what is in index.txt.
I am now bring httpd, and services up, and login via web.
Thanks for your response!
13 years, 9 months
