Processed: Re: Bug#768788: Acknowledgement (Recent installer versions using the wrong GPT partition type GUID for EFI System Partition)
Processing control commands: reassign -1 partman-efi Bug #768788 [partmen-efi] Recent installer versions using the wrong GPT partition type GUID for EFI System Partition Warning: Unknown package 'partmen-efi' Bug reassigned from package 'partmen-efi' to 'partman-efi'. Ignoring request to alter found versions of bug #768788 to the same values previously set Ignoring request to alter fixed versions of bug #768788 to the same values previously set -- 768788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768788 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: https://lists.debian.org/handler.s.b768788.141552859310675.transcr...@bugs.debian.org
d-i talk at Cambridge mini-DebConf
Hi people, I've just given a d-i talk at Cambridge mini-DebConf; you'll find the slides available here: https://people.debian.org/~kibi/talks/2014-11-09-Cambridge-mini-DebConf--jessie-wrap-up.pdf TL;DR: that was mainly about thanking people who either contributed a particular fix, or are maintaining a particular component, or have been contributing for a very long time. Joey, I can't really convey this by email, but the last slide was received with warm applause. Thank you so much, for everything. Mraw, KiBi. signature.asc Description: Digital signature
Processed: jessie + wheezy-ignore
Processing commands for cont...@bugs.debian.org:
tags 559767 + sid jessie
Bug #559767 [java3d] java3d: FTBFS on armel: install: cannot stat
`j3d-core/build/default/opt/native/libj3dcore-ogl.so': No such file or directory
Added tag(s) sid and jessie.
tags 767589 + sid jessie
Bug #767589 [initramfs-tools] systemd: cryptdisks other than root/swap fail
cryptsetup
Added tag(s) sid and jessie.
tags 719519 + sid jessie
Bug #719519 {Done: Bernd Zeimetz b...@debian.org} [lua-json] lua-json:
Current version of lua-json conflicts with lpeg
Added tag(s) sid and jessie.
tags 768788 + sid jessie
Bug #768788 [partman-efi] Recent installer versions using the wrong GPT
partition type GUID for EFI System Partition
Added tag(s) sid and jessie.
tags 768547 + wheezy-ignore
Bug #768547 [gnat-gps-doc] gnat-gps-doc: wrong license for user guide (GPL
instead of GFDL)
Added tag(s) wheezy-ignore.
tags 768597 + wheezy-ignore
Bug #768597 [src:libgtkada] libgtkada: GFDL non free file with front cover
Added tag(s) wheezy-ignore.
tags 768539 + wheezy-ignore
Bug #768539 [src:libgtkada] gtkada: GFDL non free file with front cover
Added tag(s) wheezy-ignore.
#as per https://lists.debian.org/debian-release/2013/12/msg00446.html
End of message, stopping processing here.
Please contact me if you need assistance.
--
559767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559767
719519: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719519
767589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767589
768539: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768539
768547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768547
768597: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768597
768788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768788
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:
https://lists.debian.org/handler.s.c.141553942720399.transcr...@bugs.debian.org
Bug#764437: console-setup hangs during install in jessie/wheezy on eeepc 1005ha
On Wed, Oct 08, 2014 at 01:13:16AM -0400, marv wrote: After doing so and booting the now successful install, renaming /usr/bin/ckbcomp back, the system will not boot any more. I don't think there is anything hardware-specific in ckbcomp. Try running ckbcomp us I suppose everything will be OK with ckbcomp. If this is so, then the next suspect is /bin/setupcon. Try restoring ckbcomp and running setupcon by hand (from the text console). Does it work? If no, then this is good as it will be easier to debug. Please run sh -x /bin/setupcon /tmp/setupcon.debug and send the file setupcon.debug. Otherwise (that is if setupcon works), there must be something early during the boot process causing the problem. In this case you can replace the line if setupcon -k 2/dev/null; then in the script /etc/init.d/keyboard-setup with if setupcon -k 2/tmp/setupcon.debug; then Then send us the content of the file setupcon.debug. Anton Zinoviev P.S. In case this laptop is a multiuser system, don't forget to restore the original content of /etc/init.d/keyboard-setup because ouputting to a fixed file name in a world-writtable directory is a security risk. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141109142011.gc2...@debian.lan
Bug#745262: console-setup: Caps lock doesn't take effect on øæå (Danish characters)
On Wed, Aug 13, 2014 at 12:47:26AM +0200, Samuel Thibault wrote: Anton Zinoviev, le Wed 06 Aug 2014 20:39:02 +0300, a écrit : On Sun, Apr 20, 2014 at 10:35:23PM +0200, Samuel Thibault wrote: Oops, indeed, it seems the version in Jessie does not properly defines the ctrll layer for upper cases like it used to in Wheezy. See ckbcomp dk: keycode 39 = +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute It uses only +U+00e6 +U+00c6, while it should use +U+00c6 +U+00e6 for ctrll layers. I am unable to reproduce this. What locale do you use? I've tested with LC_ALL=C, LC_ALL=da_DK.utf8 and LC_ALL=da_DK. Well, whatever the locale, LC_ALL=C for instance, I get only +U+00e6 +U+00c6, and never +U+00c6 +U+00e6. I've tried both console-setup 1.102 and 1.111. I just wanted to mention that I've never been able to reproduce this. I have tried this in clean install of jessie with Gnome, both i386 and amd64. Anton Zinoviev -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141109152953.ga6...@debian.lan
Bug#745262: console-setup: Caps lock doesn't take effect on øæå (Danish characters)
Anton Zinoviev, le Sun 09 Nov 2014 17:29:53 +0200, a écrit : On Wed, Aug 13, 2014 at 12:47:26AM +0200, Samuel Thibault wrote: Anton Zinoviev, le Wed 06 Aug 2014 20:39:02 +0300, a écrit : On Sun, Apr 20, 2014 at 10:35:23PM +0200, Samuel Thibault wrote: Oops, indeed, it seems the version in Jessie does not properly defines the ctrll layer for upper cases like it used to in Wheezy. See ckbcomp dk: keycode 39 = +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute It uses only +U+00e6 +U+00c6, while it should use +U+00c6 +U+00e6 for ctrll layers. I am unable to reproduce this. What locale do you use? I've tested with LC_ALL=C, LC_ALL=da_DK.utf8 and LC_ALL=da_DK. Well, whatever the locale, LC_ALL=C for instance, I get only +U+00e6 +U+00c6, and never +U+00c6 +U+00e6. I've tried both console-setup 1.102 and 1.111. I just wanted to mention that I've never been able to reproduce this. I have tried this in clean install of jessie with Gnome, both i386 and amd64. I don't have the issue any more currently on my Jessie system. Andreas, do you still have the issue? Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141109155710.ga3...@type.youpi.perso.aquilenet.fr
Re: vt2-6 still not available with base system
Hi Samuel Am 08.11.2014 um 12:54 schrieb Samuel Thibault: Hello, I've just checked this morning with the latest netboot, when installing just the base system with no task, dbus does not get installed, and thus vt2-6 do not have a login banner because systemd-logind needs dbus for that. In 758111, systemd was made to recommend dbus so that it works on system upgrade, and in 759293 dbus was made priority standard in the archive. But this is not enough for making d-i install dbus on just a base system. Just to make sure we agree on this: do we want to install dbus in a base system without the standard task? It's not very big: 1MiB installed files. It is also getting more and more used by basic things in the system. And not getting vt2-6 working on a base system is a bit ew. Running for i in `seq 2 6` ; do systemctl enable getty@tty$i.service; done on a system without dbus, would statically enable a getty on vt2-6. So we could simply document this fact (in README.Debian, release notes etc). The alternative would be, to bump dbus to priority standard, so it's installed by default (on new installations). I think Simon wasn't to keen on raising the prio of dbus further. I've CCed him for his input. A third idea would be to have a generator, which creates the getty@tty$i.service symlinks in /run/systemd/system/getty.target.wants Implementing that in shell, would only take a couple of lines. We should be careful though, to add yet another generator. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: vt2-6 still not available with base system
Michael Biebl, le Sun 09 Nov 2014 19:56:40 +0100, a écrit : Running for i in `seq 2 6` ; do systemctl enable getty@tty$i.service; done on a system without dbus, would statically enable a getty on vt2-6. I know, but I don't think we want to make the user have to do that. So we could simply document this fact (in README.Debian, release notes etc). The alternative would be, to bump dbus to priority standard, so it's installed by default (on new installations). It is already priority standard. That is not enough to make it part of the base system though. A third idea would be to have a generator, which creates the getty@tty$i.service symlinks in /run/systemd/system/getty.target.wants Implementing that in shell, would only take a couple of lines. We should be careful though, to add yet another generator. Yes :/ Samuel -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141109190412.gg3...@type.youpi.perso.aquilenet.fr
Re: vt2-6 still not available with base system
Am 09.11.2014 um 20:04 schrieb Samuel Thibault: Michael Biebl, le Sun 09 Nov 2014 19:56:40 +0100, a écrit : The alternative would be, to bump dbus to priority standard, so it's installed by default (on new installations). It is already priority standard. That is not enough to make it part of the base system though. Sorry, I obviously meant priority important. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: vt2-6 still not available with base system
On 09/11/14 18:56, Michael Biebl wrote: Running for i in `seq 2 6` ; do systemctl enable getty@tty$i.service; done on a system without dbus, would statically enable a getty on vt2-6. So we could simply document this fact (in README.Debian, release notes etc). I'm very tempted to say systemd in Debian should just make these 5 symlinks to preserve traditional Debian behaviour, at least for jessie. It doesn't really even need to run systemctl, it can just use ln -s or whatever. People who are so desperately short of memory that 5 agetty instances are undesired can always disable them. If you want it to be clear that it's a Debian-specific thing that's pulling them in, maybe it would be better to add a new debian-gettys.target or debian-gettys.service that Wants them, and make it WantedBy an appropriate target? We can reconsider in a few months for jessie+1, at which point these will hopefully be clearer: * how many people switch to systemd and how many stick to sysvinit * whether kdbus is likely to be merged by the time the kernel for jessie+1 freezes, making dbus-daemon entirely unnecessary on systemd systems * whether we can get rid of init from Essential so chroots don't need a /sbin/init (yes I know chroots don't necessarily have Priority:important) The alternative would be, to bump dbus to priority [important], so it's installed by default (on new installations). I think Simon wasn't to keen on raising the prio of dbus further. I've CCed him for his input. I'm not delighted by the idea of dbus-daemon escalating from standard to important. I install it on my own headless machines, but I know a lot of sysadmins are more change-averse than me. Also, installations with sysvinit (or no init at all) really shouldn't need it, and we don't have a way to make it conditionally important depending on init system (other than the Recommends that systemd already has). A third idea would be to have a generator, which creates the getty@tty$i.service symlinks in /run/systemd/system/getty.target.wants Implementing that in shell, would only take a couple of lines. My instinct is that that just sounds like an unnecessarily complicated way to add 5 symlinks or a Wants that could equally well be there statically. A generator could be conditional on the absence of dbus.service, or some such, but then again so could a debian-gettys.service with ConditionPathExists=!/lib/systemd/system/dbus.service. S -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/545fd1f8.80...@debian.org
Stop offering /usr in the partition usage list?
Hello debian-boot, while trying out a daily jessie d-i snapshot, I noticed that the where-do-you-want-to-mount-this-partition menu offers /usr. Given current troubles with a split /usr and possible future directions, maybe it'd be a good idea to stop offering this? (Experts can still enter /usr manually...) Christian -- ,''`. Christian Hofstaedtler z...@debian.org : :' : Debian Developer `. `' 7D1A CFFA D9E0 806C 9C4C D392 5C13 D6DB 9305 2E03 `- signature.asc Description: Digital signature
Bug#768875: debian-installer: graphical install ignores (both newly created and already existing) EFI partition(s)
Package: debian-installer Version: 20141002 Severity: important Tags: d-i Dear Maintainer, I am installing Debian testing (Jessie) on a MacBook Pro 8,2. When using the graphical expert install, EFI partitions seem to be ignored when validating the partition structure. I have tried both with the already existant Mac EFI and an additional ad-hoc- created EFI partion. When I execute Finish partitioning and write changes to disk I get a No EFI partition was found. Workaround: use the text install (always in expert mode). Best, Leandro -- System Information: Debian Release: jessie/sid Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAAn03x4aR5_peV4SFOXF-14_QSant0iGNV2mP5HBw7=qcav...@mail.gmail.com
Bug#768876: busybox-static is statically linked against libc6, but doesn't have a Built-Using: field
Package: busybox Version: 1:1.22.0-9 Severity: serious Justification: Policy 7.8 busybox-static is statically linked against libc6. According to Debian Policy §7.8 such a package MUST list the glibc source package in the Built-Using: field. Note: While this is a serious policy violation and given Jessie is already frozen, it has been agreed with the release team that the bug does not need to be fixed for Jessie. That's why the jessie-ignore tag is added, this makes this bug non RC. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141109205014.9038.83032.report...@weber.rr44.fr
Processed: tagging 768876
Processing commands for cont...@bugs.debian.org: tags 768876 + jessie-ignore Bug #768876 [busybox] busybox-static is statically linked against libc6, but doesn't have a Built-Using: field Added tag(s) jessie-ignore. thanks Stopping processing here. Please contact me if you need assistance. -- 768876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768876 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: https://lists.debian.org/handler.s.c.141556691831571.transcr...@bugs.debian.org
Bug#745262: console-setup: Caps lock doesn't take effect on øæå (Danish characters)
No - I can confirm that the bug is gone. 2014-11-09 16:57 GMT+01:00 Samuel Thibault sthiba...@debian.org: Anton Zinoviev, le Sun 09 Nov 2014 17:29:53 +0200, a écrit : On Wed, Aug 13, 2014 at 12:47:26AM +0200, Samuel Thibault wrote: Anton Zinoviev, le Wed 06 Aug 2014 20:39:02 +0300, a écrit : On Sun, Apr 20, 2014 at 10:35:23PM +0200, Samuel Thibault wrote: Oops, indeed, it seems the version in Jessie does not properly defines the ctrll layer for upper cases like it used to in Wheezy. See ckbcomp dk: keycode 39 = +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute +U+00e6 +U+00c6 dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute dead_acute dead_doubleacute It uses only +U+00e6 +U+00c6, while it should use +U+00c6 +U+00e6 for ctrll layers. I am unable to reproduce this. What locale do you use? I've tested with LC_ALL=C, LC_ALL=da_DK.utf8 and LC_ALL=da_DK. Well, whatever the locale, LC_ALL=C for instance, I get only +U+00e6 +U+00c6, and never +U+00c6 +U+00e6. I've tried both console-setup 1.102 and 1.111. I just wanted to mention that I've never been able to reproduce this. I have tried this in clean install of jessie with Gnome, both i386 and amd64. I don't have the issue any more currently on my Jessie system. Andreas, do you still have the issue? Samuel
Bug#768897: debian-installer: manual partitioning with LVM destroys all non-target LVM+LUKS+GPT volumes
Package: debian-installer Version: (from Debian 7.6.0 amd64 DVD 1) Severity: critical Justification: causes serious data loss As with some other d-i reports, the Version is set from the ISO image, as I'm not sure how to get the d-i version proper from that. My current best test case for this: (blkid lines are split for readability.) 1. The starting conditions: I've pared them down to two small disks, tested in a QEMU+KVM virtual machine. Both have GPT partition tables, per [[STARTING-TABLES]] below. Take note of disk 2, partition 3, which is marked with an LVM type code (applied via setting 8e00 in gdisk) but in fact contains a LUKS volume which contains an LVM PV. (gdisk doesn't have an obvious type code for Linux LUKS volume, and a straw poll of another Linux sysadmin says they do the same thing I do and use the underlying type. Maybe Linux reserved would be more accurate?) host# losetup --show --find disk2 /dev/loop0 host# kpartx -a /dev/loop0 host# blkid /dev/mapper/loop0p3 /dev/mapper/loop0p3: UUID=67e3b0d0-986d-43d3-9618-f6f8895ebbb7 TYPE=crypto_LUKS PARTLABEL=Linux LVM PARTUUID=1eec58ea-5479-49f1-88cb-308dd583ff66 2. Boot the Debian 7.6.0 amd64 installer: host% /sbin/blkid /dev/cdrom /dev/cdrom: UUID=2014-07-12-14-23-02-00 LABEL=Debian 7.6.0 amd64 1 TYPE=iso9660 PTUUID=46bf9aa7 PTTYPE=dos host% qemu-system-x86_64 -enable-kvm \ -cdrom /dev/cdrom -boot d \ -hda disk1 -hda disk2 -m 4096 -monitor stdio 3. Choose all defaults (and meaningless usernames, etc.) up until the partitioning stage. Then choose Manual partitioning. At this point it will be apparent to the particularly alert viewer that both sda3 and sdb3 are shown with a K and an lvm marker. (I'm not sure what the K means; maybe it's meant to represent a flaming skull?) From the second console: virt# blkid /dev/sdb3 # (line split) /dev/sdb3: UUID=67e3b0d0-986d-43d3-9618-f6f8895ebbb7 TYPE=crypto_LUKS ... so blkid from the d-i environment at this stage at least recognizes that there is a typed volume on that block device (this seems to be true earlier on as well). 4a. Choose sda2, and set it to Ext4, mount point /boot, then Done to return to Partition disks. 4b. Choose sda3, and set it to physical volume for encryption, Erase data: no, then Done to return to Partition disks. 5. Choose Configure encrypted volumes. A dialog about which changes will be made to the disks appears. The main listings read: | The partition tables of the following devices are changed: | SCSI1 (0,0,0) (sda) | | The following partitions are going to be formatted: | partition #2 of SCSI1 (0,0,0) (sda) as ext4 Choose Yes to write changes to disks. 6. Choose Create encrypted volumes, then select /dev/sda3 only. Continue, then Finish. Enter an arbitrary passphrase. Some progress bars appear, then Partition disks again. 7. Choose sda3_crypt part 1, and set it to physical volume for LVM, then Done to return to Partition disks. 8. Choose Configure the Logical Volume Manager. The alert viewer will notice that there are more Free Physical Volumes than there should be. At this point sdb3 has _already_ been reinitialized as a new PV, destroying its LUKS header and rendering it unrecoverable except by restoring from backup: host# blkid /dev/mapper/loop0p3 # (line split) /dev/mapper/loop0p3: UUID=1jZyPo-mXqX-GuSt-L1KP-knSn-j6Yw-5yl2ct TYPE=LVM2_member PARTLABEL=Linux LVM PARTUUID=1eec58ea-5479-49f1-88cb-308dd583ff66 host# cryptsetup luksOpen /dev/mapper/loop0p3 DITest_pv Device /dev/mapper/loop0p3 is not a valid LUKS device. Note especially that none of the warning screens that normally appear to confirm which partitions will have their data destroyed refer to sdb3 at all, and this occurs regardless of whether I create any VGs incorporating sdb3 as a PV. Continuing with the installation in this vein, if I: - create a single VG using only sda3_crypt, + for which the selection dialog for PVs displays _all_ available block devices, not merely those marked for LVM use per se---so the idea that sdb3 is now a PV is not made obvious by that means (but this would be too late anyway) - then a single LV on it with an ext4 root partition then a warning appears about overwriting data on the VG and the LV, but makes no reference to the physical partitions. If I go for Configure the Logical Volume Manager _first_, there is some kind of warning about not being able to change the partition tables of the disks on which PVs will be placed later, which I didn't investigate further, but this doesn't appear in the above sequence. The original
Bug#768897: Test disk images uploaded
disk1_pristine, disk2_pristine, and the key file for the test LUKS volume on p3 of disk2 are now available at: http://dasyatidae.net/tmp/d-i-test-20141109.tar.xz (49 MiB) SHA-256: f35d2a8573998f6a82949cf8bb302b1e34c7fdc3f184545f8d682a6e19bb1059 Use tar -S or equivalent to unpack! The disk images are raw, 4 GiB sparse files. And please make a local copy of this file if you wish to keep it. The LUKS volume should contain an LVM PV in a single-PV VG, with one LV with an ext4 filesystem with one test file in it, though most of that is not directly relevant to the report. --- Drake Wilson -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/545ff86a.3080...@dasyatidae.net
Bug#768897: Rough data flow trace
It seems that (debugging with the assumption that latest git and the on-DVD version are Sufficiently Similar): 1. Flags for partitions are retrieved via libparted, which sets the lvm flag on any partitions that have that GPT type. 2. partman-lvm/init.d/lvm sets the lvm method on all partitions with the lvm flag, resulting in (3) from the test sequence. 3. partman-lvm/lib/lvm-base.sh:pv_list assumes all devices with the method lvm are PVs. 4. partman-lvm/choose_partition/lvm/do_option:do_initial_setup iterates over pv_list and does pv_create on everything in it immediately. 5. partman-lvm/lib/lvm-base.sh:pv_create tests for the presence of an active PV using the exit code of the pvs command, and anything that doesn't indicate one results in pvcreate -ff, resulting in (8) from the test sequence. Running pvcreate without -f interactively will detect the LUKS signature and offer an abort, as it happens. On the immediate front, it _may_ be that testing whether it's safe to create a new PV there would be better done via something like pvcreate --test --quiet -- $pv /dev/null /dev/null 21 (which e.g. exits 5 on finding a LUKS signature) rather than checking using ! pvs. Or, better yet, along the lines of crypttab(5)'s precheck=un_blkid. By itself, that would probably make the install fail without further reworking though. A better question would probably be why that flag-method propagation is done in manual partitioning mode in the first place; I assume that's used for something, but I don't know what, having not delved into this code before. --- Drake Wilson -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/546015d2.4060...@dasyatidae.net
Bug#768914: netcfg/wireless_wpa is type string, not type password
Package: netcfg Severity: minor I just installed wheezy over WPA and ran into #694068. While investigating that, I grepped for my PSK across /. I found it in /var/log/installer/cdebconf/questions.dat under netcfg/wireless_wpa. It is stored in cleartext; the file is only readable by root. In templates.dat (same dir), I see Name: netcfg/wireless_wpa Type: string Description: WPA/WPA2 passphrase [...] Since it's a PASSPHRASE, shouldn't it be Type: password? Normal users cannot read questions.dat, so I don't think this is an immediate problem. (FWIW hostapd's wpa_psk_file option lets each device have its own PSK, so when Mallet is sacked and his PSK is revoked, he can't simply spoof Alice's MAC and use his PSK to get in. I don't use EAP-TLS client certs because support for that is depressingly limited. This means my PSKs are more secret than your typical home network where there's one shared PSK that everyone knows.) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141110060725.7743.44054.reportbug@frey
Processing of console-setup_1.115_amd64.changes
console-setup_1.115_amd64.changes uploaded successfully to localhost along with the files: console-setup_1.115.dsc console-setup_1.115.tar.xz keyboard-configuration_1.115_all.deb console-setup_1.115_all.deb console-setup-mini_1.115_all.deb console-setup-linux_1.115_all.deb console-setup-freebsd_1.115_all.deb bdf2psf_1.115_all.deb console-setup-udeb_1.115_all.udeb console-setup-amiga-ekmap_1.115_all.udeb console-setup-ataritt-ekmap_1.115_all.udeb console-setup-macintoshold-ekmap_1.115_all.udeb console-setup-pc-ekmap_1.115_all.udeb console-setup-sun4-ekmap_1.115_all.udeb console-setup-sun5-ekmap_1.115_all.udeb console-setup-pc-ekbd_1.115_all.udeb console-setup-linux-fonts-udeb_1.115_all.udeb console-setup-freebsd-fonts-udeb_1.115_all.udeb console-setup-linux-charmaps-udeb_1.115_all.udeb console-setup-freebsd-charmaps-udeb_1.115_all.udeb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/e1xnikj-00062z...@franck.debian.org
Bug#762399: marked as done (console-setup: WARNING: Unknown X keysym permille)
Your message dated Mon, 10 Nov 2014 06:34:08 + with message-id e1xniyc-00084t...@franck.debian.org and subject line Bug#762399: fixed in console-setup 1.115 has caused the Debian Bug report #762399, regarding console-setup: WARNING: Unknown X keysym permille 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.) -- 762399: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: console-setup Version: 1.113 Severity: normal Setting up console-setup (1.113) ... WARNING: Unknown X keysym permille WARNING: Unknown X keysym permille WARNING: Unknown X keysym permille WARNING: Unknown X keysym permille WARNING: Unknown X keysym ezh WARNING: Unknown X keysym EZH WARNING: Unknown X keysym ezh WARNING: Unknown X keysym EZH WARNING: Unknown X keysym ezh WARNING: Unknown X keysym EZH WARNING: Unknown X keysym ezh WARNING: Unknown X keysym EZH Setting up libprotobuf9:i386 (2.6.0-3) ... Could this be caused by ckbcomp's built-in (X keysym - kernel keysym) table missing these? -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (1001, 'testing'), (1001, 'oldstable') Architecture: i386 (i686) Kernel: Linux 3.14-2-686-pae (SMP w/1 CPU core) Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-setup depends on: ii console-setup-linux 1.113 ii debconf 1.5.53 ii keyboard-configuration 1.113 ii xkb-data2.12-1 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.19-11 ii lsb-base 4.1+Debian13 Versions of packages keyboard-configuration depends on: ii debconf 1.5.53 ii initscripts 2.88dsf-53.4 ii liblocale-gettext-perl 1.05-8+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-1 ii keyboard-configuration 1.113 console-setup-linux suggests no packages. Versions of packages console-setup is related to: pn console-common none pn console-datanone pn console-tools none ii kbd 1.15.5-1 -- debconf information: * console-setup/model: Generic 105-key (Intl) PC * console-setup/unsupported_config_options: true keyboard-configuration/unsupported_options: true keyboard-configuration/unsupported_options: true keyboard-configuration/unsupported_options: true * console-setup/charmap47: UTF-8 keyboard-configuration/unsupported_config_layout: true keyboard-configuration/unsupported_config_layout: true keyboard-configuration/unsupported_config_layout: true * console-setup/store_defaults_in_debconf_db: true * console-setup/ask_detect: false * console-setup/ask_detect: false * console-setup/charmap: UTF-8 console-setup/use_system_font: console-setup/detect: console-setup/detect: debian-installer/console-setup/title: console-setup/guess_font: * console-setup/fontsize-text47: 8x16 * console-setup/compose: No compose key * keyboard-configuration/variantcode: * keyboard-configuration/variantcode: * keyboard-configuration/variantcode: keyboard-configuration/unsupported_layout: true keyboard-configuration/unsupported_layout: true keyboard-configuration/unsupported_layout: true * console-setup/ttys: /dev/tty[1-9] * console-setup/codesetcode: guess * console-setup/layout: Finland * console-setup/unsupported_config_layout: true * console-setup/fontsize: 8x16 * console-setup/fontsize-fb: 16 console-setup/dont_ask_layout: * keyboard-configuration/store_defaults_in_debconf_db: true * keyboard-configuration/store_defaults_in_debconf_db: true * keyboard-configuration/store_defaults_in_debconf_db: true * keyboard-configuration/model: Generic 105-key (Intl) PC * keyboard-configuration/model: Generic 105-key (Intl) PC * keyboard-configuration/model: Generic 105-key (Intl) PC * console-setup/codeset: Uni1 * keyboard-configuration/modelcode: pc105 * keyboard-configuration/modelcode: pc105 * keyboard-configuration/modelcode: pc105 * keyboard-configuration/toggle: No toggling * keyboard-configuration/toggle: No toggling * keyboard-configuration/toggle: No toggling * keyboard-configuration/layoutcode: fi * keyboard-configuration/layoutcode: fi * keyboard-configuration/layoutcode: fi * console-setup/modelcode: pc105 console-setup/framebuffer_only: * console-setup/unsupported_layout: true * console-setup/unsupported_options: true * keyboard-configuration/variant: Finnish * keyboard-configuration/variant: Finnish * keyboard-configuration/variant: Finnish *
console-setup_1.115_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 09 Nov 2014 21:58:45 +0200 Source: console-setup Binary: keyboard-configuration console-setup console-setup-mini console-setup-linux console-setup-freebsd bdf2psf console-setup-udeb console-setup-amiga-ekmap console-setup-ataritt-ekmap console-setup-macintoshold-ekmap console-setup-pc-ekmap console-setup-sun4-ekmap console-setup-sun5-ekmap console-setup-pc-ekbd console-setup-linux-fonts-udeb console-setup-freebsd-fonts-udeb console-setup-linux-charmaps-udeb console-setup-freebsd-charmaps-udeb Architecture: source all Version: 1.115 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team debian-boot@lists.debian.org Changed-By: Anton Zinoviev zinov...@debian.org Description: bdf2psf- font converter to generate console fonts from BDF source fonts console-setup - console font and keymap setup program console-setup-amiga-ekmap - encoded Linux keyboard layouts for Amiga keyboards (udeb) console-setup-ataritt-ekmap - encoded Linux keyboard layouts for Atari TT keyboards (udeb) console-setup-freebsd - FreeBSD specific part of console-setup console-setup-freebsd-charmaps-udeb - FreeBSD 8-bit charmaps for console-setup-udeb (udeb) console-setup-freebsd-fonts-udeb - FreeBSD console fonts for Debian Installer (udeb) console-setup-linux - Linux specific part of console-setup console-setup-linux-charmaps-udeb - Linux 8-bit charmaps for console-setup-udeb (udeb) console-setup-linux-fonts-udeb - Linux console fonts for Debian Installer (udeb) console-setup-macintoshold-ekmap - encoded Linux keyboard layouts for old-style Macintosh keyboards (udeb) console-setup-mini - console font and keymap setup program - reduced version for Linux console-setup-pc-ekbd - encoded FreeBSD keyboard layouts for PC keyboards (udeb) console-setup-pc-ekmap - encoded Linux keyboard layouts for PC keyboards (udeb) console-setup-sun4-ekmap - encoded Linux keyboard layouts for Sun4 keyboards (udeb) console-setup-sun5-ekmap - encoded Linux keyboard layouts for Sun5 keyboards (udeb) console-setup-udeb - Configure the keyboard (udeb) keyboard-configuration - system-wide keyboard preferences Closes: 762399 Changes: console-setup (1.115) unstable; urgency=medium . [ Anton Zinoviev ] * ckbcomp: define missing X keysyms. Thanks to Martin-Éric Racine, closes: #762399. Checksums-Sha1: 43883a5ab84ef86f8e1a49d7b3175e6773d02749 2619 console-setup_1.115.dsc 91a1cb453e779eec77baae6a6be406ef42227057 1879128 console-setup_1.115.tar.xz f5e42154461d504f586ea2a24591715f3fe3fa51 764596 keyboard-configuration_1.115_all.deb a7afa13562977abe83043f85a047119df77eab83 128130 console-setup_1.115_all.deb 9de926b21ce500ff3031f865184158f0c02d2d13 23184 console-setup-mini_1.115_all.deb a20cfbc6e67f0ce5e25020a48c9606396903f81e 984652 console-setup-linux_1.115_all.deb 1c23875668062dc97cd709609f71c92850eae4a0 99926 console-setup-freebsd_1.115_all.deb 033d0b6f5febbb9d535f414e6b232a75bf20d858 50128 bdf2psf_1.115_all.deb 0d3f7b0575c3c1f8d991254cdb1afb870dccab43 243168 console-setup-udeb_1.115_all.udeb 2a7aedfc1889425e7417a53e26d35a533197fb4d 39318 console-setup-amiga-ekmap_1.115_all.udeb 26b0dd314548c2a073f7882fb00653d78b9784bc 38910 console-setup-ataritt-ekmap_1.115_all.udeb 043a92e1ee3ae6854d884e0469e214c3e5c96fe4 39104 console-setup-macintoshold-ekmap_1.115_all.udeb 68c5a13ef6eafd1daf27da02cf9a19980f59cb2f 40950 console-setup-pc-ekmap_1.115_all.udeb c1e54457b3fc7135349100a3ee8408d8294bf99f 40922 console-setup-sun4-ekmap_1.115_all.udeb ce174f174a981d3dac0bd04fa41f772572fc7973 41184 console-setup-sun5-ekmap_1.115_all.udeb ec8cb0b25c8c185dcb26507670c0b2692c066841 28382 console-setup-pc-ekbd_1.115_all.udeb 7d18e3336af5273091de18d100a3fe92baa1b67d 18020 console-setup-linux-fonts-udeb_1.115_all.udeb 3a396d7182894762d173f8fd10702d0f0ca50468 11154 console-setup-freebsd-fonts-udeb_1.115_all.udeb 72480f0b86025c9f67cee49754019c8138bb376c 22758 console-setup-linux-charmaps-udeb_1.115_all.udeb 8a5dab0733ae23c37906f91c5f91865e9bab9c72 7148 console-setup-freebsd-charmaps-udeb_1.115_all.udeb Checksums-Sha256: 2bdc1a6d8fc97cf2c15d7e52ab85e4ac5c7f0ac81e48198b1c737987a96ffa54 2619 console-setup_1.115.dsc c609200e1b09adce919dbd33abadb35777377436cb106377c56a873a41e83e6e 1879128 console-setup_1.115.tar.xz 5cb635ff5525b3e905bfe578213a44b36f90596e5a33ba6d1bcdcc5845b8cd0b 764596 keyboard-configuration_1.115_all.deb 1f8da82e11a9d7cc3eca75f5b712160e14c50d966380cf827891e7dd59ea7a8f 128130 console-setup_1.115_all.deb a06f6c7b7e56a3cbd89db45642ab62036d7baa331eaad593242f772734343086 23184 console-setup-mini_1.115_all.deb 68f345f2009a7dad09761ca1488fb9c9a13718b356915a30241c8cb23e184af3 984652 console-setup-linux_1.115_all.deb 6203b2f8ab74286484fe48582d996d10cb5fd7d0fa4797a1ebabedd7c2f1fd9f 99926 console-setup-freebsd_1.115_all.deb c0a2e24d8a8fbbf7dabc0eda70a55286da8042029065f55299fcf6c63b34ea2b 50128
Processed: Re: [Pkg-sysvinit-devel] Bug#768657: sysvinit: Please provide xen virtual console in inittab
Processing control commands: reassign -1 debian-installer Bug #768657 [sysvinit-core] sysvinit: Please provide xen virtual console in inittab Bug reassigned from package 'sysvinit-core' to 'debian-installer'. No longer marked as found in versions sysvinit/2.88dsf-57. Ignoring request to alter fixed versions of bug #768657 to the same values previously set -- 768657: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768657 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: https://lists.debian.org/handler.s.b768657.1415603998673.transcr...@bugs.debian.org
Bug#768657: [Pkg-sysvinit-devel] Bug#768657: sysvinit: Please provide xen virtual console in inittab
On 11/10/2014 02:19 AM, Steve Langasek wrote: It's not for the sysvinit-core package to fix up the installer's handling of consoles, when sysvinit-core is not installed. Reassigning this to the debian-installer package. And how could it possibly be debian-installer's job to modify a file that is part of your package, when the package is not installed? I find your response incomprehensible. This bug is about making sure inittab, part of sysvinit-core, supports the console on the platform is is running on. Currently sysvinit-core is defective in not doing so. My comment about debian-installer was just so that you could see an example for code that handles this, and it explains why the maintainers of this package coincidentally haven't had to worry about this problem thus far. One way or another, to reproduce this problem all one needs to do is to install sysvinit-core on a xen VM, with debian-installer nowhere in sight. I also don't understand why #745260 was fixed (exactly the same problem) and this one somehow not. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54606bb0.5020...@gedalya.net
