New partman-basicfilesystems debconf templates
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? -- signature.asc Description: Digital signature
Processed: Bug#717511: partman-basicfilesystems: warn if bootable partition is not ext2 on Pegasos machines
Processing commands for cont...@bugs.debian.org: > tags 717511 pending Bug #717511 [partman-basicfilesystems] Bug#717511: partman-basicfilesystems: warn if bootable partition is not ext2 on Pegasos machines Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 717511: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717511 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.13749010537387.transcr...@bugs.debian.org
Debian installer build: failed or old builds
Debian installer build overview --- Failed or old builds: * FAILED BUILD: amd64 Jul 27 00:07 buildd@barber build_netboot http://d-i.debian.org/daily-images/amd64/daily/build_netboot.log * FAILED BUILD: amd64 Jul 27 00:07 buildd@barber build_netboot-gtk http://d-i.debian.org/daily-images/amd64/daily/build_netboot-gtk.log * FAILED BUILD: amd64 Jul 27 00:07 buildd@barber build_netboot-xen http://d-i.debian.org/daily-images/amd64/daily/build_netboot-xen.log * FAILED BUILD: i386 Jul 27 00:08 buildd@biber build_netboot http://d-i.debian.org/daily-images/i386/daily/build_netboot.log * FAILED BUILD: i386 Jul 27 00:08 buildd@biber build_netboot-gtk http://d-i.debian.org/daily-images/i386/daily/build_netboot-gtk.log * FAILED BUILD: i386 Jul 27 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 27 00:32 buildd@fano build_netboot http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot.log * FAILED BUILD: kfreebsd-amd64 Jul 27 00:33 buildd@fano build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-9.log * FAILED BUILD: kfreebsd-amd64 Jul 27 00:36 buildd@fano build_netboot-gtk http://d-i.debian.org/daily-images/kfreebsd-amd64/daily/build_netboot-gtk.log * FAILED BUILD: kfreebsd-amd64 Jul 27 00:39 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 27 00:33 buildd@finzi build_netboot http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot.log * FAILED BUILD: kfreebsd-i386 Jul 27 00:36 buildd@finzi build_netboot-9 http://d-i.debian.org/daily-images/kfreebsd-i386/daily/build_netboot-9.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 * 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 * 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 * 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 * 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 * 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 27 00:02 buildd@praetorius build_powerpc_netboot http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_netboot.log * FAILED BUILD: powerpc Jul 27 00:02 buildd@praetorius build_powerpc_netboot-gtk http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc_netboot-gtk.log * FAILED BUILD: powerpc Jul 27 00:05 buildd@praetorius build_powerpc64_netboot http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc64_netboot.log * FAILED BUILD: powerpc Jul 27 00:05 buildd@praetorius build_powerpc64_netboot-gtk http://d-i.debian.org/daily-images/powerpc/daily/build_powerpc64_netboot-gtk.log * FAILED BUILD: amd64 Jul 26 21:52 debian-cd@pettersson 2sidmips http://cdbuilder.debian.org/cdimage-log/2sidmips Totals: 126 builds (23 failed, 2 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/e1v2srg-0004oc...@ravel.debian.org
Bug#716935: What i have done
Hello Holger At your last post, you asked: > I'm not sure I get what you are doing: what self made iso image are you > coping > onto which official image? What i have done: 1. I prepared an USB stick for loading the hd-media images. The procedure is described in the installation manual at chapter 4.3.3: "4.3.3. Manually copying files to the USB stick - the flexible way". 2. As a next step, i copied the kernel images vmlinuz and initrd.gz from the daily builds in hd-media to the USB stick. Booting from USB stick works. 3. As described in chapter 4.3.3.2 "Adding the installer image", i copied an ISO image to the USB stick. Searching for ISO image on USB stick fails. With the images from wheezy, installation from USB stick is successfully. With the current daily images, installation fails. I had a look in the current changelog for linux kernel in subversion. At revision 20357, there is the following entry: > -add ehci-pci to usb-modules to get back usb during installation Possibly, we only have to wait for the new kernel. I'll test the installation, after new kernel is available in sid. Best regards Bernhard signature.asc Description: OpenPGP digital signature
Bug#717792: marked as done (Should generate secondary locales in some cases)
Your message dated Fri, 26 Jul 2013 10:01:54 +0200 with message-id <51f22cf2.2090...@prezent.nl> and subject line Re: Bug#717792: debian-installer: locale warnings after clean installation in US English with Dutch timezone has caused the Debian Bug report #717792, regarding Should generate secondary locales in some cases 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.) -- 717792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: debian-installer Severity: normal Tags: d-i I installed a clean Debian Wheezy 7.1 using the following options: - US English language - Europe/Ansterdam timezone - US keymap Pretty common in The Netherlands. With these options, the locales are not correctly generated. Output of `locale`: LANG=en_US.UTF-8 LANGUAGE=en_US:en LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME=nl_NL.utf8 LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= Everything is set to en_US, except for LC_TIME which is nl_NL. Problem is that during installation Debian doesn't actually generate the nl_NL locale. So, on every new machine I always get perl warnings about missing locales. I always have to run `dpkg-reconfigure locales` and add nl_NL.UTF-8 myself. IMHO the installer should add this locale during the installation process. Kind regards, Sander Marechal -- System Information: Debian Release: 7.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- On 26-07-13 09:17, Samuel Thibault wrote: > Did you follow exactly the same steps as I did? Did you install any > package beyond just the base? (i.e. not even the standard task). Can > you find out where in /etc LC_TIME gets defined? I think I found the problem. It's the SSH client. It passes LC_TIME from my host system to the newly installed system in a default ssh client setup. Most of our workstations have LC_TIME=nl_NL.UTF-8 set so we get MDY instead of DMY date formatting. If I login directly though the VirtualBox console I don't get any locale warnings and LC_TIME is set to en_US.UTF-8 like the rest of the locale settings. So, I guess bug is invalid. My apologies. -- Sander Marechal--- End Message ---
Bug#717791: debian-installer: virtualbox guest additions not installed correctly
Christian PERRIER (2013-07-25): > Quoting Sander Marechal (san...@prezent.nl): > > Package: debian-installer > > Severity: normal > > Tags: d-i > > > > I installed a clean Debian Wheezy 7.1. The installer correctly > > determined that it was running in a Virtualbox VM and installed the > > virtualbox guest additions. The problem is that the additions were > > not correctly installed. The kernel module wasn't built so the guest > > additions did not work. > > > > I first had to install the build-essentials myself. Also, the > > installer installed the wrong kernel headers for my kernel. The > > debian installation came out running the -486 kernel but the > > installer installed the -686-pae kernel headers. > > > > IMHO if the debian installer installs the virtualbox guest > > additions, it should also build and load the kernel module. Strange, ISTR that did work (and that was taking a fair amount of CPU time). Attaching your installer logs would be nice (I guess we only need syslog); /var/log/installer to the rescue. > To be confirmed but I suspect this is not the installer that > triggerred the installation of virtualbox extensions. > > I see nothing in tasksel's tasks that is related to virtualbox or > virtualization. Yeah, I needed a few minutes to find out, that's actually pulled through discover/discover-data: | discover-data (2.2010.10.14) unstable; urgency=low | | * Update HW mappings for PCI devices: | 8086:3582: install i810switch. | 80ee:beef: Install virtualbox-ose-guest-x11. | […] | | -- Petter Reinholdtsen Thu, 14 Oct 2010 23:07:42 +0200 Mraw, KiBi. -- 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/20130726091036.gb22...@mraw.org
Bug#717792: debian-installer: locale warnings after clean installation in US English with Dutch timezone
On 26-07-13 09:17, Samuel Thibault wrote: > Did you follow exactly the same steps as I did? Did you install any > package beyond just the base? (i.e. not even the standard task). Can > you find out where in /etc LC_TIME gets defined? I think I found the problem. It's the SSH client. It passes LC_TIME from my host system to the newly installed system in a default ssh client setup. Most of our workstations have LC_TIME=nl_NL.UTF-8 set so we get MDY instead of DMY date formatting. If I login directly though the VirtualBox console I don't get any locale warnings and LC_TIME is set to en_US.UTF-8 like the rest of the locale settings. So, I guess bug is invalid. My apologies. -- Sander Marechal -- 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/51f22cf2.2090...@prezent.nl
Bug#717791: debian-installer: virtualbox guest additions not installed correctly
On 25-07-13 18:45, Christian PERRIER wrote: > Quoting Sander Marechal (san...@prezent.nl): >> Package: debian-installer >> Severity: normal >> Tags: d-i >> >> I installed a clean Debian Wheezy 7.1. The installer correctly determined >> that it >> was running in a Virtualbox VM and installed the virtualbox guest additions. >> The >> problem is that the additions were not correctly installed. The kernel >> module wasn't >> built so the guest additions did not work. >> >> I first had to install the build-essentials myself. Also, the installer >> installed >> the wrong kernel headers for my kernel. The debian installation came out >> running the >> -486 kernel but the installer installed the -686-pae kernel headers. >> >> IMHO if the debian installer installs the virtualbox guest additions, it >> should also >> build and load the kernel module. > > To be confirmed but I suspect this is not the installer that > triggerred the installation of virtualbox extensions. > > I see nothing in tasksel's tasks that is related to virtualbox or > virtualization. I found a couple of blog posts that indicate the D-I does detect it. Perhaps in some other part of D-I than tasksel? For example: http://www.calebscreek.com/2010/08/how-to-install-virtualbox-ose-guest-additions-in-debian-testing-squeeze/ http://tech.barwick.de/linux/installing-debian-virtualbox-guestadditions.html http://www.printandweb.ca/2013/05/installing-guest-additions-for.html For reference, during installation I choose the "ssh-server" and "standard" options in tasksel. -- Sander Marechal -- 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/51f22397.1060...@prezent.nl
Bug#717792: debian-installer: locale warnings after clean installation in US English with Dutch timezone
On 26-07-13 09:17, Samuel Thibault wrote: > Sander Marechal, le Fri 26 Jul 2013 09:11:13 +0200, a écrit : >> Absolutely sure. I did a clean install in a Virtualbox VM, just >> following the console installer (not the GUI one). > > Did you follow exactly the same steps as I did? Did you install any > package beyond just the base? (i.e. not even the standard task). Can > you find out where in /etc LC_TIME gets defined? I installed the "standard" and "ssh-server" task. I'll try to reproduce the problem selecting no tasks. -- Sander -- 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/51f223ce.3000...@prezent.nl
Bug#717792: debian-installer: locale warnings after clean installation in US English with Dutch timezone
On 25-07-13 22:10, Samuel Thibault wrote: > Mmm, I couldn't achieve that. I have: > > - selected english > - selected netherlands > - selected the en_US.UTF-8 locale > - selected US keymap > > and used default values for the rest. > > The installed system has en_US.UTF-8 as locale: /etc/environment > contains: > > # File generated by update-locale > LANG="en_US.UTF-8" > LANGUAGE="en_US:en" > > I don't see where LC_TIME=nl_NL.utf8 would come from. Are you sure you > didn't modify your environment? Absolutely sure. I did a clean install in a Virtualbox VM, just following the console installer (not the GUI one). The VM clock was set to UTC. I have been having this same problem with Debian 6.0, 7.0 and 7.1 netinst CD's. The problem shows up as soon as I do for example `aptitude install `. Perhaps LC_TIME is set based off something else? When I install new machines I am *in* the Netherlands. Perhaps it guesses your location from the network connection? Or perhaps from the mirror? I always use ftp.nl.debian.org as the mirror for a netinst. -- Sander Marechal -- 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/51f22111.8040...@prezent.nl
Bug#717792: debian-installer: locale warnings after clean installation in US English with Dutch timezone
Sander Marechal, le Fri 26 Jul 2013 09:11:13 +0200, a écrit : > Absolutely sure. I did a clean install in a Virtualbox VM, just > following the console installer (not the GUI one). Did you follow exactly the same steps as I did? Did you install any package beyond just the base? (i.e. not even the standard task). Can you find out where in /etc LC_TIME gets defined? Samuel -- 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/20130726071748.gn5...@type.youpi.perso.aquilenet.fr
