date:20040224

On Sat, Feb 14, 2004 at 07:01:31PM +0900, Kenshi Muto wrote:
> At 13 Feb 04 11:13:43 GMT,
> Matt Kraai wrote:
> > In order to have main-menu run the postinst for bterm-unifont, I
> > think the latter needs to have a menu item.  Is it OK to use 22?
> 
> I tried to use 22 on CD install.
> 
> Installer step is:
> language -> country -> keyboard -> cd detect -> installer component from CD -> 
> detect network hardware -> configure network -> bterm-unifont
> 
> Hmm, that's bad.
> bterm-unifont is called after configure network. And 'configure
> network' step needs some additional glyph.

The CVS version of anna should run the postinst.  Would you please
test it?  This avoids the useless menu item.

-- 
Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/


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

Bug#232397: bterm-unifont: postinst won't run?

On Tue, Feb 24, 2004 at 12:26:04PM -0500, Joey Hess wrote:
> Matt Kraai:
> > How about making anna configure packages that do not have menu
> > items?
> 
> I think that is a good idea. Only problem I can anticipate is that if
> something w/o a menu item depended on something with a menu item, it
> might fail to configure, but obviously nothing in current d-i has the
> problem.

I've checked in a patch to do so.  Would someone please test it?

-- 
Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/


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

Bug#234687: Boot fails on g5 desktop

2004-02-24 Thread Mattias Wadenstein

Package: installation-reports

INSTALL REPORT

Debian-installer-version: gluck daily netinst, 2004-02-19
uname -a: n/a
Date: 2004-02-19
Method: Booted from CDROM

Machine: Powermac G5 Desktop
Processor: 2 x ppc 970 @ 2.0GHz
Memory: 4G
Root Device: Maxtor 250G SATA drive
Root Size/partition table:  n/a
Output of lspci:

In mac-speak:
http://www.acc.umu.se/~maswan/debian/g5-hardware.txt

Relevant part, I think:
PCI/AGP Cards:

ATY,R350:

  Type: display
  Bus: AGP
  Slot: SLOT-1
  VRAM (Total): 128 MB
  Vendor: ATI (0x1002)
  Device ID: 0x4e48
  Revision ID: 0x
  ROM Revision: 113-A14401-116

ATY,Rocket_A:

  Type: display
  Display Type: LCD
  VRAM (In Use): 128 MB

ATY,Rocket_B:

  Status: No display connected


Base System Installation Checklist:

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

Comments/Problems:

Does not give any output after "opening display" with a string indicating
the graphics card referenced above.

/Mattias Wadenstein


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

netcfg_0.47_i386.changes ACCEPTED


Accepted:
netcfg-dhcp_0.47_i386.udeb
  to pool/main/n/netcfg/netcfg-dhcp_0.47_i386.udeb
netcfg-static_0.47_i386.udeb
  to pool/main/n/netcfg/netcfg-static_0.47_i386.udeb
netcfg_0.47.dsc
  to pool/main/n/netcfg/netcfg_0.47.dsc
netcfg_0.47.tar.gz
  to pool/main/n/netcfg/netcfg_0.47.tar.gz
netcfg_0.47_i386.udeb
  to pool/main/n/netcfg/netcfg_0.47_i386.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]

Processing of netcfg_0.47_i386.changes

netcfg_0.47_i386.changes uploaded successfully to localhost
along with the files:
  netcfg_0.47.dsc
  netcfg_0.47.tar.gz
  netcfg_0.47_i386.udeb
  netcfg-dhcp_0.47_i386.udeb
  netcfg-static_0.47_i386.udeb

Greetings,

Your Debian queue daemon


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

linux-kernel-di_0.37_source+i386+alpha+ia64+m68k+mips+mipsel+powerpc+sparc.changes ACCEPTED


Accepted:
affs-modules-2.4.22-powerpc-di_0.37_powerpc.udeb
  to pool/main/l/linux-kernel-di/affs-modules-2.4.22-powerpc-di_0.37_powerpc.udeb
affs-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
  to pool/main/l/linux-kernel-di/affs-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
brltty-modules-2.4.22-itanium-di_0.37_ia64.udeb
  to pool/main/l/linux-kernel-di/brltty-modules-2.4.22-itanium-di_0.37_ia64.udeb
brltty-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
  to 
pool/main/l/linux-kernel-di/brltty-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
brltty-modules-2.4.22-speakup-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/brltty-modules-2.4.22-speakup-di_0.37_i386.udeb
brltty-modules-2.4.24-1-386-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/brltty-modules-2.4.24-1-386-di_0.37_i386.udeb
brltty-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  to pool/main/l/linux-kernel-di/brltty-modules-2.4.24-1-generic-di_0.37_alpha.udeb
cdrom-core-modules-2.4.22-itanium-di_0.37_ia64.udeb
  to pool/main/l/linux-kernel-di/cdrom-core-modules-2.4.22-itanium-di_0.37_ia64.udeb
cdrom-core-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
  to 
pool/main/l/linux-kernel-di/cdrom-core-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
cdrom-core-modules-2.4.22-speakup-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/cdrom-core-modules-2.4.22-speakup-di_0.37_i386.udeb
cdrom-core-modules-2.4.24-1-386-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/cdrom-core-modules-2.4.24-1-386-di_0.37_i386.udeb
cdrom-core-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  to pool/main/l/linux-kernel-di/cdrom-core-modules-2.4.24-1-generic-di_0.37_alpha.udeb
cdrom-modules-2.4.22-speakup-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/cdrom-modules-2.4.22-speakup-di_0.37_i386.udeb
cdrom-modules-2.4.24-1-386-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/cdrom-modules-2.4.24-1-386-di_0.37_i386.udeb
cdrom-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  to pool/main/l/linux-kernel-di/cdrom-modules-2.4.24-1-generic-di_0.37_alpha.udeb
ext3-modules-2.4.22-itanium-di_0.37_ia64.udeb
  to pool/main/l/linux-kernel-di/ext3-modules-2.4.22-itanium-di_0.37_ia64.udeb
ext3-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
  to pool/main/l/linux-kernel-di/ext3-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
ext3-modules-2.4.22-speakup-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/ext3-modules-2.4.22-speakup-di_0.37_i386.udeb
ext3-modules-2.4.24-1-386-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/ext3-modules-2.4.24-1-386-di_0.37_i386.udeb
ext3-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  to pool/main/l/linux-kernel-di/ext3-modules-2.4.24-1-generic-di_0.37_alpha.udeb
fat-modules-2.4.20-amiga-di_0.37_m68k.udeb
  to pool/main/l/linux-kernel-di/fat-modules-2.4.20-amiga-di_0.37_m68k.udeb
fat-modules-2.4.22-itanium-di_0.37_ia64.udeb
  to pool/main/l/linux-kernel-di/fat-modules-2.4.22-itanium-di_0.37_ia64.udeb
fat-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
  to pool/main/l/linux-kernel-di/fat-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
fat-modules-2.4.22-speakup-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/fat-modules-2.4.22-speakup-di_0.37_i386.udeb
fat-modules-2.4.24-1-386-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/fat-modules-2.4.24-1-386-di_0.37_i386.udeb
fb-modules-2.4.22-itanium-di_0.37_ia64.udeb
  to pool/main/l/linux-kernel-di/fb-modules-2.4.22-itanium-di_0.37_ia64.udeb
fb-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
  to pool/main/l/linux-kernel-di/fb-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
fb-modules-2.4.22-speakup-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/fb-modules-2.4.22-speakup-di_0.37_i386.udeb
fb-modules-2.4.24-1-386-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/fb-modules-2.4.24-1-386-di_0.37_i386.udeb
fb-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  to pool/main/l/linux-kernel-di/fb-modules-2.4.24-1-generic-di_0.37_alpha.udeb
firewire-core-modules-2.4.22-itanium-di_0.37_ia64.udeb
  to pool/main/l/linux-kernel-di/firewire-core-modules-2.4.22-itanium-di_0.37_ia64.udeb
firewire-core-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
  to 
pool/main/l/linux-kernel-di/firewire-core-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
firewire-core-modules-2.4.22-speakup-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/firewire-core-modules-2.4.22-speakup-di_0.37_i386.udeb
firewire-core-modules-2.4.24-1-386-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/firewire-core-modules-2.4.24-1-386-di_0.37_i386.udeb
floppy-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
  to 
pool/main/l/linux-kernel-di/floppy-modules-2.4.22-powerpc-small-di_0.37_powerpc.udeb
floppy-modules-2.4.22-speakup-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/floppy-modules-2.4.22-speakup-di_0.37_i386.udeb
floppy-modules-2.4.24-1-386-di_0.37_i386.udeb
  to pool/main/l/linux-kernel-di/floppy-modules-2.4.24-1-386-di_0.37_i386.udeb
hfs-modules-2.4.22-powerpc-di_0.37_powerpc.udeb
  to pool/main/l/linux-kern

linux-kernel-di override disparity

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

fat-modules-2.4.22-itanium-di_0.37_ia64.udeb: package says priority is standard, 
override says extra.
fat-modules-2.4.22-speakup-di_0.37_i386.udeb: package says priority is standard, 
override says extra.
fat-modules-2.4.24-1-386-di_0.37_i386.udeb: package says priority is standard, 
override says extra.

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]

Re: Sparc d-i status

2004-02-24 Thread Ben Collins

On Wed, Feb 25, 2004 at 12:23:34AM -0500, Jeff Bailey wrote:
> On Tue, 2004-02-24 at 11:26, Ben Collins wrote:
> 
> > > Hmm...  Why don't we just use parted for now, until a better solution
> > > comes around?  It's in the archive, and AFAICT supports Sparc.  (ia64
> > > uses it right now, too)
> 
> > I know it supports sparc. I worked a long time ago to get the sun
> > partition support into that.
> 
> Nice!
> 
> > > > we also need a silo-installer
> > > 
> > > Right.  Any takers? =)
> > 
> > Obviously, that's a "me" :)
> 
> Actually, I had been hoping that since we have grub-installer to model
> after, this should be in the category "things anyone who cares about
> Sparc" can do, as opposed to the "benc and davem are the only ones with
> a clue how to fix this" category... =)  Your call, though.

Not sure what this has to do with Dave, but it's in the category of "I'm
the silo maintainer, let me handle it, rather than letting someone else
do it and end up asking me tons of questions or not getting it right the
first time".

-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/


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

Bug#234681: Cannot select keyboard type and layout with powerpc bus. card iso

Package: installation-reports

Debian-installer-version: February 24, 2004 -  
http://gluck.debian.org/cdimage/testing/daily/powerpc/20040223/sarge- 
powerpc-businesscard.iso
uname -a: N/A, install could not complete
Date: 02/24/2004, 20:30 EST
Method: Boot from CD holding down C key after chime, business card  
install of unstable using debian.mirrors.pair.com

Machine: Apple Titanium PowerBook G4 500MHz
Processor: G4 500 MHz
Memory: 512MB RAM
Root Device: IDE
Root Size/partition table: N/A, install could not complete; could not  
reach the Detect Hardware menu option
Output of lspci: N/A, install could not complete

Base System Installation Checklist:

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

Upon choosing the keyboard layout menu option, the installer responds  
by looping back to the same screen.  The keyboard type and layout  
cannot be chosen, and installation cannot progress beyond loading the  
installer modules.



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

Processing of linux-kernel-di_0.37_source+i386+alpha+ia64+m68k+mips+mipsel+powerpc+sparc.changes

linux-kernel-di_0.37_source+i386+alpha+ia64+m68k+mips+mipsel+powerpc+sparc.changes 
uploaded successfully to localhost
along with the files:
  linux-kernel-di_0.37.dsc
  linux-kernel-di_0.37.tar.gz
  kernel-image-2.4.24-1-386-di_0.37_i386.udeb
  nic-modules-2.4.24-1-386-di_0.37_i386.udeb
  nic-extra-modules-2.4.24-1-386-di_0.37_i386.udeb
  nic-shared-modules-2.4.24-1-386-di_0.37_i386.udeb
  serial-modules-2.4.24-1-386-di_0.37_i386.udeb
  ppp-modules-2.4.24-1-386-di_0.37_i386.udeb
  isa-pnp-modules-2.4.24-1-386-di_0.37_i386.udeb
  socket-modules-2.4.24-1-386-di_0.37_i386.udeb
  ide-modules-2.4.24-1-386-di_0.37_i386.udeb
  ide-core-modules-2.4.24-1-386-di_0.37_i386.udeb
  cdrom-core-modules-2.4.24-1-386-di_0.37_i386.udeb
  cdrom-modules-2.4.24-1-386-di_0.37_i386.udeb
  firewire-core-modules-2.4.24-1-386-di_0.37_i386.udeb
  scsi-core-modules-2.4.24-1-386-di_0.37_i386.udeb
  scsi-modules-2.4.24-1-386-di_0.37_i386.udeb
  scsi-common-modules-2.4.24-1-386-di_0.37_i386.udeb
  scsi-extra-modules-2.4.24-1-386-di_0.37_i386.udeb
  plip-modules-2.4.24-1-386-di_0.37_i386.udeb
  floppy-modules-2.4.24-1-386-di_0.37_i386.udeb
  loop-modules-2.4.24-1-386-di_0.37_i386.udeb
  ipv6-modules-2.4.24-1-386-di_0.37_i386.udeb
  ext3-modules-2.4.24-1-386-di_0.37_i386.udeb
  jfs-modules-2.4.24-1-386-di_0.37_i386.udeb
  reiserfs-modules-2.4.24-1-386-di_0.37_i386.udeb
  fat-modules-2.4.24-1-386-di_0.37_i386.udeb
  md-modules-2.4.24-1-386-di_0.37_i386.udeb
  usb-modules-2.4.24-1-386-di_0.37_i386.udeb
  usb-storage-modules-2.4.24-1-386-di_0.37_i386.udeb
  brltty-modules-2.4.24-1-386-di_0.37_i386.udeb
  fb-modules-2.4.24-1-386-di_0.37_i386.udeb
  input-modules-2.4.24-1-386-di_0.37_i386.udeb
  irda-modules-2.4.24-1-386-di_0.37_i386.udeb
  parport-modules-2.4.24-1-386-di_0.37_i386.udeb
  nic-pcmcia-modules-2.4.24-1-386-di_0.37_i386.udeb
  pcmcia-modules-2.4.24-1-386-di_0.37_i386.udeb
  nic-modules-2.4.22-speakup-di_0.37_i386.udeb
  nic-extra-modules-2.4.22-speakup-di_0.37_i386.udeb
  nic-shared-modules-2.4.22-speakup-di_0.37_i386.udeb
  serial-modules-2.4.22-speakup-di_0.37_i386.udeb
  ppp-modules-2.4.22-speakup-di_0.37_i386.udeb
  isa-pnp-modules-2.4.22-speakup-di_0.37_i386.udeb
  socket-modules-2.4.22-speakup-di_0.37_i386.udeb
  ide-modules-2.4.22-speakup-di_0.37_i386.udeb
  ide-core-modules-2.4.22-speakup-di_0.37_i386.udeb
  cdrom-core-modules-2.4.22-speakup-di_0.37_i386.udeb
  cdrom-modules-2.4.22-speakup-di_0.37_i386.udeb
  firewire-core-modules-2.4.22-speakup-di_0.37_i386.udeb
  scsi-core-modules-2.4.22-speakup-di_0.37_i386.udeb
  scsi-modules-2.4.22-speakup-di_0.37_i386.udeb
  scsi-common-modules-2.4.22-speakup-di_0.37_i386.udeb
  scsi-extra-modules-2.4.22-speakup-di_0.37_i386.udeb
  plip-modules-2.4.22-speakup-di_0.37_i386.udeb
  floppy-modules-2.4.22-speakup-di_0.37_i386.udeb
  loop-modules-2.4.22-speakup-di_0.37_i386.udeb
  ipv6-modules-2.4.22-speakup-di_0.37_i386.udeb
  ext3-modules-2.4.22-speakup-di_0.37_i386.udeb
  jfs-modules-2.4.22-speakup-di_0.37_i386.udeb
  reiserfs-modules-2.4.22-speakup-di_0.37_i386.udeb
  fat-modules-2.4.22-speakup-di_0.37_i386.udeb
  md-modules-2.4.22-speakup-di_0.37_i386.udeb
  usb-modules-2.4.22-speakup-di_0.37_i386.udeb
  usb-storage-modules-2.4.22-speakup-di_0.37_i386.udeb
  brltty-modules-2.4.22-speakup-di_0.37_i386.udeb
  fb-modules-2.4.22-speakup-di_0.37_i386.udeb
  input-modules-2.4.22-speakup-di_0.37_i386.udeb
  irda-modules-2.4.22-speakup-di_0.37_i386.udeb
  parport-modules-2.4.22-speakup-di_0.37_i386.udeb
  nic-pcmcia-modules-2.4.22-speakup-di_0.37_i386.udeb
  pcmcia-modules-2.4.22-speakup-di_0.37_i386.udeb
  kernel-image-2.4.24-1-generic-di_0.37_alpha.udeb
  nic-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  nic-extra-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  nic-shared-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  serial-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  ppp-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  isa-pnp-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  socket-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  ide-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  ide-core-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  cdrom-core-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  cdrom-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  scsi-core-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  scsi-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  scsi-common-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  scsi-extra-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  plip-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  ipv6-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  ext3-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  jfs-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  reiserfs-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  md-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  usb-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  usb-storage-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  brltty-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  fb-modules-2.4.24-1-generic-di_0.37_alpha.udeb
  parport-modules-2.4.24-1-generic-d

