Bug#614504: Can't install debian 6.0 on a Dell optiplex gx110
It works! I simply removed the quiet option, and I encountered no other problem during the installation process. Thanks. -- 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/1299404941.2291.7.camel@trantor
Bug#616522: GeoMirror (aka cdn.debian.net) as default mirror in standard installation?
On Sat, Mar 5, 2011 at 10:30, Holger Levsen hol...@layer-acht.org wrote: Hi, On Samstag, 5. März 2011, Christian PERRIER wrote: I think it should be used, but IMO it should become cdn.debian._org_ first, at least for stable. For sid and testing it's ok without debian.org but a stable install should fetch things from .org. That doesn't seem to be that easy, as mirrors would need to be checked constantly, zone files need to be updated constantly too. This will lead to problems due to dns caches, additionally there are problems with dnssec too. +1 to Miguel suggestion. I was indeed thinking about the same when looking at choose-mirror bugs. grml.org has been doing this, but they are appearantly not too happy with that. Yes. I share your view Holger. Using cdn on my laptop I had problems with some broken mirrors. So it really needs a good way of checking to be used by default. -- 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/AANLkTim5hGXt07q4SewutPYfWFW9bW=fg2srtidq1...@mail.gmail.com
Re: Preparation of fixes to 6.0.1
On Sat, 2011-02-12 at 22:46 +, Otavio Salvador wrote: I have prepare some branches that has what I am intending to upload to stable-proposed-updates. The modules I have changed are the following: grub-installer Doesn't look like this got uploaded yet? The relevant fix is in unstable but not testing yet; could we unblock the unstable package? linux-kernel-di-sparc-2.6 Presumably needs the kernel to be in before uploading. Also, I'd assumed that each of the l-k-d-i-* would get re-uploaded after the kernel had been updated? That's certainly what tended to happen for lenny. tasksel We agreed to skip this. cdebconf Was this a checksum-related change? I can't immediately find a repository for it in order to check. debootstrap Uploaded and accepted minus the checksum changes, as agreed. kernel-wedge Not uploaded yet? - kernel Planned for this weekend, although not uploaded yet afaics. - libdebian-installer tbm's fixes for the new devices look fine. Not updated in unstable yet though, so you'll end up with the squeeze version being propagated upwards. - debian-installer Needs everything else (except d-i-n-i) to be in place first. Is the current proposed upload everything between the 20110106 tag and the head of the squeeze branch? (i.e. up to 60f4ca5) As there hasn't been a d-i upload in unstable since the release, and assuming there isn't one beforehand, the updated images from p-u should get copied to testing and unstable during the point release; not sure how you (-boot) and ftp-master feel about that. - debian-installer-netboot-images Needs updating for #616014, both for sanity and license compliance reasons. See above r.e. versioning. - colo-installer Updated in both p-u and unstable, but not in testing yet as it's on britney's needs-approval list. Could we unblock it? Otherwise 1.17 +squeeze1 will end up in testing during the point release. - console-setup Looks okay, other than the version number should be 1.68+squeeze1. Fixed in unstable but not migrated to testing yet; could we unblock it? - hw-detect The fix for #611314 was previously acked and is fine. The comment removed as part of 4b40c64 says # Loading snd-powermac locks up G5 systems; is that no longer the case? Again, this has been fixed in unstable but not unblocked for testing yet. - apt-setup Admittedly I have a slight vested interest here, but getting #613910 fixed in squeeze (and preferably unstable and testing) should help reduce the support burden on #debian from people who chose not to use a network mirror during install uncommenting the broken sources.list entries, either manually or using e.g. update-manager, and then being surprised when they don't work. - anything I missed? Regards, Adam -- 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/1299424851.25972.11607.ca...@hathi.jungle.funky-badger.org
Bug#558036: Incorrect RO translation in d-i
On Sat, Mar 5, 2011 at 11:26, Andrei Popescu andreimpope...@gmail.com wrote: I tried the latest image and a few before that, but neither would boot from a usb stick (cat mini.iso /dev/sdb) or in VirtualBox. Strange. Can you provide the URL of image you tested? The latest testing business card image worked fine though, but I didn't get as far as grub because sdhci-pci is still missing. This is going to be fixed for 6.0.1. -- 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/AANLkTimLyp5jEEwYDCknGkS3M73FjMTv0AFsUL=ifj=5...@mail.gmail.com
Re: Touchscreen support in d-i
On Thu, Mar 3, 2011 at 18:48, Thibaut Girka t...@sitedethib.com wrote: Le jeudi 03 mars 2011 à 18:23 +0100, Cyril Brulebois a écrit : Don't you want to maintain it under d-i/something.git on alioth? :) Why not, although it could really be used outside of d-i or even Debian, and we still have to figure out the something part :) touchkbd as suggested by Samuel seems good. Or: Yet Another TouchScreen Virtual Keyboard - yatkbd :-) -- 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/AANLkTimwQyNQfCz7aPR5e6o1DQHzZUbP-+=gexrop...@mail.gmail.com
Re: Uploading linux-2.6 (2.6.32-31) for point release 6.0.1
On Wed, Mar 2, 2011 at 05:18, Ben Hutchings b...@decadent.org.uk wrote: ... That should be fine. That gives us time to include longterm release 2.6.32.30 and pick up a few other bug fixes. It would be nice if it can be done before since I'll do a surgery on 26th and need to travel for it on 24th or 25th. -- 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/AANLkTimoueanxN+CjQGSFLN3i0H1=euk5pbou0_9k...@mail.gmail.com
Processing of kernel-wedge_2.74+squeeze1_amd64.changes
kernel-wedge_2.74+squeeze1_amd64.changes uploaded successfully to localhost along with the files: kernel-wedge_2.74+squeeze1.dsc kernel-wedge_2.74+squeeze1.tar.gz kernel-wedge_2.74+squeeze1_all.deb 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/e1pwfnm-0005rh...@franck.debian.org
Processing of grub-installer_1.60+squeeze1_amd64.changes
grub-installer_1.60+squeeze1_amd64.changes uploaded successfully to localhost along with the files: grub-installer_1.60+squeeze1.dsc grub-installer_1.60+squeeze1.tar.gz grub-installer_1.60+squeeze1_amd64.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pwfsc-0006u7...@franck.debian.org
Processing of kernel-wedge_2.74+squeeze1_amd64.changes
/kernel-wedge_2.74+squeeze1_amd64.changes is already present on target host: kernel-wedge_2.74+squeeze1_all.deb Either you already uploaded it, or someone else came first. Job kernel-wedge_2.74+squeeze1_amd64.changes removed. 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/e1pwfx3-0006pm...@franck.debian.org
Processing of grub-installer_1.60+squeeze1_amd64.changes
/grub-installer_1.60+squeeze1_amd64.changes is already present on target host: grub-installer_1.60+squeeze1_amd64.udeb Either you already uploaded it, or someone else came first. Job grub-installer_1.60+squeeze1_amd64.changes removed. 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/e1pwg1u-0007tz...@franck.debian.org
Re: Preparation of fixes to 6.0.1
On 06/03/11 11:20 AM, Adam D. Barratt wrote: - anything I missed? netcfg. #614884 blocks #606268 against network-manager. We have a working solution with the two fixes I mentioned in 614884 and my supplied patch for NM's ifblacklist_migrate.sh filed against 606268. The NM bug is RC but had no immediate solution forthcoming and was therefore deferred. For over a month I've hung out on #debian and have seen plenty of users affected by this bug, which is why I made the effort to fix both the netcfg and NM halves of the problem myself. But now it seems both the d-i and gnome teams have been rather busy and unable to do anything with my patches. Is there anything more I can do to help ensure this makes it? Ben -- 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/4d73aaba.4000...@debian.org
Bug#558036: marked as done (mmc-modules-2.6.30-2-486-di doesn't include sdhci-pci.ko)
Your message dated Sun, 06 Mar 2011 16:03:42 + with message-id e1pwgqo-0005lw...@franck.debian.org and subject line Bug#558036: fixed in kernel-wedge 2.74+squeeze1 has caused the Debian Bug report #558036, regarding mmc-modules-2.6.30-2-486-di doesn't include sdhci-pci.ko 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.) -- 558036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558036 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mmc-modules-2.6.30-2-486-di Version: 1.84 Hi! Daily d-i fails to detect SDHC card slot in Acer Aspire One ( 04:00.2 SD Host controller [0805]: JMicron Technology Corp. Standard SD Host Controller [197b:2381] (prog-if 01) Subsystem: Acer Incorporated [ALI] Device [1025:015b] ). Manually downloading and insmod'ing sdhci-pci.ko from linux-image-2.6.30-2-486 fixes this. Please include it. -- Vadim Solomin ---End Message--- ---BeginMessage--- Source: kernel-wedge Source-Version: 2.74+squeeze1 We believe that the bug you reported is fixed in the latest version of kernel-wedge, which is due to be installed in the Debian FTP archive: kernel-wedge_2.74+squeeze1.dsc to main/k/kernel-wedge/kernel-wedge_2.74+squeeze1.dsc kernel-wedge_2.74+squeeze1.tar.gz to main/k/kernel-wedge/kernel-wedge_2.74+squeeze1.tar.gz kernel-wedge_2.74+squeeze1_all.deb to main/k/kernel-wedge/kernel-wedge_2.74+squeeze1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 558...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otavio Salvador ota...@debian.org (supplier of updated kernel-wedge package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 06 Mar 2011 12:18:41 -0300 Source: kernel-wedge Binary: kernel-wedge Architecture: source all Version: 2.74+squeeze1 Distribution: unstable Urgency: low Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Otavio Salvador ota...@debian.org Description: kernel-wedge - udeb package builder for Debian-Installer Closes: 558036 584973 Changes: kernel-wedge (2.74+squeeze1) unstable; urgency=low . [ Miguel Figueiredo ] * mmc-modules: sdhci_pci. Closes: #558036. * Add support for Cherry keyboards (hid-cherry on input-modules). Closes: #584973. . [ Joey Hess ] * build-arch: Pass -I to dpkg-buildpackage without arguments to take advantage of its built-in list of all version control gunk to ignore. Checksums-Sha1: 64c00abdcd1038452765982c009c18afe65e992e 1611 kernel-wedge_2.74+squeeze1.dsc 396394f9a57c847b2552a43127485284032f6b38 43326 kernel-wedge_2.74+squeeze1.tar.gz 701e1299e1bb341888c6cac85889afd8c81ec3af 48508 kernel-wedge_2.74+squeeze1_all.deb Checksums-Sha256: 5ca55453a24bd0d39304054c843af13300c8887dac7e44531193772bb97f4129 1611 kernel-wedge_2.74+squeeze1.dsc 3022cbfb67c92bef0c7cba21f2b54ba633b9ab91568ed07940f07560bf9e0dfd 43326 kernel-wedge_2.74+squeeze1.tar.gz 54ab51f156f142a7ad7c97056e7333d7ac171912926de3eaf55af8e5e4436950 48508 kernel-wedge_2.74+squeeze1_all.deb Files: 69f30e251a84990f40a5f6535982be38 1611 utils optional kernel-wedge_2.74+squeeze1.dsc f534ad34cfc96342da5ee098415371c6 43326 utils optional kernel-wedge_2.74+squeeze1.tar.gz 4d1dd327b41ce7caf9afa8ee38c00e67 48508 utils optional kernel-wedge_2.74+squeeze1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBCAAGBQJNc6aaAAoJEOtw/vPN/G5POhQQALQmvdnYlIsEGP0sAGJMAzsT B1lr+2IB5FteV8fJCaB3eF4aipppPUObMSraxrIYsA6ejAHd59l0DqkBIwumjoiD l6Sq/MwwFuSI8rjr8mjQjuMMSWXf54MVFmgQOfdhj76h7poetb01ZB3MFbLKT98M JWwrcsu0kdxqRI0RFsVsZk7LpTR4/Pzdx3129opSOLtKnyKOZUiSD670oo7XhKQv v8gHEHKGFVB3Y/K0o356SzUg9uLGUq4IVLdMnHvla0K33bQx+N5QzCt6RUFj4uVH 9uej5jjEUpxALCI1ToGZ9Z+eU7Pn4oOBrlX6DQTdH3bN/5EG6G4N2ngwE1PyzXtk hDkZVQTIGZuFJWNLunMWhmlKADjfEmPtHEPzBh88O0V1veCPZZbqifSnTCpCIXPR u5ujtrbpBY8s4UCMOerxXtpn6xWSdxQUpqLZXwHDHPeis+tUoxxq3dt4E79+YzFQ ct7rA9Q4RpF6zfmYTqan3IouqCtYkvaO1j+Rp0zUhz0YPr/aj1r7TLXYtMD5+jue 9ZfzVZNazfWs5FvM+AsoMIzDjC9Hn3PewN5bZo9lM3R3IbYgw5oji3rQaWzrX4Vt r+n+cTBsyJRcUrMl2H+rfJflpSTv3HEsHQL5vjHNl54y2v+ueAFyEYAjIMqyvC8T zk9T/H+V9KUS7jHocnNu =tmVB -END PGP SIGNATURE- ---End Message---
Bug#584973: marked as done (installer squeeze does not support Cherry USB keyboards)
Your message dated Sun, 06 Mar 2011 16:03:42 + with message-id e1pwgqo-0005lc...@franck.debian.org and subject line Bug#584973: fixed in kernel-wedge 2.74+squeeze1 has caused the Debian Bug report #584973, regarding installer squeeze does not support Cherry USB keyboards 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.) -- 584973: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=584973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: installation-reports Boot method: USB stick with netinst image Image version: http://cdimage.debian.org/cdimage/squeeze_di_alpha1/amd64/iso-cd/debian-testing-amd64-netinst.iso, http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: Tue, 8 Jun 2010 00:30 +0100 Machine: PC Processor: Intel Core i5 650 Memory: 8GByte Partitions: none yet Output of lspci -knn (or lspci -nn): (Ubuntu 10.04 amd64 live system, update-pciids) 00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0040] (rev 02) Kernel driver in use: agpgart-intel Kernel modules: intel-agp 00:02.0 VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 02) Kernel driver in use: i915 Kernel modules: i915 00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06) 00:16.2 IDE interface [0101]: Intel Corporation 5 Series/3400 Series Chipset PT IDER Controller [8086:3b66] (rev 06) 00:16.3 Serial controller [0700]: Intel Corporation 5 Series/3400 Series Chipset KT Controller [8086:3b67] (rev 06) Kernel driver in use: serial 00:19.0 Ethernet controller [0200]: Intel Corporation 82578DM Gigabit Network Connection [8086:10ef] (rev 06) Kernel driver in use: e1000e Kernel modules: e1000e 00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 06) Kernel driver in use: ehci_hcd 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 06) Kernel driver in use: HDA Intel Kernel modules: snd-hda-intel 00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 06) Kernel driver in use: pcieport Kernel modules: shpchp 00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 [8086:3b4a] (rev 06) Kernel driver in use: pcieport Kernel modules: shpchp 00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 06) Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a6) 00:1f.0 ISA bridge [0601]: Intel Corporation 5 Series Chipset LPC Interface Controller [8086:3b0a] (rev 06) Kernel modules: iTCO_wdt 00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b22] (rev 06) Kernel driver in use: ahci Kernel modules: ahci 00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 06) Kernel modules: i2c-i801 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ E] 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: USB keyboard works fine in BIOS and Ubuntu 10.04 amd64 live system. After booting debian squeeze installers, keyboard does not get initialized (no response to keys, no numlock switching, etc), cannot continue to install. lsusb (Ubuntu 10.04 amd64 live system, update-usbids) 002 Device 004: ID 046d:c01d Logitech, Inc. MX510 Optical Mouse Bus 002 Device 003: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 2.0 Stick (4GB) / PNY Attache 4GB Stick Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 046a:0023 Cherry GmbH CyMotion Master Linux Keyboard Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus
Re: Preparation of fixes to 6.0.1
On Sun, 2011-03-06 at 11:39 -0400, Ben Armstrong wrote: On 06/03/11 11:20 AM, Adam D. Barratt wrote: - anything I missed? netcfg. #614884 blocks #606268 against network-manager. We have a working solution with the two fixes I mentioned in 614884 and my supplied patch for NM's ifblacklist_migrate.sh filed against 606268. The NM bug is RC but had no immediate solution forthcoming and was therefore deferred. For over a month I've hung out on #debian and have seen plenty of users affected by this bug, which is why I made the effort to fix both the netcfg and NM halves of the problem myself. But now it seems both the d-i and gnome teams have been rather busy and unable to do anything with my patches. Is there anything more I can do to help ensure this makes it? Well, having it fixed in unstable would be a good start. The problem doesn't just affect stable so having the first time the patch is in the archive be a stable point release isn't generally appropriate. Where would one find the patch for #614884? Is it purely the snippet in your message #21 in the bug log? Regards, Adam -- 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/1299427710.25972.11809.ca...@hathi.jungle.funky-badger.org
Bug#558036: Incorrect RO translation in d-i
On Du, 06 mar 11, 15:20:24, Otavio Salvador wrote: On Sat, Mar 5, 2011 at 11:26, Andrei Popescu andreimpope...@gmail.com wrote: I tried the latest image and a few before that, but neither would boot from a usb stick (cat mini.iso /dev/sdb) or in VirtualBox. Strange. Can you provide the URL of image you tested? The latest one does it as well, also the non-gtk version http://d-i.debian.org/daily-images/amd64/20110306-00:20/netboot/gtk/mini.iso FYI, I created the VirtualBox machine with the default for Debian. I get as far as the boot menu, but if I press enter on 'Install' it just freezes, but it still reacts to Ctrl+Alt+Del. $ dpkg -l virtualbox* | grep ^ii ii virtualbox-ose4.0.4-dfsg-1+b1 x86 virtualization solution - base binaries ii virtualbox-ose-dkms 4.0.4-dfsg-1 x86 virtualization solution - kernel module sources for dkms ii virtualbox-ose-qt 4.0.4-dfsg-1+b1 x86 virtualization solution - Qt based user interface (this is on amd64) On the real hardware I don't even get to the boot menu. The laptop is a HP ElitBook 8540p. The latest testing business card image worked fine though, but I didn't get as far as grub because sdhci-pci is still missing. This is going to be fixed for 6.0.1. Great :) Regards, Andrei -- Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic signature.asc Description: Digital signature
grub-installer_1.60+squeeze1_amd64.changes REJECTED
Reject Reasons: grub-installer_1.60+squeeze1.dsc: old version (1.62) in unstable = new version (1.60+squeeze1) targeted at unstable. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- 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/e1pwgql-0005jx...@franck.debian.org
kernel-wedge_2.74+squeeze1_amd64.changes ACCEPTED into unstable
Accepted: kernel-wedge_2.74+squeeze1.dsc to main/k/kernel-wedge/kernel-wedge_2.74+squeeze1.dsc kernel-wedge_2.74+squeeze1.tar.gz to main/k/kernel-wedge/kernel-wedge_2.74+squeeze1.tar.gz kernel-wedge_2.74+squeeze1_all.deb to main/k/kernel-wedge/kernel-wedge_2.74+squeeze1_all.deb Override entries for your package: kernel-wedge_2.74+squeeze1.dsc - source utils kernel-wedge_2.74+squeeze1_all.deb - optional utils Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 558036 584973 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/e1pwgqo-0005ln...@franck.debian.org
Re: Preparation of fixes to 6.0.1
On 06/03/11 12:08 PM, Adam D. Barratt wrote: Well, having it fixed in unstable would be a good start. The problem doesn't just affect stable so having the first time the patch is in the archive be a stable point release isn't generally appropriate. Where would one find the patch for #614884? Is it purely the snippet in your message #21 in the bug log? There were two problems. One was the wrong filepath to the migrate script (yes, the snippet,) and the other was the missing execution bit. With both fixes applied, the migrate script was executed as intended, and once I patched the migrate script, NM worked properly after an install. Ben -- 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/4d73b286.5040...@debian.org
Re: Debian installer build: failed or old builds
Quoting dann frazier (da...@dannf.org): And how about hppa builds? IIRC, hppa is now only supported in unstable, so that may explain why D-I daily builds are no longer run. Am I right? oops - powered down my hppa box before i went out of town. It should be back up daily buildin' again. Thanks for the poke. As of today, we still have reports of old builds for hppa... * OLD BUILD:hppa Jan 17 07:06 didaily@c3700 build_cdrom http://d-i.debian.org/daily-images/hppa/daily/build_cdrom.log * OLD BUILD:hppa Jan 17 07:10 didaily@c3700 build_netboot http://d-i.debian.org/daily-images/hppa/daily/build_netboot.log * OLD BUILD:hppa Jan 17 07:14 didaily@c3700 build_miniiso http://d-i.debian.org/daily-images/hppa/daily/build_miniiso.log signature.asc Description: Digital signature
Re: Preparation of fixes to 6.0.1
On 06/03/11 12:08 PM, Adam D. Barratt wrote: Well, having it fixed in unstable would be a good start. The problem doesn't just affect stable so having the first time the patch is in the archive be a stable point release isn't generally appropriate. The biggest barrier to this is that Matt said he'd commit upload as soon as someone confirmed the bug is fixed by his patch. Well, I did that, but don't have the source for the patched netcfg so we at least need the commit ... Ben -- 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/4d73b6fb.9000...@debian.org
Processed: reassign 614583 to debian-cd, found 614583 in 3.1.6
Processing commands for cont...@bugs.debian.org: reassign 614583 debian-cd 3.1.5 Bug #614583 [debian-installer] Boot prompt for powerpc should tell G5 users to select 'install64' not 'install' Bug reassigned from package 'debian-installer' to 'debian-cd'. Bug #614583 [debian-cd] Boot prompt for powerpc should tell G5 users to select 'install64' not 'install' Bug Marked as found in versions debian-cd/3.1.5. found 614583 3.1.6 Bug #614583 [debian-cd] Boot prompt for powerpc should tell G5 users to select 'install64' not 'install' Bug Marked as found in versions debian-cd/3.1.6. thanks Stopping processing here. Please contact me if you need assistance. -- 614583: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614583 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.12994302785986.transcr...@bugs.debian.org
Re: Preparation of fixes to 6.0.1
On Sun, 2011-03-06 at 15:20 +, Adam D. Barratt wrote: On Sat, 2011-02-12 at 22:46 +, Otavio Salvador wrote: I have prepare some branches that has what I am intending to upload to stable-proposed-updates. The modules I have changed are the following: grub-installer Doesn't look like this got uploaded yet? The relevant fix is in unstable but not testing yet; could we unblock the unstable package? It looks like this got uploaded, but targeted at unstable where there's already a newer version, so it got rejected: grub-installer_1.60+squeeze1.dsc: old version (1.62) in unstable = new version (1.60+squeeze1) targeted at unstable. The earlier question regarding unblocking the unstable version still stands. [...] kernel-wedge Not uploaded yet? Uploaded, but to (I assume) the wrong target: kernel-wedge | 2.74+squeeze1 | unstable | source, all Regards, Adam -- 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/1299434998.25972.12296.ca...@hathi.jungle.funky-badger.org
Bug#616716: No crypted volume identification for existing volumes
Package: debian-installer Severity: normal Tags: d-i Lates debian installer on Squeeze Iso disk debian-6.0.0-amd64-BD-1.iso used to install new computer. I've created on sda and sdb the same partition configuration: xen:~# fdisk -l /dev/sda /dev/sdb Disk /dev/sda: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 2 12 88357+ fd Linux raid autodetect /dev/sda2 13244419530752 fd Linux raid autodetect /dev/sda38520 38914 244140032 fd Linux raid autodetect Disk /dev/sdb: 320.0 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sdb1 2 12 88357+ fd Linux raid autodetect /dev/sdb2 13244419530752 fd Linux raid autodetect /dev/sdb38520 38914 244140032 fd Linux raid autodetect At the moment the above two hds are available for installation. After migrating something from the old two existing hard drives with the same geometry I will add them in the system, too. So I want to configure all md's with 4 drives where 2 are missing. This is not configurable in debian installer at the moment so I created the needed md's manually with mdadm command. In short the command I used must be mdadm --bitmap=internal --name=bootmd --level=1 --raid-devices=3 --spare- devices=1 /dev/md125 /dev/sda1 /dev/sdb1 missing missing mdadm --bitmap=internal --name=bootmd --level=1 --raid-devices=3 --spare- devices=1 /dev/md126 /dev/sda2 /dev/sdb2 missing missing mdadm --bitmap=internam --name=datamd --level=6 --raid-devices=4 /dev/md127 /dev/sda3 /dev/sdb3 missing missing Here the output of the examine command after starting the old lenny: xen:~# mdadm --examine /dev/sda1 /dev/sda1: Magic : a92b4efc Version : 01 Feature Map : 0x1 Array UUID : ffc6e33d:438fe377:28767059:ae3356d9 Name : xen:bootmd (local to host xen) Creation Time : Wed Mar 2 13:03:11 2011 Raid Level : raid1 Raid Devices : 3 Device Size : 176691 (86.29 MiB 90.47 MB) Array Size : 176690 (86.29 MiB 90.47 MB) Used Size : 176690 (86.29 MiB 90.47 MB) Data Offset : 24 sectors Super Offset : 8 sectors State : clean Device UUID : af12b571:217d90d7:7dc7b5ee:850ef865 Internal Bitmap : 8 sectors from superblock Update Time : Sun Mar 6 02:28:30 2011 Checksum : 79726af5 - correct Events : 370 Array Slot : 0 (0, 1) Array State : Uu_ xen:~# mdadm --examine /dev/sda2 /dev/sda2: Magic : a92b4efc Version : 01 Feature Map : 0x1 Array UUID : 48d33aa8:997c6d99:ac8f68c1:a1a4a73e Name : xen:rootmd (local to host xen) Creation Time : Wed Mar 2 13:03:45 2011 Raid Level : raid1 Raid Devices : 3 Device Size : 39059456 (18.63 GiB 20.00 GB) Array Size : 39059312 (18.62 GiB 20.00 GB) Used Size : 39059312 (18.62 GiB 20.00 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : ec97cdb6:dfa61e5a:134643a1:f7d45645 Internal Bitmap : 8 sectors from superblock Update Time : Sun Mar 6 02:28:33 2011 Checksum : 30d293a4 - correct Events : 3808 Array Slot : 0 (0, 1) Array State : Uu_ xen:~# mdadm --examine /dev/sda3 /dev/sda3: Magic : a92b4efc Version : 01 Feature Map : 0x1 Array UUID : 45d7a2d4:628276ee:28b1e996:c44bc3c6 Name : xen:datamd (local to host xen) Creation Time : Sat Mar 5 02:23:00 2011 Raid Level : raid6 Raid Devices : 4 Device Size : 488278016 (232.83 GiB 250.00 GB) Array Size : 976553984 (465.66 GiB 500.00 GB) Used Size : 488276992 (232.83 GiB 250.00 GB) Data Offset : 2048 sectors Super Offset : 8 sectors State : clean Device UUID : b5f9456b:6b379c3f:0837a437:044b2aa8 Internal Bitmap : 8 sectors from superblock Update Time : Sat Mar 5 22:28:58 2011 Checksum : c59fd9de - correct Events : 168 Chunk Size : 512K Array Slot : 0 (0, 1) Array State : Uu__ All the rest I did with the installer: The /dev/md125 is configured as /boot with ext3. Then I created on /dev/md126 and /dev/md127 the crypted devices without changing the parameters. After the crypting devices are created (named md126_crypt and md127_crypt ?) I've set up both for LVM and created in md126_crypt the xenrootdg. md127_crypt I left alone for the installation. On xenrootdg I created an varvol for /var, homevol for /home, rootvol for / all with ext3. I've used varfs, homefs and rootfs for logical name of the filesystem. I created swapvol for swap use. Here the graphical layout: /boot ext3 bootfs on md125 with
Bug#616721: Add support to create degraded md devices
Package: debian-installer Severity: whishlist Tags: d-i Latest debian installer on Squeeze Iso disk debian-6.0.0-amd64-BD-1.iso used to install new computer. At the level of creating md devices it is not possible to create degraded md devices. For example if you have only one disk of two available for the md configuration it is not possible to create an md1 with one active and one missing device. You need an minimum of 2 disks available. The same issue with raid-5 (3 needed, but in degraded mode working already with 2 devices) or with raid-6 (4 needed, but in degraded mode must work with 2 devices) It is possible to use spare devices as missing but this is not the fact what I mean. I can create e.g. manually md devices in the console with mdadm --create --raid-devices=2 --raid-lcvel=1 /dev/md1 /dev/sda1 mdadm --create --raid-devices=2 --raid-level=5 /dev/md1 /dev/sda1 /dev/sdb1 missing mdadm --create --raid-devices=2 --raid-level=6 /dev/md1 /dev/sda1 /dev/sdb1 missing missing so I can later add the missing devices. Please extend the md configuration so degraded raid array's can be build at time of installation. A warning message should be seen here, if an degraded array will be build. -- System Information: Debian Release: 6.0 Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) signature.asc Description: OpenPGP digital signature
Bug#616722: Add support to give logical name of md device
Package: debian-installer Severity: whishlist Tags: d-i Latest debian installer on Squeeze Iso disk debian-6.0.0-amd64-BD-1.iso used to install new computer. At the level of creating md devices it is not possible give an name to the created md device which can be do with --name mdadm option. Please add. -- System Information: Debian Release: 6.0 Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) signature.asc Description: OpenPGP digital signature
Bug#616723: Add support for bitmap option of md device
Package: debian-installer Severity: whishlist Tags: d-i Latest debian installer on Squeeze Iso disk debian-6.0.0-amd64-BD-1.iso used to install new computer. At the level of creating md devices it is not possible to add an bitmap as I can do with --bitmap=internal. Please add (for me internal is good enough ;-). -- System Information: Debian Release: 6.0 Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) signature.asc Description: OpenPGP digital signature
Bug#616723: Add support for bitmap option of md device
07.03.2011 01:00, Pierre Bernhardt wrote: Package: debian-installer Severity: whishlist Tags: d-i Latest debian installer on Squeeze Iso disk debian-6.0.0-amd64-BD-1.iso used to install new computer. At the level of creating md devices it is not possible to add an bitmap as I can do with --bitmap=internal. Please add (for me internal is good enough ;-). MD bitmap can trivially be done later... FWIW. md configuration is quite complex nowadays, and some things (various options for different layouts like r10 near and far copies, chunk size, algorithm for r5 etc) are more important than bitmap, because these can't be changed after the array has been created (or requires rebuilding (reshaping) the array). /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/4d7407bf.4030...@msgid.tls.msk.ru
Re: GeoMirror (aka cdn.debian.net) as default mirror in standard installation?
Miguel Figueiredo at Sat, 5 Mar 2011 09:51:00 + wrote: MF Hi all, MF Using GeoMirror [1] (aka cdn.debian.net) as default mirror in the default MF installation can save decisions and interaction to who is installing and be a MF more automated process. MF * Pros: MF - 'good' default as it should select a nearby working mirror MF - efficient use of Debian mirrors MF - less decisions to who is installing MF - less interactivity MF * Cons: MF - Less customization MF - 'good' default could not be the best default MF What to you think about it's use in the installer? MF 1 - http://wiki.debian.org/DebianGeoMirror Why don't use something like apt-spy to test mirror speed and select the best? Bye Stefano PS: some one is supposed to manage apt-spy as I gave up after receveing one rude email -- Stefano Canepa aka sc: s...@linux.it - http://www.stefanocanepa.it Three great virtues of a programmer: laziness, impatience and hubris. Le tre grandi virtù di un programmatore: pigrizia, impazienza e arroganza. (Larry Wall) -- 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/87bp1nhowy@lepre.stefanocanepa.home
Processed: your mail
Processing commands for cont...@bugs.debian.org: reassign 612281 apt-setup Bug #612281 [installation-reports] installation-reports: volatile reference instead of squeeze/updates in, installer Bug reassigned from package 'installation-reports' to 'apt-setup'. forcemerge 614862 612281 492937 596716 Bug#614862: debian-installer: Still asks whether to enable volatile updates Bug#492937: apt-setup: inconsistent path handling for 'security' and 'volatile' services Bug#596716: debian-installer: please add easy path to bpo and volatile sources Bug#612281: installation-reports: volatile reference instead of squeeze/updates in, installer Forcibly Merged 492937 596716 612281 614862. thanks Stopping processing here. Please contact me if you need assistance. -- 614862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=614862 492937: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=492937 612281: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612281 596716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=596716 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.12994537229667.transcr...@bugs.debian.org
Bug#607301: No boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, SATA, SiI 3114
Package: installation-reports Severity: critical Justification: Will not boot, so no system, with or without rescue-disk-pc. Now Debian 6.0.0 is out, should I be sending this report to GRUB package directly ? 06.03.2011 Fails to boot with Debian sid, unstable grub-rescue-pc 1.99~rc1-3 i386, From a Sil 3114 controller and a single SATA drive. No raid array is set. grub-rescue-cdrom.iso: El Torito CDROM image. The rescue disk boots itself ok, but it does not rescue the machine. The pc does not boot in conjunction with the rescue disk, after succesfully installing from, (except auto booting) versions of :- Debian 6.0.0, wheezy weekly build , unstable-20.02.2011 and also experimemtal-20.02.2011, and experimental-04.03.2011. After I set the rescue-disk-pc GNU/Linux parameters to :- set params 'GNU/Linux' (as it comes, a blank line here) set root=(hd0,1) linux /boot/vmlinux-2.6.37-2-486root=/dev/sda1 initrd /boot/initrd.img-2.6.37-2-486 As a reminder from way above, this processor is: AMD K-6-2/400, along with all the other machine and system details. The rescue-disk-pc Boot Symptom is :- error: hd0 cannot get c/h/s values error: you need to load the kernel first. press any key to continue grub ls (cd) (cd,msdos1) (fd0) I also tried with the rescue-disk-pc 1.99~rc1-3 set root= (sd0,0) or (sd1,0) or (sd0) or (sd0,1) or (sd1,1) or (sda,1) or (sda) error: no such disk. I set it back to hd0,1 and tried again. No joy. back to the symptom. I can use the 'install disk, graphical rescue mode' to /dev/sda1 ok. # eject /dev/scd0 works, along with other sda1 resident applications. # /usr/bin/nano /etc/apt/sources.list # /boot/grub/grub --version grub (GNU GRUB 1.99~rc1-3) I also ran # /usr/sbin/update-grub2 I tried booting from the dasd without using the rescue-disk-pc to hd0 again, but it would still not boot afterwards, or with a subsequent rescue-disk-pc. In the machines AMIBIOS setup - Advanced CMOS setup :- With the cdrom trays empty, a boot from the DASD with 'SCSI' set in the machines Bios as '1st Boot Device' and further Devices set to disabled, still gives :- Searching for Boot Record from SCSI..Not Found Boot Failure Reboot and Select proper Boot device or insert Boot Media in selected Boot device Press any key when ready With CDROM set as '1st Boot Device' and SCSI set as '2nd Boot Device' still gives:- Searching for Boot Record from CDROM..Not Found Reboot and Select proper Boot device or insert Boot Media in selected Boot device Press any key when ready You would think that with the last (2nd Boot Device) set as SCSI, the 4th from last line would still say :- Searching for Boot Record from SCSI..Not Found. as this would be the last device it tried to boot from. Further boot devices are set to disabled. I hope my installation-report helps with the GRUB Release Candidate 1-3 work. Regards McTech. -- 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/AANLkTim1aX3qK2+UEB=ql7fpr6jafrwkaz9jgc-ya...@mail.gmail.com
Processed: your mail
Processing commands for cont...@bugs.debian.org: tags 612631 + pending Bug #612631 [installation-guide] debian-installer: error in example-preseed.txt Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 612631: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=612631 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.129945569316997.transcr...@bugs.debian.org
Bug#616733: os-prober: Does not detect MS-DOS reliably
Package: os-prober Version: 1.42 Severity: normal Configuration: - system is partitioned as follows: /dev/sda1 = Linux /boot /dev/sda2 = DOS 6.22 /dev/sda3 = extended partition /dev/sda5 = Linux LVM PV, containing swap and Linux filesystems - /dev/sda2 is mounted on /dos (so the DOS 6.22 system directory is /dos/dos ) Commands issued as root: # cd /root # update-grub2 # cd /dos # update-grub2 Expected results: update-grub2 runs grub-mkconfig, which uses os-prober via /etc/grub.d/30_os-prober script. It finds the DOS partition and adds it to GRUB boot menu. The results should be the same no matter in which directory update-grub2 is run. Actual results: When the current directory is /root, the DOS partition is not detected. When the current directory is /dos, the DOS partition is detected successfully. # cd /root # update-grub2 Found linux image: /boot/vmlinuz-2.6.36.4-c7 Found initrd image: /boot/initrd.img-2.6.36.4-c7 Found linux image: /boot/vmlinuz-2.6.32-5-686 Found initrd image: /boot/initrd.img-2.6.32-5-686 Found memtest86 image: /memtest86.bin Found memtest86+ image: /memtest86+.bin done # cd /dos # update-grub2 Generating grub.cfg ... Found linux image: /boot/vmlinuz-2.6.36.4-c7 Found initrd image: /boot/initrd.img-2.6.36.4-c7 Found linux image: /boot/vmlinuz-2.6.32-5-686 Found initrd image: /boot/initrd.img-2.6.32-5-686 Found memtest86 image: /memtest86.bin Found memtest86+ image: /memtest86+.bin Found MS-DOS 5.x/6.x/Win3.1 on /dev/sda2 done Analysis: os-prober's MS-DOS test in /usr/lib/os-probes/mounted/20microsoft does not use an absolute path when it verifies that dos is a directory. Patch attached. Further suggestions: Testing for the presence of dos directory is not a very reliable test for MS-DOS: the directory might exist also on systems updated from MS-DOS/Win3.1 to Windows 9x, and the name of the MS-DOS system directory was relatively easy to customize. A better test would be to look for initial boot files: IO.SYS and MSDOS.SYS: their location is fixed at the root of the MS-DOS/Windows system partition. Step 1) If both IO.SYS and MSDOS.SYS exist, and no other versions of MS-Windows are detected, the OS is either MS-DOS/Win3.1 or Windows 9x/ME. Step 2) If MSDOS.SYS is a binary, the OS is MS-DOS/Win3.1; if MSDOS.SYS contains only text with CRLF line terminators (although not necessarily ASCII only: localized versions may have included national characters in CP850 or other Microsoft proprietary extended-ASCII encodings), the OS is Windows 9x/ME. -- System Information: Debian Release: 6.0 APT prefers squeeze-updates APT policy: (500, 'squeeze-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.36.4-c7 Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages os-prober depends on: ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib os-prober recommends no packages. os-prober suggests no packages. -- no debconf information --- /usr/lib/os-probes/mounted/20microsoft.distrib 2010-08-27 02:39:38.0 +0300 +++ /usr/lib/os-probes/mounted/20microsoft 2011-03-07 00:33:43.0 +0200 @@ -64,7 +64,7 @@ fi fi # MS-DOS -elif [ -d $(item_in_dir dos $2) ]; then +elif [ -d $2/$(item_in_dir dos $2) ]; then long=MS-DOS 5.x/6.x/Win3.1 short=MS-DOS # 95/98/Me
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * 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. * FAILED BUILD: amd64 Feb 28 06:35 debian-cd@pettersson source http://cdbuilder.debian.org/cdimage-log/source Totals: 170 builds (1 failed, 5 old) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1pwons-00015h...@ravel.debian.org
Re: Preparation of fixes to 6.0.1
On Sun, Mar 6, 2011 at 18:09, Adam D. Barratt a...@adam-barratt.org.uk wrote: It looks like this got uploaded, but targeted at unstable where there's already a newer version, so it got rejected: Yes. I did it wrong :-( My fault. -- 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=duGdtpn2tVfAKkHL6bvT4xXW_rp=piojov...@mail.gmail.com
