Bug#156452: Wanna bulk up

[Gale Waller]

rebuild the South by educating it's youth. Lee truly felt his great purpose
in what people would think of him if he pulled outrageous stunts. When Gene
told him that

http://es.geocities.com/GastonqiTgxnjE/ is the store to disappear those pds

ant. Most shoe stores in the U.S. sell a range of Brazilian-made shoes,
while Brazilian aircraft are 

presenting them in The Awakening.The Hobbit by J.R.R. Tolkien is set in a
fantasy world that has



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

a little problem with my custom debian cd

[Pierre DURAND]

hello 
I'm making my own custom debian cd .
I'have choose to change the orignal kernel 2.6 from sarge cd to a 2.6.15
from etch .
My cd boot and all seems working fine, but after partitioning the installer
failed and i'have this debug message : 
run_program: exec of program '/lib/udev/volumid' failed 
Plesea help, i'have change the udev package from the original cd but that
failed again .
Thanks for all
bye

Bug#341380: lilo-installer cannot handle image in /boot

[Hermann Lauer]

Hi all,

will this issue be fixed in an installer update for sarge ?

At the moment I'm generating two links from my preseed file with the
following kludge to get lilo-installer running:

d-i preseed/early_command   string echo ln -s boot/initrd.img 
/target/initrd.img; ln -s boot/vmlinuz /target/vmlinuz 
/usr/lib/base-installer.d/40netcfg


Thanks,

  Hermann


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

Bug#359649: discover1: BinNMU will FTBFS

[Daniel Schepler]

Package: discover1
Version: 1.7.17
Severity: serious

I tried building discover1 with a version of 1.7.17+pb1 here and got this from
pbuilder:

...
sh debian/check-configure.sh
dpkg-parsechangelog: warning: no utmp entry available and LOGNAME not defined; 
using uid of process (1234)
debian: warning: no utmp entry available and LOGNAME not defined; using uid of 
process (1234)
Versions in AC_INIT/changelog do not match. Fix and run autogen.sh.
Configure says: 1.7.17   debian/changelog says: 1.7.17+pb1
make: *** [config.status] Error 1
-- 
Daniel Schepler


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

Bug#355851: a blindunfriendly debian installer problem

[Samuel Thibault]

Samuel Thibault, le Tue 28 Mar 2006 01:06:55 +0200, a écrit :
 Joey Hess, le Mon 27 Mar 2006 16:51:45 -0500, a écrit :
  if there is a way for udev to discover braille devices
  that would be an excellent way to go.
 
 Here is a .rules file that should work fine

Mmm, sorry, here is one that actually _does_ work :)

However, although it works well when hotplugging the device after
bootup, it does not when booting with the device already plugged,
because USB seems to be discovered before vcsa nodes are available,
hence brltty fails.

Dave, maybe we should add a little loop for trying to open vcsa a few
times before failing?

Regards,
Samuel
# udev rules file for brltty
#

ACTION!=add, GOTO=brltty_rules_end
SUBSYSTEM!=usb_device, GOTO=brltty_rules_end

# Alva
SYSFS{idVendor}==06b0, SYSFS{idProduct}==0001, RUN+=/sbin/brltty -b al -d 
usb: 

# Baum
SYSFS{idVendor}==0403, SYSFS{idProduct}==fe71, RUN+=/sbin/brltty -b bm -d 
usb: 
SYSFS{idVendor}==0403, SYSFS{idProduct}==fe72, RUN+=/sbin/brltty -b bm -d 
usb: 
SYSFS{idVendor}==0403, SYSFS{idProduct}==fe73, RUN+=/sbin/brltty -b bm -d 
usb: 
SYSFS{idVendor}==0403, SYSFS{idProduct}==fe74, RUN+=/sbin/brltty -b bm -d 
usb: 
SYSFS{idVendor}==0403, SYSFS{idProduct}==fe75, RUN+=/sbin/brltty -b bm -d 
usb: 

# FreedomScientific
SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0100, RUN+=/sbin/brltty -b fs -d 
usb: 
SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0111, RUN+=/sbin/brltty -b fs -d 
usb: 
SYSFS{idVendor}==0f4e, SYSFS{idProduct}==0112, RUN+=/sbin/brltty -b fs -d 
usb: 

# HandyTech
SYSFS{idVendor}==0921, SYSFS{idProduct}==1200, RUN+=/sbin/brltty -b ht -d 
usb: 
SYSFS{idVendor}==0403, SYSFS{idProduct}==6001, RUN+=/sbin/brltty -b ht -d 
usb: 

# Papenmeier
SYSFS{idVendor}==0403, SYSFS{idProduct}==f208, RUN+=/sbin/brltty -b pm -d 
usb: 

# Voyager
SYSFS{idVendor}==0798, SYSFS{idProduct}==0001, RUN+=/sbin/brltty -b vo -d 
usb: 

LABEL=brltty_rules_end

Processed: BinNMU bugs are (apparently) not RC, add usertags

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 user [EMAIL PROTECTED]
Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]).
 severity 359634 important
Bug#359634: apt: binNMU will FTBFS
Bug#359035: apt: mising builddep on autoconf
Severity set to `important'.

 severity 359649 important
Bug#359649: discover1: BinNMU will FTBFS
Severity set to `important'.

 severity 359652 important
Bug#359652: libsoup: binNMU's will be broken
Severity set to `important'.

 usertag 359634 binnmu
There were no usertags set.
Usertags are now: binnmu.
 usertag 359649 binnmu
There were no usertags set.
Usertags are now: binnmu.
 usertag 359652 binnmu
There were no usertags set.
Usertags are now: binnmu.
 usertag 359636 binnmu
There were no usertags set.
Usertags are now: binnmu.
 usertag 359632 binnmu
There were no usertags set.
Usertags are now: binnmu.
 thanks
Stopping processing here.

Please contact me if you need assistance.

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


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

Processed: severity of 359649 is important

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.15
  # binNMU support is not RC in general
 severity 359649 important
Bug#359649: discover1: BinNMU will FTBFS
Severity set to `important'.


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: Bug#359062: debian-installer: bterm is not (yet) accessible for brltty

[Samuel Thibault]

Hi,

Here are quick-and-dirty-but-working implementations.

Regards,
Samuel
diff -ur bogl-0.1.18/bogl-term.c bogl-0.1.18-mine/bogl-term.c
--- bogl-0.1.18/bogl-term.c 2003-11-05 05:38:22.0 +0100
+++ bogl-0.1.18-mine/bogl-term.c2006-03-28 04:09:07.0 +0200
@@ -26,24 +26,84 @@
 
 #include bogl.h
 #include bogl-term.h
+#include sys/mman.h
+#include fcntl.h
+#include stdio.h
+#include unistd.h
+#include string.h
+#include errno.h
 
 #define MAX_CCHARS 5
 
