Bug#474043: Bug report

2008-04-02 Thread Christian Perrier
Quoting K|Ke ([EMAIL PROTECTED]):
> Package: installation-reports
> 
> Boot method: 
> Image version: 
> Processor: Intel Core 2 Quad

Have you tried to use an i386 image instead of an amd64 one?




signature.asc
Description: Digital signature


Re: 2.6.24 boot floppy

2008-04-02 Thread Joey Hess
Joey Hess wrote:
> Dropping klibc sh and rewriting init as a custom klibc executable would
> probably save about 25kb..

Done, new C init is about 3kb, and once klibc sh, mkdir, and mknod are
removed and a kernel with modular ext2 used, and all the syslinux help
screens dropped, it fits. Barely. Less than 1k free.. :-/

A few things can still be done to reduce size. Embedding mount, umount,
cat, gunzip, and cpio code in the init binary and statically linking it
to klibc would probably save 30 kb or so. (This would also allow upxing
init.)

-- 
see shy jo


signature.asc
Description: Digital signature


partman-multipath_1_powerpc.changes ACCEPTED

2008-04-02 Thread Debian Installer

Accepted:
partman-multipath_1.dsc
  to pool/main/p/partman-multipath/partman-multipath_1.dsc
partman-multipath_1.tar.gz
  to pool/main/p/partman-multipath/partman-multipath_1.tar.gz
partman-multipath_1_all.udeb
  to pool/main/p/partman-multipath/partman-multipath_1_all.udeb


Override entries for your package:
partman-multipath_1.dsc - optional debian-installer
partman-multipath_1_all.udeb - optional debian-installer

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#474043: Bug report

2008-04-02 Thread K|Ke
Package: installation-reports

Boot method: 
Image version: 
Date: <01/04/2008 - 15:00 hrs.>

Machine: 
Processor: Intel Core 2 Quad
Memory: 4 Gbytes
Partitions: 

Output of lspci -nn and lspci -vnn: It is not possible

Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [E]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems: I can't continue the installation process, by not
detecting the CD





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



Bug#472487: additional info

2008-04-02 Thread Holger Wansing
Hi,

On Wed, 2 Apr 2008 19:58:39 +0200 Frans Pop wrote:
> Could you try to manually add the patch below to /bin/hw-detect, right at 
> the beginning of the installation (while the language selection dialog is 
> displayed)?

Yes, the patch does the job! CD-ROM drive is automatically detected.

> It's a rough patch and needs a bit more refinement, but it should hopefully 
> do what we want for this type of system. I've added debugging commands so 
> the result should show up in the syslog. Please send that both if it works 
> and if it doesn't.

syslog is attached.


Holger



--

==
Created with Sylpheed 2.3.0
under THE NEW DEBIAN GNU/LINUX 4.0 »Etch«
http://counter.li.org/,  Registered LinuxUser #311290
Try out OpenGL 3D-Desktop Beryl! www.beryl-project.org
=



syslog-patch.tar.gz
Description: Binary data


Bug#474023: Installation report (ath5k wireless driver / Thinkpad R51e)

2008-04-02 Thread Chris Lamb
Package: installation-reports

 NB. This installation was intended to test the ath5k wireless driver with
 d-i, and does not use a "standard" weekly or daily image.

Boot method: netboot
Image version: http://people.debian.org/~fjp/tmp/d-i/netboot-ath5k.tar.gz
Date: Wed Apr  2 20:05:01 BST 2008

Machine: IBM ThinkPad R51e

 [...]
04:02.0 Ethernet controller: Atheros Communications, Inc. AR5212/AR5213
 Multiprocol MAC/baseband processor (rev 01)
 [...]


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [E]
Detect CD:  [ ] 
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

This installation was intended to test the ath5k wireless driver with d-i:

 * netcfg correctly identified the wireless device and did not show any
   spurious control devices

 * "Automatic" configuration of the device failed

 * Entering an ESSID manually resulted in a DHCP failure

 * I continued the installation using my wired ethernet adaptor to a point
   where I could install wireless-tools-udeb

 * "iwconfig wlan0" and "iwgetid" showed that the wlan0 had been configured
   to point at the correct access point by BSSID address

 * Running:
