I have koji running great on a single server setup, and have gotten to
go ahead to start rolling it out/letting our dev's play with it. I
have a question, commands like "koji build dist-el5 SCMURL?pkgname#tip"
work fine on the koji server, but when I install the koji rpm say on my
laptop, I keep getting errors like:
koji build dist-el5 SCMURL?pkg#tip
Unable to log in, no authentication methods available
My user certs have not changed, and my $HOME is NFS roaming so it's the
same on the Koji Server and on the "dev" laptop, and the user SSL Certs
are in the same location.
I do not want to set this up to be a "builder" box that actually does
the builds, I want to install on a DEV laptop and have them be able to
call a koji build from there, rather than having to login to the koji
I took a look at the Howto's and this sort of config/setup doesn't seem
to be addressed or I just may be dense and missed it. I would
appreciate it if someone could point me in the right direction for this
sort of setup.
Dear open source contributors,
I am Eunyoung Chung, a Masters student working with Dr. Jensen at
Oregon State University.
We are currently doing a research project in collaboration with Dr.
Truong and Ph.D student Koji Yatani at University of Toronto. Our goal
is to understand how contributors communicate and collaborate in Open
Source Software (OSS) projects, including diagramming practices.
We are seeking volunteers for a quick survey on this topic. Any person
who is actively working on a OSS project is eligible. The survey takes
approximately 10-15 minutes, and the 5 volunteers will be picked to
receive a $30 Amazon gift certificate. Your participation is anonymous
(unless you consent to have us contact you)
Here is the survey address.
We really appreciate your help!
Useful to diagnose problems with %post scripts during the build. This patch
adds the method to the ImageCreator class, and the corresponding options to
image-creator and livecd-creator
Actually, quite a handy trick when my dodgy %post scripts mess up
during initial/anaconda installs.
martin(a)laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
The attached patchset adds the following functionality to pungi:
- building 'full' trees, that include all subpackages for any included
- building 'selfhosting' trees, that solve the package set for, and include,
any build dependencies
This is a rebase of some patches sent earlier this year.
bin/pungi.py | 23 ++++++++++
pypungi/__init__.py | 109 ++++++++++++++++++++++++++++++++++++++++++----------
2 files changed, 112 insertions(+), 20 deletions(-)