Currently we're doing a mass rebuild about every couple of releases,
ie. once a year.
Since Dennis Gilmore has written this rebuild script already, why
don't we run the script more or less continuously? Obviously we could
pace the builds so they happen for each package about once a month and
don't overload Koji.
Then we track packages that don't build, say, 3 times in a row, and
file FTBFS bugs for them and after that prioritize fixing them or kick
them out of the distro.
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
My name is Samuel Sieb. I live near Vancouver, Canada. I'm on IRC on moznet
and freenode with the nick "ssieb". I started programming around the time I
started high school, beginning with Assembler on an Apple II and working up to
higher level languages after that. :-) I've been using RedHat/Fedora since
RH5.1 and love the freedom and openness of Linux and the community around it.
I'm married and we have four boys, so my available time is somewhat limited
which has kept me from getting as involved as I would like.
I'm also one of the developers of the ChatZilla IRC client and as the current
maintainer of the package does not have time to keep it updated, I would like to
co-maintain it. However, he is not able to sponsor me and after reading the
wiki pages, I'm still not sure what the process would be for me to get involved
in this case. I'm familiar with building RPMs as I have done it many times for
creating and testing patches in various packages, but I haven't directly used
the Fedora build system. The documentations appears to be clear and useful
though. I have a FAS account and SSH key setup. I would appreciate if someone
would let me know what the next step should be or if there is any other
information you would like me to provide.
I'm trying to generate a custom spin with pungi *and* add a kickstart
file (and be able to use that). The custom spin works, I also can
add a kickstart file to the DVD (using growisofs), but I don't seem
to be able to access it.
I tried both of these boot options:
Using the first method, the installer stops with:
dracut Warming: Unable to process initqueue
Dropping to debug shell.
The second attempt continues a bit further (it starts services) and
finally stops with:
The following problem occurred on line 0 of the kickstart file:
Unable to open input kickstart file: Could not open/read file:///run/install/ks.cfg
Accessing a kickstart file via the network works, but I explicitly
want to create a DVD that does not need the network.
I think I ran out of options now...
Any suggestions are welcome.
-- Jos Vos <jos(a)xos.nl>
-- X/OS Experts in Open Systems BV | Phone: +31 20 6938364
-- Amsterdam, The Netherlands | Fax: +31 20 6948204
Some shorewall (firewall) operations depend on several modules moved to
Without the kernel-modules-extra package shorewall stops with errors like:
RTNETLINK answers: No such file or directory
leaving the system without network connectivity. Very fun for when upgrading a
network only device :) In my case at least sch_ingress and sch_sfq.
The functionality concerns traffic shaping and I think there are a lot of
traffic shape scripts depending of those modules out of there. At least google
So how to deal with that? From my POI, either make shorewall depending of the
kernel-modules-extra or move back some of the sch_* modules to the main kernel
package. Need to know in order to fill a bug report :)
# Fedora Quality Assurance Meeting
# Date: 2012-07-30
# Time: 15:00 UTC
# Location: #fedora-meeting on irc.freenode.net
Feels like just about time to have another meeting, with F18 Alpha
starting to impend. (Can you start to impend? Quick, someone call the
dictionary people). It's probably a good idea to discuss the status of
the new anaconda UI: if anyone from the anaconda team can come along for
that, it'd be a big help, thanks folks. If anyone has anything else to
discuss, please propose it or bring it up in open floor.
This is a reminder of the upcoming QA meeting. Please add any topic
suggestions to the meeting wiki page:
The current proposed agenda is included below.
== Proposed Agenda Topics ==
1. F18 preparation / newUI status
2. AutoQA update
3. Open floor
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
test-announce mailing list