Processing of iso-scan_1.33_i386.changes
iso-scan_1.33_i386.changes uploaded successfully to ftp-master.debian.org along with the files: iso-scan_1.33.dsc iso-scan_1.33.tar.gz iso-scan_1.33_all.udeb load-iso_1.33_all.udeb Greetings, Your Debian queue daemon (running on host ravel.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q0qz5-0006y4...@ravel.debian.org
Processing of iso-scan_1.33_i386.changes
iso-scan_1.33_i386.changes uploaded successfully to localhost along with the files: iso-scan_1.33.dsc iso-scan_1.33.tar.gz iso-scan_1.33_all.udeb load-iso_1.33_all.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q0qcb-0008hj...@franck.debian.org
iso-scan_1.33_i386.changes ACCEPTED into unstable
Accepted: iso-scan_1.33.dsc to main/i/iso-scan/iso-scan_1.33.dsc iso-scan_1.33.tar.gz to main/i/iso-scan/iso-scan_1.33.tar.gz iso-scan_1.33_all.udeb to main/i/iso-scan/iso-scan_1.33_all.udeb load-iso_1.33_all.udeb to main/i/iso-scan/load-iso_1.33_all.udeb Override entries for your package: iso-scan_1.33.dsc - source debian-installer iso-scan_1.33_all.udeb - optional debian-installer load-iso_1.33_all.udeb - extra debian-installer Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1q0qds-9s...@franck.debian.org
Bug#513924: marked as done (lvmcfg: Physical Extent (PE) size too small)
Your message dated Sat, 19 Mar 2011 09:42:18 + with message-id 201103190942.18499.el...@debianpt.org and subject line has caused the Debian Bug report #513924, regarding lvmcfg: Physical Extent (PE) size too small to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 513924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513924 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: important Debian-installer-version: Debian Lenny RC1 The default PE size is too small (4MB) for some use when creating volume groups (VG) with debian-installer. If you're dealing with large amounts of data, it is highly suggested to go for a larger extent size for performance reasons. 32MB is the default for RHEL and CentOS installers but the user has the possibility to choose another size. For this reason, I have to create volume groups from command line with the -s 32M option of vgcreate. Regards, Laurent -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- Closing as the installer is using the siggested default for lvm (4MB) and there is no impact on I/O performance. -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org ---End Message---
Bug#569107: marked as done (installation-reports: Problems with md raid metadata but otherwise ok)
Your message dated Sat, 19 Mar 2011 10:07:37 + with message-id 201103191007.37391.el...@debianpt.org and subject line has caused the Debian Bug report #569107, regarding installation-reports: Problems with md raid metadata but otherwise ok to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 569107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569107 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: normal -- Package-specific info: Boot method: CD Image version: Debian GNU/Linux testing Squeeze - Official Snapshot amd64 NETINST Binary-1 20100203-00:02 Date: Date and time of the install Machine: Asus P5QL-VM EPU, core2duo 2.8, 2GB RAM Partitions: df -Tl will do; the raw partition table is preferred Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[O] Comments/Problems: It all went smoothly, except that grub2 could not cope with the MD-RAID1 array, as it can't cope with metadata verions other than 0.9. A bit of web-searching led me to bug #554500 so I tried compiling grub2 with that patch on another machine and installing the resulting packages. No luck though, so I rebuilt the array, forcing it to use metadata version 0.9 and it all worked. Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to sub...@bugs.debian.org. == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION=Debian GNU/Linux installer DISTRIB_RELEASE=6.0 (squeeze) - installer build 20100202-00:00 X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux thor 2.6.30-2-amd64 #1 SMP Fri Sep 25 22:16:56 UTC 2009 x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 4 Series Chipset DRAM Controller [8086:2e20] (rev 03) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8336] lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e22] (rev 03) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8336] lspci -knn: 00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e23] (rev 03) lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:8336] lspci -knn: 00:1a.0 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4 [8086:3a37] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.1 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5 [8086:3a38] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.2 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6 [8086:3a39] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: 00:1a.7 USB Controller [0c03]: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2 [8086:3a3c] lspci -knn: Subsystem: ASUSTeK Computer Inc. Device [1043:82d4] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 1 [8086:3a40] lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.4 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 5 [8086:3a48] lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1c.5 PCI bridge [0604]: Intel Corporation 82801JI (ICH10 Family) PCI Express Root Port 6 [8086:3a4a] lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:1d.0
Bug#443962: marked as done (partman does not recognize existing partitions)
Your message dated Sat, 19 Mar 2011 10:28:53 + with message-id 201103191028.53540.el...@debianpt.org and subject line has caused the Debian Bug report #443962, regarding partman does not recognize existing partitions to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 443962: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=443962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: partman severity: important I am just trying to install debian to existing partitions of the harddisk of my laptop. However, the manual partitioning method only shows the whole Harddisk, and wants to create a new partition-table for the whole disk. This is true with the netinst-, as well as with the businesscard-CD-image, and it is also true when I use the expert boot option. Do you have an idea about a possible reason? Once more: When I enter into manual partition mode, I see one line corresponding to my harddrive only. This line shows the harddrive itself. It should display a list of partitions below this line, right? The laptop is from Gericom, the harddrive is a toshiba (40G). In another thread, I learned about a file that may be useful: /var/log/partman. How do I acess this file? Thanks alot for your help! Andreas ---End Message--- ---BeginMessage--- Fixed in parted. See #443962. ---End Message---
Bug#530909: marked as done (parted error message about device being busy doesn't work well)
Your message dated Sat, 19 Mar 2011 10:41:45 + with message-id 201103191041.45748.el...@debianpt.org and subject line has caused the Debian Bug report #530909, regarding parted error message about device being busy doesn't work well to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 530909: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: parted-udeb Version: 1.8.8.git.2008.03.24-11.1 I got the following message while installing with a daily image (maybe due to #530904): ┌┤ [!!] Partition disks ├─┐ │ │ │ Error informing the kernel about modifications to partition /dev/sda2 │ │ -- Device or resource busy. This means Linux won't know about any │ │ changes you made to /dev/sda2 until you reboot -- so you shouldn't │ │ mount it or use it in any way before rebooting. │ │ │ │ ERROR!!!│ │ │ │Ignore │ │Cancel │ │ │ │ Go Back │ │ │ └─┘ I'm not sure who displays this error message, but the error itself comes from parted. What's not great: - The ERROR!!! string that doesn't really say anything at all. - The choice Ignore and Cancel. I guess Ignore is go ahead and Cancel is go back, but there's a go back already. - When I press Go Back, it actually goes ahead to format the partition (which worked fine). -- Martin Michlmayr http://www.cyrius.com/ ---End Message--- ---BeginMessage--- Fixed in parted, see #558686. -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org ---End Message---
Processed: your mail
Processing commands for cont...@bugs.debian.org: retitle 539586 improve how partman reports the error when there is a critical_error() in parted_server Bug #539586 [partman-base] [s390] partman-base: fails ugly when ext4 is selected Changed Bug title to 'improve how partman reports the error when there is a critical_error() in parted_server' from '[s390] partman-base: fails ugly when ext4 is selected' thanks Stopping processing here. Please contact me if you need assistance. -- 539586: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539586 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13005328046708.transcr...@bugs.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: retitle 267727 [alpha] Installer creates partition (9th) which breaks the aboot installer Bug #267727 [partman-base] Alpha PC164SX debian installer report Bug #274926 [partman-base] aboot install fails Changed Bug title to '[alpha] Installer creates partition (9th) which breaks the aboot installer' from 'Alpha PC164SX debian installer report' Changed Bug title to '[alpha] Installer creates partition (9th) which breaks the aboot installer' from 'aboot install fails' retitle 274926 [alpha] /target/sbin/swriteboot: partition number must be in range 1-8 Bug #274926 [partman-base] [alpha] Installer creates partition (9th) which breaks the aboot installer Bug #267727 [partman-base] [alpha] Installer creates partition (9th) which breaks the aboot installer Changed Bug title to '[alpha] /target/sbin/swriteboot: partition number must be in range 1-8' from '[alpha] Installer creates partition (9th) which breaks the aboot installer' Changed Bug title to '[alpha] /target/sbin/swriteboot: partition number must be in range 1-8' from '[alpha] Installer creates partition (9th) which breaks the aboot installer' thanks Stopping processing here. Please contact me if you need assistance. -- 274926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274926 267727: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=267727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130053373510308.transcr...@bugs.debian.org
Re: Re: UNable to reload package states from mirrors
login as root gpg --keyserver pgp.mit.edu --recv-keys AED4B06F473041FA gpg --armor --export AED4B06F473041FA | apt-key add - apt-get update and run the above line -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d84a0c4.8010...@blueyonder.co.uk
d-i location on mirrors
Heyho, todays Squeeze Point Release made on thing obvious: The location of the installer files on the mirrors in dists/ is somewhat crap. What happens at point release time (provided a d-i update is included) is that the mirror sync goes and deletes the installer files from the proposed-updates directory and then goes to transfer them all again into the stable directory. That is a 2GB transfer thats entirely unneeded. What I want to do now is to go and put all the installer-* directories into /d-i/ on our mirrors. The directories in dists/$SUITE would only contain symlinks for their version over to the ones in /d-i/. Basically, the idea behind pool/ all over, just for d-i. As far as I can see this should be possible to get implemented now without causing any trouble, as we keep all the current places alive (using symlinks), but I wanted to confirm with you that this is really the case and I don't miss anything important in d-i. If you don't have anything, I would want to change the stuff during the meeting next week. -- bye, Joerg GyrosGeier I've annoyed Ganneff enough with that package already, no reason to top it off by a build-depend on emacs for writing control files pgpvmL7Do7Rz5.pgp Description: PGP signature
Bug#618915: tasksel: Should provide an easy way to choose the selected desktop environment
Package: tasksel Version: 2.89 Severity: normal Hello, Currently, the easy way (that is, not expert-mode install) to select e.g. the KDE desktop to be installed from a netboot image is at the boot menu to enter advanced options, then alternative desktop environments. This looks quite hairy, to say the least. People usually expect to be given the choice at installation, I've seen complaints here and there that Debian doesn't easily provide the choice. One way to do it is to simply enable the desktop question, which, yes, makes one more question during installation, but users will probably find it critical: people are usually used to either gnome or KDE, and thus want the one they're used to. And people who simply want to get X working without a complete desktop (because they're using fvwm or such) will be happy to easily select LXDE or XFCE. If they don't know, well, they can default to gnome, that's fine. Another way to do it, which may be better, is to replace the Desktop task with Gnome desktop, KDE desktop, etc. The benefit is that you can then install several desktops, for the case of a machine used by several users with different habits. Samuel -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tasksel depends on: ii aptitude 0.6.3-3.2 terminal-based package manager (te ii cdebconf [debconf-2.0]0.153 Debian Configuration Management Sy ii debconf [debconf-2.0] 1.5.38 Debian configuration management sy ii liblocale-gettext-perl1.05-6 Using libc functions for internati ii tasksel-data 2.89 Official tasks used for installati tasksel recommends no packages. tasksel suggests no packages. -- debconf information: tasksel/title: tasksel/desktop: gnome tasksel/first: Laptop, Standard system tasksel/tasks: Print server, Mail server, SSH server, Laptop -- Samuel Thibault samuel.thiba...@fnac.net void packerFlushTheToiletFirstThingInTheMorning( void* arg ) -+- chromium's source code -+- -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110319145638.ga30...@const.famille.thibault.fr
Bug#618920: debootstrap: needs more robust download error handling
package: debootstrap
version: 1.0.28
severity: important
tags: patch
debootstrap's current download error handling isn't very robust. It
declares success just for the presence of a downloaded file, which may
be a partial download, or one for which the checksum doesn't match.
Eventually those conditions will lead to unhandled failures elsewhere
within debootstrap.
This can make d-i very rocky on certain mirrors since one bad package
download ultimately lead to a complete failure of the debootstrap
process, and thus a failed install. An expert can recover from this,
but an average user will get rather frustrated (especially since the
dialogs for debootstrap errors are rather confusing).
It may also be useful to expand a bit on these d-i debootstrap error
messages: when an error happens, the right answer that the user wants is
to hit 'go back' twice in a row to start the debootstrap all over again,
but the dialogs are confusing, and 'continue' seems to be the obvious
choice, but that will lead to the broken debootstrap continuing to
completion with various brokenness. Anyway, that maybe should be
submitted as another bug.
So, back to the original issue, I've created a patch that will retry
downloads whenever anything in the get routine fails, which I
believe is much more robust than the current situation. Please see
attached patch.
Best wishes,
Mike
--- newhd/source/debootstrap-1.0.28/functions 2011-02-21 19:25:08.0 -0500
+++ /usr/share/debootstrap/functions 2011-03-19 10:58:57.0 -0400
@@ -1,3 +1,5 @@
+MAXATTEMPTS=10
+
### smallutils
smallyes() {
@@ -241,6 +243,13 @@
}
get () {
+ for iters in $(seq 1 $MAXATTEMPTS); do
+ if single_get $@; then break; fi
+ warning RETRYING Retrying failed download.
+ done
+}
+
+single_get () {
# args: from dest 'nocache'
# args: from dest [checksum size] [alt {checksum size type}]
local displayname
@@ -331,13 +340,6 @@
# http/ftp mirror
if wgetprogress -O $dest $from; then
return 0
- elif [ -s $dest ]; then
- local iters=0
- while [ $iters -lt 3 ]; do
-warning RETRYING Retrying failed download of %s $from
-if wgetprogress -c -O $dest $from; then break; fi
-iters=$(($iters + 1))
- done
else
rm -f $dest
return 1
@@ -346,13 +348,6 @@
# http/ftp mirror
if wgetprogress $CHECKCERTIF $CERTIFICATE $PRIVATEKEY -O $dest $from; then
return 0
- elif [ -s $dest ]; then
- local iters=0
- while [ $iters -lt 3 ]; do
-warning RETRYING Retrying failed download of %s $from
-if wgetprogress $CHECKCERTIF $CERTIFICATE $PRIVATEKEY -c -O $dest $from; then break; fi
-iters=$(($iters + 1))
- done
else
rm -f $dest
return 1
Re: d-i location on mirrors
* Joerg Jaspert jo...@ganneff.de [110319 15:16]: What I want to do now is to go and put all the installer-* directories into /d-i/ on our mirrors. The directories in dists/$SUITE would only contain symlinks for their version over to the ones in /d-i/. Do all the official Debian mirrors support symlinks? * Joerg Jaspert jo...@ganneff.de [110319 15:44]: the thread around it will be on -boot, but now you got it directly too. Will debmirror/reprepro be able to deal with the change? Reprepro only mirrors packages, so only looks at dists/N/C/debian-installer/ stuff and gets the udebs. This it should not be affected by your proposal, if I understand it correctly. With my reprepro author hat on, the installer-* stuff is only a nuisance making it more hard to have a tidy dists/ dir. (Which is one of the rough edges in reprepro, it only ever adds stuff to dists/ and never deletes it but leaves that to the user). Thanks for asking, Bernhard R. Link -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110319152904.ga5...@pcpool00.mathematik.uni-freiburg.de
Re: d-i location on mirrors
Joerg Jaspert wrote: If you don't have anything, I would want to change the stuff during the meeting next week. debmirror will probably use the symlinks, and store the files where they are now. -- see shy jo signature.asc Description: Digital signature
Bug#615985: installation-reports: PowerPC netinst image: Debootstrap Error
On Mon, 14 Mar 2011 19:27:24 + Miguel Figueiredo el...@debianpt.org wrote: Hi, in the installation log may be more information on what happened. Can you take a look and also send it (gzipped) ? Tested again with a newer image: be53803c6649587722d8d32e76149426 debian-testing-powerpc-netinst.iso Date: 19-Mar-2011 10:28 And the installation completed without a hitch, so I guess this bug can be closed, along with: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=543267 And maybe also this one can be closed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572897 I am going to submit another installation report for the successful install, with some suggestions about Debian on PS3. Thanks a lot, Antonio -- Antonio Ospite http://ao2.it PGP public key ID: 0x4553B001 A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? pgpSMBMvOTO4B.pgp Description: PGP signature
Bug#618920: debootstrap: needs more robust download error handling
I probably should have mentioned that these errors are much more likely within d-i for some reason. The best way to reproduce this is to do an installation up through partitioning, then do: $ debootstrap wheezy /target/wheezy-chroot http://snapshot.debian.org/archive/debian/20110318T093210Z At least a few package downloads should fail from that mirror, and they'll be different every time. Executing the same command in a full system seems to work fine for that exact same mirror, so maybe its some other variability within d-i that is the cause of this issue. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTinic9TK-G7pu+=a5aafaboifjhzhwhirebns...@mail.gmail.com
Bug#572897: marked as done (PS3 installation with d-i daily image as of March 07, 2010)
Your message dated Sat, 19 Mar 2011 16:22:06 +
with message-id 201103191622.06314.el...@debianpt.org
and subject line
has caused the Debian Bug report #572897,
regarding PS3 installation with d-i daily image as of March 07, 2010
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
572897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Boot method: petitboot
Image version:
http://d-i.debian.org/daily-images/powerpc/daily/powerpc64/netboot/{vmlinux,initrd.gz}
Date: Sun, 07 Mar 2010 14:57:08 +0100
Machine: Sony Playstation 3
Partitions: 10Gb partition for OtherOS
Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
Initial boot: [O]
Detect network card:[ ]
Configure network: [ ]
Detect CD: [ ]
Load installer modules: [ ]
Detect hard drives: [ ]
Partition hard drives: [ ]
Install base system:[ ]
Clock/timezone setup: [ ]
User/password setup:[ ]
Install tasks: [ ]
Install boot loader:[ ]
Overall install:[ ]
Comments/Problems:
The installer seems to boot fine, and presents its initial menu.
However, the attached USB keyboard isn't functional at that point,
making further installation impossible.
I understand that petitboot, the bootloader i used, is just a regular
linux system. The keyboard works flawlessly with petitboot, so I'm
assuming debian-installer is at fault here.
--
BOFH excuse #253:
We've run out of licenses
signature.asc
Description: Digital signature
---End Message---
---BeginMessage---
Tested and now working with current images, see #615985.
---End Message---
Bug#615985: marked as done (installation-reports: PowerPC netinst image: Debootstrap Error)
Your message dated Sat, 19 Mar 2011 16:22:06 + with message-id 201103191622.06314.el...@debianpt.org and subject line has caused the Debian Bug report #615985, regarding installation-reports: PowerPC netinst image: Debootstrap Error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 615985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=615985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Severity: grave Tags: d-i Justification: renders package unusable -- Package-specific info: Boot method: CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/powerpc/iso-cd/debian-testing-powerpc-netinst.iso (01-Mar-2011 10:23) Date: 01-Mar-2011 14:00 Machine: Sony PS3 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: [ ] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[E] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: The Install Base System task fails with this message: Debootstrap Error: Invalid Release file: no entry for main/binary-powerpc/Packages And in syslog I get: Mar 1 14:35:35 main-menu[234]: INFO: Menu item 'bootstrap-base' selected Mar 1 14:45:28 base-installer: error: exiting on error base-installer/debootstrap-failed Mar 1 14:45:30 main-menu[234]: WARNING **: Configuring 'bootstrap-base' failed with error code 30 Mar 1 14:45:30 main-menu[234]: WARNING **: Menu item 'bootstrap-base' failed. I added some debug output to /var/lib/dpkg/info/bootstrap-base.postinst and the actual bootstrap command is: log-output -t debootstrap run-debootstrap --components-main \ --debian-installer --resolve-deps wheezy /target file:///cdrom/ As a workaround, if the file:///cdrom/ argument is removed the installation completes fine, but I guess that is just because the installer is downloading everything from the net, right? Any idea of what is going on? Thanks, Antonio -- Antonio Ospite http://ao2.it PGP public key ID: 0x4553B001 A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? uname -a: Linux ps3 2.6.37-1-powerpc64 #1 SMP Tue Feb 15 22:31:08 UTC 2011 ppc64 GNU/Linux usb-list: usb-list: Bus 01 Device 01: PS3 EHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 2.6.37-1-powerpc64 ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 01 Device 02: USB2.0 Hub [05e3:0607] usb-list:Level 01 Parent 01 Port 01 Class 09(hub ) Subclass 00 Protocol 02 usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 02 Driver hub usb-list: usb-list: Bus 01 Device 03: Wireless Keyboard/Mouse [099a:7202] usb-list:Level 02 Parent 02 Port 00 Class 00(ifc ) Subclass 00 Protocol 00 usb-list:Interface 00: Class 03(HID ) Subclass 01 Protocol 01 Driver usbhid usb-list:Interface 01: Class 03(HID ) Subclass 01 Protocol 02 Driver usbhid usb-list: usb-list: Bus 02 Device 01: PS3 EHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 2.6.37-1-powerpc64 ehci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 02 Device 02: Bluetooth Transceiver [054c:0267] usb-list:Level 01 Parent 01 Port 01 Class e0(wlcon) Subclass 01 Protocol 01 usb-list:Manufacturer: Sony usb-list:Interface 00: Class e0(wlcon) Subclass 01 Protocol 01 Driver none usb-list:Interface 01: Class e0(wlcon) Subclass 01 Protocol 01 Driver none usb-list:Interface 02: Class e0(wlcon) Subclass 01 Protocol 01 Driver none usb-list:Interface 03: Class fe(app. ) Subclass 01 Protocol 00 Driver none usb-list: usb-list: Bus 03 Device 01: PS3 OHCI Host Controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 00 usb-list:Manufacturer: Linux 2.6.37-1-powerpc64 ohci_hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 04 Device 01: PS3 OHCI Host Controller [1d6b:0001] usb-list:Level 00 Parent 00 Port 00
Bug#618927: busybox-udeb: provide seq
package: busybox-udeb version: 1.18.4-1 severity: normal It would be nice if busybox-udeb provided seq for use in d-i scripts. See bug #618920 for one particular case where I would like to use it. That code of course could be rewritten to avoid the use of seq, but its so much cleaner with it. Thanks, Mike -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110319123935.7c5d7e60.michael.s.gilb...@gmail.com
Processed: your mail
Processing commands for cont...@bugs.debian.org: retitle 617469 PowerPC does not boot - framebuffer issue Bug #617469 [installation-reports] installation-report: Debian sid_d-i wheezy PowerPC businesscard does not boot Changed Bug title to 'PowerPC does not boot - framebuffer issue' from 'installation-report: Debian sid_d-i wheezy PowerPC businesscard does not boot' reassign 617469 linux-2.6 Bug #617469 [installation-reports] PowerPC does not boot - framebuffer issue Bug reassigned from package 'installation-reports' to 'linux-2.6'. Bug No longer marked as found in versions 2.44. fixed 617469 2.6.38~rc7-1~experimental.1 Bug #617469 [linux-2.6] PowerPC does not boot - framebuffer issue There is no source info for the package 'linux-2.6' at version '2.6.38~rc7-1~experimental.1' with architecture '' Unable to make a source version for version '2.6.38~rc7-1~experimental.1' Bug Marked as fixed in versions 2.6.38~rc7-1~experimental.1. thanks Stopping processing here. Please contact me if you need assistance. -- 617469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130055329426369.transcr...@bugs.debian.org
Bug#614385: marked as done (installation-reports: [sparc] Debian 6.0r0 installation on SunFire T1000 via netboot)
Your message dated Sat, 19 Mar 2011 17:06:06 +
with message-id 201103191706.06566.el...@debianpt.org
and subject line
has caused the Debian Bug report #614385,
regarding installation-reports: [sparc] Debian 6.0r0 installation on SunFire
T1000 via netboot
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
614385: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: installation-reports
Severity: wishlist
Tags: d-i
Hi,
-- Package-specific info:
Boot method: network
Image version: sparc boot.img from 2011-01-17
Date: 2011-02-21
Machine: SunFire T1000
Partitions: df -Tl will do; the raw partition table is preferred
FilesystemType 1K-blocks Used Available Use% Mounted on
/dev/sda2 ext373521984931552 71096548 2% /
tmpfstmpfs 4082168 0 4082168 0% /lib/init/rw
varrun tmpfs 408216872 4082096 1% /var/run
varlock tmpfs 4082168 0 4082168 0% /var/lock
udev tmpfs 4077576 216 4077360 1% /dev
tmpfstmpfs 4082168 0 4082168 0% /dev/shm
/dev/sda1 ext2 90329 12943 75459 15% /boot
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: [ ]
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:
Description of the install, in prose, and any thoughts, comments
and ideas you had during the initial install.
My first attempt to install Debian 6.0 has failed with Kernel panic -
not syncing: Attempted to kill the idle task!. After upgrading the
device firmware using Sun_System_Firmware-6_7_11-Sun_Fire_T1000.bin
the installation was a success.
http://lists.debian.org/debian-sparc/2011/02/msg00017.html
The boot environment was set with:
{4} ok setenv network-boot-arguments host-ip=x.y.z.4,
router-ip=x.y.z.1,
subnet-mask=255.255.255.240,
hostname=sun.DOMAIN.com,
file=tftp://x.y.z.37/boot.img
(everything in one line and no white spaces)
The complete boot command was:
{0} ok boot net DEBIAN_FRONTEND=text video=atyfb:offa \
cdrom-detect/eject=false netcfg/disable_dhcp=true modules=network-console
Other minor observations:
- the installer asked for tg3 firmare files but the network was working
without them anyway;
- using net1 (instead of net/net0) the connection didn't worked properly
for DNS resolution (for hostname/domain) and Debian mirror scan;
- no logon console was available over the serial terminal (the only one
available for headless SPARC systems).
Thanks
--
Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.
Once you have filled out this report, mail it to sub...@bugs.debian.org.
==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0 (squeeze) - installer build 20110106+b1
X_INSTALLATION_MEDIUM=netboot
==
Installer hardware-summary:
==
uname -a: Linux sundance 2.6.32-5-sparc64 #1 Fri Dec 10 16:11:52 UTC 2010
sparc64 GNU/Linux
lspci -knn: 0001:02:00.0 PCI bridge [0604]: Broadcom EPB PCI-Express to PCI-X
Bridge [1166:0103] (rev b3)
lspci -knn: 0001:03:04.0 Ethernet controller [0200]: Broadcom Corporation
NetXtreme BCM5714 Gigabit Ethernet [14e4:1668] (rev a2)
lspci -knn: Subsystem: Oracle Corporation Device [108e:1668]
lspci -knn: Kernel driver in use: tg3
lspci -knn: 0001:03:04.1 Ethernet controller [0200]: Broadcom Corporation
NetXtreme BCM5714 Gigabit Ethernet [14e4:1668] (rev a2)
lspci -knn: Subsystem: Oracle Corporation Device [108e:1668]
lspci -knn: Kernel driver in use: tg3
lspci -knn: 0001:03:08.0 PCI bridge [0604]: Broadcom BCM5785 [HT1000] PCI/PCI-X
Bridge [1166:0104] (rev b3)
lspci -knn: 0001:04:01.0 Ethernet controller [0200]: Broadcom Corporation
NetXtreme BCM5704 Gigabit Ethernet [14e4:1648] (rev 10)
lspci -knn: Subsystem: Oracle Corporation Device [108e:1648]
lspci -knn: Kernel driver in
Re: d-i location on mirrors
On 2011-03-19, Joey Hess jo...@debian.org wrote: Joerg Jaspert wrote: If you don't have anything, I would want to change the stuff during the meeting next week. debmirror will probably use the symlinks, and store the files where they are now. Is this also true for the rsync method? Kind regards Philipp Kern -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/slrnio9pr0.heu.tr...@kelgar.0x539.de
Re: d-i location on mirrors
* Joerg Jaspert jo...@ganneff.de [2011-03-19 15:16]: What I want to do now is to go and put all the installer-* directories into /d-i/ on our mirrors. How about installer/*/ instead? Not everyone knows what d-i stands for. -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110319174339.gn31...@jirafa.cyrius.com
Bug#618929: Debian bootup/install bug report
Package: Installer Problem: Will not boot after installation System: ~2000 vintage HP Vecta XU, 6/200, system D4365N, dual Pentium II processors, 64 MB RAM, three hard drives - 200G IDE, two 1.3 G SCSI (Quantum Fireball), network card, no USB The most common outcome of an installation session is that the bootup step at the end of the session results in the letters GRUB appearing in the upper left corner of the screen with the blinking cursor to the right of the B, and nothing else. The system does not respond to any keystrokes, or combination of CTRL-key, ALT-key, etc. It seems like the system is waiting for keyboard input, but the keyboard is not enabled. If I had a responsive keyboard AND I knew what to type, this could be an acceptable outcome, since it does occur most times. What I've tried: All combinations of discs (all three drives plugged in, each one separately, all combinations of two drives). The drives all appear to be accessed but the boot ultimately fails as described above. I've tried most combinations of answering the partitioning questions and placement of the boot sector. The failures are not all as stated above; it's just the most common outcome. Other results are GRUB being continuously written to the screen, until I power off. I was able to get the boot to succeed once, but that particular system build led to other problems causing me to attempt a second install. This one time the result was that the system would, after powering on and all the verbiage of the boot up process, presents me with a login prompt, accepts my login and allows me to use the system. I was able to run with this system for a couple of weeks, loading packages, etc. until I filled the discs and had to start over. The disc full issue occurred because the IDE drive (most of the system's capacity) was not mounted. I did not realize this until the disc full failure. The version of Debian is 2.4. I have a 15 CD set, purchased in roughly 2004. Last week I downloaded disc image 1 of Debian 6.0 in hopes that the boot problem has been fixed, but the results are the same. Thanks, Mike Tremblay
Processed: Re: Bug#618929: Debian bootup/install bug report
Processing commands for cont...@bugs.debian.org: reassign 618929 installation-reports Bug #618929 [installer] Debian bootup/install bug report Warning: Unknown package 'installer' Bug reassigned from package 'installer' to 'installation-reports'. -- Stopping processing here. Please contact me if you need assistance. -- 618929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13005567307629.transcr...@bugs.debian.org
Bug#618927: busybox-udeb: provide seq
severity 618927 wishlist thanks 19.03.2011 19:39, Michael Gilbert wrote: package: busybox-udeb version: 1.18.4-1 severity: normal It would be nice if busybox-udeb provided seq for use in d-i scripts. See bug #618920 for one particular case where I would like to use it. That code of course could be rewritten to avoid the use of seq, but its so much cleaner with it. Yes, udeb flavour lacks quite a few commands which should be there. We're going that direction, hopefully ;) And yes, seq is one of the applets I thought about enabling, too. Hopefully it will be in the next release. Thanks! /mjt -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d84ee1f.30...@msgid.tls.msk.ru
Processed: Bug#618927: busybox-udeb: provide seq
Processing commands for cont...@bugs.debian.org: severity 618927 wishlist Bug #618927 [busybox-udeb] busybox-udeb: provide seq Severity set to 'wishlist' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 618927: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130055747211503.transcr...@bugs.debian.org
Bug#618929: Debian bootup/install bug report
Hi, A Sábado 19 Março 2011 17:07:24 Mike Tremblay você escreveu: Package: Installer Problem: Will not boot after installation System: ~2000 vintage HP Vecta XU, 6/200, system D4365N, dual Pentium II processors, 64 MB RAM, three hard drives - 200G IDE, two 1.3 G SCSI (Quantum Fireball), network card, no USB The most common outcome of an installation session is that the bootup step at the end of the session results in the letters GRUB appearing in the upper left corner of the screen with the blinking cursor to the right of the B, and nothing else. The system does not respond to any keystrokes, or combination of CTRL-key, ALT-key, etc. It seems like the system is waiting for keyboard input, but the keyboard is not enabled. If I had a responsive keyboard AND I knew what to type, this could be an acceptable outcome, since it does occur most times. [...] Please check the installation report for any errors during installation. Please extract the installation report [1] in the end of installation and send a copy (gzipped). What image heve you used for installation? [1] - /var/log/installer/syslog -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103191807.05178.el...@debianpt.org
Re: d-i location on mirrors
What I want to do now is to go and put all the installer-* directories into /d-i/ on our mirrors. The directories in dists/$SUITE would only contain symlinks for their version over to the ones in /d-i/. Do all the official Debian mirrors support symlinks? Otherwise they would be lost with the current symlink already. All the mirrors using ftpsync wont care about this change. Reprepro only mirrors packages, so only looks at dists/N/C/debian-installer/ stuff and gets the udebs. This it should not be affected by your proposal, if I understand it correctly. Right. With my reprepro author hat on, the installer-* stuff is only a nuisance making it more hard to have a tidy dists/ dir. (Which is one of the rough edges in reprepro, it only ever adds stuff to dists/ and never deletes it but leaves that to the user). Well. This change is step1 in getting it out of there. Maybe at some point we wont even have the symlinks anymore. (But I don't care too much about that, actually) -- bye, Joerg HE liw: Ah, but now I'm old enough, so can I adopt your sex? HE liw: Or do I need to hijack it? -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87wrjukh7q@gkar.ganneff.de
Re: d-i location on mirrors
On 12424 March 1977, Joey Hess wrote: If you don't have anything, I would want to change the stuff during the meeting next week. debmirror will probably use the symlinks, and store the files where they are now. So it works, which is good. -- bye, Joerg Oh, so they have internet on computers now! -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87sjuij2kn@gkar.ganneff.de
Re: d-i location on mirrors
What I want to do now is to go and put all the installer-* directories into /d-i/ on our mirrors. How about installer/*/ instead? Not everyone knows what d-i stands for. Fine. -- bye, Joerg maxx Aqua mach mal man brain Aquariophile maxx: schon probiert das gibts ned -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87oc56j2k2@gkar.ganneff.de
Bug#587658: marked as done (Won't recognize the Broadcom BCM57780 Gigabit Ethernet PCIe)
Your message dated Sat, 19 Mar 2011 22:57:51 + with message-id 201103192257.51125.el...@debianpt.org and subject line has caused the Debian Bug report #587658, regarding Won't recognize the Broadcom BCM57780 Gigabit Ethernet PCIe to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 587658: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: Netinstall CD Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso Date: 30 June 2010 1100hrs Machine: Dell Precision T1500 Processor: Memory: Partitions:df -Tl will do; the raw partition table is preferred Output of lspci -knn (or lspci -nn): Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[E] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Won't recognize the Broadcom BCM57780 Gigabit Ethernet PCIe device (although lspci does). I found this bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574888 which indicates the problem will be fixed when the installer uses the linux-2.6.32-11 kernel. I don't know how to find an installer that uses this kernel, so in the meanwhile, I have a totally useless brand new computer. Any help? Thanks! -- Kent West*))) http://kentwest.blogspot.com Praise Yah! \o/ ---End Message--- ---BeginMessage--- Fixed in linux-2.6 2.6.32-11 ---End Message---
Bug#614912: (no subject)
Please test and give feedback with the daily images [1]. 1 - http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso -- Melhores cumprimentos/Best regards, Miguel Figueiredo http://www.DebianPT.org -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201103192327.57594.el...@debianpt.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: retitle 606697 wrong keymap during installation in french on virtualbox Bug #606697 [installation-reports] installation-reports: install succes in virtualbox with M-A DVD iso Changed Bug title to 'wrong keymap during installation in french on virtualbox' from 'installation-reports: install succes in virtualbox with M-A DVD iso' # seems to be a post installation issue, reassigning to wicd, whose team may have a clue on what's happening reassign 616442 wicd Bug #616442 [installation-reports] installation-report: wlan configuration during installation brakes wicd Bug reassigned from package 'installation-reports' to 'wicd'. Bug No longer marked as found in versions 2.44. reassign 616051 gdm3 Bug #616051 [installation-reports] no root account after installation Bug reassigned from package 'installation-reports' to 'gdm3'. Bug No longer marked as found in versions 6.0.0. retitle 614806 [nouveaufb] boots into 1024x768 framebuffer text mode beyond the limits of VGA monitor (800x600) Bug #614806 [installation-reports] installation-reports: Installed system boots into hi-res framebuffer text mode beyond the limits of VGA monitor Changed Bug title to '[nouveaufb] boots into 1024x768 framebuffer text mode beyond the limits of VGA monitor (800x600)' from 'installation-reports: Installed system boots into hi-res framebuffer text mode beyond the limits of VGA monitor' reassign 614806 linux-2.6 Bug #614806 [installation-reports] [nouveaufb] boots into 1024x768 framebuffer text mode beyond the limits of VGA monitor (800x600) Bug reassigned from package 'installation-reports' to 'linux-2.6'. thanks Stopping processing here. Please contact me if you need assistance. -- 614806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614806 616051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616051 606697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606697 616442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.130057898227608.transcr...@bugs.debian.org
Re: Stopping d-i pulling in virtualbox-ose-guest packages
On 1 March 2011 16:11, Joey Hess jo...@debian.org wrote: Jonathan Matthews wrote: I can't find a way of getting squeeze's (i386) netinst to install inside virtualbox without pulling in 3 virtualbox-ose-guest-* packages: So, these are pulled in by the discover package, particularly by discover-pkginstall. I don't see any way to disable it by preseeding. While discover uses the discover/install_hw_packages debconf question, it uses it in a way that ignores preseeding. (This is easily a bug.) Thanks for this - appreciated. I'll file a bug for this behaviour. Could anyone comment on how a request for a discover blacklist debconf question would be viewed? I'm thinking that it might be productive to be able to communicate let discover do what it likes, as hwdiscovery is its forte, but I *know* I don't want to install anything matching $REGEX. The only option I see for now is to use preseed/early_command to rm /usr/lib/pre-pkgsel.d/20install-hwpackages For the list archives: this worked under 6.0.0 (tested on i386) but now, post-6.0.1 release, on both 64- and 32-bit 6.0.0 PXE installers (with subsequent packages pulled during the install from a (presumably) updated 6.0.1 mirror) it fails to have the desired affect. It appears that preseed/early_command may be running before the installer has created /usr/lib/pre-pkgsel.d/20install-hwpackages. I'm not sure if that's a bug. The workaround I'm using successfully at the moment is: d-i preseed/early_command string \ echo -e '#! /bin/sh\necho /usr/lib/pre-pkgsel.d/20install-hwpackages' \ /usr/lib/pre-pkgsel.d/19remove-install-hwpackages; \ chmod 755 /usr/lib/pre-pkgsel.d/19remove-install-hwpackages Ugly, but it works. Regards, Jonathan -- Jonathan Matthews London, UK http://www.jpluscplusm.com/contact.html -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktik7r+egpko_kkvz4x0lrkx9s+97jrpx49ro6...@mail.gmail.com
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * OLD BUILD:amd64 Mar 18 00:10 buildd@barber build_cdrom_isolinux http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log * OLD BUILD:amd64 Mar 18 00:10 buildd@barber build_cdrom_gtk http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log * OLD BUILD:amd64 Mar 18 00:10 buildd@barber build_cdrom-xen http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log * OLD BUILD:amd64 Mar 18 00:11 buildd@barber build_netboot http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log * OLD BUILD:amd64 Mar 18 00:14 buildd@barber build_netboot-gtk http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log * OLD BUILD:amd64 Mar 18 00:15 buildd@barber build_netboot-xen http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log * OLD BUILD:amd64 Mar 18 00:18 buildd@barber build_hd-media http://d-i.debian.org/daily-images/amd64/daily/build_hd-media.log * OLD BUILD:amd64 Mar 18 00:18 buildd@barber build_hd-media_gtk http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log * FAILED BUILD: armel Mar 19 21:54 joey@box build_iop32x_netboot http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_netboot.log * FAILED BUILD: armel Mar 19 21:58 joey@box build_iop32x_network-console_glantank http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_network-console_glantank.log * FAILED BUILD: armel Mar 19 22:01 joey@box build_iop32x_network-console_n2100 http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_network-console_n2100.log * FAILED BUILD: armel Mar 19 22:04 joey@box build_iop32x_network-console_ss4000e http://people.debian.org/~joeyh/d-i/armel/images/daily/build_iop32x_network-console_ss4000e.log * FAILED BUILD: armel Mar 19 22:08 joey@box build_ixp4xx_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_ixp4xx_network-console.log * FAILED BUILD: armel Mar 19 22:37 joey@box build_kirkwood_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_kirkwood_network-console.log * FAILED BUILD: armel Mar 19 22:40 joey@box build_orion5x_network-console http://people.debian.org/~joeyh/d-i/armel/images/daily/build_orion5x_network-console.log * FAILED BUILD: hppa Mar 19 06:02 didaily@c3700 build_cdrom http://d-i.debian.org/daily-images/hppa/daily/build_cdrom.log * FAILED BUILD: hppa Mar 19 06:02 didaily@c3700 build_netboot http://d-i.debian.org/daily-images/hppa/daily/build_netboot.log * FAILED BUILD: hppa Mar 19 06:03 didaily@c3700 build_miniiso http://d-i.debian.org/daily-images/hppa/daily/build_miniiso.log * OLD BUILD:ia64 Mar 17 00:14 buildd@alkman build_cdrom http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log * OLD BUILD:ia64 Mar 17 00:17 buildd@alkman build_netboot http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log * FAILED BUILD: kfreebsd-amd64 Mar 20 00:11 buildd@fano build_cdrom http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_cdrom.log * FAILED BUILD: kfreebsd-amd64 Mar 20 00:11 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * daily mipsel images build: The build daemon responsible for these builds is currently moving to a new hosting location. Daily builds should be available again within the first two weeks of 2011. * OLD BUILD:powerpc Mar 18 00:06 buildd@praetorius build_powerpc_cdrom http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_cdrom.log * OLD BUILD:powerpc Mar 18 00:09 buildd@praetorius build_powerpc_netboot http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_netboot.log * OLD BUILD:powerpc Mar 18 00:14 buildd@praetorius build_powerpc_netboot-gtk http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_netboot-gtk.log * OLD BUILD:powerpc Mar 18 00:16 buildd@praetorius build_powerpc_hd-media http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_hd-media.log * OLD BUILD:powerpc Mar 18 00:18 buildd@praetorius build_powerpc64_cdrom http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc64_cdrom.log * OLD BUILD:powerpc Mar 18 00:21 buildd@praetorius build_powerpc64_netboot http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc64_netboot.log * OLD BUILD:powerpc Mar 18 00:25 buildd@praetorius build_powerpc64_netboot-gtk
Re: d-i location on mirrors
On Sat, Mar 19, 2011 at 11:16, Joerg Jaspert jo...@ganneff.de wrote: If you don't have anything, I would want to change the stuff during the meeting next week. I think the idea is nice but as Martin suggested I prefer installer over d-i since d-i is meanless for new users. -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/AANLkTi=dulq4-or1h5ivcjhyq+5ut93tf3jf0ewln...@mail.gmail.com