-struct bogl_term *bogl_term_new(struct bogl_font *font)
+static void *mmaped_alloc(const char *map_path, const char *file, size_t size, 
int zero)
+{
+  void *ptr;
+  if (map_path) {
+char c[strlen(map_path) + 1 + strlen(file) + 1];
+static const char zero = 0;
+int fd;
+snprintf(c, sizeof(c), %s/%s, map_path, file);
+fd = open(c, O_RDWR|O_CREAT|O_TRUNC, 0400);
+if (fd  0)
+  return NULL;
+if (lseek(fd, size - 1, SEEK_SET)  0
+   || write(fd, zero, 1)  0) {
+  close(fd);
+  unlink(c);
+  return NULL;
+}
+ptr = mmap(NULL, size, PROT_READ|PROT_WRITE, MAP_SHARED, fd, 0);
+close(fd);
+if (!ptr) {
+  unlink(c);
+  return NULL;
+}
+if (zero)
+  memset(ptr, 0, size - 1);
+  } else {
+if (zero)
+  ptr = calloc(size, 1);
+else
+  ptr = malloc(size);
+  }
+  return ptr;
+}
+
+static void mmaped_free(const char *map_path, const char *file, void *ptr, 
size_t size)
+{
+  if (map_path) {
+char c[strlen(map_path) + 1 + strlen(file) + 1];
+if (!ptr)
+  return;
+snprintf(c, sizeof(c), %s/%s, map_path, file);
+munmap(ptr, size);
+unlink(c);
+  } else {
+free(ptr);
+  }
+}
+
+struct bogl_term *bogl_term_new(struct bogl_font *font, const char *map_path)
 {
   struct bogl_term *term;
   int i;
 
-  term = calloc(sizeof(struct bogl_term), 1);
-  if (!term)
+  if (mkdir(map_path, 0755)  errno != EEXIST)
 return 0;
 
+  term = mmaped_alloc(map_path, term, sizeof(struct bogl_term), 1);
+  if (!term) {
+rmdir(map_path);
+return 0;
+  }
+
   term-font = font;
   term-xbase = term-ybase = 0;
   term-xstep = bogl_font_glyph(font, ' ', 0);
   term-ystep = bogl_font_height(font);
   if (term-xstep = 0 || term-ystep = 0) {
-free(term);
+mmaped_free(map_path, term, term, sizeof(struct bogl_term));
+rmdir(map_path);
 return 0;
   }
 
@@ -57,20 +117,21 @@
   term-cur_visible = 1;
   memset(term-ps, 0, sizeof(term-ps));
 
-  term-screen = malloc(term-xsize * term-ysize * sizeof(wchar_t));
+  term-screen = mmaped_alloc(map_path, screen, term-xsize * term-ysize * 
sizeof(wchar_t), 0);
   term-dirty = malloc(term-xsize * term-ysize);
-  term-screenfg = malloc(term-xsize * term-ysize * sizeof(int));
-  term-screenbg = malloc(term-xsize * term-ysize * sizeof(int));
-  term-screenul = malloc(term-xsize * term-ysize * sizeof(int));
+  term-screenfg = mmaped_alloc(map_path, screenfg, term-xsize * 
term-ysize * sizeof(int), 0);
+  term-screenbg = mmaped_alloc(map_path, screenbg, term-xsize * 
term-ysize * sizeof(int), 0);
+  term-screenul = mmaped_alloc(map_path, screenul, term-xsize * 
term-ysize * sizeof(int), 0);
   term-cchars = malloc(term-xsize * term-ysize * sizeof(wchar_t *));
   if (!term-screen || !term-screenfg || !term-screenbg || !term-screenul 
|| !term-cchars || !term-dirty) {
-free(term-screen);
-free(term-screenfg);
-free(term-screenbg);
-free(term-screenul);
+mmaped_free(map_path, screen, term-screen, term-xsize * term-ysize * 
sizeof(wchar_t));
+mmaped_free(map_path, screenfg, term-screenfg, term-xsize * 
term-ysize * sizeof(int));
+mmaped_free(map_path, screenbg, term-screenbg, term-xsize * 
term-ysize * sizeof(int));
+mmaped_free(map_path, screenul, term-screenul, term-xsize * 
term-ysize * sizeof(int));
 free(term-cchars);
 free(term-dirty);
-free(term);
+mmaped_free(map_path, term, term, sizeof(struct bogl_term));
+rmdir(map_path);
 return 0;
   }
   for (i = 0; i  term-xsize * term-ysize; i++) {
diff -ur bogl-0.1.18/bogl-term.h bogl-0.1.18-mine/bogl-term.h
--- bogl-0.1.18/bogl-term.h 2003-11-05 04:01:47.0 +0100
+++ bogl-0.1.18-mine/bogl-term.h2006-03-28 04:02:33.0 +0200
@@ -26,7 +26,7 @@
   int acs;
 };
 
-struct bogl_term *bogl_term_new(struct bogl_font *font);
+struct bogl_term *bogl_term_new(struct bogl_font *font, const char *map_path);
 void bogl_term_out(struct bogl_term *term, char *s, int n);
 void bogl_term_redraw(struct bogl_term *term);
 void bogl_term_delete(struct bogl_font *font);
diff -ur bogl-0.1.18/bterm.c bogl-0.1.18-mine/bterm.c
--- bogl-0.1.18/bterm.c 2004-07-22 12:39:42.0 +0200
+++ bogl-0.1.18-mine/bterm.c2006-03-28 02:12:53.0 +0200
@@ -217,7 +217,7 @@
   struct timeval tv;
   int ptyfd, ttyfd;
   struct bogl_font *font;
-  char *locale = , *command = NULL;
+  char *locale = , *command = NULL, *map_path = NULL;
   int i;
   char o = ' ';
   int pending = 0;
@@ -228,6 +228,7 

Bug#359663: [INTL:km] base-config_debian_po

[kakada]

Package: base-config_debian_po_km.po
Version: N/A
Severity: wishlist
Tags: l10n patch


# translation of base-config_debian_po_km.po to Khmer
# Hok Kakada [EMAIL PROTECTED], 2005, 2006.
# Khoem Sokhem [EMAIL PROTECTED], 2006.
msgid 
msgstr 
Project-Id-Version: base-config_debian_po_km\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2005-12-05 21:15-0700\n
PO-Revision-Date: 2006-03-27 15:24+0700\n
Last-Translator: Khoem Sokhem [EMAIL PROTECTED]\n
Language-Team: Khmer [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: KBabel 1.11\n

#. Type: title
#. Description
#: ../templates:3
msgid Base system configuration
msgstr ការ​កំណត់​រចនា​សម្ព័ន្ធ​របស់​​ប្រព័ន្ធ​មូលដ្ឋាន

#. Type: select
#. Description
#: ../templates:8
msgid Choose the next step in the install process:
msgstr ជ្រើស​ជំហាន​បន្ទាប់​ក្នុង​ដំណើរការ​​ដំឡើង ៖

#. Type: select
#. Description
#: ../templates:8
msgid This is the base system configuration menu.
msgstr នេះ​ជា​ម៉ឺនុយ​កំណត់​រចនា​សម្ព័ន្ធ​របស់​​ប្រព័ន្ធ​មូលដ្ឋាន ។

#. Type: note
#. Description
#: ../templates:13
msgid Welcome to your newly installed system!
msgstr សូម​ស្វាគមន៍​មក​កាន់​ប្រព័ន្ធ​ដែល​បាន​ដំឡើង​បច្ចុប្បន្ន​​របស់​អ្នក !

#. Type: note
#. Description
#: ../templates:13
msgid 
This program will now walk you through the process of setting up your newly 
installed system.
msgstr ឥឡូវ កម្មវិធី​នេះ​នឹង​ណែនាំ​អ្នក​អំពី​​ដំណើរ​ការ​​ដំឡើង​ប្រព័ន្ធ​ដែល​បាន​ដំឡើង​បច្ចុប្បន្ន ។

#. Type: boolean
#. Description
#: ../templates:20
msgid Use a PPP connection to install the system?
msgstr ប្រើ​តំណ PPP មួយ​ដើម្បី​ដំឡើង​ប្រព័ន្ធ​នេះឬ ?

#. Type: boolean
#. Description
#: ../templates:20
msgid 
This system does not seem to be currently connected to the internet. Even if 
you plan to install from CD, it is wise to download at least security 
updates from the internet.
msgstr ប្រព័ន្ធ​នេះ​ហាក់​បី​ដូច​ជា​មិន​ត្រូវ​បាន​តភ្ជាប់​ទៅ​អ៊ិនធឺណិត​បច្ចុប្បន្ន​ទេ ។ ទោះបី​ជា​អ្នក​មាន​គម្រោង​ដំឡើង​ពី​ស៊ីឌីក៏​ដោយ វា​ឆ្លាត​​ដើម្បី​ទាញ​យក​យ៉ាង​ហោច​ណាស់​​ការ​ធ្វើឲ្យ​​សុវត្ថិភាព​​ទាន់​សម័យ​ពី​​អ៊ីនធឺណិត ។

#. Type: boolean
#. Description
#: ../templates:20
msgid 
If you have an account on an Internet Services Provider (ISP), and you want 
to use it during the install, you may configure the PPP service now, and 
open a PPP connection to your ISP.
msgstr ប្រសិន​បើ​​អ្នក​មាន​គណនី​មួយ​នៅ​ក្រុមហ៊ុន​ផ្ដល់​​សេវា​​អ៊ីនធឺណិត (ISP) ហើយ​អ្នក​ចង់​ប្រើ​វា​កំឡុង​ពេល​ដំឡើង អ្នក​អាច​​កំណត់​រចនាសម្ព័ន្ធ​សេវា PPP ឥឡូវ រួច​បើក​តំណ PPP ទៅ (ISP) របស់​អ្នក ។

#. Type: note
#. Description
#: ../templates:31
msgid Thank you for choosing Debian!
msgstr សូម​អរគុណ​សម្រាប់​ការ​ជ្រើស​យក​ដេបៀន !​

#. Type: note
#. Description
#: ../templates:31
msgid 
Setup of your Debian system is complete. You may now login at the login: 
prompt.
msgstr ការ​ដំឡើង​ប្រព័ន្ធ​ដេបៀន​របស់​អ្នក​បាន​បញ្ចប់ ។ ឥឡូវ​ អ្នក​អាច​ចូល​នៅ​​ត្រង់​ប្រអប់​ចូល​បាន​ ។

#. Type: note
#. Description
#: ../templates:31
msgid 
If you want to revisit this setup process at a later date, just run the base-
config program.
msgstr ប្រសិន​បើ​​អ្នក​ចង់​ទស្សនា​​ដំណើរការ​ដំឡើង​នេះ​ម្ដង​ទៀត​នៅ​ពេល​ក្រោយ 

Bug#359664: [INTL:km] base-config_po translation

[kakada]

Package:base-config_po_km.po
Version:N/A
Severity: wishlist
Tags:l10n patch
# translation of base-config_po_km.po to Khmer
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
# Hok Kakada [EMAIL PROTECTED], 2005.
# Khoem Sokhem [EMAIL PROTECTED], 2006.
msgid 
msgstr 
Project-Id-Version: base-config_po_km\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2005-12-12 18:15-0700\n
PO-Revision-Date: 2006-03-27 15:26+0700\n
Last-Translator: Khoem Sokhem [EMAIL PROTECTED]\n
Language-Team: Khmer [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: KBabel 1.11\n

#: ../base-config:55
msgid Configuring the base system...
msgstr កំពុង​កំណត់​រចនា​សម្ព័ន្ធ​របស់​​ប្រព័ន្ធ​មូលដ្ឋាន...

#: ../lib/menu/shell:3
msgid Type 'exit' to return to base-config.
msgstr វាយ 'exit' ដើម្បី​ត្រឡប់​ទៅ base-config ។

Bug#359333: Acknowledgement (discover1-udeb should not depend on non-udeb libdiscover1)

[Otavio Salvador]

Christian Perrier [EMAIL PROTECTED] writes:

 I've abused my commit rights and commited the patch, betting that you
 would have done so yourself, Joey, and that debhelper-related changes
 by the debhelper author are probably safe..:-)

Hey! We're a team!

 I'm even considering building and uploading the file if noone else
 cares to. However, Otavio probably can also. Otavio? My loose
 understanding of this bug is that it would help d-i if it is fixed.

Go ahead and upload it. I'll work on Debian packages again just in
friday so would be good if you could upload it yourself.

-- 
O T A V I OS A L V A D O R
-
 E-mail: [EMAIL PROTECTED]  UIN: 5906116
 GNU/Linux User: 239058 GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
-
Microsoft gives you Windows ... Linux gives
 you the whole house.


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

Re: Bug#359164: [powerpc64] d-i fails, base-installer/initramfs/no-generator

[Martin Michlmayr]

* Sven Luther [EMAIL PROTECTED] [2006-03-28 10:32]:
  Did you actually take *any look* at the failure at all?  If so, you'd
  know that you're blaming the wrong people...
 Actually, Frans is blaming me, so ...

You mean for not taking a look at the build logs from time to time,
and a new installing a package every few months?
-- 
Martin Michlmayr
http://www.cyrius.com/


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

Bug#355851: a blindunfriendly debian installer problem

[Dave Mielke]

[quoted lines by Samuel Thibault on 2006/03/28 at 11:41 +0200]

Hi:

However, although it works well when hotplugging the device after
bootup, it does not when booting with the device already plugged,
because USB seems to be discovered before vcsa nodes are available,
hence brltty fails.

brltty makes any vcsa devices which it needs but aren't there yet.

-- 
Dave Mielke   | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: [EMAIL PROTECTED] | Canada  K2A 1H7   | if you're concerned about Hell.
http://FamilyRadio.com/   | http://Mielke.cc/bible/


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

Re: Bug#295476: add support for disabling auto-eject

[Christoph Kobe]

Hi,
I've just installed Debian Sarge (Using the network-install-CD 3.1_r1a) to a new Server 
which was nearly damaged due to the cd-eject feature without prior warning at

the end of the installation procedure.
After looking around for some time I found that there has been a 
discussion already about this subject. I am now trying to convince you to 
remove this annoying behaviour from the installation procedure. I have 
understood the reasons for including this feature and I'm sure that 
there's an alternative to what's happening right now that will satisfy 
both sides.


A solution could look like this:

Message: The system will be rebooted. Do you want to eject the CD to make sure 
you're not booting the installation system but you newly installed debian 
system?

no = reboot without ejecting the CD
yes = next message:
Please remove the CD and hit Enter to reboot.

I know this is one more question during the install process, but there are 
good reasons why this question should be added:


1. The user should keep control over his hardware, ejecting a CD without 
prior warning has been annoying to many user I know (Nero does this, too)


2. There's always the risk that by ejecting the CD, the users hardware is 
damaged or even worse. Do you sit in front of your computer during the 
whole installation procedure? I usually do different things at the same 
time and walk around the room and a suddenly ejecting CD could even cause 
an accident this way. This nearly happened to me when I first used Nero to 
burn a CD and was not aware of what was going to happen.


3. Everyone installing a debian system should know what he is doing and 
should be aware of the fact that the computer would start from the cd 
again if he didn't remove it. I don't think Debian should be adapted to 
people who cannot handle a computer.


If you're not going to remove this annoying feature, please include at least a 
warning for the user and instructions on how to disable the automatic cd-eject.

See also:
http://lists.debian.org/debian-boot/2005/02/msg00540.html

I don't know if this patch has been applied already and I don't know where to look for 
this but as far as I know it hasn't The Sarge version of the installer does not 
have this option:
http://lists.debian.org/debian-boot/2005/09/msg00107.html


Thanks for your attention,

Christoph Kobe


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

Re: Bug#295476: add support for disabling auto-eject

[Frans Pop]

On Tuesday 28 March 2006 14:46, Christoph Kobe wrote:
 Hi,
 I've just installed Debian Sarge (Using the network-install-CD 3.1_r1a)
 to a new Server which was nearly damaged due to the cd-eject feature
 without prior warning at the end of the installation procedure.

There is a boot option that allows you to disable ejecting the CD:
http://d-i.alioth.debian.org/manual/en.i386/ch05s02.html#installer-args

Adding an extra question was decided against as you _are_ warned that the 
CD will be ejected.

Cheers,
FJP


pgptBl5ryAm91.pgp
Description: PGP signature

Re: Bug#295476: add support for disabling auto-eject

[Frans Pop]

On Tuesday 28 March 2006 14:46, Christoph Kobe wrote:
 I've just installed Debian Sarge (Using the network-install-CD 3.1_r1a)
 to a new Server which was nearly damaged due to the cd-eject feature
 without prior warning at the end of the installation procedure.

There is a boot option that allows you to disable ejecting the CD:
http://d-i.alioth.debian.org/manual/en.i386/ch05s02.html#installer-args

Note: this feature is only available in the Etch version of the installer.


pgp9MeOTKwIwX.pgp
Description: PGP signature

Bug#359663: marked as done ([INTL:km] base-config_debian_po)

[Debian Bug Tracking System]

Your message dated Tue, 28 Mar 2006 14:37:55 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#359663: [INTL:km] base-config_debian_po
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)

---BeginMessage---
Package: base-config_debian_po_km.po
Version: N/A
Severity: wishlist
Tags: l10n patch


# translation of base-config_debian_po_km.po to Khmer
# Hok Kakada [EMAIL PROTECTED], 2005, 2006.
# Khoem Sokhem [EMAIL PROTECTED], 2006.
msgid 
msgstr 
Project-Id-Version: base-config_debian_po_km\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2005-12-05 21:15-0700\n
PO-Revision-Date: 2006-03-27 15:24+0700\n
Last-Translator: Khoem Sokhem [EMAIL PROTECTED]\n
Language-Team: Khmer [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: KBabel 1.11\n

#. Type: title
#. Description
#: ../templates:3
msgid Base system configuration
msgstr ការ​កំណត់​រចនា​សម្ព័ន្ធ​របស់​​ប្រព័ន្ធ​មូលដ្ឋាន

#. Type: select
#. Description
#: ../templates:8
msgid Choose the next step in the install process:
msgstr ជ្រើស​ជំហាន​បន្ទាប់​ក្នុង​ដំណើរការ​​ដំឡើង ៖

#. Type: select
#. Description
#: ../templates:8
msgid This is the base system configuration menu.
msgstr នេះ​ជា​ម៉ឺនុយ​កំណត់​រចនា​សម្ព័ន្ធ​របស់​​ប្រព័ន្ធ​មូលដ្ឋាន ។

#. Type: note
#. Description
#: ../templates:13
msgid Welcome to your newly installed system!
msgstr សូម​ស្វាគមន៍​មក​កាន់​ប្រព័ន្ធ​ដែល​បាន​ដំឡើង​បច្ចុប្បន្ន​​របស់​អ្នក !

#. Type: note
#. Description
#: ../templates:13
msgid 
This program will now walk you through the process of setting up your newly 
installed system.
msgstr ឥឡូវ កម្មវិធី​នេះ​នឹង​ណែនាំ​អ្នក​អំពី​​ដំណើរ​ការ​​ដំឡើង​ប្រព័ន្ធ​ដែល​បាន​ដំឡើង​បច្ចុប្បន្ន ។

#. Type: boolean
#. Description
#: ../templates:20
msgid Use a PPP connection to install the system?
msgstr ប្រើ​តំណ PPP មួយ​ដើម្បី​ដំឡើង​ប្រព័ន្ធ​នេះឬ ?

#. Type: boolean
#. Description
#: ../templates:20
msgid 
This system does not seem to be currently connected to the internet. Even if 
you plan to install from CD, it is wise to download at least security 
updates from the internet.
msgstr ប្រព័ន្ធ​នេះ​ហាក់​បី​ដូច​ជា​មិន​ត្រូវ​បាន​តភ្ជាប់​ទៅ​អ៊ិនធឺណិត​បច្ចុប្បន្ន​ទេ ។ ទោះបី​ជា​អ្នក​មាន​គម្រោង​ដំឡើង​ពី​ស៊ីឌីក៏​ដោយ វា​ឆ្លាត​​ដើម្បី​ទាញ​យក​យ៉ាង​ហោច​ណាស់​​ការ​ធ្វើឲ្យ​​សុវត្ថិភាព​​ទាន់​សម័យ​ពី​​អ៊ីនធឺណិត ។

#. Type: boolean
#. Description
#: ../templates:20
msgid 
If you have an account on an Internet Services Provider (ISP), and you want 
to use it during the install, you may configure the PPP service now, and 
open a PPP connection to your ISP.
msgstr ប្រសិន​បើ​​អ្នក​មាន​គណនី​មួយ​នៅ​ក្រុមហ៊ុន​ផ្ដល់​​សេវា​​អ៊ីនធឺណិត (ISP) ហើយ​អ្នក​ចង់​ប្រើ​វា​កំឡុង​ពេល​ដំឡើង អ្នក​អាច​​កំណត់​រចនាសម្ព័ន្ធ​សេវា PPP ឥឡូវ រួច​បើក​តំណ PPP ទៅ (ISP) របស់​អ្នក ។

#. Type: note
#. Description
#: ../templates:31
msgid Thank you for choosing Debian!
msgstr សូម​អរគុណ​សម្រាប់​ការ​ជ្រើស​យក​ដេបៀន !​

#. Type: note
#. Description
#: ../templates:31
msgid 
Setup of your Debian system is complete. You may now login at the login: 
prompt.

Bug#359664: marked as done ([INTL:km] base-config_po translation)

[Debian Bug Tracking System]

Your message dated Tue, 28 Mar 2006 14:37:55 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#359663: [INTL:km] base-config_debian_po
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)

---BeginMessage---
Package:base-config_po_km.po
Version:N/A
Severity: wishlist
Tags:l10n patch
# translation of base-config_po_km.po to Khmer
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
#
# Hok Kakada [EMAIL PROTECTED], 2005.
# Khoem Sokhem [EMAIL PROTECTED], 2006.
msgid 
msgstr 
Project-Id-Version: base-config_po_km\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2005-12-12 18:15-0700\n
PO-Revision-Date: 2006-03-27 15:26+0700\n
Last-Translator: Khoem Sokhem [EMAIL PROTECTED]\n
Language-Team: Khmer [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=UTF-8\n
Content-Transfer-Encoding: 8bit\n
X-Generator: KBabel 1.11\n

#: ../base-config:55
msgid Configuring the base system...
msgstr កំពុង​កំណត់​រចនា​សម្ព័ន្ធ​របស់​​ប្រព័ន្ធ​មូលដ្ឋាន...

#: ../lib/menu/shell:3
msgid Type 'exit' to return to base-config.
msgstr វាយ 'exit' ដើម្បី​ត្រឡប់​ទៅ base-config ។

---End Message---
---BeginMessage---
Quoting kakada ([EMAIL PROTECTED]):
 Package: base-config_debian_po_km.po
 Version: N/A
 Severity: wishlist
 Tags: l10n patch

base-config is no more maintained and, actually, no more part of D-I
level2

Anyway, there is also no more translatable material in what remains.

Sorry for the extra work you had to do...:-[



signature.asc
Description: Digital signature
---End Message---

Re: Changing udebs priority

[Abel Martín]

I forgot to say that I'm using a sarge-based installer. Must I use
etch installer to change udebs priorities?

Processing of discover1_1.7.18_i386.changes

[Archive Administrator]

discover1_1.7.18_i386.changes uploaded successfully to localhost
along with the files:
  discover1_1.7.18.dsc
  discover1_1.7.18.tar.gz
  discover1_1.7.18_i386.deb
  libdiscover1_1.7.18_i386.deb
  libdiscover1-dev_1.7.18_i386.deb
  libdiscover1-pic_1.7.18_i386.deb
  discover1-udeb_1.7.18_i386.udeb
  libdiscover1-udeb_1.7.18_i386.udeb

Greetings,

Your Debian queue daemon


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

discover1_1.7.18_i386.changes is NEW

[Debian Installer]

discover1-udeb_1.7.18_i386.udeb
  to pool/main/d/discover1/discover1-udeb_1.7.18_i386.udeb
discover1_1.7.18.dsc
  to pool/main/d/discover1/discover1_1.7.18.dsc
discover1_1.7.18.tar.gz
  to pool/main/d/discover1/discover1_1.7.18.tar.gz
discover1_1.7.18_i386.deb
  to pool/main/d/discover1/discover1_1.7.18_i386.deb
libdiscover1-dev_1.7.18_i386.deb
  to pool/main/d/discover1/libdiscover1-dev_1.7.18_i386.deb
libdiscover1-pic_1.7.18_i386.deb
  to pool/main/d/discover1/libdiscover1-pic_1.7.18_i386.deb
(new) libdiscover1-udeb_1.7.18_i386.udeb extra debian-installer
hardware identification library (udeb)
libdiscover1_1.7.18_i386.deb
  to pool/main/d/discover1/libdiscover1_1.7.18_i386.deb
Changes: discover1 (1.7.18) unstable; urgency=low
 .
  [ Otavio Salvador ]
  * Improve autogen.sh script to make sure that we include all need files.
  * Change debhelper compatibility level to 4. I'll keep it until Etch is
released.
 .
  [ Joey Hess ]
  * Produce a nice clean libdiscover1-udeb and make discover1-udeb
depend on that.
  * remove debian/libdiscover1.shlibs to allow for dh_makeshlibs do its magic
  * Fix the description of discover1-udeb
Announcing to debian-devel-changes@lists.debian.org


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

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


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

Re: Bug#359164: [powerpc64] d-i fails, base-installer/initramfs/no-generator

[Colin Watson]

On Mon, Mar 27, 2006 at 04:43:12PM +0200, Sven Luther wrote:
 On Mon, Mar 27, 2006 at 02:23:47AM +0200, Frans Pop wrote:
  This is not an initramfs-tools problem, but the result of powerpc daily 
  d-i builds, for which Sven himself is responsible, failing for the last 
  few days.
 
 I didn't touch the buildd since more than a week, so it is clear that (again)
 the d-i team broke the daily builds and don't take the responsability to fix
 them. Bashing on your porter is fine, but then don't expect them to fix stuff
 at your whim, and do the job yourself.
 
 I hereby officially announce that i won't continue to do the ungratefull job
 of powerpc d-i porting, i hear the d-i team has plenty of folk to take my
 place, so they should fix this.

I've set up http://people.debian.org/~cjwatson/d-i/images/; the images
there are untested, and I haven't yet cronned the build (I probably need
to get my Pegasos going again and move it there, rather than trying to
do it on my laptop), but I'll try to get that sorted out sometime this
week.

If you'd like me to take this job over permanently, I'm prepared to do
so.

Cheers,

-- 
Colin Watson   [EMAIL PROTECTED]


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

Bug#359333: Acknowledgement (discover1-udeb should not depend on non-udeb libdiscover1)

[Christian Perrier]

 Go ahead and upload it. I'll work on Debian packages again just in

Done. But it requires NEW processing because of the new udeb.




signature.asc
Description: Digital signature

Bug#355851: a blindunfriendly debian installer problem

[Samuel Thibault]

Dave Mielke, le Tue 28 Mar 2006 06:59:56 -0500, a écrit :
 [quoted lines by Samuel Thibault on 2006/03/28 at 11:41 +0200]
 
 However, although it works well when hotplugging the device after
 bootup, it does not when booting with the device already plugged,
 because USB seems to be discovered before vcsa nodes are available,
 hence brltty fails.
 
 brltty makes any vcsa devices which it needs but aren't there yet.

Yes I know, but for some reason it fails here... Maybe udev, while still
booting, prevents brltty from being able to create anything in /dev?

Regards,
Samuel

Re: Bug#359164: [powerpc64] d-i fails, base-installer/initramfs/no-generator

[Sven Luther]

On Tue, Mar 28, 2006 at 01:27:55PM +0200, Martin Michlmayr wrote:
 * Sven Luther [EMAIL PROTECTED] [2006-03-28 10:32]:
   Did you actually take *any look* at the failure at all?  If so, you'd
   know that you're blaming the wrong people...
  Actually, Frans is blaming me, so ...
 
 You mean for not taking a look at the build logs from time to time,
 and a new installing a package every few months?

For accusing me in two different emails that it is my fault the daily build is
broken, while he knows perfectly i am currently half a world away.

Furthermore, i have a script which daily scans the build-dep of the svn
checkout of the d-i tree, and installs the build-dependencies, so it should
not cause problems.

Also as said, it is a bit difficult to swallow that i am told debian is better
off without me, and then being held responsible for the d-i daily builds,
don't you think ? 

Really, i just wanted to be helpful to hsaymal, and orient him to the right
place, i may not have checked everything in detail, as i am not really in
conditions to do so, but that is no excuse for bashing me in 2 different
emails, and is furthermore a behavior very similar to the one i was almost
expulsed for, so two weights two measures ? 

Friendly,

Sven Luther


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

Bug#355851: a blindunfriendly debian installer problem

[Dave Mielke]

[quoted lines by Samuel Thibault on 2006/03/28 at 15:57 +0200]

Hi:

for some reason it fails here... Maybe udev, while still
booting, prevents brltty from being able to create anything in /dev?

In my opinion, it's more important to give the blind person his screen as
quickly as possible rather than to wait, which would still leave him wondering
what went wrong. A better solution, therefore, might be for brltty to make the
device file somewhere else, e.g. in /etc/brltty, if it can't create it in the
usual place. It could even remove the file immediately after opening it, in
this case, if we deem it important to not leave device files lying around in
strange places.

-- 
Dave Mielke   | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: [EMAIL PROTECTED] | Canada  K2A 1H7   | if you're concerned about Hell.
http://FamilyRadio.com/   | http://Mielke.cc/bible/


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

Fixed in NMU of apt-setup 1:0.8

[Colin Watson]

tag 348509 + fixed

quit

This message was generated automatically in response to a
non-maintainer upload.  The .changes file follows.

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 28 Mar 2006 17:14:50 +0100
Source: apt-setup
Binary: apt-mirror-setup apt-cdrom-setup apt-setup-udeb
Architecture: source all
Version: 1:0.8
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Colin Watson [EMAIL PROTECTED]
Description: 
 apt-cdrom-setup - set up a CD in sources.list (udeb)
 apt-mirror-setup - set up a mirror in sources.list (udeb)
 apt-setup-udeb - Configure apt (udeb)
Closes: 348509
Changes: 
 apt-setup (1:0.8) unstable; urgency=low
 .
   * Add support for preseeding local archives to be appended to
 sources.list, based on a patch by Timo Aaltonen (closes: #348509).
 .
   [ Updated translations ]
   * German (de.po) by Jens Seidel
   * Irish (ga.po) by Kevin Patrick Scannell
   * Khmer (km.po) by hok kakada
Files: 
 d71a9d5a241aa26cc5f8dc8542f009f0 617 debian-installer extra apt-setup_0.8.dsc
 eedfe58f7d172df818bfc4557dab3ca0 82028 debian-installer extra 
apt-setup_0.8.tar.gz
 6b3821059d69ebd8c7141c79a5318f80 13778 debian-installer standard 
apt-setup-udeb_0.8_all.udeb
 7e52bf5cf241da29d2a9d508ff016d31 25744 debian-installer extra 
apt-mirror-setup_0.8_all.udeb
 5ac12d7e63cc001e6d284a0e6870c9b4 5216 debian-installer extra 
apt-cdrom-setup_0.8_all.udeb
Package-Type: udeb

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

iD8DBQFEKWGH9t0zAhD6TNERAgGVAJ4/im9IroVeo5rshsu+TCOTSXgEjQCdEXvy
NzE2/Vy3LhVJIb78Hb6X9hc=
=Iw67
-END PGP SIGNATURE-


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

Processing of linux-kernel-di-powerpc-2.6_1.12_powerpc.changes

[Archive Administrator]

linux-kernel-di-powerpc-2.6_1.12_powerpc.changes uploaded successfully to 
localhost
along with the files:
  linux-kernel-di-powerpc-2.6_1.12.dsc
  linux-kernel-di-powerpc-2.6_1.12.tar.gz
  kernel-image-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  nic-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  nic-extra-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  nic-shared-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  serial-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  ppp-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  ide-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  cdrom-core-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  firewire-core-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  scsi-core-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  scsi-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  scsi-common-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  scsi-extra-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  floppy-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  loop-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  ipv6-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  ext2-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  ext3-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  jfs-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  reiserfs-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  xfs-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  fat-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  hfs-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  affs-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  ufs-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  md-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  usb-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  usb-storage-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  pcmcia-storage-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  input-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  mouse-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  irda-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  nic-pcmcia-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  pcmcia-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  sata-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  firmware-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  crypto-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  fs-common-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb
  kernel-image-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  nic-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  nic-extra-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  nic-shared-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  serial-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  ppp-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  ide-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  cdrom-core-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  firewire-core-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  scsi-core-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  scsi-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  scsi-common-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  scsi-extra-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  floppy-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  loop-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  ipv6-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  ext2-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  ext3-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  jfs-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  reiserfs-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  xfs-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  fat-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  hfs-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  affs-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  ufs-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  md-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  usb-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  usb-storage-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  pcmcia-storage-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  input-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  mouse-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  irda-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  nic-pcmcia-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  pcmcia-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  sata-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  firmware-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  crypto-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  fs-common-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  hypervisor-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb
  kernel-image-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb
  nic-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb
  nic-extra-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb
  nic-shared-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb
  serial-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb
  ppp-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb
  ide-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb
  

Re: using initrd preseed.cfg during netboot

[Steve Feehan]

On Mon, Mar 27, 2006 at 03:29:54PM -0500, Steve Feehan wrote:
 Forgot (at least) one critical bit of information: I'm working
 with the Sarge installer and the netboot image retrieved from:
 
   
 ftp://ftp.us.debian.org/debian/dists/sarge/main/installer-i386/current/images/netboot/
 
 Thanks!
 
 Steve
 
 On Mon, Mar 27, 2006 at 03:27:30PM -0500, Steve Feehan wrote:
  I have been working on preseeding during network booting. I got a
  network preseed file to work, but I'm having trouble putting the
  preseed.cfg file in the initrd.
  
  First, I know this is probably not the correct way to modify the initrd, 
  but here is what I did:
  
  Uncompress the initrd:
  
gunzip initrd.gz
  
  Mount on a loopback device:
  
mount -o loop=/dev/loop0 initrd /mnt
  
  Copy the preseed file into the initrd file system:
  
cp preseed.cfg /mnt/preseed.cfg
  
  Unmount:
  
umount /mnt
  
  Compress the initrd:
  
gzip initrd
  
  When I boot with this initrd I can drop to a shell and see that
  /preseed.cfg is there. But the installer won't use the values in
  the preseed file. I've tried with and without passing the kernel 
  parameter:
  
 preseed/file=/preseed.cfg
  
  But in either case, the preseed values are not used.
  
  Am I missing something obvious? Does the netboot initrd not support
  preseed files inside the initrd? Do I need to build my own customized
  netboot images? If there is documentation on this, please point me in
  the right direction. And if I didn't explain the problem clearly enough,
  please let me know and I'll try and clarify.
  
  Thanks for your time!
  
  -- 
  Steve Feehan
 
 -- 
 Steve Feehan

Yesterday afternoon I decided to proceed down the path of building
a custom debian installer netboot image with the file-preseed and/or
initrd-preseed udebs.

The first problem I encountered is that the initrd-preseed udeb seems
to not exist for the version of preseed used in stable. The other 
preseed udebs for stable are version 1.01 but initrd-preseed only 
exists as version 1.14.1.

So my questions...

  1. Am I proceeding in the right direction? Ie. is creating a custom
 debian-installer netboot image the correct solution to storing a
 preseed.cfg inside the initrd?

  2. Do I need to use/build the debian-installer version from sid since
 there does not appear to be an initrd-preseed for stable?

  3. Is it possible to use the sid installer to install a stable system?

Thanks.

-- 
Steve Feehan


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

linux-kernel-di-powerpc-2.6_1.12_powerpc.changes is NEW

[Debian Installer]

(new) affs-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb extra debian-installer
Amiga filesystem support
 This package contains the Amiga filesystem module for the Linux kernel.
(new) affs-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb extra 
debian-installer
Amiga filesystem support
 This package contains the Amiga filesystem module for the Linux kernel.
(new) affs-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb extra 
debian-installer
Amiga filesystem support
 This package contains the Amiga filesystem module for the Linux kernel.
(new) cdrom-core-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb standard 
debian-installer
CDROM support
 This package contains core CDROM support for the Linux kernel.
(new) cdrom-core-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb standard 
debian-installer
CDROM support
 This package contains core CDROM support for the Linux kernel.
(new) cdrom-core-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb standard 
debian-installer
CDROM support
 This package contains core CDROM support for the Linux kernel.
(new) crypto-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb extra 
debian-installer
crypto modules
 This package contains crypto modules.
(new) crypto-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb extra 
debian-installer
crypto modules
 This package contains crypto modules.
(new) crypto-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb extra 
debian-installer
crypto modules
 This package contains crypto modules.
(new) ext2-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb standard 
debian-installer
EXT2 filesystem support
 This package contains the EXT2 filesystem module for the Linux kernel.
(new) ext2-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb standard 
debian-installer
EXT2 filesystem support
 This package contains the EXT2 filesystem module for the Linux kernel.
(new) ext2-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb standard 
debian-installer
EXT2 filesystem support
 This package contains the EXT2 filesystem module for the Linux kernel.
(new) ext3-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb standard 
debian-installer
EXT3 filesystem support
 This package contains the EXT3 filesystem module for the Linux kernel.
(new) ext3-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb standard 
debian-installer
EXT3 filesystem support
 This package contains the EXT3 filesystem module for the Linux kernel.
(new) ext3-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb standard 
debian-installer
EXT3 filesystem support
 This package contains the EXT3 filesystem module for the Linux kernel.
(new) fat-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb extra debian-installer
FAT filesystem support
 This package contains the FAT and VFAT filesystem modules for the Linux kernel.
(new) fat-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb extra 
debian-installer
FAT filesystem support
 This package contains the FAT and VFAT filesystem modules for the Linux kernel.
(new) fat-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb extra debian-installer
FAT filesystem support
 This package contains the FAT and VFAT filesystem modules for the Linux kernel.
(new) firewire-core-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb standard 
debian-installer
Core FireWire drivers
 This package contains core FireWire drivers for the Linux kernel.
(new) firewire-core-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb 
standard debian-installer
Core FireWire drivers
 This package contains core FireWire drivers for the Linux kernel.
(new) firewire-core-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb standard 
debian-installer
Core FireWire drivers
 This package contains core FireWire drivers for the Linux kernel.
(new) firmware-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb standard 
debian-installer
Firmware request modules
 This package contains linux kernel modules that support requesting
 external firmware.
(new) firmware-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb standard 
debian-installer
Firmware request modules
 This package contains linux kernel modules that support requesting
 external firmware.
(new) firmware-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb standard 
debian-installer
Firmware request modules
 This package contains linux kernel modules that support requesting
 external firmware.
(new) floppy-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb standard 
debian-installer
Floppy driver
 This package contains the floppy driver for the Linux kernel.
(new) floppy-modules-2.6.16-1-powerpc-miboot-di_1.12_powerpc.udeb standard 
debian-installer
Floppy driver
 This package contains the floppy driver for the Linux kernel.
(new) floppy-modules-2.6.16-1-powerpc64-di_1.12_powerpc.udeb standard 
debian-installer
Floppy driver
 This package contains the floppy driver for the Linux kernel.
(new) fs-common-modules-2.6.16-1-powerpc-di_1.12_powerpc.udeb standard 
debian-installer
Common filesystem support
 This package contains drivers common to several filesystem modules.
(new) 

Bug#348509: marked as done (add support for local archives)

[Debian Bug Tracking System]

Your message dated Tue, 28 Mar 2006 17:41:51 +0100
with message-id [EMAIL PROTECTED]
and subject line [EMAIL PROTECTED]: Fixed in NMU of apt-setup 1:0.8]
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)

---BeginMessage---

Package: apt-setup
Version: 0.5

It would be nice to have support for local archives in apt-setup. Here's a 
simple patch for that. Currently it supports only one repository because 
it doesn't (well, I don't) know how to parse the string into multiple 
entries. Maybe something like a ';' could be the delimiter?


