Re: Re: Must debian-installer use iso-codes package when choosing country?

[Anthony Johnson]

--- "Carlos Z.F. Liu" <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 03, 2004 at 05:48:43PM -0800, Anthony
> Johnson wrote:
> > No, some of you did, but more don't(especially
> people
> > in China mainland), AFAIK.
> As a chinese, I think most people in mainland won't
> mind using "Taiwan"
I am also Chinese(please do not use 'chinese')
I don't think so. Many people do mind here.
> here. Even in many governmental newspapers, they
> also use "Taiwan"
This is just short name, not as the same case in d-i.
> directly sometimes.
> 
> -- 
>  Best Regards,
>  Carlos
> 
> 
> -- 
> To UNSUBSCRIBE, email to
> [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: Must debian-installer use iso-codes package when choosing country?

[Anthony Johnson]

Then use the translated iso-codes in countrychooser
--- "Carlos Z.F. Liu" <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 03, 2004 at 02:28:49PM -0600, Steve
> Langasek wrote:
> > Will these users be installing using English or
> Traditional Chinese as
> > the language?
> Unfortunately, even you choose Traditional Chinese
> in languagechooser,
> you will still get english country/area names in the
> next screen. You
> can see translated names in full country list only.
> It's an old bug
> since countrychooser was change to current style.
> 
> -- 
>  Best Regards,
>  Carlos
> 
> 
> -- 
> To UNSUBSCRIBE, email to
> [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
> [EMAIL PROTECTED]
> 


__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241256: possible discover bug ? (Was Re: Bug#241256: Debian-Installer bug report)

[Sven Luther]

On Sun, Apr 04, 2004 at 01:19:55AM -0500, David Nusinow wrote:
> On Thu, Apr 01, 2004 at 11:30:47AM +0200, Sven Luther wrote:
> > On Thu, Apr 01, 2004 at 11:34:05AM +0900, Takushi Fujiwara wrote:
> > > ps.
> > > Installer detect iMac G3(Early 2001) Build in Ethernet but module is not
> > > installed.
> > 
> > The :
> > 
> > < >   GMAC (G4/iBook ethernet) support (OBSOLETE, use Sun GEM) 
> >  
> > driver has been replaced by the : 
> > 
> > <*>   Sun GEM & Apple GMAC support 
> > 
> > which should do as fine for you, and is indeed builtin. This should work
> > without problem for you, or else i would like to know about it.
> > 
> > The more probable reason for what i seem to understand your problem is,
> > is that discover/discover2 doesn't know about this change, and is not
> > able to load the sungem driver for your hardware, this would be a
> > bugreport against discover if this was the case, but to be certain, we
> > need more info.
> 
> Right. To fix this, or even check on it, I'll need the output of lspci
> and lspci -n. Only a couple of things in discover's current database use
> the sungem driver, so if there are more now, I'd like to get them in.
> Even if the driver is compiled in to the kernel right now, I'd still
> like the entry in the database for completeness sake as well as a
> fallback.

What about using the kernel source as inspiration ? 

static struct pci_device_id gem_pci_tbl[] = {
{ PCI_VENDOR_ID_SUN, PCI_DEVICE_ID_SUN_GEM,
  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0UL },

/* These models only differ from the original GEM in
 * that their tx/rx fifos are of a different size and
 * they only support 10/100 speeds. -DaveM
 * 
 * Apple's GMAC does support gigabit on machines with
 * the BCM54xx PHYs. -BenH
 */
{ PCI_VENDOR_ID_SUN, PCI_DEVICE_ID_SUN_RIO_GEM,
  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0UL },
{ PCI_VENDOR_ID_APPLE, PCI_DEVICE_ID_APPLE_UNI_N_GMAC,
  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0UL },
{ PCI_VENDOR_ID_APPLE, PCI_DEVICE_ID_APPLE_UNI_N_GMACP,
  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0UL },
{ PCI_VENDOR_ID_APPLE, PCI_DEVICE_ID_APPLE_UNI_N_GMAC2,
  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0UL },
{ PCI_VENDOR_ID_APPLE, PCI_DEVICE_ID_APPLE_K2_GMAC,
  PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0UL },
{0, }
};

#define PCI_VENDOR_ID_SUN   0x108e
#define PCI_DEVICE_ID_SUN_GEM   0x2bad
#define PCI_DEVICE_ID_SUN_RIO_GEM   0x1101
#define PCI_VENDOR_ID_APPLE 0x106b
#define PCI_DEVICE_ID_APPLE_UNI_N_GMAC  0x0021
#define PCI_DEVICE_ID_APPLE_UNI_N_GMACP 0x0024
#define PCI_DEVICE_ID_APPLE_UNI_N_GMAC2 0x0032
#define PCI_DEVICE_ID_APPLE_K2_GMAC 0x004c

Taken from the sungem driver of the 2.4.25-powerpc kernel.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Must debian-installer use iso-codes package when choosing country?

[Alastair McKinstry]

DÃ Domh, 2004-04-04 ag 02:53 +0200, scrÃobh Frans Pop:

> I really think that using the 'really' short names (that is just plain Taiwan 
> instead of Taiwan, P.. of C..) would not be a bad compromise despite what the 
> official so called short UN names say.

Agreed the "official short names" are ugly ;
(http://www.iso.org/iso/en/prods-services/iso3166ma/02iso-3166-code-lists/list-en1.html)
 eg. "LAO PEOPLE'S DEMOCRATIC REPUBLIC", "LIBYAN ARAB JAMAHIRIYA" for
those countries normally called "Laos" and "Libya". However, sometimes
the short version is the problem too: eg. do we allow 
"MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF", to be shortened to
"Macedonia"? I'm sure the Greeks won't agree to that ...

> After all, isn't Linux for a large part about being "free" as in "able to 
> choose for yourselves" which is what Taiwan has been trying to to for the 
> past decades.

Ironically, one of the main reasons I created the iso-codes package is
to allow this; if someone wanted to create "Kurdish Linux" and add
Kurdistan as a territory, then they would only have 1 list to override
or correct on Linux, rather than n separate lists of countries and
translations ...
(But I don't want to fork Debian over this issue :-( )


> I think the really short names are often a lot more politically neutral than 
> the semi-official names in iso-3166. 

The countries in question have used the list to make their own political
points; but the problem is that Debian deciding to change some names and
not others is no longer being neutral. 


> FJP

Regards,
Alastair


-- 
Alastair McKinstry <[EMAIL PROTECTED]>
GPG Key fingerprint = CD45 260A 4546 C3C0 F595  F0F6 4132 BF90 2A38 5C57
He that would make his own liberty secure must guard even his enemy from
oppression; for if he violates this duty he establishes a precedent that
will reach to himself.

- --Thomas Paine

Bug#241984: more comments about installation

[Joe Drew]

I accidentally mistyped my WEP key; DHCP failed for obvious reasons, but
it should say said "You may have mis-typed your WEP key" if one is
entered in such a situation, and offer to take you right back there
before retrying.

-- 
Joe Drew <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>

Just admit to yourself that you're a thief: http://me.woot.net/stealing.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#229325: marked as done (countrychooser: please use "country/region" instead of "country")

[Debian Bug Tracking System]

Your message dated Sun, 4 Apr 2004 08:26:30 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug fixed
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; 24 Jan 2004 10:13:06 +
>From [EMAIL PROTECTED] Sat Jan 24 02:13:06 2004
Return-path: <[EMAIL PROTECTED]>
Received: from ip203-97-106-233.compass.net.nz (cliux.homeunix.net) [203.97.106.233] 
(postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AkKmn-0001nd-00; Sat, 24 Jan 2004 02:13:06 -0800
Received: from [127.0.0.1] (localhost [127.0.0.1])
by cliux.homeunix.net (Postfix) with ESMTP
id 9311388D; Sat, 24 Jan 2004 23:12:19 +1300 (NZDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Carlos Z.F. Liu" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: countrychooser: please use "country/region" instead of "country"
Reply-To: "Carlos Z.F. Liu" <[EMAIL PROTECTED]>
X-Mailer: reportbug 2.39
Date: Sat, 24 Jan 2004 23:12:18 +1300
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_01_20 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-1.4 required=4.0 tests=FORGED_YAHOO_RCVD,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_01_20
X-Spam-Level: 

Package: countrychooser
Severity: normal

In the selection interface, we should use "country/region" instead of a
lone "country", because many items in the list are not countries.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux cliux.homeunix.net 2.4.24-ck1 #1 Mon Jan 19 01:37:52 NZDT 2004 i686
Locale: LANG=zh_CN.GBK, LC_CTYPE=zh_CN.GBK


---
Received: (at 229325-done) by bugs.debian.org; 4 Apr 2004 06:27:02 +
>From [EMAIL PROTECTED] Sat Apr 03 22:27:02 2004
Return-path: <[EMAIL PROTECTED]>
Received: from lns-th2-5f-81-56-227-253.adsl.proxad.net (kheops.homeunix.org) 
[81.56.227.253] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BA15y-0001PH-00; Sat, 03 Apr 2004 22:27:02 -0800
Received: from localhost (localhost [127.0.0.1])
by kheops.homeunix.org (Postfix) with ESMTP id EF864405D
for <[EMAIL PROTECTED]>; Sun,  4 Apr 2004 08:26:30 +0200 (CEST)
Received: from kheops.homeunix.org ([127.0.0.1])
by localhost (kheops [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 19889-07 for <[EMAIL PROTECTED]>;
Sun, 4 Apr 2004 08:26:29 +0200 (CEST)
Received: from mykerinos.kheops.frmug.org (mykerinos.kheops.frmug.org [192.168.1.3])
by kheops.homeunix.org (Postfix) with ESMTP id 35F764052
for <[EMAIL PROTECTED]>; Sun,  4 Apr 2004 08:26:29 +0200 (CEST)
Received: from localhost (mykerinos.kheops.frmug.org [127.0.0.1])
by mykerinos.kheops.frmug.org (Postfix) with ESMTP id 310FDD064
for <[EMAIL PROTECTED]>; Sun,  4 Apr 2004 08:26:31 +0200 (CEST)
Received: from mykerinos.kheops.frmug.org ([127.0.0.1])
by localhost (cc-mykerinos [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 06799-03 for <[EMAIL PROTECTED]>;
Sun, 4 Apr 2004 08:26:30 +0200 (CEST)
Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426)
id 5A567D058; Sun,  4 Apr 2004 08:26:30 +0200 (CEST)
Date: Sun, 4 Apr 2004 08:26:30 +0200
From: Christian Perrier <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Bug fixed
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-message-flag: Outlook is a good virus spreading tool. It can send mail, too.
X-pot_a_miel: [EMAIL PROTECTED]
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at mykerinos
X-Virus-Scanned: by amavisd-new-20030616-p7 (Debian) at kheops.frmug.org
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=-2.0 required=4.0 tests=BAYES_00 autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Scores: 1

This bug has been fixed in 0.013 release of the package

-- 



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241984: /etc/fstab not written

[Joe Drew]

Package: installation-reports
Severity: important

This is debian-installer beta 3 on powerpc.

Package: installation-reports

Debian-installer-version: beta 3
uname -a: Linux virgo 2.4.25-powerpc #1 ven mar 19 19:29:26 CET 2004 ppc GNU/Linux
Date: 2004-04-04
Method: Businesscard/network install from canadian mirror debian.yorku.ca

Machine: iBook
Processor: 900 MHz G3
Memory: 640 MB
Root Device: /dev/hda
Root Size/partition table:
/dev/hda1 Apple_partition_map   31.5k
/dev/hda2 Apple_Bootstrap   800.0k
/dev/hda3 Apple_UNIX_SVR2   300.0M  swap
/dev/hda4 Apple_UNIX_SVR2   9.7G/
/dev/hda5 Apple_HFS 27.3G   Mac OS X
/dev/hda6 Apple_Free4.0k

Output of lspci:

00:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea AGP
00:10.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon 
Mobility 7500]
10:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea PCI
10:17.0 Class ff00: Apple Computer Inc. KeyLargo/Pangea Mac I/O
10:18.0 USB Controller: Apple Computer Inc. KeyLargo/Pangea USB
10:19.0 USB Controller: Apple Computer Inc. KeyLargo/Pangea USB
20:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea Internal PCI
20:0e.0 Class : Apple Computer Inc. UniNorth/Pangea FireWire (rev ff)
20:0f.0 Class : Apple Computer Inc. UniNorth/Pangea GMAC (Sun GEM) (rev ff)

Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [E]
Config network: [O]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [E]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

My Airport card wasn't detected; this is already dealt with I believe.

I placed an "E" in partition hard drives because my hard drive was
already partitioned; the initial setup for this was absolutely transcendent,
but I didn't format my partition and so I had to go back to the "
Partition hard drive" menu item (since the installer didn't want to
install on top of a semi-installed previous attempt). When I did so
all hell broke loose.

It doesn't seem as though the same menus/etc are used between the initial
setup and what happens when you select the menu item for partition hard drive.
I selected /dev/hda4 as my root, and then /dev/hda3 as swap, and in both cases
I said "leave my partition as-is," but swap somehow got the idea that it
should be mounted as /, and the installer complained. I then specified swap
as swap space and it proceeded.

These problems would have been avoided had the same setup been available
as when the installer first goes through, I think.

The real problem is what happened on boot-up. Here is the contents of
/etc/fstab:
# UNCONFIRURED FSTAB FOR BASE SYSTEM

I blame this on the weird partitioner I got on the second run through as well.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=en_US, LC_CTYPE=en_US


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: Must debian-installer use iso-codes package when choosing country?

[Christian Perrier]

Quoting Tetralet ([EMAIL PROTECTED]):

> You may visit http://moto.debian.org.tw/viewtopic.php?t=3192 for more 
> details.

Provided you read Chinese..:-)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#221533: marked as done (needs to load airport driver)

[Debian Bug Tracking System]

Your message dated Sun, 04 Apr 2004 01:02:02 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#221533: fixed in ddetect 0.82
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; 18 Nov 2003 23:37:06 +
>From [EMAIL PROTECTED] Tue Nov 18 17:37:05 2003
Return-path: <[EMAIL PROTECTED]>
Received: from testing.woot.net (capricorn.woot.net) [65.214.160.189] 
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AMFP6-0002LT-00; Tue, 18 Nov 2003 17:37:04 -0600
Received: from pisces.woot.net (181-117.SPEEDe.golden.net [216.75.181.117])
by capricorn.woot.net (Postfix) with ESMTP
id 7D3A61E4491; Tue, 18 Nov 2003 18:37:03 -0500 (EST)
Received: by pisces.woot.net (Postfix, from userid 1000)
id 8A354FE8FE; Tue, 18 Nov 2003 18:36:46 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Joe Drew <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: install fails - "couldn't download exim4"
X-Mailer: reportbug 2.36
Date: Tue, 18 Nov 2003 18:36:46 -0500
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-6.0 required=4.0
tests=BAYES_20,HAS_PACKAGE
version=2.53-bugs.debian.org_2003_11_15
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_11_15 
(1.174.2.15-2003-03-30-exp)

Package: installation-reports
Severity: important

INSTALL REPORT

Debian-installer-version: Beta 1 100 MB CD image for powerpc
uname -a: Linux (none) 2.4.22-powerpc #1 Sat Sep 27 06:55:23 CEST 2003
ppc unknown
Date: 2003-11-18, 17:00 EST
Method: Boot off CD with 100 MB cd iamge

Machine: iBook
Processor: 900 MHz G3
Memory: 640 MB
Root Device: IDE, /dev/hda
Root Size/partition table: 
/dev/ide/host0/bus0/target0/lun0/part1 Apple_partition_map 31.5k
/dev/ide/host0/bus0/target0/lun0/part2 Apple_Bootstrap 800.0k
/dev/ide/host0/bus0/target0/lun0/part3 Apple_UNIX_SVR2 300.0M swap
/dev/ide/host0/bus0/target0/lun0/part4 Apple_UNIX_SVR2 9.7G /
/dev/ide/host0/bus0/target0/lun0/part5 Apple_HFS 27.3G Mac OS X
/dev/ide/host0/bus0/target0/lun0/part6 Apple_Free 4.0k

Output of lspci:

00:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea AGP
00:10.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M7 LW [Radeon 
Mobility 7500]
10:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea PCI
10:17.0 Class ff00: Apple Computer Inc. KeyLargo/Pangea Mac I/O
10:18.0 USB Controller: Apple Computer Inc. KeyLargo/Pangea USB
10:19.0 USB Controller: Apple Computer Inc. KeyLargo/Pangea USB
20:0b.0 Host bridge: Apple Computer Inc. UniNorth/Pangea Internal PCI
20:0e.0 Class : Apple Computer Inc. UniNorth/Pangea FireWire (rev ff)
20:0f.0 Class : Apple Computer Inc. UniNorth/Pangea GMAC (Sun GEM) (rev ff)

Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [E]
Config network: [E]
Detect CD:  [O]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[E]
Install boot loader:[ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:

At first, DHCP failed since the Debian installer didn't detect my
Airport card. This resulted in the screen background turning red and a
mis-rendered dialogue with no context and a message "Feel free to retry."
This should be changed to at least mention that DHCP failed, and
probably say something about connecting cables and/or consulting with
system administrator about configuration. As it is there's no context:
what exactly are you retrying?

Every so often when I switch between consoles, my screen turns red (and
then will turn blue again for no clear reason).

Partitioning was not very well automated, as I was just dumped into
pfdisk. Luckily I had previously partitioned this drive so I simply
quit. Even so, some better method must exist.

I had previously tried (and failed) to install debian-installer. As such
I didn't reinitialize any disks. When the base system tried installing,
I got an error "couldn't download exim4." I was unable to proceed.

I then tried all over again, but this time I initialized the disk as
ext3 (even though it was already initialized). This time the install
worked.

Comments on tasksel: It doesn't follow the UI of the rest of the

Bug#241256: possible discover bug ? (Was Re: Bug#241256: Debian-Installer bug report)

[David Nusinow]

On Thu, Apr 01, 2004 at 11:30:47AM +0200, Sven Luther wrote:
> On Thu, Apr 01, 2004 at 11:34:05AM +0900, Takushi Fujiwara wrote:
> > ps.
> > Installer detect iMac G3(Early 2001) Build in Ethernet but module is not
> > installed.
> 
> The :
> 
> < >   GMAC (G4/iBook ethernet) support (OBSOLETE, use Sun GEM) 
>  
> driver has been replaced by the : 
> 
> <*>   Sun GEM & Apple GMAC support 
> 
> which should do as fine for you, and is indeed builtin. This should work
> without problem for you, or else i would like to know about it.
> 
> The more probable reason for what i seem to understand your problem is,
> is that discover/discover2 doesn't know about this change, and is not
> able to load the sungem driver for your hardware, this would be a
> bugreport against discover if this was the case, but to be certain, we
> need more info.

Right. To fix this, or even check on it, I'll need the output of lspci
and lspci -n. Only a couple of things in discover's current database use
the sungem driver, so if there are more now, I'd like to get them in.
Even if the driver is compiled in to the kernel right now, I'd still
like the entry in the database for completeness sake as well as a
fallback.

 - David Nusinow


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Processing discover1-data bugs

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 236777 pending
Bug#236777: discover1-data: bad data causes xserver-xfree86 config script to chatter
There were no tags set.
Tags added: pending

> tags 231298 pending
Bug#231298: Should detect and use Broadcom Corporation NetXtreme BCM5782 Gigabit 
Ethernet
Tags were: d-i
Tags added: pending

> tags 233147 pending
Bug#233147: didn't detect the NVidia card
Tags were: d-i
Tags added: pending

> tags 241977 pending
Bug#241977: installation report, IBM HS20 blade
There were no tags set.
Tags added: pending

> tags 233535 wontfix
Bug#233535: discover-data: erroneous Prism module in pci.list
There were no tags set.
Tags added: wontfix

> quit
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: Must debian-installer use iso-codes package when choosing country?

[Christian Perrier]

Quoting Carlos Z.F. Liu ([EMAIL PROTECTED]):

> Unfortunately, even you choose Traditional Chinese in languagechooser,
> you will still get english country/area names in the next screen. You
> can see translated names in full country list only. It's an old bug
> since countrychooser was change to current style.

Hmmm, yes, that is indeed right. We never found a way to solve this as
the short list is built on the fly.

But, there is AFAIK no bug report about this.or if there is one,
it is not assigned to countrychooser.

Someone should report one, just for the record.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

ddetect_0.82_i386.changes ACCEPTED

[Debian Installer]

Accepted:
archdetect_0.82_i386.udeb
  to pool/main/d/ddetect/archdetect_0.82_i386.udeb
ddetect_0.82.dsc
  to pool/main/d/ddetect/ddetect_0.82.dsc
ddetect_0.82.tar.gz
  to pool/main/d/ddetect/ddetect_0.82.tar.gz
ethdetect_0.82_all.udeb
  to pool/main/d/ddetect/ethdetect_0.82_all.udeb
hw-detect-full_0.82_all.udeb
  to pool/main/d/ddetect/hw-detect-full_0.82_all.udeb
hw-detect_0.82_all.udeb
  to pool/main/d/ddetect/hw-detect_0.82_all.udeb
Announcing to [EMAIL PROTECTED]
Closing bugs: 221533 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#238777: marked as done (defaults to vesa, not savage for S3 Inc. 86C270-294 Savage/MX-MV)

[Debian Bug Tracking System]

Your message dated Sun, 4 Apr 2004 00:52:38 -0500
with message-id <[EMAIL PROTECTED]>
and subject line This bug is already closed
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; 18 Mar 2004 18:33:09 +
>From [EMAIL PROTECTED] Thu Mar 18 10:33:09 2004
Return-path: <[EMAIL PROTECTED]>
Received: from pop.gmx.de (mail.gmx.net) [213.165.64.20] 
by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
id 1B42KK-0006Qp-00; Thu, 18 Mar 2004 10:33:08 -0800
Received: (qmail 2043 invoked by uid 0); 18 Mar 2004 18:32:37 -
Received: from 129.187.254.12 by www3.gmx.net with HTTP;
Thu, 18 Mar 2004 19:32:37 +0100 (MET)
Date: Thu, 18 Mar 2004 19:32:37 +0100 (MET)
From: "Patrick Tischler" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="GMXBoundary302881079634757"
Subject: installation-reports
X-Priority: 3 (Normal)
X-Authenticated: #2382640
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: WWW-Mail 1.6 (Global Message Exchange)
X-Flags: 0001
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-4.5 required=4.0 tests=BAYES_00,BODY_8BITS,DATING,
HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level: 

This is a MIME encapsulated multipart message -
please use a MIME-compliant e-mail program to open it.

Dies ist eine mehrteilige Nachricht im MIME-Format -
bitte verwenden Sie zum Lesen ein MIME-konformes Mailprogramm.

--GMXBoundary302881079634757
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

Package: installation-reports

Debian-installer-version: 2004-03-16 Debian-Installer beta 3 for i386 from
http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-netinst.iso
uname -a: Linux murmeltier 2.4.25-1-386 #1 Tue Feb 24 08:11:13 EST 2004 i686
GNU/Linux
Date: 2004-03-18 11:00 am CET
Method: Debian-Installer beta 3 netinstall; installation from
http://ftp.leo.org; no proxy

Machine: Asus L8400C (in Germany: Medion MD9580A)
Processor: Genuine Intel Pentium III (Coppermine) CPU Mhz 1002.285 (CPU Mhz
with Battery: 701.616) 256KB cache 
Memory: 257024 KB
Root Device: IDE HITACHI_DK23CA-20 20GB /dev/hda
Root Size/partition table: #1 /dev/hda1 primary 510.9MB swap swap
   #2 /dev/hda2 primary 19.46GB reiserfs /
Output of lspci: 
00:00.0 Host bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
(rev 03
)
00:01.0 PCI bridge: Intel Corp. 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge (rev
03)
00:06.0 Multimedia audio controller: ESS Technology ES1988 Allegro-1 (rev
12)
00:06.1 Communication controller: ESS Technology ESS Modem (rev 12)
00:07.0 ISA bridge: Intel Corp. 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corp. 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB/EB/MB PIIX4 ACPI (rev 03)
00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139
C+ (rev 10)
00:0a.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
00:0a.1 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev 80)
01:00.0 VGA compatible controller: S3 Inc. 86C270-294 Savage/MX-MV (rev 12)


Base System Installation Checklist:

Initial boot worked:[0]
Configure network HW:   [0]
Config network: [0]
Detect CD:  [0]
Load installer modules: [0]
Detect hard drives: [0]
Partition hard drives:  [0]
Create file systems:[0]
Mount partitions:   [0]
Install base system:[0]
Install boot loader:[0]
Reboot: [0]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it


Comments/Problems:

My aim was to install a system in American English with a German keyboard
layout.
I'm not sure whether the listed steps of the installationprocess are of use
but here they are. I'll talk about the problems later:

Boot Menu => Enter
Choose Language => en_US 
Keyboard Layout => German (nodeadkeys) 
Try DHCP again => No 
IP => ... 
Netmask => ... 
Gateway => ... 
Nameservers => ... 
hostname => murmeltier 
domain-name => ... 
Partition Disks => Manual (See above) 
Create Filesystems => Yes 
Device for Bootloader GRUB => (hd0) 
System Reboot => Continue 
Welcome => Ok 
GMT => No 
Select time zone => other 
Select time zone => Europe 
Select time zone => Berlin
Root password

Bug#241976: marked as done (missing usb-ohci ids)

[Debian Bug Tracking System]

Your message dated Sun, 4 Apr 2004 00:54:11 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Closing
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; 4 Apr 2004 05:16:42 +
>From [EMAIL PROTECTED] Sat Apr 03 21:16:42 2004
Return-path: <[EMAIL PROTECTED]>
Received: from kitenet.net [64.62.161.42] (postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B9zzu-0006xP-00; Sat, 03 Apr 2004 21:16:42 -0800
Received: from dragon.kitenet.net (216-98-95-35.access.naxs.com [216.98.95.35])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
by kitenet.net (Postfix) with ESMTP id 241DB17F9F
for <[EMAIL PROTECTED]>; Sun,  4 Apr 2004 05:16:41 + (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
id D809D6F1CF; Sun,  4 Apr 2004 00:16:11 -0500 (EST)
Date: Sun, 4 Apr 2004 00:16:11 -0500
From: Joey Hess <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: missing usb-ohci ids
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J"
Content-Disposition: inline
X-Reportbug-Version: 2.54
User-Agent: Mutt/1.5.5.1+cvs20040105i
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=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Scores: 1


--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: discover1-data
Version: 1.2004.02.08-5
Severity: normal

Comparison of usb-discover's uhci list with discover1-data reveals the
following pci ids that are in the former, but not in the latter:

808624c2
808624c4
808624c7

These three are the USB controllers in a Linux Certified LC2000 laptop
which I have on loan. I thought I'd already filed a bug on these, but I
cannot find it. If you need lspci info, I can get that.

808624de
808624d7
808624d4
808624d2

These are from a PIV-based abit motherboard, according to usb-discover's
changelog. Unfortunatly, I don't know any more details.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=3Den_US, LC_CTYPE=3Den_US

-- no debconf information

--=20
see shy jo

--VbJkn9YxBvnuCH5J
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)

iD8DBQFAb5obd8HHehbQuO8RArJIAJ9AD5DO/FWEzQUQ6oDqXDWTV+DLVACg6ysn
LPm1wii+jrdKJOzrUmZJeMc=
=6QFT
-END PGP SIGNATURE-

--VbJkn9YxBvnuCH5J--

---
Received: (at 241976-done) by bugs.debian.org; 4 Apr 2004 05:54:13 +
>From [EMAIL PROTECTED] Sat Apr 03 21:54:13 2004
Return-path: <[EMAIL PROTECTED]>
Received: from out005pub.verizon.net (out005.verizon.net) [206.46.170.143] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BA0aD-0008EH-00; Sat, 03 Apr 2004 21:54:13 -0800
Received: from squee ([129.44.175.211]) by out005.verizon.net
  (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP
  id <[EMAIL PROTECTED]>
  for <[EMAIL PROTECTED]>; Sat, 3 Apr 2004 23:54:13 -0600
Received: by squee (Postfix, from userid 1000)
id D6B6346EB9; Sun,  4 Apr 2004 00:54:11 -0500 (EST)
Date: Sun, 4 Apr 2004 00:54:11 -0500
From: David Nusinow <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Closing
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.5.1+cvs20040105i
X-Authentication-Info: Submitted using SMTP AUTH at out005.verizon.net from 
[129.44.175.211] at Sat, 3 Apr 2004 23:54:12 -0600
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=0.0 required=4.0 tests=none autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 
X-CrossAssassin-Scores:

ddetect override disparity

[Debian Installer]

There are disparities between your recently accepted upload and the
override file for the following file(s):

hw-detect-full_0.82_all.udeb: package says priority is optional, override says 
standard.
hw-detect_0.82_all.udeb: package says priority is optional, override says standard.

Either the package or the override file is incorrect.  If you think
the override is correct and the package wrong please fix the package
so that this disparity is fixed in the next upload.  If you feel the
override is incorrect then please reply to this mail and explain why.

[NB: this is an automatically generated mail; if you replied to one
like it before and have not received a response yet, please ignore
this mail.  Your reply needs to be processed by a human and will be in
due course, but until then the installer will send these automated
mails; sorry.]

--
Debian distribution maintenance software

(This message was generated automatically; if you believe that there
is a problem with it please contact the archive administrators by
mailing [EMAIL PROTECTED])


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

os-prober_0.02_i386.changes is NEW

[Debian Installer]

(new) os-prober_0.02.dsc optional debian-installer
(new) os-prober_0.02.tar.gz optional debian-installer
(new) os-prober_0.02_i386.udeb optional debian-installer
utility to detect other OSes on a set of drives
Changes: os-prober (0.02) unstable; urgency=low
 .
  * Include init dir in the udeb.
Announcing to [EMAIL PROTECTED]


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of ddetect_0.82_i386.changes

[Archive Administrator]

ddetect_0.82_i386.changes uploaded successfully to localhost
along with the files:
  ddetect_0.82.dsc
  ddetect_0.82.tar.gz
  hw-detect_0.82_all.udeb
  ethdetect_0.82_all.udeb
  hw-detect-full_0.82_all.udeb
  archdetect_0.82_i386.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of os-prober_0.02_i386.changes

[Archive Administrator]

os-prober_0.02_i386.changes uploaded successfully to localhost
along with the files:
  os-prober_0.02.dsc
  os-prober_0.02.tar.gz
  os-prober_0.02_i386.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241559: marked as done (installation report, IBM HS20 blade)

[Debian Bug Tracking System]

Your message dated Sun, 04 Apr 2004 00:32:14 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#241559: fixed in usb-discover 0.12
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; 1 Apr 2004 21:14:40 +
>From [EMAIL PROTECTED] Thu Apr 01 13:14:40 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mendel.broad.mit.edu [18.103.9.70] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B99WK-00067t-00; Thu, 01 Apr 2004 13:14:40 -0800
Received: from [18.103.3.50] (cmbde-61e.broad.mit.edu [18.103.3.50])
by mendel.broad.mit.edu (8.12.10/8.12.8) with ESMTP id i31LEcfC020284
for <[EMAIL PROTECTED]>; Thu, 1 Apr 2004 16:14:38 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v613)
To: [EMAIL PROTECTED]
Message-Id: <[EMAIL PROTECTED]>
Content-Type: multipart/alternative; boundary=Apple-Mail-1--532338977
From: Bruce Walker <[EMAIL PROTECTED]>
Subject: installation report, IBM HS20 blade
Date: Thu, 1 Apr 2004 16:14:36 -0500
X-Mailer: Apple Mail (2.613)
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=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


--Apple-Mail-1--532338977
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
charset=US-ASCII;
format=flowed

Package: installation-reports

Debian-installer-version: Beta 3
uname -a: Linux zirconium 2.4.25-1-686-smp #1 SMP Tue Feb 24 12:07:16 
EST 2004 i686 GNU/Linux
Date: Thu Apr  1 15:55:05 EST 2004
Method: beta3 i386 netinst CD
Machine: IBM HS20 blade
Processor: dual 2.8GHz Xeon
Memory: 2.5GB
Root Device: IDE /dev/hda
Root Size/partition table:
Disk /dev/hda: 40.0 GB, 40007761920 bytes
16 heads, 63 sectors/track, 77520 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes

Device Boot  Start End  Blocks   Id  System
/dev/hda1   *   1 969  488344+  83  Linux
/dev/hda2 9708719 3906000   83  Linux
/dev/hda38720   18407 4882752   82  Linux swap
/dev/hda4   18408   7752029792952f  W95 Ext'd (LBA)
/dev/hda5   18408   26157 3905968+  83  Linux
/dev/hda6   26158   7752025886920+  83  Linux
Filesystem   1K-blocks  Used Available Use% Mounted on
/dev/hda1   457656 90392342847  21% /
tmpfs  1293908 0   1293908   0% /dev/shm
/dev/hda2  3844616   1016352   2632964  28% /usr
/dev/hda5  3844584125992   3523296   4% /var

Output of lspci:
00:00.0 Host bridge: ServerWorks CNB20-HE Host Bridge (rev 33)
00:00.1 Host bridge: ServerWorks CNB20-HE Host Bridge
00:00.2 Host bridge: ServerWorks CNB20-HE Host Bridge
00:01.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0f.0 Host bridge: ServerWorks CSB6 South Bridge (rev b0)
00:0f.1 IDE interface: ServerWorks CSB6 RAID/IDE Controller (rev b0)
00:0f.2 USB Controller: ServerWorks CSB6 OHCI USB Controller (rev 05)
00:0f.3 ISA bridge: ServerWorks GCLE-2 Host Bridge
00:10.0 Host bridge: ServerWorks: Unknown device 0110 (rev 12)
00:10.2 Host bridge: ServerWorks: Unknown device 0110 (rev 12)
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S 
Gigabit Ethernet (rev 02)
01:00.1 Ethernet controller: Broadcom Corporation NetXtreme BCM5704S 
Gigabit Ethernet (rev 02)
02:02.0 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 
02)
02:02.1 Fibre Channel: QLogic Corp. QLA2312 Fibre Channel Adapter (rev 
02)


Base System Installation Checklist:

Initial boot worked:[O]
Configure network HW:   [O]
Config network: [O]
Detect CD:  [E]
Load installer modules: [O]
Detect hard drives: [O]
Partition hard drives:  [O]
Create file systems:[O]
Mount partitions:   [O]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems:
This was an install on an IBM HS20 blade.  It uses a USB CDROM and 
floppy.  Installation was ultimately successful, but...

Using netinst CDROM, it loaded the kernel fine and started the 
installer. After the HW detection, it could not see the CDROM to mount 
it (at least it gave a nice prompt saying it couldn't find it, and to 
hi

Secrets of Z00fils revealed! New ph0t0s. Humans fakking @n1m@ls. Stallions penetr@tes human pu-.ss1es. capacitor

[Support dogwood]

Looks like you've come to a real Z00 here! Yeap! We have goats, we have horses,
sheep, snakes, even dogs!

e have lots of @[EMAIL PROTECTED] here and we also have lots of g1r|s who just love
to have some s. e -x with these creatures? How do they do it?


http://dnabri.ding17.biz/50015/?IAFK1


How do they sa-ck those c0c.k-s?

How do they [EMAIL PROTECTED] with snakes? Snakes don't have c0c.k-s!!!

Guys! Our g1r|s can do it with every creature they want!
They are ready for it! They are tired from men!

They do realize that wild @[EMAIL PROTECTED] are [EMAIL PROTECTED] like no man would 
ever [EMAIL PROTECTED] them.
Cause they are animals and they [EMAIL PROTECTED] just like everybody did thousands
and millions years ago!



http://dnabri.ding17.biz/50015/?iYqUR


Stunning 1ma-.ges, v1de0s, art series, lots of @[EMAIL PROTECTED], y0.u-n.g horny g1r|s
[EMAIL PROTECTED] their legs and [EMAIL PROTECTED] c0c-k.s!

This is a first ever -X-.-X-.-X- zoo where every g1r| can [EMAIL PROTECTED] the 
creature she wants!

LOOK AT THIS NOW!




snare clone giggle cave fink monte their canaan mastery vestal cutaneous potentiometer 
dockyard gemstone glycogen respiration ampersand chronic bayou mommy atypic deadlock 
aqueous pliable teddy built mcmahon soapsud ecumenist crease durward insomniac .

millions pact tablecloth lifeboat effeminate glassy sympathetic chimera continuum 
electoral breadfruit delimit grindstone lighthouse diluent coercion irrevocable goff 
beaten transoceanic judicatory medallion apposition marilyn hungary veda allude tall .
aurochs slogan opposable automata inhospitable ceylon plainfield ellipse palladian 
manzanita seedy alger doldrum eros infima agrimony mini megalomania atheism bookseller 
nectarine spencer .

eric dahomey mesmeric orgasm reach theory bonaparte breathy gerber copolymer deuteron 
wing puma narcissus brackish gingham preventive pistol echo chime grandeur indefinable 
teethe macrame nursery debility .

Bug#241976: missing usb-ohci ids

[Martin Michlmayr]

* Joey Hess <[EMAIL PROTECTED]> [2004-04-04 00:16]:
> Comparison of usb-discover's uhci list with discover1-data reveals the

The subject speaks of ohci but the body of uhci.
-- 
Martin Michlmayr
[EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: categorising installation report

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Most of this installation report has already been dealt with, but
> # there are still some bits that can stand to be broken out.
> clone 221533 -1
Bug#221533: install fails - "couldn't download exim4"
Bug 221533 cloned as bug 241979.

> reassign -1 tasksel
Bug#241979: install fails - "couldn't download exim4"
Bug reassigned from package `installation-reports' to `tasksel'.

> retitle -1 tasksel's UI does not really match rest of installer
Bug#241979: install fails - "couldn't download exim4"
Changed Bug title.

> severity -1 minor
Bug#241979: tasksel's UI does not really match rest of installer
Severity set to `minor'.

> reassign 221533 hw-detect
Bug#221533: install fails - "couldn't download exim4"
Bug reassigned from package `installation-reports' to `hw-detect'.

> retitle 221533 needs to load airport driver
Bug#221533: install fails - "couldn't download exim4"
Changed Bug title.

> --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [l10n:ro]iso-3166

[Christian Perrier]

Quoting Eddy Petrisor ([EMAIL PROTECTED]):
> wasn't this file integrated into svn somehow?

It seems that it wasn't. Either because youy didn't send it...or
because I missed it..:-)

It is now commited in CVS (iso-codes is managed by CVS, not SVN)

When in doubt, don't hesitate filing a bug report against the given
package. This is the only way to keep track of what's been sent or
what has not.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

usb-discover_0.12_i386.changes ACCEPTED

[Debian Installer]

Accepted:
usb-discover_0.12.dsc
  to pool/main/u/usb-discover/usb-discover_0.12.dsc
usb-discover_0.12.tar.gz
  to pool/main/u/usb-discover/usb-discover_0.12.tar.gz
usb-discover_0.12_all.udeb
  to pool/main/u/usb-discover/usb-discover_0.12_all.udeb
Announcing to [EMAIL PROTECTED]
Closing bugs: 241559 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: cloning 241559, reassign -1 to discover1-data

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> clone 241559 -1
Bug#241559: installation report, IBM HS20 blade
Bug 241559 cloned as bug 241977.

> reassign -1 discover1-data
Bug#241977: installation report, IBM HS20 blade
Bug reassigned from package `installation-reports' to `discover1-data'.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of usb-discover_0.12_i386.changes

[Archive Administrator]

usb-discover_0.12_i386.changes uploaded successfully to localhost
along with the files:
  usb-discover_0.12.dsc
  usb-discover_0.12.tar.gz
  usb-discover_0.12_all.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241976: missing usb-ohci ids

[Joey Hess]

Package: discover1-data
Version: 1.2004.02.08-5
Severity: normal

Comparison of usb-discover's uhci list with discover1-data reveals the
following pci ids that are in the former, but not in the latter:

808624c2
808624c4
808624c7

These three are the USB controllers in a Linux Certified LC2000 laptop
which I have on loan. I thought I'd already filed a bug on these, but I
cannot find it. If you need lspci info, I can get that.

808624de
808624d7
808624d4
808624d2

These are from a PIV-based abit motherboard, according to usb-discover's
changelog. Unfortunatly, I don't know any more details.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=en_US, LC_CTYPE=en_US

-- no debconf information

-- 
see shy jo


signature.asc
Description: Digital signature

Re: Re: Must debian-installer use iso-codes package when choosing country?

[Carlos Z.F. Liu]

On Sat, Apr 03, 2004 at 05:48:43PM -0800, Anthony Johnson wrote:
> No, some of you did, but more don't(especially people
> in China mainland), AFAIK.
As a chinese, I think most people in mainland won't mind using "Taiwan"
here. Even in many governmental newspapers, they also use "Taiwan"
directly sometimes.

-- 
 Best Regards,
 Carlos


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

os-prober_0.01_i386.changes is NEW

[Debian Installer]

(new) os-prober_0.01.dsc optional debian-installer
(new) os-prober_0.01.tar.gz optional debian-installer
(new) os-prober_0.01_i386.udeb optional debian-installer
utility to detect other OSes on a set of drives
Changes: os-prober (0.01) unstable; urgency=low
 .
  * Initial Release.
Announcing to [EMAIL PROTECTED]


Your package contains new components which requires manual editing of
the override file.  It is ok otherwise, so please be patient.  New
packages are usually added to the override file about once a week.

You may have gotten the distribution wrong.  You'll get warnings above
if files already exist in other distributions.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Must debian-installer use iso-codes package when choosing country?

[Carlos Z.F. Liu]

On Sun, Apr 04, 2004 at 02:53:08AM +0200, Frans Pop wrote:
> I really think that using the 'really' short names (that is just plain Taiwan 
> instead of Taiwan, P.. of C..) would not be a bad compromise despite what the 
> official so called short UN names say.
> After all, isn't Linux for a large part about being "free" as in "able to 
> choose for yourselves" which is what Taiwan has been trying to to for the 
> past decades.
> I think the really short names are often a lot more politically neutral than 
> the semi-official names in iso-3166. Especially as 3116 is incredibly 
> inconsistent. _Short_ names should be _short_.
I also prefer the really _short_ name.

-- 
 Best Regards,
 Carlos


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: Must debian-installer use iso-codes package when choosing country?

[Carlos Z.F. Liu]

On Sat, Apr 03, 2004 at 02:28:49PM -0600, Steve Langasek wrote:
> Will these users be installing using English or Traditional Chinese as
> the language?
Unfortunately, even you choose Traditional Chinese in languagechooser,
you will still get english country/area names in the next screen. You
can see translated names in full country list only. It's an old bug
since countrychooser was change to current style.

-- 
 Best Regards,
 Carlos


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of os-prober_0.01_i386.changes

[Archive Administrator]

os-prober_0.01_i386.changes uploaded successfully to localhost
along with the files:
  os-prober_0.01.dsc
  os-prober_0.01.tar.gz
  os-prober_0.01_i386.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241559: installation report, IBM HS20 blade

[Bruce Walker]

lspci -v:
:00:0f.2 USB Controller: ServerWorks CSB6 OHCI USB Controller (rev 
05) (prog-if 10 [OHCI])
Subsystem: ServerWorks: Unknown device 0220
Flags: bus master, medium devsel, latency 64, IRQ 7
Memory at febfe000 (32-bit, non-prefetchable)

lspci -vn:
:00:0f.2 Class 0c03: 1166:0221 (rev 05) (prog-if 10)
Subsystem: 1166:0220
Flags: bus master, medium devsel, latency 64, IRQ 7
Memory at febfe000 (32-bit, non-prefetchable)
/usr/share/discover/pci.lst:
1166 Relience Computer
	 ...
11660220usb usb-ohciOSB4/CSB5 OHCI USB 
Controller
11660221unknown unknown CSB6 OHCI USB Controller

Thanks,
--bruce


On Apr 2, 2004, at 7:20 PM, Joey Hess wrote:
hw-detect only loads usb-storage if it sees a usb bus.
So the only problem is probably a missing PCI id for your USB
controller in discover1-data. Could you send the necessary info?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#240575: installation-reports: Fails to boot on Alpha

[Steve Langasek]

Craig,

On Sun, Mar 28, 2004 at 11:20:07AM +1000, Craig Small wrote:
> Package: installation-reports
> Version: beta 3
> Severity: grave
> Justification: renders package unusable

> I tried the beta 3 CD on my alpha, it doesn't boot.

> Here is what happens from the SRM console, the command I used was 
> "boot dqb" 

> (boot dqb1.1.1.208.0 -flags 0)
> block 0 of dqb1.1.1.208.0 is a valid boot block
> reading 171 blocks from dqb1.1.1.208.0
> bootstrap code read in
> vase = 20, image_start = 0, image_bytes = 15600
> initializing HWRPB at 2000
> initializing page table at ffee000
> initializing machine state
> setting affinity to the primary CPU
> jumping to bootstrap code
> aboot: Linux/Alpha SRM bootloaded version 0.9b
> aboot: switching to OSF/1 PALcode version 1.23
> aboot: booting from device 'IDE 0 208 1 1 1 0 0'

> cb_open: failed IDE 0 208 1 1 1 0 0, dqb1.1.1.208.0
> aboot: unable to open boot device 'IDE 0 208 1 1 1 0 0': c000
> aboot: kernel load failed (-1)

I've configured my CD ROM as a slave drive on the IDE bus, and it still
boots the d-i CDs just fine.  Did any of the other ideas in my previous
email pan out?

Thanks,
-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature

Re: debian-installer: how much memory is needed (on other archs than i386) ?

[Stephen R Marenka]

On Sat, Apr 03, 2004 at 11:04:13PM +0200, Holger Levsen wrote:
> Hello,
> 
> from the beta2 announcement: "Support for systems with only 32 MB of memory 
> (i386 only)." anybody ot an idea what the requirements for other archs (e.g. 
> powerpc) are ? I guess they should be roughly the same ?
> 
> The lowest I tested was 48mb which seemed fine.

m68k has had a successful install at 24mb.

-- 
Stephen R. Marenka If life's not fun, you're not doing it right!
<[EMAIL PROTECTED]>


signature.asc
Description: Digital signature

Re: Re: Must debian-installer use iso-codes package when choosing country?

[Anthony Johnson]

--- Tetralet <[EMAIL PROTECTED]> wrote:

> We, the debian users in Taiwan, Hongkong and
> mainland China, have 
> discussed about this for several days.
> We all consent that to replace "Taiwan" with
> "Taiwan, Province of China" 
> is not suitable.
No, some of you did, but more don't(especially people
in China mainland), AFAIK.

As already discussed several times here: There is no
way to satisfy everybody. Debian should not
participate in this kind of arguments.
"We have to choose names from some standards body
somewhere, and no matter
what we do somebody will disagree." -- as Colin has
said.



__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of debian-installer_20040403_i386.changes

[Archive Administrator]

debian-installer_20040403_i386.changes uploaded successfully to localhost
along with the files:
  debian-installer_20040403.dsc
  debian-installer_20040403.tar.gz
  debian-installer-manual_20040403_i386.deb
  debian-installer-images_20040403_i386.tar.gz

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Sr, Best prices for medication.

[Japed Q. Excommunicates]

Buenos tardes!The pursuit of happiness is the chase of a life time.
Sr, searching for a place to buy medication?
Getting older is like riding a bicycle, if you don't keep peddling, you'll fall.Can anything be so elegant as to have few wants, and to serve them one's self?In the city a funeral is just an interruption of traffic in the country it is a form of popular entertainment.
We ship worldwide
When we direct our thoughts properly, we can control our emotions...
Go here and get it
You are totally anonymous!
The dice of Zeus always fall luckily.The art of conversation consist as much in listening politely, as in talking agreeably.

Processed: Processing #238472

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 238472 discover1
Bug#238472: discover should not load i810-tco module
Bug reassigned from package `discover1-data' to `discover1'.

> quit
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Process #238472

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 238472 important
Bug#238472: discover should not load i810-tco module
Severity set to `important'.

> reassign 238472 discover1-data
Bug#238472: discover should not load i810-tco module
Bug reassigned from package `discover1' to `discover1-data'.

> quit
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[l10n:ro]iso-3166

[Eddy Petrisor]

wasn't this file integrated into svn somehow?

Eddy

__
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway 
http://promotions.yahoo.com/design_giveaway/

ro.po
Description: ro.po

Re: Must debian-installer use iso-codes package when choosing country?

[Frans Pop]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Saturday 03 April 2004 22:28, Steve Langasek wrote:
> Will these users be installing using English or Traditional Chinese as
> the language?

The problem is that some users in that area will install in English, 
especially for servers.
I really think that using the 'really' short names (that is just plain Taiwan 
instead of Taiwan, P.. of C..) would not be a bad compromise despite what the 
official so called short UN names say.

After all, isn't Linux for a large part about being "free" as in "able to 
choose for yourselves" which is what Taiwan has been trying to to for the 
past decades.
I think the really short names are often a lot more politically neutral than 
the semi-official names in iso-3166. Especially as 3116 is incredibly 
inconsistent. _Short_ names should be _short_.

FJP
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFAb1x0gm/Kwh6ICoQRAmacAJ0WQ7Q7K44lzqj6IYtnvWq4Ys/qTQCfTC+y
uZH/32RjGoJWfUF1QBmeChk=
=yDZh
-END PGP SIGNATURE-

the new super via|g|ra you have been hearing about prolix

[Terrance Rhodes]

Hello Debian-boot,

C:ialis (Apqalis), at rock-bottom prpces.
Most places charge $9, while we charge only $3.
Quite a difference.
http://biometrika.medsplace.net/sv/index.php?pid=eph3404

Ciakis is known as a S)(per-viagr-a or Weekend-Viasra because its effects start sooner 
and last much lotger.

Shieped worldwide.

Your easy-to-use solution is here:
http://bragg.hotspringprices.com/sv/index.php?pid=eph3404

The [EMAIL PROTECTED] Gener&ic [EMAIL PROTECTED]@ also available HERE:
http://lamp.mybestchoice.net/gv/index.php?pid=eph3404






copter

Bug#241943: impossible to correct an error in net modules config

[sylvain ferriol]

Package: ethdetect
Version: 0.81
when configuring net modules parameters, if we 've made a mistake and 
the modprobe is ok.
it is impossible to go back  and  correct module parameters (unless you 
are in expert mode).
you are always directed to the dhcp network config.

sylvain



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#212921: cdebconf: Merge in new translations in templates

[Petter Reinholdtsen]

[Denis Barbier]
> Ack.

Very good.  This make it possible to add extra translations by adding
packages to the CD and listing them in the udeb_include file. :)

Now we just need to start using this feature. :)

> The current behaviour should certainly still be the default, so I
> added a --merge command-line flag to debconf-loadtemplate.

I'm unable to come up with any sensible scenario where one want to
keep the current behaviour.

If the database contain foo and foo-ll, and then is loaed with
identical foo and only foo-nl, I see no reason to throw away foo-ll.
Do you?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#212921: cdebconf: Merge in new translations in templates

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 212921 + pending
Bug#212921: cdebconf: Merge in new translations in templates
Tags were: d-i
Tags added: pending

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: remove speakup

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 239385 pending
Bug#239385: speakup keymap does not work in d-i
Tags were: d-i moreinfo
Tags added: pending

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#212921: cdebconf: Merge in new translations in templates

[Denis Barbier]

tags 212921 + pending
thanks

On Sat, Apr 03, 2004 at 04:30:44PM +0200, Petter Reinholdtsen wrote:
> [Denis Barbier]
> > I do not understand, debconf-loadtemplate already allows this, what
> > else do you need?
> 
> As far as I know, it will _replace_ the existing translations, not
> just add new ones.
> 
> That means that if you have template 'foo' with translations 'foo-es',
> and then load a new template file with template 'foo' and translation
> 'foo-nb', the 'foo-es' translation is dropped.  I want the database at
> that point to contain both 'foo', 'foo-es' and 'foo-nb'.

Ack.
The current behaviour should certainly still be the default, so
I added a --merge command-line flag to debconf-loadtemplate.

Denis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

replaceable

[ypjpx]

Bourgeois +


The cablefilterz will allow 
you to receive all the channels that
you order with your remote control"

payperviews,aXXXmovies,sport events,special-events\

http://www.8004hosting.com/cable/

toy,the secretary turned.

Re: Re: Must debian-installer use iso-codes package when choosing country?

[Alastair McKinstry]

DÃ Domh, 2004-04-04 ag 04:17 +0800, scrÃobh Tetralet:

> My original question is:
> 
> "Must debian-installer use "iso-codes" package when choosing country,
> Even though it will hurt some people, like people who living in Taiwan?"
> 
> And I think your answer is "YES".

> People who install Debian via debian-installer will find that "Taiwan" 
> was replaced with "Taiwan, Province of China".
> They may not detect immediately that this country code is based on ISO-3166,
> But they will think that Debian is discriminating against Taiwan people.
> It will not be a very good first impression to Debian users.

As has been noted in previous discussions on this subject, it is
basically impossible to draw up a list of countries and their names that
does not insult somebody. For Debian, picking an official list, (and
ISO-3166 is _the_ offfical list) is pretty much the only solution.

Please update the zh_TW entries, as discussed before. D-I is designed
that the first question people see is the Language; if they pick zh_CN
they should _not_see  Province_of_China.

Regards,
Alastair

> 
> Tetralet
> 
> 
> ==
>  ~2UUA{150U
>  http://edm-prg.epaper.com.tw/click.php?ad_code=87098
> ==
>  PChome~~ \*^o^*//
>  http://love.pchome.com.tw/
> ==
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

-- 

debian-installer: how much memory is needed (on other archs than i386) ?

[Holger Levsen]

Hello,

from the beta2 announcement: "Support for systems with only 32 MB of memory 
(i386 only)." anybody ot an idea what the requirements for other archs (e.g. 
powerpc) are ? I guess they should be roughly the same ?

The lowest I tested was 48mb which seemed fine.


regards,
Holger


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Re: Must debian-installer use iso-codes package when choosing country?

[Steve Langasek]

On Sun, Apr 04, 2004 at 04:17:05AM +0800, Tetralet wrote:

> "Must debian-installer use "iso-codes" package when choosing country,
> Even though it will hurt some people, like people who living in Taiwan?"

> And I think your answer is "YES".

> We, the debian users in Taiwan, Hongkong and mainland China, have 
> discussed about this for several days.
> You may visit http://moto.debian.org.tw/viewtopic.php?t=3192 for more 
> details.

> We all consent that to replace "Taiwan" with "Taiwan, Province of China" 
> is not suitable.
> It don't match to the real political situation,
> And it will bring a mountain of political disputes.

> People who install Debian via debian-installer will find that "Taiwan" 
> was replaced with "Taiwan, Province of China".
> They may not detect immediately that this country code is based on ISO-3166,
> But they will think that Debian is discriminating against Taiwan people.
> It will not be a very good first impression to Debian users.

Will these users be installing using English or Traditional Chinese as
the language?

-- 
Steve Langasek
postmodern programmer


signature.asc
Description: Digital signature

Re: Re: Must debian-installer use iso-codes package when choosing country?

[Tetralet]

My original question is:

"Must debian-installer use "iso-codes" package when choosing country,
Even though it will hurt some people, like people who living in Taiwan?"
And I think your answer is "YES".

We, the debian users in Taiwan, Hongkong and mainland China, have 
discussed about this for several days.
You may visit http://moto.debian.org.tw/viewtopic.php?t=3192 for more 
details.

We all consent that to replace "Taiwan" with "Taiwan, Province of China" 
is not suitable.
It don't match to the real political situation,
And it will bring a mountain of political disputes.

People who install Debian via debian-installer will find that "Taiwan" 
was replaced with "Taiwan, Province of China".
They may not detect immediately that this country code is based on ISO-3166,
But they will think that Debian is discriminating against Taiwan people.
It will not be a very good first impression to Debian users.

And, It is a gross disparagement to Taiwan people.
Thus some of us may refuse to use Debian anymore.
Sorry, but I think it is necessary to repeat again,
I suggest that debian-installer should not use the data form "iso-codes" 
package as country code.
We should try to found something else to replace the "iso-codes" package 
in debian-installer.

Tetralet

==
¤ëÁ~2¸U¶U§A²{ª÷150¸U
http://edm-prg.epaper.com.tw/click.php?ad_code=87098
==
PChome¥æ¤Í~~©¯ºÖ¤Ñ¤Ñ¦³ \*^o^*//
http://love.pchome.com.tw/
==
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241932: New installer don't allow to choose ftp as install source

[Klaus Ethgen]

-BEGIN PGP SIGNED MESSAGE-

Package: boot-floppies
Severity: important

In the new installer it is not possible to choose ftp as install source.
(minimal install CD Beta 3 from
http://gluck.debian.org/cdimage/testing/sarge_d-i/i386/beta3/sarge-i386-businesscard.iso)

For some reasons I'm not able to install over http. So I need ftp to do
so. Unlike it is a bad habit this days to transfer files over http which
is like word documents in mails or such think. (Yes, it works. but that
do not means to do it in any case.)

Regards
   Klaus
- -- 
Klaus Ethgenhttp://www.ethgen.de/
pub  2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <[EMAIL PROTECTED]>
Fingerprint: D7 67 71 C4 99 A6 D4 FE  EA 40 30 57 3C 88 26 2B
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iQEVAwUBQG8Xcp+OKpjRpO3lAQFsRgf/ac+6z/xp+c99VycOd68HWGlqanLQpyOT
JAWZmOWGJZh67bYW4Xf+blNoBoP+2kIA9jOhjAy7aj5ANODGCdq2KaQRExaEb5X2
9ExSyy2GDbNlf6qj6OIEb7JkOsIm2NXAysSeWDlnq0AzpGFtjQ2D/FPQU/XHupz4
eu1qm7zaN3DmBFCys7a87dlG18KkMp/yBrbvHa80w2Ldxd0rEqj+POIDB8JwaRtA
GMa5g6T+b0pCYscjiybSIFGocRkHeJe6EJTNQ7e5AZ9pWHakdpIl3X0f4nNZ/+2J
Qb3E2LXljsDx218YG8KbzAf/rK9a+Sz/imOHlWgH4dZYOY/t7ttAjw==
=EmGj
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

linux-kernel-di-arm_0.53_arm.changes ACCEPTED

[Debian Installer]

Accepted:
cdrom-core-modules-2.4.25-bast-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/cdrom-core-modules-2.4.25-bast-di_0.53_arm.udeb
cdrom-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/cdrom-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
ext3-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/ext3-modules-2.4.25-netwinder-di_0.53_arm.udeb
ext3-modules-2.4.25-riscpc-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/ext3-modules-2.4.25-riscpc-di_0.53_arm.udeb
ext3-modules-2.4.25-riscstation-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/ext3-modules-2.4.25-riscstation-di_0.53_arm.udeb
fat-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/fat-modules-2.4.25-netwinder-di_0.53_arm.udeb
fat-modules-2.4.25-riscpc-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/fat-modules-2.4.25-riscpc-di_0.53_arm.udeb
fat-modules-2.4.25-riscstation-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/fat-modules-2.4.25-riscstation-di_0.53_arm.udeb
isa-pnp-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/isa-pnp-modules-2.4.25-netwinder-di_0.53_arm.udeb
kernel-image-2.4.25-bast-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-bast-di_0.53_arm.udeb
kernel-image-2.4.25-lart-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-lart-di_0.53_arm.udeb
kernel-image-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-netwinder-di_0.53_arm.udeb
kernel-image-2.4.25-riscpc-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-riscpc-di_0.53_arm.udeb
kernel-image-2.4.25-riscstation-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-riscstation-di_0.53_arm.udeb
linux-kernel-di-arm_0.53.dsc
  to pool/main/l/linux-kernel-di-arm/linux-kernel-di-arm_0.53.dsc
linux-kernel-di-arm_0.53.tar.gz
  to pool/main/l/linux-kernel-di-arm/linux-kernel-di-arm_0.53.tar.gz
loop-modules-2.4.25-bast-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/loop-modules-2.4.25-bast-di_0.53_arm.udeb
loop-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/loop-modules-2.4.25-netwinder-di_0.53_arm.udeb
loop-modules-2.4.25-riscpc-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/loop-modules-2.4.25-riscpc-di_0.53_arm.udeb
nic-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/nic-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
nic-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/nic-modules-2.4.25-netwinder-di_0.53_arm.udeb
nic-shared-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/nic-shared-modules-2.4.25-netwinder-di_0.53_arm.udeb
scsi-common-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/scsi-common-modules-2.4.25-netwinder-di_0.53_arm.udeb
scsi-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/scsi-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
scsi-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/scsi-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
scsi-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/scsi-modules-2.4.25-netwinder-di_0.53_arm.udeb
socket-modules-2.4.25-bast-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/socket-modules-2.4.25-bast-di_0.53_arm.udeb
socket-modules-2.4.25-lart-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/socket-modules-2.4.25-lart-di_0.53_arm.udeb
socket-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/socket-modules-2.4.25-netwinder-di_0.53_arm.udeb
socket-modules-2.4.25-riscpc-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/socket-modules-2.4.25-riscpc-di_0.53_arm.udeb
socket-modules-2.4.25-riscstation-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/socket-modules-2.4.25-riscstation-di_0.53_arm.udeb
usb-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/usb-modules-2.4.25-netwinder-di_0.53_arm.udeb
Announcing to [EMAIL PROTECTED]


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241817: install: does not create yaboot partition

[Joey Hess]

Sven Luther wrote:
> The idea is that some hardware configurations needs some particular
> partitions to be there (like a prep boot partition or a palo boot
> partition, or the yaboot boot partition on pmac), or even some
> filesystem to be used for the /boot partition (like affs on pegasos 1).

Notice that there already exists a partman-palo package to do this for
hppa. You just need to make some kind of partman-yaboot, I suppose.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: loop device install or how to skip partman ?

[Joey Hess]

Bill Allombert wrote:
> Hello Debian-installer team,
> 
> After testing beta 1 and beta 2, I tried beta 3, with the 
> same goal in mind: install Debian in a file using a loop
> device.
> 
> As far as I could see, all beta detected the hardware of
> the box fine.
> 
> beta 1 and 2 lacked the minimal support to create loop device,
> but the situation has improved : now there is a 'dd' utility and 'mount'
> support '-oloop' provide we issue modprobe loop before calling mount
> (which I found a bit confusing, it would be better if the module was
> autoloaded, but never mind). There is no 'losetup' but it is probably not
> neccessary.

Sounds like you have all the pieces you need to write a partman-loop
module that adds loopback support directly to partman.
 
> Now, the problem is that I can't find any way to skip the 'partman'
> step of d-i. b-f conveniently detected that /target existed and 
> allow to go to 'install base system' directly.

Just mount /target, edit /var/lib/dpkg/status to mark partman as already
configured, and skip over it in the menu.

> The 'expert mode' modules selection suffers from a usability problem:
> usually it is easier to select the module we need that the modules we do
> not need.

AFAIK it only has this problem with hardware that discover cannot probe.

-- 
see shy jo


signature.asc
Description: Digital signature

linux-kernel-di-arm_0.53_arm.changes is NEW

[Debian Installer]

cdrom-core-modules-2.4.25-bast-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/cdrom-core-modules-2.4.25-bast-di_0.53_arm.udeb
cdrom-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/cdrom-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
ext3-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/ext3-modules-2.4.25-netwinder-di_0.53_arm.udeb
ext3-modules-2.4.25-riscpc-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/ext3-modules-2.4.25-riscpc-di_0.53_arm.udeb
ext3-modules-2.4.25-riscstation-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/ext3-modules-2.4.25-riscstation-di_0.53_arm.udeb
fat-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/fat-modules-2.4.25-netwinder-di_0.53_arm.udeb
fat-modules-2.4.25-riscpc-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/fat-modules-2.4.25-riscpc-di_0.53_arm.udeb
fat-modules-2.4.25-riscstation-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/fat-modules-2.4.25-riscstation-di_0.53_arm.udeb
isa-pnp-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/isa-pnp-modules-2.4.25-netwinder-di_0.53_arm.udeb
kernel-image-2.4.25-bast-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-bast-di_0.53_arm.udeb
kernel-image-2.4.25-lart-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-lart-di_0.53_arm.udeb
kernel-image-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-netwinder-di_0.53_arm.udeb
kernel-image-2.4.25-riscpc-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-riscpc-di_0.53_arm.udeb
kernel-image-2.4.25-riscstation-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/kernel-image-2.4.25-riscstation-di_0.53_arm.udeb
linux-kernel-di-arm_0.53.dsc
  to pool/main/l/linux-kernel-di-arm/linux-kernel-di-arm_0.53.dsc
linux-kernel-di-arm_0.53.tar.gz
  to pool/main/l/linux-kernel-di-arm/linux-kernel-di-arm_0.53.tar.gz
loop-modules-2.4.25-bast-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/loop-modules-2.4.25-bast-di_0.53_arm.udeb
loop-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/loop-modules-2.4.25-netwinder-di_0.53_arm.udeb
loop-modules-2.4.25-riscpc-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/loop-modules-2.4.25-riscpc-di_0.53_arm.udeb
nic-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/nic-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
nic-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/nic-modules-2.4.25-netwinder-di_0.53_arm.udeb
nic-shared-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/nic-shared-modules-2.4.25-netwinder-di_0.53_arm.udeb
scsi-common-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/scsi-common-modules-2.4.25-netwinder-di_0.53_arm.udeb
scsi-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/scsi-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
scsi-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to 
pool/main/l/linux-kernel-di-arm/scsi-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
scsi-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/scsi-modules-2.4.25-netwinder-di_0.53_arm.udeb
(new) socket-modules-2.4.25-bast-di_0.53_arm.udeb extra debian-installer
Socket drivers
 This package contains the packet socket driver, used by dhcp and other
 things that need raw network device access. It also contains the UNIX
 domain socket driver.
(new) socket-modules-2.4.25-lart-di_0.53_arm.udeb extra debian-installer
Socket drivers
 This package contains the packet socket driver, used by dhcp and other
 things that need raw network device access. It also contains the UNIX
 domain socket driver.
(new) socket-modules-2.4.25-netwinder-di_0.53_arm.udeb extra debian-installer
Socket drivers
 This package contains the packet socket driver, used by dhcp and other
 things that need raw network device access. It also contains the UNIX
 domain socket driver.
(new) socket-modules-2.4.25-riscpc-di_0.53_arm.udeb extra debian-installer
Socket drivers
 This package contains the packet socket driver, used by dhcp and other
 things that need raw network device access. It also contains the UNIX
 domain socket driver.
(new) socket-modules-2.4.25-riscstation-di_0.53_arm.udeb extra debian-installer
Socket drivers
 This package contains the packet socket driver, used by dhcp and other
 things that need raw network device access. It also contains the UNIX
 domain socket driver.
usb-modules-2.4.25-netwinder-di_0.53_arm.udeb
  to pool/main/l/linux-kernel-di-arm/usb-modules-2.4.25-netwinder-di_0.53_arm.udeb
Changes: linux-kernel-di-arm (0.53) unstable; urgency=low
 .
  * Joey Hess
- Fix up path to kernel-wedge rules file.
  * Vincent Sanders
- Fix kernel dependancies
- Add missing socket module builds
An

Re: base-installer_0.066_powerpc.changes ACCEPTED

[Joey Hess]

Sven Luther wrote:
> > /build/build/cdebconf-0.58/src/debconf.c:115 (main): Error reading 
> > configuration information
> > /build/build/cdebconf-0.58/src/debconf-loadtemplate.c:68 (main): Error reading 
> > configuration information
> 
> Ok, this seems broken today, i have had three reports about this.

Cdebconf was recently broken to not include /etc/cdebconf.conf. This was
fixed in version 0.59, released on April 1.

-- 
see shy jo


signature.asc
Description: Digital signature

Processing of linux-kernel-di-arm_0.53_arm.changes

[Archive Administrator]

linux-kernel-di-arm_0.53_arm.changes uploaded successfully to localhost
along with the files:
  linux-kernel-di-arm_0.53.dsc
  linux-kernel-di-arm_0.53.tar.gz
  kernel-image-2.4.25-netwinder-di_0.53_arm.udeb
  nic-modules-2.4.25-netwinder-di_0.53_arm.udeb
  nic-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
  nic-shared-modules-2.4.25-netwinder-di_0.53_arm.udeb
  isa-pnp-modules-2.4.25-netwinder-di_0.53_arm.udeb
  socket-modules-2.4.25-netwinder-di_0.53_arm.udeb
  cdrom-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
  scsi-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
  scsi-modules-2.4.25-netwinder-di_0.53_arm.udeb
  scsi-common-modules-2.4.25-netwinder-di_0.53_arm.udeb
  scsi-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
  loop-modules-2.4.25-netwinder-di_0.53_arm.udeb
  ext3-modules-2.4.25-netwinder-di_0.53_arm.udeb
  fat-modules-2.4.25-netwinder-di_0.53_arm.udeb
  usb-modules-2.4.25-netwinder-di_0.53_arm.udeb
  kernel-image-2.4.25-bast-di_0.53_arm.udeb
  socket-modules-2.4.25-bast-di_0.53_arm.udeb
  cdrom-core-modules-2.4.25-bast-di_0.53_arm.udeb
  loop-modules-2.4.25-bast-di_0.53_arm.udeb
  kernel-image-2.4.25-riscpc-di_0.53_arm.udeb
  socket-modules-2.4.25-riscpc-di_0.53_arm.udeb
  loop-modules-2.4.25-riscpc-di_0.53_arm.udeb
  ext3-modules-2.4.25-riscpc-di_0.53_arm.udeb
  fat-modules-2.4.25-riscpc-di_0.53_arm.udeb
  kernel-image-2.4.25-riscstation-di_0.53_arm.udeb
  socket-modules-2.4.25-riscstation-di_0.53_arm.udeb
  ext3-modules-2.4.25-riscstation-di_0.53_arm.udeb
  fat-modules-2.4.25-riscstation-di_0.53_arm.udeb
  kernel-image-2.4.25-lart-di_0.53_arm.udeb
  socket-modules-2.4.25-lart-di_0.53_arm.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

linux-kernel-di-arm_0.53_arm.changes REJECTED

[Debian Installer]

Rejected: socket-modules-2.4.25-lart-di_0.53_arm.udeb: has 1 file(s) with a time stamp 
too far into the future (e.g. control [Tue Sep 14 16:33:50 2004]).
Rejected: cdrom-core-modules-2.4.25-bast-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:30:46 2004]).
Rejected: scsi-core-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a 
time stamp too far into the future (e.g. control [Tue Sep 14 16:28:08 2004]).
Rejected: scsi-common-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a 
time stamp too far into the future (e.g. control [Tue Sep 14 16:28:41 2004]).
Rejected: socket-modules-2.4.25-bast-di_0.53_arm.udeb: has 1 file(s) with a time stamp 
too far into the future (e.g. control [Tue Sep 14 16:30:30 2004]).
Rejected: loop-modules-2.4.25-bast-di_0.53_arm.udeb: has 1 file(s) with a time stamp 
too far into the future (e.g. control [Tue Sep 14 16:31:02 2004]).
Rejected: ext3-modules-2.4.25-riscstation-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:33:04 2004]).
Rejected: fat-modules-2.4.25-riscpc-di_0.53_arm.udeb: has 1 file(s) with a time stamp 
too far into the future (e.g. control [Tue Sep 14 16:32:19 2004]).
Rejected: nic-shared-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a 
time stamp too far into the future (e.g. control [Tue Sep 14 16:27:05 2004]).
Rejected: scsi-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:28:24 2004]).
Rejected: fat-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:29:44 2004]).
Rejected: nic-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:26:34 2004]).
Rejected: isa-pnp-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:27:21 2004]).
Rejected: scsi-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a 
time stamp too far into the future (e.g. control [Tue Sep 14 16:28:56 2004]).
Rejected: ext3-modules-2.4.25-riscpc-di_0.53_arm.udeb: has 1 file(s) with a time stamp 
too far into the future (e.g. control [Tue Sep 14 16:32:04 2004]).
Rejected: kernel-image-2.4.25-riscpc-di_0.53_arm.udeb: has 3 file(s) with a time stamp 
too far into the future (e.g. boot/System.map-2.4.25-riscpc [Tue Sep 14 16:24:00 
2004]).
Rejected: socket-modules-2.4.25-riscstation-di_0.53_arm.udeb: has 1 file(s) with a 
time stamp too far into the future (e.g. control [Tue Sep 14 16:32:48 2004]).
Rejected: nic-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a 
time stamp too far into the future (e.g. control [Tue Sep 14 16:26:50 2004]).
Rejected: socket-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:27:37 2004]).
Rejected: loop-modules-2.4.25-riscpc-di_0.53_arm.udeb: has 1 file(s) with a time stamp 
too far into the future (e.g. control [Tue Sep 14 16:31:50 2004]).
Rejected: loop-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:29:12 2004]).
Rejected: usb-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:29:59 2004]).
Rejected: fat-modules-2.4.25-riscstation-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:33:20 2004]).
Rejected: socket-modules-2.4.25-riscpc-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:31:34 2004]).
Rejected: ext3-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:29:27 2004]).
Rejected: cdrom-core-modules-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a 
time stamp too far into the future (e.g. control [Tue Sep 14 16:27:52 2004]).
Rejected: kernel-image-2.4.25-riscstation-di_0.53_arm.udeb: has 2 file(s) with a time 
stamp too far into the future (e.g. boot/System.map-2.4.25-riscstation [Tue Sep 14 
16:24:18 2004]).
Rejected: kernel-image-2.4.25-netwinder-di_0.53_arm.udeb: has 1 file(s) with a time 
stamp too far into the future (e.g. control [Tue Sep 14 16:26:19 2004]).
Rejected: kernel-image-2.4.25-bast-di_0.53_arm.udeb: has 1 file(s) with a time stamp 
too far into the future (e.g. control [Tue Sep 14 16:30:14 2004]).
Rejected: kernel-image-2.4.25-lart-di_0.53_arm.udeb: has 3 file(s) with a time stamp 
too far into the future (e.g. boot/System.map-2.4.25-lart [Tue Sep 14 16:24:33 2004]).


