Your message dated Sat, 17 Dec 2005 15:40:29 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#340298: Patch to clarify the Ports page
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; 22 Nov 2005 14:25:55 +0000
>From [EMAIL PROTECTED] Tue Nov 22 06:25:55 2005
Return-path: <[EMAIL PROTECTED]>
Received: from a-eskwadraat.nl ([131.211.39.72])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EeZ5n-00057v-GP
for [EMAIL PROTECTED]; Tue, 22 Nov 2005 06:25:55 -0800
Received: from 22pc220.sshunet.nl ([145.97.220.22] helo=bla.wolffelaar.nl)
by a-eskwadraat.nl with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32)
(Exim 4.50)
id 1EeZ5k-0004Ya-Rt
for [EMAIL PROTECTED]; Tue, 22 Nov 2005 15:25:53 +0100
Received: from jeroen by bla.wolffelaar.nl with local (Exim 4.50)
id 1EeZ5l-0001Xm-GB
for [EMAIL PROTECTED]; Tue, 22 Nov 2005 15:25:53 +0100
Date: Tue, 22 Nov 2005 15:25:53 +0100
From: Jeroen van Wolffelaar <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: www.debian.org/ports unclear about ia64
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.8
X-Debbugs-Cc: debian-ia64@lists.debian.org
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-Level:
X-Spam-Status: No, hits=-11.0 required=4.0 tests=BAYES_00,HAS_PACKAGE,
X_DEBBUGS_CC autolearn=ham version=2.60-bugs.debian.org_2005_01_02
Package: www.debian.org
Severity: important
www.debian.org/ports says about ia64:
"This is a port to Intel's 64-bit architecture."
Without further any warning/information about that other 64bit architecture
intel, amd etc are producing: amd64. A *lot* of people try to use ia64
installation media to install Debian on their Opteron's etc, and then mail
(for example) debian-cd that the cd is broken and doesn't boot.
The paragraph in question could and IMHO should be more elaborate, like,
saying it's Intel *alpha* 64, aka Itanium, and mention it's a high-end
processor that's not available in consumer's computer shops at all, and
also mention there exists another 64-bit processer made by Intel and
others, that is *not* ia64, but rather 'amd64'.
The fact that i386 is also called ia32 above, without any introduction to
what ia32 means, isn't helping at all of course. If it doesn't serve
anything, I strongly suggest to drop the name of 'ia-32', I've never
heard of it before, while eh, I've been an i386 users for quite some time.
Mentioning 'Pentium', 'Sempron' etc would seem more useful to me, as that's
much more likely to be known to people than ia32 and even i386. Generally,
having a bit of availability info in the summary so that people can more
easily find which one's they need to look at. The m68k entry is a good
example of this.
I've X-Debbugs-Cc'd debian-ia64, who can maybe elaborate on this, or
correct me where I've been wrong (I know very little about ia64 myself).
(filed at important due to the huge amount of confusion this and maybe some
other debian.org pages cause in this regard).
Thanks,
--Jeroen
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-k7
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
--
Jeroen van Wolffelaar
[EMAIL PROTECTED]
http://jeroen.A-Eskwadraat.nl
---------------------------------------
Received: (at 340298-done) by bugs.debian.org; 17 Dec 2005 14:41:02 +0000
>From [EMAIL PROTECTED] Sat Dec 17 06:41:02 2005
Return-path: <[EMAIL PROTECTED]>
Received: from smtp15.wxs.nl ([195.121.247.6])
by spohr.debian.org with esmtp (Exim 4.50)
id 1EndF8-0006Aj-Be
for [EMAIL PROTECTED]; Sat, 17 Dec 2005 06:41:02 -0800
Received: from strider.fjphome.nl (ip545593b6.speed.planet.nl [84.85.147.182])
by smtp15.wxs.nl (iPlanet Messaging Server 5.2 Patch 2 (built Jul 14 2004))
with ESMTP id <[EMAIL PROTECTED]> for [EMAIL PROTECTED];
Sat, 17 Dec 2005 15:40:30 +0100 (CET)
Date: Sat, 17 Dec 2005 15:40:29 +0100
From: Frans Pop <[EMAIL PROTECTED]>
Subject: Re: Bug#340298: Patch to clarify the Ports page
In-reply-to: <[EMAIL PROTECTED]>
To: =?iso-8859-1?q?Fr=E9d=E9ric_Bothamy?= <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Message-id: <[EMAIL PROTECTED]>
MIME-version: 1.0
Content-type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary=nextPart1840357.0VVcxKtsPU
Content-transfer-encoding: 7bit
User-Agent: KMail/1.7.2
References: <[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-Level:
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
--nextPart1840357.0VVcxKtsPU
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
On Saturday 17 December 2005 15:13, Fr=E9d=E9ric Bothamy wrote:
> Here is a patch to clarify which port EM64T users should use as this
> seems to generate a lot of confusion for Intel users who try (and fail)
> to use IA64 images.
Applied with thanks.
I've made a few textual changes to your patch. Please let me know if you=20
don't like them and I can fix it.
Cheers,
=46JP
--nextPart1840357.0VVcxKtsPU
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQBDpCNegm/Kwh6ICoQRAkOkAJ9HToKjwilaz9zPITzaX8wmlildwQCgkENu
nTiKv0ThL967sUgTdrDjHOc=
=St4T
-----END PGP SIGNATURE-----
--nextPart1840357.0VVcxKtsPU--
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