Re: Sparc d-i status

On Tue, 2004-02-24 at 11:26, Ben Collins wrote:

> > Hmm...  Why don't we just use parted for now, until a better solution
> > comes around?  It's in the archive, and AFAICT supports Sparc.  (ia64
> > uses it right now, too)

> I know it supports sparc. I worked a long time ago to get the sun
> partition support into that.

Nice!

> > > we also need a silo-installer
> > 
> > Right.  Any takers? =)
> 
> Obviously, that's a "me" :)

Actually, I had been hoping that since we have grub-installer to model
after, this should be in the category "things anyone who cares about
Sparc" can do, as opposed to the "benc and davem are the only ones with
a clue how to fix this" category... =)  Your call, though.

Tks,
Jeff Bailey

-- 
I never know what to expect when you respond to my postings. No insult
intended, you are merely a surprise :)
 - Carlos O'Donnell

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

nobootloader_0.0.6_powerpc.changes ACCEPTED


Accepted:
nobootloader_0.0.6.dsc
  to pool/main/n/nobootloader/nobootloader_0.0.6.dsc
nobootloader_0.0.6.tar.gz
  to pool/main/n/nobootloader/nobootloader_0.0.6.tar.gz
nobootloader_0.0.6_all.udeb
  to pool/main/n/nobootloader/nobootloader_0.0.6_all.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]

Processing of nobootloader_0.0.6_powerpc.changes

nobootloader_0.0.6_powerpc.changes uploaded successfully to localhost
along with the files:
  nobootloader_0.0.6.dsc
  nobootloader_0.0.6.tar.gz
  nobootloader_0.0.6_all.udeb

Greetings,

Your Debian queue daemon


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

Re: nobootloader oops

On Tue, Feb 24, 2004 at 03:08:30PM -0600, Stephen R Marenka wrote:
> I just fixed a thinko in nobootloader, which causes it to always fail.
> Please upload the new version.

Done.

-- 
Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/


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

ddetect_0.68_i386.changes ACCEPTED


Accepted:
archdetect_0.68_i386.udeb
  to pool/main/d/ddetect/archdetect_0.68_i386.udeb
ddetect_0.68.dsc
  to pool/main/d/ddetect/ddetect_0.68.dsc
ddetect_0.68.tar.gz
  to pool/main/d/ddetect/ddetect_0.68.tar.gz
ethdetect_0.68_all.udeb
  to pool/main/d/ddetect/ethdetect_0.68_all.udeb
hw-detect-full_0.68_all.udeb
  to pool/main/d/ddetect/hw-detect-full_0.68_all.udeb
hw-detect_0.68_all.udeb
  to pool/main/d/ddetect/hw-detect_0.68_all.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#233294: installation report - tar: Unrecognised file type

On Tue, Feb 24, 2004 at 02:28:50PM -0500, Barry Hawkins wrote:
>   What is the status on this bug?  I tried to install again on 02/22 
>   and still got the failure at perl-base, even using the 02/21 daily.  I 
> don't understand how people are still able to test the installer if 
> this is happening.

A fixed package has been uploaded, but the i386 floppy images are
still broken, since the root floppy hasn't built since the fixed
package was uploaded.  This should be fixed in tomorrow's images.
I don't know about the other images.

-- 
Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/

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

Re: debootstrap fails on hard links in tar files

On Tue, Feb 24, 2004 at 11:26:49PM +0100, Dimitry Andric wrote:
> For some days now, I've been trying to complete a successful
> installation of Sid into a VMware box, with the 20040209 version of
> the debian installer boot floppies.
> 
> However, every install I try eventually bombs out at the "installing
> base system" stage, with an error "The debootstrap program exited with
> an error (return value 1)".  Checking out /var/log/messages shows as
> last line:
> 
>   tar: Unrecognised file type
> 
> Then I ran debootstrap from the Alt-F2 shell, as follows:
> 
>   debootstrap --arch i386 sid /target
> 
> which first checks and validates all debs OK, but then fails while
> unpacking:
> 
>   ...
>   I: Extracting libblkid1...
>   I: Extracting e2fsprogs...
>   tar: Unrecognised file type
> 
> When I unpack the said e2fsprogs_1.34+1.35-WIP-2004.01.31-2_i386.deb
> file, it turns out that the contained data.tar.gz file contains a hard
> link, which doesn't seem to be supported by busybox's tar:
> 
>   # ar -x 
> /target/var/cache/apt/archives/e2fsprogs_1.34\+1.35-WIP-2004.01.31-2_i386.deb
>   # tar -xvzf data.tar.gz
>   .
>   ./sbin
>   ./mke2fs
>   ./mkfs.ext2
>   tar: Unrecognised file type
> 
> Note that this is BusyBox v1.00-pre5 (Debian 20040101-6). After some
> searching around, I found this commit:
> 
>   
> http://www.busybox.net/cgi-bin/cvsweb/busybox/archival/libunarchive/get_header_tar.c#rev1.31
> 
> and this busybox-cvs-udeb bug report:
> 
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=233627
> 
> So it seems there have been some problems before with different tar
> formats, and I guess they are caused by some "too old" or "too new"
> format tar files being released lately?  I hope either the tar files
> or busybox can be fixed.  The former seems quite unlikely, but the
> latter shouldn't be too hard.
> 
> I know I did complete a few debian-installer installations
> successfully before, some weeks ago, so this must have been a quite
> recent thing.  Now that I'm writing this, some messages "tar: removing
> leading / from paths" also come to my mind...
> 
> Please accept my apologies if this has been covered before, but Google
> and the mail archive search turned up nothing for the obvious
> keywords.  So from now on, they hopefully will. ;)

See bug 233627.

-- 
Matt Kraai[EMAIL PROTECTED]http://ftbfs.org/


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

Processing of ddetect_0.68_i386.changes

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

Greetings,

Your Debian queue daemon


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

Re: Automated installer / kickstart instructions?

Erik Dykema wrote:
> Hi-
>   Thanks for the links to the other automatic installation packages. 
> Looking at what they do, they confirm that what I think I want to do is 
> use the actual debian-installer, as suggested where you wrote:
> 
> 1) Manual install.
> 2) Save the answers from the debconf database into a file.
> 3) Put the file in a preseeding udeb.
> 
>   Can anyone expand on points two and three?

The debconf database is in /var/log/debian-installer/cdebconf on the
installed system.

> or what/where the debconf database is, or once I have them what format to 
> put them into in the 'file', and once I have that file how to make it 
> into a 'preseeding udeb'.  I taught myself the bare minimums of making 
> regular deb's last week, is it a similar process?

I guess you could put the files into a deb, moved to /var/lib/cdebconf,
and then you'd have to work out how to make d-i load this deb. It might
be better though to have the preseeding deb get the files from the
network, then you'd not need to change the installation media, assuming
the preseeder was on the default media.

-- 
see shy jo

signature.asc
Description: Digital signature

Bug#195704: Introduction for valves

2004-02-24 Thread liangq

  Tang Shan Hong Yuan Valve Industry Co. is located in Tangshan, Hebei province, 
China,
 140 kilometers southeast to Beijing. Hebei province is famous for the Hometown of 
Casting. 
 Our factory is mainly in wafer butterfly valve, lug butterfly valve, flanged 
butterfly valve,
 wafer check valve, balancing valve, lift check valve, swing check valve and Y 
strainer.
 With the export experience, we have been able to provide products with 
 GB, API,ANSI, BS, AS, DIN, ISO, JIS, and various world standards. Beside our regular 
products, 
 we also can make products according to customers' requirement. 

 Sales Office: 609 Room,NO.101, Jian Hua East Road, Tang Shan, He Bei, China
 Tel: 86-315-2728326 Fax:86-315-2728356
 Email: [EMAIL PROTECTED]
 Website: http://www.hyvp.com
 Casting Foundry: Zuojiawu Town,Fengrun county,TangShan , Hebei , China
 Tel: 0086-315-5575326 
 Machining factory:  NO.106 Daqing Road Tang Shan , Hebei , China
 Tel: 0086-315-2808326 


price sheet.xls
Description: Binary data

Re: Automated installer / kickstart instructions?

Hi-
	Thanks for the links to the other automatic installation packages. 
Looking at what they do, they confirm that what I think I want to do is 
use the actual debian-installer, as suggested where you wrote:

1) Manual install.
2) Save the answers from the debconf database into a file.
3) Put the file in a preseeding udeb.
	Can anyone expand on points two and three?  If I could get it working 
for myself I'd be happy to contribute some more complete documentation 
for this part.
	I have the manual install part down, it's the rest that I'm not clear 
about.  I'm not sure how to get answers out of the debconf database, or 
what/where the debconf database is, or once I have them what format to 
put them into in the 'file', and once I have that file how to make it 
into a 'preseeding udeb'.  I taught myself the bare minimums of making 
regular deb's last week, is it a similar process?

Thanks,
Erik


Geert Stappers wrote:
> +
> +debian-installer
> +
> +this section needs love & care
> +
> +
> +Manual install
> +
> +
> +
> +Save the answers from the debconf database into a file.
> +
> +
> +
> +Put the file in preseeding udeb
On Tue, Feb 24, 2004 at 03:51:18PM -0500, Erik Dykema wrote:

Hi-
	A while back there was a lot of talk about automating installations, 
and in many places it was claimed that it actually worked.  Does anyone 
have instructions for how to actually do it?
	For example, if I wanted to automate a network install, and I had done 
the homework, including:

	Install first by hand making sure things work.
	Making notes of all my choices and the answers to the questions that it 
asks me (alternately keystrokes?)

	How would I then translate this into an automated installation?

	I know of FAI and have been trying to use it, but it is extremely 
complicated and provides a lot of functionality that most users (even 
most administrators!) don't need.. I just want to use the regular 
debian-installer without having to sit here and press enter and type in 
my mirror location every time :)


AFAIK:

--- doc/manual/en/install-methods/automatic-install.xml 15 Jun 2003 17:39:02 - 
 1.3
+++ doc/manual/en/install-methods/automatic-install.xml 24 Feb 2004 21:40:28 -
@@ -9,8 +9,28 @@
 automatic installations. Debian packages intended for this include
 fai (which uses an install server),
 replicator,
-systemimager, and
-autoinstall.
+systemimager,
+autoinstall, and
+debian-installer.


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

Re: Installation report - failed install

2004-02-24 Thread David Fries

What about compiling in CONFIG_IDEDISK_STROKE?  I wouldn't think that
it would hurt anything and it is required on older systems.

> [EMAIL PROTECTED] Wrote:
>
> It seems that debootstrap from unstable is already aware of the
> libdevmapper1.00 dependency. See
> http://packages.debian.org/changelogs/pool/main/d/debootstrap/debootstrap_0.2.27/changelog
> 
> 
> > Two big problems, libdevmapper1.00 now needs to be installed,
> > Another system with a 120GB drive requires CONFIG_IDEDISK_STROKE
> > compiled into the kernel to see the entire drive.
> 
> > I used the three floppy images (boot, root, net drivers) off the
> > business card iso from here.
> > http://gluck.debian.org/cdimage/testing/daily/i386/20040220/

-- 
David Fries <[EMAIL PROTECTED]>
http://fries.net/~david/pgpkey.txt


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

unsubscribe

2004-02-24 Thread Lawrence Lee




---
Lawrence Lee
[EMAIL PROTECTED]
http://hills.ccsf.edu/~llee32/index.html


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

Bug#234663: countrychooser: should not remove @euro modifier

