Re: Wheezy: Questions about UEFI boot etc.
On Tue, 2013-05-14 at 13:58 -0400, Lennart Sorensen wrote: > On Tue, May 14, 2013 at 07:25:55PM +0200, Svante Signell wrote: > > Hi, > > (Please Cc: me, I'm not subscribed) > > 3) I plan to split both large disks partitions into a small W8 part and > > a larger Linux part. Should I do the split in W8 or with the Wheezy CD. > > The HDD has a rescue partition in the end of the disk, while the SSD has > > it in the beginning. > > Windows's storage manage will allow you to shrink the disk (although > only if it doesn't require moving files I believe). Don't create new > partitions from windows though, just leave unppartitioned space. Thanks, the disk shrinking worked. > > 4) The Wheezy CD has support for UEFI boot. Should I choose that or the > > traditional boot option when installing grub2? Which are the > > differences? > > UEFI boot places the boot code in the boot partition and is then > controlled by the UEFI boot manager as far as I know (I have not tried > it myself yet). If UEFI boot works, then it makes sense to use it, > given future machines are likely to drop lagacy boot support eventually, > so if you use UEFI now, it would be easy to moee the drive to a new > machine later (although windows wouldn't like it of course). The installation went well, thanks. The remaining problem is that W8 boot manager partition on the SSD /dev/sda2 has the boot flag set (not changeable from Linux, is it from W8?) On the SSD the Linux partition is /dev/sda5, which I made bootable (also UEFI boot). However, even if grub is written to /dev/sda no grub menu appears, and only W8 starts up every time. Additionally, booting from the HDD does not seem to be possible, at least within W8. How to access the UEFI boot manager, can it be enabled by a BIOS setting change? Thanks, Svante -- 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/1368599982.4575.39.camel@PackardBell-PC
Bug#708315: Debian 7 netboot failed on IBM Power 7 lpar
Package: installation-reports Boot method: netboot Image version: Debian 7 netboot image files Date: May 15, 2013 Machine: IBM Power7 LPAR 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: The yaboot cannot find the images files under the /tftpboot dir (I have used this install server for SuSE/RH, which can work). Followed is the bootup console output: == IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM STARTING SOFTWARE IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMPLEASE WAIT... IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM TFTP BOOT --- Server IP.10.33.4.4 Client IP.10.33.0.170 Gateway IP10.33.0.1 Subnet Mask...255.255.0.0 ( 1 ) Filename.yaboot.debian7 TFTP Retries..5 Block Size512 FINAL PACKET COUNT = 388 FINAL FILE SIZE = 198596 BYTES Elapsed time since release of system processors: 232424 mins 39 secs Try to netboot TFTP BOOT --- Server IP.10.33.4.4 Client IP.10.33.0.170 Gateway IP10.33.0.1 Subnet Mask...255.255.0.0 ( 1 ) Filename.yaboot.debian7 TFTP Retries..5 Block Size512 FINAL PACKET COUNT = 388 FINAL FILE SIZE = 198596 BYTES Config file read, 32768 bytes Welcome to yaboot version 1.3.16 Enter "help" to get some basic usage information boot: boot: boot: boot: help Press the tab key for a list of defined images. The label marked with a "*" is is the default image, press to boot it. To boot any other label simply type its name and press . To boot a kernel image which is not defined in the yaboot configuration file, enter the kernel image name as [[device:][partno],]/path, where "device:" is the OpenFirmware device path to the disk the image resides on, and "partno" is the partition number the image resides on. Note that the comma (,) is only required if you specify an OpenFirmware device, if you only specify a filename you should not start it with a "," To boot a alternative initrd file rather than specified in the yaboot configuration file, use the "initrd" command on Yaboot's prompt: "initrd=[name.img]". This will load the "name.img" file after the default kernel image. You can, also, specify a different initrd file to any other label of the yaboot configuration file. Just type "label initrd=[name.img]" and the specified initrd file will be loaded. To load an alternative config file rather than /etc/yaboot.conf, enter its device, partno and path, on Open Firmware Prompt: boot conf=device:partno,/path/to/configfile .To reload the config file or load a new one, use the "conf" command on Yaboot's prompt: conf [device=device] [partition=partno] [file=/path/to/configfile] If you omit "device" and "partno", Yaboot will use their current values. You can check them
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: amd64 May 15 00:05 buildd@barber build_cdrom_isolinux http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_isolinux.log * FAILED BUILD: amd64 May 15 00:05 buildd@barber build_cdrom_gtk http://d-i.debian.org/daily-images/amd64/daily/build_cdrom_gtk.log * FAILED BUILD: amd64 May 15 00:05 buildd@barber build_cdrom-xen http://d-i.debian.org/daily-images/amd64/daily/build_cdrom-xen.log * FAILED BUILD: amd64 May 15 00:05 buildd@barber build_netboot http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log * FAILED BUILD: amd64 May 15 00:06 buildd@barber build_netboot-gtk http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log * FAILED BUILD: amd64 May 15 00:06 buildd@barber build_netboot-xen http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log * FAILED BUILD: amd64 May 15 00:06 buildd@barber build_hd-media http://d-i.debian.org/daily-images/amd64/daily/build_hd-media.log * FAILED BUILD: amd64 May 15 00:06 buildd@barber build_hd-media_gtk http://d-i.debian.org/daily-images/amd64/daily/build_hd-media_gtk.log * OLD BUILD:armel May 10 08:11 buildd@ancina build_iop32x_netboot http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log * FAILED BUILD: armel May 10 08:11 buildd@ancina build_iop32x_netboot http://d-i.debian.org/daily-images/armel/daily/build_iop32x_netboot.log * OLD BUILD:armel May 10 08:12 buildd@ancina build_iop32x_network-console_glantank http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_glantank.log * FAILED BUILD: armel May 10 08:12 buildd@ancina build_iop32x_network-console_glantank http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_glantank.log * OLD BUILD:armel May 10 08:12 buildd@ancina build_iop32x_network-console_n2100 http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_n2100.log * FAILED BUILD: armel May 10 08:12 buildd@ancina build_iop32x_network-console_n2100 http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_n2100.log * OLD BUILD:armel May 10 08:13 buildd@ancina build_iop32x_network-console_ss4000e http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_ss4000e.log * FAILED BUILD: armel May 10 08:13 buildd@ancina build_iop32x_network-console_ss4000e http://d-i.debian.org/daily-images/armel/daily/build_iop32x_network-console_ss4000e.log * OLD BUILD:armel May 10 08:13 buildd@ancina build_kirkwood_netboot http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot.log * FAILED BUILD: armel May 10 08:13 buildd@ancina build_kirkwood_netboot http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot.log * OLD BUILD:armel May 10 08:14 buildd@ancina build_kirkwood_netboot-gtk http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log * FAILED BUILD: armel May 10 08:14 buildd@ancina build_kirkwood_netboot-gtk http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_netboot-gtk.log * OLD BUILD:armel May 10 08:15 buildd@ancina build_kirkwood_network-console http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_network-console.log * FAILED BUILD: armel May 10 08:15 buildd@ancina build_kirkwood_network-console http://d-i.debian.org/daily-images/armel/daily/build_kirkwood_network-console.log * OLD BUILD:armel May 10 08:15 buildd@ancina build_orion5x_network-console http://d-i.debian.org/daily-images/armel/daily/build_orion5x_network-console.log * FAILED BUILD: armel May 10 08:15 buildd@ancina build_orion5x_network-console http://d-i.debian.org/daily-images/armel/daily/build_orion5x_network-console.log * OLD BUILD:armel May 10 08:16 buildd@ancina build_versatile_netboot http://d-i.debian.org/daily-images/armel/daily/build_versatile_netboot.log * FAILED BUILD: armel May 10 08:16 buildd@ancina build_versatile_netboot http://d-i.debian.org/daily-images/armel/daily/build_versatile_netboot.log * OLD BUILD:armel May 10 08:18 buildd@ancina build_ads_cf http://d-i.debian.org/daily-images/armel/daily/build_ads_cf.log * FAILED BUILD: i386 May 15 00:05 buildd@biber build_cdrom_isolinux http://d-i.debian.org/daily-images/i386/daily/build_cdrom_isolinux.log * FAILED BUILD: i386 May 15 00:05 buildd@biber build_cdrom_gtk http://d-i.debian.org/daily-images/i386/daily/build_cdrom_gtk.log * FAILED BUILD: i386
Re: Wheezy: Questions about UEFI boot etc.
On Tue, May 14, 2013 at 07:25:55PM +0200, Svante Signell wrote: > Hi, > (Please Cc: me, I'm not subscribed) > > I'm about to install Debian Wheezy on a ACER Predator G3620 with Windows > 8 installed. The hard disks are an 128GB SSD and 1TB HDD. I have a few > questions: > 1) I had to disable secure boot in the BIOS to be able to boot with the > CD. What is checked wrt secure boot in the BIOS? Secureboot by default on most systems will only boot code signed by Microsoft. Debian obviously isn't distributing code signed by Microsoft so secureboot won't work with it. > 2) When booting with the CD the kernel complains about no prefix set. A > serious error? (I've done the install up to the disk partitioning step) I haven't tried UEFI cd boot myself yet, but I think it uses grub, which certainly can give that error. If it boots past that, then I wouldn't worry about it. > 3) I plan to split both large disks partitions into a small W8 part and > a larger Linux part. Should I do the split in W8 or with the Wheezy CD. > The HDD has a rescue partition in the end of the disk, while the SSD has > it in the beginning. Windows's storage manage will allow you to shrink the disk (although only if it doesn't require moving files I believe). Don't create new partitions from windows though, just leave unppartitioned space. > 4) The Wheezy CD has support for UEFI boot. Should I choose that or the > traditional boot option when installing grub2? Which are the > differences? UEFI boot places the boot code in the boot partition and is then controlled by the UEFI boot manager as far as I know (I have not tried it myself yet). If UEFI boot works, then it makes sense to use it, given future machines are likely to drop lagacy boot support eventually, so if you use UEFI now, it would be easy to moee the drive to a new machine later (although windows wouldn't like it of course). > 5) Anything else I forgot? Not that I can think of. -- Len Sorensen -- 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/20130514175805.gg14...@csclub.uwaterloo.ca
Wheezy: Questions about UEFI boot etc.
Hi, (Please Cc: me, I'm not subscribed) I'm about to install Debian Wheezy on a ACER Predator G3620 with Windows 8 installed. The hard disks are an 128GB SSD and 1TB HDD. I have a few questions: 1) I had to disable secure boot in the BIOS to be able to boot with the CD. What is checked wrt secure boot in the BIOS? 2) When booting with the CD the kernel complains about no prefix set. A serious error? (I've done the install up to the disk partitioning step) 3) I plan to split both large disks partitions into a small W8 part and a larger Linux part. Should I do the split in W8 or with the Wheezy CD. The HDD has a rescue partition in the end of the disk, while the SSD has it in the beginning. 4) The Wheezy CD has support for UEFI boot. Should I choose that or the traditional boot option when installing grub2? Which are the differences? 5) Anything else I forgot? Thanks, Svante -- 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/1368552355.4575.29.camel@PackardBell-PC
Bug#626219: Installer could not detect booted USB drive in USB3 port
Hello, I tried today to install from the official Debian 7.0 i386 installer (netinst iso image) from a USB stick. From a USB3 port the system boots but then the installer fails at the cdrom detection phase. Using a USB2 port fixes the problem. After the installation I can use the USB3 ports without problem. So the installed kernel has no problem using a USB3 port. I do not have access to the machine any more. So I can't make new tests, sorry. Bye, -- Dr. Ludovic Rousseau -- 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/51926b26.2040...@free.fr
cdebconf-terminal_0.19_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 14 May 2013 16:29:20 +0200 Source: cdebconf-terminal Binary: cdebconf-gtk-terminal cdebconf-newt-terminal Architecture: source i386 Version: 0.19 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: cdebconf-gtk-terminal - cdebconf gtk plugin displaying a terminal (udeb) cdebconf-newt-terminal - cdebconf newt plugin to provide a clean terminal (udeb) Changes: cdebconf-terminal (0.19) unstable; urgency=low . [ Updated translations ] * Croatian (hr.po) by Tomislav Krznar Checksums-Sha1: 05a898138a47dfc5f99a77941a87c4c0f41dd81a 1931 cdebconf-terminal_0.19.dsc 1677e6f17c7324721bbd9bcd3d9ef594fbe06293 96848 cdebconf-terminal_0.19.tar.gz 1350b908de266a68d7beb3fbb6e3b1d8acacd44d 14790 cdebconf-gtk-terminal_0.19_i386.udeb 177055c74b0c1b2cb056fbaa957457bd536ca149 4454 cdebconf-newt-terminal_0.19_i386.udeb Checksums-Sha256: 566e5e23332b24b90b7bc56328f972198120f3235ef68abe99efbe6a44e27422 1931 cdebconf-terminal_0.19.dsc 1b60f54d2c349ad9c5fda0bf4a954dcf1c7ae2faa15ec068dcc712f2c1c45444 96848 cdebconf-terminal_0.19.tar.gz 918784ac3fd2d8b1d5b67693373893e58d3a675f0247dc7f26bd167d5788c119 14790 cdebconf-gtk-terminal_0.19_i386.udeb 5f9dc9495b1e39588638ccfe21f00042fc861ffc0cf1cd85fb5a89882194 4454 cdebconf-newt-terminal_0.19_i386.udeb Files: 841859b622a6774063ac20835203c178 1931 debian-installer extra cdebconf-terminal_0.19.dsc 53de1a7f1195c6203b5ad07576b23842 96848 debian-installer extra cdebconf-terminal_0.19.tar.gz f5854cc5fabaab79b89e667f690bf8b4 14790 debian-installer extra cdebconf-gtk-terminal_0.19_i386.udeb 2a9395ee09bea403e49ee48d3e8a05f9 4454 debian-installer extra cdebconf-newt-terminal_0.19_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBUZJe+4cvcCxNbiWoAQLv/RAAkkHQceP9EMsECKyZuauhlVZ8LaLCHcoq Fl55a/YUv2MsoMPYo4nd1ElbE8r11PCxLWZif+CQ88p5h/jdua4Wa2Vk7tZawtrC 0+7ndY1eN2v/v6GXZvrD5NubL1UVuKwTMh5sASCMZTX4sG5MEJHSb892dQcICvr4 DKcKVgnGHJ2NJP/SlB0gSWoNH1UETXG3Yj0M80y7YzDq7nHeecn3+9krFLzfOJ5u NEWThNkRvGEk3AFwDaqC3m0FGslXX0/6IGHdAZg+NDMMmhJf+y+h3epDiIhX3kro j/Fico4frBp/b/D32E0U/jEa4QsDZlIgUXbywpindxUbA/fns6fT+BDZN1urxD+c gf3nlgocR5LzlIsgg/lCuz9LeaFLpDWRqIsPUJawQoN7hf2xTPCJS9pAGHypjz65 XLRkCVrqymMdi3iV2nxxH89FTxrw1aGIai2a0HXYfVNoeP2OPGjiCbrNS5FTHVtB COOTzo4L5QZ7h60HMYxiGH3ovzjOSXOBQgYZYriSOq+ccIOUAJWLEFEo81aO/2Md pyEaEPKYOzvPcVjUFW7tDSh2Fqfg99FfeE/3KCeXcP6RVA1F5gBanmW/50OJR8x1 sZvniu0/ut+jcvXKJDftAAduryPvotT/DUn6r+lrZZwy+gHUAfSFG9AgHxpN6nMq tPyLVwzcph8= =oi9Y -END PGP SIGNATURE- 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/e1uchht-00073l...@franck.debian.org
Processing of cdebconf-terminal_0.19_i386.changes
cdebconf-terminal_0.19_i386.changes uploaded successfully to localhost along with the files: cdebconf-terminal_0.19.dsc cdebconf-terminal_0.19.tar.gz cdebconf-gtk-terminal_0.19_i386.udeb cdebconf-newt-terminal_0.19_i386.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/e1uchwp-0005g9...@franck.debian.org
Processing of cdebconf-terminal_0.19_i386.changes
cdebconf-terminal_0.19_i386.changes uploaded successfully to ftp-master.debian.org along with the files: cdebconf-terminal_0.19.dsc cdebconf-terminal_0.19.tar.gz cdebconf-gtk-terminal_0.19_i386.udeb cdebconf-newt-terminal_0.19_i386.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/e1uchtz-pa...@ravel.debian.org
cdebconf-entropy_0.25_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 14 May 2013 10:54:26 +0200 Source: cdebconf-entropy Binary: cdebconf-text-entropy cdebconf-newt-entropy cdebconf-gtk-entropy Architecture: source i386 Version: 0.25 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: cdebconf-gtk-entropy - cdebconf gtk plugin for reading from /dev/random (udeb) cdebconf-newt-entropy - cdebconf newt plugin for reading from /dev/random (udeb) cdebconf-text-entropy - cdebconf text plugin for reading from /dev/random (udeb) Changes: cdebconf-entropy (0.25) unstable; urgency=low . [ Updated translations ] * Croatian (hr.po) by Tomislav Krznar Checksums-Sha1: 55d9d5356fa491958e5f38b308a0fc804a1e72fe 2016 cdebconf-entropy_0.25.dsc 80ec476cb58bbdca3e8d6b1e67012eaa5245b1e6 109032 cdebconf-entropy_0.25.tar.gz 5a3c1623d6a9e6ac36a9dac22f77ec27acb1a493 18018 cdebconf-text-entropy_0.25_i386.udeb 8f51f6da8138363818f212ea5dabbe38677c9a83 18300 cdebconf-newt-entropy_0.25_i386.udeb 243915d3f66d784b055ba93036f1e9222ddaeb4b 17334 cdebconf-gtk-entropy_0.25_i386.udeb Checksums-Sha256: b1346a1e23a6c84526d45a2c4cdde6a63f477b5ebc5d7b32cd63775eeae0a9f6 2016 cdebconf-entropy_0.25.dsc 5bd4da6b174f3ec8987841cc004b6f267d6a2477407fcaccb53407ef1d02 109032 cdebconf-entropy_0.25.tar.gz 6c74dc77f87f5fc84597c55ddb70ecd3e71c795561a790fc1caee215d752b1dc 18018 cdebconf-text-entropy_0.25_i386.udeb cf798de10b78f40ab4eff1133cf8d16ff0c89d11c6341d2effe660e48416c7f9 18300 cdebconf-newt-entropy_0.25_i386.udeb 91fabbd358d34ee54ceaefcd5ae4df066df5d1f91198ef0acfc463c226c25f43 17334 cdebconf-gtk-entropy_0.25_i386.udeb Files: 9c7e117205c9dcd88952b0769c1b8616 2016 debian-installer extra cdebconf-entropy_0.25.dsc ac0937e56259bfd2e226d50e64eb3902 109032 debian-installer extra cdebconf-entropy_0.25.tar.gz b1c8fdefc277cf0d896b8406b00026fd 18018 debian-installer extra cdebconf-text-entropy_0.25_i386.udeb 74d0d1016581c648fda16153acb5ba9a 18300 debian-installer extra cdebconf-newt-entropy_0.25_i386.udeb 4959f6c57c35af10ecddbfae4770d416 17334 debian-installer extra cdebconf-gtk-entropy_0.25_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBUZIWw4cvcCxNbiWoAQJZfRAArmTK+Q7ZiSLppUWXjjtlOwvmDo4VzZrO lhMwev0+K9VSZlWP2vR6u+rhuNtloBol/FFv7aKeZBvGTCGqU/DeCtIpo3Gh5kwc J9RfbxmzQacK6kYYW3+XwKeAVrR/VUO5d4koz2iufPTeWvqhvZUo3J0bJdseEi6y 0usyZf/2qLYIxBFswQ9gKWAWv2D1GS+ua6Z0c3SKl8blAI5inJmeYfjbxAYUf7dU xg3qdR5lSBduRxYCEShANs6igxA3XJ7ej5h4StNLLoHJHkAAWRqjG3PDSfL40Lov vS/1dP/tkSLvLKhXas407hpV+78M60+QD/X+fA7nBBkzEj/PpYPkRFhbOjIC1Fhy DpnXn+AsAlLZ50KZ5pg6ZnYOGMLqgTWm8Ws/eIks/6cjTORZPDxfFkuqmHxokD6c fIqTgPLvhFhRITyAt2wL/9N/g9vReD/AfamuU6uYR3iXT9HcZ2+VJ+Dww8vT/ttX xHR/tG0LSmjRXO/bdTvrbqMB1m+lGekDT38MERgLvMbJwdeMols0p+81n/z8FEvk CoGBGir5T93hqPLE/71Htq5QifMUdpu1EgHDBEWweI1Uy8VwslVx8Gs+M6sjJfH3 SG4lttcdKx4LML6+zZy2O56iwMXl/Oq+pkPzS93vvqM58AlBRZKfO98bzQc5V47s S2pYsbc7K2M= =DItp -END PGP SIGNATURE- 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/e1uccli-0007qq...@franck.debian.org
Processing of cdebconf-entropy_0.25_i386.changes
cdebconf-entropy_0.25_i386.changes uploaded successfully to localhost along with the files: cdebconf-entropy_0.25.dsc cdebconf-entropy_0.25.tar.gz cdebconf-text-entropy_0.25_i386.udeb cdebconf-newt-entropy_0.25_i386.udeb cdebconf-gtk-entropy_0.25_i386.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/e1ucckh-0006ud...@franck.debian.org
Processing of cdebconf-entropy_0.25_i386.changes
cdebconf-entropy_0.25_i386.changes uploaded successfully to ftp-master.debian.org along with the files: cdebconf-entropy_0.25.dsc cdebconf-entropy_0.25.tar.gz cdebconf-text-entropy_0.25_i386.udeb cdebconf-newt-entropy_0.25_i386.udeb cdebconf-gtk-entropy_0.25_i386.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/e1uccih-0008iu...@ravel.debian.org
preseeding de-latin1-nodeadkeys
Hi, i fail to preseed a de-latin1-nodeadkeys keymap into the Wheezy d-i. Having a de deadkeys in d-i would be acceptable but not in the final system. When i put language=en country=DE locale=en_US.UTF-8 on the tftp command line i get a german deadkeys layout. Loading a preseed.cfg with keyboard-configuration keyboard-configuration/xkb-keymap select de keyboard-configuration keyboard-configuration/variant select German - German (eliminate dead keys) keyboard-configuration keyboard-configuration/variantcode string nodeadkeys Or the whole of keyboard-configuration does not help. I am little puzzled on which preseed conf items i must set ... Flo -- Florian Lohoff f...@zz.de signature.asc Description: Digital signature
base-installer_1.131_i386.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 12 May 2013 20:09:34 +0200 Source: base-installer Binary: base-installer bootstrap-base Architecture: source all i386 Version: 1.131 Distribution: unstable Urgency: low Maintainer: Debian Install System Team Changed-By: Christian Perrier Description: base-installer - base system installation framework (udeb) bootstrap-base - Install the base system (udeb) Changes: base-installer (1.131) unstable; urgency=low . [ Updated translations ] * Croatian (hr.po) by Tomislav Krznar Checksums-Sha1: d40673db2e55d75c268f4e8bacee5a87ddf84f92 1871 base-installer_1.131.dsc a023d93796106435508c50fdad5d5e162c2fcdf9 308783 base-installer_1.131.tar.gz 42b3155fa796694404a25d4500ed4452afd4e14a 46850 base-installer_1.131_all.udeb d32e5ec72a1620f82669ed4970bf7d6befe05587 191112 bootstrap-base_1.131_i386.udeb Checksums-Sha256: aaf1d555d550980d0556515e608fd95ad318fab2fb612422b02307e39368e5f6 1871 base-installer_1.131.dsc 62873523432ac4fd50abc63a86eb36d11107a1a04e76031f73f77bdd8d43f48e 308783 base-installer_1.131.tar.gz 04818a39c9a30b356d63eb9409f206e7bcca879da622d198645843f7ddd2c2ed 46850 base-installer_1.131_all.udeb 5354df976049ad0bf34faac0e0a204801735a424d089939c71b2ef77ad9aa18e 191112 bootstrap-base_1.131_i386.udeb Files: 5c6734ffd9da6653afe4bdaf1ff162fe 1871 debian-installer required base-installer_1.131.dsc 8494b84e8797682aef9d9cddf9f7d060 308783 debian-installer required base-installer_1.131.tar.gz 4249c2e9a68debf102d5f9e61c981ef7 46850 debian-installer required base-installer_1.131_all.udeb 22bffeb24cc89f8af37d8fd7cc7eb1bd 191112 debian-installer required bootstrap-base_1.131_i386.udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIVAwUBUZH6RIcvcCxNbiWoAQLSog/+L//MCuRHF8RpNnnfzhsH3usIKp4bGggo QnlIuWIAmYVEeyNxZM9k+eQwtnvo1W5yvjcsXB0PcEtdmRZj7/i6Yl6zICyfMUmU xGSnEDx5B4QZCepSN3KXfSGh2PpSUJzD5CUu5dihyKE02zPkSdSTyvewvzgc6Bsp VtFurT8k6p2Wk5/vr3bzd2Lf83rmr6CvKO5ABP4+gZiS9jVdQDayRe1IbgmWggxO AXs9GEfBbnAx6EiVEQ5K0/eQU01S20Y8BUb66qXOtkjbiwTZLRn5U2gtjORxf61Q l3DYJ4MGkfNwx59o3A9YVoVk9r4g/K8Zt6CN5sWRwqctpP4yuhKe3A5R+JO8D+cf TAcHrjVZCSHJaAvZcaCx5DKJcpcK83HAbY7nvRbV8eMkADm2OdiNTa08BQcQSOKw nuwE+RP5jkt0LAGBmA6Nn+lP1fPOeEkTavBpV7sVJNhG33ntVVycf8Vpf8i1q9Is oU+1+Pwmb2lGs5u5upMJ0y413XvpBNrBzx6AXB6osxTf2keP9L6edB7frwkEXCy/ uq4kRiDPL4tYtGE6PQM9Xr5cF865GkZ50QBEaMTZqEkgVueT4U9Stj++9Gj7W4tQ 0rPR/YETjZ+QTPfBLulRLcI/n1SNouyE+iL20IdvFb9tkUbTHKLZShPSuYNII3ZO XbsJXTCp6FA= =YoRX -END PGP SIGNATURE- 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/e1ucb8h-0002fl...@franck.debian.org
Bug#697675: debootstrap: please report package version-revision (patch)
Hello, On Mon, Jan 28, 2013 at 03:04:59AM +0100, Cyril Brulebois wrote: > Hector Oron (08/01/2013): > > On Tue, Jan 08, 2013 at 11:02:19AM +0100, Hector Oron wrote: > > > When using debootstrap to create a given environment, it would > > > be nice to output version-revision information to keep track of > > > which software version components are installed. > > Please review and consider following patch: […] > looks like a nice idea, but a bit late for wheezy, so that might wait > until the jessie release cycle. As release has already happened, I'll go ahead and push the patch into debootstrap, unless someone complains loud. Regards -- Hector Oron signature.asc Description: Digital signature
Processing of base-installer_1.131_i386.changes
base-installer_1.131_i386.changes uploaded successfully to localhost along with the files: base-installer_1.131.dsc base-installer_1.131.tar.gz base-installer_1.131_all.udeb bootstrap-base_1.131_i386.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/e1ucamu-0006nh...@franck.debian.org
Processing of base-installer_1.131_i386.changes
base-installer_1.131_i386.changes uploaded successfully to ftp-master.debian.org along with the files: base-installer_1.131.dsc base-installer_1.131.tar.gz base-installer_1.131_all.udeb bootstrap-base_1.131_i386.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/e1ucale-0003zn...@ravel.debian.org
Processed: found 672160 in 1.93
Processing commands for cont...@bugs.debian.org: > found 672160 1.93 Bug #672160 [console-setup] console-setup: unowned files after purge (policy 6.8, 10.8) Marked as found in versions console-setup/1.93. > thanks Stopping processing here. Please contact me if you need assistance. -- 672160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=672160 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.136852013114921.transcr...@bugs.debian.org