===

If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi

Bug#238228: FTBFS: setgid DEBIAN directory

[Steve McIntyre]

On Sat, Apr 03, 2004 at 05:42:22PM +0100, Steve McIntyre wrote:
>
>Matt,
>
>I can't find anything wrong with this package - it builds just fine
>and the debian/ dir is not setgid in the .tar.gz. Can you check this
>again?

Gah, f*cked up looking at the package - it _does_ have the setgid dirs
that you listed. But nonetheless running dpkg-buildpackage and
pdebuild here don't show any problems actually building the
package. Am I missing something here?

-- 
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
Welcome my son, welcome to the machine.


pgp0.pgp
Description: PGP signature

Bug#238228: FTBFS: setgid DEBIAN directory

[Petter Reinholdtsen]

[Steve McIntyre]
> I can't find anything wrong with this package - it builds just fine
> and the debian/ dir is not setgid in the .tar.gz. Can you check this
> again?

Why not just call 'dh_fixperms' in rules to avoid the problem
completely?


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

loop device install or how to skip partman ?

[Bill Allombert]

Hello Debian-installer team,

After testing beta 1 and beta 2, I tried beta 3, with the 
same goal in mind: install Debian in a file using a loop
device.

As far as I could see, all beta detected the hardware of
the box fine.