2004-02-24 Thread Denis Barbier

Package: countrychooser
Severity: normal

During installation in French, the fr_FR locale is selected whereas
it is set to [EMAIL PROTECTED] in languagechooser.  As #232049 is fixed, a
workaround is to set this default locale to [EMAIL PROTECTED]
in languagechooser (and of course add ISO-8859-15 encoding to all
@euro locales defined there).

Denis


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

Re: [d-i manual] repetitious para

2004-02-24 Thread John Buttery

* "Steinar H. Gunderson" <[EMAIL PROTECTED]> [2004-02-24 13:15:08 +0100]:
> Or perhaps more the _packaging_. Debian has lots and lots of software
> packaged, most of which is of extremely good quality. The Debian
> policy is IMO a lot more important than using a specific package
> system.

  Yeah, I was sort of including the QA process under the umbrella of
the "package management" term, but you're right that the two concepts
should be brought up separately.  After all, it's only the heightened
attention to detail and diligence that allows the tools to be as strong
as they are in the first place (see my comment in the previous email
about apt-listchanges).

  Speaking of apt-listchanges, I know this is OT but does anyone happen
to know why, as of a not-so-recent-anymore version, the followup
changelog mailings are showing up with everything all jumbled together,
like there aren't any line breaks or something?  I thought it might be a
character set thing, but I tried both us-ascii and iso-8859-1.

-- 
  John  ! EVERYTHING I EVER NEEDED TO KNOW I LEARNED FROM GAMING
 Buttery!  Never summon anything bigger than your head.
www.io.c!  Don't sweat the small stuff.  Gnomes, for example.
om/~john!  A rod of silence means never having to say you're sorry.


signature.asc
Description: Digital signature

Processed: Re: Bug#232071: base-config: Output messed up with ISO-8859-2 locales

Processing commands for [EMAIL PROTECTED]:

> tags 232071 + pending
Bug#232071: base-config: Output messed up with ISO-8859-2 locales
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]

Bug#232071: base-config: Output messed up with ISO-8859-2 locales

2004-02-24 Thread Denis Barbier

tags 232071 + pending
thanks

On Thu, Feb 12, 2004 at 06:05:19PM +0100, Miroslav Kure wrote:
> I did two more test installs (with 20040209 iso) and, as expected,
> this problem also affects other ISO-8859-2 languages (I tried Slovak
> and Polish).

Miroslav, I just committed a fix for termwrap, could you please check if
it works as expected?  I think so, but cannot read any ISO-8859-2 language.

Denis


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

Re: debootstrap fails on hard links in tar files

Dimitry Andric wrote:
> For some days now, I've been trying to complete a successful
> installation of Sid into a VMware box, with the 20040209 version of
> the debian installer boot floppies.

Upgrade. This was fixed in busybox some days ago, but not back on the
9th!

-- 
see shy jo


signature.asc
Description: Digital signature

COMPILING KERNEL FOR LAPTOP, PLAIN TEXT :-)

2004-02-24 Thread Wes Reneau

I'm at a loss for words due to my own ignorance but I'm not sure what to 
do at this point.

I've compiled the 2.6.3 kernel by "make mrproper, make xconfig (saved 
.config), make-kpkg --revision=custom1.0 kernel_image modues_image.

The process runs thru w/ a few errors as listed below:

/I've retyped the error so syntax may be just a bit off

/

   CC [M]drivers/pcmcia/i82365.o

   drivers/pcmcia/i82365.c: In funciton 'is alive':

   drivers/pcmica/i82365.c:665: warning: 'check_region' is depreciated
   (declard at include/linux/ioport.h:121)
these type of errors continue untill it's thru processing the pcmcia 
drivers with the words following In function that read 'isa_probe', 
'i365_set_io_map', tcic_set_io_map'.

Now furthere down I see other /drivers/pcmcia/i82092.ko compile with no 
errors.  Again, I have no idea why this is occuring.

When the compiler reaches the "Linux PCMCIA Configuration Script" I get 
this:

   ** Your kernel is configured with PCMCIA driver support.  Therefore

   **  'make all' will compile the PCMCIA utilities but not the drivers.

   **   See README-2.4 if this is not what you intended

   IMPORTANT NOTE FOR DEBIAN USERS
   This means that a pcmcia-modules package will not be built.
Any help would be appreciated.

PS:  Now I've recompiled again tweaking other hardware and I'm getting a 
new error soundcore: version mage '2.6.3 PENTIUMIII gcc-3.3' should be 
'2.6.3 PENTIUMIII GCC-2.95'

tHANKS

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

Re: m68k port status update

Stephen R Marenka wrote:
> On Tue, Feb 24, 2004 at 01:51:38PM -0500, Joey Hess wrote:
> > Wouter Verhelst wrote:
> > > You don't. In both cases, you need to download an image, boot the native
> > > OS, start a kernel loader which will put the image up as a RAMdisk, and
> > > go from there. The difference is that the CD-ROM image will get its
> > > udebs from CDROM, whereas the network image will work with the network.
> > 
> > So it's much more like the hd-media stuff we have on i386.
> 
> Yes, except not mounted loopback.
> 
> A native bootloader, kernel, and ramdisk all reside on the native 
> filesystem. Amiga and mac can *only* be booted this way.
> 
> boot-floppies delivered a tarball which contained all three of these
> things for download onto a native partition. I'm not sure I intend to
> emulate that, though.
> 
> How about I create a new type called nativehd or something?

With i386's hd-media, only the cdrom iso is loopback mounted, the
initrd, kernel, and bootloader can all be on the HD the same way.

I think the important thing is to name it something that will make sense
to users, since the names are used for directory names.

-- 
see shy jo


signature.asc
Description: Digital signature

[no subject]

2004-02-24 Thread Daniel R. Sparks









 

 

Daniel R. Sparks

 

   Hy-Tec

Business Equipment

 

266 Dundee Ave.

Elgin, IL 60120

 

(847) 741-4595

 

dasparkss@sbcglobal.net

Processed: Re: Bug#226471: lilo: default lilo.conf has broken LinuxOLD entry

Processing commands for [EMAIL PROTECTED]:

> reassign 226471 lilo-installer
Bug#226471: lilo: default lilo.conf has broken LinuxOLD entry
Bug reassigned from package `lilo' to `lilo-installer'.

> 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]

problem

2004-02-24 Thread dbrown53




I have run into difficulty trying to install Debian 
GNU/Linux 3.Or2 i386 from Linux Central. While trying to install the base system 
I first get:
 
warning   
file:/instmnt/pool/main/n/nano/nano_1.0.6-3_i386.deb was corrupt
 
then:
 
error   Couldn't download nano
 
Then I am returned to the screen to install the base 
system.
 
Can you help?
 
Thanks,
Doug Brown

Re: release status

2004-02-24 Thread Thorsten Sauter


Hello all,

* Joey Hess <[EMAIL PROTECTED]> [2004-02-24 02:39]:
|  - Get daily builds working.
|   Currently working: alpha, i386, ia64, m68k, sparc
|   Hppa's daily build has been down since the 17th.

I'm working on this issue. Since we have switched to the new
build-system hppa doesn't produce any image. It simply create a boot.img
file, but nothing more.

I need time to have a depther look into the new build system.


Bye
Thorsten


-- 
Thorsten Sauter
<[EMAIL PROTECTED]>

(Is there life after /sbin/halt -p?)


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

debootstrap fails on hard links in tar files

2004-02-24 Thread Dimitry Andric

Hi,

For some days now, I've been trying to complete a successful
installation of Sid into a VMware box, with the 20040209 version of
the debian installer boot floppies.

However, every install I try eventually bombs out at the "installing
base system" stage, with an error "The debootstrap program exited with
an error (return value 1)". Checking out /var/log/messages shows as
last line:

tar: Unrecognised file type

Then I ran debootstrap from the Alt-F2 shell, as follows:

debootstrap --arch i386 sid /target

which first checks and validates all debs OK, but then fails while
unpacking:

...
I: Extracting libblkid1...
I: Extracting e2fsprogs...
tar: Unrecognised file type

When I unpack the said e2fsprogs_1.34+1.35-WIP-2004.01.31-2_i386.deb
file, it turns out that the contained data.tar.gz file contains a hard
link, which doesn't seem to be supported by busybox's tar:

# ar -x /target/var/cache/apt/archives/e2fsprogs_1.34\+1.35-WIP-2004.01.31-2_i386.deb
# tar -xvzf data.tar.gz
.
./sbin
./mke2fs
./mkfs.ext2
tar: Unrecognised file type

Note that this is BusyBox v1.00-pre5 (Debian 20040101-6). After some
searching around, I found this commit:

http://www.busybox.net/cgi-bin/cvsweb/busybox/archival/libunarchive/get_header_tar.c#rev1.31

and this busybox-cvs-udeb bug report:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=233627

So it seems there have been some problems before with different tar
formats, and I guess they are caused by some "too old" or "too new"
format tar files being released lately? I hope either the tar files
or busybox can be fixed. The former seems quite unlikely, but the
latter shouldn't be too hard.

I know I did complete a few debian-installer installations
successfully before, some weeks ago, so this must have been a quite
recent thing. Now that I'm writing this, some messages "tar: removing
leading / from paths" also come to my mind...

Please accept my apologies if this has been covered before, but Google
and the mail archive search turned up nothing for the obvious
keywords. So from now on, they hopefully will. ;)

Cheers,
Dimitry

pgp0.pgp
Description: PGP signature

Re: Bug#226471: lilo: default lilo.conf has broken LinuxOLD entry

2004-02-24 Thread Andrés Roldán

reassign 226471 lilo-installer
thanks

I think it can be marked as closed but I leave it under your 
consideration.

Robert Millan <[EMAIL PROTECTED]> writes:

> Package: lilo
> Version: 1:22.2-3
> Severity: important
>
> Default lilo.conf found in a Woody system has a broken LinuxOLD entry. It
> refers to /initrd.img instead of /initrd.img.old, which causes boot to break
> when the kernel image and the modules in initrd do not correspond to the same
> version of Linux.
>
> The following change in lilo.conf would fix it:
>
> --- /etc/lilo.conf~ Tue Dec  2 01:29:28 2003
> +++ /etc/lilo.conf  Tue Jan  6 23:28:46 2004
> @@ -116,7 +116,7 @@
>   
>  image=/vmlinuz.old
> label=LinuxOLD
> -   initrd=/initrd.img
> +   initrd=/initrd.img.old
> read-only
> optional
>  #  restricted
>
>

-- 
Andrés Roldán <[EMAIL PROTECTED]>
GPG Key-ID: 0xB29396EB
http://people.fluidsignal.com/~aroldan


pgp0.pgp
Description: PGP signature

Re: Automated installer / kickstart instructions?

2004-02-24 Thread Geert Stappers

On Tue, Feb 24, 2004 at 03:51:18PM -0500, Erik Dykema wrote:
> Hi-
>   A while back there was a lot of talk about automating installations, 
> and in many places it was claimed that it actually worked.  Does anyone 
> have instructions for how to actually do it?
>   For example, if I wanted to automate a network install, and I had done 
> the homework, including:
> 
>   Install first by hand making sure things work.
>   Making notes of all my choices and the answers to the questions that it 
> asks me (alternately keystrokes?)
> 
>   How would I then translate this into an automated installation?
> 
>   I know of FAI and have been trying to use it, but it is extremely 
> complicated and provides a lot of functionality that most users (even 
> most administrators!) don't need.. I just want to use the regular 
> debian-installer without having to sit here and press enter and type in 
> my mirror location every time :)

AFAIK:

--- doc/manual/en/install-methods/automatic-install.xml 15 Jun 2003 17:39:02 - 
 1.3
+++ doc/manual/en/install-methods/automatic-install.xml 24 Feb 2004 21:40:28 -
@@ -9,8 +9,28 @@
 automatic installations. Debian packages intended for this include
 fai (which uses an install server),
 replicator,
-systemimager, and
-autoinstall.
+systemimager,
+autoinstall, and
+debian-installer.
  
 
+
+
+debian-installer
+
+this section needs love & care
+
+
+Manual install
+
+
+
+Save the answers from the debconf database into a file.
+
+
+
+Put the file in preseeding udeb
+
+
+
  

> 
> thanks,
> Erik
> 

Geert Stappers


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

Bug#233294: installation report - tar: Unrecognised file type

On Feb 24, 2004, at 3:53 PM, Glenn McGrath wrote:

On Tue, 24 Feb 2004 14:28:50 -0500
Barry Hawkins <[EMAIL PROTECTED]> wrote:
What is the status on this bug?  I tried to install again on
02/22 and
still got the failure at perl-base, even using the 02/21 daily.  I
don't understand how people are still able to test the installer if
this is happening.
I can extract perl-base deb using upstream busybox and
busybox-cvs-udeb_20040101-7
As far as i can see this bug is fixed.

Glenn

Glenn,
	Thanks for the reply.  I will try to install again tonight.  When you 
say "using upstream busybox and busybox-cvs-udeb_20040101-7", do I take 
that to mean that I should be able to successfully install using the 
daily sarge-powerpc-businesscard.iso from 02/21/2004?

Regards,
--
Barry C. Hawkins
All Things Computed
site: www.allthingscomputed.com
weblog: www.yepthatsme.com


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

Bug#233135: marked as done (base-config no longer works with locale el_GR.UTF-8)

