Pungi doesn't create usable media anymore with F17 + updates
by Jos Vos
Hi,
When using pungi on a F17 system with all updates applied, it seems
to work fine when I only use the F17 release repo in the config file,
but it creates useless media when I also include the F17 updates repo.
Then, when booting the DVD, it times out after a long time when spawning
the shell on tty2 and after selecting the keyboard it runs into a Python
exception.
Are these known problems and what can I do about it? My main goal is
to create media to install an up-to-date F17 from (only) DVD.
Otherwise I'll file a bug with all details
Thx,
--
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
11 years, 2 months
who uses mock's SCM plugin?
by Clark Williams
We're considering breaking mock's SCM plugin out into a sub-package
(mock-scm) so that we can pull in dependencies (git, cvs, svn, tar,
etc.) automagically. We don't do it currently because most folks don't
actually need an SCM to use mock, but it's a PITA when you actually do
want to use it and don't have all the dependent packages installed.
Would it be an incredible inconvenience for anyone to have the SCM
functionality migrate to a sub-package?
11 years, 3 months
RE: Koji "free" task
by Moray Henderson
> Last night I started a build task, got the "(this may be safely
> interrupted)..." message from build task 881, interrupted it, logged
> off and went home expecting the build to continue on the build server.
>
> Today I still have build task 881 listed as state "free" with no logs
> or output in the web UI, and no subtasks. The watch-logs and watch-
> task commands give me no output and the resubmit command says "only
> canceled or failed tasks may be resubmitted". What exactly is state
> "free" and is it possible to get that task to continue?
Never mind. Some clown had turned off kojid on the build server.
Moray.
"To err is human; to purr, feline."
11 years, 3 months
Koji "free" task
by Moray Henderson
Hi all
Last night I started a build task, got the "(this may be safely
interrupted)..." message from build task 881, interrupted it, logged off and
went home expecting the build to continue on the build server.
Today I still have build task 881 listed as state "free" with no logs or
output in the web UI, and no subtasks. The watch-logs and watch-task
commands give me no output and the resubmit command says "only canceled or
failed tasks may be resubmitted". What exactly is state "free" and is it
possible to get that task to continue?
Moray.
"To err is human; to purr, feline."
11 years, 3 months
old builders in koji
by Seth Vidal
We have a bunch of hosts in koji which WERE builders but aren't anymore or
in some cases don't exist anymore. I'd like to prune them out so when I
run:
koji list-hosts
they don't show up anymore.
1. How do I do this?
2. If I do this does something terrible happen?
thanks,
-sv
11 years, 3 months
koji and mock configs
by Seth Vidal
Where should I look to edit the default template for the mock config that
koji uses to run mock?
I need to set a value in the yum.conf section of the mock config file so
that syslog_device=/dev/null or syslog_device='' so that koji builds will
stop sending yum output to syslog.
Thanks,
-sv
11 years, 3 months
Pungi and anaconda interpret %packages differently
by Jos Vos
Hi,
I found out that pungi interprets %packages listed with a minus sign
(e.g. "-packagename") different from anaconda. Is this "by design"?
To be more precise:
When I specify a package in the kickstart file this way but other
packages in the list depend on it, the package is still installed
by anaconda (which is ok, I think). But pungi will always exclude
the package from the generated media, regardless the fact that
other packages depend on it.
It is not a big problem, I can just leave out all the minus-entries
in the pungi %packages list (it's not that much extra space), but a
consistent behavior would be nicer.
Any comments on this?
--
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
11 years, 3 months
Policy : delete permission ?
by Thomas Guthmann
Hi,
I would like to have confirmation that only admin can delete a NVR. I
read http://fedoraproject.org/wiki/Koji/Policies and it's not clearly
detailed except when you say "only admins may modify package lists".
Ideally I'd like my users to be able to untag and delete a faulty build
from a tag so I don't have to do it :) But obviously I don't want them
to be an admin.
Thomas
11 years, 3 months
