Your message dated Wed, 7 May 2008 12:02:25 +0200 with message-id <200805071202.25932.elendil@planet.nl> and subject line Re: Bug#479913: linux-kernel-di-i386-2.6: FTBFS: Nonexistent build-dependency: linux-image-2.6.24-1-486 has caused the Debian Bug report #479913, regarding linux-kernel-di-i386-2.6: FTBFS: Nonexistent build-dependency: linux-image-2.6.24-1-486 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 owner@bugs.debian.org immediately.) -- 479913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479913 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux-kernel-di-i386-2.6: FTBFS: Nonexistent build-dependency: linux-image-2.6.24-1-486
- From: Lucas Nussbaum <lucas@lucas-nussbaum.net>
- Date: Wed, 7 May 2008 10:28:39 +0200
- Message-id: <[🔎] 20080507082839.GA938@xanadu.blop.info>
Package: linux-kernel-di-i386-2.6 Version: 1.60 Severity: serious User: debian-qa@lists.debian.org Usertags: qa-ftbfs-20080506 qa-ftbfs Justification: FTBFS on i386 Hi, During a rebuild of all packages in sid, your package failed to build on i386. This rebuild was done with gcc 4.3 instead of gcc 4.2, because gcc 4.3 is now the default on most architectures (even if it's not the case on i386 yet). Consequently, many failures are caused by the switch to gcc 4.3. If you determine that this failure is caused by gcc 4.3, feel free to downgrade this bug to 'important' if your package is only built on i386, and this bug is specific to gcc 4.3 (i.e the package builds fine with gcc 4.2). Relevant part: > ** Using build dependencies supplied by package: > Build-Depends: kernel-wedge (>= 2.44), linux-image-2.6.24-1-486 [i386] > Checking for already installed source dependencies... > kernel-wedge: missing > Using default version 2.44 > linux-image-2.6.24-1-486: missing > Checking for source dependency conflicts... > Reading package lists... > Building dependency tree... > Reading state information... > Package linux-image-2.6.24-1-486 is not available, but is referred to by another package. > This may mean that the package is missing, has been obsoleted, or > is only available from another source > E: Package linux-image-2.6.24-1-486 has no installation candidate The full build log is available from: http://people.debian.org/~lucas/logs/2008/05/06 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing a sid i386 environment. Internet was not accessible from the build systems. -- | Lucas Nussbaum | lucas@lucas-nussbaum.net http://www.lucas-nussbaum.net/ | | jabber: lucas@nussbaum.fr GPG: 1024D/023B3F4F |
--- End Message ---
--- Begin Message ---
- To: 479913-done@bugs.debian.org
- Cc: Lucas Nussbaum <lucas@lucas-nussbaum.net>
- Subject: Re: Bug#479913: linux-kernel-di-i386-2.6: FTBFS: Nonexistent build-dependency: linux-image-2.6.24-1-486
- From: Frans Pop <elendil@planet.nl>
- Date: Wed, 7 May 2008 12:02:25 +0200
- Message-id: <200805071202.25932.elendil@planet.nl>
- In-reply-to: <[🔎] 20080507082839.GA938@xanadu.blop.info>
- References: <[🔎] 20080507082839.GA938@xanadu.blop.info>
Hi Lucas, On Wednesday 07 May 2008, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build on > i386. I thought we'd agreed that trying to rebuild the linux-kernel-di-*-2.6 and linux-modules-di-*-2.6 packages was rather pointless and that you would exclude them, or at least not report bugs against them? Closing as the cause of this failure is known and not something that needs to be kept track of. Cheers, FJPAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---