date:20101212

Processing commands for cont...@bugs.debian.org:

 forcemerge 606840 606843
Bug#606840: installation-report: Keyboard not functioning correctly in the 
graphical installer
Bug#606843: Installation-Report: English language with Finnish location, half 
of the keys stop working
Forcibly Merged 606840 606843.

 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
606843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606843
606840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.12921476672903.transcr...@bugs.debian.org

Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working


 keys were not working anymore
 abcdefghijklmnopqrstuvwxyzåäö -- bcdemnprstxzåäö
 (a,f,g,h,i,j,k,l,o,q,u,v,w,y letters not working)

The problem seems to happen when one picks the Finnish keymap.

Picking the French one doesn't trigger the problem (so I assume others
are OK, too).

Even picking the French keymap *after* picking the Finnish one (by
using Go Back in screen and redo the Choose keyboard
step)leaves you with non-working keys.

So, in some way, the problem might lie in the finnish keymap.




signature.asc
Description: Digital signature

Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working - bug not valid for Germany

2010-12-12 Thread Holger Wansing

Hello,

Jani Reunanen linyp...@gmail.com wrote:
 configure the network: could not write the hostname since part of the
 keys were not working anymore
 abcdefghijklmnopqrstuvwxyzåäö -- bcdemnprstxzåäö
 (a,f,g,h,i,j,k,l,o,q,u,v,w,y letters not working)

while I can confirm this bug for English/Finland, I tried
if this is also valid for Germany, but it isn't:

If language: English is selected in combination with 
country: Germany and keyboard layout: German, everything works
fine.


Holger

-- 

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Created with Sylpheed 2.5.0
under DEBIAN GNU/LINUX 5.0.0 - L e n n y
Registered LinuxUser #311290 - http://counter.li.org/
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101212110406.f71ba5aa.li...@wansing-online.de

Bug#606188: installation-reports: xserver-xorg not installed for gnome/gdm3

2010-12-12 Thread Miguel Figueiredo

A Quarta 08 Dezembro 2010 23:28:52, você escreveu:
 Hi Miguel,
  I have gone the logs on your suggestion (initially was too lazy to
 crawl syslog, SIGH). I should have seen it earlier ...

thanks for analyzing the installation logs.

 
  From syslog, it seem something got wrong on the network so the packages
 were not downloaded.
 (I am pretty sure it was not a permanent error as I was browsing the net
 all that time through the same router/switch)
 
 Here it goes:
 [code]
 Dec  7 03:33:13 in-target: Get:970
 ftp://ftp.sk.debian.org/debian/squeeze/main ntfs-3g i386 1:2010.3.6-1
 [63.8 kB]
 Dec  7 03:33:13 kernel: [ 4842.663844] eth0: Transmit error, Tx status
 register 90.
 Dec  7 03:33:13 kernel: [ 4842.664070] eth0: Transmit error, Tx status
 register c0.
 Dec  7 03:35:13 in-target: Err
 ftp://ftp.sk.debian.org/debian/squeeze/main ntfs-3g i386 1:2010.3.6-1
 Dec  7 03:35:13 in-target:   Data socket timed out
 Dec  7 03:35:22 in-target: Err
 ftp://ftp.sk.debian.org/debian/squeeze/main ntfsprogs i386 2.0.0-1+b1
 [/code]

quoting linux-2.6-2-6-32/Documentation/networking/vortex.txt:

Transmit error, Tx status register 82
-

This is a common error which is almost always caused by another host on
the same network being in full-duplex mode, while this host is in
half-duplex mode.  You need to find that other host and make it run in
half-duplex mode or fix this host to run in full-duplex mode.

As a last resort, you can force the 3c59x driver into full-duplex mode
with

options 3c59x full_duplex=1

but this has to be viewed as a workaround for broken network gear and
should only really be used for equipment which cannot autonegotiate.


I suggest you install again passing  the option to the module to use full 
duplex:

(5.3.1.2 on http://d-i.alioth.debian.org/manual/en.i386/ch05s03.html)

3c509.full_duplex=1

...or try with all hosts as half-duplex if using that NIC.

 
 
 It seems to me the installer error-handling can use some improvement.
 What bothers me most is the silent failure - which to most inexperienced
 user will indicate Debian/Linux's immaturity.

I found a related BR, #579520, on tasksel package. 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579520
If it's the correct package for this, i suggest the discussion to be kept in 
it instead of ending up with several BRs for the same issue.

 
 I am using GUI or basic installer, so the suggestion belove  is for
 Expert mode. But the general idea shall be plausible across the board.
 
 Here it is:
 --
 
 First stage = only detect and report issue
 
 1) The installer will notify the user that (some) package downloads
 failed
  - just writing it into syslog is not enough (who watches that screen
 anyway...)
 
 Second stage = attempt optimistic autocorrection + alow for manual
 
 auto correction)
 
 2) To solve intermittend networks issues, Debian-installer shall
 (automatically) try at least twice to call for installing of the
 packages in case of errors (be it network or other)
  - this should be trivial to achieve - apt will anyway ignore everything
 that is allready installed, so calling it twice is a no-brainer
  - it is actually desirable to do it this way - the delay in APT
 installing what was installer shall provide for time shinf that may
 suffice to mittigate the connection issue
  - in case a dual run was needed (and second run was flawless), user
 just needs be notified of issues (even though they were worked around)
 
 3) In case multi-run of apt is not sufficient to solve all problems,
 user shall be prompted to take appropriate measures to resolve the
 situation
  - dialog box with options like:
  - - a) repair issue (now) and try again
  - - b) repair issue later and reboot into the system
  - - c) repair issue later and perform a cleanup to remove orphaned
 packages (to ensure clean state if only a dependency got installed but
 the parent package was not)
 
 Third stage = provide the user with a list of packages affected
 
 4) When the above (IMO easy to implement) features are there, there
 should be a serious thought given to actually providing a list of
 broken/not-installed packages in a (file) format suitable as input for
 apt for alter use
  - until this is available, user shall be directed
 to /var/log/installer/syslog
 
 Optional addon
 
 5) Actually provide user with two lists as in 4) but of all packages:
  - designated for installation by Debian-installer
  - installed correctly
 So for every installation, succesfull or not, user will get 3 package
 list with, hopefully, one zero-file while the other 2 identical.
 
 
 Yeah I know I am newbie here and now work done, but sometimes even an
 idea can have a non-zero value so here it is :)
 
 
 If you'd like to check the box, let me know until it's clean.
 
 
 Best regards,
 Milan Niznansky
 
 On Wed, 2010-12-08 at 18:55 +, Miguel Figueiredo wrote:
  Hi,
  
  A Terça 07 Dezembro 2010 10:38:31 Milan Niznansky

Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

2010-12-12 Thread Cyril Brulebois

Hi,

Christian PERRIER bubu...@debian.org (12/12/2010):
 So, in some way, the problem might lie in the finnish keymap.

sounds like it. Reproducible in a non-di environment with:
  $ setxkbmap -option -model pc105 fi fi

(People may want to run setxkbmap $their $stuff right before so they
can use the 'Up' arrow to get back to a functional keymap.)

which is what gets called from console-setup-udeb's postinst script
(as seen by inserting 'echo' at the beginning of the line in
/var/lib/dpkg/info/console-setup-udeb.postinst).

