Your message dated Wed, 8 Jun 2005 01:20:21 +1000
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Re: TODO for Sarge: address #249386 -
kernel-headers on CD1]
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; 17 May 2004 06:33:43 +0000
>From [EMAIL PROTECTED] Sun May 16 23:33:43 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail017.syd.optusnet.com.au [211.29.132.168]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BPbh1-0005WY-00; Sun, 16 May 2004 23:33:43 -0700
Received: from espresso.caffeine (c211-30-26-231.mirnd1.nsw.optusnet.com.au
[211.30.26.231])
by mail017.syd.optusnet.com.au (8.11.6p2/8.11.6) with ESMTP id
i4H6XdM17056
for <[EMAIL PROTECTED]>; Mon, 17 May 2004 16:33:40 +1000
Received: from netsnipe by espresso.caffeine with local (Exim 4.34)
id 1BPbgw-0004HF-FX
for [EMAIL PROTECTED]; Mon, 17 May 2004 16:33:38 +1000
Date: Mon, 17 May 2004 16:33:38 +1000
From: Andrew Lau <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: debian-cd: Sarge CD1 jigdo file lacks matching kernel-headers/source
package
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="ew6BAiZeqk4r7MaW"
Content-Disposition: inline
X-Reportbug-Version: 2.59
X-Debbugs-CC: [email protected]
User-Agent: Mutt/1.5.6i
Sender: Andrew Lau <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-10.0 required=4.0 tests=BAYES_01,HAS_PACKAGE,
X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
--ew6BAiZeqk4r7MaW
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Package: debian-cd
Severity: normal
Hey everyone,
Otavio Salvador recommended that I report this jigdo file bug here. Feel
free to refile it if I've assigned it to the wrong place.
The Jigdo files for Sarge at:
http://gluck.debian.org/cdimage/testing/cd/jigdo-area/i386/
do not prioritise the corresponding kernel-headers and kernel-source
packages for the kernel-image that the installer is using.
% zgrep kernel-source-2.4.26 *
sarge-i386-12.jigdo:GtAK9gxomZaDuSnP3rSBBg=3DDebian:pool/main/k/kernel-sour=
ce-2.4.26/kernel-source-2.4.26_2.4.26-2_all.deb
sarge-i386-13.jigdo:gUh4-TR7enpeKM2zuCiAYA=3DDebian:pool/main/k/kernel-sour=
ce-2.4.26/kernel-doc-2.4.26_2.4.26-2_all.deb
sarge-i386-13.jigdo:8z44y3e_inbjZQ9-xy_lKQ=3DDebian:pool/main/k/kernel-sour=
ce-2.4.26/kernel-patch-debian-2.4.26_2.4.26-2_all.deb
sarge-i386-13.jigdo:b_Lvln53v1gIUVaX9xKKSw=3DDebian:pool/main/k/kernel-sour=
ce-2.4.26/kernel-tree-2.4.26_2.4.26-2_all.deb
% zgrep kernel-headers-2.4.26 *
sarge-i386-13.jigdo:1ATpvFDaOpVHYTzbcyNFug=3DDebian:pool/main/k/kernel-imag=
e-2.4.26-i386/kernel-headers-2.4.26-1-386_2.4.26-2_i386.deb
sarge-i386-13.jigdo:-Z-ho3GY8XynYzaA8UIo8Q=3DDebian:pool/main/k/kernel-imag=
e-2.4.26-i386/kernel-headers-2.4.26-1-586tsc_2.4.26-2_i386.deb
sarge-i386-13.jigdo:VF6_wOS6aL_0jVsUpJH_5A=3DDebian:pool/main/k/kernel-imag=
e-2.4.26-i386/kernel-headers-2.4.26-1-686-smp_2.4.26-2_i386.deb
sarge-i386-13.jigdo:AoNWNiKeKOgQvI0kLVDAWg=3DDebian:pool/main/k/kernel-imag=
e-2.4.26-i386/kernel-headers-2.4.26-1-686_2.4.26-2_i386.deb
sarge-i386-13.jigdo:8WcHONDEO_PxzbwDQVMXYA=3DDebian:pool/main/k/kernel-imag=
e-2.4.26-i386/kernel-headers-2.4.26-1-k6_2.4.26-2_i386.deb
sarge-i386-13.jigdo:vIPTFRQXAKDFx__U4NGLuw=3DDebian:pool/main/k/kernel-imag=
e-2.4.26-i386/kernel-headers-2.4.26-1-k7-smp_2.4.26-2_i386.deb
sarge-i386-13.jigdo:sibKbTszUfbSkrHYoGKhfQ=3DDebian:pool/main/k/kernel-imag=
e-2.4.26-i386/kernel-headers-2.4.26-1-k7_2.4.26-2_i386.deb
sarge-i386-13.jigdo:gncQ_XaeQcsJy3GhamvaTQ=3DDebian:pool/main/k/kernel-imag=
e-2.4.26-i386/kernel-headers-2.4.26-1_2.4.26-2_i386.deb
=46rom the above output, you can see that the kernel-headers and source
packages for the kernel-image that the installer uses reside on the last
two CDs, and not a lot of people even get around to downloading them.
This problem makes it quite difficult for users to recompile a third
party kernel module (eg. ATI, Nvidia video or Broadcom, Centrino network
drivers) against the stock kernel if they've only obtained the first few
Debian Sarge CDs. Some can't even get online to obtain the header
package in the first place thanks to this.
The Jigdo scripts should override the results of Debian popularity
contest and always place either the Debian kernel-source or
kernel-header package that matches the stock kernel the installer is
using on the first CD in order to facilitate getting the system up and
running when 3rd party drivers are required.
Cheers,
Andrew "Netsnipe" Lau
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.6
Locale: LANG=3Den_AU.UTF-8, LC_CTYPE=3Den_AU.UTF-8
--=20
---------------------------------------------------------------------------
Andrew "Netsnipe" Lau <http://www.cse.unsw.edu.au/~alau/>
Debian GNU/Linux Maintainer & UNSW Computing Students' Society President
-
"Nobody expects the Debian Inquisition!
Our two weapons are fear and surprise...and ruthless efficiency!"
---------------------------------------------------------------------------
--ew6BAiZeqk4r7MaW
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAqFzCmyTAfS6LaL0RArOTAJ4wCG7pMtzwi/SVANhRsz7gE5RrIQCdG8lW
05dZ+J+uVFi+JAeCOKBB/FQ=
=uzZH
-----END PGP SIGNATURE-----
--ew6BAiZeqk4r7MaW--
---------------------------------------
Received: (at 249386-done) by bugs.debian.org; 7 Jun 2005 15:20:24 +0000
>From [EMAIL PROTECTED] Tue Jun 07 08:20:23 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mail24.syd.optusnet.com.au [211.29.133.165]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DffsN-00011j-00; Tue, 07 Jun 2005 08:20:23 -0700
Received: from espresso.caffeine (c211-30-49-101.mirnd1.nsw.optusnet.com.au
[211.30.49.101])
by mail24.syd.optusnet.com.au (8.12.11/8.12.11) with ESMTP id
j57FKLgZ020706
(version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NO)
for <[EMAIL PROTECTED]>; Wed, 8 Jun 2005 01:20:21 +1000
Received: from netsnipe by espresso.caffeine with local (Exim 4.50)
id 1DffsL-0002s5-IO
for [EMAIL PROTECTED]; Wed, 08 Jun 2005 01:20:21 +1000
Date: Wed, 8 Jun 2005 01:20:21 +1000
From: Andrew Lau <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [EMAIL PROTECTED]: Re: TODO for Sarge: address #249386 -
kernel-headers on CD1]
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="pvezYHf7grwyp3Bc"
Content-Disposition: inline
X-PGP-Key-ID: 0x2E8B68BD
X-PGP-Fingerprint: 0B77 73D0 4F3B F286 63F1 9F4A 9B24 C07D 2E8B 68BD
X-PGP-Key: http://pgp.dtype.org:11371/pks/lookup?op=get&search=0x2E8B68BD
User-Agent: Mutt/1.5.9i
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
--pvezYHf7grwyp3Bc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Thanks Steve.
Closing the report.
----- Forwarded message from Steve McIntyre <[EMAIL PROTECTED]> -----
=46rom: Steve McIntyre <[EMAIL PROTECTED]>
To: Andrew Lau <[EMAIL PROTECTED]>
Cc: [email protected]
Subject: Re: TODO for Sarge: address #249386 - kernel-headers on CD1
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on espresso.caffeine
X-Spam-Level:=20
X-Spam-Status: No, score=3D-2.5 required=3D5.0 tests=3DAWL,BAYES_00 autolea=
rn=3Dham=20
version=3D3.0.3
On Mon, Jun 06, 2005 at 12:14:21PM +1000, Andrew Lau wrote:
>On Sun, Jun 05, 2005 at 08:55:14PM +0100, Steve McIntyre wrote:
>> In the end, we've managed to get kernel-headers on CD#1 for i386
>> easily, and will do the same on amd64, but on other arches:
>>=20
>> a) there's not much point
>> b) it screwed up tasks
>>=20
>> so we didn't do it for any others. I hope that does what you need...
>
>Thanks Steve!
>
>That'd be enough to get me out of most scrapes at Installfests from now
>on. Will I need to remind you of this again for 3.1r1, or has this been
>added to the future image generation procedure now?
It's been added into the scripts that generate the CD task lists, so
it should work fine from now on.
--=20
Steve McIntyre, Cambridge, UK. [EMAIL PROTECTED]
com
"I suspect most samba developers are already technically insane... Of
course, since many of them are Australians, you can't tell." -- Linus Torv=
alds
----- End forwarded message -----
--=20
---------------------------------------------------------------------------
Andrew "Netsnipe" Lau <http://www.cse.unsw.edu.au/~alau/>
Debian GNU/Linux Maintainer & Computer Science, UNSW
-
"Nobody expects the Debian Inquisition!
Our two weapons are fear and surprise...and ruthless efficiency!"
---------------------------------------------------------------------------
--pvezYHf7grwyp3Bc
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCpbs1myTAfS6LaL0RAqkWAJ9kgiWHQ4bT0m1jPLqY21k59dNNcwCguL2s
boZgaC4SLrHGEgAd2kzC7tg=
=Ze9V
-----END PGP SIGNATURE-----
--pvezYHf7grwyp3Bc--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
