Re: New partman-basicfilesystems debconf templates
Quoting Christian PERRIER (bubu...@debian.org): > Hello Milan, > > I noticed that you added new templates to partman-basicfilesystems for > the following: > > * Warn if bootable partition is not ext2 on Pegasos machines. Closes: > #717511 Thanks for your comments. I finally left the templates unchanges and turned them to translatable in sublevel 5 (uncommon architectures+messages that do not appear in default installs) I might be changing the templates slightly later on as I noticed there are remaining "double spaces after full stop", which we in the past decided to hunt down. However, as other D-I packages also have these, that will be part of a more general action (with unfuzzyfication of translations). signature.asc Description: Digital signature
Re: New partman-basicfilesystems debconf templates
On 20130727_122708, Rick Thomas wrote: > > On Jul 26, 2013, at 11:23 PM, Christian PERRIER wrote: > > >Hello Milan, > > > >I noticed that you added new templates to partman-basicfilesystems for > >the following: > > > > * Warn if bootable partition is not ext2 on Pegasos machines. > >Closes: #717511 > > > >I'll turn these templates to translatable (they are not, yet) and mark > >them for sublevel 4 or 5 (belong to "less common" architectures). > > > >However, before doing that, I'd like to use the same wording than > >other similar templates (so that translations can be re-used). > > > >Particularly, the following: > > > >Template: partman-basicfilesystems/boot_not_first_partition > >Type: boolean > >Description: Go back to the menu and correct this problem? > >Your boot partition is not located on the first partition of your > >hard disk. This is needed by your machine in order to boot. Please go > >back and use your first partition as a boot partition. > >. > >If you do not go back to the partitioning menu and correct this error, > >the partition will be used as is. This means that you may not be able > >to boot from your hard disk. > > > >We already have such a template, but it says "on the first PRIMARY > >partition". Would it be wrong to add this "primary" word to the > >templates you added? > > I may be sticking my nose in where it's not appropriate, but... I am sticking my nose in where it doesn't belong, but ... I had always supposed that the boot flag was required by DOS BIOS, and only by DOS, and was required only because DOS was badly designed. I know I have never set the boot flag on the root partition of my Debian installs. Sometimes the flag is set automatically, sometimes not. I have never had to reinstall, or jump through any hoops to get an install to boot. I had lots of other problems but never that one. Is Pegasos special, in that it resurrects (from DOS) this design flaw? And when I install a dual boot, preserving a DOS partition that is already installed, I am careful to keep the boot flag set on the DOS partition, where I think it belongs. Other opinions? I have been wrong before on other topics. Cheers > > The word "primary" refers to a peculiarity of the PC-style MBR > partitioning scheme. I believe Pegasos uses a very different > partitioning scheme, so adding "primary" would be incorrect and > confusing. > > The Wikipedia article on Pegasos -- http://en.wikipedia.org/wiki/ > Pegasos says, "For hard disk drive booting the [Pegasos] Open > Firmware requires an RDB boot partition that contains either an affs1 > or ext2 partition". Following the link to the Wikipedia article on > RDB explains the differences between MBR and RDB partitioning. It > says, "Because [with RDB] there is no limitation in partition block > count, there is no need to distinguish primary and extended types and > all partitions are equal in stature and architecture." > > I don't have a Pegasos machine, so I'm just repeating what I read by > Googling, but I do have a number of PowerPC Macs running Debian and I > know they don't use MBR partitioning, so my interest was piqued. > > Rick > > > -- > 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/332b4c3a-8370-4b2f-ab28-166fffb18...@pobox.com > -- Paul E Condon pecon...@mesanetworks.net -- 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/20130728011036.GA20388@big
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: amd64 Jul 28 00:07 buildd@barber build_netboot http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log * FAILED BUILD: amd64 Jul 28 00:07 buildd@barber build_netboot-gtk http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log * FAILED BUILD: amd64 Jul 28 00:07 buildd@barber build_netboot-xen http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log * OLD BUILD:armhf Jul 25 09:41 buildd@hasse build_mx5_netboot http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot.log * OLD BUILD:armhf Jul 25 09:44 buildd@hasse build_mx5_network-console http://d-i.debian.org/daily-images/armhf/daily/build_mx5_network-console.log * OLD BUILD:armhf Jul 25 09:51 buildd@hasse build_mx5_netboot-gtk http://d-i.debian.org/daily-images/armhf/daily/build_mx5_netboot-gtk.log * OLD BUILD:armhf Jul 25 09:54 buildd@hasse build_vexpress_netboot http://d-i.debian.org/daily-images/armhf/daily/build_vexpress_netboot.log * FAILED BUILD: i386 Jul 28 00:08 buildd@biber build_netboot http://d-i.debian.org/daily-images/i386/daily/build_netboot.log * FAILED BUILD: i386 Jul 28 00:08 buildd@biber build_netboot-gtk http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log * FAILED BUILD: i386 Jul 28 00:09 buildd@biber build_netboot-xen http://d-i.debian.org/daily-images/i386/daily/build_netboot-xen.log * OLD BUILD:ia64 May 26 00:12 buildd@alkman build_cdrom http://d-i.debian.org/daily-images/ia64/daily/build_cdrom.log * OLD BUILD:ia64 May 26 00:16 buildd@alkman build_netboot http://d-i.debian.org/daily-images/ia64/daily/build_netboot.log * FAILED BUILD: kfreebsd-amd64 Jul 28 00:33 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * FAILED BUILD: kfreebsd-amd64 Jul 28 00:35 buildd@fano build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log * FAILED BUILD: kfreebsd-amd64 Jul 28 00:37 buildd@fano build_netboot-gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log * FAILED BUILD: kfreebsd-amd64 Jul 28 00:40 buildd@fano build_netboot-gtk-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk-9.log * FAILED BUILD: kfreebsd-i386 Jul 28 00:34 buildd@finzi build_netboot http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log * FAILED BUILD: kfreebsd-i386 Jul 28 00:37 buildd@finzi build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot-9.log * OLD BUILD:mips Jul 26 00:30 buildd@lucatelli build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_malta_netboot-2.6.log * FAILED BUILD: mips Jul 26 00:30 buildd@lucatelli build_malta_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_malta_netboot-2.6.log * OLD BUILD:mips Jul 26 00:31 buildd@lucatelli build_r4k-ip22_cdrom-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_cdrom-2.6.log * FAILED BUILD: mips Jul 26 00:31 buildd@lucatelli build_r4k-ip22_cdrom-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_cdrom-2.6.log * OLD BUILD:mips Jul 26 00:31 buildd@lucatelli build_r4k-ip22_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_netboot-2.6.log * FAILED BUILD: mips Jul 26 00:31 buildd@lucatelli build_r4k-ip22_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r4k-ip22_netboot-2.6.log * OLD BUILD:mips Jul 26 00:32 buildd@lucatelli build_r5k-ip32_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r5k-ip32_netboot-2.6.log * FAILED BUILD: mips Jul 26 00:32 buildd@lucatelli build_r5k-ip32_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_r5k-ip32_netboot-2.6.log * OLD BUILD:mips Jul 26 00:33 buildd@lucatelli build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_sb1-bcm91250a_netboot-2.6.log * FAILED BUILD: mips Jul 26 00:33 buildd@lucatelli build_sb1-bcm91250a_netboot-2.6 http://d-i.debian.org/daily-images/mips/daily/build_sb1-bcm91250a_netboot-2.6.log * OLD BUILD:mips Jul 26 00:33 buildd@lucatelli build_miniiso http://d-i.debian.org/daily-images/mips/daily/build_miniiso.log * FAILED BUILD: mips Jul 26 00:33 buildd@lucatelli build_miniiso http://d-i.debian.org/daily-images/mips/daily/build_miniiso.log * FAILED BUILD: powerpc Jul 28
Re: New partman-basicfilesystems debconf templates
On Jul 27, 2013, at 12:27 PM, Rick Thomas wrote: On Jul 26, 2013, at 11:23 PM, Christian PERRIER wrote: ... We already have such a template, but it says "on the first PRIMARY partition". Would it be wrong to add this "primary" word to the templates you added? ... The word "primary" refers to a peculiarity of the PC-style MBR partitioning scheme. I believe Pegasos uses a very different partitioning scheme, so adding "primary" would be incorrect and confusing. ... Googling a bit more, it looks like [1] the Pegasos Open Firmware does have some limited support for MS-DOS style MBR partitioning of the boot disk. In this case, the boot partition can *only* be primary -- it doesn't understand extended or logical partitions. So the question of whether "primary" is appropriate depends on whether you are using Amiga style or MS-DOS style partitioning. Curiousser and curiousser cried Alice! Rick [1] http://old-en.opensuse.org/PegasosQuickStart -- 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/25de75b5-1812-45c0-8d36-0671e2976...@pobox.com
Re: New partman-basicfilesystems debconf templates
On 07/27/2013 02:23 AM, Christian PERRIER wrote: Hello Milan, I noticed that you added new templates to partman-basicfilesystems for the following: * Warn if bootable partition is not ext2 on Pegasos machines. Closes: #717511 I'll turn these templates to translatable (they are not, yet) and mark them for sublevel 4 or 5 (belong to "less common" architectures). However, before doing that, I'd like to use the same wording than other similar templates (so that translations can be re-used). Particularly, the following: Template: partman-basicfilesystems/boot_not_first_partition Type: boolean Description: Go back to the menu and correct this problem? Your boot partition is not located on the first partition of your hard disk. This is needed by your machine in order to boot. Please go back and use your first partition as a boot partition. . If you do not go back to the partitioning menu and correct this error, the partition will be used as is. This means that you may not be able to boot from your hard disk. We already have such a template, but it says "on the first PRIMARY partition". Would it be wrong to add this "primary" word to the templates you added? The partition table on this platform has no concept of primary and secondary class of partitions. Therefore, the word "primary" is not technically correct if you contrast it with the same word as used in DOS partition table concept. But the word itself does not change the message to the user that the partition should be first. FYI I've found the same message in templates of partman-ext2r0 and partman-ext3 packages, where I actually took the text from. The best, Milan -- 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/51f41d90.3050...@physics.harvard.edu
Re: New partman-basicfilesystems debconf templates
On Jul 26, 2013, at 11:23 PM, Christian PERRIER wrote: Hello Milan, I noticed that you added new templates to partman-basicfilesystems for the following: * Warn if bootable partition is not ext2 on Pegasos machines. Closes: #717511 I'll turn these templates to translatable (they are not, yet) and mark them for sublevel 4 or 5 (belong to "less common" architectures). However, before doing that, I'd like to use the same wording than other similar templates (so that translations can be re-used). Particularly, the following: Template: partman-basicfilesystems/boot_not_first_partition Type: boolean Description: Go back to the menu and correct this problem? Your boot partition is not located on the first partition of your hard disk. This is needed by your machine in order to boot. Please go back and use your first partition as a boot partition. . If you do not go back to the partitioning menu and correct this error, the partition will be used as is. This means that you may not be able to boot from your hard disk. We already have such a template, but it says "on the first PRIMARY partition". Would it be wrong to add this "primary" word to the templates you added? I may be sticking my nose in where it's not appropriate, but... The word "primary" refers to a peculiarity of the PC-style MBR partitioning scheme. I believe Pegasos uses a very different partitioning scheme, so adding "primary" would be incorrect and confusing. The Wikipedia article on Pegasos -- http://en.wikipedia.org/wiki/ Pegasos says, "For hard disk drive booting the [Pegasos] Open Firmware requires an RDB boot partition that contains either an affs1 or ext2 partition". Following the link to the Wikipedia article on RDB explains the differences between MBR and RDB partitioning. It says, "Because [with RDB] there is no limitation in partition block count, there is no need to distinguish primary and extended types and all partitions are equal in stature and architecture." I don't have a Pegasos machine, so I'm just repeating what I read by Googling, but I do have a number of PowerPC Macs running Debian and I know they don't use MBR partitioning, so my interest was piqued. Rick -- 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/332b4c3a-8370-4b2f-ab28-166fffb18...@pobox.com