I know nothing about fi for now, probably a xkb-data bug; will try to
look into what happened upstream since the version we're shipping.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#606843: Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

2010-12-12 Thread Cyril Brulebois

Hi again,

debian-user-finnish@ added since I need some feedback on that
fi-specific issue. Context: broken debian installer with Finnish
keymap, see bugs #606840 and #606843.

Cyril Brulebois k...@debian.org (12/12/2010):
 I know nothing about fi for now, probably a xkb-data bug; will try to
 look into what happened upstream since the version we're shipping.

I know kung^Wabout fi now.

One workaround:
 - Stick to 'American English' instead of 'Finnish'.
 - Validate that choice, you get 'setxkbmap us' or so.
 - On the next prompts, select 'Go back' until the menu appears. At the
   bottom of the menu, pick 'Execute a shell'.
 - Run this command: 'setxkbmap fi'.
 - Exit the terminal and go back to your installation process.

The (probable) actual bug: Looking into /usr/share/X11/xkb/symbols/fi
one can see that the section starting with “xkb_symbols fi {”,
there's no include besides kpdl and level3, meaning no “basic”
keys. So you only get the ones which are listed in that section. Which
breaks “setxkbmap fi fi” so badly.

AFAICT, adding “include latin(type2)” for example as the first line of
this section makes it possible to get a working keyboard with
“setxkbmap fi fi”. People may try editing this file from the shell
(see above for instructions), with the “nano” editor (and then run
“setxkbamp fi fi”), or in a non-debian-installer environment, to make
sure it does what people may expect from it.

This bug probably should be reassigned to xkb-data. An upload will
follow as soon as I get feedback from fi-knowledgeable people.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#606843: Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

2010-12-12 Thread Cyril Brulebois

Sorry,

Cyril Brulebois k...@debian.org (12/12/2010):
 AFAICT, adding “include latin(type2)” for example as the first line of
 this section makes it possible to get a working keyboard with
 “setxkbmap fi fi”. People may try editing this file from the shell
 (see above for instructions), with the “nano” editor (and then run
 “setxkbamp fi fi”), or in a non-debian-installer environment, to make
 sure it does what people may expect from it.

I forgot the quotes. That should read:
include latin(type2)

Otherwise, one gets this when running “setxkbmap fi fi”:
| Error loading new keyboard description

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#606840: Bug#606843: Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

reassign 606843 xkb-data
severity 606843 important
thanks

Quoting Cyril Brulebois (k...@debian.org):
 Hi again,
 
 debian-user-finnish@ added since I need some feedback on that
 fi-specific issue. Context: broken debian installer with Finnish
 keymap, see bugs #606840 and #606843.
 
 Cyril Brulebois k...@debian.org (12/12/2010):
  I know nothing about fi for now, probably a xkb-data bug; will try to
  look into what happened upstream since the version we're shipping.
 
 I know kung^Wabout fi now.
 
 One workaround:
  - Stick to 'American English' instead of 'Finnish'.
  - Validate that choice, you get 'setxkbmap us' or so.
  - On the next prompts, select 'Go back' until the menu appears. At the
bottom of the menu, pick 'Execute a shell'.
  - Run this command: 'setxkbmap fi'.
  - Exit the terminal and go back to your installation process.
 
 The (probable) actual bug: Looking into /usr/share/X11/xkb/symbols/fi
 one can see that the section starting with “xkb_symbols fi {”,
 there's no include besides kpdl and level3, meaning no “basic”
 keys. So you only get the ones which are listed in that section. Which
 breaks “setxkbmap fi fi” so badly.
 
 AFAICT, adding “include latin(type2)” for example as the first line of
 this section makes it possible to get a working keyboard with
 “setxkbmap fi fi”. People may try editing this file from the shell
 (see above for instructions), with the “nano” editor (and then run
 “setxkbamp fi fi”), or in a non-debian-installer environment, to make
 sure it does what people may expect from it.
 
 This bug probably should be reassigned to xkb-data. An upload will
 follow as soon as I get feedback from fi-knowledgeable people.

Reassigning, then.

I think an upload is OK and is worth going into squeeze as all install
with the finnish keymap are badly broken by this bug.

Thanks for your analysis, Cyril.





signature.asc
Description: Digital signature

Processed: Re: Bug#606843: Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

Processing commands for cont...@bugs.debian.org:

 reassign 606843 xkb-data
Bug #606843 [installation-reports] Installation-Report: English language with 
Finnish location, half of the keys stop working
Bug #606840 [installation-reports] installation-report: Keyboard not 
functioning correctly in the graphical installer
Bug reassigned from package 'installation-reports' to 'xkb-data'.
Bug reassigned from package 'installation-reports' to 'xkb-data'.
Bug No longer marked as found in versions 2.43.
Bug No longer marked as found in versions 2.43.
 severity 606843 important
Bug #606843 [xkb-data] Installation-Report: English language with Finnish 
location, half of the keys stop working
Bug #606840 [xkb-data] installation-report: Keyboard not functioning correctly 
in the graphical installer
Ignoring request to change severity of Bug 606843 to the same value.
Ignoring request to change severity of Bug 606840 to the same value.
 thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
606843: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606843
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.12921714992272.transcr...@bugs.debian.org

Re: Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

2010-12-12 Thread Julien Cristau

reassign 606840 console-setup 1.61
tag 606840 patch
kthxbye

On Sun, Dec 12, 2010 at 13:51:02 +0100, Cyril Brulebois wrote:

 Hi,
 
 Christian PERRIER bubu...@debian.org (12/12/2010):
  So, in some way, the problem might lie in the finnish keymap.
 
 sounds like it. Reproducible in a non-di environment with:
   $ setxkbmap -option -model pc105 fi fi
 
That's not a valid configuration.  The fi variant doesn't exist.

Index: debian/keyboard-configuration.config
===
--- debian/keyboard-configuration.config(revision 65908)
+++ debian/keyboard-configuration.config(working copy)
@@ -511,7 +511,6 @@
;;
 *_FI*)
XKBLAYOUT=fi  # Finland
-   XKBVARIANT=fi # Finland
;;
 *_FR*)
XKBLAYOUT=fr  # French


Cheers,
Julien


signature.asc
Description: Digital signature

Processed: Re: Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

Processing commands for cont...@bugs.debian.org:

 reassign 606840 console-setup 1.61
Bug #606840 [xkb-data] installation-report: Keyboard not functioning correctly 
in the graphical installer
Bug #606843 [xkb-data] Installation-Report: English language with Finnish 
location, half of the keys stop working
Bug reassigned from package 'xkb-data' to 'console-setup'.
Bug reassigned from package 'xkb-data' to 'console-setup'.
Bug #606840 [console-setup] installation-report: Keyboard not functioning 
correctly in the graphical installer
Bug #606843 [console-setup] Installation-Report: English language with Finnish 
location, half of the keys stop working
Bug Marked as found in versions console-setup/1.61.
Bug Marked as found in versions console-setup/1.61.
 tag 606840 patch
Bug #606840 [console-setup] installation-report: Keyboard not functioning 
correctly in the graphical installer
Bug #606843 [console-setup] Installation-Report: English language with Finnish 
location, half of the keys stop working
Added tag(s) patch.
Added tag(s) patch.
 kthxbye