Your message dated Tue, 24 Feb 2004 15:32:08 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#233135: fixed in base-config 2.13
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--
Received: (at submit) by bugs.debian.org; 17 Feb 2004 02:09:46 +
>From [EMAIL PROTECTED] Mon Feb 16 18:09:46 2004
Return-path: <[EMAIL PROTECTED]>
Received: from ppp3-adsl-91.ath.forthnet.gr (silmaril.devel.internal.bullet.gr) 
[212.251.109.91] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AsugB-00027s-00; Mon, 16 Feb 2004 18:09:43 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Konstantinos Margaritis <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: base-config no longer works with locale el_GR.UTF-8
Bcc: Konstantinos Margaritis <[EMAIL PROTECTED]>
X-Mailer: reportbug 2.39
Date: Tue, 17 Feb 2004 04:08:28 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_16 
(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_02_16
X-Spam-Level: 

Package: base-config
Version: 2.12
Severity: normal
Tags: l10n

After the install of Debian, using d-i, until the previous version
base-config recognized the locale el_GR.UTF-8 (which is the default for
the Greek language, since we are moving to UTF-8 instead of the older
ISO-8859-7). This locale is set in d-i/tools/languagechooser/languagelist.
Now it reports the following message:

"warning: disabling unsupported locale el_GR.UTF-8"

Thanks.

Konstantinos

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux silmaril 2.4.24 #1 Fri Jan 30 03:06:17 EET 2004 i686
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8

Versions of packages base-config depends on:
ii  adduser 3.51 Add and remove users and groups
ii  apt 0.5.21   Advanced front-end for dpkg
ii  aptitude0.2.13-2 curses-based apt frontend
ii  bsdutils1:2.12-3 Basic utilities from 4.4BSD-Lite
ii  console-data2002.12.04dbs-28 Keymaps, fonts, charset maps, fall
ii  console-tools   1:0.2.3dbs-47Linux console and font utilities
ii  debconf 1.3.22   Debian configuration management sy
ii  debianutils 2.6.2Miscellaneous utilities specific t
ii  gettext-base0.13.1-2 GNU Internationalization utilities
ii  passwd  1:4.0.3-17   Change and administer password and

-- debconf information excluded


---
Received: (at 233135-close) by bugs.debian.org; 24 Feb 2004 20:38:13 +
>From [EMAIL PROTECTED] Tue Feb 24 12:38:13 2004
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AvjJl-0001RO-00; Tue, 24 Feb 2004 12:38:13 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1AvjDs-0006Is-00; Tue, 24 Feb 2004 15:32:08 -0500
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.43 $
Subject: Bug#233135: fixed in base-config 2.13
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 24 Feb 2004 15:32:08 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_22 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=HAS_BUG_NUMBER autolearn=no 
version=2.60-bugs.debian.org_2004_02_22
X-Spam-Level: 

Source: base-config
Source-Version: 2.13

We believe that the bug you reported is fixed in the latest version of
base-config, which is due to be installed in the Debian FTP archive:

base-config_2.13.dsc
  to pool/main/b/base-config/base-config_2.13.dsc
base-config_2.13.tar.gz
  to pool/main/b/base-config/base-config_2.13.tar.gz
base-config_2.13_all.deb
  to pool/main/b/base-config/base-config_2.13_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if

Bug#232547: marked as done (base-config: update of spanish manpages)

Your message dated Tue, 24 Feb 2004 15:32:08 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#232547: fixed in base-config 2.13
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; 13 Feb 2004 15:16:52 +
>From [EMAIL PROTECTED] Fri Feb 13 07:16:52 2004
Return-path: <[EMAIL PROTECTED]>
Received: from 81-203-235-224.user.ono.com (nahoo) [81.203.235.224] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Arf3j-0007MD-00; Fri, 13 Feb 2004 07:16:51 -0800
Received: from bennett by nahoo with local (Exim 4.30)
id 1Arf3f-vz-TW; Fri, 13 Feb 2004 16:16:47 +0100
Content-Type: multipart/mixed; boundary="===0730835447=="
MIME-Version: 1.0
From: Ruben Porras <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: base-config: update of spanish manpages
X-Mailer: reportbug 2.43
Date: Fri, 13 Feb 2004 16:16:33 +0100
Message-Id: <[EMAIL PROTECTED]>
Sender: Ruben Porras <[EMAIL PROTECTED]>
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
  using "From" header
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_12 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-1.1 required=4.0 tests=FROM_ENDS_IN_NUMS,HAS_PACKAGE,
UNWANTED_LANGUAGE_BODY autolearn=no 
version=2.60-bugs.debian.org_2004_02_12
X-Spam-Level: 

This is a multi-part MIME message sent by reportbug.

--===0730835447==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: base-config
Version: 2.11
Severity: minor
Tags: patch l10n

I've attached the patch.

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

Versions of packages base-config depends on:
ii  adduser 3.51 Add and remove users and groups
ii  apt 0.5.22   Advanced front-end for dpkg
hi  aptitude0.2.13.-1curses-based apt frontend
ii  bsdutils1:2.12-6 Basic utilities from 4.4BSD-Lite
ii  console-data2002.12.04dbs-28 Keymaps, fonts, charset maps, fall
ii  console-tools   1:0.2.3dbs-46Linux console and font utilities
ii  debconf 1.4.9Debian configuration management sy
ii  debianutils 2.6.2Miscellaneous utilities specific t
ii  gettext-base0.13.1-2 GNU Internationalization utilities
ii  passwd  1:4.0.3-17   Change and administer password and

-- debconf information excluded


--===0730835447==
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: attachment; filename="base-config.diff"

diff -u -N base-config.old/base-config.es.8 base-config/base-config.es.8
--- base-config.old/base-config.es.82003-11-02 21:34:48.0 +0100
+++ base-config/base-config.es.82004-02-13 16:13:54.0 +0100
@@ -1,7 +1,7 @@
 .\" (c) 2003 Software in the Public Interest
 .\" Esta traducción ha sido realizada por Rubén Porras Campo <[EMAIL PROTECTED]>
 .\" Está basada en la página de manual original:
-.\" versión 1.3 del CVS de
+.\" versión 1.5 del CVS de
 .\" /cvs/debian-doc/manpages/english/base-config/base-config.8
 
 .TH BASE-CONFIG 8
@@ -17,39 +17,53 @@
 momento posterior para realizar el mismo proceso de nuevo.
 .SH IMPLEMENTACIÓN
 .BR base-config
-está implementado como un script que ejecuta todos los programas en 
+genera un menú de elecciones con los contenidos de
 .BR /usr/lib/base-config/ ,
-siguiendo un orden numérico. Si el sistema es un sistema recién instalado,
-entonces todos los programas reciben "new" como primer argumento.
+y de las plantillas de debconf.
+.P
+Los ficheros .mnu de /usr/lib/base-config/ controlan si el elemento del menú
+aparece sólo en nuevas instalaciones (Only-New: true), si debconf puede estar
+siendo ejecutado en el momento en el que se ejecute el elemento (Debconf: true).
+Una opción numérica "Order" controla el lugar en el menú. Si el fichero .mnu
+contiene "Exit-Menu:true", base-config terminará después de ejectuar ese
+elemento del menú. Finalmente, una línea "Changes-Menu: true" hará que
+base-config

Bug#233262: marked as done (base-config: apt-setup template apt-setup/another incomplete in french)

Your message dated Tue, 24 Feb 2004 15:32:09 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#233262: fixed in base-config 2.13
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--
Received: (at submit) by bugs.debian.org; 17 Feb 2004 18:30:50 +
>From [EMAIL PROTECTED] Tue Feb 17 10:30:50 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 1At9zd-0006ce-00; Tue, 17 Feb 2004 10:30:49 -0800
Received: from localhost (localhost [127.0.0.1])
by kheops.homeunix.org (Postfix) with ESMTP
id 263524050; Tue, 17 Feb 2004 19:30:17 +0100 (CET)
Received: from kheops.homeunix.org ([127.0.0.1])
by localhost (kheops [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 28591-10; Tue, 17 Feb 2004 19:30:10 +0100 (CET)
Received: from mykerinos.kheops.frmug.org (mykerinos.kheops.frmug.org [192.168.1.3])
by kheops.homeunix.org (Postfix) with ESMTP
id 85C174057; Tue, 17 Feb 2004 19:30:00 +0100 (CET)
Received: by mykerinos.kheops.frmug.org (Postfix, from userid 7426)
id E5561D065; Tue, 17 Feb 2004 18:46:27 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Christian Perrier <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: base-config: apt-setup template apt-setup/another incomplete in french
X-Mailer: reportbug 2.47
Date: Tue, 17 Feb 2004 18:46:27 +0100
Message-Id: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p5 (Debian) at kheops.frmug.org
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_16 
(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_02_16
X-Spam-Level: 

Package: base-config
Version: 2.12
Severity: normal
Tags: d-i

When running in french language, the apt-setup/another template is
incomplete. It seems that the MESSAGE variable which is set just before
calling db_input is empty while it should contain the output of ngettext.

This is not french-specific, but happens also for german and, I guess, for
all languages but english (MESSAGE is not empty when using english)

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (400, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.2
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (ignored: LC_ALL set to fr_FR.UTF-8)

Versions of packages base-config depends on:
ii  adduser 3.51 Add and remove users and groups
ii  apt 0.5.22   Advanced front-end for dpkg
ii  aptitude0.2.14-3 curses-based apt frontend
ii  bsdutils1:2.12-6 Basic utilities from 4.4BSD-Lite
ii  console-data2002.12.04dbs-29 Keymaps, fonts, charset maps, fall
ii  console-tools   1:0.2.3dbs-48Linux console and font utilities
ii  debconf 1.4.10   Debian configuration management sy
ii  debianutils 2.6.2Miscellaneous utilities specific t
ii  gettext-base0.14.1-1 GNU Internationalization utilities
ii  passwd  1:4.0.3-17   Change and administer password and

-- debconf information excluded


---
Received: (at 233262-close) by bugs.debian.org; 24 Feb 2004 20:38:12 +
>From [EMAIL PROTECTED] Tue Feb 24 12:38:12 2004
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AvjJk-0001RC-00; Tue, 24 Feb 2004 12:38:12 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1AvjDt-0006Iu-00; Tue, 24 Feb 2004 15:32:09 -0500
From: Joey Hess <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.43 $
Subject: Bug#233262: fixed in base-config 2.13
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Tue, 24 Feb 2004 15:32:09 -0500
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_22 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=HAS_BUG_

Bug#233995: marked as done (base-config: l10n of apt-setup's mirror country list)

Your message dated Tue, 24 Feb 2004 15:32:09 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#233995: fixed in base-config 2.13
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

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

--
Received: (at submit) by bugs.debian.org; 21 Feb 2004 07:26:00 +
>From [EMAIL PROTECTED] Fri Feb 20 23:26:00 2004
Return-path: <[EMAIL PROTECTED]>
Received: from orochi.topstudio.co.jp (mail.topstudio.co.jp) [202.224.239.193] 
(postfix)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1AuRWR-0007X0-00; Fri, 20 Feb 2004 23:26:00 -0800
Received: from localhost (localhost [127.0.0.1])
by mail.topstudio.co.jp (Postfix) with ESMTP id 86126222F84
for <[EMAIL PROTECTED]>; Sat, 21 Feb 2004 16:25:56 +0900 (JST)
Received: from mail.topstudio.co.jp ([127.0.0.1])
by localhost (hydra [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
id 30482-07 for <[EMAIL PROTECTED]>;
Sat, 21 Feb 2004 16:25:56 +0900 (JST)
Received: from hellhound (orochi.topstudio.co.jp [202.224.239.193])
by mail.topstudio.co.jp (Postfix) with ESMTP id 4764A222F2C
for <[EMAIL PROTECTED]>; Sat, 21 Feb 2004 16:25:56 +0900 (JST)
Received: by hellhound (Postfix, from userid 1000)
id 1DE31214084; Sat, 21 Feb 2004 16:26:01 +0900 (JST)
From: Kenshi Muto <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: base-config: l10n of apt-setup's mirror country list
X-Debbugs-CC: Kenshi Muto <[EMAIL PROTECTED]>
User-Agent: SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 MULE XEmacs/21.4 
(patch 14) (Reasonable Discussion) (i386-debian-linux)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: multipart/mixed;
 boundary="Multipart_Sat_Feb_21_16:26:01_2004-1"
Message-Id: <[EMAIL PROTECTED]>
Date: Sat, 21 Feb 2004 16:26:01 +0900 (JST)
X-Virus-Scanned: by amavisd-new-20030616-p5 (Debian) at topstudio.co.jp
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
  using "From" header
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_02_18 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=HAS_PACKAGE,X_DEBBUGS_CC 
autolearn=no version=2.60-bugs.debian.org_2004_02_18
X-Spam-Level: 

--Multipart_Sat_Feb_21_16:26:01_2004-1
Content-Type: text/plain; charset=US-ASCII

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: base-config
Version: 2.12
Severity: wishlist
Tags: l10n

Hi,

I'm trying more l10n about base-config.
apt-setup shows countries have mirror list, but this isn't ready l10n.

I created a patch about apt-setup.
For l10n, iso-codes is needed (or, simply shows in English).

Thanks,
- -- 
Kenshi Muto
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 

iEYEARECAAYFAkA3B3cACgkQQKW+7XLQPLGzqgCfZSKjVVc5XPYPvUdc0thbBDrs
8uQAoIZ6yxUWXdntVdurl+eaSOMwXEK0
=gSPR
-END PGP SIGNATURE-

--Multipart_Sat_Feb_21_16:26:01_2004-1
Content-Type: application/octet-stream; type=patch
Content-Disposition: attachment; filename="apt-setup.l10n.patch"
Content-Transfer-Encoding: base64

SW5kZXg6IGFwdC1zZXR1cAo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiAvY3Zzcm9vdC9iYXNl
LWNvbmZpZy9iYXNlLWNvbmZpZy9hcHQtc2V0dXAsdgpyZXRyaWV2aW5nIHJldmlzaW9uIDEu
NDIKZGlmZiAtdSAtcjEuNDIgYXB0LXNldHVwCi0tLSBhcHQtc2V0dXAJMTkgRmViIDIwMDQg
MTQ6NDY6MDggLTAwMDAJMS40MgorKysgYXB0LXNldHVwCTIxIEZlYiAyMDA0IDA3OjI1OjI2
IC0wMDAwCkBAIC0zOCw2ICszOCw5IEBACiAJZ2V0dGV4dCAiZW50ZXIgaW5mb3JtYXRpb24g
bWFudWFsbHksICIKIAlwZXJsIC1uZSAnCiAJCUJFR0lOIHsKKwkJCXVzZSBMb2NhbGU6Omdl
dHRleHQ7CisJCQl1c2UgUE9TSVg7CisJCQl0ZXh0ZG9tYWluKCJpc29fMzE2NiIpOwogCQkJ
JHR5cGU9c2hpZnQ7CiAJCQlvcGVuIChULCAiL3Vzci9zaGFyZS96b25laW5mby9pc28zMTY2
LnRhYiIpOwogCQkJd2hpbGUgKDxUPikgewpAQCAtNTEsNyArNTQsNyBAQAogCQl9CiAJCWlm
ICgvQXJjaGl2ZS0kdHlwZTovKSB7CiAJCQkoJGMpPS9Db3VudHJ5OiAoLio/KVxzKy4qXG4v
OwotCQkJJGNvdW50cmllc3skY3skY319PTEgaWYgJGM7CisJCQkkY291bnRyaWVze2dldHRl
eHQoJGN7JGN9KX09MSBpZiAkYzsKIAkJfQogCQlFTkQgeyBwcmludCBqb2luKCIsICIsIHNv
cnQoa2V5cyAlY291bnRyaWVzKSkgfQogCScgJDEgJE1JUlJPUkxJU1QKQEAgLTY0LDYgKzY3
LDkgQEAKIG1pcnJvcl9saXN0ICgpIHsKIAlwZXJsIC1uZSAnCiAJCUJFR0lOIHsKKwkJCXVz
ZSBMb2NhbGU6OmdldHRleHQ7CisJCQl1c2UgUE9TSVg7CisJCQl0ZXh0ZG9tYWluKCJpc29f
MzE2NiIpOwogCQkJJHR5cGU9c2hpZnQ7CiAJCQkkY291bnRyeT1zaGlmdDsKIAkJCW9wZW4g
KFQsICIvdXNyL3NoYXJlL3pvbmVpbmZvL2lzbzMxNjYu

nobootloader oops

2004-02-24 Thread Stephen R Marenka

I just fixed a thinko in nobootloader, which causes it to always fail.
Please upload the new version.

Thanks,

Stephen

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


signature.asc
Description: Digital signature

Bug#233294: installation report - tar: Unrecognised file type

2004-02-24 Thread Glenn McGrath

On Tue, 24 Feb 2004 14:28:50 -0500
Barry Hawkins <[EMAIL PROTECTED]> wrote:

>   What is the status on this bug?  I tried to install again on
>   02/22 and 
> still got the failure at perl-base, even using the 02/21 daily.  I 
> don't understand how people are still able to test the installer if 
> this is happening.

I can extract perl-base deb using upstream busybox and
busybox-cvs-udeb_20040101-7 

As far as i can see this bug is fixed.



Glenn


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

Compiling kernel for laptop

2004-02-24 Thread Wes Reneau





I'm at a loss for words due to my own ignorance but I'm not sure what
to do at this point.

I've compiled the 2.6.3 kernel by "make mrproper, make xconfig (saved
.config), make-kpkg --revision=custom1.0 kernel_image modues_image.

The process runs thru w/ a few errors as listed below:

I've retyped the error so syntax may be just a bit off


CC [M]    drivers/pcmcia/i82365.o

drivers/pcmcia/i82365.c: In funciton 'is alive':

drivers/pcmica/i82365.c:665: warning: 'check_region' is
depreciated (declard at include/linux/ioport.h:121)


these type of errors continue untill it's thru processing the pcmcia
drivers with the words following In function that read 'isa_probe',
'i365_set_io_map', tcic_set_io_map'.

Now furthere down I see other /drivers/pcmcia/i82092.ko compile with no
errors.  Again, I have no idea why this is occuring.

When the compiler reaches the "Linux PCMCIA Configuration Script" I get
this:

** Your kernel is configured with PCMCIA driver support. 
Therefore

**  'make all' will compile the PCMCIA utilities but not
the drivers.

**   See README-2.4 if this is not what you intended


IMPORTANT NOTE FOR DEBIAN USERS
This means that a pcmcia-modules package will not be built.
  

Obviously this is a problem for me being that I'm running a laptop can
you please advise.




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

Changelogs & translations, once again....

2004-02-24 Thread Nikolai Prokoschenko

Hello!

I'm sorry to annoy the people, who think this topic is redundant, but
nevertheless, I've just updated my small script for updating
translations changelogs. It is positioned in the scripts/ directory in
the debian-installer CVS tree.

New since the last release is the output of the script, it can now be
simply copy&pasted into the changelog. For example, running it on the
tools/kbd-chooser directory in the current CVS version yields the
following output:

* Updated translations: 
   - Catalan (ca.po) by Jordi Mallach
   - Czech (cs.po) by Miroslav Kure
   - Danish (da.po) by Claus Hindsgaul
   - Greek (el.po) by Konstantinos Margaritis
   - French (fr.po) by Christian Perrier
   - Hungarian (hu.po) by VERÃK IstvÃn
   - Japanese (ja.po) by Kenshi Muto
   - Lithuanian (lt.po) by KÄstutis BiliÅnas
   - Portuguese (Brazil) (pt_BR.po) by AndrÃ LuÃs Lopes
   - Albanian (sq.po) by Elian Myftiu
   - Ukrainian (uk.po) by Eugeniy Meshcheryakov
   - Simplified Chinese (zh_CN.po) by Carlos Z.F. Liu

(Of course, this has been copy&pasted ;))

I have also implemented a simple logic to ensure that the output is
UTF-8 even if some translation is not held in UTF-8. 

I'd be really glad, if someone could test this script in his own
release cycle, so I know at least, how good/bad/usable/awkward it
is. I get the feeling it gets ignored :)

Have fun with it!


PS: I'd like to give some more explanation to the motivation for this
script.  As I have mentioned before, I'd like to push the
responsibility for updating the changelogs away from translators and
hand it over to the maintainers, or even better, to this script. Apart
from being lazy, preventing double and missing entries and preventing
possible mess in the changelog, this could be of use, if the
translation work gets organized. For example, I am thinking of
implementing a script for synchronising out russian l10n CVS
repository with debian-installer's (actually, this script works, but
only one way for now). This should work without problems, except the
changelog problem, where some handwork is mostly needed. 

-- 
Nikolai Prokoschenko 
[EMAIL PROTECTED] / Jabber: [EMAIL PROTECTED]


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

base-config_2.13_i386.changes ACCEPTED


Accepted:
base-config_2.13.dsc
  to pool/main/b/base-config/base-config_2.13.dsc
base-config_2.13.tar.gz
  to pool/main/b/base-config/base-config_2.13.tar.gz
base-config_2.13_all.deb
  to pool/main/b/base-config/base-config_2.13_all.deb
Announcing to [EMAIL PROTECTED]
Closing bugs: 232547 233135 233262 233995 


Thank you for your contribution to Debian.


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

Automated installer / kickstart instructions?

Hi-
	A while back there was a lot of talk about automating installations, 
and in many places it was claimed that it actually worked.  Does anyone 
have instructions for how to actually do it?
	For example, if I wanted to automate a network install, and I had done 
the homework, including:

	Install first by hand making sure things work.
	Making notes of all my choices and the answers to the questions that it 
asks me (alternately keystrokes?)

	How would I then translate this into an automated installation?

	I know of FAI and have been trying to use it, but it is extremely 
complicated and provides a lot of functionality that most users (even 
most administrators!) don't need.. I just want to use the regular 
debian-installer without having to sit here and press enter and type in 
my mirror location every time :)

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

Re: debian-installer/tools/languagechooser/debian changelog,1.202,1.203

2004-02-24 Thread Denis Barbier

On Mon, Feb 23, 2004 at 11:51:14PM -0800, Joshua Kwan wrote:
> On Tue, 24 Feb 2004 08:14:53 +0100, Denis Barbier wrote:
> >> +  * Joshua Kwan
> >> +- iconv all the .po files to UTF-8 to silence unifont building.
> > 
> > The right fix is to add a debian/po/output file, just done.
> 
> OK. So should I revert the .po files to the way they were?

No need to, translators will do it themselves if they want.

Denis


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

Processing of base-config_2.13_i386.changes

base-config_2.13_i386.changes uploaded successfully to localhost
along with the files:
  base-config_2.13.dsc
  base-config_2.13.tar.gz
  base-config_2.13_all.deb

Greetings,

Your Debian queue daemon


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

Re: m68k port status update

2004-02-24 Thread Stephen R Marenka

On Tue, Feb 24, 2004 at 01:51:38PM -0500, Joey Hess wrote:
> Wouter Verhelst wrote:
> > You don't. In both cases, you need to download an image, boot the native
> > OS, start a kernel loader which will put the image up as a RAMdisk, and
> > go from there. The difference is that the CD-ROM image will get its
> > udebs from CDROM, whereas the network image will work with the network.
> 
> So it's much more like the hd-media stuff we have on i386.

Yes, except not mounted loopback.

A native bootloader, kernel, and ramdisk all reside on the native 
filesystem. Amiga and mac can *only* be booted this way.

boot-floppies delivered a tarball which contained all three of these
things for download onto a native partition. I'm not sure I intend to
emulate that, though.

How about I create a new type called nativehd or something?

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

signature.asc
Description: Digital signature

languagechooser_1.13_i386.changes ACCEPTED


Accepted:
languagechooser_1.13.dsc
  to pool/main/l/languagechooser/languagechooser_1.13.dsc
languagechooser_1.13.tar.gz
  to pool/main/l/languagechooser/languagechooser_1.13.tar.gz
languagechooser_1.13_all.udeb
  to pool/main/l/languagechooser/languagechooser_1.13_all.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#234605: Package: installation-reports

2004-02-24 Thread Marco Loewl

Package: installation-reports

Debian-installer-version: 
uname -a: <2.4.24>
Date: <22.2.2004>
Method: 
Machine: 
Processor: Pentium 4 2,6 GHz HT Enabled 
Memory: 1024 MB
Root Device:  Seagate 120 MB 7200 rpm/s 8 MB Cache P-ATA
Root Size/partition table: 
 Tabelle ein, mit Notizen, welche Partition wo eingebunden wurde.>
Output of lspci: musste ich leider unter Kernel 2.6.3 machen ! 

[EMAIL PROTECTED] root]# lspci -vv
:00:00.0 Host bridge: Intel Corp. 82875P Memory Controller Hub (rev 02)
   Subsystem: Asustek Computer, Inc.: Unknown device 80f6
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR+ FastB2B-
   Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
:00:01.0 PCI bridge: Intel Corp. 82875P Processor to AGP Controller (rev 02)  
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR+ FastB2B-
   Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B-
:00:03.0 PCI bridge: Intel Corp. 82875P Processor to PCI to CSA Bridge (rev 02) 
(prog-if 00 [Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR+ FastB2B-
   Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B-
:00:1d.0 USB Controller: Intel Corp. 82801EB USB (rev 02) (prog-if 00 [UHCI] )
   Subsystem: Asustek Computer, Inc.: Unknown device 80a6
   Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR- FastB2B-
   Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
:00:1d.1 USB Controller: Intel Corp. 82801EB USB (rev 02) (prog-if 00 [UHCI] )
   Subsystem: Asustek Computer, Inc.: Unknown device 80a6
   Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR- FastB2B-
   Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
:00:1d.2 USB Controller: Intel Corp. 82801EB USB (rev 02) (prog-if 00 [UHCI] )
   Subsystem: Asustek Computer, Inc.: Unknown device 80a6
   Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR- FastB2B-
   Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
:00:1d.3 USB Controller: Intel Corp. 82801EB USB (rev 02) (prog-if 00 [UHCI] )
   Subsystem: Asustek Computer, Inc.: Unknown device 80a6
   Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR- FastB2B-
   Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
:00:1d.7 USB Controller: Intel Corp. 82801EB USB2 (rev 02) (prog-if 20 [EHCI ])
   Subsystem: Asustek Computer, Inc.: Unknown device 80a6
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR+ FastB2B-
   Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
:00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB PCI Bridge (rev c2) (prog- if 00 
[Normal decode])
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR+ FastB2B-
   Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Reset- FastB2B-
:00:1f.0 ISA bridge: Intel Corp. 82801EB LPC Interface Controller (rev 02)
   Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Step ping- 
SERR- FastB2B-
   Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
:00:1f.1 IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (re v 02) 
(prog-if 8a [Master SecP PriP])
   Subsystem: Asustek Computer, Inc.: Unknown device 80a6
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR- FastB2B-
   Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
   Region 1: I/O ports at 
   Region 2: I/O ports at 
   Region 3: I/O ports at 
   Region 4: I/O ports at fc00 [size=16]
   Region 5: Memory at 4000 (32-bit, non-prefetchable) [size=1K]
:00:1f.3 SMBus: Intel Corp. 82801EB SMBus Controller (rev 02)
   Subsystem: Asustek Computer, Inc.: Unknown device 80a6
   Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR- FastB2B-
   Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
:00:1f.5 Multimedia audio controller: Intel Corp. 82801EB AC'97 Audio Contro ller 
(rev 02)
   Subsystem: Asustek Computer, Inc.: Unknown device 80f3
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step ping- 
SERR- FastB2B-
   Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- 
:01:00.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti 460 0] 
(rev a3) (prog-if 00 [VGA])
   Subsystem: nVidia Corporation: Unknown device 0130
   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- V

Bug#233294: installation report - tar: Unrecognised file type

On Feb 19, 2004, at 3:46 AM, Sven Luther wrote:
On Thu, Feb 19, 2004 at 12:39:02AM -0800, Matt Kraai wrote:
On Thu, Feb 19, 2004 at 08:04:49AM +0100, Sven Luther wrote:
On Wed, Feb 18, 2004 at 10:46:53AM -0800, Matt Kraai wrote:
BusyBox tar cannot handle archives built with the latest version
of tar.  In particular, /usr/lib/debootstrap/devices.tar.gz and
the following packages installed by debootstrap:
 debconf
 debconf-i18n
 gcc-3.3-base
 libnewt0.51
 libstdc++5
 libgcc1
 perl-base
 tar
 whiptail
 apt
 apt-utils
 base-config
 aptitude
 bsdmainutils
 console-data
 zlib1g
 wget
 lilo
 iptables
It seems to me that the latest tar fixes this issue :

 Date: Sun, 15 Feb 2004 16:03:20 -0700
 tar (1.13.92-5) unstable; urgency=low
 .
   * patch from Paul Eggert to revert bogus behavior where 
POSIXLY_CORRECT
 set in the environment forced 'pax' format archives, closes: 
#230872
The changelog is misleading.  BusyBox tar cannot handle archives
produced by tar 1.13.92-5.
Ok, good to know this.

So, the problem would either be to :

  a) fill RC bug against all those above mentioned packages so they 
are
  rebuilt with this new tar.

  b) fix busybox tar so they can handle the broken archives. More 