debian-installer/packages/apt-setup/generators/95local:
#!/bin/sh
set -e

. /usr/share/debconf/confmodule

file=$1

db_get apt-setup/local
local=$RET

echo  $file
if [ -n $local ]; then
cat  $file EOF
## The local repository
$local
EOF


--- debian/apt-mirror-setup.templates.orig  2006-01-17 
14:13:33.531371000 +0200
+++ debian/apt-mirror-setup.templates   2006-01-17 14:18:25.212208000 
+0200

@@ -35,3 +35,8 @@
  network, or with the mirror. You can choose to retry the download, 
select

  a different mirror, or ignore the problem and continue without all the
  packages from this mirror.
+
+Template: apt-setup/local
+Type: string
+_Description: Local archive(s) to be added in sources.list
+


---End Message---
---BeginMessage---
Not an NMU.

-- 
Colin Watson   [EMAIL PROTECTED]

- Forwarded message from Colin Watson [EMAIL PROTECTED] -

From: Colin Watson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Colin Watson [EMAIL PROTECTED],
Debian Install System Team debian-boot@lists.debian.org
X-Katie: $Revision: 1.65 $
Subject: Fixed in NMU of apt-setup 1:0.8
Date: Tue, 28 Mar 2006 08:32:07 -0800
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on 
riva.pelham.vpn.ucam.org
X-Spam-Status: No, score=-0.0 required=4.5 tests=AWL,BAYES_50 autolearn=no 
version=3.0.3

