kernel-package: latest unstable version breaks linux-2.6 build on amd64

Automatically imported from Debian bug report #344740 http://bugs.debian.org/344740

Message-ID: <email address hidden>
Date: Sun, 25 Dec 2005 13:45:58 +0100
From: Frederik Schueler <email address hidden>
To: <email address hidden>
Subject: kernel-package: latest unstable version breaks linux-2.6 build on amd64

--eqp4TxRxnD4KrmFZ
Content-Type: multipart/mixed; boundary="+nBD6E3TurpgldQp"
Content-Disposition: inline

--+nBD6E3TurpgldQp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: kernel-package
Version: 10.024
Severity: grave

Hello,

The changes introduced in kernel-package between 10.020 and 10.023 break
the amd64 build in the linux-2.6 package, see attached build log.

This might be a problem with amd64/x86-64, having dpkg and the kernel
sources call the arch differently (If this is the case, sparc hppa and
powerpc might be afffected too).

If I just need to change something in the build defines ( setting kpkg-arch
to either amd64 or x86_64, like Svenl suggested on IRC, did not help) or
in the package build system itself, please give me some a hand to fix
it.=20

Best regards
Frederik Schueler

--=20
ENOSIG

--+nBD6E3TurpgldQp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="10.024.log"
Content-Transfer-Encoding: quoted-printable

dpkg-buildpackage: source package is linux-2.6
dpkg-buildpackage: source version is 2.6.14+2.6.15-rc7-0experimental.1
dpkg-buildpackage: host architecture amd64
 debian/rules clean
dh_testdir
rm -rf debian/build debian/stamps debian/lib/python/*.pyc debian/*.kpatches=
=2Earch
dh_clean
 debian/rules build
dh_testdir
/usr/bin/make -f debian/rules.gen setup-amd64
make[1]: Entering directory `/usr/src/debian-kernel/linux-2.6-2.6.14+2.6.15=
-rc7'
/usr/bin/make -f debian/rules.real setup-arch SOURCE_VERSION=3D'2.6.14+2.6.=
15-rc7-0experimental.1' VERSION=3D'2.6.15' SOURCE_UPSTREAM=3D'2.6.14+2.6.15=
-rc7' ABINAME=3D'rc7' KPKG_ABINAME=3D'' ARCH=3D'amd64' UPSTREAM_VERSION=3D'=
2.6.15-rc7' REVISIONS=3D'0experimental.1'
make[2]: Entering directory `/usr/src/debian-kernel/linux-2.6-2.6.14+2.6.15=
-rc7'
rm -rf 'debian/build/source'
mkdir -p 'debian/build/source'
cp -al COPYING CREDITS Documentation Kbuild MAINTAINERS Makefile README REP=
ORTING-BUGS arch block crypto drivers fs include init ipc kernel lib mm net=
 scripts security sound usr 'debian/build/source'
cd 'debian/build/source'; override_version=3D'2.6.14+2.6.15-rc7-0experiment=
al.1' override_revisions=3D'0experimental.1' home=3D'/usr/src/debian-kernel=
/linux-2.6-2.6.14+2.6.15-rc7/debian/patches-debian' sh '/usr/src/debian-ker=
nel/linux-2.6-2.6.14+2.6.15-rc7/debian/bin/apply'
W: No version.Debian file, assuming pristine Linux 2.6.14+2.6.15-rc7
fbdev-radeon-noaccel.patch OK (+)
fs-asfs-2.patch OK (+)
ia64-irq-affinity-upfix.patch OK (+)
modular-ide-pnp.patch OK (+)
powerpc-mkvmlinuz-support.patch OK (+)
powerpc-serial.patch OK (+)
sparc64-hme-lockup.patch OK (+)
version.patch OK (+)
m68k-bvme.patc...

Message-Id: <email address hidden>
Date: Sun, 25 Dec 2005 08:47:06 -0800
From: Manoj Srivastava <email address hidden>
To: <email address hidden>
Subject: Bug#344740: fixed in kernel-package 10.025

Source: kernel-package
Source-Version: 10.025

We believe that the bug you reported is fixed in the latest version of
kernel-package, which is due to be installed in the Debian FTP archive:

kernel-package_10.025.dsc
  to pool/main/k/kernel-package/kernel-package_10.025.dsc
kernel-package_10.025.tar.gz
  to pool/main/k/kernel-package/kernel-package_10.025.tar.gz
kernel-package_10.025_all.deb
  to pool/main/k/kernel-package/kernel-package_10.025_all.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Manoj Srivastava <email address hidden> (supplier of updated kernel-package package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sun, 25 Dec 2005 10:14:33 -0600
Source: kernel-package
Binary: kernel-package
Architecture: source all
Version: 10.025
Distribution: unstable
Urgency: low
Maintainer: Manoj Srivastava <email address hidden>
Changed-By: Manoj Srivastava <email address hidden>
Description:
 kernel-package - A utility for building Linux kernel related Debian packages.
Closes: 344413 344740
Changes:
 kernel-package (10.025) unstable; urgency=low
 .
   * Bug fix: "kernel-package: latest unstable version breaks linux-2.6
     build on amd64", thanks to Frederik Schueler. Now we let the
     architecture still be whatever DEB_HOST_ARCH_CPU says it should
     be. Just set KERNEL_ARCH correctly on amd64/x86_64 machines early, so
     that make-kpkg clean does not flake out when there is no ./debian dir.
     Accept either x86_64 or amd64 as the architecture, just in case, when
     selecting the correct Makefile snippet. So it is perfectly fine to
     still say --arch=amd64, like linux-2.6 does (Closes: #344740).
   * Bug fix: "[powerpc] k-p 10.00x breaks debconf based /etc/kernel/*.d
     scripts like mkvmlinuz", thanks to Sven Luther. Well. In the recent
     10.X series, kernel package has started producing image packages whose
     maintainer scripts use debconf for user interaction. Unfortunately,
     this meant that any hook scripts called in the maintainer scripts for
     the image package (update-grub comes to mind), if they wrote anything
     at all to the STDOUT, would cause debconf to throw hissy fits, since
     it was expecting commands on STDOUT, not random chatter from the hook
     scripts.
 .
     One solution was to call db_stop before calling the hook scripts, and
     redirecting stdout to stderr in hte invocation of the
     scripts. Unfortunately, this made any scripts that used debconf
     impossible.
 .
     So, ei...

blah