work,
  but more foolproof in the future.

Unless i miss something, that is.
Actually, all (b) requires is enabling
CONFIG_FEATURE_TAR_OLDGNU_COMPATABILITY.  See bug 233627.
So, let's do it. What are we waiting for.

Friendly,

Sven Luther

	What is the status on this bug?  I tried to install again on 02/22 and 
still got the failure at perl-base, even using the 02/21 daily.  I 
don't understand how people are still able to test the installer if 
this is happening.

Thanks,
--
Barry C. Hawkins
All Things Computed
site: www.allthingscomputed.com
weblog: www.yepthatsme.com


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

Processing of languagechooser_1.13_i386.changes

languagechooser_1.13_i386.changes uploaded successfully to localhost
along with the files:
  languagechooser_1.13.dsc
  languagechooser_1.13.tar.gz
  languagechooser_1.13_all.udeb

Greetings,

Your Debian queue daemon


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

Re: latest testing netinst missing network driver modules?

2004-02-24 Thread Santiago Garcia Mantinan

> If we can only build one set, they should be built against sid's d-i for
> now, I think.

We could build against the two, but it takes a really long time to build
because of jigdo, so I think it is better to build just for the one we wan't
people to test, besides, if we provide several, people tends to get confused
not knowing what to download.

Regards...
-- 
Manty/BestiaTester -> http://manty.net


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