tag 348509 + fixed

quit

This message was generated automatically in response to a
non-maintainer upload.  The .changes file follows.

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.7
Date: Tue, 28 Mar 2006 17:14:50 +0100
Source: apt-setup
Binary: apt-mirror-setup apt-cdrom-setup apt-setup-udeb
Architecture: source all
Version: 1:0.8
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Colin Watson [EMAIL PROTECTED]
Description: 
 apt-cdrom-setup - set up a CD in sources.list (udeb)
 apt-mirror-setup - set up a mirror in sources.list (udeb)
 apt-setup-udeb - Configure apt (udeb)
Closes: 348509
Changes: 
 apt-setup (1:0.8) unstable; urgency=low
 .
   * Add support for preseeding local archives to be appended to
 sources.list, based on a patch by Timo Aaltonen (closes: #348509).
 .
   [ Updated translations ]
   * German (de.po) by Jens Seidel
   * Irish (ga.po) by Kevin Patrick Scannell
   * Khmer (km.po) by hok kakada
Files: 
 d71a9d5a241aa26cc5f8dc8542f009f0 617 debian-installer extra apt-setup_0.8.dsc
 eedfe58f7d172df818bfc4557dab3ca0 82028 debian-installer extra 
apt-setup_0.8.tar.gz
 6b3821059d69ebd8c7141c79a5318f80 13778 debian-installer standard 
apt-setup-udeb_0.8_all.udeb
 7e52bf5cf241da29d2a9d508ff016d31 25744 debian-installer extra 
apt-mirror-setup_0.8_all.udeb
 5ac12d7e63cc001e6d284a0e6870c9b4 5216 debian-installer extra 
apt-cdrom-setup_0.8_all.udeb
Package-Type: udeb

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

iD8DBQFEKWGH9t0zAhD6TNERAgGVAJ4/im9IroVeo5rshsu+TCOTSXgEjQCdEXvy
NzE2/Vy3LhVJIb78Hb6X9hc=
=Iw67
-END PGP SIGNATURE-



- End forwarded message -
---End Message---

Processed: Fixed in NMU of apt-setup 1:0.8

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 tag 348509 + fixed
Bug#348509: add support for local archives
Tags were: patch
Tags added: fixed

 quit
Stopping processing here.

Please contact me if you need assistance.

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


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

Re: using initrd preseed.cfg during netboot

[Steven Van Acker]

On Tue, Mar 28, 2006 at 09:47:00AM -0500, Steve Feehan wrote:
 Yesterday afternoon I decided to proceed down the path of building
 a custom debian installer netboot image with the file-preseed and/or
 initrd-preseed udebs.
 
 The first problem I encountered is that the initrd-preseed udeb seems
 to not exist for the version of preseed used in stable. The other 
 preseed udebs for stable are version 1.01 but initrd-preseed only 
 exists as version 1.14.1.
 
 So my questions...
 
   1. Am I proceeding in the right direction? Ie. is creating a custom
  debian-installer netboot image the correct solution to storing a
  preseed.cfg inside the initrd?
 
   2. Do I need to use/build the debian-installer version from sid since
  there does not appear to be an initrd-preseed for stable?
 
   3. Is it possible to use the sid installer to install a stable system?
 
 Thanks.

Hello,

I'm using the sarge netboot CD to build a custom install-CD aswell.
I applied a patch from http://www.hands.com/d-i/ in order to be able
to do preseeding. In my case, the file is stored in the initrd too.

greets,
-- Steven


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

Re: using initrd preseed.cfg during netboot

[Steve Feehan]

On Tue, Mar 28, 2006 at 09:47:00AM -0500, Steve Feehan wrote:

 Yesterday afternoon I decided to proceed down the path of building
 a custom debian installer netboot image with the file-preseed and/or
 initrd-preseed udebs.
 
 The first problem I encountered is that the initrd-preseed udeb seems
 to not exist for the version of preseed used in stable. The other 
 preseed udebs for stable are version 1.01 but initrd-preseed only 
 exists as version 1.14.1.
 
 So my questions...
 
   1. Am I proceeding in the right direction? Ie. is creating a custom
  debian-installer netboot image the correct solution to storing a
  preseed.cfg inside the initrd?
 
   2. Do I need to use/build the debian-installer version from sid since
  there does not appear to be an initrd-preseed for stable?
 
   3. Is it possible to use the sid installer to install a stable system?
 
 Thanks.
 
 -- 
 Steve Feehan

OK, here is my temporary work around (I'm still open to guidance
on the correct way to handle this).

  1. checkout debian-installer from svn.
  2. mount the initrd on a loopback device.
  3. copy packages/preseed/debian-installer-startup.d/S35initrd-preseed
 to /mnt/lib/debian-installer-startup.d/S35initrd-preseed
  4. Unmount and compress initrd image.

And now my final (hopefully minor) problem: a couple of the preseed
lines don't seem to be used. For instance, I don't want sshd to start so
I add:

  ssh ssh/run_sshd  string  false

at the end of /preseed.cfg, but it doesn't seem to be honored. Are
preseeds that are not strictly part of the installer not used?

And there are two prompts I can't seem to get rid of, I think the 
debconf keys for one is keymap/policy. The other is just a note 
before the keymap/policy question.

Thanks.

-- 
Steve Feehan


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

Bug#359750: tasksel: [INTL:pl] updated Polish translation

[Bartosz Fenski aka fEnIo]

Package: tasksel
Version: 2.41
Severity: wishlist
Tags: patch l10n

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello.

Please include updated tasks translation.

regards
fEnIo

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

iD8DBQFEKXCKhQui3hP+/EARAskfAJ42ii6NIezz6OCqE6BjaaMmaLfLgQCdH//Y
0b3pAAWKcfbTEtKIIVncfE4=
=SHSF
-END PGP SIGNATURE-
# Polish translation of tasksel tasks.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# Bartosz Fenski aka fEnIo [EMAIL PROTECTED], 2004, 2005.
#
msgid 
msgstr 
Project-Id-Version: tasksel/tasks\n
Report-Msgid-Bugs-To: \n
POT-Creation-Date: 2006-02-23 15:01-0500\n
PO-Revision-Date: 2006-03-28 19:18+0200\n
Last-Translator: Bartosz Fenski [EMAIL PROTECTED]\n
Language-Team: Polish [EMAIL PROTECTED]\n
MIME-Version: 1.0\n
Content-Type: text/plain; charset=ISO-8859-2\n
Content-Transfer-Encoding: 8bit\n

#. Description
#: ../po/debian-tasks.desc:3
msgid 
This task installs programs, data files, fonts, and documentation that makes 
it easier for Arabic speakers to use Debian.
msgstr 
To zadanie instaluje programy, dane, czcionki i dokumentacjê, by u³atwiæ 
korzystanie z Debiana osobom pos³uguj±cym siê jêzykiem arabskim.

#. Description
#: ../po/debian-tasks.desc:14
msgid Arabic environment
msgstr ¦rodowisko arabskie

#. Description
#: ../po/debian-tasks.desc:14
msgid This task localises the desktop in Arabic.
msgstr 
To zadanie spowoduje, ¿e ¶rodowisko graficzne bêdzie siê komunikowaæ po 
arabsku.

#. Description
#: ../po/debian-tasks.desc:21
msgid 
This task installs programs, data files, fonts, and documentation that makes 
it easier for Bengali speakers to use Debian.
msgstr 
To zadanie instaluje programy, dane, czcionki i dokumentacjê, by u³atwiæ 
korzystanie z Debiana osobom pos³uguj±cym siê jêzykiem bengalskim.

#. Description
#: ../po/debian-tasks.desc:32
msgid Bengali environment
msgstr ¦rodowisko bengalskie

#. Description
#: ../po/debian-tasks.desc:32
msgid This task localises the desktop in Bengali.
msgstr 
To zadanie spowoduje, ¿e ¶rodowisko graficzne bêdzie siê komunikowaæ po 
bengalsku.

#. Description
#: ../po/debian-tasks.desc:39
msgid Brazilian Portuguese environment
msgstr ¦rodowisko portugalskie (brazylijskie)

#. Description
#: ../po/debian-tasks.desc:39
msgid 
This task installs programs, data files, and documentation that make it 
easier for Brazilian Portuguese speakers to use Debian.
msgstr 
To zadanie instaluje pakiety i dokumentacjê w jêzyku portugalskim 
(brazylijskim), by pomóc osobom pos³uguj±cym siê tym jêzykiem w u¿ywaniu 
Debiana.

#. Description
#: ../po/debian-tasks.desc:50
msgid Brazilian Portuguese desktop
msgstr Graficzne ¶rodowisko portugalskie (brazylijskie)

#. Description
#: ../po/debian-tasks.desc:50
msgid This task localises the desktop in Brasilian Portuguese.
msgstr 
To zadanie spowoduje, ¿e ¶rodowisko graficzne bêdzie siê komunikowaæ po 
portugalsku (brazylijski).

#. Description
#: ../po/debian-tasks.desc:57
msgid Bulgarian environment
msgstr ¦rodowisko bu³garskie

#. Description
#: ../po/debian-tasks.desc:57
msgid 
This task installs programs and data files that make it easier for Bulgarian 
speakers to use Debian.
msgstr 
To zadanie instaluje pakiety u³atwiaj±ce korzystanie Debiana ludziom 
pos³uguj±cym siê jêzykiem bu³garskim.

#. Description
#: ../po/debian-tasks.desc:66
msgid Bulgarian desktop
msgstr Graficzne ¶rodowisko bu³garskie

#. Description
#: ../po/debian-tasks.desc:66
msgid This task localises the desktop in Bulgarian.
msgstr 
To zadanie spowoduje, ¿e ¶rodowisko graficzne bêdzie siê komunikowaæ po 
bu³garsku.

#. Description
#: ../po/debian-tasks.desc:73
msgid Catalan environment
msgstr ¦rodowisko kataloñskie

#. Description
#: ../po/debian-tasks.desc:73
msgid 
This task installs packages and documentation in Catalan to help Catalan 
speaking people use Debian.
msgstr 
To zadanie instaluje pakiety i dokumentacjê w jêzyku kataloñskim, by pomóc 
osobom pos³uguj±cym siê tym jêzykiem w u¿ywaniu Debiana.

#. Description
#: ../po/debian-tasks.desc:83
msgid Catalan desktop
msgstr Graficzne ¶rodowisko kataloñskie

#. Description
#: ../po/debian-tasks.desc:83
msgid This task localises the desktop in Catalan.
msgstr 
To zadanie spowoduje, ¿e ¶rodowisko graficzne bêdzie siê komunikowaæ po 
kataloñsku.

#. Description
#: ../po/debian-tasks.desc:90
msgid Simplified Chinese environment
msgstr ¦rodowisko chiñskie (uproszczone)

#. Description
#: ../po/debian-tasks.desc:90
msgid 
This task installs programs, data files, fonts, and documentation that make 
it easier for Chinese speakers to use Debian, using the simplified Chinese 
encoding.
msgstr 
To zadanie instaluje programy, dane, czcionki i dokumentacjê, by u³atwiæ 
korzystanie z Debiana osobom pos³uguj±cym siê jêzykiem chiñskim z 
wykorzystaniem uproszczonego kodowania.

#. Description
#: ../po/debian-tasks.desc:102
msgid Simplified Chinese desktop
msgstr Graficzne 

Processing of apt-setup_0.8_powerpc.changes

[Archive Administrator]

apt-setup_0.8_powerpc.changes uploaded successfully to localhost
along with the files:
  apt-setup_0.8.dsc
  apt-setup_0.8.tar.gz
  apt-setup-udeb_0.8_all.udeb
  apt-mirror-setup_0.8_all.udeb
  apt-cdrom-setup_0.8_all.udeb

Greetings,

Your Debian queue daemon


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

Re: d-i on serial console with name != ttyS/tts

[Rob Landley]

On Sunday 26 March 2006 8:30 pm, Martin Michlmayr wrote:
 * Rob Landley [EMAIL PROTECTED] [2006-03-26 17:40]:
   I saw the following problem today: I started debian-installer on a
   machine with serial console, the device node /dev/tts/0 got
   created
 
  Still using devfs names, I see.

 Yes, and that won't change soon.  We're using udev on 2.6 though and
 have a devfs compatability schema.  The problem I saw was on 2.6.

There's a use devfs names option somewhere.  (Support for devfs in the 
first menu turns on CONFIG_FEATURE_DEVFS, that's probably it.)

Among other things, that makes init look for devfs names for console and such 
by default.  (That's a legacy support feature that will eventually go away, 
probably in 1.2.0, but you've got at least a year, maybe as much as three.  
We'll move it to a deprecated menu for a release before actually removing 
it...)

  I'm confused: what exactly are you trying to do?  (You're using init
  without an inittab, or...?)

 inittab contains:
 ::sysinit:/sbin/debian-installer-startup
 ::respawn:/sbin/debian-installer

 vc/2::askfirst:/bin/sh
 vc/3::respawn:/usr/bin/tail -f /var/log/messages
 vc/4::respawn:/usr/bin/tail -f /var/log/syslog

 ::ctrlaltdel:/sbin/shutdown  /dev/null 21
 ::restart:/sbin/init

