Your message dated Sun, 20 Nov 2011 18:09:13 +0000 with message-id <1321812553.2839.40.camel@deadeye> and subject line Re: Bug#649394: linux-source-2.6.32: can't build 2.6.32-5 using 2.6_2.6.32-34squeeze1 has caused the Debian Bug report #649394, regarding linux-source-2.6.32: can't build 2.6.32-5 using 2.6_2.6.32-34squeeze1 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 649394: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649394 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: linux-source-2.6.32 Version: 2.6.32-38 Severity: normal I'm running 2.6.32-5-xen-amd64 and I'd like to compile a new vmlinuz with enhanced errno reporting (distinguish between ENOMEM returns in fork.c). When I try to build 2.6.32-5, it applies all the patches through 34squeeze1 (and actually fails to do that as one of the later patches conflicts with my change). What I did: dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc /usr/src/kernel-patches/all/2.6.32/apply/debian 5 cd linux-2.6-2.6.32 vi kernel/fork.c fakeroot make -f debian/rules.gen binary-arch_amd64_xen What happened: (all the rest of the patches started to apply, and failed at version 14 where there was another edit to fork.c, so the build failed) What I expected: A build without all the rest of the patches being applied. Variant: in "What I did", I tried this also, and all the patches still got applied: dpkg-source -x linux-2.6_2.6.32-34squeeze1.dsc /usr/src/kernel-patches/all/2.6.32/apply/debian 5 cd linux-2.6-2.6.32 vi kernel/fork.c fakeroot make -f debian/rules.gen build_amd64_xen_amd64_real I looked in the makefiles, and noted that in debian/rules.real, the apply-patch command definition has no way to specify the patch-level: define patch_cmd cd '$(DIR)'; python '$(CURDIR)/debian/bin/patch.apply' --overwrite-home='$(CURDIR)/debian/patches' endef Maybe the $(ABINAME) could be used to produce a "patch-level" for this command? I'm not all that familiar with building Debian kernels from source, I'd be happy to learn the "right way" if I was doing it wrong. I was following instructions from http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage and supplemented it by reading the makefiles. bjb -- System Information: Debian Release: 6.0.3 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/8 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages linux-source-2.6.32 depends on: ii binutils 2.20.1-16 The GNU assembler, linker and bina ii bzip2 1.0.5-6 high-quality block-sorting file co Versions of packages linux-source-2.6.32 recommends: ii gcc 4:4.4.5-1 The GNU C compiler ii libc6-dev [libc-dev] 2.11.2-10 Embedded GNU C Library: Developmen ii make 3.81-8 An utility for Directing compilati Versions of packages linux-source-2.6.32 suggests: ii kernel-package 12.036+nmu1 A utility for building Linux kerne ii libncurses5-dev [ncurses- 5.7+20100313-5 developer's libraries and docs for pn libqt3-mt-dev <none> (no description available) -- no debconf information
--- End Message ---
--- Begin Message ---Not a bug. See <http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.3>. Ben. -- Ben Hutchings Usenet is essentially a HUGE group of people passing notes in class. - Rachel Kadel, `A Quick Guide to Newsgroup Etiquette'signature.asc
Description: This is a digitally signed message part
--- End Message ---