Bug#269878: marked as done (Please default to Icelandic keyboard when choosing Iceland as country even if language is English)
Your message dated Tue, 19 Sep 2006 08:29:39 +0200 with message-id [EMAIL PROTECTED] and subject line Bug no more relevant 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 INSTALL REPORT Debian-installer-version: RC1 downloaded Aug 20 from http://cdimage.debian.org/pub/cdimage-testing/sarge_d-i/i386/rc1/sarge-i386-businesscard.iso uname -a: Linux vr3pc28 2.6.7-1-k7 #1 Thu Jul 8 06:45:35 EDT 2004 i686 GNU/Linux Date: Sat Sep 4 02:01:38 GMT 2004 Method: Booted off a buisness card iso. Network install from ftp.rhnet.is. Not proxied. Machine: Self built box with nvida nforce motherboard. Processor: processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 6 model name : AMD Athlon(TM) XP 1600+ stepping: 2 cpu MHz : 1403.252 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow bogomips: 2777.08 Memory: MemTotal: 484604 kB MemFree: 3248 kB Buffers: 24232 kB Cached: 423956 kB SwapCached: 0 kB Active: 39600 kB Inactive: 416928 kB HighTotal: 0 kB HighFree:0 kB LowTotal: 484604 kB LowFree: 3248 kB SwapTotal: 497968 kB SwapFree: 497968 kB Dirty: 0 kB Writeback: 0 kB Mapped: 12816 kB Slab:17604 kB Committed_AS:14152 kB PageTables:220 kB VmallocTotal: 540664 kB VmallocUsed: 6240 kB VmallocChunk: 534112 kB Root Device: # sfdisk -d # partition table of /dev/hda unit: sectors /dev/hda1 : start= 63, size= 995967, Id=82 /dev/hda2 : start= 996030, size= 498015, Id=83, bootable /dev/hda3 : start= 1494045, size= 9767520, Id=83 /dev/hda4 : start= 11261565, size= 69143760, Id= 5 /dev/hda5 : start= 11261628, size= 1959867, Id=83 /dev/hda6 : start= 13221558, size= 1959867, Id=83 /dev/hda7 : start= 15181488, size= 65223837, Id=83 # mount -a /dev/hda2 on / type reiserfs (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/hda5 on /tmp type reiserfs (rw) /dev/hda3 on /usr type reiserfs (rw) /dev/hda6 on /var type reiserfs (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/hda7 on /home type reiserfs (rw) 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] Install base system:[O] Install boot loader:[O] Reboot: [O] Comments/Problems: Super smooth! Great work on the Debian installer! The only thing I can think of is that after choosing the country Iceland the default keybord should be Icelandic. Install logs and other status info is available in /var/log/debian-installer/. Once you have filled out this report, mail it to [EMAIL PROTECTED] ---End Message--- ---BeginMessage--- From console-data settings, an Icelandic keyboard should now be chosen when language is English and country is Iceland. -- ---End Message---
Bug#276067: marked as done (Please base the keyboard layout choice on country rather than language or language/country settings)
Your message dated Tue, 19 Sep 2006 08:29:39 +0200 with message-id [EMAIL PROTECTED] and subject line Bug no more relevant 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 Debian-installer-version: from http://cdimage.debian.org/pub/cdimage-testing/daily/i386/ just before rc2 was released (sorry, don't have the exact date for the download) uname -a: Linux betula 2.6.8-1-386 #1 Mon Sep 13 23:29:55 EDT 2004 i686 GNU/Linux (I upgraded the kernel from the 2.4. on the install) Date: 2004-07-26 Method: Boot from cdrom, fetched packages through http from no.debian.org Machine: Compaq deskpro Processor: vendor_id : GenuineIntel cpu family : 6 model : 8 model name : Pentium III (Coppermine) stepping: 6 cpu MHz : 731.133 cache size : 256 KB Memory: [EMAIL PROTECTED]:~$ free total used free sharedbuffers cached Mem:192052 183652 8400 0 21304 86628 -/+ buffers/cache: 75720 116332 Swap: 181396 48 181348 Root Device: ide: /dev/hda7 on / type reiserfs (rw) Root Size/partition table: /boot: /dev/hda1 * 1 285 143608+ 83 Linux /dev/hda2 286 19386 96269045 Extended /dev/hda555215880 181408+ 82 Linux swap /var: /dev/hda6 2863195 1466577 83 Linux /: /dev/hda731965520 1171768+ 83 Linux /usr: /dev/hda858819755 1952968+ 83 Linux /home: /dev/hda99756 19386 4853992+ 83 Linux Output of lspci and lspci -n: betula:/home/morten# lspci :00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02) :00:01.0 PCI bridge: Intel Corp. 82815 815 Chipset AGP Bridge (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 01) :00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 01) :00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 01) :00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 01) :01:00.0 VGA compatible controller: nVidia Corporation NV5 [RIVA TNT2/TNT2 Pro] (rev 15) :02:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller (rev 01) :02:0a.0 Multimedia audio controller: VIA Technologies Inc. ICE1712 [Envy24] PCI Multi-Channel I/O Controller (rev 02) betula:/home/morten# lspci -n :00:00.0 0600: 8086:1130 (rev 02) :00:01.0 0604: 8086:1131 (rev 02) :00:1e.0 0604: 8086:244e (rev 01) :00:1f.0 0601: 8086:2440 (rev 01) :00:1f.1 0101: 8086:244b (rev 01) :00:1f.4 0c03: 8086:2444 (rev 01) :01:00.0 0300: 10de:0028 (rev 15) :02:08.0 0200: 8086:2449 (rev 01) :02:0a.0 0401: 1412:1712 (rev 02) 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] but see below Create file systems:[ O] Mount partitions: [ O] Install base system:[ O] Install boot loader:[ O] Reboot: [O ] Comments/Problems: Minor nitpicks: After the initial question of language, I did not find Norway as one of the primary countriesafter having selected UK English, I would guess most Norwegian running debian has english as their main computing language Further on, having told the installer that I was in Norway, I was a bit surprised not to find norwegian as the pre selecetd keyboard On the partitioning step, I was a bit confused on which buttons that meant [OK] and [Cancel] quite a few times, I defined a partition, just to manage to misunderstand which button to press and immideately lose it again. Might have been a bit late though.. Mainly, just great! I have installed quite a few debian 3.0 system, this was mostly a much more 'polished' experience. Morten ---End Message--- ---BeginMessage--- From console-data settings, an Icelandic keyboard should now be chosen when language is English and country is Iceland. -- ---End Message---
Processed: Bug assigned to wrong package
Processing commands for [EMAIL PROTECTED]: reassign 251423 kbd-chooser Bug#251423: Give users some hints about possible keyboards Bug reassigned from package `console-common' to `kbd-chooser'. forcemerge 248882 251423 Bug#248882: Provive an option to test a keyboard map Bug#251423: Give users some hints about possible keyboards Forcibly Merged 248882 251423. 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]
Please update debconf PO translation for the package console-common 0.7.62
(PLEASE READ this mail carefully. The usual procedure is slightly changed for that update) Hi, You are noted as the last translator of the Debian configuration translation for the console-common package. The templates in this package have been rewritten to better fit the recommended writing style described in Debian Developers Reference. This marks some of your translations as fuzzy. Please update them with regards to the new writing style. Please note that former translations have been kept at the end of the attached file to save you extra work. Please respect the Reply-To: field and send your updated translation to [EMAIL PROTECTED] This Debian bug report will collect ALL translation updates. Please DO NOT send translation updates as separate bug reports, this time. The deadline for submitting translation updates is October 1st. Thanks, Christian, in name of the console-common maintainers. # translation of console-common_debian_po.po to Wolof # #Translators, if you are not familiar with the PO format, gettext #documentation is worth reading, especially sections dedicated to #this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' #Some information specific to po-debconf are available at #/usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans# #Developers do not need to manually edit POT or PO files. # Mouhamadou Mamoune Mbacke [EMAIL PROTECTED], 2006. # msgid msgstr Project-Id-Version: console-common_debian_po\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-09-19 09:15+0200\n PO-Revision-Date: 2006-09-09 16:07+\n Last-Translator: Mouhamadou Mamoune Mbacke [EMAIL PROTECTED]\n Language-Team: Wolof debian-boot@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n X-Generator: KBabel 1.9.1\n #. Type: select #. Choices #: ../templates.in:1001 msgid Select keymap from arch list msgstr Tannal tërëliinu tablocaabi ci list arch #. Type: select #. Choices #: ../templates.in:1001 msgid Don't touch keymap msgstr Bul laal tërëliinwi #. Type: select #. Choices #: ../templates.in:1001 msgid Keep kernel keymap msgstr Tëyéel tërëliinu kernel bi #. Type: select #. Choices #: ../templates.in:1001 msgid Select keymap from full list msgstr Tannal aw tërëliin ci ab list bu mat #. Type: select #. Description #: ../templates.in:1002 msgid Policy for handling keymaps: msgstr #. Type: select #. Description #: ../templates.in:1002 msgid The keymap describes how keys are laid out on your keyboard, and what symbols (letters, digits, etc.) are drawn on them. msgstr Tërëliinu tablocaabi bi mooy wane yoon winuy toftalee butoŋ yi nekk ci tablocaabi bi (clavier), ak yan mandarga (araf, numero,...)lañu ci bind. #. Type: select #. Description #: ../templates.in:1002 msgid \Select keymap from arch list\ will allow you to select one of the predefined keymaps specific for your architecture - you will most likely want this unless you have a USB keyboard. msgstr \Tannal tërëliinu tablocaabi ci list arch\ dana la may nga tann benn ci tërëliinu tablocaabi yiñu defaral sa arkitektuur (architecture) ba noppi - jamtaluna lool ne lii ngay bëgg, ndare book nga yore tablocaabi USB. #. Type: select #. Description #: ../templates.in:1002 msgid \Don't touch keymap\ will prevent the configuration system from overwriting the keymap you have in /etc/console. Select this if you want to keep a keymap you obtained through other means. Please remember to install new keymaps with install-keymap(8) if you select this choice. msgstr \Bul laal tërëliinwi\ dana tax ba sistemu komfigraasioŋ bi du far sa tërëliin wi nekk ci fiise /etc/console. Tannal bii bu fekkee dangaa yore aw tërëliin boo ame ci waneen yoon. Bul fattee istale ay tërëliin yu bess ak install-keymap(8), bu fekkee bii nga tann. #. Type: select #. Description #: ../templates.in:1002 msgid \Keep kernel keymap\ will prevent any keymap from being loaded next time your system boots. It will remove from /etc/console any keymap you may have already selected (it will be lost), but if you have already loaded a keymap, it cannot be changed back until you reboot. msgstr \Tëyéel tërëliinu kernel bi\ dana tax booy talaat (boot) sa masin deesul sëf waneen tërëliin(keymap). Weppu tërëliin wu nekkoon ci fiise /etc/ console deesna ko fa jële (deesna ko ñakk), waaye bu fekkee jotoon ngaa sëf aw tërëliin, konn deesuko mana soppi fiiyak ngay talaat (reboot) sa masin. #. Type: select #. Description #: ../templates.in:1002 msgid \Select keymap from full list\ offers a full listing of all predefined keymaps. You want this, if you use an USB keyboard from a different computer architecture or if you use an adapter to use such a keyboard. msgstr \Tannal aw tërëliin ci ab list bu mat\ dana la jox ab list bu am mbooleem tërëliin yi fi am. yaangi soxlaa bii, bu fekkee
Please update debconf PO translation for the package console-common 0.7.62
(PLEASE READ this mail carefully. The usual procedure is slightly changed for that update) Hi, You are noted as the last translator of the Debian configuration translation for the console-common package. The templates in this package have been rewritten to better fit the recommended writing style described in Debian Developers Reference. This marks some of your translations as fuzzy. Please update them with regards to the new writing style. Please note that former translations have been kept at the end of the attached file to save you extra work. Please respect the Reply-To: field and send your updated translation to [EMAIL PROTECTED] This Debian bug report will collect ALL translation updates. Please DO NOT send translation updates as separate bug reports, this time. The deadline for submitting translation updates is October 1st. Thanks, Christian, in name of the console-common maintainers. # #Translators, if you are not familiar with the PO format, gettext #documentation is worth reading, especially sections dedicated to #this format, e.g. by running: # info -n '(gettext)PO Files' # info -n '(gettext)Header Entry' # #Some information specific to po-debconf are available at #/usr/share/doc/po-debconf/README-trans # or http://www.debian.org/intl/l10n/po-debconf/README-trans # #Developers do not need to manually edit POT or PO files. # msgid msgstr Project-Id-Version: console-common\n Report-Msgid-Bugs-To: \n POT-Creation-Date: 2006-09-19 09:15+0200\n PO-Revision-Date: 2004-04-15 18:18+0100\n Last-Translator: André Dahlqvist [EMAIL PROTECTED]\n Language-Team: Swedish debian-boot@lists.debian.org\n MIME-Version: 1.0\n Content-Type: text/plain; charset=UTF-8\n Content-Transfer-Encoding: 8bit\n #. Type: select #. Choices #: ../templates.in:1001 msgid Select keymap from arch list msgstr Välj tangentuppsättning från arkitekturlista #. Type: select #. Choices #: ../templates.in:1001 msgid Don't touch keymap msgstr Rör ej tangentuppsättning #. Type: select #. Choices #: ../templates.in:1001 msgid Keep kernel keymap msgstr Behåll kärnans tangentuppsättning #. Type: select #. Choices #: ../templates.in:1001 msgid Select keymap from full list msgstr Välj tangentuppsättning från komplett lista #. Type: select #. Description #: ../templates.in:1002 msgid Policy for handling keymaps: msgstr #. Type: select #. Description #: ../templates.in:1002 msgid The keymap describes how keys are laid out on your keyboard, and what symbols (letters, digits, etc.) are drawn on them. msgstr Tangentuppsättningen beskriver hur tangenter är placerade på tangentbordet och vilka symboler (bokstäver, siffror etc) som är avbildade på dem. #. Type: select #. Description #: ../templates.in:1002 msgid \Select keymap from arch list\ will allow you to select one of the predefined keymaps specific for your architecture - you will most likely want this unless you have a USB keyboard. msgstr \Välj tangentuppsättning från arkitekturlista\ låter dig välja en av de fördefinierade tangentuppsättningarna för just din arkitektur; du vill förmodligen välja denna, förutom om du har ett USB-tangentbord. #. Type: select #. Description #: ../templates.in:1002 msgid \Don't touch keymap\ will prevent the configuration system from overwriting the keymap you have in /etc/console. Select this if you want to keep a keymap you obtained through other means. Please remember to install new keymaps with install-keymap(8) if you select this choice. msgstr \Rör ej tangentuppsättning\ förhindrar konfigurationssystemet från att skriva över den tangentuppsättning som du har i /etc/console. Välj detta om du vill behålla en tangentuppsättning som du har fått tag i på något annat sätt. Kom ihåg att installera nya tangentuppsättningar med install-keymap(8) om du väljer det här valet. #. Type: select #. Description #: ../templates.in:1002 msgid \Keep kernel keymap\ will prevent any keymap from being loaded next time your system boots. It will remove from /etc/console any keymap you may have already selected (it will be lost), but if you have already loaded a keymap, it cannot be changed back until you reboot. msgstr \Behåll kärnans tangentuppsättning\ förhindrar att någon tangenuppsättning laddas överhuvudtaget nästa gång ditt system startar. Det tar bort en eventuell tangentuppsättning från /etc/console som du redan kan ha valt (den kommer att gå förlorad), men om du redan har laddat en tangentuppsättning så kan den inte ändras tillbaka förrän du startar om. #. Type: select #. Description #: ../templates.in:1002 msgid \Select keymap from full list\ offers a full listing of all predefined keymaps. You want this, if you use an USB keyboard from a different computer architecture or if you use an adapter to use such a keyboard. msgstr \Välj tangentuppsättning från komplett lista\ erbjuder en komplett lista med alla fördefinierade tangentuppsättningar. Välj detta om du
Re: Please update debconf PO translation for the package console-common 0.7.62
You are noted as the last translator of the Debian configuration translation for the console-common package. Hmm, sorry. It seems that some translators of console-common did set debian-boot as the Language-Team for their translations. Hence, when I sent update notifications to them, CC'ing the language team, a few mails have been sent to -boot. Sorry for those of you who have slow links. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: Debianinstaller/contrib
Title: RE: Debianinstaller/contrib hi Rajasekaran, At what stage your team has finished it or developing in which stage . what help is your team is looking for. Can you please explain . Deepak Tripathi .---. Open Source Developer / \ [EMAIL PROTECTED]@./ /`\_/`\ .''`. // _ \\ : :' : | \ )|_ `. `'` /`\_` _/ \ `- \__/'---'\__/ Debian GNU/Linux -Original Message- From: Rajasekaran J. [mailto:[EMAIL PROTECTED]] Sent: Mon 9/18/2006 4:30 PM To: debian-boot@lists.debian.org Subject: Debianinstaller/contrib Hi All, I am Rajasekaran J.I am using debian for the past two years and we came out with debian based disto called as BOSS(Bharat Operating System Solutions).I would like to participate the development activity of DebianInstaller. Thanks Regards, Rajasekaran J -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. www.aztecsoft.com
Bug#276067: marked as done (Please base the keyboard layout choice on country rather than language or language/country settings)
reopen 276067 thanks From console-data settings, an Icelandic keyboard should now be chosen when language is English and country is Iceland. Untrue..:-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#276067: marked as done (Please base the keyboard layout choice on country rather than language or language/country settings)
Processing commands for [EMAIL PROTECTED]: reopen 276067 Bug#276067: Please base the keyboard layout choice on country rather than language or language/country settings Bug#269878: Please default to Icelandic keyboard when choosing Iceland as country even if language is English Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#381979: keymap not changed in g-i after selection in kbd-chooser
On Monday 18 September 2006 23:45, Attilio Fiandrotti wrote: I did not test this by myself, but davide did it and the patch proved to work (Davide, any hint about how to reproduce a correct keymap change in the g-i ?). Davide? I don't see anything strange in a text console behaviour's not being affected by DFB. VT1 is _not_ the text console. VT2 is and that is localized correctly. VT1 is the console where DFB messages end up... BTW, how is keymap set by the d-i? AFAIK the kernel keymap is changed. pgpLLqxMcCGgU.pgp Description: PGP signature
Bug#388085: AW: Bug#388085: installation on Apple G5
Hi, I can not give you the partition table or map, because I reinstalled everything again. I now have installed MacOSX on a clean disk, the first 200 GB free HFS partition, then 40 GB for MacOSX HFS+ case-sensitive with journaling feature. After the MacOS X installation went fine, I installed Debian again, now with the latest Netinstall ISO-image for etch. Still the Partition Tool in the Debian Installer, did not recognize any of the existing Mac Partition Map. I switched to a shell and used mac-fdisk to create a Apple Bootstrap partition, a Linux Swap partition and a Linux partition for a big ext3 root filesystem. After that I could install the base system. The installation of the bootloader (yaboot) did not succeed. After I rebooted the Mac and booted again into the Rescue-System I could install yaboot. Now the dual boot is working fine. I think the Kernel does not reread the partition map after I added the Linux partitions. Are you having automatically support for Mac Partition Maps in the Debian Installer? bye Waldemar -Ursprüngliche Nachricht- Von: Sven Luther [mailto:[EMAIL PROTECTED] Gesendet: Montag, 18. September 2006 17:14 An: EXTERNAL Brodkorb Waldemar (Tarent; AA-DG/ESW1); [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Betreff: Re: Bug#388085: installation on Apple G5 On Mon, Sep 18, 2006 at 03:43:06PM +0200, EXTERNAL Brodkorb Waldemar (Tarent; AA-DG/ESW1) wrote: Package: installation-reports Boot method: mini.iso Image version: 2006-08-07 Date: 2006-09-18 Machine: Apple PowerMac G5 Processor: ppc64 Memory: 2 GB Partitions: df -Tl will do; the raw partition table is preferred Output of lspci and lspci -n: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[x] Configure network HW: [x] Config network: [x] Detect CD: [x] Load installer modules: [x] Detect hard drives: [x] Partition hard drives: [E] Create file systems:[x] Mount partitions: [x] Install base system:[x] Install boot loader:[x] Reboot: [x] Comments/Problems: The partition manager did not recognized my MacOS X partition table. I installed MacOS X on a 20 GB partition before I started the Debian installation. So a dual-boot is not supported at the moment, if you already have MacOS X installed. hi, Well, it used to work, so i, as well as the parted team i guess, really would like to know more about your mac-os-x parttition table, what mac-os-x version you are using, and how you did partition your disk. If you could provide us with a dump of the partition table part of the disk (dd if=/dev/hda of=/tmp/file bs=1K count=1024 for example), so we can look at it and investigate would be nice. Friendly, Sven Luther
Re: [D-I] mass kernel udeb update and preparations for RC1
On Sun, Sep 17, 2006 at 02:28:06PM +0200, Frans Pop wrote: * powerpc: oldworld boot problems with recent kernels Both will be fixed in 2.6.18, and are already in the 2.6.18-rc7 snapshots since today. We don't have 2.6.18 based d-i to confirm this, but i will do a custom build over the week to confirm this. I don't particularly feel like backporting those fixes to 2.6.17, especially as the etch kernel target is 2.6.18, but others may volunteer to do it, or i may do it if i find some time. Friendlly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#388159: missing lspci on a fresh install
reassign 388159 installation-reports retitle 388159 installation-reports: Please depend on lspci severity wishlist thanks Rick Thomas wrote: Package: base Please do not file bugs against the base pseudo-package. It is there just as a catch-all-I-dunno-where-to-file-this-report for users that can't really tell what package is giving them problems. All the bug reports here get reassigned to the right package. On Monday 18 September 2006 21:49, Rick Thomas wrote: On Sep 18, 2006, at 10:17 AM, De Leeuw Guy wrote: Frans Pop a écrit : The d-i team is not responsible for what is part of the base system and what is not. Then who is? Where should I send a bug report? What is your rationale for including it? lspci is hardly an essential tool (although it _is_ highly useful of course, but so are a couple of 100 other tools that are not included)... Correct place to file a bug report would be the pseudo package base, but I strongly suggest you do not file a bug for this. Wrong, see above. Since the install-report template requests the output of lspci, I would think you -- of all folks -- would want it as part of the base system. Imho, installation-reports should depend on, or recommend lspci if it requires its output for the report. Thanks -- ·''`. If I can't dance to it, it's not my revolution : :' :-- Emma Goldman `. `' Proudly running Debian GNU/Linux (unstable) `- www.amayita.com www.malapecora.com www.chicasduras.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#388159: missing lspci on a fresh install
Processing commands for [EMAIL PROTECTED]: reassign 388159 installation-reports Bug#388159: missing lspci on a fresh install Bug reassigned from package `base' to `installation-reports'. retitle 388159 installation-reports: Please depend on lspci Bug#388159: missing lspci on a fresh install Changed Bug title. severity wishlist Unknown command or malformed arguments to command. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#388159: missing lspci on a fresh install
On Tue, Sep 19, 2006 at 11:25:21AM +0200, Amaya wrote: reassign 388159 installation-reports retitle 388159 installation-reports: Please depend on lspci severity wishlist thanks Hi Amaya, ... Rick Thomas wrote: Package: base Please do not file bugs against the base pseudo-package. It is there just as a catch-all-I-dunno-where-to-file-this-report for users that can't really tell what package is giving them problems. All the bug reports here get reassigned to the right package. it was Frans who suggested this, and doing ping-pong of bug reporters is hardly user friendly, especially given the rather crude kind of response Guy and Rick are getting. Since the install-report template requests the output of lspci, I would think you -- of all folks -- would want it as part of the base system. Imho, installation-reports should depend on, or recommend lspci if it requires its output for the report. Installation-reports is always installed, right ? or would there be need of another bug report against another yet-to-be-determined package for inclusion of lspci in either the base system or the server task ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Processed: Re: Bug#388159: missing lspci on a fresh install
severity 388159 wishlist stop On Tue, Sep 19, 2006, Debian Bug Tracking System wrote: severity wishlist Unknown command or malformed arguments to command. -- Loïc Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Processed: Re: Bug#388159: missing lspci on a fresh install
Processing commands for [EMAIL PROTECTED]: severity 388159 wishlist Bug#388159: installation-reports: Please depend on lspci Severity set to `wishlist' from `normal' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#388159: missing lspci on a fresh install
I feel my previous email could be taken as harsh on my side, which it was not menat to be at all. I apologize to the reporter if he feels this way. Sven Luther wrote: it was Frans who suggested this, and doing ping-pong of bug reporters is hardly user friendly I am not doing ping pong of anything. This bug was incorrectly assigned to the base pseudo-package, which I co-maintain with Dato, so it is my duty to reassign it to where I think it belongs. Of course I could be wrong and it might be reassigned again to a more suited package and I see no problem with it. especially given the rather crude kind of response Guy and Rick are getting. Despite whatever empathy I might feel or not about this issue, I don't see how letting this bug rot in the wrong place can be more polite, useful or fulfilling for the bug reporter. Regards... and Happy and productive discussion/hacking to all involved! (Please keep me out this loop) -- ·''`. If I can't dance to it, it's not my revolution : :' :-- Emma Goldman `. `' Proudly running Debian GNU/Linux (unstable) `- www.amayita.com www.malapecora.com www.chicasduras.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388085: installation on Apple G5
reassign 388085 parted retitle 388085 parted/libparted has trouble with mac-os-x generated partition tables thanks On Tue, Sep 19, 2006 at 10:04:41AM +0200, EXTERNAL Brodkorb Waldemar (Tarent; AA-DG/ESW1) wrote: Hi, I can not give you the partition table or map, because I reinstalled everything again. I now have installed MacOSX on a clean disk, the first 200 GB free HFS partition, then 40 GB for MacOSX HFS+ case-sensitive with journaling feature. After the MacOS X installation went fine, I installed Debian again, now with the latest Netinstall ISO-image for etch. Still the Partition Tool in the Debian Installer, did not recognize any of the existing Mac Partition Map. Can i get a copy of the partition map of this one ? Or better yet, send it as bug report to the parted package ? What version of mac-os-x was this anyway ? I switched to a shell and used mac-fdisk to create a Apple Bootstrap partition, a Linux Swap partition and a Linux partition for a big ext3 root filesystem. After that I could install the base system. The installation of the bootloader (yaboot) did not succeed. What does the parted command line tool say you about your partition ? Can you run it, eventually do a print in it, and paste the output here ? After I rebooted the Mac and booted again into the Rescue-System I could install yaboot. Now the dual boot is working fine. I think the Kernel does not reread the partition map after I added the Linux partitions. It does if you ask it about it, parted and libparted based tools should handle this just fine. mac-fdisk is kinda obsoleted. Are you having automatically support for Mac Partition Maps in the Debian Installer? Sure. But then maybe apple created some bug or incompatiblity with their latest version of mac os x ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Processed: Re: Bug#388159: missing lspci on a fresh install
Processing commands for [EMAIL PROTECTED]: severity 388159 wishlist Bug#388159: installation-reports: Please depend on lspci Severity set to `wishlist' from `wishlist' stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#388085: installation on Apple G5
Processing commands for [EMAIL PROTECTED]: reassign 388085 parted Bug#388085: installation on Apple G5 Bug reassigned from package `installation-reports' to `parted'. retitle 388085 parted/libparted has trouble with mac-os-x generated partition tables Bug#388085: installation on Apple G5 Changed Bug title. 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]
Please, word diff for fuzzied translatable strings
When sending a .po file to be translated, please include word diff for strings that are marked fuzzy. It is much easier to unfuzzy when I can see what has changed in the english text. I can look the diff myself in version control, but it saves work if one developer sending the file makes the diff, compared to 40 translators doing the same work. -- Tapio Lehtonen [EMAIL PROTECTED] http://www.iki.fi/tapio.lehtonen signature.asc Description: Digital signature
Bug#388247: tasksel: strange entries in gnome-desktop
package: tasksel version: 2.54 severity: minor Hi! In the 'gnome-desktop' task in 'tasksel/tasks' there is a line which explains that gstreamer0.10-ffmpeg and gstreamer0.10-plugins-ugly should be installed to allow totem to play more formats. As far as I can see, totem-gstreamer is not installed. What gets installed is totem-mozilla, which depends on totem, which depends on either totem-xine or totem-gestreamer with the xine frontend being first choice. Same for the dependencies of the gnome-desktop-environment meta-package. With totem-xine installed there is no need for the additional gstreamer-plugins. If you want to install the totem-gstreamer package instead, it should be installed explicitely and not via the totem-mozilla or the gnome-desktop-environment dependencies. However, if totem-gstreamer is the one you want to install, there is no need for the libtheora0 package (allow totem to play theora files two lines above), as this is automatically installed via totem-gstreamer's dependencies on gstreamer0.10-base. For totem-xine it is not needed at all. Thanks for your efford! Nice Greetings, Fabian -- Fabian Greffrath Institut für Experimentalphysik I Ruhr-Universität Bochum D-44780 Bochum Raum: NB 2/28 Tel.: +49(234)32-27691 Fax: +49(234)32-14170 Email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please, word diff for fuzzied translatable strings
On Tuesday 19 September 2006 12:34, Tapio Lehtonen wrote: When sending a .po file to be translated, please include word diff for strings that are marked fuzzy. It is much easier to unfuzzy when I can see what has changed in the english text. Yes, that is a serious drawback of using PO files. I can look the diff myself in version control, but it saves work if one developer sending the file makes the diff, compared to 40 translators doing the same work. What does this have to do with debian-boot? We never _send_ po files to be translated... Also, a practical problem is that you cannot create one diff for all translations as you don't know if all translations were up-to-date before the call to translations. IMO this is something that can only be done reliably by individual translators themselves. Cheers, FJP pgpX8a2Le3sAg.pgp Description: PGP signature
Re: Bug#388159: missing lspci on a fresh install
On Tue, Sep 19, 2006 at 12:19:57PM +0200, Amaya wrote: I feel my previous email could be taken as harsh on my side, which it was not menat to be at all. I apologize to the reporter if he feels this way. :) Sven Luther wrote: it was Frans who suggested this, and doing ping-pong of bug reporters is hardly user friendly I am not doing ping pong of anything. This bug was incorrectly assigned to the base pseudo-package, which I co-maintain with Dato, so it is my duty to reassign it to where I think it belongs. It was done so on Frans suggestion. Of course I could be wrong and it might be reassigned again to a more suited package and I see no problem with it. I will let the installation-report maintainer comment, but as this is a d-i packages, ... Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Please, word diff for fuzzied translatable strings
On Tue, Sep 19, 2006 at 12:58:54PM +0200, Frans Pop wrote: On Tuesday 19 September 2006 12:34, Tapio Lehtonen wrote: When sending a .po file to be translated, please include word diff for strings that are marked fuzzy. It is much easier to unfuzzy when I can see what has changed in the english text. Yes, that is a serious drawback of using PO files. Maintainers can send a diff if they want to help translators, see #353611. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#385150: Tests with PPPoE connection
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gregory Colpart wrote: Hi, On Sat, Sep 16, 2006 at 03:01:43AM +0300, Eddy Petri??or wrote: It seems (thanks again Joey) that the problem is the db_stop line which, if commented out should kill the problem appear in both of these cases. Gregory knows this and said he will try to test with this change, but Abel should know about it, too. I would be really happy to find out that both issues disappeared when commenting out db_stop (it appears that I shouldn't do that in D-I). I use latest daily build for my PPPoE tests. Note that I use mv /usr/lib/pppd/2.4.4b1 /usr/lib/pppd/2.4.4 workaround for all my tests. I was expecting that :-) since no release of the ppp package has been made :-). Probably Marco is waiting for a fix for the issue we are talking about, too. * If I try without changing anything, I have red debconf screen. You have a full syslog here: http://gcolpart.evolix.net/debian/d-i/16092006/full-syslog.no-changes.failed * If I try with adding '|| true' in 'apt-install ppp' line, yeah, all is right !! After my PPPoE connection is up, I return to menu with no error. You have full syslog with -e and -x for debug: http://gcolpart.evolix.net/debian/d-i/16092006/full-syslog.true-patch.success.set-e http://gcolpart.evolix.net/debian/d-i/16092006/full-syslog.true-patch.success.set-x [Writing this mail offline, so I'll have to check the logs later] AFAIUI, debconf should never be ordered to stop, while in D-I (Debian Installer) environment, so I expect that the || true code is just helping the debconf protocol to get out of a messy situation, in some rare cases. Also, the 'apt-install ppp code should not fail; failing would mean that the installed system would have issues since its ppp package would not install. Needless to say that you don't want that ;-) . I don't try to test without db_stop because it seems to me that my tests above are sufficient. I don't know exactly why, but it works fine with the last d-i. Please do test without the || true code attached to apt-install and with the db_stop line removed or commented out. I expect this to be the correct fix, and, as explained above, the || true being a lucky way out in some cases. If you have other tests with PPPoE/d-i, say me. I know that last time I tested the package, the installation on the target system was not good enough and after the first reboot, although the ppp package was installed, the pppoe connection was not working. I _know_ this may be impossible for you to test, since you might not have a spare machine or a spare partition, so I won't mind if you can't do it. But, please, tell me if you can't do this test. Thanks a lot for your help. - -- Regards, EddyP = Imagination is more important than knowledge A.Einstein -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFD9VPY8Chqv3NRNoRAghXAKCwGR48+WP5lPVg/q28WaxDQHTQowCbBxUj SnzjblXVntwOizuQDoYFXWE= =nL8M -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub2 on powerpc
On Tue, Sep 19, 2006 at 07:47:27AM +0200, Sven Luther wrote: Ah, good. Btw, anyone tried loading a 64bit kernel from 32bit grub2? If it works, we could add ppc64 to the list (using biarch). As said, a year or two ago, i used grub2 to boot a dual power3 box, which is a powerpc 64bit machine. It worked just fine, especially since the default method for openfirmware bootloaders is to run as 32bit. I am not sure it makes sense to run them in 64bit mode, or even if it is supposed to work. All the documentation i have seen on this topic, even from IBM and others, show that the bootloader should be run in 32bit mode, and the kernel is launched from 32bit, and then sets up the 64bit stuff, so there should be no major difference with regard to grub2. Notice that here ppc64 is confusing, you probably speak about the one-man-show pure-64 thingy from Andreas Jochens, and not from the kernel arch ppc64. Notice that this is not and will never be an officially supported arch by debian, and despite me asking, Andreas Jochens has shown absolutely no interest to cooperate with the biarch or multi-arch effort, even though this won't happen anymore for etch anyway. Ah I see. Well, whatever it turns out, adding any-ppc64 doesn't harm (added). -- Robert Millan My spam trap is [EMAIL PROTECTED] Note: this address is only intended for spam harvesters. Writing to it will get you added to my black list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-free firmware and d-i
On Mon, Sep 18, 2006 at 12:36:00PM -0400, Nathanael Nerode wrote: Wouter Verhelst wrote: Can people please have a look and comment? I'd like to avoid some specific GR by making whatever is going to be voted upon moot ;-) We should have a way of doing the same thing, only with a custom network source. Probably not a hard thing to do. Otherwise, looks fine. But you may be reinventing bits of d-i. Yes; I noticed that too, in the mean time. Perhaps the correct structure is this: after choosing Customization modules, the user gets a menu of possible places to get them from (CD, USB, floppy, net, etc.). Chickening out of the hard work, we could just limit this list to CD-ROM, floppy, or network. The list of retrievers is limited to that anyway. Main problem is going to be the fact that currently, every installation image contains just one or two retrievers, not more. As a result, you can't download modules from the network when doing a CD-ROM based install, nor can you install modules from CD-ROM when doing a network-based install. Personally, this is the only feature that boot-floppies had while d-i doesn't that I would *love* to see again. It'd be great to be able to mount a CD or DVD-ROM in a machine, run apache off of it, copy the initrd images to a TFTP server, and install a bunch of machines over the network. With boot-floppies, this was possible; with d-i, it isn't. But I digress. [...] However, your implementation has the advantage of being simpler and less dependent on complicated setup of the customization discs. Not really. I always saw the CD-ROM stuff as intended for manufacturers who want to support Debian installations with their official driver CD-ROM; it's not unreasonable to request some more from them than from J. Random User who downloads udebs, puts them on a floppy, crosses his fingers, and boots the installer. Let's prove that Joey's six month estimate is wrong by doing it in less time even though we don't understand d-i very well. :-) I'm not so sure anymore his estimate is wrong; but, hey, let's try. -- Fun will now commence -- Seven Of Nine, Ashes to Ashes, stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: non-free firmware and d-i
On Mon, Sep 18, 2006 at 01:12:52PM -0400, Nathanael Nerode wrote: posted mailed Wouter Verhelst wrote: On Tue, Sep 05, 2006 at 11:35:25AM +0200, Wouter Verhelst wrote: Feedback is welcome. Since the only feedback I received thus far was Goswin von Brederlow saying he liked the idea, and since I didn't have much else to do today (other than wait for a supplier...), I went ahead and wrote it. It's committed to /people/wouter/customization-modules in d-i svn. It hasn't been tested at all yet (hence the commit to /people rather than /trunk), but this is mostly meant as a proof of concept anyway. I'm particularly not very happy about the way I currently look for usb storage devices (really all I'm doing is find any devices called /dev/fd*, or anything which is situated under /dev/cdrom/ or /dev/discs) Can people please have a look and comment? I'd like to avoid some specific GR by making whatever is going to be voted upon moot ;-) So I'm looking at how much of d-i is ready for multiple udeb sources Checking the net-retriver modules makes it clear that it ASSumes that there's only one source. I'm not entirely sure how to disabuse it of that assumption. I've been thinking that the best way here is to just nuke the configuration of the retriever before (or while) running customization-modules in some way. We'll be assuming that there is at least one way to get udebs onto the running debian-installer session; so the assumption that udebs have been downloaded isn't totally unfair, and there won't be a need to download additional modules at that point anymore. At least I think so; would have to do a test run to be sure. There's an easy way to do it: make a copy of net-retriever (customization-net-retriever) which instead of using the choose-mirror debconf information, prompts for a URL (and *doesn't* cache it, so that it can be run repeatedly with different URLs). I hate to duplicate code, but some of the net-retriever code (like the signature checking) should be torn out for this purpose anyway, so this is probably the way to go. Except that you'll inflate the initrd's by unnecessary amounts, which will make it harder to install Debian on RAM-limited machines. Clearly not the way to go. [...] The other way is to make the net-retriever program handle both alternatives, but if it's invoked from anna (as it should be), there's no way to tell it which version is wanted, so I think that's not workable. I think maybe I should just write this now. Be my guest ;-) If we use the more complicated anna-using version I suggested rather than your very straightforward code, then for local disk udeb loading: floppy-retriever seems good to go; it even invokes mountfloppy, and it doesn't need a Packages file or anything. Right. This should be the model for other 'customization' retrievers. cdrom-retriever looks pretty much good to go as well, but it doesn't similarly handle mounting and umounting, and it wants a fairly complicated setup on the CD. So maybe it should be forked. The complicated setup isn't too big a problem; the mounting and umounting can be done from customization-modules. As above, duplicating code is a bad idea for d-i, and I'm not convinced here. I believe the main customization menu is the place to handle ejecting and replacing the installation CD (which is clearly the Hard Part). Why? Mostly because it has to be done for all local media (CDs, floppy, USB stick, etc.), and will be done in approximately the same way for each one: check whether the device is mounted, umount if it is, do the work, remount it at the end. Right. (Frankly I'm unsure how the multiple installation CDs work now: I guess none but the first contain udebs.) Exactly. I'm not *quite* sure how to write that code (everything else mentioned here I think I could write right now pretty much). There is no usbstick-retriever or harddisk-retriever. There should be, for reasons beyond customization disks: it's a little silly that those options require an ISO image. :-) Couldn't agree more, but they're not as urgent as 'making sure it works'. These should be substantially simpler than cdrom-retriever or floppy-retriever. at least easier than cdrom-retriever, yeah. Hard to be simpler than a shell script that is 30-ish lines long. -- Fun will now commence -- Seven Of Nine, Ashes to Ashes, stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388281: installation-guide: grammatical mistake in the disks and filesystems is properly configured
Package: installation-guide Version: 20060726 Severity: minor Tags: patch In */partitioning/partition/ia64.xml: The commandpartman/command disk partitioner is the default partitioning tool for the installer. It manages the set of partitions -and their mount points to ensure that the disks and filesystems is +and their mount points to ensure that the disks and filesystems are properly configured for a successful installation. It actually uses the commandparted/command to do the on-disk partitioning. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-26-amd64-generic Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#387049: closed by Loic Minier [EMAIL PROTECTED] (Bug#387049: fixed in meta-gnome2 1:2.14.3.1)
Processing commands for [EMAIL PROTECTED]: clone 387049 -1 Bug#387049: Please add dependency on libgnomevfs2-bin to gnome-desktop-environment Bug 387049 cloned as bug 388290. reassign -1 tasksel Bug#388290: Please add dependency on libgnomevfs2-bin to gnome-desktop-environment Bug reassigned from package `gnome-desktop-environment' to `tasksel'. retitle -1 Please honor Recommends Bug#388290: Please add dependency on libgnomevfs2-bin to gnome-desktop-environment Changed Bug title. (By the way, that Bug is currently marked as done.) severity -1 normal Bug#388290: Please honor Recommends Severity set to `normal' from `normal' stop 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: powerpc d-i daily ISOs are back but broken. (was: one week out of date. )
On Fri, Sep 15, 2006 at 11:24:02AM +0200, Sven Luther wrote: someone who does the whole stuff, right ? It was an honest question, why do you respond so agressively ? Maybe because the question was asked in a rather aggressive tone? That's at least what it looked to IMNSHO. -- Fun will now commence -- Seven Of Nine, Ashes to Ashes, stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#387049: closed by Loic Minier [EMAIL PROTECTED] (Bug#387049: fixed in meta-gnome2 1:2.14.3.1)
Loïc Minier: On Tue, Sep 19, 2006, Per Olofsson wrote: I'm sorry, I really need a Depends. A Recommend: won't be picked up by tasksel. Grmpf. I think a Recommends is more appropriate, and I also think that this is a bug in tasksel. If you say so. I'll try to solve the problem in some other way then. Come to think of it, tasksel pulling in Recommends isn't such a bad idea. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388296: nobootloader: Pegasos firmware older than 1.2.99 need to substract 1 from partitions.
Package: nobootloader Version: 1.10 Severity: important Tags: d-i, patch Hi Colin, ... Can you please check the attached patch and commit it in both ubuntu and debian if it seems ok to you. I did some hand-testing only, not a full install with it, but it seems mostly ok. In any case, there is an error in the code using /sys over the old devfs code compared to the older devfs code. The devfs code always substract 1 from the partitions, while the /sys code never does it. The right behaviour is to check for the /proc/device-tree/openprom/firmware-version property, and discriminate depending on the version there. Only newer firmware versions have this property, and only those firmware more recent or equal to 1.2.99 have partitions starting at 1. older firmwares and those not having the property all start at 0. The attached patch implements this check, and brings both /sys and devfs partition numbering in sync again. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-powerpc Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388296: nobootloader: Pegasos firmware older than 1.2.99 need to substract 1 from partitions.
* Sven Luther [EMAIL PROTECTED] [2006-09-19 19:41]: Can you please check the attached patch and commit it in both ubuntu and debian if it seems ok to you. You forgot to attach the patch. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384771: debian-installer: works
Package: debian-installer Followup-For: Bug #384771 I retried the daily image of today, and now it works. Thanks, Jan -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388296: And with the patch this time.
Oh well, seems reportbug killed the patch when i got into mutt :/ Index: debian/postinst === --- debian/postinst (revision 40788) +++ debian/postinst (working copy) @@ -29,6 +29,25 @@ case `archdetect` in powerpc/chrp_pegasos) kernel=`ls /target/boot/vmlinuz-2.* | sed -e 's%/target/boot/%%'` + if [ -d /proc/device-tree/openprom/firmware-version ]; then + firmware_version=`cat /proc/device-tree/openprom/firmware-version` + fv1=host=$(echo $firmware_version | cut -d. -f1) + fv2=host=$(echo $firmware_version | cut -d. -f2) + fv3=host=$(echo $firmware_version | cut -d. -f3) + if [ $fv1 -eq 1 ] [ $fv2 -eq 2 ] [ $fv3 -ge 99 ]; then +partitions_start=1 + else if [ $fv1 -eq 1 ] [ $fv2 -ge 3 ]; then +partitions_start=1 + else if [ $fv1 -ge 2 ]; then +partitions_start=1 + else + partitions_start=0 + fi + fi + fi + else + partitions_start=0 + fi if [ -d /sys/block ] type udevinfo /dev/null 21; then bootfs_disk_syspath=$(dirname $(udevinfo -q path -n $bootfs_devfs)) @@ -55,14 +74,22 @@ lun=$(echo $bootfs_disk | cut -d: -f4) ;; esac - part=$(echo $bootfs_devfs | sed 's/[^0-9]*//') + if [ $partitions_start -eq 0 ]; then + part=$(( $(echo $bootfs_devfs | sed 's/[^0-9]*//') - 1 )) + else + part=$(echo $bootfs_devfs | sed 's/[^0-9]*//') + fi else kind=`echo $bootfs_devfs | sed -e 's%/dev/%%' -e 's%/host.*$%%'` host=`echo $bootfs_devfs | sed -e 's%^.*host%%' -e 's%/bus.*$%%'` bus=`echo $bootfs_devfs | sed -e 's%^.*bus%%' -e 's%/target.*$%%'` target=`echo $bootfs_devfs | sed -e 's%^.*target%%' -e 's%/lun.*$%%'` lun=`echo $bootfs_devfs | sed -e 's%^.*lun%%' -e 's%/part.*$%%'` - part=$((`echo $bootfs_devfs | sed -e 's%^.*part%%'`-1)) + if [ $partitions_start -eq 0 ]; then + part=$((s $(`echo $bootfs_devfs | sed -e 's%^.*part%%') -1)) + else + part=$(echo $bootfs_devfs | sed -e 's%^.*part%%') + fi fi # We don't know how to map non ide or scsi disks @@ -76,7 +103,7 @@ ;; esac - # map theidevice to the OF aliases from /proc/device-tree/aliases. + # map the device to the OF aliases from /proc/device-tree/aliases. if [ -d /proc/device-tree/aliases ]; then for alias in `ls /proc/device-tree/aliases/*`; do device=`grep disk $alias | sed -e '[EMAIL PROTECTED]/]*/%/%g'` Index: debian/changelog === --- debian/changelog(revision 40788) +++ debian/changelog(working copy) @@ -1,9 +1,14 @@ nobootloader (1.11) UNRELEASED; urgency=low + [ Colin Watson ] * Mark Open Firmware commands as untranslatable. - -- Colin Watson [EMAIL PROTECTED] Wed, 30 Aug 2006 10:12:20 +0100 + [ Sven Luther ] + * Check the pegasos firmware for versions older than 1.2.99, and substract +one from the partition number since those start counting partitions at 0. + -- Sven Luther [EMAIL PROTECTED] Tue, 19 Sep 2006 19:30:56 +0200 + nobootloader (1.10) unstable; urgency=low * If /sys/block and udevinfo are available, use them instead of devfs
Re: [D-I] mass kernel udeb update and preparations for RC1
On Sunday 17 September 2006 14:28, Frans Pop wrote: * partman-auto using LVM and crypto partman-auto-lvm now has been available for some time, but is still not available for all arches. LVM support is a prerequisite for partman-auto-crypto support which will be uploaded soon. Note: swap on LVM should be possible now and is even required for partman-auto-crypto. I have tested and activated LVM support in autopartitioning for hppa. Cheers, FJP P.S. I used to see occasional freezes when additional installer components were loaded if I booted my hppa with the 64-bit kernel. Today with 2.6.17 I could not reproduce this in 3 installation tests. I'll keep trying though ;-) pgp2mc5O8VKSi.pgp Description: PGP signature
Re: non-free firmware and d-i
Wouter Verhelst wrote: I've been thinking that the best way here is to just nuke the configuration of the retriever before (or while) running customization-modules in some way. We'll be assuming that there is at least one way to get udebs onto the running debian-installer session; so the assumption that udebs have been downloaded isn't totally unfair, and there won't be a need to download additional modules at that point anymore. At least I think so; would have to do a test run to be sure. d-i needs to be able to load udebs from the primary source at multiple points during the installation. -- see shy jo signature.asc Description: Digital signature
Processed: Reassign
Processing commands for [EMAIL PROTECTED]: reassign 388159 installation-report Bug#388159: installation-reports: Please depend on lspci Bug reassigned from package `installation-reports' to `installation-report'. 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: Processed: Re: Bug#387049: closed by Loic Minier [EMAIL PROTECTED] (Bug#387049: fixed in meta-gnome2 1:2.14.3.1)
FYI, it's not a bug in tasksel that it ignores recommends. If on one glorious day, it's possible to install even with recommands and get a sane system without mounds of unnecessary stuff being pulled in by recommends and/or recommends chains, I will reconsider this position. Not until then though. -- see shy jo signature.asc Description: Digital signature
Re: Processed: Re: Bug#387049: closed by Loic Minier [EMAIL PROTECTED] (Bug#387049: fixed in meta-gnome2 1:2.14.3.1)
On Tue, Sep 19, 2006, Joey Hess wrote: FYI, it's not a bug in tasksel that it ignores recommends. Well, let's call it a bug *and* a workaround at the same time then. :) The situation of Recommends in the archive is not going to improve if we ignore them everywhere though. If on one glorious day, it's possible to install even with recommands and get a sane system without mounds of unnecessary stuff being pulled in by recommends and/or recommends chains, I will reconsider this position. Not until then though. blahh -- Loïc Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#387049: closed by Loic Minier [EMAIL PROTECTED] (Bug#387049: fixed in meta-gnome2 1:2.14.3.1)
Loïc Minier: On Tue, Sep 19, 2006, Per Olofsson wrote: Grmpf. I think a Recommends is more appropriate, and I also think that this is a bug in tasksel. If you say so. I'll try to solve the problem in some other way then. I've cloned the bug already; meaning I still consider the original bug a bug. I will change meta-gnome2 at your request again, I simply forgot about tasksel not following Recommends. Ah, I see. Great! Come to think of it, tasksel pulling in Recommends isn't such a bad idea. This might be partly by design, as Recommends are a bit too common in the archive at some places. Ubuntu started the process of fixing some and the apt version which will enforce this is in Debian's experimental as well, so I suppose at some point the tasksel maintainer will see a lot of people breathing behind his neck. :) Yeah, well that is a welcome change. As you say, Recommends: are too common currently, and that is a bug which should be fixed. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#388296: nobootloader: Pegasos firmware older than 1.2.99 need to substract 1 from partitions.
Sven Luther wrote: Package: nobootloader Version: 1.10 Severity: important Tags: d-i, patch .. The right behaviour is to check for the /proc/device-tree/openprom/firmware-version property, and discriminate depending on the version there. What about the Pegasos 1? I am running a hand configured Linux peg 2.6.15.7 kernel, which lists under /proc/device-tree/openprom/ only the following files bplan-copyright built-on client-services CodeGen-copyright linux,phandle model name relative-addressing SmartFirmware-version [EMAIL PROTECTED]:~$ ls /proc/device-tree/openprom/SmartFirmware-version A cat /proc/device-tree/openprom/SmartFirmware-version 1.1 Best regards Niklaus Giger -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Processed: Re: Bug#387049: closed by Loic Minier [EMAIL PROTECTED] (Bug#387049: fixed in meta-gnome2 1:2.14.3.1)
Loïc Minier wrote: The situation of Recommends in the archive is not going to improve if we ignore them everywhere though. We're not ignoring them everywhere. Aptitude installs recommends by default for newly installed packages after the initial install, which does provide some exposure to catch bad recommends. -- see shy jo signature.asc Description: Digital signature
Processed: setting package to tasksel tasksel-data, tagging 386335, tagging 388247
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.21 package tasksel tasksel-data Ignoring bugs not assigned to: tasksel tasksel-data tags 386335 + pending Bug#386335: xdg-utils in desktop task There were no tags set. Tags added: pending tags 388247 + pending Bug#388247: tasksel: strange entries in gnome-desktop There were no tags set. Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: missing lspci on a fresh install
On Mon, Sep 18, 2006 at 02:44:40PM +0100, David Goodenough wrote: On Monday 18 September 2006 14:13, Frans Pop wrote: On Monday 18 September 2006 14:56, De Leeuw Guy wrote: I just finish a new net-install with the daily builds 20060918 of testing. I have a strange bug with the network after the first reboot. lo become eth0 eth0 become eth1_temp and I cannot access the network. Known issue. Upgrade to udev from unstable. I try to start lspci to identify my network card but this tools missing. Then install pci-utils... That does not help if you are trying to identify the network card in order to set up the install and you wanting to do a network install. The only alternative here is to reboot using Knoppix or the like and see what it finds, then restart the Debian install. You can also look at /sys or /proc/pci and /proc/bus/pci directly, it has all the info :) Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#384771: marked as done (installation report d-i amd64 20060826)
Your message dated Tue, 19 Sep 2006 21:01:21 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#384771: debian-installer: works 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: Network-install CD Image version: Saturday August 26th, from the official site. Date: saturday august 26th, 15:00 GMT+1 Machine: AMD 64bit machine, using Abit KN9-SLI motherboard and Nvidia GPU Processor: AMD 64X2 AM2 4200+ cpu Memory: 2gb Partitions: n/a Output of lspci and lspci -n: Not really able to provide, the system never got it's network up and running. Network part is: (typed by hand) 00:08.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2) 00:09.0 Bridge: nVidia Corporation MCP55 Ethernet (rev a2) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[O] Configure network HW: [E] Config network: [E] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: The network is detected by the forcedeth kernel module, but no traffic goes over it. DHCP didn't work, setting static IP does work, but I can't ping the IP (and I can't get to the debian mirrors to complete my installation). The module does detect link states, so that part is ok. (On a site comment: using the ubuntu installation CD (which uses a more recent kernel, 2.6.17.something) does work. So maybe the module needs upgrading?) Jan ---End Message--- ---BeginMessage--- On Tuesday 19 September 2006 20:27, Jan De Luyck wrote: I retried the daily image of today, and now it works. Thanks for following up. Closing the report. Cheers, FJP ---End Message---
Re: Processed: Re: Bug#387049: closed by Loic Minier [EMAIL PROTECTED] (Bug#387049: fixed in meta-gnome2 1:2.14.3.1)
On Tue, Sep 19, 2006, Joey Hess wrote: We're not ignoring them everywhere. Aptitude installs recommends by default for newly installed packages after the initial install, which does provide some exposure to catch bad recommends. I was pointing out that avoiding the problem was not going to solve it. But yes, aptitude is correct in its handling of Recommends (except perhaps when Recommends are added to packages). I think already mentionned the apt update which should go a long way in helping us fix the situation. I recall the mention of tasksel not honoring Recommends back when I added the rhythmbox - avahi Recommends which resulted in lots of flames from people not agreeing on what should be installed by default (me included). In the end, the package doesn't get installed currently despite this being the wish of the package maintainer. I'm not sure this is a good situation, and I'm not too happy that I can't enforce my decision. I certainly don't want to add a Depends just to make my point, as it would be technically incorrect, yet I really wish my Recommends would be honored (or debated in the tech-ctte). -- Loïc Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
how to control/override dev assigment 3ware and USB
I am trying to install using Debian etch b3 daily snapshot for 2006.09.19. The system is a Chaintech MB with Intel 875 chipset. There is a 3ware 8006 (SATA, 2port) and a USB card reader installed. The CD is attached to secondary IDE on-board controller. I have now disabled the primary IDE on-board controller and the on-board SATA controller. The installation goes fine. The 3ware is found as /dev/sde. Using the b3 installer, grub failed to install but with the daily snapshot grub installed fine. Upon reboot, grub is found, the 3ware is found as /dev/sde, a couple of things accessing the 3ware go fine, then the USB card-reader is found and it assigns devices /dev/sdb, /dev/sdc, /dev/sdd, and then stops /dev/sde, where upon the boot freezes. I need to some how overcome this conflict. I booted a Knoppix LiveCD to try fixing the system, or at least get device details but the logs are empty. Is this a known problem? Does any one have suggestions on how best to fix this? Thanks R.Parr, RHCE, Temporal Arts -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388296: nobootloader: Pegasos firmware older than 1.2.99 need to substract 1 from partitions.
tags 388296 pending thanks On Tue, Sep 19, 2006 at 07:41:45PM +0200, Sven Luther wrote: Can you please check the attached patch and commit it in both ubuntu and debian if it seems ok to you. I did some hand-testing only, not a full install with it, but it seems mostly ok. In any case, there is an error in the code using /sys over the old devfs code compared to the older devfs code. The devfs code always substract 1 from the partitions, while the /sys code never does it. Thanks, good catch; I must have simply missed that -1. I've committed a somewhat modified version of your patch. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: nobootloader: Pegasos firmware older than 1.2.99 need to substract 1 from partitions.
Processing commands for [EMAIL PROTECTED]: tags 388296 pending Bug#388296: nobootloader: Pegasos firmware older than 1.2.99 need to substract 1 from partitions. Tags were: d-i 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#388320: debian-installer: rescue mode: show software raid devices.
Package: debian-installer Version: 20060806 Severity: wishlist Hi, I've just tried to the etch beta3 image as rescue CD. Everything seems to be working properly. I'm using a software raid, and it's properly detecting that. At a certain point, it asks what I want to mount as my root partition. It's showing me a list of all partitions on all the dists. It would be useful if it also showed my raid device. Mounting /dev/md/0 manually worked without problems. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#387897: Installation report
On Sun, Sep 17, 2006 at 01:54:49PM +0200, Max Vozeler wrote: I will try to reproduce this problem. David, maybe you have an idea what might have gone wrong? I've tried to reproduce it but so far I've been unsuccessful...makes it kinda hard to debug :/ -- David Härdeman
RE: Debianinstaller/contrib
I think he's trying to help the team of the debian installer, not looking for help on his proyect. P.S: sorry for my bad english. On Tue, 2006-09-19 at 13:03 +0530, Deepak Kumar Tripathi wrote: hi Rajasekaran, At what stage your team has finished it or developing in which stage . what help is your team is looking for. Can you please explain . Deepak Tripathi .---. Open Source Developer / \ [EMAIL PROTECTED]@./ /`\_/`\ .''`. // _ \\ : :' :| \ )|_ `. `'`/`\_` _/ \ `- \__/'---'\__/ Debian GNU/Linux -Original Message- From: Rajasekaran J. [mailto:[EMAIL PROTECTED] Sent: Mon 9/18/2006 4:30 PM To: debian-boot@lists.debian.org Subject: Debianinstaller/contrib Hi All, I am Rajasekaran J.I am using debian for the past two years and we came out with debian based disto called as BOSS(Bharat Operating System Solutions).I would like to participate the development activity of DebianInstaller. Thanks Regards, Rajasekaran J -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] The information contained in, or attached to, this e-mail, contains confidential information and is intended solely for the use of the individual or entity to whom they are addressed and is subject to legal privilege. If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager. Please do not copy it for any purpose, or disclose its contents to any other person. The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email. www.aztecsoft.com -- aka nxvl key fingerprint: E140 4CC7 5E3C B6B4 DCA7 F6FD D22E 2FB4 A9BA 6877 gpg --keyserver subkeys.pgp.net --recv-keys A9BA6877 Yo uso Software Libre y tu? signature.asc Description: This is a digitally signed message part
Re: Bug#388296: nobootloader: Pegasos firmware older than 1.2.99 need to substract 1 from partitions.
On Tue, Sep 19, 2006 at 08:46:09PM +0200, Niklaus Giger wrote: Sven Luther wrote: Package: nobootloader Version: 1.10 Severity: important Tags: d-i, patch .. The right behaviour is to check for the /proc/device-tree/openprom/firmware-version property, and discriminate depending on the version there. What about the Pegasos 1? I am running a hand configured Linux peg 2.6.15.7 kernel, which lists under /proc/device-tree/openprom/ only the following files bplan-copyright built-on client-services CodeGen-copyright linux,phandle model name relative-addressing SmartFirmware-version [EMAIL PROTECTED]:~$ ls /proc/device-tree/openprom/SmartFirmware-version A cat /proc/device-tree/openprom/SmartFirmware-version 1.1 Best regards Sure, the pegasos 1 firmware behaves like the pegasos 2 1.2 firmware in this regard, the code is still correct. firmware 1.2.99 and 1.3 and beyond on pegasos 1 will have partitions starting at 1, like the pegasos2. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#388323: installation-report: Installation report + suggestion regarding XFS
Package: installation-reports Version: 2.17 Severity: normal -- Package-specific info: Boot method: CD Image version: etch beta 3 (http://cdimage.debian.org/cdimage/etch_di_beta3/i386/iso-cd/debian-testing-i386-netinst.iso) Date: September 17, 2006, some time in the morning Machine: Compaq Presario 7360 Partitions: df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/hdb1 ext3 580364157788393096 29% / tmpfstmpfs 61876 4 61872 1% /dev/shm /dev/mapper/cheops_vg-usr_lv xfs 8181760 2442712 5739048 30% /usr /dev/mapper/cheops_vg-home_lv xfs 5109760 1746012 3363748 35% /home /dev/mapper/cheops_vg-var_lv xfs 4085760566236 3519524 14% /var tmpfstmpfs 1024084 10156 1% /dev 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:[O] Overall install:[O] Comments/Problems: Install went fine with no serious problems. One thing I had to do manually, however, was to re-create the XFS filesystems. This machine is my firewall, and naturally selinux is useful for a machine in that position. Unfortunately, the default inode size for mkfs.xfs is 256 bytes, which is not optimum for selinux (see http://www.redhat.com/magazine/001nov04/features/selinux/ for one take on the situation, but there are others: try googling for selinux xfs). After the installer created the partitions and filesystems, I went into the second console with alt-f2 and re-created the three XFS filesystems by unmounting each, running mkfs.xfs -f -i size=512 /dev/hdX and remounting them. All worked fine after that. Since selinux comes with the kernel, I'd suggest that you make the XFS inode size 512 bytes by default, or at least provide for the user supplying options to mkfs. (I suppose I could have done this myself if I'd used expert mode, but I didn't think of it). There doesn't seem to be any major disadvantage to increasing the inode size, but I must admit I haven't looked very hard. I do have one other suggestion, unrelated to the actual installation: I came across the request to submit an installation report on http://d-i.alioth.debian.org/manual/en.i386/ch05s03.html#submit-bug, in section 5.3.6. This section, however, doesn't seem to be too sure whether the bug should be filed against the package installation-report or installation-reports. It would probably save some confusion if the web page were more consistent. I tried first to file under installation-reports (plural), but that resulted in a crash in reportbug. I'll file a separate bug report. .Ron -- 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. Once you have filled out this report, mail it to [EMAIL PROTECTED] == Installer hardware-summary: == (Note: logs for this installation are unavailable, since this machine is a replacement. I've copied over all the files from the original box, and the installation logs have been overwritten/lost. Sorry about that. Here, however, is the output of 'report-hw', which may be of some use.) umame -a: Linux cheops 2.6.17.13-cheops-3 #1 Mon Sep 18 21:51:16 EDT 2006 i586 GNU/Linux lspci -v -t: -[:00]-+-00.0 VIA Technologies, Inc. VT8501 [Apollo MVP4] lspci -v -t:+-01.0-[:01]00.0 Trident Microsystems CyberBlade/i7 lspci -v -t:+-07.0 VIA Technologies, Inc. VT82C686 [Apollo Super South] lspci -v -t:+-07.1 VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE lspci -v -t:+-07.2 VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller lspci -v -t:+-07.3 VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller lspci -v -t:+-07.4 VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] lspci -v -t:+-09.0 Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] lspci -v -t:+-0a.0 D-Link System Inc RTL8139 Ethernet lspci -v -t:\-0d.0 ESS Technology ES1988 Allegro-1 lspci -n: 00:00.0 0600: 1106:0501 (rev 04) lspci -n: 00:01.0 0604: 1106:8501 lspci -n: 00:07.0 0601: 1106:0686 (rev 21) lspci -n: 00:07.1 0101: 1106:0571 (rev 10) lspci -n: 00:07.2 0c03: 1106:3038 (rev 10) lspci -n: 00:07.3 0c03: 1106:3038 (rev 10) lspci -n: 00:07.4 0680: 1106:3057 (rev 30) lspci -n: 00:09.0 0200: 1011:0014 (rev 21) lspci -n: 00:0a.0 0200: 1186:1300 (rev 10) lspci -n: 00:0d.0
Re: Bug#387049: closed by Loic Minier [EMAIL PROTECTED] (Bug#387049: fixed in meta-gnome2 1:2.14.3.1)
clone 387049 -1 reassign -1 tasksel retitle -1 Please honor Recommends severity -1 normal stop On Tue, Sep 19, 2006, Per Olofsson wrote: I'm sorry, I really need a Depends. A Recommend: won't be picked up by tasksel. Grmpf. I think a Recommends is more appropriate, and I also think that this is a bug in tasksel. -- Loïc Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Returned mail: see transcript for details
From: [EMAIL PROTECTED] Subject: Automaticka odpoved na Vas mail Vazeny zakaznik, Vas e-mail sme prijali a v tomto momente pracujeme na Vasej poziadavke, ktora bude vyriesena hned ako to bude mozne. S pozdravom team PPI-ETC Slovakia Original Message -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#387049: closed by Loic Minier [EMAIL PROTECTED] (Bug#387049: fixed in meta-gnome2 1:2.14.3.1)
On Tue, Sep 19, 2006, Per Olofsson wrote: Grmpf. I think a Recommends is more appropriate, and I also think that this is a bug in tasksel. If you say so. I'll try to solve the problem in some other way then. I've cloned the bug already; meaning I still consider the original bug a bug. I will change meta-gnome2 at your request again, I simply forgot about tasksel not following Recommends. Come to think of it, tasksel pulling in Recommends isn't such a bad idea. This might be partly by design, as Recommends are a bit too common in the archive at some places. Ubuntu started the process of fixing some and the apt version which will enforce this is in Debian's experimental as well, so I suppose at some point the tasksel maintainer will see a lot of people breathing behind his neck. :) -- Loïc Minier [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