Ok.

 
  The general debain installer people might like svn 14606, which
  makes it so busybox 1.1.1 doesn't need to have the tty nodes created
  at the time the inittab is read, but instead checks when it tries to
  spawn the process on that tty...
  http://busybox.net/downloads/patches/svn-14606.patch

 Oh, great.  I'll give that a try.  This might solve the original
 problem I reported a few weeks ago.

In theory it's in 1.1.1.

 I'll get back to you but it will 
 take a while - I'm leaving for holidays soon (actually,should go to
 bed since I've to get up in 2.5 hours again) and then moving to
 another country...

Have fun,

 Thanks for your response!

Rob
-- 
Never bet against the cheap plastic solution.


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

apt-setup_0.8_powerpc.changes ACCEPTED

[Debian Installer]

Accepted:
apt-cdrom-setup_0.8_all.udeb
  to pool/main/a/apt-setup/apt-cdrom-setup_0.8_all.udeb
apt-mirror-setup_0.8_all.udeb
  to pool/main/a/apt-setup/apt-mirror-setup_0.8_all.udeb
apt-setup-udeb_0.8_all.udeb
  to pool/main/a/apt-setup/apt-setup-udeb_0.8_all.udeb
apt-setup_0.8.dsc
  to pool/main/a/apt-setup/apt-setup_0.8.dsc
apt-setup_0.8.tar.gz
  to pool/main/a/apt-setup/apt-setup_0.8.tar.gz
Announcing to debian-devel-changes@lists.debian.org
Setting bugs to severity fixed: 348509 


Thank you for your contribution to Debian.


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

Processing of kbd-chooser_1.25_i386.changes

[Archive Administrator]

kbd-chooser_1.25_i386.changes uploaded successfully to localhost
along with the files:
  kbd-chooser_1.25.dsc
  kbd-chooser_1.25.tar.gz
  kbd-chooser_1.25_i386.udeb

Greetings,

Your Debian queue daemon


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

kbd-chooser_1.25_i386.changes ACCEPTED

[Debian Installer]

Accepted:
kbd-chooser_1.25.dsc
  to pool/main/k/kbd-chooser/kbd-chooser_1.25.dsc
kbd-chooser_1.25.tar.gz
  to pool/main/k/kbd-chooser/kbd-chooser_1.25.tar.gz
kbd-chooser_1.25_i386.udeb
  to pool/main/k/kbd-chooser/kbd-chooser_1.25_i386.udeb
Announcing to debian-devel-changes@lists.debian.org


Thank you for your contribution to Debian.


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

Re: [Debian-in-workers] Country names for Bengali

[Denis Barbier]

On Thu, Mar 09, 2006 at 10:10:50PM +0100, Denis Barbier wrote:
 On Sun, Feb 26, 2006 at 08:49:22AM +0100, Christian Perrier wrote:
   Christian already informed that the bn_BD locale has an issue, I will 
   try to dig out.
  
  You can ask for help on debian-i18n, at least to be pointed at correct
  documentation about collation rules writing.
  
  Denis barbier gave a very interesting talk at last Debconf about this
  (which talk, dammit, I couldn't attend because I had a D-I talk
  immediately after it).
 
 Slides are available at
http://people.debian.org/~barbier/talks/debconf5/glibc-locale.pdf
 
 I wrote a first draft of collation rules, based on informations found in
http://tdil.mit.gov.in/bangla.pdf
http://www.unicode.org/cldr/data/common/collation/bn.xml
http://developer.mimer.com/collations/charts/bengali.htm
 Could a native speaker please send a sorted list of words, say around 50,
 one word per line?  I can then check that the file is not modified when
 passed to the sort command.

Can a native Bengali speaker please provide this file, so that I can
test collation rules?
Thanks.

Denis


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

Re: Bug#359062: debian-installer: bterm is not (yet) accessible for brltty

[Joey Hess]

Samuel Thibault wrote:
 I'm not saying that. I'm seeing that debian-installer uses bterm by
 default now.

d-i uses bterm, or writes raw data to a serial port, or to the console,
or it uses GTK. d-i is frontend independant and it would be trivial to
make it dump well-formatted text to bterm, which is what I've been
trying to say.

-- 
see shy jo


signature.asc
Description: Digital signature

Re: using initrd preseed.cfg during netboot

[Joey Hess]

sarge does not support initrd preseeding, this feature was added after
its release.

Steve Feehan wrote:
 And now my final (hopefully minor) problem: a couple of the preseed
 lines don't seem to be used. For instance, I don't want sshd to start so
 I add:
 
   ssh ssh/run_sshdstring  false
 
 at the end of /preseed.cfg, but it doesn't seem to be honored. Are
 preseeds that are not strictly part of the installer not used?

Whitespace is significant in preseed files, in particular you've just
set the value of a boolean to   false here, which has fairly undefined
behavior.