Stopping processing here.

Please contact me if you need assistance.
-- 
606840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606840
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.12921723736358.transcr...@bugs.debian.org

Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

Quoting Julien Cristau (jcris...@debian.org):

 That's not a valid configuration.  The fi variant doesn't exist.

However, if I open a shell in D-I before the keymap is set, then apply
your patch to keyboard-configuration.config, then exit the shell and
continue by selecting the Finnish keymap, the problem
is apparently still there.




signature.asc
Description: Digital signature

Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

2010-12-12 Thread Julien Cristau

On Sun, Dec 12, 2010 at 18:01:30 +0100, Christian PERRIER wrote:

 Quoting Julien Cristau (jcris...@debian.org):
 
  That's not a valid configuration.  The fi variant doesn't exist.
 
 However, if I open a shell in D-I before the keymap is set, then apply
 your patch to keyboard-configuration.config, then exit the shell and
 continue by selecting the Finnish keymap, the problem
 is apparently still there.
 
Please get the output of 'DISPLAY=:0 setxkbmap -print' and 'xkbcomp -xkb
:0 -' from the shell after selecting the finnish keymap (with the
patched config script).

Cheers,
Julien


signature.asc
Description: Digital signature

Processing of rootskel-gtk_1.21_amd64.changes

rootskel-gtk_1.21_amd64.changes uploaded successfully to localhost
along with the files:
  rootskel-gtk_1.21.dsc
  rootskel-gtk_1.21.tar.gz
  rootskel-gtk_1.21_amd64.udeb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1prtuk-0008vx...@franck.debian.org

rootskel-gtk_1.21_amd64.changes ACCEPTED into unstable




Accepted:
rootskel-gtk_1.21.dsc
  to main/r/rootskel-gtk/rootskel-gtk_1.21.dsc
rootskel-gtk_1.21.tar.gz
  to main/r/rootskel-gtk/rootskel-gtk_1.21.tar.gz
rootskel-gtk_1.21_amd64.udeb
  to main/r/rootskel-gtk/rootskel-gtk_1.21_amd64.udeb


Override entries for your package:
rootskel-gtk_1.21.dsc - source debian-installer
rootskel-gtk_1.21_amd64.udeb - optional debian-installer

Announcing to debian-devel-chan...@lists.debian.org


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1prtwd-ew...@franck.debian.org

Bug#606396: installation-reports: Squeeze Beta1 on Apple iBook G4 (powerpc)

2010-12-12 Thread Samuel Thibault

Andrzej P, le Wed 08 Dec 2010 21:41:16 +, a écrit :
I used the default single partition setup suggested by 'partman'.
I assume that the suggested partitioning is correct.  I was
puzzled however that the suggested scheme includes a 2.5 GB swap
space since the Installation Manual states On 32-bit architectures
(i386, m68k, 32-bit SPARC, and PowerPC), the maximum size of a swap
partition is 2GB. [C.3. Recommended Partitioning Scheme].  Is this
no longer true?

On i386 it's no longer true.  I'm not sure for sparc and powerpc, but
I'd tend to think the same.  Porters?

Samuel



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101212124207.ge5...@const

Bug#606621: Acknowledgement (mklibs-readelf: segfaults on static objects)

2010-12-12 Thread Samuel Thibault

Hello,

This is the patch I used for hurd-i386.  I can't remember why it never
got commited into mklibs.

