Re: Request for a DFB version of libcairo2
Hi Dave, On Sunday 28 May 2006 00:37, Dave Beckett wrote: I can try to build one in a few days time but I'm unsure how I could test it (in isolation) as I'm not familiar with udebs. If you can provide a udeb, we can at least check its contents and I'm sure that one of us will be able to test with it. If you need any help, feel free to ask here or on IRC (#d-boot on OFTC). Maybe the paper [1] for my Debconf workshop can help as well. Most important for us is that the libs in the udeb are built against only the directfb backend and not e.g. the X backend. We also need to be able to build other (library) udebs using regular library and -dev packages. I don't know if/how that will work if the udeb is compiled with different configuration options than the debs. Please do not upload to unstable without checking with us first. We will probably have to resolve a package name conflict with the package that currently provides the libcairo udeb. We'll also have to make sure that uploading the udeb does not break the daily builds of the graphical installer. Cheers and thanks, FJP [1] http://people.debian.org/~fjp/talks/debconf6/paper/ pgpwekLLROYdb.pgp Description: PGP signature
Bug#370631: failed Installation report for etch daily 2006/06/05 netinst on oldworld PowerPC Mac (beige g3)
Package: debian-installer Severity: Important This is a failed Installation report for etch daily 2006/06/05 on oldworld PowerPC Mac (beige g3) Installing from the Debian testing etch daily 2006/06/05 netinst image on a beige G3 oldworld PowerPC Mac, using the BootX bootloader from MacOS9... I get the following messages in white on a black screen (copied off the screen by hand -- sorry for any typos!): Total memory = 384MB; using 1024kB for hash table (at cff0) Linux version 2.6.16-1-powerpc (Debian 2.6.16-10) ([EMAIL PROTECTED]) (gcc version 4.0.3 (Debian 4.0.3-1)) #2 Tue Apr 25 15:16:02 CEST 2006 Found initrd at 0xc0342000:0xc0700e6e Found a Heathrow mac-io controller, ver:1, mapped at 0xfdf8 PowerMac motherboard: PowerMac G3 (Gossamer) setup_arch: bootmem Found Grackle (MPC106) PCI host bridge at 0x8000. Firmware bus number: 0-1 nvram: OF partition at 0x1800 nvram: XP partition at 0x1300 nvram: NR partition at 0x1400 arch: exit Top of RAM: 0x1800, Total RAM: 0x1800 Memory hole size: 0MB Built 1 zonelists Kernel command line: ramdisk_size=16384 video=ofonly irq: Found primary Apple PIC /pci/mac-io for 64 irqs irq: System has 64 possible interrupts PID hash table entries: 2048 (order: 11, 32768 bytes) GMT Delta read from XPRAM: -240 minutes, DST: on time_init: decrementer frequency = 16.708033 MHz time_init: processor frequency = 300.69 MHz MMU:exit Then it hangs. Any help will be appreciated! Thanks, Rick PS: Here's where I got the .iso from... = Index of //cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd Name Last modified Size Parent Directory - MD5SUMS 05-Jun-2006 02:17 143 debian-testing-powerpc-businesscard.iso 05-Jun-2006 02:15 58M debian-testing-powerpc-netinst.iso05-Jun-2006 02:17 167M Apache/2.0.53 (Debian GNU/Linux) Server at cdimage.debian.org Port 80 = the MD5SUMS file contains: b995eaf753314148b780b40f16ce1c45 debian-testing-powerpc- businesscard.iso aeba38af24d18e4c3aa81eec2f42cf90 debian-testing-powerpc-netinst.iso and these sums match the md5 checksum of the downloaded .iso files. PPS: Is this related to Bug#369760: Video problems installing etch on oldworld PowerPC Mac (beige G3)? If so, please don't assign it to a non-existent package again... On June 1, 2006 4:48:08 PM EDT, [EMAIL PROTECTED] (presumably at the behest of Joey Hess) wrote: Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 reassign 369760 linux Bug#369760: Video problems installing etch on oldworld PowerPC Mac (beige G3) Warning: Unknown package 'linux' Bug reassigned from package `debian-installer' to `linux'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370632: installation-guide
Package: installation-guide Version: Severity: minor Tags: l10n, patch random-bits.po _ po:129 auto: ⑤ Tag: para Original: ⌘0 To configure your locale settings to use a language other than English, install the locales support package and configure it: informalexamplescreen\n # apt-get install locales\n # dpkg-reconfigure locales\n /screen/informalexample NOTE: Apt must be configured beforehand by creating a sources.list and running apt-get update. Before using locales with character sets other than ASCII or latin1, please consult the appropriate localization HOWTO. I suggest: - please consult the appropriate localization HOWTO. + please consult the appropriate ulink url=\http://www.tldp.org/ HOWTO/HOWTO-INDEX/other-lang.html\localization HOWTO/ulink. because this is a useful list of such howtos, including the main Unicode one at the top, which applies to so many languages. Even if the user's language is not there, this page shows them what type of document is being described, so they can look for one elsewhere. I will try to get one done for Vietnamese, to add to this list at the LDP. _ Clytie Siddall (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
Bug#368711: marked as done (installation report, Sparc32 with Etch debian installer)
Your message dated Tue, 6 Jun 2006 08:01:48 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#368711: installation report, Sparc32 with Etch debian installer 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: netboot Image version: Etch beta2 from http://ftp.nl.debian.org/debian/dists/testing/main/installer-sparc/beta2/images/ Date: 2006-05-13 Machine: Sun Sparcstation 10 Processor: 2x SM51 Memory: 160M Partitions: 1=default small /boot, 2=most of drive as /, 4=143M swap Output of lspci and lspci -n: (not applicable to SS10, no PCI) Unit has TGX video. 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: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Create file systems:[O] Mount partitions: [O] Install base system:[E] Install boot loader:[E] Reboot: [E] Comments/Problems: The installer failed when it tried to download a kernel 2.4.27-3 sparc32 which did not exist in testing. I was operating with the default debconf priority which did not get set to low after the crash, so I was not given the choice to retry using a specific kernel. I entered a shell and manually installed a 2.4.27-2 kernel via apt-get. That succeeded. Exiting the shell and re-entering the installer menu, I could not get it to let me configure silo with the kernel I had just installed. It kept wanting to repartition the hard drive. I got a shell again and did a manual silo configure which didn't make a bootable system until I hand-edited a silo.conf file. I tried re-entering the installer by rebooting using priority=low. That got me lots of prompts, but the installer would not let me avoid repartitioning and reinstalling, which would have wasted another several hours doing exactly the same thing except for the last two steps - kernel and silo. I tried manually making /target and mounting / and /boot there, which let me eventually make a working silo. (This had already been my second attempted install on this hardware on the same day. I had used a netboot installer image that had worked previously on an SS20 a couple of months ago. It took a couple of hours to go almost all the way through in downloading and installing, but died when it could not find something in the current Etch that it expected, perhaps a kernel.) Even though my hand-installed 2.4.27-2-sparc32-smp kernel and silo do work, the post-reboot configure step that sets up a root password, a user account, and task software sets has not run. I'm not sure how to trigger that. I installed a root password and user account and password, and did accustomed apt-get installs to set up an xfce4 desktop. With two complete downloads and configures taking up much of a day, this was the most frustrating Debian install I have experienced, after about 40. The previous sparc32 one a few months ago using Etch went very well as I have reported. This one probably would have succeeded had Etch not contained a broken kernel-image-2.4-sparc32-smp pseudo-package. It would have been less annoying to recover from that had priority=low been reset after the kernel install failure, or if there were a way for the installer to be re-entered with a choice to mount /target and /target/boot instead of only one to repartition and install again from square one. ---End Message--- ---BeginMessage--- On Wednesday 24 May 2006 13:53, Steve Pacenka wrote: The installer failed when it tried to download a kernel 2.4.27-3 sparc32 which did not exist in testing. I was operating with the default debconf priority which did not get set to low after the crash, so I was not given the choice to retry using a specific kernel. It looks like you hit a moment when testing on the mirror you were using was inconsistent with regard to kernel packages. Unfortunately that can happen, but should not last too long. I entered a shell and manually installed a 2.4.27-2 kernel via apt-get. That succeeded. Exiting the shell and re-entering the installer menu, I could not get it to let me configure silo with the kernel I had just installed. It kept wanting to repartition the hard drive. I got a shell again and did a manual silo configure which didn't make a bootable system until I hand-edited a silo.conf
Bug#369048: Keyboard freezes as soon as the boot loader starts, but system works (Linux 2.6.15, HP Netserver LP1000r, Symbios Logic 53c1010 Ultra3 SCSI)
On Saturday 27 May 2006 02:24, Olivier Lange wrote: Immediately after the GRUB boot loader starts for the first time, the keyboard freezes and the lights/leds start to blink quite quickly in sequence from right to left. That is totally weird. There is no real reason why running the grub installer should interfere with the keyboard. There must be something more structural going on. The system then automatically boots the first entry from the GRUB menu and starts normally all operations. It can be accessed thru the network SSH console once started. No problems reported within 'dmesg'. You mean after completing the rest of the installation normally? How did you manage that if the keyboard stopped working after grub installation? If the installation was not finished normally, you've basically got a broken system as there are several scripts needed to complete the installation that have not been run and a number of these concern localization. If you can access the system using ssh, you may be able to repair things manually, but figuring how exactly what needs fixing may be hard. It would be better to try to trace what is causing the problem during grub installation. Would you have any suggestion on why the keyboard freezes and how to solve it? No, not really. What we can do is help you try to trace the problem, but that will probably require several reinstalls. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
reassign 370418 base-installer thanks On Tue, Jun 06, 2006 at 01:46:02AM +0200, Frans Pop wrote: reassign 370418 initramfs-tools thanks On Monday 05 June 2006 09:13, Rick Thomas wrote: Begin: Mounting root file system ... ... Begin: Running /scripts/local-top ... /scripts/local-top/lvm: 36 vgchange: not found Done. i8042.c: No controller found FATAL: Error inserting i8042 (/lib/modules/2.6.8-powerpc/kernel/ drivers/input/serio/i8042.ko): No such device ALERT! does not exist: Dropping to a shell! This looks like a initramfs-tools issue to me. Not sure, there is a serious problem here, and namely he is doing an etch beta install, but initramfs-tools somehow thinks there is a 2.6.8 sarge kernel after the reboot. It may be a initramfs-tools problem, but i may also well be a bug in the kernel-installer part of base-installer. The i8042.ko module is definitively part of both the 2.6.8 and the 2.6.16 powerpc kernels, and as thus the error is that initramfs-tools tries to use a non-working or non-existing kernel. Mmm, maybe this is related to sarge 2.6.8 kernel gaining a abi part ? Rick, can you send us a list of the dpkg -l of this system, and check exactly what did happen during the kernel installation. If you can provide us all the logs of the installation, or can do another one, it would be welcome. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Request for a DFB version of libcairo2
On 6/6/06, Frans Pop [EMAIL PROTECTED] wrote: Hi Dave, On Sunday 28 May 2006 00:37, Dave Beckett wrote: I can try to build one in a few days time but I'm unsure how I could test it (in isolation) as I'm not familiar with udebs. If you can provide a udeb, we can at least check its contents and I'm sure that one of us will be able to test with it. Probably I will be able to assist him; yesterday I started on working on the 1.1.6 cairo lib and the gtk2.8 libs. Still I have problems with the creation of the -dev package because I lack the needed knowledge for packaging libraries, but I guess I will overcome that issue with Dave. Most important for us is that the libs in the udeb are built against only the directfb backend and not e.g. the X backend. That will imply 2 builds of the cairo sources with the results of each build in separate directories. I have a rough image in my head about how the package should be modified.. We also need to be able to build other (library) udebs using regular library and -dev packages. I don't know if/how that will work if the udeb is compiled with different configuration options than the debs. I think the proper way is to have libs, -dev libs and udeb generated from the same build result. Please do not upload to unstable without checking with us first. We will probably have to resolve a package name conflict with the package that currently provides the libcairo udeb. We'll also have to make sure that If llibcairo2-directfb-udeb will result from the libcairo2 source package and libcairo-directfb wil be pulled on a dead line there shouldn't be any problem, probably except ... uploading the udeb does not break the daily builds of the graphical installer. the G-I breakage. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Request for a DFB version of libcairo2
On 6/6/06, Eddy Petrişor [EMAIL PROTECTED] wrote: Most important for us is that the libs in the udeb are built against only the directfb backend and not e.g. the X backend. That will imply 2 builds of the cairo sources with the results of each build in separate directories. I have a rough image in my head about how the package should be modified.. On second thought (and after a look over the rules and control files) I am not sure if cdbs can handle multiple builds from one source. -- Regards, EddyP = Imagination is more important than knowledge A.Einstein
Processed: Re: Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
Processing commands for [EMAIL PROTECTED]: reassign 370418 base-installer Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3) Bug reassigned from package `initramfs-tools' to `base-installer'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370667: I2O modules for 64bit platforms
Package: kernel-wedge Severity: important Tags: patch scsi-extra-modules includes dpt_i2o module, but this is only available on 32bit platforms. On 64bit, there's no mechanism in d-i to access I2O devices. This normaly makes the system uninstallable. Please could you add the i2o_block module as well? -- Robert Millan [EMAIL PROTECTED] Departamento de Asistencia Técnica Oficina central: (+34) 902 888 345 Asistencia técnica: (+34) 902 888 408 ACK STORM, S.L. http://www.ackstorm.es Este mensaje electrónico contiene información de ACK STORM, S.L. que es privada y confidencial, siendo para el uso exclusivo de las personas o entidades arriba mencionadas. Si usted no es el destinatario señalado, le informamos que cualquier divulgación, copia, distribución o uso de los contenidos está prohibida. Si usted ha recibido este mensaje por error, por favor borre su contenido y comuníquenoslo en la dirección [EMAIL PROTECTED] -- diff -ur kernel-wedge-2.22.old/modules/scsi-extra-modules kernel-wedge-2.22/modules/scsi-extra-modules --- kernel-wedge-2.22.old/modules/scsi-extra-modules2005-12-07 03:28:15.0 +0100 +++ kernel-wedge-2.22/modules/scsi-extra-modules2006-06-06 10:52:47.0 +0200 @@ -6,6 +6,7 @@ cciss cpqarray dpt_i2o ? +i2o_block dtc ? eata fdomain
Re: Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
On Jun 6, 2006, at 3:46 AM, Sven Luther wrote: Rick, can you send us a list of the dpkg -l of this system, and check exactly what did happen during the kernel installation. If you can provide us all the logs of the installation, or can do another one, it would be welcome. Friendly, Sven Luther OK, they are here: http://www.rcthomas.org/~rbthomas/logfiles/ Getting the dpkg -l listing is not possible, because I can't get this system to boot far enough to do that... All I have is the dead root filesystem that I installed into. Is there something else than the install log files that I can extract from it that will be helpful? Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
On Jun 6, 2006, at 6:18 AM, Rick Thomas wrote: On Jun 6, 2006, at 3:46 AM, Sven Luther wrote: Rick, can you send us a list of the dpkg -l of this system, and check exactly what did happen during the kernel installation. If you can provide us all the logs of the installation, or can do another one, it would be welcome. Friendly, Sven Luther OK, they are here: http://www.rcthomas.org/~rbthomas/logfiles/ Getting the dpkg -l listing is not possible, because I can't get this system to boot far enough to do that... All I have is the dead root filesystem that I installed into. Is there something else than the install log files that I can extract from it that will be helpful? Enjoy! Rick If I can get the dpkg -l by doing it before the reboot of another installation, that might work... I'll give it a try tomorrow. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
On Tue, Jun 06, 2006 at 06:18:13AM -0400, Rick Thomas wrote: On Jun 6, 2006, at 3:46 AM, Sven Luther wrote: Rick, can you send us a list of the dpkg -l of this system, and check exactly what did happen during the kernel installation. If you can provide us all the logs of the installation, or can do another one, it would be welcome. Friendly, Sven Luther OK, they are here: http://www.rcthomas.org/~rbthomas/logfiles/ Getting the dpkg -l listing is not possible, because I can't get this system to boot far enough to do that... All I have is the dead root filesystem that I installed into. Is there something else than the install log files that I can extract from it that will be helpful? Ah, please boot the installer, and then once you are past the disk mounting phase, chroot into /target, and do it there. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
On Tue, Jun 06, 2006 at 06:18:13AM -0400, Rick Thomas wrote: On Jun 6, 2006, at 3:46 AM, Sven Luther wrote: Rick, can you send us a list of the dpkg -l of this system, and check exactly what did happen during the kernel installation. If you can provide us all the logs of the installation, or can do another one, it would be welcome. Friendly, Sven Luther OK, they are here: http://www.rcthomas.org/~rbthomas/logfiles/ This is the relevant bit : Jun 5 05:10:15 base-installer: info: kernel linux-image-2.6.15-1-powerpc64 usable on powerpc Jun 5 05:10:15 base-installer: info: kernel linux-image-2.6.15-1-powerpc-smp usable on powerpc Jun 5 05:10:15 base-installer: info: kernel linux-image-2.6.15-1-powerpc usable on powerpc Jun 5 05:10:15 base-installer: info: kernel linux-image-2.6-powerpc64 usable on powerpc Jun 5 05:10:15 base-installer: info: kernel linux-image-2.6-powerpc-smp usable on powerpc Jun 5 05:10:15 base-installer: info: kernel linux-image-2.6-powerpc usable on powerpc Jun 5 05:10:15 base-installer: info: kernel kernel-image-2.6-powerpc usable on powerpc Jun 5 05:10:15 base-installer: info: kernel kernel-image-2.6-power4 not usable on powerpc Jun 5 05:10:15 base-installer: info: kernel kernel-image-2.6-power3 not usable on powerpc Jun 5 05:10:15 base-installer: info: kernel kernel-image-2.4.27-apus not usable on powerpc Jun 5 05:10:15 base-installer: info: Found kernels 'linux-image-2.6.15-1-powerpc64,linux-image-2.6.15-1-powerpc-smp,linux-image-2.6.15-1-powerpc,linux-image-2.6-powerpc64,linux-image-2.6-powerpc-smp,linux-image-2.6-powerpc,kernel-image-2.6-powerpc' Jun 5 05:10:15 base-installer: info: arch_kernel candidates: linux-image-2.6-powerpc Jun 5 05:10:15 base-installer: info: arch_kernel: linux-image-2.6-powerpc (present) Jun 5 05:11:40 base-installer: info: Using kernel 'linux-image-2.6-powerpc' Jun 5 05:11:40 base-installer: info: Setting do_initrd='yes'. Jun 5 05:11:40 base-installer: info: Setting link_in_boot='yes'. Jun 5 05:11:40 base-installer: info: Possible initramfs generator(s): 'initramfs-tools yaird' Jun 5 05:11:40 base-installer: info: Available initramfs generator(s): 'initramfs-tools' Jun 5 05:11:41 base-installer: info: Installing initramfs-tools. Jun 5 05:11:47 base-installer: info: Installing kernel 'linux-image-2.6-powerpc'. Jun 5 05:11:47 apt-install: The following extra packages will be installed: Jun 5 05:11:47 apt-install: binutils linux-image-2.6.15-1-powerpc mkvmlinuz Jun 5 05:11:47 apt-install: Suggested packages: Jun 5 05:11:47 apt-install: binutils-doc linux-doc-2.6.15 linux-source-2.6.15 Jun 5 05:11:47 apt-install: The following NEW packages will be installed: Jun 5 05:11:47 apt-install: binutils linux-image-2.6-powerpc linux-image-2.6.15-1-powerpc mkvmlinuz Jun 5 05:12:09 apt-install: Setting up linux-image-2.6.15-1-powerpc (2.6.15-8) ... Jun 5 05:12:11 apt-install: Running depmod. Jun 5 05:12:11 apt-install: Finding valid ramdisk creators. Jun 5 05:12:11 apt-install: Using mkinitramfs-kpkg to build the ramdisk. Jun 5 05:12:28 apt-install: Inconsistency detected by ld.so: dl-runtime.c: 76: fixup: Assertion `((reloc-r_info) 0xff) == 21' failed! Jun 5 05:13:34 apt-install: Examining /etc/kernel/postinst.d. Jun 5 05:13:34 apt-install: run-parts: executing /etc/kernel/postinst.d/mkvmlinuz Also, from the .udeb list, it is clear you are running a 2.6.15 kernel. Mmm, this dl-runtime.c error is supsisious, don't know why it is there, maybe still an initramfs-tools problem after all. Now, i don't know why base-installer doesn't provide the verbose version of the initramfs-tools output. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 299850 to debian-installer
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 reassign 299850 debian-installer Bug#299850: acpid should be automatically installed by debian-installer on ACPI machines Bug reassigned from package `acpid' to `debian-installer'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#299850: marked as done (acpid should be automatically installed by debian-installer on ACPI machines)
Your message dated Tue, 6 Jun 2006 12:36:59 +0200 with message-id [EMAIL PROTECTED] and subject line works on 2.6 kernels 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: acpid Version: 1.0.4-1 Severity: wishlist When installing sarge on an ACPI-compliant laptop, the Gnome desktop comes up and allows adding the Battery Charge Monitor to the panel, but the actual program errors out with a dialog box warning that /var/run/acpid.socket is inaccessible. This is hardly a friendly error message by way of explaining to someone that they need to have the acpid package installed. At a minimum, the installer should notice that it is running on ACPI-compliant hardware and ask the user whether the acpid package should be installed. For that matter, the Gnome desktop should probably notice that the acpid daemon is running and automatically configure the battery monitor. I'm not sure whether this bug should properly be filed against the acpid package, the installer, or the Gnome desktop, so I will leave that to the acpid package maintainer to sort out in connection with disposing of this bug. ---End Message--- ---BeginMessage--- Joey Hess offers this in #320094: acpid is already installed on all systems with acpi (and 2.6 kernels) by hw-detect. In addition, unstable's tasksel installs it on any system laptop-detect thinks is a laptop. I think this is covered already. which should close this bug. Thanks, -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer and author: http://debiansystem.info `. `'` `- Debian - when you have better things to do than fixing a system signature.asc Description: Digital signature (GPG/PGP) ---End Message---
Bug#370462: Serial ATA-2 Athlon 64 X2 installation report
Joey Hess [EMAIL PROTECTED] writes: Olaf Meeuwissen wrote: --- Emacs Muse notes I took while installing, wiki markup alert --- Press F1 for help, or ENTER to boot :: nah! I want control, so let's boot using =expert= mode and set the boot keyboard to =jp106= rightaway. It took me a while to figure out that you are apparently supposed to hit _Enter_ when you see =SET debian-installer/keymap jp106=, and again at =FSET debian-installer/keymap seen yes= before the installer continues. Eh, what? Why was the installer taking raw debconf protocol to you? No idea. I just said: expert bootkbd=jp106 at the bootprompt and that's what I got. Note though, that this happened not only with the beta2 installer but also with the 20060525 snapshot. I've had a look at the logs in /var/log/installer, but the only odd thing I could find was this (from beta2, note line marked with ): Jun 3 06:26:12 kernel: Probing IDE interface ide1... Jun 3 06:26:12 kernel: ieee1394: Host added: ID:BUS[0-00:1023] GUID[0010dccb7904] Jun 3 06:26:13 S30read-environment: Setting debconf/priority to 'low'. Jun 3 06:26:13 frontend: Setting debconf/priority to low Jun 3 06:26:13 kernel: vga16fb: initializing Jun 3 06:26:13 kernel: vga16fb: mapped to 0x810a Jun 3 06:26:13 kernel: Console: switching to colour frame buffer device 80x30 Jun 3 06:26:13 kernel: fb0: VGA16 VGA frame buffer device Jun 3 06:26:13 kbd-chooser[3284]: INFO: kbd_chooser: setting keymap jp106 Jun 3 06:26:16 kernel: Vendor: Generic Model: STORAGE DEVICERev: 9317 Jun 3 06:26:16 kernel: Type: Direct-Access ANSI SCSI revision: 00 Jun 3 06:26:16 kernel: sd 5:0:0:0: Attached scsi removable disk sdb Jun 3 06:26:16 kernel: Vendor: Generic Model: STORAGE DEVICERev: 9317 Jun 3 06:26:16 kernel: Type: Direct-Access ANSI SCSI revision: 00 Jun 3 06:26:16 kernel: sd 5:0:0:1: Attached scsi removable disk sdc Jun 3 06:26:16 kernel: usb-storage: device scan complete Jun 3 06:26:35 init: ^MStarting pid 3339, console /dev/vc/1: '/sbin/debian-installer' Jun 3 06:26:35 init: ^MStarting pid 3347, console /dev/vc/3: '/usr/bin/tail' Jun 3 06:26:35 init: ^MStarting pid 3350, console /dev/vc/4: '/usr/bin/tail' Jun 3 06:26:35 main-menu[3375]: DEBUG: Executing /lib/main-menu.d/10rescue Jun 3 06:26:35 main-menu[3375]: DEBUG: Executing /lib/main-menu.d/5lowmem Jun 3 06:26:35 main-menu[3375]: DEBUG: resolver (libc6): package doesn't exist (ignored) Jun 3 06:26:35 main-menu[3375]: DEBUG: resolver (libdebian-installer4): search, dependency from cdebconf-udeb Jun 3 06:26:35 main-menu[3375]: DEBUG: resolver (libdebian-installer4-udeb): mark, dependency from cdebconf-udeb For the rest there are two mentions of bootkbd=jp106 when the kernel command line is logged before the above extract from the syslog file. When that SET debian-installer/keymap jp106 is shown on the screen I can not switch VTs. The three finger salute works, though. # Cmpletely unrelated, my system clock is running at double speed. # Mighty annoying. It seems to be a well-known and old problem, though. Hope this helps, -- Olaf Meeuwissen FSF Associate Member #1962 sign up at http://member.fsf.org/ GnuPG key: 30EF893A/2774 815B DE83 06C8 D733 6B5B 033C C857 30EF 893A Penguin's lib! -- I hack, therefore I am -- LPIC-2 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354080: installation-report
It's been almost a year since I opened this bug, and I lost track of it because your response must have been marked as spam (in my yahoo). Please close it, as I've managed to install correctly since then (can submitters close their own bugs?) Eduardo OH MY ... http://www.geocities.com/jobezone/index.html __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370318: tasksel: Please provide hardinfo in desktop-environment task
I'm having trouble receiving the comments of bugs I submit in my e-mail, and I'm wondering if my posterior comments are also received by otherws. Did you receive my previous comment, where I say: I'm sorry, after all it doesn't run in text mode!... I was trying out some hardware-reporting programs, and I mixed both hardinfo and hwinfo together. It's a pitty it doesn't work on the command line... I searched for its website to make sure ( http://hardinfo.berlios.de/wiki/index.php/Main_Page ), and nope, it doesn't[...] OH MY ... http://www.geocities.com/jobezone/index.html __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processing of debian-installer-utils_1.31_powerpc.changes
debian-installer-utils_1.31_powerpc.changes uploaded successfully to localhost along with the files: debian-installer-utils_1.31.dsc debian-installer-utils_1.31.tar.gz di-utils-shell_1.31_all.udeb di-utils-reboot_1.31_all.udeb di-utils-exit-installer_1.31_all.udeb di-utils-terminfo_1.31_all.udeb di-utils_1.31_powerpc.udeb di-utils-mapdevfs_1.31_powerpc.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
debian-installer-utils_1.31_powerpc.changes ACCEPTED
Accepted: debian-installer-utils_1.31.dsc to pool/main/d/debian-installer-utils/debian-installer-utils_1.31.dsc debian-installer-utils_1.31.tar.gz to pool/main/d/debian-installer-utils/debian-installer-utils_1.31.tar.gz di-utils-exit-installer_1.31_all.udeb to pool/main/d/debian-installer-utils/di-utils-exit-installer_1.31_all.udeb di-utils-mapdevfs_1.31_powerpc.udeb to pool/main/d/debian-installer-utils/di-utils-mapdevfs_1.31_powerpc.udeb di-utils-reboot_1.31_all.udeb to pool/main/d/debian-installer-utils/di-utils-reboot_1.31_all.udeb di-utils-shell_1.31_all.udeb to pool/main/d/debian-installer-utils/di-utils-shell_1.31_all.udeb di-utils-terminfo_1.31_all.udeb to pool/main/d/debian-installer-utils/di-utils-terminfo_1.31_all.udeb di-utils_1.31_powerpc.udeb to pool/main/d/debian-installer-utils/di-utils_1.31_powerpc.udeb Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Request for a DFB version of libcairo2
Frans Pop wrote: Hi Dave, On Sunday 28 May 2006 00:37, Dave Beckett wrote: I can try to build one in a few days time but I'm unsure how I could test it (in isolation) as I'm not familiar with udebs. If you can provide a udeb, we can at least check its contents and I'm sure that one of us will be able to test with it. If you need any help, feel free to ask here or on IRC (#d-boot on OFTC). Maybe the paper [1] for my Debconf workshop can help as well. Most important for us is that the libs in the udeb are built against only the directfb backend and not e.g. the X backend. you have to build cairo = 1.1.2 with --enable-directfb=yes --disable-xlib and you may also want to exclude building of ps and pdf backends. Please, also remember we need the cairo library to be built against DFB 0.9.24. Josselin Mouette, from debian-gtk-gnome team, said he's ready to try building gtkdfb 2.8.17 package as soon cairodfb gets packages, so i belive having cairodfb packaged as soon as possible is very important for the GTK libraries upgrade process. Attilio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354147: marked as done (tasksel: Tasksel should pre-install alsa-utils package)
Your message dated Tue, 06 Jun 2006 11:48:03 -0300 with message-id [EMAIL PROTECTED] and subject line tasksel: Tasksel should pre-install alsa-utils package 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: tasksel Version: 2.40 Severity: wishlist The alsa-utils should probably be installed by default with the Desktop Task: The main reason I find this is that it contains the alsactl program which stores alsa sound levels. Without this package installed, the sound is muted after a boot (quickly fixed by just installing it). -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-k7 Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8) Versions of packages tasksel depends on: ii aptitude 0.4.1-1terminal-based apt frontend ii debconf [debconf-2.0] 1.4.70 Debian configuration management sy ii laptop-detect 0.12.1 attempt to detect a laptop ii liblocale-gettext-perl1.05-1 Using libc functions for internati tasksel recommends no packages. -- debconf information: tasksel/title: tasksel/first: tasksel/tasks: ---End Message--- ---BeginMessage--- Version: 2.41 Hi, alsa-utils package was already added (2.41) in the desktop task. Thanks, Gustavo Franco - [EMAIL PROTECTED] ---End Message---
Bug#276910: marked as done (pbbuttonsd should install by default on PowerPC)
Your message dated Tue, 06 Jun 2006 11:36:41 -0300 with message-id [EMAIL PROTECTED] and subject line pbbuttonsd in tasksel. 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: pbbuttonsd Version: 0.6.3a-2 Severity: normal pbbuttonsd should install by default on PowerPC architectures, at least when the desktop feature set is selected. It does no harm on non-laptops and will allow Powerbooks and iBooks to sleep on close as users expect, one of the signature features of Apple laptops. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Kernel: Linux 2.6.8-powerpc Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages pbbuttonsd depends on: ii eject 2.0.13deb-7 ejects CDs and operates CD-Changer ii hdparm 5.7-1Tune hard disk parameters for high ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an -- no debconf information ---End Message--- ---BeginMessage--- Version: 2.48 Hi, tasksel 2.48 closes this bug. It adds pbbuttonsd to laptop task list. :-) Thanks, Gustavo Franco - [EMAIL PROTECTED] ---End Message---
Bug#370318: tasksel: Please provide hardinfo in desktop-environment task
Hi, Is this bug still relevant? I think 'lshal' (console) and hal-device-manager (GUI) are doing this job in desktop environment task, aren't ? Thanks, Gustavo Franco - [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#370098: tasksel: Desktop Environment installs both firefox and galeon
It doesn't make sense to install it as part of the GNOME desktop. It doesn't integrate correctly with the desktop, and doesn't have any key features epiphany doesn't have. In the end, it's just confusing to have two browsers installed, just because one of them is well-known. Actually, it seems that wouldn't hurt to remove firefox from the gnome desktop task by avoiding te gnome-desktop-environment to pull it in, as it is installed by the standalone desktop task, if I'm correct. signature.asc Description: Digital signature
Re: Request for a DFB version of libcairo2
Eddy Petrişor wrote: On 6/6/06, Eddy Petrişor [EMAIL PROTECTED] wrote: Most important for us is that the libs in the udeb are built against only the directfb backend and not e.g. the X backend. That will imply 2 builds of the cairo sources with the results of each build in separate directories. I have a rough image in my head about how the package should be modified.. On second thought (and after a look over the rules and control files) I am not sure if cdbs can handle multiple builds from one source. It can't. I'll have to downgrade it to use bare make :( Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Request for a DFB version of libcairo2
Dave Beckett wrote: Eddy Petrişor wrote: On 6/6/06, Eddy Petrişor [EMAIL PROTECTED] wrote: Most important for us is that the libs in the udeb are built against only the directfb backend and not e.g. the X backend. That will imply 2 builds of the cairo sources with the results of each build in separate directories. I have a rough image in my head about how the package should be modified.. On second thought (and after a look over the rules and control files) I am not sure if cdbs can handle multiple builds from one source. It can't. I'll have to downgrade it to use bare make :( maybe keeping a separate source package for cairo 1.1.6 is a better option? Attilio -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sarge3 kernel build r3
I saw some questions on irc about the sarge3 kernel build r3... zobel it's just, i actualy wanted to release sarge r3 with sarge2 kernels. now i get told sarge3-kernels are already prepared, which disapoints me a bit, as noone told the stable release team there will be another kernel update round for r3 :( waldi ask dannf, he prepares the updates currently zobel and actually sarge r3 is just waiting for a new d-i, which i understand is currently waiting for kernel udebs... zobel dannf: ^ waldi -boot is responsible for the udebs anyway During the d-i bof at DebConf I pointed out that the sarge3 kernel build is in progress and is not an ABI change - there was consensus to wait for this build before doing the d-i build for r3. I don't remember the timeline we discussed for this build. The current status is that the build is complete and pending upload by the security team (I think Moritz would be the one to do it, so I've cc'd him). I believed aba, joeyh fjp were all in on this decision, but apologies if it didn't get communicated back to everyone involved. h01ger dannf, as long as u dont upload (before coordinating with zobel/srm-team) everybody is happy about your work :) Personally, I don't care which kernel gets used - that's a stable-release/d-i decision in my opinion. However, I do not think we should delay the release of the sarge3 kernel to security.debian.org - I want to avoid any situation that would prevent us from doing timely security updates. If you decide to stick with sarge2 for r3, would an upload of sarge3 to security.debian.org break this? As I understand it, sarge2 is already in the queue archive for stable, so those bits would still be available? -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
dann frazier wrote: I saw some questions on irc about the sarge3 kernel build r3... zobel it's just, i actualy wanted to release sarge r3 with sarge2 kernels. now i get told sarge3-kernels are already prepared, which disapoints me a bit, as noone told the stable release team there will be another kernel update round for r3 :( That's rediculous. The Security Team does not have to announce their updates n days in advance to the stable release team. The Security Team instead must be able to issue security updates at any time. Thanks to the new proposed-updates barrier these updates don't even have to affect proposed-updates as they can easily be installed into proposed-updates after the next point release. It would be good if we would be able some day to release kernel updates in a more timely fashion and also not accumulate this many security updates in one update. However, due to the number of architectures and affected packages I'm not sure this goal can be met any time soon. But that's a different story... zobel and actually sarge r3 is just waiting for a new d-i, which i understand is currently waiting for kernel udebs... waldi -boot is responsible for the udebs anyway -- Not the problem of the Security Team However, if kernel udebs should be part of the security update, then we'll need proper source packages that build these udebs - or, if these already exist, a pointer which source package has been forgotton in the last kernel update rounds. During the d-i bof at DebConf I pointed out that the sarge3 kernel build is in progress and is not an ABI change - there was consensus to wait for this build before doing the d-i build for r3. I don't remember the timeline we discussed for this build. The current status is that the build is complete and pending upload by the security team (I think Moritz would be the one to do it, so I've cc'd him). Oh. Great. Good to hear (err... sending such information to [EMAIL PROTECTED] would actually be a good idea as well...) h01ger dannf, as long as u dont upload (before coordinating with zobel/srm-team) everybody is happy about your work :) 1. Uploading to the security archive should be possible without coordination with the release team. If the later is required, something is broken. 2. Thanks to the barrier between incoming and proposed-updates even the push into the main archive should not be a problem since the stable release team only has to delay acceptance of the new packages so that the older ones are not overwritten before the point release. That's one of the benefits of the new barrier. Personally, I don't care which kernel gets used - that's a stable-release/d-i decision in my opinion. However, I do not think we Ack. should delay the release of the sarge3 kernel to security.debian.org - Ack. I want to avoid any situation that would prevent us from doing timely security updates. Ack. If you decide to stick with sarge2 for r3, would an upload of sarge3 to security.debian.org break this? As I understand it, sarge2 is already It shouldn't be able to. Regards, Joey -- Every use of Linux is a proper use of Linux. -- Jon 'maddog' Hall Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Has anyone successfully used apt-get w/ ssh?
Hello again gurus, I'm working on an automated installation and thought I would give the ssh access method a whirl with apt-get for installing my custom packages. My problem is that I can't seem to get the options that I need passed to ssh's command line by apt. The man page for apt-get hinted that this is possible, but didn't specify how to tell apt-get what command line options to pass to ssh, so I downloaded the source for the version of apt that comes with sarge and perused the source code. According to apt-0.5.28.6/methods/rsh.cc[375] I should be able to use the command line option: -o 'Acquire::ssh::Options=-i /path/to/id_rsa -l username' But when I do, apt-get hangs when it tries to contact my install server. When I use 'ps -ef | grep ssh' to check the command line apt-get used for ssh, the options I have specified aren't there, just the hostname. I have also tried using Ssh, SSH, rsh, Rsh, RSH in place of the ssh in the Aquire line above, all to no avail. (This is all being done on a freshly-installed, barest-of-bones Debian system, btw.) I know that the ssh keys are set up correctly because I can call ssh by hand, passing it the options specified above, and I'm allowed right in without being prompting for a password. Has anyone successfully gotten ssh to work with apt-get? Thanks for your help, Michael Peek -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#370098: tasksel: Desktop Environment installs both firefox and galeon
Christian Perrier wrote: It doesn't make sense to install it as part of the GNOME desktop. It doesn't integrate correctly with the desktop, and doesn't have any key features epiphany doesn't have. In the end, it's just confusing to have two browsers installed, just because one of them is well-known. Actually, it seems that wouldn't hurt to remove firefox from the gnome desktop task by avoiding te gnome-desktop-environment to pull it in, as it is installed by the standalone desktop task, if I'm correct. The gnome destktop task is pulled in by the main desktop task; firefox is part of the main desktop task. -- see shy jo signature.asc Description: Digital signature
reportbug broken
Short heads-up, if you do a d-i unstable install reportbug breaks in postinst, which in turn breaks tasksel (bug #370740). I've updated the wiki page. Re, David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Tue, Jun 06, 2006 at 06:56:33PM +0200, Martin Schulze wrote: However, if kernel udebs should be part of the security update, then we'll need proper source packages that build these udebs - or, if these already exist, a pointer which source package has been forgotton in the last kernel update rounds. I've offered to perform these builds for all archs except mips, mipsel m68k (but I can help coordinate those as well - those arch maintainers have always been very responsive to my build requests). This offer is still open, just let me know if they should be against sarge2 or sarge3. I suspect I could turn this around in a day or two (if its the right day or two). Oh. Great. Good to hear (err... sending such information to [EMAIL PROTECTED] would actually be a good idea as well...) ok -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370318: tasksel: Please provide hardinfo in desktop-environment task
Gustavo Franco wrote: Is this bug still relevant? I think 'lshal' (console) and hal-device-manager (GUI) are doing this job in desktop environment task, aren't ? hardinfo does provide more information (of some types), it's arguable whether this is bloat of the task or not. -- see shy jo signature.asc Description: Digital signature
Processed: reassign 370631 to installation-reports
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 reassign 370631 installation-reports Bug#370631: failed Installation report for etch daily 2006/06/05 netinst on oldworld PowerPC Mac (beige g3) Bug reassigned from package `debian-installer' to `installation-reports'. 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]
Processed: reassign 299850 to hw-detect
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.20 reassign 299850 hw-detect Bug#299850: acpid should be automatically installed by debian-installer on ACPI machines Bug reassigned from package `debian-installer' to `hw-detect'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354080: marked as done (installation-report)
Your message dated Tue, 6 Jun 2006 13:48:53 -0400 with message-id [EMAIL PROTECTED] and subject line Bug#354080: installation-report has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: installation-reports Boot method: Cd Image version: 23 Feb 2006, the daily gtk mini-iso at http://people.debian.org/~fjp/d-i/gtk-miniiso/daily/i386/ linked from http://wiki.debian.org/DebianInstaller/GUI Date: 23 Feb 2006 04:25 Machine: Acer Aspire 3003LMi laptop Processor:AMD Sempron 3000 Memory:1GB DDR Partitions: /dev/hda2 * 3842815 19535040c W95 FAT32 (LBA) /dev/hda328164031 9767520 83 Linux /dev/hda440329729457691855 Extended /dev/hda540324286 2048256 82 Linux swap / Solaris /dev/hda64287972943720866 83 Linux Output of lspci and lspci -n: :00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host (rev 03) :00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202 :00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 25) :00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016 :00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] :00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0) :00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0) :00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) :00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller:00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91) :00:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 02) :00:0b.0 Network controller: Broadcom Corporation: Unknown device 4318 (rev 02) :00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge :01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661FX/M661FX/M661MX/741/M741/760/M760 PCI/AGP :00:00.0 0600: 1039:0760 (rev 03) :00:01.0 0604: 1039:0002 :00:02.0 0601: 1039:0963 (rev 25) :00:02.1 0c05: 1039:0016 :00:02.5 0101: 1039:5513 :00:02.6 0703: 1039:7013 (rev a0) :00:02.7 0401: 1039:7012 (rev a0) :00:03.0 0c03: 1039:7001 (rev 0f) :00:03.1 0c03: 1039:7001 (rev 0f) :00:03.2 0c03: 1039:7002 :00:04.0 0200: 1039:0900 (rev 91) :00:06.0 0607: 104c:ac50 (rev 02) :00:0b.0 0280: 14e4:4318 (rev 02) :00:18.0 0600: 1022:1100 :00:18.1 0600: 1022:1101 :00:18.2 0600: 1022:1102 :00:18.3 0600: 1022:1103 :01:00.0 0300: 1039:6330 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[E] Configure network HW: [O] Config network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [E] Partition hard drives: [E] Create file systems:[ ] Mount partitions: [ ] Install base system:[ ] Install boot loader:[ ] Reboot: [ ] Comments/Problems: I tried the gtk mini-iso hoping to help you guys prepare the beta 2 of it, so I knew somethings would probably not work. Hope it will be helpfull:) So, from the start, the touchpad was not configured right, but _was_ detected. Meaning, as I tried moving it using the touchpad, it went diagonally to the bottom right very fast and disapeared from view. I could use the rest of the installer very well just using the keyboard. Afterward, in the partition menu, it showed the hardisk as having no partition, and with a size of 64.9 MB. It would only allow me to create an empty partition table. Maybe I have LVM (I've read that there are some issues with it with some daily images of debian-installer), although I don't know what that is. I only split the second 40GB partition into /, /home and /swap when I got this laptop. I'm now going to try the regular debian-testing-i386-businesscard.iso instead. OH MY ... http://www.geocities.com/jobezone/index.html __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the
Bug#370318: tasksel: Please provide hardinfo in desktop-environment task
Eduardo Silva wrote: Did you receive my previous comment, where I say: I'm sorry, after all it doesn't run in text mode!... Yes. -- see shy jo signature.asc Description: Digital signature
Bug#370667: I2O modules for 64bit platforms
Robert Millan [ackstorm] wrote: scsi-extra-modules includes dpt_i2o module, but this is only available on 32bit platforms. On 64bit, there's no mechanism in d-i to access I2O devices. This normaly makes the system uninstallable. Please could you add the i2o_block module as well? Which architectures include support for i2o_block? And if dpt_i2o does the same thing for i386, whouldn't we include i2o_block only for those architectures that do not have dpt_i2o? -- see shy jo signature.asc Description: Digital signature
Bug#336664: marked as done (ramdisk too small; entry fields misaligned)
Your message dated Tue, 6 Jun 2006 19:59:43 +0200 with message-id [EMAIL PROTECTED] and subject line ramdisk too small; entry fields misaligned 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: 2005-10-31, 3.1r0a netinst image from cdimage.debian.org uname -a: Linux ptdslnx 2.6.8-2-32-smp #1 SMP Mon Feb 7 22:19:10 EST 2005 parisc GNU/Linux Date: 2005-10-31 13:30 EST Method: installed base system from CD; didn't try network install yet Machine: HP Visualize B2000 Processor: 400MHz PA8600 (PCX-W+) Memory: 256M Root Device: /dev/mapper/vg00-root Root Size/partition table: Disk /dev/sda: 17366 cylinders, 64 heads, 32 sectors/track Warning: The partition table looks like it was made for C/H/S=*/255/63 (instead of 17366/64/32) For this listing I'll assume that geometry. Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0 Device Boot Start End #cyls#blocks Id System /dev/sda1 0+ 7 8- 64228+ f0 Linux/PA-RISC boot /dev/sda2 8 128 122 979965 83 Linux /dev/sda3 13022122083 16731697+ 8e Linux LVM /dev/sda4 0 - 0 00 Empty # /dev/sda2 = /boot; the rest are LVs created from a PV on /dev/sda3 Output of lspci and lspci -n: :00:0c.0 Ethernet controller: Digital Equipment Corporation DECchip 21142/43 (rev 41) :00:0d.0 Multimedia audio controller: Analog Devices AD1889 sound chip :00:0e.0 IDE interface: National Semiconductor Corporation 87415/87560 IDE (rev 03) :00:0e.1 Bridge: National Semiconductor Corporation 87560 Legacy I/O (rev 01) :00:0e.2 USB Controller: National Semiconductor Corporation USB Controller (rev 02) :00:0f.0 SCSI storage controller: LSI Logic / Symbios Logic 53c895a (rev 01) :01:00.0 3D Controller: Hewlett-Packard Company Visualize FXe (rev 03) :00:0c.0 0200: 1011:0019 (rev 41) :00:0d.0 0401: 11d4:1889 :00:0e.0 0101: 100b:0002 (rev 03) :00:0e.1 0680: 100b:000e (erv 01) :00:0e.2 0c03: 100b:0012 (rev 02) :00:0f.0 0100: 1000:0012 (rev 01) :01:00.0 0302: 103c:108b (rev 03) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:[E] Configure network HW: [ ] Config network: [ ] 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: Had to increase the ramdisk_size to 64M at the PALO prompt before install would work. Otherwise it ran out of room during startup and went into a loop, unable to find the net/unix/unix.ko kernel module. modprobe: FATAL: Could not open '/lib/modules/2.6.8-2-32/kernel/net/unix/unix.ko': No such file or directory On a separate note, during installation, text entry fields and the progress bars were all misaligned by one tty column to the right relative to their frames. Additionally, when a default value was supplied, its first character would remain as a dropping to the left of the entry field during editing. ---End Message--- ---BeginMessage--- This is a known issue for the Sarge installer for HPPA documented in the errata: http://www.debian.org/releases/sarge/debian-installer/ Therefore closing the report. Cheers, FJP ---End Message---
Re: sarge3 kernel build r3
On Tuesday 06 June 2006 18:01, dann frazier wrote: I believed aba, joeyh fjp were all in on this decision, but apologies if it didn't get communicated back to everyone involved. That's right, aba agreed to this plan as representative of the stable release team. Also, I posted an update about this in [1]. I also posted proposed patches needed for d-i itself in that mail. I seem to remember though that the security update was planned for the end of Debconf, so I was a bit surprised when reading my mail backlog this week that it is not out yet. What is the full status of the updates for Sarge for both 2.4 and 2.6? A release using sarge2 kernels would have been logical if the kernel udebs would have been available in t-p-u earlier than was the case. With all the holidays planned after debconf the timing for the remaining work was rather unfortunate. ATM waiting for sarge3 still seems more logical. Personally, I can only go full speed on this once I get back home next week. Personally, I don't care which kernel gets used - that's a stable-release/d-i decision in my opinion. However, I do not think we should delay the release of the sarge3 kernel to security.debian.org - I want to avoid any situation that would prevent us from doing timely security updates. If you decide to stick with sarge2 for r3, would an upload of sarge3 to security.debian.org break this? As I understand it, sarge2 is already in the queue archive for stable, so those bits would still be available? As kernel udebs are built manually it is entirely up to the person doing the build to make sure that the correct kernel version is installed on the machine used for the builds. On Tuesday 06 June 2006 18:56, Martin Schulze wrote: However, if kernel udebs should be part of the security update, then we'll need proper source packages that build these udebs - or, if these already exist, a pointer which source package has been forgotton in the last kernel update rounds. No, I don't think that really makes sense as just building the kernel udebs would not get them to the users. You need to release the installer as a whole for that. Cheers, FJP [1] [EMAIL PROTECTED] pgpWbtvJipT3T.pgp Description: PGP signature
Re: sarge3 kernel build r3
On Tuesday 06 June 2006 19:22, dann frazier wrote: I've offered to perform these builds for all archs except mips, mipsel m68k (but I can help coordinate those as well - those arch maintainers have always been very responsive to my build requests). This offer is still open, just let me know if they should be against sarge2 or sarge3. I suspect I could turn this around in a day or two (if its the right day or two). The more arches are built by the same person, the easier coordination is. So your offer is very welcome. Note that you'll need to check out the kernel udeb package sources from the *sarge branch* of the d-i SVN repo for the different arches as ABI numbers have to be updated there. I could do i386, sparc and S/390 myself if needed, but only next week. I'm still not sure about the status of AMD64 in this update. It would be nice if AMD64 could be brought back in line with the other arches with r3. If the kernel updates cannot be released into the main archive for AMD64, we'll have to skip that arch for d-i too. Cheers, FJP pgpHPCPQUUFY2.pgp Description: PGP signature
tasksel 2.47 MIGRATED to testing
FYI: The status of the tasksel source package in Debian's testing distribution has changed. Previous version: 2.44 Current version: 2.47 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
On Tuesday 06 June 2006 21:32, dann frazier wrote: I don't think its very likely that amd64/sarge will be added to debian.org, I did not mean to imply that of course. but this is a good question for the amd64.debian.net maintainers. The main reason we need to know is that the d-i source needs to be updated for the ABI change and so we need to know if this update should happen for AMD64 as well as for the other arches *before* we _upload_ it. Also, from a CD building point of view amd64 is the same as other arches, even if its packages reside on a different mirror. CDs for amd64 are normally built at the same time as other arches and it would be nice if they could follow the same timeline as the main archive. If need be, the _build_ of the new installer images and the build of CDs for AMD64 could be delayed, but preferably not. pgpjR3FVWhtyT.pgp Description: PGP signature
locking devices and partitions in partman
Hi all,
currently it is possible to:
1) Setup a device which depends on other devices, e.g. a LVM volume group
2) Remove/repartition the underlying devices
3) Watch as things fall apart
Being able to lock devices and/or partition which are in use would be
a helpful feature to protect from shooting oneself in the foot IMHO and
seems to have been a wishlist item for some time.
So, I've made an attempt at this. Attached is the basic outline of my
idea. I've implemented the basics (error message when trying to modify a
locked partition/device) in partman-base and added support for it to
partman-lvm as a proof-of-concept.
I'd love to hear some comments on this approach.
Regards,
David
Index: partman-base/debian/partman-base.templates
===
--- partman-base/debian/partman-base.templates (revision 37863)
+++ partman-base/debian/partman-base.templates (working copy)
@@ -14,6 +14,24 @@
Type: text
_Description: Detecting file systems...
+Template: partman-base/devicelocked
+Type: error
+_Description: The device is currently in use
+ The device ${DEVICE} is currently in use for the following purpose:
+ ${MESSAGE}
+ .
+ You must first make sure that the device is no longer in use before you
+ can make any changes to it.
+
+Template: partman-base/partlocked
+Type: error
+_Description: The partition is currently in use
+ Partition #${PARTITION} of device ${DEVICE} is currently in use for the
following purpose:
+ ${MESSAGE}
+ .
+ You must first make sure that the partition is no longer in use before you
+ can make any changes to it or the device which it resides on.
+
Template: partman/exception_handler
Type: select
Choices: ${CHOICES}
Index: partman-base/definitions.sh
===
--- partman-base/definitions.sh (revision 37863)
+++ partman-base/definitions.sh (working copy)
@@ -866,6 +866,65 @@
esac
}
+lock_device() {
+ local device message dev testdev
+ device=$1
+ message=$2
+
+ for dev in $DEVICES/*; do
+ [ -d $dev ] || continue
+ cd $dev
+
+ # First check if we should lock a device
+ if [ -e device ]; then
+ testdev=$(mapdevfs $(cat device))
+ if [ $device = $testdev ]; then
+ echo $message locked
+ return 0
+ fi
+ fi
+
+ # Second check if we should lock a partition
+ open_dialog PARTITIONS
+ while { read_line num id size type fs path name; [ $id ]; };
do
+ testdev=$(mapdevfs $path)
+ if [ $device = $testdev ]; then
+ echo $message $id/locked
+ fi
+ done
+ close_dialog
+ done
+}
+
+unlock_device() {
+ local device dev testdev
+ device=$1
+
+ for dev in $DEVICES/*; do
+ [ -d $dev ] || continue
+ cd $dev
+
+ # First check if we should unlock a device
+ if [ -e device ]; then
+ testdev=$(mapdevfs $(cat device))
+ if [ $device = $testdev ]; then
+ rm -f locked
+ return 0
+ fi
+ fi
+
+ # Second check if we should lock a partition
+ open_dialog PARTITIONS
+ while { read_line num id size type fs path name; [ $id ]; };
do
+ testdev=$(mapdevfs $path)
+ if [ $device = $testdev ]; then
+ rm -f $id/locked
+ fi
+ done
+ close_dialog
+ done
+}
+
log '***'
# Local Variables:
Index: partman-base/choose_partition/partition_tree/do_option
===
--- partman-base/choose_partition/partition_tree/do_option (revision 37863)
+++ partman-base/choose_partition/partition_tree/do_option (working copy)
@@ -8,7 +8,44 @@
id=${1#*//}
cd $dev
+device=$(humandev $(cat device))
+# If the user wants to modify a device or partition
+# the device may not be locked
+if [ -e $dev/locked ]; then
+ locked=$(cat $dev/locked)
+ db_subst partman-base/devicelocked DEVICE $device
+ db_subst partman-base/devicelocked MESSAGE $locked
+ db_set partman-base/devicelocked false
+ db_input critical partman-base/devicelocked
+ db_go
+ exit 0
+fi
+
+# Two scenarios to check for here:
+# 1) If the user wants to modify a partition - it may not be locked
+# 2) If the user wants to modify a device - none of its partitions may be
locked
+open_dialog PARTITIONS
+while { read_line
Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
On Jun 6, 2006, at 5:40 PM, Frans Pop wrote: (removing all irrelevant CCs; please respect the reply-to) On Tuesday 06 June 2006 12:18, Rick Thomas wrote: OK, they are here: http://www.rcthomas.org/~rbthomas/logfiles/ As there is absolutely no mention of 2.6.8 in this installation itself, the problem seems to be in the bootloader configuration and not in base-installer. Are you sure that the correct initrd and kernel are loaded? I don't see anything in the logs about bootloader setup... The only issue I can see in the install is the same as already spotted by Sven: apt-install: Inconsistency detected by ld.so: dl-runtime.c: 76: fixup: Assertion `((reloc-r_info) 0xff) == 21' failed! I would say that this is a problem in the target system (maybe initramfs-tools) rather than in the installer as apt-install effectively runs in the /target chroot. It also seems as if this error does not affect the installation itself as it just continues (although it might cause a broken initrd). It may be related, but it could also be a totally unrelated issue (though probably worth following up). The best way to debug this would be switching to console after base installation, do a 'chroot /target' and try to generate the initrd manually (with verbose options and checking the result afterwards; you may have to mount /sys and /proc). Anyway, the bootloader configuration should be checked to see why it tries to do anything with a 2.6.8 kernel which presumably comes from some old install. It's an oldworld Mac (beige G3) and I use MacOS-9/BootX as the bootloader, so I skipped the install quik bootloader step during the install (used continue without bootloader). That's probably why you aren't seeing anything in the logs about bootloader setup. This machine has a partition with sarge on it. Is it trying to do something with the 2.6.8 kernel from there? If so, why?!? Give me detailed instructions or a pointer to the correct part for me to RTFM, and I'll do the manual initrd generation tonight or tomorrow. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: locking devices and partitions in partman
On Wednesday 07 June 2006 00:29, David Härdeman wrote: I'd love to hear some comments on this approach. One problem I see at first glance is one of translation: you cannot hardcode a string like In use by LVM VG $vg for $MESSAGE, unless you really want all translators (led by Christian) coming after you with a heavy cluebat... Are there cases where there could be multiple locks on the same device/partition? The current code does not seem to support this. The function names look potentially confusing too as (un)lock_device can be used for both devices and partitions. Would it not be cleaner to also pass the partition as a parameter instead of using $id? Are you sure that will always be set correctly? Is it correct that a device gets unlocked if there are partitions on it that are still locked (partitions other than the current one being unlocked)? Cheers, FJP pgpgaElaC476V.pgp Description: PGP signature
Re: r37787 - trunk/packages/debian-installer-utils
On Friday 02 June 2006 20:05, Joey Hess wrote: + search-path: returns true if a program is found in the path (d-i has to which command, so use this instead) In the current code we use 'if type [program] /dev/null 21; then' for this quite often. So, although we don't have 'which', we do have 'type'. Should we replace those calls or does that make search-path redundant? pgpAQN75QgrtD.pgp Description: PGP signature
Re: r37788 - in trunk/installer: debian
On Friday 02 June 2006 20:08, Joey Hess wrote: Log: * Workaround syslinux weirdness on hd-media images; when asked to boot 2.6/linux, it tries to boot 2.6/l. Rename files out of directories to avoid this; the gtk initrd has the unappitising name initrdg.gz. Is this new syslinux weirdness and a temporary workaround or is this an old problem? I could not find a BR against syslinux for the issue. pgpK75htydxB1.pgp Description: PGP signature
Re: locking devices and partitions in partman
On Wed, Jun 07, 2006 at 01:00:22AM +0200, Frans Pop wrote: On Wednesday 07 June 2006 00:29, David Härdeman wrote: I'd love to hear some comments on this approach. One problem I see at first glance is one of translation: you cannot hardcode a string like In use by LVM VG $vg for $MESSAGE, unless you really want all translators (led by Christian) coming after you with a heavy cluebat... Yes, yes, translatable strings is something I'll fix in the timespan between post-proof-of-concept and pre-svn-commit but definately before the perrier-grabs-his-+5-cluebat-of-smiting era. Are there cases where there could be multiple locks on the same device/partition? The current code does not seem to support this. It doesn't support multiple locks per device or partition. I'm not able to come up with a situation where it would be needed though...a device or partition being used by several subsystems simultaneously does sound a bit weird to my limited brain. The function names look potentially confusing too as (un)lock_device can be used for both devices and partitions. Ok...how about partman_(un)lock_unit? I'm not sure about the naming since it should convey the fact that the function is to be used both for devices and partitions Would it not be cleaner to also pass the partition as a parameter instead of using $id? Are you sure that will always be set correctly? Ok, I'll separate the two Is it correct that a device gets unlocked if there are partitions on it that are still locked (partitions other than the current one being unlocked)? No, the partition and device locking are independent. So if you do something which locks the device (e.g. create a md-raid device using a partition from the device...once you've done that, the kernel won't let you repartition the underlying disk as its regarded as in use) you have to revert that for the device lock to be removed (that's the theory at least). In reality I'd guess that you'll have either device locks *or* partition locks in 99% of all cases. Regards, David -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: r37788 - in trunk/installer: debian
Frans Pop wrote: On Friday 02 June 2006 20:08, Joey Hess wrote: Log: * Workaround syslinux weirdness on hd-media images; when asked to boot 2.6/linux, it tries to boot 2.6/l. Rename files out of directories to avoid this; the gtk initrd has the unappitising name initrdg.gz. Is this new syslinux weirdness and a temporary workaround or is this an old problem? I could not find a BR against syslinux for the issue. I think it's an old problem, this is why we didn't put the 2.6 stuff in the same place as on the CDs before. -- see shy jo signature.asc Description: Digital signature
Processing of hw-detect_1.36_powerpc.changes
hw-detect_1.36_powerpc.changes uploaded successfully to localhost along with the files: hw-detect_1.36.dsc hw-detect_1.36.tar.gz ethdetect_1.36_all.udeb disk-detect_1.36_all.udeb hw-detect_1.36_powerpc.udeb archdetect_1.36_powerpc.udeb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
hw-detect_1.36_powerpc.changes ACCEPTED
Accepted: archdetect_1.36_powerpc.udeb to pool/main/h/hw-detect/archdetect_1.36_powerpc.udeb disk-detect_1.36_all.udeb to pool/main/h/hw-detect/disk-detect_1.36_all.udeb ethdetect_1.36_all.udeb to pool/main/h/hw-detect/ethdetect_1.36_all.udeb hw-detect_1.36.dsc to pool/main/h/hw-detect/hw-detect_1.36.dsc hw-detect_1.36.tar.gz to pool/main/h/hw-detect/hw-detect_1.36.tar.gz hw-detect_1.36_powerpc.udeb to pool/main/h/hw-detect/hw-detect_1.36_powerpc.udeb Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
On Jun 6, 2006, at 6:35 PM, Sven Luther wrote: On Tue, Jun 06, 2006 at 06:29:10PM -0400, Rick Thomas wrote: It's an oldworld Mac (beige G3) and I use MacOS-9/BootX as the bootloader, so I skipped the install quik bootloader step during the install (used continue without bootloader). That's probably why you aren't seeing anything in the logs about bootloader setup. This machine has a partition with sarge on it. Is it trying to do something with the 2.6.8 kernel from there? If so, why?!? Give me detailed instructions or a pointer to the correct part for me to RTFM, and I'll do the manual initrd generation tonight or tomorrow. How is your BootX configuration done, could it be that you copied or otherwise use the wrong ramdisk, namely the one from your sarge install ? Altough this one will presumably use initrd-tools, and not initramfs-tools. Friendly, Sven Luther That's one of the first things I thought of too. Unfortunately, the ramdisk and kernel in the BootX folder under MacOS-9 and in the /boot directory of the dead beta2 partition match up bit for bit. I used cmp to check. I re-did the boot of the beta2 kernel and initrd just to be sure. Same results. They are vmlinux--2.6.15-1-powerpc and initrd.img-2.6.15-1-powerpc. I've put them on the same web as the logfiles, if you want to take a look. Enjoy! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
On Wednesday 07 June 2006 05:58, Rick Thomas wrote: They are vmlinux--2.6.15-1-powerpc and initrd.img-2.6.15-1-powerpc. I've checked the initrd (it's a gzipped cpio archive) and there's nothing in there referring to 2.6.8 either. In the initrd: $ ls lib/modules/ 2.6.15-1-powerpc So there's no /lib/modules/2.6.8-powerpc/kernel/drivers/input/serio/i8042.ko to be inserted that could cause the error message you see. So I'm still voting for an error on your side and you're somehow booting your old 2.6.8 kernel or initrd. You really need to try and find some kind of explanation for the reference to 2.6.8 when you reboot. The puzzling thing is though that the other messages you copied initially show that it _is_ an initramfs initrd you're booting and d-i does not normally create an initramfs initrd for 2.6.8. Can you try booting with 'break=init'. This should give you a debug shell so you can check what kernel version is running and list the contents of the initrd that is being used. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: sarge3 kernel build r3
Martin Schulze wrote: It would be good if we would be able some day to release kernel updates in a more timely fashion and also not accumulate this many security updates in one update. However, due to the number of architectures and affected packages I'm not sure this goal can be met any time soon. But that's a different story... It will be possible for Etch, the linux-2.6 kernel packages can be autobuilt, which should reduce the overhead significantly. During the d-i bof at DebConf I pointed out that the sarge3 kernel build is in progress and is not an ABI change - there was consensus to wait for this build before doing the d-i build for r3. I don't remember the timeline we discussed for this build. The current status is that the build is complete and pending upload by the security team (I think Moritz would be the one to do it, so I've cc'd him). Oh. Great. Good to hear (err... sending such information to [EMAIL PROTECTED] would actually be a good idea as well...) I'm pretty sure I kept you posted. I dropped a note when I pushed out the Woody updates, but it was probably too terse. Sorry for that, I've been very busy over the last months. I'll process the 2.4.27 and 2.6.8 packages on the weekend. Wrt the ABI bump: At DebConf Dann and I agreed to omit one kernel security issue: A hard-too-trigger denial of service vulnerability in the experimental SCTP code. As there will most definitely be another ABI breaker soon, it wasn't worth all the work to cope with an ABI change. Cheers, Moritz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
On Jun 6, 2006, at 3:46 AM, Sven Luther wrote: reassign 370418 base-installer thanks On Tue, Jun 06, 2006 at 01:46:02AM +0200, Frans Pop wrote: reassign 370418 initramfs-tools thanks On Monday 05 June 2006 09:13, Rick Thomas wrote: Begin: Mounting root file system ... ... Begin: Running /scripts/local-top ... /scripts/local-top/lvm: 36 vgchange: not found Done. i8042.c: No controller found FATAL: Error inserting i8042 (/lib/modules/2.6.8-powerpc/kernel/ drivers/input/serio/i8042.ko): No such device ALERT! does not exist: Dropping to a shell! This looks like a initramfs-tools issue to me. Not sure, there is a serious problem here, and namely he is doing an etch beta install, but initramfs-tools somehow thinks there is a 2.6.8 sarge kernel after the reboot. It may be a initramfs-tools problem, but i may also well be a bug in the kernel-installer part of base-installer. The i8042.ko module is definitively part of both the 2.6.8 and the 2.6.16 powerpc kernels, and as thus the error is that initramfs-tools tries to use a non-working or non-existing kernel. Mmm, maybe this is related to sarge 2.6.8 kernel gaining a abi part ? Rick, can you send us a list of the dpkg -l of this system, and check exactly what did happen during the kernel installation. If you can provide us all the logs of the installation, or can do another one, it would be welcome. Friendly, Sven Luther Ops! Typo! The 2.6.8 in the (hand-typed) quotation above is actually 2.6.15-1 Boy! Is my face red! I'm *really* sorry for setting off a wild goose chase -- and then not catching it for more than 24 hours. I've reorganized the web where all the logfiles are. I've included stuff from /var/log in the dead filesystem. In particular, /var/log/ aptitude and /var/log/dpkg.log . I hope this helps in figuring out what's going on here. Sorry for the confusion! Rick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370418: failed Installation report for etch beta2 on oldworld PowerPC Mac (beige g3)
On Wednesday 07 June 2006 00:29, Rick Thomas wrote: Give me detailed instructions or a pointer to the correct part for me to RTFM, and I'll do the manual initrd generation tonight or tomorrow. info update-initramfs You need something like 'update-initramfs -v -u'. You may need to add the -k kernel-version option, and maybe the -t option. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
