Hi!

Attached is the patch for the nmu to 2.6-1.2 which hopefully fixet is the 
correct way.

/Sune
-- 
Man, do you know how to cancel the kernel from Office?

From the control drawer menu inside MkLinuxPPC NT you should save a mail to 
the CPU to a ethernet board over the GPU, this way you neither can load the 
modem, nor can ever telnet to a BIOS of a laser ISDN microprocessor, so that 
from Outlook Express 2000 and from the options within Word XP you either 
cannot reset the ADSL utility, or should never click the controller for 
installing the gadget.
diff -u fakechroot-2.6/debian/control fakechroot-2.6/debian/control
--- fakechroot-2.6/debian/control
+++ fakechroot-2.6/debian/control
@@ -3,7 +3,7 @@
 Section: utils
 Priority: optional
 Standards-Version: 3.7.2
-Build-Depends: libc6-dev-i386 [amd64], libc6-dev-powerpc [ppc64], libc6-dev-s390x [s390], libc6-dev-sparc64 [sparc], gcc-multilib, yada (>= 0.53)
+Build-Depends: libc6-dev-i386 [amd64], libc6-dev-powerpc [ppc64], libc6-dev-s390x [s390], libc6-dev-sparc64 [sparc], yada (>= 0.53)
 
 Package: fakechroot
 Architecture: any
diff -u fakechroot-2.6/debian/changelog fakechroot-2.6/debian/changelog
--- fakechroot-2.6/debian/changelog
+++ fakechroot-2.6/debian/changelog
@@ -1,11 +1,3 @@
-fakechroot (2.6-1.2) unstable; urgency=low
-
-  * Non-maintainer upload.
-  * Add build-dependency on gcc-multilib the yada way to avoid FTBFS. 
-    (Closes: #422586)
-
- -- Sune Vuorela <[EMAIL PROTECTED]>  Sat, 19 May 2007 15:13:28 +0200
-
 fakechroot (2.6-1.1) unstable; urgency=low
 
   * Non-maintainer upload during BSP.
diff -u fakechroot-2.6/debian/packages fakechroot-2.6/debian/packages
--- fakechroot-2.6/debian/packages
+++ fakechroot-2.6/debian/packages
@@ -26,7 +26,6 @@
 Build-Depends: libc6-dev-powerpc [ppc64]
 Build-Depends: libc6-dev-s390x [s390]
 Build-Depends: libc6-dev-sparc64 [sparc]
-Build-Depends: gcc-multilib
 Build: bash
  CC=${CC:-gcc}
  CFLAGS=${CFLAGS:--Wall -pedantic -g}

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to