ssh ssh/run_sshd string false

-- 
see shy jo


signature.asc
Description: Digital signature

Re: Bug#359062: debian-installer: bterm is not (yet) accessible for brltty

[Joey Hess]

Joey Hess wrote:
 Samuel Thibault wrote:
  I'm not saying that. I'm seeing that debian-installer uses bterm by
  default now.
 
 d-i uses bterm, or writes raw data to a serial port, or to the console,
 or it uses GTK. d-i is frontend independant and it would be trivial to
 make it dump well-formatted text to bterm, which is what I've been
   ^
   er, to brltty

-- 
see shy jo


signature.asc
Description: Digital signature

Re: using initrd preseed.cfg during netboot

[Frans Pop]

On Tuesday 28 March 2006 16:47, Steve Feehan wrote:
   2. Do I need to use/build the debian-installer version from sid since
      there does not appear to be an initrd-preseed for stable?

There are several options. You could also backport the changes in the 
preseed udeb needed for initrd-preseeding to the Sarge version of that 
package.

   3. Is it possible to use the sid installer to install a stable
  system?

Yes, that has been made possible again _after_ the Beta2 release, so you'd 
need the daily images. It's only been tested for an i386 install. Also, 
the installation will not be 100% identical to an install using the Sarge 
installer.

Note also that it is not fully supported and you may run into problems, 
especially on the reboot. Reason for this is that the installer will run 
with a newer kernel (2.6.16) than is installed on the target system 
(2.6.8).

See also the README in the d-i SVN repository for package sarge-support.

Cheers,
FJP


pgpYrkk9Ijlx8.pgp
Description: PGP signature

Bug#359774: installation-reports

[Christer Sjöholm]

Package: installation-reports

Boot method: CD
Image version: build 20060327
Date: 20060328

Machine: Dell Latitude D600
Processor: Intel Pentium M Processor - 1.70GHz
Memory: 1GB
Partitions:

Output of lspci and lspci -n:

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

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]
Creating user:  [E]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]

Comments/Problems:
If i try to enter a swedish character when entering a users full name
it displays E4 E5 or F6 instead and no further editing in the
field is possible.
Backing to previus screen do work and i can try again.
I'm usin the swedish installation and keyboard layout.

Bug#355851: a blindunfriendly debian installer problem

[Samuel Thibault]

Here is answer from Dave:

Frans Pop, le Mon 27 Mar 2006 23:52:49 +0200, a écrit :
 On Tuesday 21 March 2006 03:03, Frans Pop wrote:
  On Tuesday 21 March 2006 02:12, Samuel Thibault wrote:
BTW, is /etc/brltty/usbfs really a good location for that?
  
   Yes, because the brltty-udeb package contains that directory, so we
   are sure that it will exist.
 
  Note that kbd-chooser also uses usbfs and contains this code (slightly
  rewritten for demonstration) in kbd-chooser/usb-kbd.c:
 
  fp = fopen (/proc/bus/usb/devices, r);
  if (fp == NULL) {   // try harder.
  [...]
  if system (mount -t  usbfs usbfs /proc/bus/usb) = 0) {
  mounted_fs=1;
  [...]
  }
  [...]
  }
  if (mounted_fs)
  system (umount /proc/bus/usb);
 
  Which means that it looks if /proc/bus/usb/devices is already mounted
  and, if not, mounts it. It's only unmounted afterwards if it was
  mounted by this program.
 
  IMO it would be better to standardize on this location.

« I don't think that's a good idea. It requires that /proc be already
mounted. If we don't also mount /proc then we can't mount usbfs in the
standard palce, and, as a result, brltty still can't see USB devices. If
we do mount /proc then system boot scripts are subsequently at risk of
failing. »

Note: brltty needs to be started as soon as possible.

Regards,
Samuel


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

Processed: Re: Bug#359774: installation-reports

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 reassign 359774 user-setup
Bug#359774: installation-reports
Bug reassigned from package `installation-reports' to `user-setup'.

 severity 359774 minor