- iwconfig wlan0 ap off
- ip link set wlan0 up
- iwconfig wlan0 essid my_essid

   .. resulted in dhclient working, although there was an interesting
   conflict with the existing wired configuration:

 [...]
 DHCPREQUEST on wlan0 to 255.255.255.255 port 67
 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
 DHCPOFFER from 192.168.0.1
 DHCPREQUEST on wlan0 to 255.255.255.255 port 67
 DHCPPACK from 192.168.0.1
 ip: RTNETLINK answers: File exists
 dhclient.c(2129): null pointer
 [...]

   This process and message looped indefinately until ^C.

 * Retracing my steps in the netcfg component did not result in a working
   wireless configuration

Comments/Problems:

So, it appears that netcfg does not call 'ap off' (or ipiw equivalent) and
does not set the link up. 

 < fjp> Hmm. iwconfig wlan0 ap off is basically only to reset the AP for
 new scan/association
 < fjp> Probably makes sense to do that by default in netcfg for any retry.

I would agree, but would add that running that (or its iwlib equivalent)
before the first attempt might assist drivers that initialise in a strange
way - remember that in my test above, the wireless device was actually
configured with the correct BSSID, but required an reset via "ap off"
before it worked.

However, this and other quirks may be specific to ath5k, a somewhat
experimental driver.


Regards,

-- 
Chris Lamb, UK   [EMAIL PROTECTED]
GPG: 0x634F9A20


signature.asc
Description: PGP signature


Bug#472487: additional info

2008-04-02 Thread Holger Wansing
Hello,

On Wed, 2 Apr 2008 16:44:37 +0200 Frans Pop wrote:
> > Yes. Auto-detecting the cdrom drive works this way.
> 
> OK. That at least identifies the problem, though reverting that change would 
> not solve all problems as initramfs-tools would still need to be made to 
> load the driver.
> 
> What we basically need to do here is find a way to identify this type of 
> system so we can automate the loading of ide-generic.
> 
> BTW, doesn't the installer offer to load additional drivers when it fails to 
> detect the CD? If it does, what are the dialogs that are displayed?

1.  No common CD-ROM drive was detected.
You may need to load additional CD-ROM drivers from a
driver floppy...
Load CD-ROM drivers from a driver floppy?
Yes No
[Answered with No.]

2.  No common CD-ROM drive was detected.
Your CD-ROM drive may be an old Mitsumi or another non-IDE,
non-SCSI CD-ROM drive. ...
Manually select a CD-ROM module and device?
Yes No
[Answered with No.]

3.  An installation step failed.
You can try to run the failing item again from the menu, or
skip it and choose something else...
Continue