Re: m68k port status update

Wouter Verhelst wrote:
> You don't. In both cases, you need to download an image, boot the native
> OS, start a kernel loader which will put the image up as a RAMdisk, and
> go from there. The difference is that the CD-ROM image will get its
> udebs from CDROM, whereas the network image will work with the network.

So it's much more like the hd-media stuff we have on i386.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: Sparc d-i status

On Tue, Feb 24, 2004 at 12:58:23PM -0500, Ben Collins wrote:
> On Tue, Feb 24, 2004 at 07:14:50PM +0100, Sven Luther wrote:
> > On Tue, Feb 24, 2004 at 11:26:06AM -0500, Ben Collins wrote:
> > > On Tue, Feb 24, 2004 at 08:21:18AM -0800, Jeff Bailey wrote:
> > > > On Tue, Feb 24, 2004 at 04:22:34PM +0100, Thomas Poindessous wrote:
> > > > 
> > > > > > I also remember (was it Thomas?  Blars? hmmm...) mentioning that the
> > > > > > fdisk udeb wasn't getting loaded for some reason.  I'm hoping that the
> > > > > > whole partman thing will make this silently go away before we get there.
> > > > > 
> > > > > in fact, there is no fdisk-udeb for sparc (bug #228444 ), and there is
> > > > > no support for sparc in partitioner ( bug #228518).
> > > > 
> > > > Lovely!  I've applied the patch in 228518 to CVS and marked it pending. 
> > > > (It obviously still needs fdisk-udeb).
> > > > 
> > > > Hmm...  Why don't we just use parted for now, until a better solution
> > > > comes around?  It's in the archive, and AFAICT supports Sparc.  (ia64
> > > > uses it right now, too)
> > > 
> > > I know it supports sparc. I worked a long time ago to get the sun
> > > partition support into that.
> > 
> > Oh, you did write that ? I inspired myself from it when doing the amiga
> > partition table support. Thanks then, altough it was mostly casuality
> > which made me print the disk_sun.c file instead of another one.
> 
> Well, I copied it from some other file, so the benefits are just being
> passed around :)

Yeah, and since we all assigned copyright to the FSF anyway ...

Friendly,

Sven Luther


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

Re: Sparc d-i status

2004-02-24 Thread Ben Collins

On Tue, Feb 24, 2004 at 07:14:50PM +0100, Sven Luther wrote:
> On Tue, Feb 24, 2004 at 11:26:06AM -0500, Ben Collins wrote:
> > On Tue, Feb 24, 2004 at 08:21:18AM -0800, Jeff Bailey wrote:
> > > On Tue, Feb 24, 2004 at 04:22:34PM +0100, Thomas Poindessous wrote:
> > > 
> > > > > I also remember (was it Thomas?  Blars? hmmm...) mentioning that the
> > > > > fdisk udeb wasn't getting loaded for some reason.  I'm hoping that the
> > > > > whole partman thing will make this silently go away before we get there.
> > > > 
> > > > in fact, there is no fdisk-udeb for sparc (bug #228444 ), and there is
> > > > no support for sparc in partitioner ( bug #228518).
> > > 
> > > Lovely!  I've applied the patch in 228518 to CVS and marked it pending. 
> > > (It obviously still needs fdisk-udeb).
> > > 
> > > Hmm...  Why don't we just use parted for now, until a better solution
> > > comes around?  It's in the archive, and AFAICT supports Sparc.  (ia64
> > > uses it right now, too)
> > 
> > I know it supports sparc. I worked a long time ago to get the sun
> > partition support into that.
> 
> Oh, you did write that ? I inspired myself from it when doing the amiga
> partition table support. Thanks then, altough it was mostly casuality
> which made me print the disk_sun.c file instead of another one.

Well, I copied it from some other file, so the benefits are just being
passed around :)

-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/


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

machine restarts after grub tries to load linux

2004-02-24 Thread Lawrence Lee


The machine is a Fujitsu Lifebook 420D. Debian was installed successfully
and works with the 2.4 bootfloopy kernel. But when I installed the 2.4.18
kernel, the machine restarts right after grub tries to load it. I thought
it might have be a lilo problem, but installed grub thinking
it might fix the problem. It didn't. I checked the lilo.conf and it looks
similar to other lilo.conf's. So I don't think it's a problem with the
loaders. The symlinks pointing to vmlinuz are correct.

Where could the problem be? Should I do a fresh install? Point me the the
right direction. Thanks


---
Lawrence Lee
[EMAIL PROTECTED]
http://hills.ccsf.edu/~llee32/images.html


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

Re: Sparc d-i status