Bug#359774: installation-reports
Severity set to `minor'.


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]

Bug#355851: a blindunfriendly debian installer problem

[Samuel Thibault]

Frans Pop, le Tue 28 Mar 2006 23:20:49 +0200, a écrit :
 On Tuesday 28 March 2006 22:08, Samuel Thibault wrote:
  « I don't think that's a good idea. It requires that /proc be already
  mounted. If we don't also mount /proc then we can't mount usbfs in the
  standard palce, and, as a result, brltty still can't see USB devices.
  If we do mount /proc then system boot scripts are subsequently at risk
  of failing. »
 
  Note: brltty needs to be started as soon as possible.
 
 Before init is run?

Mmm, not that early here (but in other cases this is done).

 That is where proc is mounted by d-i, right at the very beginning of
 the boot sequence.

In debian installer, yes, but the brltty should be the same when booting
the real distribution, in which case which we would like to have brltty
started possibly before even the root partition fsck, hence before /proc
is mounted.

Regards,
Samuel


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

Bug#355851: a blindunfriendly debian installer problem

[Frans Pop]

On Tuesday 28 March 2006 23:25, Samuel Thibault wrote:
 In debian installer, yes, but the brltty should be the same when
 booting the real distribution, in which case which we would like to
 have brltty started possibly before even the root partition fsck, hence
 before /proc is mounted.

Hmm. In the real distribution this even sounds like a bigger problem to 
me. Isn't mounting something that belongs in /proc on a fairly random dir 
under /etc an FHS violation?


pgpyutqUI9R6M.pgp
Description: PGP signature

Bug#359750: tasksel: [INTL:pl] updated Polish translation

[Christian Perrier]

tags 359750 pending
thanks

Quoting Bartosz Fenski aka fEnIo ([EMAIL PROTECTED]):
 Package: tasksel
 Version: 2.41
 Severity: wishlist
 Tags: patch l10n

Commited.



signature.asc
Description: Digital signature

Processed: Re: Bug#359750: tasksel: [INTL:pl] updated Polish translation

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

 tags 359750 pending
Bug#359750: tasksel: [INTL:pl] updated Polish translation
Tags were: l10n patch
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#359774: marked as done (installation-reports)

[Debian Bug Tracking System]

Your message dated Tue, 28 Mar 2006 23:22:30 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#359774: installation-reports
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)

---BeginMessage---
Package: installation-reports

Boot method: CD
Image version: build 20060327
Date: 20060328

Machine: Dell Latitude D600
Processor: Intel Pentium M Processor - 1.70GHz
Memory: 1GB
Partitions:

Output of lspci and lspci -n:

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

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]
Creating user:  [E]
Install base system:[O]
Install boot loader:[O]
Reboot: [O]

Comments/Problems:
If i try to enter a swedish character when entering a users full name
it displays E4 E5 or F6 instead and no further editing in the
field is possible.
Backing to previus screen do work and i can try again.
I'm usin the swedish installation and keyboard layout.

---End Message---
---BeginMessage---

 If i try to enter a swedish character when entering a users full name
 it displays E4 E5 or F6 instead and no further editing in the
 field is possible.
 Backing to previus screen do work and i can try again.
 I'm usin the swedish installation and keyboard layout.

Yes, this is a known bug which noone worked on yet, unfortunately..:-|

Given that, part from that glitch, your installation was a complete
success, I do as usual with reports for successful installations: I
close the bug..:-)

This does not of course mean you weren't right to report. Knowing the
installations are correct is important for the d-i team.

Many thanks for your time testing the Debian Installer and reporting
your results. Have fun with your new Debian system!



-- 




signature.asc
Description: Digital signature
---End Message---

Bug#355851: a blindunfriendly debian installer problem

[Frans Pop]

On Tuesday 28 March 2006 22:08, Samuel Thibault wrote:
 « I don't think that's a good idea. It requires that /proc be already
 mounted. If we don't also mount /proc then we can't mount usbfs in the
 standard palce, and, as a result, brltty still can't see USB devices.
 If we do mount /proc then system boot scripts are subsequently at risk
 of failing. »

 Note: brltty needs to be started as soon as possible.

Before init is run? That is where proc is mounted by d-i, right at the 
very beginning of the boot sequence.

See src/sbin/init in rootskel udeb.


pgpmCtC201tuV.pgp
Description: PGP signature

Re: Bug#359062: debian-installer: bterm is not (yet) accessible for brltty

[Samuel Thibault]

Joey Hess, le Tue 28 Mar 2006 14:49:00 -0500, a écrit :
 Samuel Thibault wrote:
  I'm not saying that. I'm seeing that debian-installer uses bterm by
  default now.
 
 d-i uses bterm, or writes raw data to a serial port, or to the console,
 or it uses GTK. d-i is frontend independant and it would be trivial to
 make it dump well-formatted text to bterm, which is what I've been
 trying to say.

Well, I'm afraid we won't manage to understand ourselves :)

I know that d-i is flexible, etc. But dumb-Joe user just wants to boot
the cd he grabbed from debian.org and get it working without having to
care about preseeding for choosing the frontend etc.

And it happens that for now, the default frontend is the newt frontend
(which is fine) in bterm (which is not yet accessible to blind
users). So a bterm-accessibility solution needs to be found, so that
dumb-Bob _blind_ user won't either have to tinker anything and yet be
able to install debian by himself.

Regards,
Samuel


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

Bug#355851: a blindunfriendly debian installer problem

[Samuel Thibault]

Dave Mielke, le Tue 28 Mar 2006 16:52:17 -0500, a écrit :
 [quoted lines by Frans Pop on 2006/03/28 at 23:20 +0200]
 
 Before init is run? That is where proc is mounted by d-i, right at the 
 very beginning of the boot sequence.
 
 That's not generally true of all systems. What is true, however, is that 
 brltty
 happily uses /proc/bus/usb if usbfs is already mounted there. My sugestion,
 therefore, is that the Debian installer mount /proc/bus/usb right after it
 mounts /proc so that it's ready for brltty to use.

Well, actually, this is already done... The discussion went because at
some point I thought it wasn't done, because qemu doesn't have usb by
default, hence /proc/bus/usb wasn't mounted.

Regards,
Samuel


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

Bug#355851: a blindunfriendly debian installer problem

[Dave Mielke]

[quoted lines by Frans Pop on 2006/03/28 at 23:20 +0200]

Before init is run? That is where proc is mounted by d-i, right at the 
very beginning of the boot sequence.

That's not generally true of all systems. What is true, however, is that brltty
happily uses /proc/bus/usb if usbfs is already mounted there. My sugestion,
therefore, is that the Debian installer mount /proc/bus/usb right after it
mounts /proc so that it's ready for brltty to use.

-- 
Dave Mielke   | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: [EMAIL PROTECTED] | Canada  K2A 1H7   | if you're concerned about Hell.
http://FamilyRadio.com/   | http://Mielke.cc/bible/


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

Bug#355851: a blindunfriendly debian installer problem

[Samuel Thibault]

Frans Pop, le Tue 28 Mar 2006 23:45:15 +0200, a écrit :
 On Tuesday 28 March 2006 23:25, Samuel Thibault wrote:
  In debian installer, yes, but the brltty should be the same when
  booting the real distribution, in which case which we would like to
  have brltty started possibly before even the root partition fsck, hence
  before /proc is mounted.
 
 Hmm. In the real distribution this even sounds like a bigger problem to 
 me. Isn't mounting something that belongs in /proc on a fairly random dir 
 under /etc an FHS violation?

If you think about another place, well, we'd probably say fine, let's
move. But it really needs to be a private place, not /proc.

Regards,
Samuel


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

Re: Bug#359062: debian-installer: bterm is not (yet) accessible for brltty

[Samuel Thibault]

Joey Hess, le Tue 28 Mar 2006 15:11:26 -0500, a écrit :
 Joey Hess wrote:
  Samuel Thibault wrote:
   I'm not saying that. I'm seeing that debian-installer uses bterm by
   default now.
  
  d-i uses bterm, or writes raw data to a serial port, or to the console,
  or it uses GTK. d-i is frontend independant and it would be trivial to
  make it dump well-formatted text to bterm, which is what I've been
^
  er, to brltty

Without any user intervention other that having plugged his braille
device? (or put some parameters on the kernel command line, for serial
devices). _That's_ the point.

And remember that the blind person is not alone in front of the machine,
so that you need to have some synchronization between what is displayed
on the screen and on the braille device. Is it possible to run several
synchronized front-ends? Having brltty just read what bterm displays is
really a fine solution for this.

(Yes, I considered writing a brltty-oriented front-end for d-i, but the
above point takes precedence)

Regards,
Samuel


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

Re: Bug#359062: debian-installer: bterm is not (yet) accessible for brltty

[Dave Mielke]

Hi:

I, personally, don't want to see any solution which is Debian-specific, or any
other distribution-specific either. The Debian installer uses betrm. So does
RedHat when Asian characters are used. So/ probably/ do other distributions. 
Regardless of what any individual installer does, bterm can also be used at any
other time. Any solution which solves the problem for only one particular
instance of a general case is, in my opinion, an extremely poor alternative for
solving the problem as a whole in one place for all cases. This can easily be
done by changing bterm to passively export its view of the screen in a
software-readable way.

-- 
Dave Mielke   | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: [EMAIL PROTECTED] | Canada  K2A 1H7   | if you're concerned about Hell.
http://FamilyRadio.com/   | http://Mielke.cc/bible/


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

Re: Bug#359062: debian-installer: bterm is not (yet) accessible for brltty

[Samuel Thibault]

Hi,

Dave Mielke, le Tue 28 Mar 2006 15:40:43 -0500, a écrit :
 solving the problem as a whole in one place for all cases. This can easily be
 done by changing bterm to passively export its view of the screen in a
 software-readable way.

For which I already proposed a working implementation.

Regards,
Samuel


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

Re: Bug#359164: [powerpc64] d-i fails, base-installer/initramfs/no-generator

[Sven Luther]

On Tue, Mar 28, 2006 at 08:36:44AM +0200, Martin Michlmayr wrote:
 * Sven Luther [EMAIL PROTECTED] [2006-03-27 16:43]:
  I didn't touch the buildd since more than a week, so it is clear
  that (again) the d-i team broke the daily builds and don't take the
  responsability to fix them.
 
 Did you actually take *any look* at the failure at all?  If so, you'd
 know that you're blaming the wrong people...

I did now have a look at the build failure, and i get :

  The following packages have unmet dependencies:
cdebconf-newt-udeb: Depends: libnewt0.52 but it is not installable
  E: Broken packages

I don't know who is to blame for this, probably the powerpc buildd or
something, but this is clearly something of which i am not responsible, since
the d-i build-depends are clearly satisfied on my machine, as i run
dpkg-checkbuilddeps on the svn checkout, and then apt-get install all missing
packages.

If there is something on my part to do there, i will willingly do so, but i
don't really see how my responsabibility could be engaged in this failure, as
the new daily build script don't send me the log mails anymore, and joeyh
collects those for monitoring, so anyone could have a look and fix the issues.

Friendly,

Sven Luther


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

Wanted: Debian Installer PowerPC porter(s)

[Frans Pop]

Hi all,

Sven Luther has recently announced [1] that he will no longer work on 
PowerPC support in Debian Installer.

Colin Watson has already taken over the daily building of d-i images for 
PowerPC, so working daily builds are available again. Colin is willing to 
do that long term, but if a new porter should like to take care of that, 
I'm sure this can be discussed.


So what does being a d-i porter involve?
Mainly it means taking responsibility for architecture specific issues. 
Ideally this means:
- regular testing of the installer, preferably on different subarches
- keeping an eye out for installation reports for powerpc and following up
  on them (especially if architecture specific issues are reported)
- taking care of architecture specific components of the installer, such
  as kernel udebs, bootloader installers, some partman components
- reproducing, tracing and (hopefully) resolving bugs
- taking care of daily builds of d-i images

Familiarity with used filesystems and booting systems is a definite 
advantage, but in general work on the installer itself is fairly easy as 
most of it is scripted, with only some parts written in C.

Involvement on any level is welcome. Also, as PowerPC has several fairly 
distinct subarchitectures, getting involved for a specific subarch is an 
option.

The Debian Installer team is generally seen as open, friendly and helpful. 
And it has to be as the core team is fairly small but depends on a lot 
of effort from other developers, porters and translators to keep the 
installer in working order for all the (sub)architectures it supports.
General help on the structure and inner workings of the installer and its 
components is always available.

The last release of the installer (Etch Beta 2) had several PowerPC 
specific issues [2]. We'd very much like to see these resolved. There are 
also some open issues for the new graphical version of the installer.

If you are interested, please contact us on the debian-boot list.

Cheers,
Frans Pop

[1] http://lists.debian.org/debian-boot/2006/03/msg01075.html
[2] http://www.debian.org/devel/debian-installer/errata


pgp1fW3IBLt6T.pgp
Description: PGP signature

Bug#355851: a blindunfriendly debian installer problem

[Samuel Thibault]

Hi,

Ok, now that this whole discussion took place, here is something that
(almost) works:

http://brl.thefreecat.org/mini.iso (9ed7c3a112a6d72834f6ffeef19d615a)

I attached the patch that I applied to brltty and bogl for getting that
result (they shouldn't be considered as final of course).

You can test:

qemu -cdrom mini.iso
= no brltty at all

qemu -cdrom mini.iso -serial stdio
and type install brltty=tt,ttyS0  at the kernel command line.
= brltty is started from /etc/rcS.d with the given parameter: using a
TTY driver on the serial port, hence qemu's stdin/out.

qemu -cdrom mini.iso -serial stdio -usb -usbdevice mouse
= brltty is automatically started by udev thanks to the dumb last rule
of brltty.rules (just for testing).

qemu -cdrom mini.iso -serial stdio -usb
= no brltty, but when typing usb_add mouse in the qemu console (hence
simulating a braille device hot plug-in), brltty gets started.

Note for non- brltty-used people: press arrows (for instance)
for getting rid of the BRLTTY 3.7.2 and x startup problem(s)
messages. Then you'll see brltty's reading in action! :)

I said almost works because it seems like udevd calls the add hook
for the same USB device several times more during the installation (when
probing devices), hence starting brltty a few additional times... I
don't know udev stuff enough for fixing it the proper way.

(Note that running several instances of brltty for different braille
devices is fine: each of them drives one device ; but two brlttys for
the same braille device may lead to garbage).

Regards,
Samuel
diff -urN brltty-3.7.2/configure brltty-3.7.2-mine/configure
--- brltty-3.7.2/configure  2005-12-26 15:52:02.0 +0100
+++ brltty-3.7.2-mine/configure 2006-03-29 00:57:48.0 +0200
@@ -9400,227 +9400,6 @@
 
 
 
-for ac_header in iconv.h
-do
-as_ac_Header=`echo ac_cv_header_$ac_header | $as_tr_sh`
-if eval test \\${$as_ac_Header+set}\ = set; then
-  echo $as_me:$LINENO: checking for $ac_header 5
-echo $ECHO_N checking for $ac_header... $ECHO_C 6
-if eval test \\${$as_ac_Header+set}\ = set; then
-  echo $ECHO_N (cached) $ECHO_C 6
-fi
-echo $as_me:$LINENO: result: `eval echo '${'$as_ac_Header'}'` 5
-echo ${ECHO_T}`eval echo '${'$as_ac_Header'}'` 6
-else
-  # Is the header compilable?
-echo $as_me:$LINENO: checking $ac_header usability 5
-echo $ECHO_N checking $ac_header usability... $ECHO_C 6
-cat conftest.$ac_ext _ACEOF
-/* confdefs.h.  */
-_ACEOF
-cat confdefs.h conftest.$ac_ext
-cat conftest.$ac_ext _ACEOF
-/* end confdefs.h.  */
-$ac_includes_default
-#include $ac_header
-_ACEOF
-rm -f conftest.$ac_objext
-if { (eval echo $as_me:$LINENO: \$ac_compile\) 5
-  (eval $ac_compile) 2conftest.er1
-  ac_status=$?
-  grep -v '^ *+' conftest.er1 conftest.err
-  rm -f conftest.er1
-  cat conftest.err 5
-  echo $as_me:$LINENO: \$? = $ac_status 5
-  (exit $ac_status); } 
-{ ac_try='test -z $ac_c_werror_flag
-|| test ! -s conftest.err'
-  { (eval echo $as_me:$LINENO: \$ac_try\) 5
-  (eval $ac_try) 25
-  ac_status=$?
-  echo $as_me:$LINENO: \$? = $ac_status 5
-  (exit $ac_status); }; } 
-{ ac_try='test -s conftest.$ac_objext'
-  { (eval echo $as_me:$LINENO: \$ac_try\) 5
-  (eval $ac_try) 25
-  ac_status=$?
-  echo $as_me:$LINENO: \$? = $ac_status 5
-  (exit $ac_status); }; }; then
-  ac_header_compiler=yes
-else
-  echo $as_me: failed program was: 5
-sed 's/^/| /' conftest.$ac_ext 5
-
-ac_header_compiler=no
-fi
-rm -f conftest.err conftest.$ac_objext conftest.$ac_ext
-echo $as_me:$LINENO: result: $ac_header_compiler 5
-echo ${ECHO_T}$ac_header_compiler 6
-
-# Is the header present?
-echo $as_me:$LINENO: checking $ac_header presence 5
-echo $ECHO_N checking $ac_header presence... $ECHO_C 6
-cat conftest.$ac_ext _ACEOF
-/* confdefs.h.  */
-_ACEOF
-cat confdefs.h conftest.$ac_ext
-cat conftest.$ac_ext _ACEOF
-/* end confdefs.h.  */
-#include $ac_header
-_ACEOF
-if { (eval echo $as_me:$LINENO: \$ac_cpp conftest.$ac_ext\) 5
-  (eval $ac_cpp conftest.$ac_ext) 2conftest.er1
-  ac_status=$?
-  grep -v '^ *+' conftest.er1 conftest.err
-  rm -f conftest.er1
-  cat conftest.err 5
-  echo $as_me:$LINENO: \$? = $ac_status 5
-  (exit $ac_status); } /dev/null; then
-  if test -s conftest.err; then
-ac_cpp_err=$ac_c_preproc_warn_flag
-ac_cpp_err=$ac_cpp_err$ac_c_werror_flag
-  else
-ac_cpp_err=
-  fi
-else
-  ac_cpp_err=yes
-fi
-if test -z $ac_cpp_err; then
-  ac_header_preproc=yes
-else
-  echo $as_me: failed program was: 5
-sed 's/^/| /' conftest.$ac_ext 5
-
-  ac_header_preproc=no
-fi
-rm -f conftest.err conftest.$ac_ext
-echo $as_me:$LINENO: result: $ac_header_preproc 5
-echo ${ECHO_T}$ac_header_preproc 6
-
-# So?  What about this header?
-case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in
-  yes:no: )
-{ echo $as_me:$LINENO: WARNING: $ac_header: accepted by the compiler, 
rejected by the preprocessor! 5
-echo $as_me: WARNING: $ac_header: accepted by the compiler, rejected by the 
preprocessor! 2;}
-{ 

Re: Bug#359164: [powerpc64] d-i fails, base-installer/initramfs/no-generator

[Frans Pop]

On Wednesday 29 March 2006 01:56, Sven Luther wrote:
 I don't know who is to blame for this, probably the powerpc buildd or
 something, but this is clearly something of which i am not responsible,
 since the d-i build-depends are clearly satisfied on my machine, as i
 run dpkg-checkbuilddeps on the svn checkout, and then apt-get install
 all missing packages.

Try 'aptitude update; aptitude (dist-?)upgrade'.
A new libnewt has been available since:
0.52.2-2 (latest build at Mar 19 13:25: maybe-successful) [1]

This breakage is the result of an update of newt with ABI change that 
has led to a rebuild (bin-NMU) of cdebconf.
The reason that your build-depends are satisfied is that d-i depends on 
libnewt-pic for library reduction, which is unversioned.

However, all this is no longer really relevant as, as of today, Colin has 
kindly offered to do the daily builds for PowerPC. I have switched over 
all the links a few hours ago, so you are free to disable the builds and 
clean you home directory on gluck.

The only thing not covered yet is the daily builds of the graphical 
installer, but there is no real rush for that. I have saved the last good 
build.

Thank you for all the work you've done for d-i over the past years.

Cheers,
Frans

[1] http://buildd.debian.org/build.php?pkg=newtarch=powerpc


pgp0awSJQeIPn.pgp
Description: PGP signature

Re: Bug#359164: [powerpc64] d-i fails, base-installer/initramfs/no-generator

[Sven Luther]

On Wed, Mar 29, 2006 at 02:29:36AM +0200, Frans Pop wrote:
 On Wednesday 29 March 2006 01:56, Sven Luther wrote:
  I don't know who is to blame for this, probably the powerpc buildd or
  something, but this is clearly something of which i am not responsible,
  since the d-i build-depends are clearly satisfied on my machine, as i
  run dpkg-checkbuilddeps on the svn checkout, and then apt-get install
  all missing packages.
 
 Try 'aptitude update; aptitude (dist-?)upgrade'.
 A new libnewt has been available since:
 0.52.2-2 (latest build at Mar 19 13:25: maybe-successful) [1]

Mmm.

I do :

apt-get update
if [ $packages ]; then
DEBCONF_PRIORITY=critical apt-get -y --force-yes install $packages
fi
DEBCONF_PRIORITY=critical apt-get -y upgrade

so maybe apt-get upgrade is not enough here ? Is apt-get too broken to handle
this and we should move to aptitude, or is a dist-upgrade needed ?
dist-upgrade is supposed only for release-to-release upgrades, and should not
be used for day-to-day upgrades. ... Mmm, it needed a dist-upgrade indeed.

About the graphical installer, what are the plan for mainline merging, it was
supposed to be soon after the beta2 release, was it not ? 

Friendly,

Sven Luter


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

Re: Wanted: Debian Installer PowerPC porter(s)

[Sven Luther]

On Wed, Mar 29, 2006 at 02:04:58AM +0200, Frans Pop wrote:
 Hi all,
 
 Sven Luther has recently announced [1] that he will no longer work on 
 PowerPC support in Debian Installer.
 
 Colin Watson has already taken over the daily building of d-i images for 
 PowerPC, so working daily builds are available again. Colin is willing to 
 do that long term, but if a new porter should like to take care of that, 
 I'm sure this can be discussed.
 
 
 So what does being a d-i porter involve?
 Mainly it means taking responsibility for architecture specific issues. 
 Ideally this means:
 - regular testing of the installer, preferably on different subarches
 - keeping an eye out for installation reports for powerpc and following up
   on them (especially if architecture specific issues are reported)
 - taking care of architecture specific components of the installer, such
   as kernel udebs, bootloader installers, some partman components
 - reproducing, tracing and (hopefully) resolving bugs
 - taking care of daily builds of d-i images

Current open issues that i am aware of are :

  - partman-prep is broken on IBM/CHRP and PREP and doesn't mark the partition
as prep and doesn't pass the partition number to prep-installer or
yaboot-installer, making debian uninstallable without major hurdle on prep
and IBM RS6k and pseries machines.

  - d-i kernel .udebs need to add support for apus kernels. This was not
possible pre-beta2, due to changes being needed in kernel-wedge, and these
changes being too hazardous to do shortly before the etch beta2.

  - nubus support. There is a working 2.4.27 nubus kernel, which needs to get
d-i support in order to be usefull for installing on nubus machines.
Ideally, the nubus patches should be ported to 2.6.x, but that is another
category of work required.

  - each kernel abi change needs a reupload of the powerpc d-i kernels, and a
rechecking of all the modules for a new version. This is a tedious
process.

  - debian-installer CDs don't boot on ibm rs6k 32bit machines.
yaboot-installer has a problem on those, and the mkvmlinuz generated
kernels with builtin initrd can also not boot (probably due to too huge
ramdisk thansk to initramfs-tools).

  - various old-world issues, including the work to free miboot, and inclusion
of the free miboot version into the official archive. Mmm, i hope Colin
Watson doesn't forget to add miboot support to his daily builds, or
oldworld support will have been definitively killed.

  - the graphical installer doesn't work anymore on powerpc, the graphical
frontend crashes, some heavy debugging is needed here.

Well, that is what i see right now, some of these issues are open since a
couple of weeks now, if not more, and i saw nobody jump in to fix then, even
after i was scheduled for expulsion, so i hope that frans calls will give more
results, altough seeing as it is a tedious process with little respect from
the d-i team ...

Friendly,

Sven Luther


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

Re: Wanted: Debian Installer PowerPC porter(s)

[Frans Pop]

On Wednesday 29 March 2006 03:00, Sven Luther wrote:
 altough seeing as it is a tedious process with little respect from the
 d-i team ... 

I have on purpose avoided anything like this in my mail and will not go 
into any past issues here. I only hope that anyone considering helping 
out with d-i will make their own judgement based on their own experiences 
instead of taking Sven's word for this.

And yes, the Debian Installer team is very grateful to Sven as well for 
the hard work he has done for the installer and related packages like 
parted over the past years.


pgp8YyahCdOtG.pgp
Description: PGP signature

Re: Wanted: Debian Installer PowerPC porter(s)

[Sven Luther]

On Wed, Mar 29, 2006 at 03:10:34AM +0200, Frans Pop wrote:
 On Wednesday 29 March 2006 03:00, Sven Luther wrote:
  altough seeing as it is a tedious process with little respect from the
  d-i team ... 
 
 I have on purpose avoided anything like this in my mail and will not go 
 into any past issues here. I only hope that anyone considering helping 
 out with d-i will make their own judgement based on their own experiences 
 instead of taking Sven's word for this.
 
 And yes, the Debian Installer team is very grateful to Sven as well for 
 the hard work he has done for the installer and related packages like 
 parted over the past years.

It would have been nice to remember that previously though, since well saying
that after basically kicking someone out, well, it does sound more like giving
oneself good concience than any kind of gratefullness.

Friendly,

Sven Luther


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

Re: Wanted: Debian Installer PowerPC porter(s)

[Dean Hamstead]

Although im not able to help in this regard i would like to express
my thanks to sven for his work

Dean

Frans Pop wrote:

Hi all,

Sven Luther has recently announced [1] that he will no longer work on 
PowerPC support in Debian Installer.


Colin Watson has already taken over the daily building of d-i images for 
PowerPC, so working daily builds are available again. Colin is willing to 
do that long term, but if a new porter should like to take care of that, 
I'm sure this can be discussed.



So what does being a d-i porter involve?
Mainly it means taking responsibility for architecture specific issues. 
Ideally this means:

- regular testing of the installer, preferably on different subarches
- keeping an eye out for installation reports for powerpc and following up
  on them (especially if architecture specific issues are reported)
- taking care of architecture specific components of the installer, such
  as kernel udebs, bootloader installers, some partman components
- reproducing, tracing and (hopefully) resolving bugs
- taking care of daily builds of d-i images

Familiarity with used filesystems and booting systems is a definite 
advantage, but in general work on the installer itself is fairly easy as 
most of it is scripted, with only some parts written in C.


Involvement on any level is welcome. Also, as PowerPC has several fairly 
distinct subarchitectures, getting involved for a specific subarch is an 
option.


The Debian Installer team is generally seen as open, friendly and helpful. 
And it has to be as the core team is fairly small but depends on a lot 
of effort from other developers, porters and translators to keep the 
installer in working order for all the (sub)architectures it supports.
General help on the structure and inner workings of the installer and its 
components is always available.


The last release of the installer (Etch Beta 2) had several PowerPC 
specific issues [2]. We'd very much like to see these resolved. There are 
also some open issues for the new graphical version of the installer.


If you are interested, please contact us on the debian-boot list.

Cheers,
Frans Pop

[1] http://lists.debian.org/debian-boot/2006/03/msg01075.html
[2] http://www.debian.org/devel/debian-installer/errata



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

Disable CONFIG_ACORN_PARTITION_CUMANA in Debian kernels?

[Jurij Smakov]

[ Please follow-up to debian-kernel. ]

Hi,

We have received a number of bug reports (353400, 358913, 359207) against 
kernel packages about the check for the Cumana partition table, commonly 
found on Acorn machines. Being too lax, this check occasionally produces 
false positives for VFAT partition tables, preventing the proper mounting 
of USB sticks. The easy solution is, naturally, to disable support for 
this partition table by disabling CONFIG_ACORN_PARTITION_CUMANA. I wonder 
if there are any known cases of people using disks with this partition

table with our kernels. Can there be any other negative consequences?

Best regardsm

Jurij Smakov[EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/   KeyID: C99E03CC


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

Bug#341596: [PATCH] loadkeys -m shouldn't need console.

[Peter Chubb]

This bug really started to annoy me when I couldn't cross-compile ARM
kernels as a batch job...

The problem is the unicode patch, 430_read_keymaps_fmt.patch
which unconditionally tries to work out if the current console is in
unicode mode.  Appended is a patch that makes this conditional on not
-m.

diff -Nru ./console-tools-0.2.3/kbdtools/loadkeys.y 
../build-tree.new/console-tools-0.2.3/kbdtools/loadkeys.y
--- ./console-tools-0.2.3/kbdtools/loadkeys.y   2006-03-29 15:24:20.0 
+1100
+++ ../build-tree.new/console-tools-0.2.3/kbdtools/loadkeys.y   2006-03-29 
15:23:42.0 +1100
@@ -408,17 +408,18 @@
}
 }
 
-  fd = get_console_fd(NULL);
-  if (!optu) {
-if (ioctl(fd, KDGKBMODE, mode)) {
-   perror(KDGKBMODE);
-   fprintf(stderr, _(loadkeys: error reading keyboard mode\n));
-   exit(1);
- }
-if (mode == K_UNICODE)
-   set_charset(unicode);
-}
-
+  if (!optm) {
+fd = get_console_fd(NULL);
+if (!optu) {
+  if (ioctl(fd, KDGKBMODE, mode)) {
+perror(KDGKBMODE);
+fprintf(stderr, _(loadkeys: error reading keyboard mode\n));
+exit(1);
+  }
+  if (mode == K_UNICODE)
+set_charset(unicode);
+  }
+  }
   args = argv + optind - 1;
   /* set up the first input file, if any */
   yywrap();


-- 
Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
http://www.ertos.nicta.com.au   ERTOS within National ICT Australia


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

Re: [Debian-in-workers] Country names for Bengali

[Jamil Ahmed]

On 3/29/06, Denis Barbier [EMAIL PROTECTED] wrote:
 On Thu, Mar 09, 2006 at 10:10:50PM +0100, Denis Barbier wrote:
  On Sun, Feb 26, 2006 at 08:49:22AM +0100, Christian Perrier wrote:
Christian already informed that the bn_BD locale has an issue, I will
try to dig out.
  
   You can ask for help on debian-i18n, at least to be pointed at correct
   documentation about collation rules writing.
  
   Denis barbier gave a very interesting talk at last Debconf about this
   (which talk, dammit, I couldn't attend because I had a D-I talk
   immediately after it).
 
  Slides are available at
 http://people.debian.org/~barbier/talks/debconf5/glibc-locale.pdf
 
  I wrote a first draft of collation rules, based on informations found in
 http://tdil.mit.gov.in/bangla.pdf
 http://www.unicode.org/cldr/data/common/collation/bn.xml
 http://developer.mimer.com/collations/charts/bengali.htm
  Could a native speaker please send a sorted list of words, say around 50,
  one word per line?  I can then check that the file is not modified when
  passed to the sort command.

 Can a native Bengali speaker please provide this file, so that I can
 test collation rules?

Sorry for late response. I will try to send you soon.

Best,
`Jamil

