On Saturday 03 May 2008 12:37:22 am Koji Build System wrote:
> Package: kernel-18.104.22.168-1.fc10
> Tag: dist-f10
> Status: failed
> Built by: jwilson
> ID: 47960
> Started: Sat, 03 May 2008 03:42:41 UTC
> Finished: Sat, 03 May 2008 04:20:53 UTC
> * Fri May 02 2008 Jarod Wilson <jwilson(a)redhat.com> 22.214.171.124-1
> - Linux 126.96.36.199
> - Drop patches merged in 188.8.131.52:
> * linux-2.6-netdev-tehuti-check-register-size.patch
>h * linux-2.6-selinux-ssinitialized-bugon.patch
> * bits of wireless patches
> * Thu May 01 2008 Dave Airlie <airlied(a)redhat.com> 2.6.25-14
> - fix radeon fast-user-switch oops + i915 breadcrumb oops
> * Wed Apr 30 2008 Chuck Ebbert <cebbert(a)redhat.com> 2.6.25-13
> - Fix drive detection on some Macbook models (#439398)
> - Fix oops in RAID code (#441765)
> kernel-184.108.40.206-1.fc10 (47960) failed on ppc4.fedora.phx.redhat.com
> (noarch), ppc4.fedora.phx.redhat.com (ppc): BuildrootError: error building
> package (arch ppc), mock exited with status 1 SRPMS:
> Failed tasks:
> Task 593871 on ppc4.fedora.phx.redhat.com
> Task Type: build (dist-f10, devel:kernel-2_6_25_1-1_fc10)
> Task 593873 on ppc4.fedora.phx.redhat.com
> Task Type: buildArch (kernel-220.127.116.11-1.fc10.src.rpm, ppc)
Anyone have any idea why the ppc build tanked like this? Will have to try a
mock build once I have my ppc box back up and running in the new office...
Passing this along for consideration.
-------- Forwarded Message --------
> From: James Westby <jw+debian(a)jameswestby.net>
> To: distributions(a)lists.freedesktop.org
> Subject: Apport
> Date: Fri, 02 May 2008 21:58:23 +0100
> Hi all,
> I just wanted to let you all know about a little package that we
> use in Ubuntu that may benefit other distributions. This package
> is called "apport".
> Apport is an automatic bug reporting tool. It does a number of things,
> the main one of which is to pop up on crashes of system programs.
> To do this it installs a kernel core pattern in
> /proc/sys/kernel/core_pattern that pipes core files to it (available
> since the .23 kernel I believe). This writes out a .crash file to
> /var/crash. The user is then notified with a notification icon and
> libnotify message that something has crashed. Clicking on the icon
> tells them what and offers to report a bug.
> For Ubuntu this opens a new bug in launchpad with all the information,
> and then opens the page in the users web browser for them to provide
> more details.
> It also hooks in to python failures somehow to provide the same service,
> and also has intergration with update-manager so that you can report a
> bug if a package installation/upgrade fails.
> Some people may be disturbed by the thought of the flood of bugs that
> would be generated. You're right, it does generate a lot of
> bug reports, but there are a few things that make it worthwhile.
> Firstly, it's only active for development releases, as it's easiest
> to fix the bugs then, and those users will generally be more equipped
> to provide the necessary information.
> Secondly, and this is what makes apport so great, it can detect
> duplicates by itself. It takes the core file, enters a chroot,
> and using some magic it "retraces" the bug report, using full symbol
> table information.
> This means that it can detect duplicates on it's own and mark them as
> such, and also that without the users having to have debugging symbols
> in their executable, or know what gdb is, provide full backtraces.
> In addition to this a package can provide an apport script that gathers
> information from a user's system before reporting the bugs. For instance
> Firefox can report all of the extensions that the user has installed.
> It is obviously currently quite specific to Ubuntu, however it is surely
> possible to make it work on other systems as well, and I'm sure Martin
> would be happy to merge patches that did that. You can find more details
> about the project at
> and the code at
> I think other distributions would do well to look at it, and even if you
> don't want to use it in your distribution there may be ideas that you
> want to take.
> Does anyone else already have a system like this? Are there any aspects
> that are covered by other tools used in your distro? Can anyone see
> anything that would make it even better?
> Distributions mailing list
I have a problem in compiling a kernel module
(outside the kernel) in F9 (rawhide). Perhaps someone could enlighten me.
[root@localhost toshiba_acpi]# ll
-rw-r--r-- 1 root root 145 29. Apr 17:49 Makefile
-rw-r--r-- 1 root root 19774 28. Apr 21:46 toshiba_acpi.c
[root@localhost toshiba_acpi]# make
make: F?r das Ziel ?default? ist nichts zu tun.
[root@localhost toshiba_acpi]# cat Makefile
obj-m := toshiba_acpi.o
KDIR := /lib/modules/$(shell uname -r)/build
PWD := $(shell pwd)
$(MAKE) -C $(KDIR) M=$(PWD) modules
Nothing happens. Has the Makefile to be changed for F9 or do I make a
stupid mistake ?