[Bug 377446] Re: building kernel 2.6.29 failure

[Arkadiusz Miśkiewicz]

apparmor is not ready in our kernel 2.6.29. Use --without apparmor as
workaround.

** Changed in: pld-linux
       Status: New => Confirmed

-- 
building kernel 2.6.29 failure
https://bugs.launchpad.net/bugs/377446
You received this bug notification because you are subscribed to PLD
Linux.

Status in PLD Linux Distribution: Confirmed

Bug description:
Hi,

Building kernel.spec with the following conditional flags:
 --with pae --without pcmcia --without reiser4

from available:
--with   :       fbcondecor imq myown nfsroot <pae> pax pax_full rescuecd tomoyo verbose
--without:       apparmor esfq grsec_full grsec_minimal grsecurity ipv6 <pcmcia> <reiser4> smp source tuxonice vserver wrr

Available branches: LINUX_2_6_28 LINUX_2_6_27 LINUX_2_6_26 LINUX_2_6_25 LINUX_2_6_24 LINUX_2_6_22 LINUX_2_6_21 LINUX_2_6_21_TH_1 hawk-LINUX_2_6 LINUX_2_6_19 LINUX_2_6_20 LINUX_2_6_18 LINUX_2_6_17 LINUX_2_6_16 AC-branch LINUX_2_6_15 LINUX_2_6_14 LINUX_2_6_13 mm LINUX_2_6_12 LINUX_2_6_11 aniolek LINUX_2_6_9 KERNEL_BRANCHES_INFORMATION LINUX_2_6_8 LINUX_2_6_7 LINUX_2_6_7-2 SAS_26 djurban-LINUX_2_6 LNX26_IX86_PAXGRSEC kernel-2_4_22-1_5 kernel-2_4_21-2_1 LINUX_2_6 KERNEL_2_4_for_RA kernel-2_4_20-6pl8 DEVEL LINUX_2_2 RA-branch LINUX_2_4_DZIMI_DEVEL kernel-2_4_17-2_5-mosix LINUX_2_2_DEVEL LINUX_2_4_STABLE K2_2_19pre LINUX_2_4
linux-2.6.29.tar.bz2 having proper md5sum already exists
patch-2.6.29.2.bz2 having proper md5sum already exists
ccs-patch-1.6.6-20090202.tar.gz having proper md5sum already exists
Wykonywanie(%prep):  env -i PATH=/bin:/usr/bin:/usr/sbin:/sbin:/usr/X11R6/bin HOME=/home/users/dirdival TMP=/home/users/dirdival/tmp TMPDIR=/home/users/dirdival/tmp SSH_AUTH_SOCK=/tmp/keyring-XNpn5D/socket.ssh  /bin/sh -e /home/users/dirdival/tmp/rpm-tmp.45177
Patch #69 (kernel-tuxonice.patch):
Patch #70 (kernel-tuxonice-headers.patch):
Patch #4 (kernel-fbcon-margins.patch):
Patch #10 (kernel-pom-ng-IPV4OPTSSTRIP.patch):
Patch #11 (kernel-pom-ng-ipv4options.patch):
Patch #14 (kernel-pom-ng-ROUTE.patch):
Patch #16 (kernel-pom-ng-mms-conntrack-nat.patch):
Patch #22 (kernel-pom-ng-rsh.patch):
Patch #23 (kernel-pom-ng-rpc.patch):
Patch #36 (kernel-nf_rtsp.patch):
Patch #37 (kernel-owner-xid.patch):
Patch #38 (kernel-ipt_account.patch):
Patch #39 (kernel-ipt_ACCOUNT.patch):
Patch #40 (kernel-layer7.patch):
Patch #41 (kernel-ipvs-nfct.patch):
Patch #49 (kernel-zph.patch):
Patch #53 (kernel-esfq.patch):
Patch #52 (kernel-wrr.patch):
Patch #54 (kernel-toshiba_acpi.patch):
Patch #55 (kernel-atm-vbr.patch):
Patch #56 (kernel-atmdd.patch):
Patch #58 (kernel-PF_RING.patch):
Patch #59 (kernel-rndis_host-wm5.patch):
Patch #85 (kernel-hostap.patch):
Patch #90 (kernel-mpt-fusion.patch):
Patch #100 (kernel-vserver-2.3.patch):
Patch #101 (kernel-vserver-fixes.patch):
Patch #130 (kernel-forcedeth-WON.patch):
Patch #140 (kernel-unionfs.patch):
Patch #141 (kernel-unionfs-apparmor.patch):
Patch #2500 (kernel-warnings.patch):
Patch #7001 (kernel-bzip2-lzma.patch):
Patch #9999 (kernel-grsec_full.patch):
Patch #10000 (kernel-grsec-caps.patch):
Patch #10001 (kernel-grsec-common.patch):
Patch #10002 (kernel-grsec_fixes.patch):
Patch #10003 (kernel-grsec-no-stupid-SbO.patch):
Patch #5001 (kernel-apparmor-after-grsec_full.patch):
10 out of 38 hunks FAILED -- saving rejects to file fs/namei.c.rej
1 out of 1 hunk FAILED -- saving rejects to file fs/stat.c.rej
1 out of 28 hunks FAILED -- saving rejects to file fs/xattr.c.rej
4 out of 18 hunks FAILED -- saving rejects to file include/linux/security.h.rej
1 out of 1 hunk FAILED -- saving rejects to file kernel/cgroup.c.rej
1 out of 1 hunk FAILED -- saving rejects to file net/unix/af_unix.c.rej
2 out of 2 hunks FAILED -- saving rejects to file security/commoncap.c.rej
2 out of 6 hunks FAILED -- saving rejects to file security/selinux/hooks.c.rej


Błędy budowania RPM-a:
[dirdival at pld ~]$ 

Regards,
Krzysztof