Re: Wanted: Debian Installer PowerPC porter(s)

[Eddy Petrişor]

On 3/29/06, Frans Pop [EMAIL PROTECTED] wrote:
 Hi all,

 Sven Luther has recently announced [1] that he will no longer work on
 PowerPC support in Debian Installer.

Thanks for all your work.

/me asks himself: mybe is time to switch back ARCH=i386 ?! Hopefuly, not.

:-)

--
Regards,
EddyP
=
Imagination is more important than knowledge A.Einstein

Re: Bug#359164: [powerpc64] d-i fails, base-installer/initramfs/no-generator

[Eddy Petrişor]

On 3/29/06, Sven Luther [EMAIL PROTECTED] wrote:
 On Wed, Mar 29, 2006 at 02:29:36AM +0200, Frans Pop wrote:
  On Wednesday 29 March 2006 01:56, Sven Luther wrote:
  Try 'aptitude update; aptitude (dist-?)upgrade'.
  A new libnewt has been available since:
  0.52.2-2 (latest build at Mar 19 13:25: maybe-successful) [1]

 Mmm.

 I do :

 apt-get update
 if [ $packages ]; then
 DEBCONF_PRIORITY=critical apt-get -y --force-yes install $packages
 fi
 DEBCONF_PRIORITY=critical apt-get -y upgrade

 so maybe apt-get upgrade is not enough here ? Is apt-get too broken to handle
 this and we should move to aptitude, or is a dist-upgrade needed ?
 dist-upgrade is supposed only for release-to-release upgrades, and should not
 be used for day-to-day upgrades. ... Mmm, it needed a dist-upgrade indeed.

 About the graphical installer, what are the plan for mainline merging, it was
 supposed to be soon after the beta2 release, was it not ?

I _think_ the open point if the udebs dependency resolution[1]

Wasn't that point addressed by Joey some time ago?

[1] http://wiki.debian.org/DebianInstaller/GUIToDo
--
Regards,
EddyP
=
Imagination is more important than knowledge A.Einstein

Re: Wanted: Debian Installer PowerPC porter(s)

[brian morris]

hi - i am getting pretty worn out myself

putting Debian on a new world mac for first
time lately, a G4. i have thinking now it
it is a hassle. 

i think the installer is over automated and
that increase bug problems. for instance.

a) the partitioning scheme and type i was
given were not much at all to my liking or
need. i was not given any option to correct
this only take it or leave it. i was not told
that journaling was being turned on. 
   since the partition sizes i was given were
not suitable i am force to resize later. my
backup drive here is firewire and i am hearing
it won't boot a backup. (the backup i made on
scsi with the old world machine wouldn't boot
either, but i was able to run parted by interrupting
the installer - although it no longer tells
you you can i guess you can ... )



on more general :

i for one am no windows guy. I trained on unix
back in the old days and now i am 50% mac at least.

i like macs, and i like unix. i can't stand windows.
i really can't. 

is this worth it. i have done some work with 
Fink project/ macosx.2 jaguar. obviously it
it non-free.  i don't like that but i need
to do some pre-production sorts of work. 

by the way fink commander is compared to synaptic
much better !

?suggestions ??






--- Sven Luther [EMAIL PROTECTED] wrote:

 On Wed, Mar 29, 2006 at 03:10:34AM +0200, Frans Pop
 wrote:
  On Wednesday 29 March 2006 03:00, Sven Luther
 wrote:
   altough seeing as it is a tedious process with
 little respect from the
   d-i team ... 
  
  I have on purpose avoided anything like this in my
 mail and will not go 
  into any past issues here. I only hope that anyone
 considering helping 
  out with d-i will make their own judgement based
 on their own experiences 
  instead of taking Sven's word for this.
  
  And yes, the Debian Installer team is very
 grateful to Sven as well for 
  the hard work he has done for the installer and
 related packages like 
  parted over the past years.
 
 It would have been nice to remember that previously
 though, since well saying
 that after basically kicking someone out, well, it
 does sound more like giving
 oneself good concience than any kind of
 gratefullness.
 
 Friendly,
 
 Sven Luther
 
 
 -- 
 To UNSUBSCRIBE, email to
 [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact
 [EMAIL PROTECTED]
 
 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 


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