> Could you also do the following:
> - boot the installer
> - proceed until the CD fails to be recognized
> - switch to VT2
> - what is the output of the following commands at that point:
>   - ls /proc/bus/*
>   - ls /sys/bus
>   - cat /proc/interrupts
>   - cat /proc/iomem
>   - cat /proc/ioports
> - enter the following commands:
>   - logger -t DEBUG "Before loading ide-generic"
>   - modprobe ide-generic
> - send the /var/log/syslog at this point
> - is there any change in the output of the commands above after that?


Output of:  ls /proc/bus/*

/proc/bus/input:
devices
handlers

/proc/bus/pccard:
drivers

/proc/bus/pci:
00
devices

/proc/bus/usb:



Output of:  ls /sys/bus

MCA
acpi
eisa
ide
isa
pci
pci_express
pcmcia
platform
pnp
scsi
serio
spi
usb



Output of:  cat /proc/interrupts

   CPU0   
  0:  25005XT-PIC-XTtimer
  1:476XT-PIC-XTi8042
  2:  0XT-PIC-XTcascade
  6:  3XT-PIC-XTfloppy
  7:  3XT-PIC-XTparport0
 11:  0XT-PIC-XTyenta, yenta, ohci_hcd:usb1
 12:  4XT-PIC-XTi8042
 13: 26XT-PIC-XTacpi
NMI:  0 
LOC:  0 
ERR:  0
MIS:  0



Output of:  cat /proc/iomem

-0009fbff : System RAM
  - : Crash kernel
0009fc00-0009 : reserved
000a-000b : Video RAM area
000c-000c97ff : Video ROM
000f-000f : System ROM
0010-0200 : System RAM
  0010-0029e27a : Kernel code
  0029e27b-00340cc3 : Kernel data
0201-0201 : ACPI Tables
0202-0203 : reserved
1000-13ff : PCI CardBus #01
1400-17ff : PCI CardBus #01
1800-1bff : PCI CardBus #05
1c00-1fff : PCI CardBus #05
2000-2003 : :00:04.0
2004-20040fff : :00:13.0
  2004-20040fff : yenta_socket
20041000-20041fff : :00:13.1
  20041000-20041fff : yenta_socket
fcfff000-fcff : :00:0b.0
  fcfff000-fcff : ohci_hcd
fd00-fdff : :00:04.0
fef8-feff : reserved
fffe-fffe6dff : reserved
fffe6e00-fffe6fff : ACPI Non-volatile Storage
fffe7000- : reserved



Output of:  cat /proc/ioports

-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
0378-037a : parport0
03c0-03df : vga+
03f2-03f5 : floppy
03f7-03f7 : floppy DIR
03f8-03ff : serial
0778-077a : parport0
0cf8-0cff : PCI conf1
1000-10ff : PCI CardBus #01
1400-14ff : PCI CardBus #01
1800-18ff : PCI CardBus #05
  18a0-18a3 : ACPI PM1a_EVT_BLK
  18a4-18a5 : ACPI PM1a_CNT_BLK
  18a6-18a6 : ACPI PM2_CNT_BLK
  18a8-18ab : ACPI PM_TMR
  18ac-18af : ACPI GPE0_BLK
  18b0-18b5 : ACPI CPU throttle
1c00-1cff : PCI CardBus #05
ffe0- : :00:11.0



[Executed "logger -t DEBUG "Before loading ide-generic"
  and "modprobe ide-generic" ]

After that:
Output of:  /var/log/syslog
[see attached file "syslog" ]


Output of:  ls /proc/bus/*
[the same as above]


Output of:  ls /sys/bus
[the same as above]


Output of:  cat /proc/interrupts

   CPU0   
  0:  31540XT-PIC-XTtimer
  1:   1095XT-PIC-XTi8042
  2:  0XT-PIC-XTcascade
  6:  3XT-PIC-XTfloppy
  7:  3XT-PIC-XTparport0
 11:  0XT-PIC-XTyenta, yenta, ohci_hcd:usb1
 12:  4XT-PIC-XTi8042
 13: 36XT-PIC-XTacpi
 14:491XT-PIC-XTide0
 15: 27XT-PIC-XTide1
NMI:  0 
LOC:  0 
ERR:  0
MIS:  0



Output of:  cat /proc/iome

[RFC] Extending wireless-tools-udeb

2008-04-02 Thread Frans Pop
Currently wireless-tools-udeb exists and it is still included in some images 
[1], but AFAICT the binaries in the udeb are not used anywhere so there 
should be no need to include it by default.

IMO it still makes sense to keep the udeb for debugging purposes, and 
possibly also for cases that netcfg currently does not support [2]. But for 
that purpose it is probably useful to add iwevent and iwlist to the udeb 
(not sure about iwpriv and iwspy). It should then also be listed as an 
optional component in anna.

So steps would be:
- remove wireless-tools-udeb from all pkg-lists
- request addition of iwevent and iwlist (and iwpriv and iwspy?)
- request addition of menu-item-number 9

Comments?

Cheers,
FJP

[1]
$ cd installer/build/pkg-lists
$ wcgrep wireless-tools
./net_drivers/powerpc.cfg:22:#wireless-tools-udeb
./net_drivers-1/i386.cfg:20:wireless-tools-udeb
./monolithic/i386.cfg:5:wireless-tools-udeb
./monolithic/amd64.cfg:5:wireless-tools-udeb

[2] Of course this would only work for CD-based installs where no network is 
needed to load additional components.


signature.asc
Description: This is a digitally signed message part.


Re: 2.6.24 boot floppy

2008-04-02 Thread Joey Hess
Bastian Blank wrote:
> Commited. Should be available with tomorrow snapshots. Please report
> back ASAP.

With today's snapshot, it's still too large. 22kb still needs to be
trimmed from somewhere.

Dropping klibc sh and rewriting init as a custom klibc executable would
probably save about 25kb..

-- 
see shy jo


signature.asc
Description: Digital signature


Bug#472487: additional info

2008-04-02 Thread Frans Pop
On Tuesday 01 April 2008, Holger Wansing wrote:
> > Please try booting Beta1 with 'hw-detect/load-ide=true'. Does that
> > help?
>
> Yes. Auto-detecting the cdrom drive works this way.

Could you try to manually add the patch below to /bin/hw-detect, right at 
the beginning of the installation (while the language selection dialog is 
displayed)?

It's a rough patch and needs a bit more refinement, but it should hopefully 
do what we want for this type of system. I've added debugging commands so 
the result should show up in the syslog. Please send that both if it works 
and if it doesn't.

Cheers,
FJP

--- a/packages/hw-detect/hw-detect.sh
+++ b/packages/hw-detect/hw-detect.sh
@@ -288,6 +288,19 @@ if [ -z "$LIST" ]; then
db_progress STEP $MODULE_STEPS
 fi

+# Load ide-generic and check if that results in new block devices
+# If so, make sure it is added to the initrd for the installed system
+set -x
+if [ -z "$LOAD_IDE" ] && is_available ide-generic; then
+   blockdev_count=$(ls /sys/block | wc -w)
+   load_module ide-generic
+   update-dev
+   if [ $(ls /sys/block | wc -w) -gt $blockdev_count ]; then
+   register-module -i ide-generic
+   fi
+fi
+set +x
+
 if ! is_not_loaded ohci1394 || ! is_not_loaded firewire-ohci; then
# if firewire was found, try to enable firewire cd support
if is_not_loaded sbp2 && is_not_loaded firewire-sbp2 && \



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



Bug#472487: additional info

2008-04-02 Thread Frans Pop
On Tuesday 01 April 2008, Holger Wansing wrote:
> > If this is an issue, it's something in the kernel upstream as that is
> > the only thing that could detect the problem in a timely fashion and
> > warn about it. I'm not going to file a BR about it though.
> > Documentation seems the best solution here.
>
> Ok. But we have a hint in the manual, that there _is_ such an
> automatic fallback (or am I wrong?)

Yes, that needs to be clarified a bit. I'll see if I can come up with 
something.

> > > 2. cdrom drive (and harddisk) were not detected in step "detecting
> > > cd-rom drive". There were no ide related modules loaded
> > > automatically in this step, only usb-storage was loaded. When I
> > > loaded ide_generic by hand on the second console, it worked, cdrom
> > > drive and hard disk were detected.
> >
> > Please try booting Beta1 with 'hw-detect/load-ide=true'. Does that
> > help?
>
> Yes. Auto-detecting the cdrom drive works this way.

OK. That at least identifies the problem, though reverting that change would 
not solve all problems as initramfs-tools would still need to be made to 
load the driver.

What we basically need to do here is find a way to identify this type of 
system so we can automate the loading of ide-generic.

BTW, doesn't the installer offer to load additional drivers when it fails to 
detect the CD? If it does, what are the dialogs that are displayed?

> Only one note: normally there is the hint "rescue mode" in the
> left corner at the top of the screen. When running rescue mode on a
> low memory machine, there is only "low memory mode" displayed,
> nothing about that rescue mode is active.

Hmm. Maybe the rescue mode indication should be preferred over the lowmem 
one.


Thanks for the additional info. I've also asked the upstream kernel 
developers for help for this.

Could you also do the following:
- boot the installer
- proceed until the CD fails to be recognized
- switch to VT2
- what is the output of the following commands at that point:
  - ls /proc/bus/*
  - ls /sys/bus
  - cat /proc/interrupts
  - cat /proc/iomem
  - cat /proc/ioports
- enter the following commands:
  - logger -t DEBUG "Before loading ide-generic"
  - modprobe ide-generic
- send the /var/log/syslog at this point
- is there any change in the output of the commands above after that?

Cheers,
FJP



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



busybox-static question

2008-04-02 Thread Michael Meskes
Hi,

on cleaning my system from older packages I noticed that busybox-static
could replace my sash installation and offer even more functionality.
However, it needs manual administrative work to get things going while
the sash package takes care of almost all the stuff needed. Would it be
possible to add this stuff or at least parts of it to busybox-static? 

Michael
-- 
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: [EMAIL PROTECTED]
Go VfL Borussia! Go SF 49ers! Use Debian GNU/Linux! Use PostgreSQL!


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



lowmem_1.28_amd64.changes ACCEPTED

2008-04-02 Thread Debian Installer

Accepted:
lowmem_1.28.dsc
  to pool/main/l/lowmem/lowmem_1.28.dsc
lowmem_1.28.tar.gz
  to pool/main/l/lowmem/lowmem_1.28.tar.gz
lowmem_1.28_all.udeb
  to pool/main/l/lowmem/lowmem_1.28_all.udeb
lowmemcheck_1.28_amd64.udeb
  to pool/main/l/lowmem/lowmemcheck_1.28_amd64.udeb


Override entries for your package:
lowmem_1.28.dsc - source debian-installer
lowmem_1.28_all.udeb - optional debian-installer
lowmemcheck_1.28_amd64.udeb - optional debian-installer

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]



Processing of lowmem_1.28_amd64.changes

2008-04-02 Thread Archive Administrator
lowmem_1.28_amd64.changes uploaded successfully to localhost
along with the files:
  lowmem_1.28.dsc
  lowmem_1.28.tar.gz
  lowmem_1.28_all.udeb
  lowmemcheck_1.28_amd64.udeb

Greetings,

Your Debian queue daemon


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



Bug#473971: debian-installer: lenny installer kernel hangs after boot on Asus M2N notebook

2008-04-02 Thread Frans Pop
reassign 473971 linux-2.6 2.6.24-4
thanks

On Wednesday 02 April 2008, Marc Haber wrote:
> the Debian installer lenny kernel (pulled today from
> http://http.us.debian.org/debian/dists/lenny/main/installer-i386/current/
>images/hd-media/) freezes after booting, last line seen is "Setting up
> standard PCI resources" on an Asus M2N notebook. Setting "noacpi noapic"
> doesn't help. The etch installer kernel boots just fine.
>
> The M2N is a first generation Centrino notebook: Pentium M processor,
> Intel Chipset. I can deliver additional information if you ask.

Looks like a kernel issue, thus reassigning.

Cheers,
FJP



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



Processed: Re: Bug#473971: debian-installer: lenny installer kernel hangs after boot on Asus M2N notebook

2008-04-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> reassign 473971 linux-2.6 2.6.24-4
Bug#473971: debian-installer: lenny installer kernel hangs after boot on Asus 
M2N notebook
Bug reassigned from package `debian-installer' to `linux-2.6'.

> 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#473971: debian-installer: lenny installer kernel hangs after boot on Asus M2N notebook

2008-04-02 Thread Marc Haber
Package: debian-installer
Severity: normal

Hi,

the Debian installer lenny kernel (pulled today from
http://http.us.debian.org/debian/dists/lenny/main/installer-i386/current/images/hd-media/)
freezes after booting, last line seen is "Setting up standard PCI
resources" on an Asus M2N notebook. Setting "noacpi noapic" doesn't
help. The etch installer kernel boots just fine.

The M2N is a first generation Centrino notebook: Pentium M processor,
Intel Chipset. I can deliver additional information if you ask.

Greetings
Marc

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24.4-scyw00225 (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



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



Re: [RFC] Major issue with use of Choices-C

2008-04-02 Thread Frans Pop
On Wednesday 02 April 2008, Frans Pop wrote:
> This indeed is a real issue.

I've been looking at a solution for this in debconf, but am confused.

# LANG= LANGUAGE=nl LC_ALL=en_US.UTF-8 ../../test-debconf-C
=> Dialog is displayed in Dutch
@langs = nl:en_us.utf-8:en_us:en.utf-8:en

# LANG= LANGUAGE=en LC_ALL=nl_NL.UTF-8 ../../test-debconf-C
=> Dialog is displayed in Dutch
@langs = en:nl_nl.utf-8:nl_nl:nl.utf-8:nl

(Values for @langs are from /usr/share/perl5/Debconf/Template.pm.)

Why are both cases displayed in Dutch? I would have expected English for the
second.

It seems that because there are no specific -en.UTF-8 templates for English,
Dutch ends up being preferred.
This basically means that for debconf you'll never be able to override a 
specific locale setting using LANGUAGE=C or LANGUAGE=en; you'll always have 
to specify the locale and have LANGUAGE unset.

# LANG= LANGUAGE=en LC_ALL=C ../../test-debconf-C
=> Choices-C values are displayed
@langs = en:c

Here again, C is the first actual match because Choices-C exists.

# LANG= LANGUAGE= LC_ALL=en_US.UTF-8 ../../test-debconf-C
=> Dialog is displayed in English
@langs = en_us.utf-8:en_us:en.utf-8:en

Here the display is finally correct, but only because there is _no_ match
at all...

I wonder if this patch to /usr/share/perl5/Debconf/Template.pm would be
the correct way to solve this issue:
--- ../../Template.pm   2008-04-02 13:39:54.0 +0200
+++ /usr/share/perl5/Debconf/Template.pm2008-04-02 13:53:17.0 
+0200
@@ -279,6 +279,7 @@
 }
 
 my @langs=map { lc $_ } _getlangs();
+print join(":", @langs), "\n";
 
 sub AUTOLOAD {
(my $field = our $AUTOLOAD) =~ s/.*://;
@@ -294,6 +294,8 @@
if ($Debconf::Template::i18n && @langs) {
my @fields = grep /^\Q$field\E(?:[EMAIL PROTECTED]|$)/, 
$Debconf::Db::templates->fields($this->{template});
foreach my $lang (@langs) {
+   $lang="en" if ($lang eq "c");
+

$ret=$Debconf::Db::templates->getfield($this->{template}, 
$field.'-'.$lang);
return $ret if defined $ret;

@@ -306,6 +308,8 @@
}
}
}
+
+   last if ($lang eq "en")
}
} elsif (not $Debconf::Template::i18n && $field !~ /-c$/i) {

$ret=$Debconf::Db::templates->getfield($this->{template}, $field.'-c');

The first hunk makes sure that "Choices-C" fields are never explicitly
selected, but English is used instead. The second hunk solves the second
example I started with by breaking out of the loop if the language is "en"
and thereby ensuring debconf defaults to the standard field.

Cheers,
FJP


signature.asc
Description: This is a digitally signed message part.


Re: ttf-dejavu 2.24-2

2008-04-02 Thread Philipp Kern
On Tue, Apr 01, 2008 at 10:02:56PM +0200, Davide Viti wrote:
> this version fixes #471024 which affects the graphical installer:
> please unblock it.

# 20080402
#  acked by otavio on IRC
unblock ttf-dejavu/2.24-2

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp Kern Debian Developer
: :' :  http://philkern.de   Debian Release Assistant
`. `'   xmpp:[EMAIL PROTECTED]
  `-finger pkern/[EMAIL PROTECTED]


signature.asc
Description: Digital signature


Bug#395411: Get all your luxury needs here

2008-04-02 Thread Jusitn frizen

Get dressed for success here

Carry yourself with confidence by wearing one of our quality watches 
http://www.mueigbae.com/



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



Re: pegasos 1

2008-04-02 Thread Christian Perrier
Quoting David MARIE ([EMAIL PROTECTED]):
> bonjour quel et l'image iso a prendre pour un pegasos 1 si vous avez un lien 
> sa serait mieux mon adresse email et [EMAIL PROTECTED] 

debian-boot is an English-speaking mailing list aimed for development
of the Debian Installer.

"what ISO image should be used to install a Pegasos 1"

Installation images are available from http://cdimage.debian.org

If you want to install development versions of the Debian Installer
(which install testing when used out of the box), please go to
http://www.debian.org/devel. Prefrrably first choose images named
"beta1".

From my poor knowledge of these machines, the "powerpc" images should
be used to install Pegasos machines.

J'espère que la réponse ci-dessus vous convient et est compréhensible.

-- 




signature.asc
Description: Digital signature


Bug#218775: Massive discounts on luxury items

2008-04-02 Thread INSOO derick

It cannot get louder than thi

We had a pair of matching timepieces to represent our eternal love. 
http://www.bisoegiu.com/



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



Re: ttf-dejavu 2.24-2

2008-04-02 Thread Philipp Kern
On Wed, Apr 02, 2008 at 04:36:14AM +0200, Frans Pop wrote:
> Davide Viti wrote:
> > this version fixes #471024 which affects the graphical installer:
> > please unblock it.
> There is absolutely no need for special treatment of this version because of 
> the mentioned BR because the broken version never migrated to testing.

Right, but could it be unblocked or not?

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp Kern Debian Developer
: :' :  http://philkern.de   Debian Release Assistant
`. `'   xmpp:[EMAIL PROTECTED]
  `-finger pkern/[EMAIL PROTECTED]


signature.asc
Description: Digital signature


Re: [RFC] Major issue with use of Choices-C

2008-04-02 Thread Frans Pop
On Wednesday 02 April 2008, Frans Pop wrote:
> In D-I this currently results in "C, en" being displayed as languages for
> serial console installs instead of "C, English". It does not result in
> issues elsewhere because we "force" debconf/language to "en" if the C
> locale is selected.

It seems that the proper thing to do in localechooser is to clear the value 
of debconf/language in localechooser rather than setting it to C. This at 
least gets rid of the reported issue for serial console installs.

> As I expect the same will happen if LC_all=C and LANG and
> debconf/language are not explicitly set (needs verification!), the
> problem is not confined to D-I.

This indeed is a real issue.

I tested this by loading the following template on a running system (so 
using debconf):
Name: fjp/test
Choices-c: a, b, c
Choices: Option A, Option B, Option C
Choices-nl.utf-8: Optie A, Optie B, Optie C
Description: This is a test
Description-nl.utf-8: Dit is een test
Type: select
Owners: fjp/test

With the following script:
$ cat test
#! /bin/sh

. /usr/share/debconf/confmodule

db_reset fjp/test
db_input high fjp/test
db_go

Test results:
# LC_ALL=en_US.UTF-8 ./test
# LANGUAGE=de ./test
=> Question and choices displayed in English

# LC_ALL=nl_NL.UTF-8 ./test
# LANG=nl_NL.UTF-8 ./test
# LANGUAGE=nl ./test
=> Question and choices displayed in Dutch

# LC_ALL=C ./test
# LANG=C ./test
# LANGUAGE=C ./test
# LANG=nl ./test # invalid
# LC_ALL= ./test
=> Choices are the values from Choices-c!

Cheers,
FJP


signature.asc
Description: This is a digitally signed message part.