Samuel
diff -ur mklibs-0.1.29.backup/src/mklibs-readelf/main.cpp 
mklibs-0.1.29/src/mklibs-readelf/main.cpp
--- mklibs-0.1.29.backup/src/mklibs-readelf/main.cpp2009-07-24 
10:16:15.0 +
+++ mklibs-0.1.29/src/mklibs-readelf/main.cpp   2009-12-29 09:51:52.0 
+
@@ -56,7 +56,9 @@
 static void process_dynamics (Elf::file *file, int64_t tag)
 {
   const Elf::section_typeElf::section_type_DYNAMIC *section = 
file-get_section_DYNAMIC ();
-  for (std::vectorElf::dynamic *::const_iterator it = section-get_dynamics 
().begin (); it != section-get_dynamics ().end (); ++it)
+  if (!section)
+return;
+  for (std::vectorElf::dynamic *::const_iterator it = section-get_dynamics 
().begin ();it != section-get_dynamics ().end (); ++it)
   {
 Elf::dynamic *dynamic = *it;
 if (dynamic-get_tag () == tag)
@@ -123,6 +125,7 @@
 static void process (command cmd, const char *filename)
 {
   Elf::file *file = Elf::file::open (filename);
+  const Elf::section_typeElf::section_type_DYNSYM *section;
 
   switch (cmd)
   {
@@ -143,10 +146,14 @@
   process_dynamics (file, DT_SONAME);
   break;
 case COMMAND_PRINT_SYMBOLS_PROVIDED:
-  process_symbols_provided (file-get_section_DYNSYM ());
+  section = file-get_section_DYNSYM ();
+  if (section)
+process_symbols_provided (section);
   break;
 case COMMAND_PRINT_SYMBOLS_UNDEFINED:
-  process_symbols_undefined (file-get_section_DYNSYM ());
+  section = file-get_section_DYNSYM ();
+  if (section)
+process_symbols_undefined (section);
   break;
   }
 }

J'ai retrouvé ce qui tu m'avais prêté

2010-12-12 Thread adriana59



Lis jusqu'au bout, tu vas pleurer ...Voici quelques raisons pourquoi, les gants 
tactiles sont l’accessoire de relation social indispensable à ton bien être et 
à ton équilibre sexuel- Tu as chaud aux mains, surtout quand tu les mets.- On 
ne voit plus que tu as les mains sales.- Tu ne raye plus ton iphone avec tes 
ongles de préhistoire.- Au ski, tu niques 10 fois plus parce que tu loupes plus 
un numéro de téléphone.- Ca peut remplacer la préparation H.- Les gants 
tactiles se marient très bien avec la burqa.- Les embouts tactiles provoquent 
des caresses sensuelles et aphrodisiaques, et ils sont de très  bons 
stimulateurs.- Quand tu en a marre de les porter, tu peux en mettre un dans 
chaque poche.- Si tu n’as pas de costume pour Halloween, tu te déguises en 
Batman en les accrochant à tes oreilles.- Tu peux t’en servir d’antenne télé, 
et mettre en place une liaison interplanétaire, d’ailleurs E.T , Buzz lighter 
et Nicolas SARKOZY en ont à une paire.- Tu peux nettoyer ta voiture avec et 
faire la vaisselle, mais évite le micro onde- Ca évite les ampoules
- Au Mac Do tout le monde te matera.- Sur la plage on ne verra que toi
 
- …Nous aimons nos gants tactiles pour un million de raisons,c’est pour 
cela qu’ils sont indispensables et qu’ils nous changent la vie.En plus de nous 
réchauffer les mains, il nous réchauffe le cœur et le reste…. Ceci est une 
chaîne d'humour.Si tu brises la chaîne,ta vie ne sera que solitude, malchance 
et pauvreté. Célibataire tu seras, et à la masturbation éternelle, tu seras 
condamné.
Tu pourras récréer une nouvelle chaîne et annuler ton mauvais sort portant des 
gants tactiles le soir de la Saint valentin, mais uniquement ce soir là.
 
Cette chaîne à le pouvoir de réaliser n’importe quel vœu.
Maintenant, fais un voeuEnvoie cette chaîne à:0 personne: Ton 
voeu va prendre le sens inverse et ta vie ne sera que solitude, malchance et 
pauvreté3 personnes: Ton voeu va se réaliser dans un an.5 personnes: Ton voeu 
va se réaliser dans un mois.7 personnes: Ton voeu va se réaliser dans 2 
semaines.10 personnes: Ton voeu va se réaliser dans la semaine qui suit.+ de 10 
personnes: Ton voeu va se réaliser demain
fais un copier coller, comme ça, pas de risque de virus

Debian installer build: failed or old builds

2010-12-12 Thread Daily build aggregator

Debian installer build overview
---

Failed or old builds:

* OLD BUILD:hppa Jun 07 00:12 bui...@lafayette build_cdrom 
http://d-i.debian.org/daily-images/hppa/daily/build_cdrom.log

* OLD BUILD:hppa Jun 07 00:16 bui...@lafayette build_netboot 
http://d-i.debian.org/daily-images/hppa/daily/build_netboot.log

* OLD BUILD:hppa Jun 07 00:21 bui...@lafayette build_miniiso 
http://d-i.debian.org/daily-images/hppa/daily/build_miniiso.log

* OLD BUILD:mipsel Dec 09 00:12 bui...@rem build_cobalt_netboot-2.6_serial 

http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_serial.log

* OLD BUILD:mipsel Dec 09 00:18 bui...@rem build_cobalt_netboot-2.6_ssh 

http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_ssh.log

* OLD BUILD:mipsel Dec 09 00:20 bui...@rem build_cobalt_netboot-2.6_common 

http://d-i.debian.org/daily-images/mipsel/daily/build_cobalt_netboot-2.6_common.log

* OLD BUILD:mipsel Dec 09 00:24 bui...@rem build_malta_netboot-2.6 

http://d-i.debian.org/daily-images/mipsel/daily/build_malta_netboot-2.6.log

* OLD BUILD:mipsel Dec 09 00:29 bui...@rem build_sb1-bcm91250a_netboot-2.6 

http://d-i.debian.org/daily-images/mipsel/daily/build_sb1-bcm91250a_netboot-2.6.log

* OLD BUILD:sparc Jul 12 11:04 stapp...@dd build_cdrom 

http://people.debian.org/~stappers/d-i/sparc/daily/build_cdrom.log

* OLD BUILD:sparc Jul 12 11:08 stapp...@dd build_netboot 

http://people.debian.org/~stappers/d-i/sparc/daily/build_netboot.log

* OLD BUILD:sparc Jul 12 11:11 stapp...@dd build_miniiso 

http://people.debian.org/~stappers/d-i/sparc/daily/build_miniiso.log


Totals: 113 builds (0 failed, 11 old)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1prwln-0003tt...@ravel.debian.org

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-12 Thread Qin Bo

2010/12/10 Lennart Sorensen lsore...@csclub.uwaterloo.ca


 Is this another case of a driver/NIC taking longer to get link up after
 being enabled than the installer is willing to wait?  I seem to recall
 a bnx2 user a few days ago reporting a similar problem.


How can i find the bnx2 problem? I had set  netcfg/dhcp_timeout=60 as boot
parameter, the problem still reproduce.
But I still think the netcfg didn't got the correct interface, then couldn't
get the IP address from dhcp server.
Because I had read the netcfg source:netcfg.c netcfg-common.c, i can't find
where the program deal with interface=auto.

Bug#606928: tasksel: upgrade fails with debconf in lenny (1.5.24)

2010-12-12 Thread Theppitak Karoonboonyanan

Package: tasksel
Version: 2.85
Severity: serious
Justification: Policy 7.2

On lenny-to-squeeze upgrade, tasksel fails with the following message:

---8---
Preconfiguring packages ...
tasksel template parse error: Template parse error near
`description...@latin.utf-8: Izaberite softver za instaliranje:', in
stanza #1 of /tmp/tasksel.template.34760

(Reading database ... 38788 files and directories currently installed.)
Preparing to replace tasksel-data 2.78 (using .../tasksel-data_2.85_all.deb) ...
Unpacking replacement tasksel-data ...
Preparing to replace tasksel 2.78 (using .../archives/tasksel_2.85_all.deb) ...
Unpacking replacement tasksel ...
Processing triggers for man-db ...
Setting up tasksel-data (2.85) ...
Setting up tasksel (2.85) ...
Template parse error near `description...@latin.utf-8: Izaberite
softver za instaliranje:', in stanza #1 of
/var/lib/dpkg/info/tasksel.templates
dpkg: error processing tasksel (--configure):
 subprocess installed post-installation script returned error exit status 9
Errors were encountered while processing:
 tasksel
E: Sub-process /usr/bin/dpkg returned an error code (1)
---8---

Upgrading debconf (to 1.5.36 for squeeze) first does solve the problem.

It's obvious that tasksel needs a newer versioned dependency on debconf than
the current one (= 0.5). I just don't know which one between 1.5.24 and
1.5.36.

-- System Information:
Debian Release: 5.0.7
 APT prefers testing
 APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.28-11-server (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages tasksel depends on:
ii  aptitude              0.4.11.11-1~lenny1 terminal-based package manager
ii  debconf [debconf-2.0] 1.5.24             Debian configuration management sy
ii  liblocale-gettext-per 1.05-4             Using libc functions for internati
ii  tasksel-data          2.85               Official tasks used for installati

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information:
 tasksel/title:
 tasksel/desktop: gnome
 tasksel/first:
 tasksel/tasks: Mail server



--
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktimw_o3a11cglcdarf7aqmn04eujurgnq4odp...@mail.gmail.com

Re: boot parameter interface=auto can't adaptation the correct NIC

2010-12-12 Thread Floris Bos

Hi,

On Monday, December 13, 2010 04:15:46 am Qin Bo wrote:
 2010/12/10 Lennart Sorensen lsore...@csclub.uwaterloo.ca
 
  Is this another case of a driver/NIC taking longer to get link up after
  being enabled than the installer is willing to wait?  I seem to recall
  a bnx2 user a few days ago reporting a similar problem.
 
 How can i find the bnx2 problem? I had set  netcfg/dhcp_timeout=60 as boot
 parameter, the problem still reproduce.
 But I still think the netcfg didn't got the correct interface, then
 couldn't get the IP address from dhcp server.
 Because I had read the netcfg source:netcfg.c netcfg-common.c, i can't find
 where the program deal with interface=auto.

You need netcfg/choose_interface=auto


As far as the detection goes, it is this part in netcfg.c:

==
interface_up(*ifaces);

usleep(250);

if (ethtool_lite (*ifaces) == 1) /* CONNECTED */ {
di_info(found link on interface %s, making it the 
default., *ifaces);
defiface = strdup(*ifaces);
interface_down(*ifaces);
break;
} else {
#ifdef WIRELESS
struct wireless_config wc;
#endif /* WIRELESS */
di_info(found no link on interface %s., *ifaces);
==


A 250 us delay is kinda short.

It takes 3 seconds for the link of my test box to get up.
(on-board Intel 82574L NIC, connected to a HP 1810G gigabit switch).


-- 
Yours sincerely,

Floris Bos


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201012130441.46315.i...@je-eigen-domein.nl

Bug#606840: Bug#606843: Installation-Report: English language with Finnish location, half of the keys stop working

Quoting Julien Cristau (jcris...@debian.org):
 On Sun, Dec 12, 2010 at 18:01:30 +0100, Christian PERRIER wrote:
 
  Quoting Julien Cristau (jcris...@debian.org):
  
   That's not a valid configuration.  The fi variant doesn't exist.
  
  However, if I open a shell in D-I before the keymap is set, then apply
  your patch to keyboard-configuration.config, then exit the shell and
  continue by selecting the Finnish keymap, the problem
  is apparently still there.
  
 Please get the output of 'DISPLAY=:0 setxkbmap -print' and 'xkbcomp -xkb
 :0 -' from the shell after selecting the finnish keymap (with the
 patched config script).


Gee, hard to do in my setup (Virtualbox): I need to find a way to
switch to a text console (Ctrl-Alt-foo is intercepted by the host
system and I can't remember how to icrcumvent this)and usig a
shell is a no-no as the keymap is set, there...so I can't type these
commands..:-)




signature.asc
Description: Digital signature

Bug#606928: marked as done (tasksel: upgrade fails with debconf in lenny (1.5.24))

Your message dated Mon, 13 Dec 2010 07:10:58 +0100
with message-id 20101213061058.gp1...@mykerinos.kheops.frmug.org
and subject line Re: Bug#606928: tasksel: upgrade fails with debconf in lenny
(1.5.24)
has caused the Debian Bug report #606928,
regarding tasksel: upgrade fails with debconf in lenny (1.5.24)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)

--
606928: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: tasksel
Version: 2.85
Severity: serious
Justification: Policy 7.2

On lenny-to-squeeze upgrade, tasksel fails with the following message:

---8---
Preconfiguring packages ...
tasksel template parse error: Template parse error near
`description...@latin.utf-8: Izaberite softver za instaliranje:', in
stanza #1 of /tmp/tasksel.template.34760

(Reading database ... 38788 files and directories currently installed.)
Preparing to replace tasksel-data 2.78 (using .../tasksel-data_2.85_all.deb) ...
Unpacking replacement tasksel-data ...
Preparing to replace tasksel 2.78 (using .../archives/tasksel_2.85_all.deb) ...
Unpacking replacement tasksel ...
Processing triggers for man-db ...
Setting up tasksel-data (2.85) ...
Setting up tasksel (2.85) ...
Template parse error near `description...@latin.utf-8: Izaberite
softver za instaliranje:', in stanza #1 of
/var/lib/dpkg/info/tasksel.templates
dpkg: error processing tasksel (--configure):
subprocess installed post-installation script returned error exit status 9
Errors were encountered while processing:
tasksel
E: Sub-process /usr/bin/dpkg returned an error code (1)
---8---

Upgrading debconf (to 1.5.36 for squeeze) first does solve the problem.

It's obvious that tasksel needs a newer versioned dependency on debconf than
the current one (= 0.5). I just don't know which one between 1.5.24 and
1.5.36.

-- System Information:
Debian Release: 5.0.7
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.28-11-server (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages tasksel depends on:
ii aptitude 0.4.11.11-1~lenny1 terminal-based package manager
ii debconf [debconf-2.0] 1.5.24 Debian configuration management sy
ii liblocale-gettext-per 1.05-4 Using libc functions for internati
ii tasksel-data 2.85 Official tasks used for installati

tasksel recommends no packages.

tasksel suggests no packages.

-- debconf information:
tasksel/title:
tasksel/desktop: gnome
tasksel/first:
tasksel/tasks: Mail server

---End Message---
---BeginMessage---
Version: 2.86

Quoting Theppitak Karoonboonyanan (t...@linux.thai.net):
Package: tasksel
Version: 2.85
Severity: serious
Justification: Policy 7.2

On lenny-to-squeeze upgrade, tasksel fails with the following message:

(Reading database ... 38788 files and directories currently installed.)
Preparing to replace tasksel-data 2.78 (using .../tasksel-data_2.85_all.deb)
...
Unpacking replacement tasksel-data ...
Preparing to replace tasksel 2.78 (using .../archives/tasksel_2.85_all.deb)
...
Unpacking replacement tasksel ...
Processing triggers for man-db ...
Setting up tasksel-data (2.85) ...
Setting up tasksel (2.85) ...
Template parse error near `description...@latin.utf-8: Izaberite
softver za instaliranje:', in stanza #1 of
/var/lib/dpkg/info/tasksel.templates
dpkg: error processing tasksel (--configure):
subprocess installed post-installation script returned error exit status 9
Errors were encountered while processing:
tasksel
E: Sub-process /usr/bin/dpkg returned an error code (1)
---8---

This is #605569, fixed in tasksel 2.86.

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

Bug#605932: marked as done (drives seem to be detected in undefined order)

Your message dated Mon, 13 Dec 2010 06:32:15 +
with message-id e1ps1xh-0002kg...@franck.debian.org
and subject line Bug#572925: fixed in yaboot-installer 1.1.19
has caused the Debian Bug report #572925,
regarding drives seem to be detected in undefined order
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
572925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/powerpc/iso-cd/debian-testing-powerpc-xfce+lxde-CD-1.iso
29-Nov-2010 11:07  648M
Date: 3-Dec-2010 21:00

Machine: PowerMac G3 (BW)
Processor: PowerPC G3
Memory: 512M
Partitions: /dev/sdc
#type name length   base
  ( size )  system
/dev/sdc1 Apple_partition_map Apple63 @ 1
  ( 31.5k)  Partition map
/dev/sdc2  Apple_Driver43 Macintosh56 @ 64
  ( 28.0k)  Driver 4.3
/dev/sdc3  Apple_Driver43 Macintosh56 @ 120
  ( 28.0k)  Driver 4.3
/dev/sdc4Apple_Driver_ATA Macintosh56 @ 176
  ( 28.0k)  Unknown
/dev/sdc5Apple_Driver_ATA Macintosh56 @ 232
  ( 28.0k)  Unknown
/dev/sdc6  Apple_FWDriver Macintosh   512 @ 288
  (256.0k)  Unknown
/dev/sdc7  Apple_Driver_IOKit Macintosh   512 @ 800
  (256.0k)  Unknown
/dev/sdc8   Apple_Patches Patch Partition 512 @ 1312
  (256.0k)  Unknown
/dev/sdc9 Apple_Bootstrap boot   1600 @ 1824
  (800.0k)  NewWorld bootblock
/dev/sdc10Apple_UNIX_SVR2 root   17519256 @ 263968
  (  8.4G)  Linux native
/dev/sdc11Apple_UNIX_SVR2 swap 260544 @ 3424
  (127.2M)  Linux swap
/dev/sdc12 Apple_Free Extra16 @
17783224 (  8.0k)  Free space

Block size=512, Number of Blocks=17783240
DeviceType=0x0, DeviceId=0x0
Drivers-
1: @ 64 for 23, type=0x1
2: @ 120 for 36, type=0x
3: @ 176 for 21, type=0x701
4: @ 232 for 34, type=0xf8ff

Output of lspci -knn:
00:00.0 Host bridge [0600]: Motorola MPC106 [Grackle] [1057:0002] (rev 40)
00:0d.0 PCI bridge [0604]: Digital Equipment Corporation DECchip 21154
[1011:0026] (rev 02)
00:10.0 VGA compatible controller [0300]: ATI Technologies Inc Rage
128 RE/SG [1002:5245]
Subsystem: Device [b530:0408]
Kernel driver in use: aty128fb
01:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments
PCILynx/PCILynx2 IEEE 1394 Link Layer Controller [104c:8000] (rev 02)
Subsystem: Apple Computer Inc. Device [106b:001c]
01:01.0 IDE interface [0101]: Silicon Image, Inc. PCI0646 [1095:0646] (rev 07)
Subsystem: Silicon Image, Inc. PCI0646 [1095:0646]
Kernel driver in use: pata_cmd64x
01:03.0 SCSI storage controller [0100]: Adaptec AIC-7850 [9004:5078] (rev 03)
Subsystem: Adaptec AHA-2904/Integrated AIC-7850 [9004:7850]
Kernel driver in use: aic7xxx
01:05.0 Unassigned class [ff00]: Apple Computer Inc. Paddington Mac
I/O [106b:0017]
Kernel driver in use: macio
01:06.0 USB Controller [0c03]: OPTi Inc. 82C861 [1045:c861] (rev 10)
Subsystem: OPTi Inc. 82C861 [1045:c861]
Kernel driver in use: ohci_hcd

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

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

Comments/Problems:

boot loader: mkofboot couldn't find /proc/scsi (existing Bug #572869).

After manually editing /etc/yaboot.conf, I was facing another problem
on boot: the disk drives seem to be detected in undefined order, and
this makes it difficult to guess correct /dev/sd letter (and yaboot
doesn't accept LABEL= syntax). I have two IDE disks (pata_cmd64x) and
one SCSI disk (the one used here) (aic7xxx).

Third problem was with X. It was running wild and filling the disk
with its log file. The salvation came with package
firmware-linux-nonfree containing the file r128_cce.bin. Still, I'm
unable to log out and in again, as this makes X hang.


---End Message---
---BeginMessage---
Source: yaboot-installer
Source-Version: 1.1.19

We believe that the bug you reported is fixed in the latest

Bug#572925: marked as done (installation-reports: PowerMac G5 installation report: ofpath doesn't work in the absence of /proc/scsi/scsi)

Your message dated Mon, 13 Dec 2010 06:32:15 +
with message-id e1ps1xh-0002kg...@franck.debian.org
and subject line Bug#572925: fixed in yaboot-installer 1.1.19
has caused the Debian Bug report #572925,
regarding installation-reports: PowerMac G5 installation report: ofpath doesn't 
work in the absence of /proc/scsi/scsi
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
572925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: important

-- Package-specific info:

Boot method: CD
Image version: Debian installer 6.0alpha1
Date: The 2 days preceding Sun Mar  7 08:26:32 UTC 2010

Machine: PowerMac G5 Quad (M9592)
Partitions: df -Tl will do; the raw partition table is preferred

FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/sdb4 ext3   922517820   4569404 871087188   1% /
tmpfstmpfs 8121084 0   8121084   0% /lib/init/rw
udev tmpfs   10240   188 10052   2% /dev
tmpfstmpfs 8121084 0   8121084   0% /dev/shm

/dev/sdb
#type name   length   base   ( 
size )  system
/dev/sdb1 Apple_partition_map Apple  63 @ 1  ( 
31.5k)  Partition map
/dev/sdb2 Apple_Bootstrap bootstrap1600 @ 64 
(800.0k)  NewWorld bootblock
/dev/sdb3  Apple_Free Extra 354 @ 1664   
(177.0k)  Free space
/dev/sdb4 Apple_UNIX_SVR2 root   1874449219 @ 2018   
(893.8G)  Linux native
/dev/sdb5 Apple_UNIX_SVR2 swap 79073931 @ 1874451237 ( 
37.7G)  Linux swap

Block size=512, Number of Blocks=1953525168
DeviceType=0x0, DeviceId=0x0


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

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

Comments/Problems:

Installation worked beautifully with the major exception of yaboot getting
hopelessly confused.

Evidently the ofpath utility has not been updated to handle the state of the
world now that /proc/scsi/scsi is deprecated.  I had to dredge out old
OpenFirmware references and manually edit /etc/yaboot.conf, then run mkofboot.
This generation of PowerMacs (the very last :-( ) uses SATA drives on a PCI-E
bus.

Once I stuffed OpenFirware device-tree magic into yaboot.conf, things sprinted
to a finish.  Even X worked on this foul NVidia device.

Oddly, in rescue mode, the installer told me that installing yaboot failed, then
told me it succeeded with the very next dialog.  Its first guess was correct; I
had to implement the fix myself at a shell prompt.

Here is my /etc/yaboot.conf in case other poor miserable G5 users suffer my
SATAnic fate.  I had to add ofboot, and correct partition and root (which were 3
instead of 4).  At some point I managed to create an over-sized blank area for
the hfs bootblock partition, wasting 177kB of precious space.

N.B.: I'm booting from the second SATA drive, not the first, because I stupidly
installed the drives in the wrong order.  People using sda will probably want:

ofboot=/ht/p...@9/k2-sata-root/k2-s...@0/d...@0:2

## yaboot.conf generated by debian-installer
##
## run: man yaboot.conf for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

boot=/dev/sdb2
ofboot=/ht/p...@9/k2-sata-root/k2-s...@1/d...@0:2
partition=4
root=/dev/sdb4
timeout=50
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot
enablecdboot

image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img

image=/boot/vmlinux.old
label=old
read-only
initrd=/boot/initrd.img.old

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

*** I can't find these logs.  Where did they go?

Here's lspci:
:00:0b.0 PCI bridge: Apple Computer Inc. CPC945 PCIe Bridge
:0a:00.0 VGA compatible controller:

Bug#605932: marked as done (drives seem to be detected in undefined order)

Your message dated Mon, 13 Dec 2010 06:32:15 +
with message-id e1ps1xh-0002km...@franck.debian.org
and subject line Bug#605932: fixed in yaboot-installer 1.1.19
has caused the Debian Bug report #605932,
regarding drives seem to be detected in undefined order
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
605932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports

Boot method: CD
Image version: 
http://cdimage.debian.org/cdimage/weekly-builds/powerpc/iso-cd/debian-testing-powerpc-xfce+lxde-CD-1.iso
29-Nov-2010 11:07  648M
Date: 3-Dec-2010 21:00

Machine: PowerMac G3 (BW)
Processor: PowerPC G3
Memory: 512M
Partitions: /dev/sdc
#type name length   base
  ( size )  system
/dev/sdc1 Apple_partition_map Apple63 @ 1
  ( 31.5k)  Partition map
/dev/sdc2  Apple_Driver43 Macintosh56 @ 64
  ( 28.0k)  Driver 4.3
/dev/sdc3  Apple_Driver43 Macintosh56 @ 120
  ( 28.0k)  Driver 4.3
/dev/sdc4Apple_Driver_ATA Macintosh56 @ 176
  ( 28.0k)  Unknown
/dev/sdc5Apple_Driver_ATA Macintosh56 @ 232
  ( 28.0k)  Unknown
/dev/sdc6  Apple_FWDriver Macintosh   512 @ 288
  (256.0k)  Unknown
/dev/sdc7  Apple_Driver_IOKit Macintosh   512 @ 800
  (256.0k)  Unknown
/dev/sdc8   Apple_Patches Patch Partition 512 @ 1312
  (256.0k)  Unknown
/dev/sdc9 Apple_Bootstrap boot   1600 @ 1824
  (800.0k)  NewWorld bootblock
/dev/sdc10Apple_UNIX_SVR2 root   17519256 @ 263968
  (  8.4G)  Linux native
/dev/sdc11Apple_UNIX_SVR2 swap 260544 @ 3424
  (127.2M)  Linux swap
/dev/sdc12 Apple_Free Extra16 @
17783224 (  8.0k)  Free space

Block size=512, Number of Blocks=17783240
DeviceType=0x0, DeviceId=0x0
Drivers-
1: @ 64 for 23, type=0x1
2: @ 120 for 36, type=0x
3: @ 176 for 21, type=0x701
4: @ 232 for 34, type=0xf8ff

Output of lspci -knn:
00:00.0 Host bridge [0600]: Motorola MPC106 [Grackle] [1057:0002] (rev 40)
00:0d.0 PCI bridge [0604]: Digital Equipment Corporation DECchip 21154
[1011:0026] (rev 02)
00:10.0 VGA compatible controller [0300]: ATI Technologies Inc Rage
128 RE/SG [1002:5245]
Subsystem: Device [b530:0408]
Kernel driver in use: aty128fb
01:00.0 FireWire (IEEE 1394) [0c00]: Texas Instruments
PCILynx/PCILynx2 IEEE 1394 Link Layer Controller [104c:8000] (rev 02)
Subsystem: Apple Computer Inc. Device [106b:001c]
01:01.0 IDE interface [0101]: Silicon Image, Inc. PCI0646 [1095:0646] (rev 07)
Subsystem: Silicon Image, Inc. PCI0646 [1095:0646]
Kernel driver in use: pata_cmd64x
01:03.0 SCSI storage controller [0100]: Adaptec AIC-7850 [9004:5078] (rev 03)
Subsystem: Adaptec AHA-2904/Integrated AIC-7850 [9004:7850]
Kernel driver in use: aic7xxx
01:05.0 Unassigned class [ff00]: Apple Computer Inc. Paddington Mac
I/O [106b:0017]
Kernel driver in use: macio
01:06.0 USB Controller [0c03]: OPTi Inc. 82C861 [1045:c861] (rev 10)
Subsystem: OPTi Inc. 82C861 [1045:c861]
Kernel driver in use: ohci_hcd

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

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

Comments/Problems:

boot loader: mkofboot couldn't find /proc/scsi (existing Bug #572869).

After manually editing /etc/yaboot.conf, I was facing another problem
on boot: the disk drives seem to be detected in undefined order, and
this makes it difficult to guess correct /dev/sd letter (and yaboot
doesn't accept LABEL= syntax). I have two IDE disks (pata_cmd64x) and
one SCSI disk (the one used here) (aic7xxx).

Third problem was with X. It was running wild and filling the disk
with its log file. The salvation came with package
firmware-linux-nonfree containing the file r128_cce.bin. Still, I'm
unable to log out and in again, as this makes X hang.


---End Message---
---BeginMessage---
Source: yaboot-installer
Source-Version: 1.1.19

We believe that the bug you reported is fixed in the latest

Bug#606147: marked as done (yaboot-installer: Use short unique OS labels returned by os-prober)

Your message dated Mon, 13 Dec 2010 06:32:15 +
with message-id e1ps1xh-0002kq...@franck.debian.org
and subject line Bug#606147: fixed in yaboot-installer 1.1.19
has caused the Debian Bug report #606147,
regarding yaboot-installer: Use short unique OS labels returned by os-prober
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
606147: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: yaboot-installer
Tags: patch

Yaboot-installer should use short unique OS labels returned by os-prober
instead of long titles. It should add oldlabel to the label, if available.

Currently, first word from long title is actually used by yaboot. This
regularly makes duplicate labels. Current solution of prepending the
last part of the partition name to the label just adds to the confusion
as unix device/partition names are not persistent anymore.


Index: debian/postinst
===
--- debian/postinst	(revision 65533)
+++ debian/postinst	(working copy)
@@ -255,10 +255,10 @@
 	linux)
 	IFS=:
 	linux-boot-prober $partition | while read \
-		rootpart bootpart label kernel initrd params; do
+		rootpart bootpart oldlabel kernel initrd params; do
 		IFS=$OLDIFS
 		info linux-boot-probed: \
-		 $rootpart:$bootpart:$label:$kernel:$initrd:$params
+		 $rootpart:$bootpart:$oldlabel:$kernel:$initrd:$params
 		ofrootpart=$(map_of_path $mappedpartition) || continue
 		debug OF root partition: $ofrootpart
 		# bootpart may or may not be in devfs syntax.
@@ -267,13 +267,8 @@
 		debug mapped boot partition: $mappedbootpart
 		ofbootpart=$(map_of_path $mappedbootpart) || continue
 		debug OF boot partition: $ofbootpart
-		if [ -z $label ]; then
-		label=$title
-		fi
-		# Prepend the last part of the partition name to the label,
-		# for uniqueness and (I hope) clarity, given that we don't
-		# have a way to display a useful description in yaboot.
-		label=${mappedbootpart##*/}-$label
+		# Add oldlabel to os-prober provided label, if available.
+		label=$label${oldlabel:+-${oldlabel}}
 		if echo $kernel | grep -q '^/boot/'  \
 		   [ $mappedbootpart != $mappedpartition ]; then
 		# separate /boot partition


signature.asc
Description: OpenPGP digital signature
---End Message---
---BeginMessage---
Source: yaboot-installer
Source-Version: 1.1.19

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

yaboot-installer_1.1.19.dsc
  to main/y/yaboot-installer/yaboot-installer_1.1.19.dsc
yaboot-installer_1.1.19.tar.gz
  to main/y/yaboot-installer/yaboot-installer_1.1.19.tar.gz
yaboot-installer_1.1.19_powerpc.udeb
  to main/y/yaboot-installer/yaboot-installer_1.1.19_powerpc.udeb



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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 606...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Milan Kupcevic mi...@physics.harvard.edu (supplier of updated 
yaboot-installer package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 11 Dec 2010 22:42:27 -0500
Source: yaboot-installer
Binary: yaboot-installer
Architecture: source powerpc
Version: 1.1.19
Distribution: unstable
Urgency: low
Maintainer: Debian Install System Team debian-boot@lists.debian.org
Changed-By: Milan Kupcevic mi...@physics.harvard.edu
Description: 
 yaboot-installer - Install yaboot on a hard disk (udeb)
Closes: 572925 605932 606147
Changes: 
 yaboot-installer (1.1.19) unstable; urgency=low
 .
   [ Milan Kupcevic ]
   * Use short unique OS labels returned by os-prober instead of long titles.
 Add oldlabel to the label, if available.  (Closes: #606147)
   * Use persistent device naming symlinks and UUID/LABEL tags instead of unix
 block device names.  (Closes: #572925, #605932)
 .
   [ Updated translations ]
   * Lao (lo.po) by Anousak Souphavanh
   * Sinhala (si.po) by Danishka Navin
   * Slovenian (sl.po) by Vanja Cvelbar
Checksums-Sha1: 
 3984d32e4e29e9ab991da258d809414a74e2edc3 1257 yaboot-installer_1.1.19.dsc
 2f335013085c6a9ff296bcc001e97e67d3311b97 118196 yaboot-installer_1.1.19.tar.gz

Bug#572925: marked as done (installation-reports: PowerMac G5 installation report: ofpath doesn't work in the absence of /proc/scsi/scsi)

Your message dated Mon, 13 Dec 2010 06:32:15 +
with message-id e1ps1xh-0002km...@franck.debian.org
and subject line Bug#605932: fixed in yaboot-installer 1.1.19
has caused the Debian Bug report #605932,
regarding installation-reports: PowerMac G5 installation report: ofpath doesn't 
work in the absence of /proc/scsi/scsi
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
605932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: important

-- Package-specific info:

Boot method: CD
Image version: Debian installer 6.0alpha1
Date: The 2 days preceding Sun Mar  7 08:26:32 UTC 2010

Machine: PowerMac G5 Quad (M9592)
Partitions: df -Tl will do; the raw partition table is preferred

FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/sdb4 ext3   922517820   4569404 871087188   1% /
tmpfstmpfs 8121084 0   8121084   0% /lib/init/rw
udev tmpfs   10240   188 10052   2% /dev
tmpfstmpfs 8121084 0   8121084   0% /dev/shm

/dev/sdb
#type name   length   base   ( 
size )  system
/dev/sdb1 Apple_partition_map Apple  63 @ 1  ( 
31.5k)  Partition map
/dev/sdb2 Apple_Bootstrap bootstrap1600 @ 64 
(800.0k)  NewWorld bootblock
/dev/sdb3  Apple_Free Extra 354 @ 1664   
(177.0k)  Free space
/dev/sdb4 Apple_UNIX_SVR2 root   1874449219 @ 2018   
(893.8G)  Linux native
/dev/sdb5 Apple_UNIX_SVR2 swap 79073931 @ 1874451237 ( 
37.7G)  Linux swap

Block size=512, Number of Blocks=1953525168
DeviceType=0x0, DeviceId=0x0


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

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

Comments/Problems:

Installation worked beautifully with the major exception of yaboot getting
hopelessly confused.

Evidently the ofpath utility has not been updated to handle the state of the
world now that /proc/scsi/scsi is deprecated.  I had to dredge out old
OpenFirmware references and manually edit /etc/yaboot.conf, then run mkofboot.
This generation of PowerMacs (the very last :-( ) uses SATA drives on a PCI-E
bus.

Once I stuffed OpenFirware device-tree magic into yaboot.conf, things sprinted
to a finish.  Even X worked on this foul NVidia device.

Oddly, in rescue mode, the installer told me that installing yaboot failed, then
told me it succeeded with the very next dialog.  Its first guess was correct; I
had to implement the fix myself at a shell prompt.

Here is my /etc/yaboot.conf in case other poor miserable G5 users suffer my
SATAnic fate.  I had to add ofboot, and correct partition and root (which were 3
instead of 4).  At some point I managed to create an over-sized blank area for
the hfs bootblock partition, wasting 177kB of precious space.

N.B.: I'm booting from the second SATA drive, not the first, because I stupidly
installed the drives in the wrong order.  People using sda will probably want:

ofboot=/ht/p...@9/k2-sata-root/k2-s...@0/d...@0:2

## yaboot.conf generated by debian-installer
##
## run: man yaboot.conf for details. Do not make changes until you have!!
## see also: /usr/share/doc/yaboot/examples for example configurations.
##
## For a dual-boot menu, add one or more of:
## bsd=/dev/hdaX, macos=/dev/hdaY, macosx=/dev/hdaZ

boot=/dev/sdb2
ofboot=/ht/p...@9/k2-sata-root/k2-s...@1/d...@0:2
partition=4
root=/dev/sdb4
timeout=50
install=/usr/lib/yaboot/yaboot
magicboot=/usr/lib/yaboot/ofboot
enablecdboot

image=/boot/vmlinux
label=Linux
read-only
initrd=/boot/initrd.img

image=/boot/vmlinux.old
label=old
read-only
initrd=/boot/initrd.img.old

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

*** I can't find these logs.  Where did they go?

Here's lspci:
:00:0b.0 PCI bridge: Apple Computer Inc. CPC945 PCIe Bridge
:0a:00.0 VGA compatible controller:

Bug#606928: tasksel: upgrade fails with debconf in lenny (1.5.24)

2010-12-12 Thread Theppitak Karoonboonyanan

On Mon, Dec 13, 2010 at 1:10 PM, Christian PERRIER bubu...@debian.org wrote:

 This is #605569, fixed in tasksel 2.86.

Oh, before filing the bug, I did check tasksel 2.88 in unstable, and
found Depends: debconf (= 0.5) is still there. But I didn't notice the
Pre-Depends field.

This is OK. But why keeping duplicate info overridden by the other?

Besides, are you sure Pre-Depends is really needed? I also tried
upgrading debconf together with tasksel, not one by one, and it still
worked.

Regards,
-- 
Theppitak Karoonboonyanan
http://linux.thai.net/~thep/



-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/aanlktimjygoc_07ssy75ewcfzbdqrgellm3t9l5mm...@mail.gmail.com

Processing of yaboot-installer_1.1.19_powerpc.changes

yaboot-installer_1.1.19_powerpc.changes uploaded successfully to localhost
along with the files:
  yaboot-installer_1.1.19.dsc
  yaboot-installer_1.1.19.tar.gz
  yaboot-installer_1.1.19_powerpc.udeb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ps1vp-0002fq...@franck.debian.org

yaboot-installer_1.1.19_powerpc.changes ACCEPTED into unstable




Accepted:
yaboot-installer_1.1.19.dsc
  to main/y/yaboot-installer/yaboot-installer_1.1.19.dsc
yaboot-installer_1.1.19.tar.gz
  to main/y/yaboot-installer/yaboot-installer_1.1.19.tar.gz
yaboot-installer_1.1.19_powerpc.udeb
  to main/y/yaboot-installer/yaboot-installer_1.1.19_powerpc.udeb


Override entries for your package:
yaboot-installer_1.1.19.dsc - source debian-installer
yaboot-installer_1.1.19_powerpc.udeb - standard debian-installer

Announcing to debian-devel-chan...@lists.debian.org
Closing bugs: 572925 605932 606147 


Thank you for your contribution to Debian.


-- 
To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/e1ps1xg-0002k9...@franck.debian.org

Bug#606928: tasksel: upgrade fails with debconf in lenny (1.5.24)