Your message dated Wed, 23 Mar 2005 04:32:18 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#291600: fixed in gibraltar-bootcd 0.50
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 21 Jan 2005 18:36:34 +0000
>From [EMAIL PROTECTED] Fri Jan 21 10:36:34 2005
Return-path: <[EMAIL PROTECTED]>
Received: from master.green-dragon.org [80.68.90.70] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Cs3e6-0005Su-00; Fri, 21 Jan 2005 10:36:34 -0800
Received: from lactodorum.jadevine.org.uk ([82.152.39.136] helo=jupiter)
by master.green-dragon.org with esmtp (Exim 3.35 #1 (Debian))
id 1Cs3e5-0005mn-00; Fri, 21 Jan 2005 18:36:33 +0000
Received: from stephen by jupiter with local (Exim 3.36 #1 (Debian))
id 1Cs3fH-0005WG-00; Fri, 21 Jan 2005 18:37:47 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Stephen Quinney <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: FTBFS: Attempts to use 'apt-get source'
X-Mailer: reportbug 3.6
Date: Fri, 21 Jan 2005 18:37:47 +0000
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: gibraltar-bootcd
Severity: serious
I was just attempting to build gibraltar-bootcd version 0.40 from the
source using pbuilder and it failed horribly.
Upon investigation I found that debian/rules is calling two scripts:
build-discover (which attempts to download the source for curl, expat
and discover) and build-paste (which attempts to grab the source for
coreutils). This is total and utter madness, I've never come across
anything so odd before in my experience of Debian packaging.
You must not assume even the existence of a network connection from a
buildd never mind the ability to run apt-get. It must be possible to
build a package inside a self-contained chroot. You should also note
that there is a high chance that the apt source urls will not be
listed in typical chroots.
I am absolutely certain that you really do not need to download the
source code for each of these packages and then build them. There must
be a better way to achieve what you are trying to do here.
Stephen Quinney
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
---------------------------------------
Received: (at 291600-close) by bugs.debian.org; 23 Mar 2005 09:38:19 +0000
>From [EMAIL PROTECTED] Wed Mar 23 01:38:19 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DE2Je-0002NF-00; Wed, 23 Mar 2005 01:38:18 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DE2Dq-0001h6-00; Wed, 23 Mar 2005 04:32:18 -0500
From: Rene Mayrhofer <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#291600: fixed in gibraltar-bootcd 0.50
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 23 Mar 2005 04:32:18 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 2
Source: gibraltar-bootcd
Source-Version: 0.50
We believe that the bug you reported is fixed in the latest version of
gibraltar-bootcd, which is due to be installed in the Debian FTP archive:
gibraltar-bootcd_0.50.dsc
to pool/main/g/gibraltar-bootcd/gibraltar-bootcd_0.50.dsc
gibraltar-bootcd_0.50.tar.gz
to pool/main/g/gibraltar-bootcd/gibraltar-bootcd_0.50.tar.gz
gibraltar-bootsupport_0.50_i386.deb
to pool/main/g/gibraltar-bootcd/gibraltar-bootsupport_0.50_i386.deb
mkinitrd-cd_0.50_i386.deb
to pool/main/g/gibraltar-bootcd/mkinitrd-cd_0.50_i386.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 PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Rene Mayrhofer <[EMAIL PROTECTED]> (supplier of updated gibraltar-bootcd
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 PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sat, 5 Mar 2005 22:21:26 +0100
Source: gibraltar-bootcd
Binary: mkinitrd-cd gibraltar-bootsupport
Architecture: source i386
Version: 0.50
Distribution: unstable
Urgency: low
Maintainer: Rene Mayrhofer <[EMAIL PROTECTED]>
Changed-By: Rene Mayrhofer <[EMAIL PROTECTED]>
Description:
gibraltar-bootsupport - Boot support for Gibraltar live CD-ROM
mkinitrd-cd - Creates an initrd image for booting from a live CD-ROM or USB dev
Closes: 288295 291600
Changes:
gibraltar-bootcd (0.50) unstable; urgency=low
.
* Include the Debian package source for curl, expat, discover and
coreutils (which are used for buidling the binary package mkinitrd-cd).
I am still not happy with that solution because it wastes bandwith and
storage space for all Debian mirrors, but I agree with Goswin that source
updates are a problem that can lead to DFSG conflicts. If anybody has an
idea on how to solve this without duplicating source packages in this
source package, please drop me a hint.
Closes: #291600: FTBFS: Attempts to use 'apt-get source'
* gibraltar-bootsupport: Fix a small bug in common-definitions.sh which
caused a (cosmetical) error during shutdown.
* mkinitrd-cd: Compile busybox during package build and ship it with
mkinitrd-cd. This makes the mkinitrd-cd script a lot faster and should not
need to be modified anyways.
* mkinitrd-cd: Make it work with kernel 2.6. Necessary changes were:
- also look for *.ko in addition to *.o
- some module names have been changed, namely
Closes: #288295: mkinitrd-cd: no support for 2.6 kernel objects
* mkinitrd-cd: Introduce a config file /etc/mkinitrd-cd/mkinitrd-cd.conf
with config options that could possible by modified. This file is also
source during package build, as it contains the busybox modules to build
(and install in the initrd image during the mkinitrd-cd run).
* Move architecture-dependent files from /usr/share/mkinitrd-cd to
/usr/lib/mkinitrd-cd, as demanded by FHS. These are the discover, paste
and busybox binaries that are built during the package building.
* Copy only *.xml files for discover and skip the *.lst files - they are
only needed to create the *.xml files, but not during usage.
Thanks to Thomas Lange for suggesting a few of the above changes!
Files:
a66e216fbc3226b2fd02874d4e46696e 608 admin optional gibraltar-bootcd_0.50.dsc
23671e70d12a7d8bb41970ef28e5eed4 9027406 admin optional
gibraltar-bootcd_0.50.tar.gz
4719f322ae58aede46995d8ca0121c8b 226800 admin optional
mkinitrd-cd_0.50_i386.deb
ab12e64198ca910edd6905df54c9736b 254238 admin optional
gibraltar-bootsupport_0.50_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCK0Ztq7SPDcPCS94RAmWkAJ9hijDi2iCI4x5ueOnco2x40ALK/gCeNhdm
5aE4bRYb4mQI1DlbUfjorDo=
=iZ3+
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