On Tue, Feb 24, 2004 at 11:26:06AM -0500, Ben Collins wrote:
> On Tue, Feb 24, 2004 at 08:21:18AM -0800, Jeff Bailey wrote:
> > On Tue, Feb 24, 2004 at 04:22:34PM +0100, Thomas Poindessous wrote:
> > 
> > > > I also remember (was it Thomas?  Blars? hmmm...) mentioning that the
> > > > fdisk udeb wasn't getting loaded for some reason.  I'm hoping that the
> > > > whole partman thing will make this silently go away before we get there.
> > > 
> > > in fact, there is no fdisk-udeb for sparc (bug #228444 ), and there is
> > > no support for sparc in partitioner ( bug #228518).
> > 
> > Lovely!  I've applied the patch in 228518 to CVS and marked it pending. 
> > (It obviously still needs fdisk-udeb).
> > 
> > Hmm...  Why don't we just use parted for now, until a better solution
> > comes around?  It's in the archive, and AFAICT supports Sparc.  (ia64
> > uses it right now, too)
> 
> I know it supports sparc. I worked a long time ago to get the sun
> partition support into that.

Oh, you did write that ? I inspired myself from it when doing the amiga
partition table support. Thanks then, altough it was mostly casuality
which made me print the disk_sun.c file instead of another one.

Friendly,

Sven Luther


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

Re: m68k port status update

On Tue, Feb 24, 2004 at 12:16:41PM -0500, Joey Hess wrote:
> Stephen R Marenka wrote:
> > So you'd rather call these floppy? 
> > 
> > I'll note that i386 can boot off floppy, whereas amiga and mac 
> > cannot. Would another target name be clearer?
> > 
> > I don't care much one way or the other. So far everything will fit on 
> > a floppy, but I hadn't much been paying attention to size.
> 
> If you need to download a floppy, then boot the native os, and run a
> bootloader from the floppy, then it's best to call the image a floppy
> image.

Notice that amigas usually booted from harddisk, not floppies, since
most users had only 720K floppies (but 880 if they were amiga formated).

Maybe calling those disk or something such would be more truthful.

Friendly,

Sven Luther


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

Re: m68k port status update

2004-02-24 Thread Wouter Verhelst

On Tue, Feb 24, 2004 at 12:16:41PM -0500, Joey Hess wrote:
> Stephen R Marenka wrote:
> > So you'd rather call these floppy? 
> > 
> > I'll note that i386 can boot off floppy, whereas amiga and mac 
> > cannot. Would another target name be clearer?
> > 
> > I don't care much one way or the other. So far everything will fit on 
> > a floppy, but I hadn't much been paying attention to size.
> 
> If you need to download a floppy, then boot the native os, and run a
> bootloader from the floppy, then it's best to call the image a floppy
> image.

You don't. In both cases, you need to download an image, boot the native
OS, start a kernel loader which will put the image up as a RAMdisk, and
go from there. The difference is that the CD-ROM image will get its
udebs from CDROM, whereas the network image will work with the network.

-- 
Wouter Verhelst
Debian GNU/Linux -- http://www.debian.org
Nederlandstalige Linux-documentatie -- http://nl.linux.org
"Stop breathing down my neck." "My breathing is merely a simulation."
"So is my neck, stop it anyway!"
  -- Voyager's EMH versus the Prometheus' EMH, stardate 51462.


signature.asc
Description: Digital signature

Re: debian-installer help wanted

Magnus Ekdahl wrote:
> * When one finds a bug report containing only one issue I assume its 
> correct just to reassign it to its respective package? An alternative 
> line of thought would be to collect all installation-reports in one 
> place, hence every bug needs to be cloned.

Since we're not doing any other analysis of installation reports right
now, and most of the one bug install reports tend to be shy on other
details anyway, I guess it's easier to simply reassign them.

> * Shouldn't I (send a notification)/cc developers of the affected 
> packages? Here I refer to the notorisly quiet reassign command.

Probably doesn't matter much if the package is part of d-i. For stuff
outside d-i yes, I always get better results when I mail the maintainer
as well.

> * Could you please add bug numbers to every item in the TODO so one 
> knows to whom one should forward requests such as "include 2.6"

Ugh. I'm not sure they all have bugs, I hope people can add bug numbers
if they're aware of any.

> * Often[0][1] one finds bugs where the reporter needs to fill in things 
> to make sense. So I send a mail to the submitter asking for more info. 
> Then I need to follow up on the bug. But I can't recall any way of 
> getting all mail sent to the bug other than changing the owner. Is there 
> a better way?

Not AFAIK at the moment, aside from [EMAIL PROTECTED]
and procmail. I try to arrange for the submitter to mail replys to me,
instead of the bug.

-- 
see shy jo

signature.asc
Description: Digital signature

Re: Installing Debian using debian-sarge-netinst.iso (powerpc)

2004-02-24 Thread Seb Tennant

Hi all.

As the person who started this thread it's about time I responded! First of all, though it hardly matters, my machine is a G4 desktop, not a laptop. I have overcome my partitioning problems and have seemingly successfully employed the Debian Installer twice now.

The first time I did it in 'trust mode', (my terminology), and it worked without a hitch. I then decided to install emacs and it's dependencies using dselect. It got about half way through before stopping, (cleanly), only for me to find that my keyboard had gone completely haywire. I spent about half an hour trying to type the command 'shutdown -r now' but try as I might I could not find the 's' ! I pulled the plug and rebooted but no change. Hence my second attempt at using the installer.

This time I ran it in 'expert mode' and again it seemed to run without a hitch. I chose not to install any packages, shutdown cleanly and went to bed. However, the following day it hung at 'Detecting hardware' on boot up, and has hanged there ever since.

Perhaps it's going to be a case of third time lucky! The sarge-netinst.iso I'm using was built on 14th Jan so perhaps this problem has already been addressed.

sebyte
___
Please post your reply to the list without CC'ing me.
If you do I will only get your mesage twice.

In reply to all your comments:

Derrik Pates - First of all thanks for taking the time to comprehensively address each of my questions in turn.

As was mentioned in another reply, you shouldn't try to do the partitioning through Apple's Disk Utility. IMHO, it's terrible, not to mention it wastes big chunks of space between partitions for no discernable reason at all.

128 MB to be precise! There must be a reason. Surely...

I don't believe you'll be able to write to a MacOS/OpenStep UFS filesystem from Linux anyway.

Read only support is OK for now. All I'm hoping is to be able to access my sizeable mp3 collection from Debian when I am up and running.

You have to make an 800KB (1600 block) partition of type Apple_Bootstrap for yaboot to install itself into. If you don't do this, you won't be able to boot Linux on your Powerbook. (I think that's actually mentioned in the Debian install guide for PowerPC - did you read it?) [...] Also, after you've set up the MacOS X partition, and got it all happy, do the rest of the partition in Linux using mac-fdisk.

I've sussed this. I knew I needed one, I just didn't know how to create it. In fact, the first couple of times I booted up from the CD, I didn't know it was mac-fdisk I was using. I had even read about mac-fdisk but with nothing to indicate which actual program the installer is running I don't see how I was supposed to know this. The 'branden-ibook' link, (that I mentioned in an earlier post), made everything clear.

Why are you splitting your main filesystem into partitions? Especially "/boot, /tmp, /var, /usr, /home, etc." all on one partition? That's a very poor layout, really. Better to just go with one FS for your root, one for the exchange partition, one for OS X, the 800 KB bootstrap partition, and your swap partition.

I think I am right in saying that for a partition to be bootable it must include /bin, /dev, /etc, /lib, /mnt, /root and /sbin. It seems to me that /home, /opt, /var, /tmp and /usr should ideally all have their own partitions. I was thinking more along the lines of creating one small bootable 'root' partition and putting everything else on one large second partition thus eliminating partition sizing issues).

I'm not saying that multiple partitions is a bad thing, but stuffing a whole bunch of subtrees on one filesystem right away, as I said before, is silly, and I really think you shouldn't do it.

In the light of the above rationale, would you still argue that this is silly?

Go with ext3. If the system crashes, or whatever, you don't have to sit and wait while fsck runs on the filesystem.

Thanks for the tip.

S. Keeling - I have to agree with Klaus Ita. There's no point attacking someone who is only trying to help. Having said that, I am pleased to hear that I am not alone in my understanding that a filesystem hierarchy distributed across multiple partitions makes a system more robust. There seem to be many different opinions out there.

To clarify, /usr, /opt, /var, and /home should be separate, and /var
(in Debian) should be big enough to hold logs and a dist-upgrade.
/boot and /tmp shouldn't be separate. On that, we can agree.

Out of interest, why should /boot and /tmp be kept together? Regarding /usr, /opt, /var and /home, see note above and/or a new thread I've started called 'Small and bootable'.

Klaus Ita - I'm afraid your advice is a little over my head at the moment.

You might also want to try mounting different partitions with different
permissions. and then tmp should definitely have a noexec tag and not
share the same [partition] as /boot (ro)

/boot as read only makes perfect s

Re: latest testing netinst missing network driver modules?

Santiago Garcia Mantinan wrote:
> Joey, should I be building the cds and dvds against sid for now?
> Any other changes?

If we can only build one set, they should be built against sid's d-i for
now, I think.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#232397: bterm-unifont: postinst won't run?

Matt Kraai:
> How about making anna configure packages that do not have menu
> items?

I think that is a good idea. Only problem I can anticipate is that if
something w/o a menu item depended on something with a menu item, it
might fail to configure, but obviously nothing in current d-i has the
problem.

-- 
see shy jo


signature.asc
Description: Digital signature

Bug#234562: debian-installer: Boot delay too short to read information

Thomas Arendsen Hein wrote:
> Package: debian-installer
> Version: N/A; reported 2004-02-24
> Severity: wishlist
> 
> When booting from CD you don't have enough time to read about the
> boot options 'install', 'install-safe', 'expert' and 'expert-safe'.
> 
> Of course you can press a key to stop booting the default entry, but
> maybe this should be printed in the first line.

The daily built cd images have exactly one line of text "Press F1 for
help or ENTER to boot:", and a 5 second timeout.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: m68k port status update

Stephen R Marenka wrote:
> So you'd rather call these floppy? 
> 
> I'll note that i386 can boot off floppy, whereas amiga and mac 
> cannot. Would another target name be clearer?
> 
> I don't care much one way or the other. So far everything will fit on 
> a floppy, but I hadn't much been paying attention to size.

If you need to download a floppy, then boot the native os, and run a
bootloader from the floppy, then it's best to call the image a floppy
image.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: [d-i manual] repetitious para

2004-02-24 Thread Miroslav Kure

On Mon, Feb 23, 2004 at 08:39:13PM -0600, John Buttery wrote:
>   IMO the biggest feature that distinguishes distributions is the
> package management.  I mean, it's the same kernel, the same core
> software bundled with it for the most part, stored in the same places
> (mostly, depending on how FHS-compliant a distro is)...what's really the
> difference between distributions if not the package manager?  The only
> other real difference is the installer, which you only use once anyway.
>   I think that's something that _should_ be played up...the fact that
> users of all these other distributions are installing part of Debian's
> package management system.  We should also emphasize that it's only a
> small part of it...'apt-get' != 'APT'.  When you install apt4rpm, you
> may get apt-get but you don't get the rest of the army of apt-* tools,
> the existence of which is made possible only by Debian's stringent
> package format QA process (try having a tool like apt-listchanges with a
> bunch of packages that don't have a changelog format spec...).

Ok, ok. You are absolutely right.
I guess I've been using Debian for too long, so I forgot problems that
plague other package managers. My contact with other distributions is
intermediated only through reviews on LWN.net :-).

But back to the real work. Minor rephrasing can wait. The most
important tasks for now are:
 * write en/module/*.xml
 * update references to the kernel flavors and install files
 * rest of doc/manual/TODO
Volunteers?

-- 
Miroslav Kure


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

Bug#234581: iso doesn't checksum

2004-02-24 Thread Gus Heck

Package: installation-reports

Debian-installer-version: sarge-i386.netinst.iso from 
uname -a: Linux cs101srv 2.4.22-1-386 #9 Sat Oct 4 14:30:39 EST 2003 i686 unkown
Date: 2/23/04 to 2/24/04
Method: Boot from CD using ISO

Machine: 
Processor: Dual Pentium III 1 Ghz, Intel stl2 mb  
Memory: 1GB ECC RAM
Root Device: Adaptec 2100s SCSI RAID-1 with 2 Fujitsu 10k 68pin drives

Root Size/partition table: 

Prob not relevant, but mail me if you think you need it.

Output of lspci:

not avail.

Base System Installation Checklist:

Initial boot worked:[yes ]
Configure network HW:   [? ]
Config network: [Error ] (asked hostname twice, domain 0, mirror 0
Detect CD:  [yes ]
Load installer modules: [yes ]
Detect hard drives: [yes ] (adaptec 2100s raid! good!)
Partition hard drives:  [yes ]
Create file systems:[yes ]
Mount partitions:   [in shell at least ]
Install base system:[Failed on libacl1 & checksum from menu fails!]
Install boot loader:[ ]
Reboot: [ ]
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Comments/Problems:

I have wasted half a pack of CD's and 2 days trying different isos both 
from debian installer and jigdo for the woody release.  I am charged 
with evaluating potential replacements for our soon-to-be-expensive 
redhat install. The only installer which seemed to be able to deal with 
my raid card is this one. I only found it with the help of a student who 
is our local Debian Prophet. I downloaded it 3 times and burned it at 
max, 16x, 8x and 4x to be sure the checksum failure wasn't something I 
did. Debian is getting a "does not install" rating. I cannot spend any 
more time on your distro and need to move on to SUSE/Mandrake/Gentoo. I 
had hoped Debian would work out, and had placed it at the top of the 
list because it is my impression that it has aproximately as large a 
user base as RedHat.

If it's hard/impossible to install it doesn't matter how well it runs, I 
just can't evaluate it.





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

Re: Sparc d-i status

2004-02-24 Thread Ben Collins

On Tue, Feb 24, 2004 at 08:21:18AM -0800, Jeff Bailey wrote:
> On Tue, Feb 24, 2004 at 04:22:34PM +0100, Thomas Poindessous wrote:
> 
> > > I also remember (was it Thomas?  Blars? hmmm...) mentioning that the
> > > fdisk udeb wasn't getting loaded for some reason.  I'm hoping that the
> > > whole partman thing will make this silently go away before we get there.
> > 
> > in fact, there is no fdisk-udeb for sparc (bug #228444 ), and there is
> > no support for sparc in partitioner ( bug #228518).
> 
> Lovely!  I've applied the patch in 228518 to CVS and marked it pending. 
> (It obviously still needs fdisk-udeb).
> 
> Hmm...  Why don't we just use parted for now, until a better solution
> comes around?  It's in the archive, and AFAICT supports Sparc.  (ia64
> uses it right now, too)

I know it supports sparc. I worked a long time ago to get the sun
partition support into that.

> > we also need a silo-installer
> 
> Right.  Any takers? =)

Obviously, that's a "me" :)

-- 
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/


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

Re: boot logo vote

2004-02-24 Thread debian user

yes me to i like it

Le mar 24/02/2004 Ã 16:34, Erik Dykema a Ãcrit :
> I vote for the moonish one, here:
> 
> http://sloth.voxel.net/~joshk/d-i-logos/deb_boot_02-1.png
> by Volkan YAZICI
> 
>   It points to a future when the astronauts are running debian while they 
> work in their moon base :)
> 
> Erik
> 


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

Re: a test of converting to subversion

Denis Barbier wrote:
> On Mon, Feb 23, 2004 at 07:29:23PM -0500, Joey Hess wrote:
> [...]
> > Failing that, your b) looks not too bad. One thing that makes it easier
> > is that due to svn's different versioning method, we only need to record
> > one number, the current revision of the whole repository after it is
> > switched to subversion (will be 9500 or so).
> 
> I did not notice that, then the only point is not to disable cvs, say
> for a couple of weeks.

Maybe I can come up with something to keep only manual/ open. I'd hate
to see other commits go to the wrong place.

> Also $Id$ cvs keywords should be replaced by
> svn keywords.  Is
>   svn propset svn:keywords "Id"
> the command to be run from doc/manual/en?

Yes, that's right, I think you have to force svn to re-update the files
afterwards for the Id substitution to take place.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: boot logo vote

2004-02-24 Thread Harald Dunkel

Hans Fugal wrote:
I vote for the first image on http://sloth.voxel.net/~joshk/d-i-logos/
with the sixth image as runner-up.
If I am allowed to vote, then

http://sloth.voxel.net/~joshk/d-i-logos/deb_boot_02-1.png

would be my favourite.

Regards

Harri

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

Re: release status / daily builds?

Erik Dykema wrote:
>   Would it be possible to consolidate the downloading sites in such a 
>   way that all the necessary images could be downloaded from the same place?

http://www.debian.org/devel/debian-installer/ports-status is prominantly
linked to from the main d-i web page.

-- 
see shy jo

signature.asc
Description: Digital signature

Processed: tagging 228518

Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.7.95.1
> tags 228518 + pending
Bug#228518: partitioner: [PATCH] sparc.sh for sparc system
Tags were: d-i patch
Tags added: pending

>
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]

Re: Sparc d-i status

On Tue, Feb 24, 2004 at 04:22:34PM +0100, Thomas Poindessous wrote:

> > I also remember (was it Thomas?  Blars? hmmm...) mentioning that the
> > fdisk udeb wasn't getting loaded for some reason.  I'm hoping that the
> > whole partman thing will make this silently go away before we get there.
> 
> in fact, there is no fdisk-udeb for sparc (bug #228444 ), and there is
> no support for sparc in partitioner ( bug #228518).

Lovely!  I've applied the patch in 228518 to CVS and marked it pending. 
(It obviously still needs fdisk-udeb).

Hmm...  Why don't we just use parted for now, until a better solution
comes around?  It's in the archive, and AFAICT supports Sparc.  (ia64
uses it right now, too)

> we also need a silo-installer

Right.  Any takers? =)

Tks,
Jeff Bailey

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

Bug#234564: minor problems

2004-02-24 Thread Frank Lichtenheld

Package: installation-reports

Debian-installer-version: Beta 2
uname -a: not available, see below
Date: 2004-02-24 15:00
Method: CD-Boot, installed from CD, additional packages installed from http mirror
Machine: Gericom Notebook
Processor: AMD K6-2
Memory: 64 MB
Root Device: IDE
Root Size/partition table:
 /dev/hda1 /boot
 /dev/hda2 swap
 /dev/hda3 /
Output of lspci:
 not available, see below

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:  [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:

After I installed the system sucessfully and worked a little bit on
it, the harddrive has started giving strange error messages and the filesystem
is totally f***ed up now. I believe this is a hardware problem though.
I only took the machine to try the installer. Haven't used it for a
year or two.

Here the problems during the install:

I use a pcmcia network card, but the PCMCIA bus was not correctly
configured (insmod of ds.o failed, because there was no socket driver
loaded), so the network didn't work. After the install I used modconf
to load the correct module and it worked. Don't know what the problem
exactly was.  I can give you a lspci output later if wanted.

I encountered some minor problems during the install process:
 While creating the filesystems, I selected /dev/hda1 and ext2 and
/boot. Then I selected /dev/hda2 (which was already a swap partition)
and "keep filesystem". After that /dev/hda1 and /dev/hda2 were both
marked as to be mounted on /boot

After the note about the reboot showed up a note about debconf
priorities, but I couldn't read it since the reboot was already
started. Somewhat confusing ;)

Gruesse,
-- 
Frank Lichtenheld <[EMAIL PROTECTED]>
www: http://www.djpig.de/


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

Re: Sparc d-i status

2004-02-24 Thread Thomas Poindessous

On Tue, Feb 24, 2004 at 09:34:06AM -0500, Jeff Bailey wrote:
> I also remember (was it Thomas?  Blars? hmmm...) mentioning that the
> fdisk udeb wasn't getting loaded for some reason.  I'm hoping that the
> whole partman thing will make this silently go away before we get there.

in fact, there is no fdisk-udeb for sparc (bug #228444 ), and there is
no support for sparc in partitioner ( bug #228518).

we also need a silo-installer

-- 
Thomas Poindessous


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

Bug#234562: debian-installer: Boot delay too short to read information

2004-02-24 Thread Thomas Arendsen Hein

Package: debian-installer
Version: N/A; reported 2004-02-24
Severity: wishlist

When booting from CD you don't have enough time to read about the
boot options 'install', 'install-safe', 'expert' and 'expert-safe'.

Of course you can press a key to stop booting the default entry, but
maybe this should be printed in the first line.

Thomas

-- 
Email: [EMAIL PROTECTED]
http://intevation.de/~thomas/


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

Bug#234529: duplicate of bug #232426

2004-02-24 Thread Eugeniy Meshcheryakov

Package: base-config
Version: 2.12
Severity: normal
Followup-For: Bug #234529

 This looks like a duplicate of bug #232426 in whiptail package.

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

Versions of packages base-config depends on:
ii  adduser 3.51 Add and remove users and groups
ii  apt 0.5.22   Advanced front-end for dpkg
ii  aptitude0.2.14-3 curses-based apt frontend
ii  bsdutils1:2.12-6 Basic utilities from 4.4BSD-Lite
ii  console-data2002.12.04dbs-29 Keymaps, fonts, charset maps, fall
ii  console-tools   1:0.2.3dbs-48Linux console and font utilities
ii  debconf 1.4.11   Debian configuration management sy
ii  debianutils 2.6.2Miscellaneous utilities specific t
ii  gettext-base0.14.1-1 GNU Internationalization utilities
ii  passwd  1:4.0.3-17   Change and administer password and

-- debconf information excluded



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

Bug#234561: Package: installation-reports

2004-02-24 Thread Warner, William - Perot

Package: installation-reports

Debian-installer-version:
http://gluck.debian.org/cdimage/testing/daily/i386/current/sarge-i386-netins
t.iso  23-Feb-2004 13:50   107M
uname -a: Linux (none) 2.4.24-1-386 #1 Wed Feb 18 19:44:56 ESD 2004 i686
unknown
Date: Feb 24, 800am
Method: Netinst cdrom

Machine: vmware virtual machine on a dell d400
Processor: Pentium M
Memory:256
Root Device: scsi /dev/scsi/host0/bus0/target0/lun0/disc
Root Size/partition table: part1 = swap 128M part2 = / 3.9G
Output of lspci:

Base System Installation Checklist:

Initial boot worked:[yes ]
Configure network HW:   [yes ]
Config network: [ yes]
Detect CD:  [yes ]
Load installer modules: [ yes]
Detect hard drives: [ yes]
Partition hard drives:  [yes ]
Create file systems:[ no] install couldn't go any farther see notes
Mount partitions:   [no ] 
Install base system:[no ]
Install boot loader:[ no]
Reboot: [ no]
[ ] = didn't try it

Comments/Problems:

>From cfdisk on, the key strokes started jumping around all over the place.
Screens would flash back and forth and I was not able to set up the
filesystems correctly.  I have done several installs before including the
beta 2 installer successfully but I was unable to install the latest
snapshot.



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

boot logo vote

I vote for the moonish one, here:

http://sloth.voxel.net/~joshk/d-i-logos/deb_boot_02-1.png
by Volkan YAZICI
	It points to a future when the astronauts are running debian while they 
work in their moon base :)

Erik

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

release status / daily builds?

>  - Get daily builds working.
>Currently working: alpha, i386, ia64, m68k, sparc
>Hppa's daily build has been down since the 17th.
>Mips needs a daily build.
>Powerpc's daily build is failing.
Hi-
	WRT the recent message that the best place to download testing images 
is here:
http://gluck.debian.org/cdimage/testing/daily/

	But other testing images are available here:

http://people.debian.org/~joeyh/d-i/images/daily/netboot/

	Would it be possible to consolidate the downloading sites in such a way 
that all the necessary images could be downloaded from the same place?
	In other words, if there was for example a directory structure like this:

testing/daily/i386/current/iso
testing/daily/i386/current/netboot
testing/daily/i386/current/cdrom
testing/daily/i386/current/floppy
etc.?
	And all builds (current, 'beta release', daily, etc.) were found there? 
 Having to snoop around on the list to find out where the best place to 
download the testing images sometimes leads one to the wrong place.

Erik

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

d-i boot logo vote

2004-02-24 Thread Kotrla Vitezslav

Just my vote:

1. mark selby
2. mark riedesel (klowner)
3. andrea mottola


Vit Kotrla
[EMAIL PROTECTED]


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

Re: m68k port status update

2004-02-24 Thread Stephen R Marenka

On Mon, Feb 23, 2004 at 09:24:35PM -0500, Joey Hess wrote:
> Stephen R Marenka wrote:
> > Atari and mvme147 should have netboot targets.
> > 
> > I'm using the term netboot inconsistently on m68k. Ya'll tell me if it
> > should be changed. Amiga, atari, and mac cannot be tftp booted. So the
> > netboot target really just loads components and base off the net instead
> > of a cdrom. The vme's can all be tftp booted. 
> 
> That's really not netboot; i386 does the same for floppy installs.

So you'd rather call these floppy? 

I'll note that i386 can boot off floppy, whereas amiga and mac 
cannot. Would another target name be clearer?

I don't care much one way or the other. So far everything will fit on 
a floppy, but I hadn't much been paying attention to size.

Stephen

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


signature.asc
Description: Digital signature

Re: boot logo vote

On Feb 24, 2004, at 8:57 AM, [EMAIL PROTECTED] wrote:


I vote for the first image on http://sloth.voxel.net/~joshk/d-i-logos/
with the sixth image as runner-up.
Me for the 3rd one, I think it shows a debian "futuristic", something 
that seems to be projected to the future. Good idea to express the 
innovations within the new d-u, isn't?

SteX

SteX
Happy Debian GNU/Linux user since 1998!
---
Spazio ILLIMITATO per la tua Email, Scanner Antivirus,
Antispam, Backup e POP3. Prova la nuova Email di superEva:
http://webmail.supereva.it/
---
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact 
[EMAIL PROTECTED]
I would vote as follows:

First - the sixth one, attributed to Alessandro Polverini and Andrea 
Mottola; a good balance between artful and professional
Second - the fifth one, also by the above persons; if the background of 
the sixth (the debian watermark) were used for this one, it would be my 
favorite

The others are also appealing to me personally, but I am trying to look 
at it from the perspective of appealing to the broadest possible 
audience.  We want the image to convey both the exceptional quality and 
the artful uniqueness that is the Debian distro.  (Can you tell I was a 
marketing major for a while?)

I also believe the chosen image should clearly display that 
characteristic swirl logo that so many Debian fans identify and that 
newcomers will come to know as a familiar and fond image representing 
their favorite Linux distro.

Many thanks to those who have crafted the candidate images.  Just 
seeing them on that page is exciting!

Regards,
--
Barry C. Hawkins
All Things Computed
site: www.allthingscomputed.com
weblog: www.yepthatsme.com


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

Bug#234549: Report installer --successful

2004-02-24 Thread Pau Rul·lan Ferragut

Package: installation-reports

Debian-installer-version: 02 17 2004 / From the Debian website
uname -a: 
Date: 02 20 2004
Method: I downloaded the big installer iso ( the net one). Inserted the CD into the laptop, reboot with the key "c" preset and the installer run. 

Machine: Apple iBook G4 14" 
Processor: PowerPC 933 Mhz
Memory: 256 Mb RAM
Root Device: UltraATA ( IDE ?) ( the only one)
Root Size/partition table: 
	hda4 -- yaboot
	hda5 -- root
	hda6 -- swap

Output of lspci:

Base System Installation Checklist:

Initial boot worked:[o]
Configure network HW:   [o]
Config network: [o]
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:

I am sorry, I can't give more inforation because I am not in that machine.
I am having problems with the XFree86, but that is not installer chores.
I must say I found the installer process very easy and it worket at the first 
;)
Sincerely:
Pau Rul·lan Ferragut


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

Re: debian-installer on arm status

2004-02-24 Thread Wookey

+++ Jeff Bailey [04-02-24 09:19 -0500]:
> On Tue, 2004-02-24 at 08:55, Wookey wrote:
> 
> > D-B people - Is the above still true? ARM currently has (approximately) one
> > kernel per machine. Even just supporting the existing supported stuff and
> > things that have enough resources for installing Debian to be a vaguely
> > sensible thing to do (which excludes quite a lot of potential machines),
> > means at least 10 kernel udebs, and some lesser number of initrds and module
> > sets.
> 
> That's not really that bad.  Given the time limit, it's not bad enough
> that I'd spend any time worrying about it that I could spend doing
> porting work. =)

OK, fair enough.

> > Likely targets that someone cares about enough to support are:
> > Iyonix, RiscPC, Riscstation, Netwinder, Balloon, CATS, LART.
> 
> Looking at the Woody boot disks, ARM has support for CATS, LART, RiscPC
> and Netwinder there.  Are these other ones new machines that are
> supported, or did they fit somehow boot off of those other images?

They are new, although Riscstation and Iyonix have been supported with
special-case bootfloppies stuff for a while now.


Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/


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

Sparc d-i status

May as well post one of these, too. =)

Nightly builds are happening so sparc32-tftp, sparc64-tftp, and
miniiso.  These don't generally work, though.  

#232720 is our major blocker for tftpbooting, there's a patch in the BTS
that the maintainer is reviewing (Thanks James!)

That bug will also affect us for CD booting, but right now I'm working
with Ben Collins to figure out why the kernel's not loading the initrd.

I also remember (was it Thomas?  Blars? hmmm...) mentioning that the
fdisk udeb wasn't getting loaded for some reason.  I'm hoping that the
whole partman thing will make this silently go away before we get there.

Other TODOs:
 - Once we have CD Booting working, start producing snapshots for Manty
to builds CDs from.
 - Switch from piggyback to tilo.  tilo currently doesn't like our
kernels, though.  (This isn't necessary, just a nice to have)

Tks,
Jeff Bailey

-- 
I never know what to expect when you respond to my postings. No insult
intended, you are merely a surprise :)
 - Carlos O'Donnell


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

Re: debian-installer on arm status

On Tue, 2004-02-24 at 08:55, Wookey wrote:

> D-B people - Is the above still true? ARM currently has (approximately) one
> kernel per machine. Even just supporting the existing supported stuff and
> things that have enough resources for installing Debian to be a vaguely
> sensible thing to do (which excludes quite a lot of potential machines),
> means at least 10 kernel udebs, and some lesser number of initrds and module
> sets.

That's not really that bad.  Given the time limit, it's not bad enough
that I'd spend any time worrying about it that I could spend doing
porting work. =)

> Likely targets that someone cares about enough to support are:
> Iyonix, RiscPC, Riscstation, Netwinder, Balloon, CATS, LART.

Looking at the Woody boot disks, ARM has support for CATS, LART, RiscPC
and Netwinder there.  Are these other ones new machines that are
supported, or did they fit somehow boot off of those other images?

Tks,
Jeff Bailey

-- 
I never know what to expect when you respond to my postings. No insult
intended, you are merely a surprise :)
 - Carlos O'Donnell

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

Re: boot logo vote

2004-02-24 Thread stefanomelchior


>I vote for the first image on http://sloth.voxel.net/~joshk/d-i-logos/
>with the sixth image as runner-up.

Me for the 3rd one, I think it shows a debian "futuristic", something that seems to be 
projected to the future. Good idea to express the innovations within the new d-u, 
isn't?

SteX

SteX
Happy Debian GNU/Linux user since 1998!
---
Spazio ILLIMITATO per la tua Email, Scanner Antivirus,
Antispam, Backup e POP3. Prova la nuova Email di superEva:
http://webmail.supereva.it/
---


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

Re: debian-installer on arm status

2004-02-24 Thread Wookey

+++ [EMAIL PROTECTED] [04-02-23 18:53 +]:
> On Mon, Feb 23, 2004 at 05:49:57PM +, Wookey wrote:
> > +++ Peter Naulls [04-02-23 13:07 +]:
> > > In message <[EMAIL PROTECTED]>
> > >   Anthony Towns <[EMAIL PROTECTED]> wrote:
> > > 
> > > > It's time to get debian-installer ported to arm; all the major porting
> > > > work should already have been done getting it to work on other arches,
> > > > so what's left should be fairly straightforward.
> > > > 
> > > > If you can't get this working, arm's status as a supported arch will
> > > > have to be reviewed: there's no point releasing a distribution that
> > > > can't be installed. (It'd be possible to release arm with a different
> > > > installation toolset than d-i, but I can't imagine that'd be any easier
> > > > or much more useful than getting d-i ported)
> > 
> > You're right of course, and as you observe it really is getting to 'make it
> > work or have arse kicked' time. Part of the problem is of course that arm
> > installation has always been somewhat 'distributed'  - there is a special
> > version of bootfloppies for most 'supported' machines because the default
> > one doesn't actaully work, and an awful lot of people using debian-derived
> > stuff don't use either b-f or d-i to get things installed - they use some
> > random bootloader for the board in question.
> > 
> > So in fact debian-arm remains useful to a lot of people even without a
> > working debian-installer.
> > 
> > That's not really an adequate excuse for not making it work on at least the
> > suitable machines, and hopefully it will be better suited to weird hardware
> > than b-f was. We'll see.

I've now got uptodate on d-i again at alioth and will take a look at
what needs doing for lart/balloon.

> > Poor old vince has found he can't do the kernel _and_ D-I - there aren't
> > enough hours in the day.
> 
> While true to some extent I did get D-I to the point where I had
> working tftp images for winder, bast, riscstation. I tried to talk to
> #debian-boot about autobuilders and kernel-image builders and (as
> usual) got blown off, this was several months ago and my tree is now
> very very out of date so needs to be done again...
> 
> One point, I was going to use the kernel udeb image thingy but in its
> current form adding all the ARM sub arches would make it generate an
> additional 40odd packages from the one source...this seemed grossly
> excessive and I wanted to find a more elegant solution.
> 
> One issue which was being cleared up but hadn't been resolved was that
> the final image stuff wanted to put a single vmlinuz file down for all
> sub arches...with several subarches to choose from we ended up without
> a sensible kernel for the bootloader to start except for one target :-/

OK - we need to have this discussion on debian-boot I think, in order to
work out how best to proceed, so I've added it.

D-B people - Is the above still true? ARM currently has (approximately) one
kernel per machine. Even just supporting the existing supported stuff and
things that have enough resources for installing Debian to be a vaguely
sensible thing to do (which excludes quite a lot of potential machines),
means at least 10 kernel udebs, and some lesser number of initrds and module
sets.

Likely targets that someone cares about enough to support are:
Iyonix, RiscPC, Riscstation, Netwinder, Balloon, CATS, LART.

Advice on best way to proceed is welcome.

For much arm hardware using debootstrap rather than D-I may actually make
more sense/be easier. We (arm people) need to look at that too.

Wookey
-- 
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK  Tel +44 (0) 1223 811679
work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/


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

boot logo vote

2004-02-24 Thread Hans Fugal

I vote for the first image on http://sloth.voxel.net/~joshk/d-i-logos/
with the sixth image as runner-up.

-- 
 .O.  Hans Fugal| De gustibus non disputandum est.
 ..O  http://hans.fugal.net | Debian, vim, mutt, ruby, text, gpg
 OOO| WindowMaker, gaim, UTF-8, RISC, JS Bach
-
GnuPG Fingerprint: 6940 87C5 6610 567F 1E95  CB5E FC98 E8CD E0AA D460


signature.asc
Description: Digital signature

Bug#234529: strings truncated

2004-02-24 Thread Konstantinos Margaritis

Package: base-config
Version: 2.12
Severity: normal
Tags: l10n

When using locale el_GR.UTF-8, all the strings are truncated up to a
certain column. It doesn't matter whether I run this from normal
console, jfbterm or an X term, it's always the same. The messages are
uncomprehensible since a lot of information is missing.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux silmaril 2.4.24 #1 Wed Feb 18 14:14:52 EET 2004 i686
Locale: LANG=el_GR.UTF-8, LC_CTYPE=el_GR.UTF-8

Versions of packages base-config depends on:
ii  adduser 3.51 Add and remove users and groups
ii  apt 0.5.22   Advanced front-end for dpkg
ii  aptitude0.2.13-2 curses-based apt frontend
ii  bsdutils1:2.12-3 Basic utilities from 4.4BSD-Lite
ii  console-data2002.12.04dbs-28 Keymaps, fonts, charset maps, fall
ii  console-tools   1:0.2.3dbs-47Linux console and font utilities
ii  debconf 1.3.22   Debian configuration management sy
ii  debianutils 2.6.2Miscellaneous utilities specific t
ii  gettext-base0.13.1-2 GNU Internationalization utilities
ii  passwd  1:4.0.3-17   Change and administer password and

-- debconf information excluded



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

Mini Iso

2004-02-24 Thread Andree=20K=F6rber

Hello
being a newbie I have a very basic question about your minni isos. Do I need all four 
or just one of them? I'd like to install Debian on an Athlon 2000+ 
THank you for your help
Andrew
__
Extra-Konto: 2,50 %* Zinsen p. a. ab dem ersten Euro! Nur hier mit 25
Euro-Tankgutschein & ExtraPrämie! https://extrakonto.web.de/?mc=021110


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

Re: release status

2004-02-24 Thread Kenshi Muto

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

At 24 Feb 04 01:39:23 GMT,
Joey Hess wrote:
>  - BIDI support (for Arabic)

Well, this is one of i18n TODO.

Others TODO I know are:

- - update shadow package (Bug#227237 and others). NMU?
- - cfdisk-udeb (util-linux package) utf-8 support. Bug#229875. NMU?
  (but doesn't Lamont look active on IRC?)
- - bterm-unifont reloading. Bug#232397.

Thanks,
- -- 
Kenshi Muto
[EMAIL PROTECTED]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 

iEYEARECAAYFAkA7ScsACgkQQKW+7XLQPLEcmwCeKdXbqC7Os3IzSYA5JrZb9gdm
LvMAni+cawzxkdLwcsRT4WHoJYHyCgCp
=XYpr
-END PGP SIGNATURE-


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

Re: release status