beta 1 and 2 lacked the minimal support to create loop device,
but the situation has improved : now there is a 'dd' utility and 'mount'
support '-oloop' provide we issue modprobe loop before calling mount
(which I found a bit confusing, it would be better if the module was
autoloaded, but never mind). There is no 'losetup' but it is probably not
neccessary.

Now, the problem is that I can't find any way to skip the 'partman'
step of d-i. b-f conveniently detected that /target existed and 
allow to go to 'install base system' directly.

So I have not yet be able to complete the installation this time!

Anyway, for all I can see, beta 3 is a huge improvement over beta 2.

The 'expert mode' modules selection suffers from a usability problem:
usually it is easier to select the module we need that the modules we do
not need.

Cheers,
-- 
Bill. <[EMAIL PROTECTED]>

Imagine a large red swirl here. 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: FTBFS: setgid DEBIAN directory

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 238228 normal
Bug#238228: FTBFS: setgid DEBIAN directory
Severity set to `normal'.

> tags 238228 +wontfix +unreproducible
Unknown tag/s: +unreproducible.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid help 
security upstream pending sarge sarge-ignore experimental d-i confirmed ipv6 lfs 
fixed-in-experimental fixed-upstream l10n.

Bug#238228: FTBFS: setgid DEBIAN directory
There were no tags set.
Tags added: wontfix

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processing of linux-kernel-di-arm_0.53_arm.changes

[Archive Administrator]

linux-kernel-di-arm_0.53_arm.changes uploaded successfully to localhost
along with the files:
  linux-kernel-di-arm_0.53.dsc
  linux-kernel-di-arm_0.53.tar.gz
  kernel-image-2.4.25-netwinder-di_0.53_arm.udeb
  nic-modules-2.4.25-netwinder-di_0.53_arm.udeb
  nic-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
  nic-shared-modules-2.4.25-netwinder-di_0.53_arm.udeb
  isa-pnp-modules-2.4.25-netwinder-di_0.53_arm.udeb
  socket-modules-2.4.25-netwinder-di_0.53_arm.udeb
  cdrom-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
  scsi-core-modules-2.4.25-netwinder-di_0.53_arm.udeb
  scsi-modules-2.4.25-netwinder-di_0.53_arm.udeb
  scsi-common-modules-2.4.25-netwinder-di_0.53_arm.udeb
  scsi-extra-modules-2.4.25-netwinder-di_0.53_arm.udeb
  loop-modules-2.4.25-netwinder-di_0.53_arm.udeb
  ext3-modules-2.4.25-netwinder-di_0.53_arm.udeb
  fat-modules-2.4.25-netwinder-di_0.53_arm.udeb
  usb-modules-2.4.25-netwinder-di_0.53_arm.udeb
  kernel-image-2.4.25-bast-di_0.53_arm.udeb
  socket-modules-2.4.25-bast-di_0.53_arm.udeb
  cdrom-core-modules-2.4.25-bast-di_0.53_arm.udeb
  loop-modules-2.4.25-bast-di_0.53_arm.udeb
  kernel-image-2.4.25-riscpc-di_0.53_arm.udeb
  socket-modules-2.4.25-riscpc-di_0.53_arm.udeb
  loop-modules-2.4.25-riscpc-di_0.53_arm.udeb
  ext3-modules-2.4.25-riscpc-di_0.53_arm.udeb
  fat-modules-2.4.25-riscpc-di_0.53_arm.udeb
  kernel-image-2.4.25-riscstation-di_0.53_arm.udeb
  socket-modules-2.4.25-riscstation-di_0.53_arm.udeb
  ext3-modules-2.4.25-riscstation-di_0.53_arm.udeb
  fat-modules-2.4.25-riscstation-di_0.53_arm.udeb
  kernel-image-2.4.25-lart-di_0.53_arm.udeb
  socket-modules-2.4.25-lart-di_0.53_arm.udeb

Greetings,

Your Debian queue daemon


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#238228: FTBFS: setgid DEBIAN directory

[Steve McIntyre]

severity 238228 normal
tags 238228 +wontfix +unreproducible
thanks

Matt,

I can't find anything wrong with this package - it builds just fine
and the debian/ dir is not setgid in the .tar.gz. Can you check this
again?

-- 
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
We don't need no education.
We don't need no thought control.


pgp0.pgp
Description: PGP signature

Re: speakup and debian-installer

[Mario Lang]

"Alastair McKinstry" <[EMAIL PROTECTED]> writes:

> I'm the kbd-chooser maintainer for the new Debian Installer.
> I'm working on bug #239385, which appears to have problems
> with kbd-chooser and console-tools due to speakup not
> being installed; from looking at the code it appears that
> for the speakup keymaps to work, you need a speakup-patched
> kernel; is this the case?

Yes, and no.  As far as I can see, speakup only required a special console
keymap up until recently.  The patch and kernel-image packages of
speakup currently in sid/sarge do no longer require a special speakup keymap.
Actually, to tell the truth, I have no idea why the keymap is in there
at all.

> In which case, why are the speakup patches not in the
> mainline Debian kernels

Well, I'd certainly like that, but it is a quite intrusive patch, which
is probably not really suitable for default inclusion.

> d-i uses a default kernel for each architecture; it may then install onto the
> system an optimised kernel for that particular machine. So, it
> appears:
>
> (1) For speakup to work in the installer, we need to use a kerne-image-*-speakup
> image. (Other than the speakup patches, how does this differ from the normal
> i386 images?)

The current state of things is that we have *one* generic
kernel-image-VERSION-speakup package.  Building packages for all arch flavours
is way too much overkill right now.  A user who uses the access flavour should
ideally have a choice of which kernel she wants to install in the target
system.  Speakup users would choose the speakup variant to not loose speech
after reboot, and people who do not require speakup (but use a braille
display for instance) would be free to install an optimized kernel
if they want.

> (2) If the kernel is not speakup-patched, how do we detect this in
> kbd-chooser (the system map will not be shipped in d-i)?  Does it
> make more sense just to not offer speakup in kbd-chooser, or ship a
> speakup-variant of d-i with speakup kernel and keymap?
Well, we have a speakup variant of d-i already (the access floppy).
And I'd say kbd-chooser doesn't need to ship a speakup keymap at all.
At least not since speakup does its review mappings internally now.

-- 
CYa,
  Mario | Debian Developer http://debian.org/>
| Get my public key via finger [EMAIL PROTECTED]
| 1024D/7FC1A0854909BCCDBE6C102DDFFC022A6B113E44


pgp0.pgp
Description: PGP signature

Processed: Re: Bug#241847: 3rd of April, daily build powerpc-small root floppy broken

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 241847 grave
Bug#241847: 3rd of April, daily build powerpc-small root floppy broken
Severity set to `grave'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241847: 3rd of April, daily build powerpc-small root floppy broken

