This question is addressed at those with kernel building experience.
The Fedora wiki has instructions on building a custom kernel:
That's good, thanks.
Let's say that someone would like to build a kernel with different
configuration options. He or she has created a new .config file. The
relevant instructions are under the heading "Configure Kernel
Options". Instruction 6 says the following:
"Copy the config file to ~/rpmbuild/SOURCES/:
cp .config ~/rpmbuild/SOURCES/config-$arch"
The line above appears incorrect. This was recognized by another wiki
editor as can be seen in the following sentences:
"In actual fact, a Fedora 11 x86_64 machine would use the following
command, because the spec file has no config-x86_64 item, and so will
not process it. The only spec entry is for generic.
cp .config ~/rpmbuild/SOURCES/config-$arch-generic"
My question is this: what should be the name of the configuration file
for Intel 32 bits architecture?
one of the above followed by "-generic"?
PostgreSQL 9 was released
Are there any chances to get this for F14? The new version supports
basic replication scenarios, so I would not have to use PgPool :)
Compiled code for minimum(), maximum(), etc. suffers from a compiler bug:
https://bugzilla.redhat.com/show_bug.cgi?id=634757 -O1 wrong-code by cmove
Unfortunately this bug can corrupt user data silently.
I have hit the bug three times myself (bz 635508, 637303, 637461)
and consider myself lucky that the bad effects were evident and ignorable.
A fix is in testing, and a critical path update has been approved:
IMNSHO this will require a mass rebuild of all architecture-specific
Meanwhile, do not use Fedora 14 Beta on data that you value (e-mail,
documents, database, etc.) It really is that dangerous.
I would like to exchange review requests - someone may pick up each of
these three easy-to-review Erlang-related applications, and I will
finish your stalled review request. One mine package for one yours -
that's quite fair deal!
Here is the list of my packages for trade:
* https://bugzilla.redhat.com/632190 - erlang-amf - Erlang Action
Message Format Library
* https://bugzilla.redhat.com/632189 - erlang-misultin - Erlang
library for building fast lightweight HTTP(S) servers
* https://bugzilla.redhat.com/632186 - erlang-log4erl - A logger for
erlang in the spirit of Log4J
With best regards, Peter Lemenkov.
It's time to summarize F-14 Beta RC validation tests. Apologies for the
absence of some RC3 install testing, but I'm glad to see that it went on
smoothly, so special thanks for the ones who helped executing the cases.
Though Beta has been declared gold based on the Beta release
criterion, the summary of it is still helpful to make the issues
clear for the final release candidates cycle.
************************* Installation *******************************
623956 NEW - VESA driver fails in qemu/kvm machines, system hangs at X
635821 NEW - Attempting to submit (scp or bugzilla) an exception report
fails if networking not active
627789 MODIFIED - Error setting up repository - 16, Device busy
585006 NEW - livecd-creator creates i386 and x86_64 ISOs which are
larger than indicated by the ISO header
633815 NEW - Network installation fails when IPv4 DHCP fails/ IPv6
635873 MODIFIED - ImportError: No module named product
635887 MODIFIED - TypeError: getDiskPart() takes exactly 1 argument (2
************************** Desktop ***********************************
624136 NEW - [abrt] evolution-2.31.5-2.fc14: e_import_cancel:
Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
625367 NEW - SELinux is preventing /usr/libexec/kde4/kdm_greet "write"
access on /usr/libexec/kde4/lnusertemp
636118 NEW - Swell Foop fails to run in F14 Beta RC3 Desktop live
542255 ASSIGNED - [abrt] crash detected in gmixer-1.3-11.fc12
635897 NEW - SELinux is preventing /usr/sbin/lxdm-binary "execute"
access on xauth.
636229 NEW - Wrong defaults for actions on pressing power, suspend and
636380 NEW - Boot Failure from Live CD Desktop (F14B RC3) Can't mount
636104 NEW - [abrt] nautilus-2.31.92-1.fc14:
g_type_check_instance_cast: Process /usr/bin/nautilus was killed by
signal 11 (SIGSEGV)
635895 MODIFIED - SELinux is
preventing /lib64/dbus-1/dbus-daemon-launch-helper "execute" access
For testing details, please visit:
If your bug is not listed, feel free to discuss it in the list, and next
time please share your results on the result pages.
FAS Name: Rhe
IRC nick: rhe #fedora-qa #fedora-zh
test-announce mailing list
A bug was filed against meshlab because of an FTBFS for Fedora 14. I
added a patch to resolve it and submitted an update. After seven days
with no feedback, I was able to push it to stable.
For an FTBFS for a new Fedora release, does it really make sense to have
the seven day delay? I don't see what the downside would be of allowing
it to be pushed to stable immediately. Even if there's something wrong
with the update, it isn't going to replace a working package.