[Sven Luther]

severity 241847 grave
thanks
On Sat, Apr 03, 2004 at 01:48:09PM +0200, Holger Levsen wrote:
> Package: debian-installer
> 
> floppy images from 
> http://people.debian.org/~luther/debian-installer/daily-powerpc-built/current/powerpc-small/floppy/
>  
> at 2004-04-03, 10:00:00 CEST 2004
> 
> Since I couldn't get a working boot floppy from these images (no idea whether 
> the image is broken or I had just bad luck with 20 tries and 8 floppies) I 
> used my old boot floppy from 2004-03-26? from Jeremie König and a new root 
> floppy made from the above source.
> 
> The root-floppy gets loaded, it starts but almost 
> instantly hangs with:
> 
> /build/build/cdebconf-0.58/src/debconf.c:115 (main): Error reading 
> configuration information
> /build/build/cdebconf-0.58/src/debconf-loadtemplate.c:68 (main): Error reading 
> configuration information
> 
> (I also tried three different boot-floppies, the same error. (As expected as 
> they're read ok and load into ramdisk fine.)
> 
> So I guess, the root floppy images are broken :(

For info, this is not the only case, so i suppose that debian-installer
is currently broken. I have had a report on pegasos for this, and just
saw Arturo report the same thing on irc on his x86 box.

You can try the just uploading version of the root floppy (2004.04.03),
or an earlier one (2004.03.31 for example).

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: base-installer_0.066_powerpc.changes ACCEPTED

[Sven Luther]

On Sat, Apr 03, 2004 at 11:29:28AM +0200, Holger Levsen wrote:
> Good Morning ;)
> 
> by looking at the changelog I found that you fixed the kernel install problem 
> and this morning I found some new images at 
> http://people.debian.org/~luther/debian-installer/daily-powerpc-built/current/powerpc-small/floppy/
>  
> 
> I tried to write the root.img on about 10 different floppies, twice, and 
> bootet them without any succes. The disks read fine, the mac-tux logo turns 
> black and the systems freezes. Is it possible that the root.img is broken or 
> had I just very bad luck with floppies ?
> 
> Anyhow, I realized I could use the "old" root-floppy from Jeremie and an new 
> boot-floppy. (I wrote the image on the same floppies I tried with the 
> root-image, and the floppy works.) The root-floppy gets loaded but almost 
> instantly hangs with:
> 
> /build/build/cdebconf-0.58/src/debconf.c:115 (main): Error reading 
> configuration information
> /build/build/cdebconf-0.58/src/debconf-loadtemplate.c:68 (main): Error reading 
> configuration information

Ok, this seems broken today, i have had three reports about this.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#212921: cdebconf: Merge in new translations in templates

[Petter Reinholdtsen]

[Denis Barbier]
> I do not understand, debconf-loadtemplate already allows this, what
> else do you need?

As far as I know, it will _replace_ the existing translations, not
just add new ones.

That means that if you have template 'foo' with translations 'foo-es',
and then load a new template file with template 'foo' and translation
'foo-nb', the 'foo-es' translation is dropped.  I want the database at
that point to contain both 'foo', 'foo-es' and 'foo-nb'.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#212921: cdebconf: Merge in new translations in templates

[Denis Barbier]

On Fri, Sep 26, 2003 at 11:57:45PM +0200, Petter Reinholdtsen wrote:
> 
> Package: cdebconf 
> Version: 0.42
> 
> We should modify cdebconf to do a compare of the English text and
> merge when loading new templates. This is to support add-on modules
> that may contain a complete translation for a given language, detached
> from the modules that are translated.
> 
> If the English text differ, the new template should replace the old
> one.

I do not understand, debconf-loadtemplate already allows this, what
else do you need?

Denis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Trying to build debian-installer on amd64.

[Kurt Roeckx]

On Fri, Apr 02, 2004 at 11:45:12PM -0500, Joey Hess wrote:
> That's the problem, you need the current version in subversion, or at
> least version 20040331.

Everything seems to be building except for those 3:
build_floppy_boot, build_floppy_root, build_floppy_access

They all fail with "Disk full"

For boot I have those files:
-rw-r--r--1 root root   863450 Apr  1 22:21 vmlinuz
-rw-r--r--1 root root   948875 Apr  3 16:07 initrd.gz

For root:
-rw-r--r--1 root root  2012982 Apr  3 15:53 initrd.gz

and for access:
-rw-r--r--1 root root  1827645 Apr  3 16:08 initrd.gz

What should I do to make them smaller?


Kurt


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#239761: debian-installer: also with pcnet32 module (vmware)

[Stephen Stafford]

Package: debian-installer
Version: N/A; reported 2004-04-03
Followup-For: Bug #239761

Hi,

After a seamless and really quite impressive boot from the
sarge-i386-businesscard.iso (marred only by it failing to run the GUI
installer and so falling back on textmode...not surprising given it's
vmware), the pcnet32 module fails to load, hence the network fails to come
up.  This after it all being autodetected when booting from the iso.

This is even stranger given that the output of "dmesg" shows that the module
WAS loaded at boot.  Something somewhere removed it again.

Still, the whole thing looks pretty slick, I'm quietly impressed

Cheers,
Stephen

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux yaffle 2.6.3 #1 Sat Mar 6 15:13:58 GMT 2004 i686
Locale: LANG=C, LC_CTYPE=C



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241850: installation-reports PPC

[Ronald Gravelle]

Package: installation-reports

Debian-installer-version: 

uname -a: 
Date: 
Method: 

Machine: 
Processor:233mhz PPC G3
Memory:160 megs
Root Device: 
Root Size/partition table: 
Output of lspci:

Base System Installation Checklist:

Initial boot worked:[ O ]
Configure network HW:   [ O ]
Config network: [ E ]
Detect CD:  [ O ]
Load installer modules: [ O ]
Detect hard drives: [ O ]
Partition hard drives:  [ O ]
Create file systems:[ O ]
Mount partitions:   [ O ]
Install base system:[ O ]
Install boot loader:[ O ]
Reboot: [ O ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Comments/Problems: The only installer problem was the network did not automaticallt 
set up DHCP, which worked in earlier versions, however manual set up worked fine.
The yaboot installer worked great, the partition finally created a proper bootstrap.

A side note, I have been trying the daily builds for a month, this days (03/31/04) has 
worked best for me, the 04/01/04 daily build gets stuck in a loop trying to modprobe 
when installing.

I have not tried the 04/02/04 daily, I am going to wait till the next major beta, 
unless I see no one else is doing much PPC testing.
Thanks again everyone for all their work I appreciate Debian very much.

Best
Ron Gravelle


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: New alioth repository for console-data, console-common

[Denis Barbier]

On Fri, Apr 02, 2004 at 12:19:12AM +0100, Alastair McKinstry wrote:
> Hi,
> 
> I have created new Alioth SVN repositories for the console-data and
> console-common packages. These contain debconf templates that are used
> as part of the 2nd stage installation.  Translators are welcome to
> commit additions and changes to the .po files included .
> 
> Anyone wanting access, please email me your alioth username; Debian
> developers should already have access, I believe.
> 
> They are available from svn.debian.org via svn , using
> 
>  svn import svn+ssh://[EMAIL PROTECTED]/svn/console-data
> ditto for console-common, etc
[...]

  $ svn co svn+ssh://svn.debian.org/svn/console-data
  svn: Berkeley DB error while opening environment for filesystem
  /svn/console-common/db:
  Permission denied

An anonymous access would also be very helpful.

Denis


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241256: I tested new test CD-image but cannot load builtin ethernet.

[Takushi Fujiwara]

My mailaddress changed.And Send report again.

I tested new image.But it does not work well.
I used image follows.
http://people.debian.org/cdimage/testing/daily/powerpc/20040331/sarge-powerpc-netinst.iso
Hardware detected but cannot load module "sungem(Apple Computer Inc.
Uninorth/Pangea GMAC).Why builtin ethernet module is not loaded?
How can I gather debug information?
I also tested new Image follows.
http://people.debian.org/cdimage/testing/daily/powerpc/20040401/sarge-powerpc-netinst.iso
Failed keyboad configuration.Message follows.
umount: /initrd:Invalid argument
/build/buildd/cdebconf-0.58/src/debconf-loadtemplate.c:68 (main):Error
configuration infomation
insmod: usb-ohci.o:no module by that name found
modprobe failed to load module usb-ohci
modprobe usbkk:no module by usb-kbd
insmod: keybdev.o:no module by that name found
modprobe failed to load module usb-kbd
Using /lib/modules/2.4.25-powerpc/kernel/usb/serial.o
/build/buildd/cdebconf-0.58/src/debconf.c:115 (main) Error reading
configuration information
insmod: usb-ohci.o:no module by that name found
modprobe failed to load module usb-ohci
modprobe usbkk:no module by usb-kbd
insmod: keybdev.o:no module by that name found
modprobe failed to load module usb-kbd
...
These message output endless.And cannot start Debian-Installer.
--
Takushi Fujiwara
mailto:[EMAIL PROTECTED]






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241847: 3rd of April, daily build powerpc-small root floppy broken

[Holger Levsen]

Package: debian-installer

floppy images from 
http://people.debian.org/~luther/debian-installer/daily-powerpc-built/current/powerpc-small/floppy/
 
at 2004-04-03, 10:00:00 CEST 2004

Since I couldn't get a working boot floppy from these images (no idea whether 
the image is broken or I had just bad luck with 20 tries and 8 floppies) I 
used my old boot floppy from 2004-03-26? from Jeremie König and a new root 
floppy made from the above source.

The root-floppy gets loaded, it starts but almost 
instantly hangs with:

/build/build/cdebconf-0.58/src/debconf.c:115 (main): Error reading 
configuration information
/build/build/cdebconf-0.58/src/debconf-loadtemplate.c:68 (main): Error reading 
configuration information

(I also tried three different boot-floppies, the same error. (As expected as 
they're read ok and load into ramdisk fine.)

So I guess, the root floppy images are broken :(


regards,
Holger

Re: base-installer_0.066_powerpc.changes ACCEPTED

[Sven Luther]

On Sat, Apr 03, 2004 at 01:38:15PM +0200, Holger Levsen wrote:
> Hi,
> 
> Am Samstag, 3. April 2004 12:09 schrieb Sven Luther:
> > Jeremie, any idea what is going on here ? Can you build a new image set
> > on your box, and have Holger test it ?
> 
> that would be nice...
> 
> > Could you try one of the older snapshots ? From :
> > http://people.debian.org/~luther/debian-installer/daily-powerpc-built/2004.
> >03.31/powerpc-small/floppy/
> > for example ?
> 
> but you fixed base-installer yesterday ?! (installs 
> kernel-image-2.4.25-power-pmac instead ...powerpc-pmac-small)

Ah, no, that has nothing to do with that. It is the second part, once
debian-installer has finished installing the base system, it will
install a kernel (to be used with quik or whatever), so you get a
working system. Nothing to do with your problem.

> > > I tried to write the root.img on about 10 different floppies, twice, and
> > > bootet them without any succes. The disks read fine, the mac-tux logo
> > > turns black and the systems freezes. Is it possible that the root.img is
> > > broken or had I just very bad luck with floppies ?
> 
> er..., I meant "is it possible that the _boot.img_ is broken ? (as well, see 
> below...)

Mmm.

> > Yeah, the boot.img should be mostly ok, since it is nothing more than
> > the kernel and the miboot stuff.
> 
> yeah, that's theoretics. but I tried 8 floppies (all new), writings them once 
> and reading (=booting) at least twice, none work. but after that, when I used 
> the old working boot floppy from jeremie, three of them worked as 
> root-floppies!

Can you use compare to compare the written floppy to the image used ? 

> but still, that could have been bad luck, that's why I asked here, I anybody 
> hat success booting that boot.img ?? (you, sven, have no access to mac 
> hardware with floppy, right ?)

I have no access to mac hardware of any kind :)

> > Maybe you could try loop mounting both root floppies, and compare them.
> 
> would that really make more sense than setting up d-i to build from svn ? 

Well, if the problem is with the root.img, knowing what the difference
between the working image and the bad one is, would be a good idea.

> there are at least five days in between the creation of the images, I expect 
> a lot to have changed.

Yeah, and packages used which are not in the debian-installer svn, and a
different box used, and ...

> > It would be nice to get some kind of log of what is happening ? No idea
> > how to achieve this though.
> 
> optional logging to some kind of loghost (via ssh and/or ftp) as part of d-i, 
> executed after the installation is finished or manually in case of an error.

Yeah, altough in your case, this will not help, since apparently the
system freezes before going to even boot debian-installer. What i want
is not the debian-installer log, but the kernel boot log. Usually
acquired by serial console (console=ttyS01,115200n8 console=tty0 on my
box) or by plain looking at the kernel log info on the screen (provided
there is such a thing.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: base-installer_0.066_powerpc.changes ACCEPTED

[Holger Levsen]

Hi,

Am Samstag, 3. April 2004 12:09 schrieb Sven Luther:
> Jeremie, any idea what is going on here ? Can you build a new image set
> on your box, and have Holger test it ?

that would be nice...

> Could you try one of the older snapshots ? From :
> http://people.debian.org/~luther/debian-installer/daily-powerpc-built/2004.
>03.31/powerpc-small/floppy/
> for example ?

but you fixed base-installer yesterday ?! (installs 
kernel-image-2.4.25-power-pmac instead ...powerpc-pmac-small)

> > I tried to write the root.img on about 10 different floppies, twice, and
> > bootet them without any succes. The disks read fine, the mac-tux logo
> > turns black and the systems freezes. Is it possible that the root.img is
> > broken or had I just very bad luck with floppies ?

er..., I meant "is it possible that the _boot.img_ is broken ? (as well, see 
below...)

> Yeah, the boot.img should be mostly ok, since it is nothing more than
> the kernel and the miboot stuff.

yeah, that's theoretics. but I tried 8 floppies (all new), writings them once 
and reading (=booting) at least twice, none work. but after that, when I used 
the old working boot floppy from jeremie, three of them worked as 
root-floppies!

but still, that could have been bad luck, that's why I asked here, I anybody 
hat success booting that boot.img ?? (you, sven, have no access to mac 
hardware with floppy, right ?)

> Maybe you could try loop mounting both root floppies, and compare them.

would that really make more sense than setting up d-i to build from svn ? 
there are at least five days in between the creation of the images, I expect 
a lot to have changed.

> It would be nice to get some kind of log of what is happening ? No idea
> how to achieve this though.

optional logging to some kind of loghost (via ssh and/or ftp) as part of d-i, 
executed after the installation is finished or manually in case of an error.

> > Anyhow, I realized I could use the "old" root-floppy from Jeremie and an
> > new boot-floppy. (I wrote the image on the same floppies I tried with the
> > root-image, and the floppy works.) The root-floppy gets loaded but almost
> > instantly hangs with:
> The old boot floppy with the old root floppy was fine, right ?

yeah, and the old boot floppy with the new root floppy showed this error:

> > /build/build/cdebconf-0.58/src/debconf.c:115 (main): Error reading
> > configuration information
> > /build/build/cdebconf-0.58/src/debconf-loadtemplate.c:68 (main): Error
> > reading configuration information
>
> Mmm, strange, no idea what caused this.
>
> > (I also tried three different boot-floppies, the same error. (As expected
> > as they're read ok.)
> >
> > So I guess, the floppy images are broken :(
>
> Oh, well, i guess so. Maybe the trick used for building them on a 2.6
> kernel was not ok. Don't know.
>
> BTW, can you fill a proper bug report about this problem, so it doesn't
> get lost ?

yup.


regards,
Holger


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241841: discover1: Updated Danish debconf-po translation

[Claus Hindsgaul]

Package: discover1
Version: sid
Severity: normal
Tags: patch l10n

Please use the attached updated Danish (da.po) debconf-po translation

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (600, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=da_DK, LC_CTYPE=da_DK
# translation of da.po to Danish
#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans#
#Developers do not need to manually edit POT or PO files.
# Claus Hindsgaul <[EMAIL PROTECTED]>, 2004.
#
msgid ""
msgstr ""
"Project-Id-Version: da\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2003-11-17 18:46+0100\n"
"PO-Revision-Date: 2004-04-03 12:59+0200\n"
"Last-Translator: Claus Hindsgaul <[EMAIL PROTECTED]>\n"
"Language-Team: Danish <[EMAIL PROTECTED]>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=ISO-8859-1\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.3.1\n"

#. Type: boolean
#. Description
#: ../discover.templates:4
msgid "Manage CD-ROM devices and mount points with discover?"
msgstr "Håndtér cdrom-drev og monteringspunkter med discover?"

#. Type: boolean
#. Description
#: ../discover.templates:4
msgid ""
"The \"discover\" program can automatically manage the /dev/cdrom* symbolic "
"links and device mount points, if you desire.  The available CD-ROM (and "
"compatible) devices are scanned at boot-time and these links and mount "
"points can be automatically updated."
msgstr ""
"Hvis du ønsker det, kan programmet \"discover\" kan automatisk håndtere de "
"symbolske \"/dev/cdrom\"-lænker og cdrom-drevenes monteringspunkter. Der "
"bliver søgt efter tilgængelige cdrom-drev (og kompatible) under opstarten, "
"hvorefter lænker og monteringspunkter automatisk bliver opdateret."

#. Type: boolean
#. Description
#: ../discover.templates:4
msgid ""
"If you enable this option, discover will link /dev/cdrom to /dev/cdrom0 for "
"convenience."
msgstr ""
"Hvis du aktiverer denne funktion, vil discover for letheds skyld lænke /dev/"
"cdrom til /dev/cdrom0."

#. Type: boolean
#. Description
#: ../discover.templates:4
msgid ""
"If you don't want discover to manage the device symbolic links and mount "
"points for you, decline this option."
msgstr ""
"Hvis du ikke ønsker at discover skal håndtere de enheds-specifikke lænker og "
"monteringspunkter for dig, skal du fravælge dette."

#. Type: string
#. Description
#: ../discover.templates:19
msgid "Directory for CD-ROM device mount points:"
msgstr "Mappe til cdrom-drevenes monteringspunkter:"

#. Type: string
#. Description
#: ../discover.templates:19
msgid ""
"Mounted filesystems accessible via CD-ROM (or compatible) devices can be "
"placed just about anywhere in the filesystem hierarchy, but it is common to "
"place them off the root directory, so that they are available as, e.g., \"/"
"cdrom0\", \"/cdrom1\", and so forth."
msgstr ""
"Monterede filsystemer, der kan tilgås via cdrom-drev (eller tilsvarende) kan "
"placeres næsten hvor som helst i filsystemet, men de lægges normalt i "
"rodmappen, så de er tilgængelige som f.eks. \"/cdrom0\", \"/cdrom1\" o.s.v."

#. Type: string
#. Description
#: ../discover.templates:19
msgid ""
"Note that discover will link the \"cdrom\" mount point to the \"cdrom0\" "
"mount point for convenience."
msgstr ""
"Bemærk at discover for letheds skyld vil lænke monteringspunktet \"cdrom\" "
"med \"cdrom0\"."

#. Type: string
#. Description
#: ../discover.templates:19
msgid ""
"Unless you have a need or preference for placing the CD-ROM mount points "
"elsewhere, the root directory (\"/\") is a good choice."
msgstr ""
"Medmindre du behøver eller ønsker at placere cdrom-monteringspunkterne andre "
"steder, er rodmappen (\"/\") et godt valg."

#. Type: note
#. Description
#: ../discover.templates:33
msgid "Invalid path for mount point"
msgstr "Ugyldig sti til monteringspunkt"

#. Type: note
#. Description
#: ../discover.templates:33
msgid "You entered an invalid path as CD-ROM devices mount point."
msgstr "Du har angivet en ugyldig sti som monteringspunkt for cdrom-enheder."

#. Type: note
#. Description
#: ../discover.templates:33
msgid ""
"The base filesystem mount point for CD-ROM drives must be an absolute path "
"(begin with \"/\") and must not be null.  If the path does not exist, it "
"will be created when needed."
msgstr ""
"Filsystemets monteringspunkt for cdrom-drev skal være en absolut sti "
"(starte med \"/\") og må ikke være tom. Hvis stien ikke eksisterer, "
"vil den blive oprettet, når den kræves."

#, fuzzy
#~ msgid "Please enter a valid filesystem path."
#~ msgstr "Ugyldig sti for monterings

Bug#241840: discover1 should conflict with libdiscover2

[Per Olofsson]

Package: discover1
Version: 1.5-7

Unpacking discover1 (from .../discover1_1.5-7_i386.deb) ...
dpkg: error processing
/var/cache/apt/archives/discover1_1.5-7_i386.deb (--unpack):
 trying to overwrite `/usr/share/man/man5/discover.conf.5.gz', which
 is also in package libdiscover2

-- 
Pelle


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#238472: discover should not load i810-tco module

[Petter Reinholdtsen]

[David Nusinow, 2003-03-28]
> I'm not going to release another discover1 update until the current
> one hits sarge though.

Package discover1 will not enter sarge as long as bug #238472 have
critical severity.

So you will either have to fix the problem and upload a new version,
or reduce the priority of the problem.

Besides, isn't this better fixed in discover1-data, changing all
entries with i810-tco to ignore instead?  These are the entries in pci.lst:

80862410bridge  i810-tco82801AA ISA Bridge (LPC)
80862420bridge  i810-tco82801AB ISA Bridge (LPC)
8086244cbridge  i810-tco82801BAM ISA Bridge (LPC)
80862450unknown i810-tco82801E ISA Bridge (LPC)
8086248cunknown i810-tco82801CAM ISA Bridge (LPC)
808624c0unknown i810-tco82801DB (ICH4) LPC Bridge

I suggest this bug should be reassigned to discover1-data and fixed
there.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: base-installer_0.066_powerpc.changes ACCEPTED

[Sven Luther]

Jeremie, any idea what is going on here ? Can you build a new image set
on your box, and have Holger test it ? 

On Sat, Apr 03, 2004 at 11:29:28AM +0200, Holger Levsen wrote:
> Good Morning ;)
> 
> by looking at the changelog I found that you fixed the kernel install problem 
> and this morning I found some new images at 
> http://people.debian.org/~luther/debian-installer/daily-powerpc-built/current/powerpc-small/floppy/
>  

Could you try one of the older snapshots ? From : 

 
http://people.debian.org/~luther/debian-installer/daily-powerpc-built/2004.03.31/powerpc-small/floppy/

for example ? 

> I tried to write the root.img on about 10 different floppies, twice, and 
> bootet them without any succes. The disks read fine, the mac-tux logo turns 
> black and the systems freezes. Is it possible that the root.img is broken or 
> had I just very bad luck with floppies ?

Yeah, the boot.img should be mostly ok, since it is nothing more than
the kernel and the miboot stuff.

Maybe you could try loop mounting both root floppies, and compare them.

It would be nice to get some kind of log of what is happening ? No idea
how to achieve this though.

> Anyhow, I realized I could use the "old" root-floppy from Jeremie and an new 
> boot-floppy. (I wrote the image on the same floppies I tried with the 
> root-image, and the floppy works.) The root-floppy gets loaded but almost 
> instantly hangs with:

The old boot floppy with the old root floppy was fine, right ? 

> /build/build/cdebconf-0.58/src/debconf.c:115 (main): Error reading 
> configuration information
> /build/build/cdebconf-0.58/src/debconf-loadtemplate.c:68 (main): Error reading 
> configuration information

Mmm, strange, no idea what caused this.

> (I also tried three different boot-floppies, the same error. (As expected as 
> they're read ok.)
> 
> So I guess, the floppy images are broken :(

Oh, well, i guess so. Maybe the trick used for building them on a 2.6
kernel was not ok. Don't know.

BTW, can you fill a proper bug report about this problem, so it doesn't
get lost ? 

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241838: d-i Turkish keyboard issues

[Alastair McKinstry]

DÃ DÃar, 2004-04-01 ag 01:15 -0700, scrÃobh [EMAIL PROTECTED]:

> [My previous postings were probably blocked due to your spam
> configuration, so I am reposting from a different domain] 
> 
> Hi, 
> 
Sorry, it was my fault; I've been setting up spam filters and
evolution-1.5 from experimental; some mail got lost.

> Default Turkish keymap 'trq.kmap' doesn't fully work in bterm.  I
> couldn't type Turkish spesific characters (all other non-turkish
> spesific ascii chars are okay).  Though this is not a critical problem,
> I want to propose a solution.  The problem stems from the fact that
> trq.kmap was not designed for UTF-8.  There is another Turkish Q kmap
>  --trqu.kmap for this purpose. 
> 
> I create a simple netboot iso with a modified console-data udeb which
> uses the trqu.kmap as default and it works at least in bterm (under
> C.UTF-8 locale).  There is also a minor problem for this case.
> In the second console (Alt-F2) Turkish characters can be typed, but can
> not be properly displayed, since we don't have unifont where it exists
> in bterm frame buffer.  But I could live with this problem. 
> 
> The real problem with this solution is that, I don't want to use UTF-8
> mode in virtual consoles after the installation is completed.  There is
> a lot of problem in tr_TR.UTF-8 locale.  Man files can't be properly
> displayed in UTF-8, readline has problems and the most important one,
> there are a few serious bugs in glibc. 
> 
> I couldn't perform a full d-i installation for some other d-i bugs, so
> couldn't test the whole case.  Before submitting a patch, I want to
> know your suggestions.  Is there a mechanism just to use Unicode keymap
> (trqu.kmap) for the early stages of d-i, but install the ISO keymap
> (trq.kmap) in the later stage.  As you can see in the language-chooser
> module, we've already set the default locale as tr_TR which corresponds
> to tr_TR.ISO-8859-9 locale.  If we install unicode trqu.kmap by default,
> it wouldn't work under this locale. 
> 
> As you may notice the keymap/fgGIod directory, there is another keyboard
> layout in Turkish, known as Turkish F.  I would want to add it to
> kbd-chooser templates, but the same UTF-8 problem also exists here.  So
> before creating a patch, we should solve the above problems. 
> 
> Hope I described the whole picture, let me know if you need additional
> info.  Thanks for your help. 
> 
> Cheers, 
> 
> -- 
> roktas

Ok, the best solution that appears to me is
(1) Change the default keyboard in kbd-chooser for Turkish to trqu.kmap.
(2) In kbd-chooser prebaseconfig, we can change the settings passed to
the second stage; I can add code there to change trqu -> trq for the
second stage. I will need to test this, though.

Regards,
Alastair McKinstry


-- 

Processed: Re: libdiscover-dev: Want to compile with dietlibc

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 149536 discover
Bug#149536: libdiscover-dev: Want to compile with dietlibc
Bug reassigned from package `discover1' to `discover'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Not ignoring serial port disabling is already reported

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> merge 234812 217788
Bug#217788: discover ignores 'disable serial' in /etc/discover.conf
Bug#234812: xserver-xfree86: configure script hangs
Merged 217788 234812.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#109763: marked as done (discover: no way to use one module name for kernel 2.2 and another for kernel 2.4)

[Debian Bug Tracking System]

Your message dated Sat, 03 Apr 2004 11:31:29 +0200
with message-id <[EMAIL PROTECTED]>
and subject line discover: no way to use one module name for kernel 2.2 and another 
for kernel 2.4
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; 23 Aug 2001 13:12:16 +
>From [EMAIL PROTECTED] Thu Aug 23 08:12:16 2001
Return-path: <[EMAIL PROTECTED]>
Received: from p3e9e5a27.dip.t-dialin.net (Monkey.linuxfaqs.de) [62.158.90.39] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 15ZuHP-0001wE-00; Thu, 23 Aug 2001 08:12:15 -0500
Received: by Monkey.linuxfaqs.de
via sendmail from stdin
id <[EMAIL PROTECTED]> (Debian Smail3.2.0.111)
for [EMAIL PROTECTED]; Thu, 23 Aug 2001 15:12:43 +0200 (CEST) 
Message-Id: <[EMAIL PROTECTED]>
From: Kai Lahmann <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: the module for the Realtek 8139 NIC ins#T "rtl8139" any bmore. IT#s called 
8139too now.
X-Reportbug-Version: 1.23
X-Mailer: reportbug 1.23
Date: Thu, 23 Aug 2001 15:12:43 +0200
Bcc:
Delivered-To: [EMAIL PROTECTED]

Package: discover
Version: 1.0-1
Severity: normal
Tags: sid



-- System Information
Debian Release: unstable
Architecture: i386
Kernel: Linux Monkey 2.4.9 #11 Fre Aug 17 14:14:13 CEST 2001 i686
Locale: LANG=de_DE.ISO-8859-1, LC_CTYPE=de_DE

Versions of packages discover depends on:
ii  ash   0.3.8-24   NetBSD /bin/sh
ii  libc6 2.2.4-1GNU C Library: Shared libraries an
ii  libdiscover1  1.0-1  hardware discovery and detection l


---
Received: (at 109763-done) by bugs.debian.org; 3 Apr 2004 09:32:02 +
>From [EMAIL PROTECTED] Sat Apr 03 01:32:02 2004
Return-path: <[EMAIL PROTECTED]>
Received: from 217-13-7-10.dd.nextgentel.com (minerva.hungry.com) [217.13.7.10] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B9hVR-0001tF-00; Sat, 03 Apr 2004 01:32:02 -0800
Received: from pere by minerva.hungry.com with local (Exim 3.35 #1 (Debian))
id 1B9hUv-0003wv-00; Sat, 03 Apr 2004 11:31:29 +0200
To: [EMAIL PROTECTED]
Subject: Re: discover: no way to use one module name for kernel 2.2 and another for 
kernel 2.4
From: Petter Reinholdtsen <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Sender: Petter Reinholdtsen <[EMAIL PROTECTED]>
Date: Sat, 03 Apr 2004 11:31:29 +0200
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=0.0 required=4.0 tests=none autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


Version 2 of discover is now in Debian Unstable.  This problem is
fixable, as the version 2 dataformat support having kernel modules
change from kernel version to kernel version.

Because of this, I close this bug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#152677: marked as done (discover: kernel 2.4.18 with RealTek RTL-8139 s/rtl8139/8139too/)

[Debian Bug Tracking System]

Your message dated Sat, 03 Apr 2004 11:31:29 +0200
with message-id <[EMAIL PROTECTED]>
and subject line discover: no way to use one module name for kernel 2.2 and another 
for kernel 2.4
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; 11 Jul 2002 23:35:24 +
>From [EMAIL PROTECTED] Thu Jul 11 18:35:24 2002
Return-path: <[EMAIL PROTECTED]>
Received: from asl.microsharp.com (juniper.intra.microsharp.com) [206.190.130.132] 
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 17SnT2-0002ej-00; Thu, 11 Jul 2002 18:35:24 -0500
Received: from juniper.intra.microsharp.com ([EMAIL PROTECTED] [127.0.0.1])
by juniper.intra.microsharp.com (8.12.4/8.12.4/Debian-2) with ESMTP id 
g6BNZNSK000805
(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL);
Thu, 11 Jul 2002 16:35:23 -0700
Received: (from [EMAIL PROTECTED])
by juniper.intra.microsharp.com (8.12.4/8.12.4/Debian-2) id g6BNZN6G000802;
Thu, 11 Jul 2002 16:35:23 -0700
Message-Id: <[EMAIL PROTECTED]>
Subject: discover: kernel 2.4.18 with RealTek RTL-8139 s/rtl8139/8139too/
From: "Karl M. Hegbloom" <[EMAIL PROTECTED]>
To: "Debian Bug Tracking System" <[EMAIL PROTECTED]>
X-Mailer: reportbug 1.99.40
Date: Thu, 11 Jul 2002 16:35:22 -0700
Delivered-To: [EMAIL PROTECTED]

Package: discover
Version: 1.5-1
Severity: normal

  Bus  0, device  11, function  0:
Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 16).
  IRQ 10.
  Master Capable.  Latency=64.  Min Gnt=32.Max Lat=64.
  I/O at 0x6800 [0x68ff].
  Non-prefetchable 32 bit memory at 0xe0a0 [0xe0a000ff].

 (What other info and how do I obtain it please?)

 That device is detected by "discover" as an "rtl8139".  That's
probably right for a 2.2 kernel, but for 2.4.18, there's two choices
for the 8139.  I tried to modprobe 8139cp, and it failed, but modprobe
8139too worked fine.


-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux juniper 2.4.18.1.juniper #1 SMP Thu May 2 13:28:57 PDT 2002 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages discover depends on:
ii  ash   0.3.8-38   NetBSD /bin/sh
ii  debconf   1.1.11 Debian configuration management sy
ii  libc6 2.2.5-6GNU C Library: Shared libraries an
ii  libdiscover1  1.5-1  hardware identification library

-- debconf information excluded


---
Received: (at 109763-done) by bugs.debian.org; 3 Apr 2004 09:32:02 +
>From [EMAIL PROTECTED] Sat Apr 03 01:32:02 2004
Return-path: <[EMAIL PROTECTED]>
Received: from 217-13-7-10.dd.nextgentel.com (minerva.hungry.com) [217.13.7.10] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B9hVR-0001tF-00; Sat, 03 Apr 2004 01:32:02 -0800
Received: from pere by minerva.hungry.com with local (Exim 3.35 #1 (Debian))
id 1B9hUv-0003wv-00; Sat, 03 Apr 2004 11:31:29 +0200
To: [EMAIL PROTECTED]
Subject: Re: discover: no way to use one module name for kernel 2.2 and another for 
kernel 2.4
From: Petter Reinholdtsen <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Sender: Petter Reinholdtsen <[EMAIL PROTECTED]>
Date: Sat, 03 Apr 2004 11:31:29 +0200
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=0.0 required=4.0 tests=none autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


Version 2 of discover is now in Debian Unstable.  This problem is
fixable, as the version 2 dataformat support having kernel modules
change from kernel version to kernel version.

Because of this, I close this bug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#164229: marked as done (discover: no way to specify different data for 2.2.x and 2.4.x kernels)

[Debian Bug Tracking System]

Your message dated Sat, 03 Apr 2004 11:31:29 +0200
with message-id <[EMAIL PROTECTED]>
and subject line discover: no way to use one module name for kernel 2.2 and another 
for kernel 2.4
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; 11 Oct 2002 02:22:46 +
>From [EMAIL PROTECTED] Thu Oct 10 21:22:46 2002
Return-path: <[EMAIL PROTECTED]>
Received: from 206.180.155.20.adsl.hal-pc.org (decoy.wox.org) [206.180.155.20] (foobar)
by master.debian.org with smtp (Exim 3.12 1 (Debian))
id 17zpRt-0002Xi-00; Thu, 10 Oct 2002 21:22:45 -0500
Received: (qmail 23329 invoked from network); 11 Oct 2002 02:22:42 -
Received: from homer.opus.geek (HELO homer) (192.168.1.1)
  by 0 with SMTP; 11 Oct 2002 02:22:42 -
Received: (nullmailer pid 752 invoked by uid 1000);
Fri, 11 Oct 2002 02:22:42 -
Date: Thu, 10 Oct 2002 21:22:42 -0500
From: Graham Wilson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: discover-data: discover does not work with kernel-image-2.4.18
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Reportbug-Version: 2.2
X-gpg-fingerprint: a0a7 ae54 665d 6446 f2d9  81ff 8b94 031d 7f75 635f
X-gpg-key: http://decoy.wox.org/~bob/public.asc
Delivered-To: [EMAIL PROTECTED]

Package: discover-data
Version: 1.2002.08.21-1
Severity: normal

the pci.list in discover data makes reference to a module called
`rtl8139', which not in the kernel-image-2.4.18 package. thus if you
have an ethernet with an RealTek 8139 chip, discover will not load the
module for it.

references to `rtl8139' need to be replaced with `8139too', which is a
module that comes with the kernel-images-2.4.18 package. this driver has
the same functionality.

thanks.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux homer.opus.geek 2.4.18-k7 #1 Sun Apr 14 13:19:11 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C

-- no debconf information

---
Received: (at 109763-done) by bugs.debian.org; 3 Apr 2004 09:32:02 +
>From [EMAIL PROTECTED] Sat Apr 03 01:32:02 2004
Return-path: <[EMAIL PROTECTED]>
Received: from 217-13-7-10.dd.nextgentel.com (minerva.hungry.com) [217.13.7.10] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B9hVR-0001tF-00; Sat, 03 Apr 2004 01:32:02 -0800
Received: from pere by minerva.hungry.com with local (Exim 3.35 #1 (Debian))
id 1B9hUv-0003wv-00; Sat, 03 Apr 2004 11:31:29 +0200
To: [EMAIL PROTECTED]
Subject: Re: discover: no way to use one module name for kernel 2.2 and another for 
kernel 2.4
From: Petter Reinholdtsen <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Sender: Petter Reinholdtsen <[EMAIL PROTECTED]>
Date: Sat, 03 Apr 2004 11:31:29 +0200
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=0.0 required=4.0 tests=none autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


Version 2 of discover is now in Debian Unstable.  This problem is
fixable, as the version 2 dataformat support having kernel modules
change from kernel version to kernel version.

Because of this, I close this bug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241838: kbd-chooser: Need non-UTF8 keymap for Turkish

[Alastair McKinstry]

Package: kbd-chooser
Version: 0.47
Severity: normal


For Turkish, we want the trqu UTF8 keymap for the first stage of the
install, with a non-UTF-8 keymap trq on the second stage.

-- System Information:
Debian Release: testing/unstable
  APT prefers experimental
  APT policy: (990, 'experimental'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.4-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (ignored: LC_ALL set to ga_IE.UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: discover initrd is mostly useless

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 152604 + pending
Bug#152604: discover: linuxrc must have executable bits in initrd
Tags were: patch
Tags added: pending

> retitle discover initrd fail to install required modules for root fs
Unknown command or malformed arguments to command.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#241817: install: does not create yaboot partition

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 241817 partman
Bug#241817: install: does not create yaboot partition
Bug reassigned from package `install' to `partman'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: base-installer_0.066_powerpc.changes ACCEPTED

[Holger Levsen]

Good Morning ;)

by looking at the changelog I found that you fixed the kernel install problem 
and this morning I found some new images at 
http://people.debian.org/~luther/debian-installer/daily-powerpc-built/current/powerpc-small/floppy/
 

I tried to write the root.img on about 10 different floppies, twice, and 
bootet them without any succes. The disks read fine, the mac-tux logo turns 
black and the systems freezes. Is it possible that the root.img is broken or 
had I just very bad luck with floppies ?

Anyhow, I realized I could use the "old" root-floppy from Jeremie and an new 
boot-floppy. (I wrote the image on the same floppies I tried with the 
root-image, and the floppy works.) The root-floppy gets loaded but almost 
instantly hangs with:

/build/build/cdebconf-0.58/src/debconf.c:115 (main): Error reading 
configuration information
/build/build/cdebconf-0.58/src/debconf-loadtemplate.c:68 (main): Error reading 
configuration information

(I also tried three different boot-floppies, the same error. (As expected as 
they're read ok.)

So I guess, the floppy images are broken :(


regards,
Holger

Am Freitag, 2. April 2004 14:32 schrieb Debian Installer:
> Accepted:
> base-installer_0.066.dsc
>   to pool/main/b/base-installer/base-installer_0.066.dsc
> base-installer_0.066.tar.gz
>   to pool/main/b/base-installer/base-installer_0.066.tar.gz
> base-installer_0.066_powerpc.udeb
>   to pool/main/b/base-installer/base-installer_0.066_powerpc.udeb
> Announcing to [EMAIL PROTECTED]
>
>
> Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#241817: install: does not create yaboot partition

[Sven Luther]

reassign 241817 partman
thanks
On Sat, Apr 03, 2004 at 12:04:48AM -0700, Brett Wuth wrote:
> Package: install
> Severity: important
> 
> Using the sarge-powerpc-netinst.iso image as of 2004-04-01, I
> attempted to install Debian on an iMac.  The install failed because it
> did not create a partition for yaboot.

Well, if i understood this correctly, this is only a symptom of a larger
deficiency in partman. It was already a great thing to have partman be
the default for beta3, but i guess that we should fine tune this for
beta4.

The idea is that some hardware configurations needs some particular
partitions to be there (like a prep boot partition or a palo boot
partition, or the yaboot boot partition on pmac), or even some
filesystem to be used for the /boot partition (like affs on pegasos 1).

We need to get partman to be smarter, and guide the user through the
creation of those partitions trully needed for his given arch. I believe
that this can be achieved by having some per arch, subarch and
particular case proposal of partitioning and mounting in partman,
doubled with a per arch/subarch/... choice of pre-configured partition
tables, and a warning to the user in case he doesn't mount the
partitions as is needed on the hardware in question.

Friendly,

Sven Luther


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Updated discover1 CVS

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> tags 213866 pending
Bug#213866: discover: extend manpage see-also section
There were no tags set.
Tags added: pending

> tags 240308 pending
Bug#240308: Discover: Spanish debconf translation
Tags were: l10n
Tags added: pending

> tags 241701 pending
Bug#241701: discover1-data: Should include repurtbug script to include lspci info
There were no tags set.
Tags added: pending

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Processed: Re: Bug#241478: partman: fatal error : OK - cancel ?

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 241478 partman
Bug#241478: partman: fatal error : OK - cancel ?
Bug reassigned from package `partman' to `partman'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#239725: marked as done (should provide discover-udeb)

[Debian Bug Tracking System]

Your message dated Sat, 03 Apr 2004 09:53:15 +0200
with message-id <[EMAIL PROTECTED]>
and subject line should provide discover-udeb
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; 24 Mar 2004 02:25:54 +
>From [EMAIL PROTECTED] Tue Mar 23 18:25:54 2004
Return-path: <[EMAIL PROTECTED]>
Received: from kitenet.net [64.62.161.42] (postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B5y5a-0003Vh-00; Tue, 23 Mar 2004 18:25:54 -0800
Received: from dragon.kitenet.net (216-98-95-32.access.naxs.com [216.98.95.32])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(Client CN "Joey Hess", Issuer "Joey Hess" (verified OK))
by kitenet.net (Postfix) with ESMTP id 671BB17EF8
for <[EMAIL PROTECTED]>; Wed, 24 Mar 2004 02:25:51 + (GMT)
Received: by dragon.kitenet.net (Postfix, from userid 1000)
id 472C56F11C; Tue, 23 Mar 2004 21:25:06 -0500 (EST)
Date: Tue, 23 Mar 2004 21:25:05 -0500
From: Joey Hess <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: should provide discover-udeb
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="WIyZ46R2i8wDzkSu"
Content-Disposition: inline
X-Reportbug-Version: 2.53
User-Agent: Mutt/1.5.5.1+cvs20040105i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_12 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_12
X-Spam-Level: 


--WIyZ46R2i8wDzkSu
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: discover1-udeb
Severity: normal
Tags: d-i

hw-detect depends on discover-udeb, so I think that discover1-udeb
should provide it. Currently the d-i initrd build process downloads
discover-udeb, but does not put it in the initrd, and in the initrd,
hw-detects dependency is unsatisfied.

It might be better if discover 1 and 2 udebs both provided a third name,
like discover, then hw-detect could depend on that.

--=20
see shy jo

--WIyZ46R2i8wDzkSu
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)

iD8DBQFAYPGBd8HHehbQuO8RAoQBAJ9nH99u/d2SXFNsf4KjpayvTeaUfQCgqNtm
A22S3Oi+W+xlxq418n66qKk=
=cdZw
-END PGP SIGNATURE-

--WIyZ46R2i8wDzkSu--

---
Received: (at 239725-done) by bugs.debian.org; 3 Apr 2004 07:53:50 +
>From [EMAIL PROTECTED] Fri Apr 02 23:53:50 2004
Return-path: <[EMAIL PROTECTED]>
Received: from 217-13-7-10.dd.nextgentel.com (minerva.hungry.com) [217.13.7.10] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1B9fyP-0003KY-00; Fri, 02 Apr 2004 23:53:50 -0800
Received: from pere by minerva.hungry.com with local (Exim 3.35 #1 (Debian))
id 1B9fxr-00037s-00; Sat, 03 Apr 2004 09:53:15 +0200
To: [EMAIL PROTECTED]
Subject: Re: should provide discover-udeb
From: Petter Reinholdtsen <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
Sender: Petter Reinholdtsen <[EMAIL PROTECTED]>
Date: Sat, 03 Apr 2004 09:53:15 +0200
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=-1.0 required=4.0 tests=BAYES_30 autolearn=no 
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 


The package control  file now reads

  Package: discover1-udeb
  Section: debian-installer
  Priority: extra
  Architecture: any
  Provides: discover
  Depends: ${shlibs:Depends}, discover1-data-udeb
  Description: hardware identification library (udeb)

Checking the changelog, I see that the fix was included in version
1.5-7.  This problem is fixed.  Closing the bug.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]