Bug#720439: marked as done (console-setup: /etc/default/console-setup values overwritten on upgrade)
Your message dated Thu, 17 Oct 2013 12:46:17 +0300 with message-id 20131017094617.ga3...@logic.fmi.uni-sofia.bg and subject line Re: Bug#720439: console-setup: /etc/default/console-setup values overwritten on upgrade has caused the Debian Bug report #720439, regarding console-setup: /etc/default/console-setup values overwritten on upgrade 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.) -- 720439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720439 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: console-setup Version: 1.95 Severity: normal Dear Maintainer, A few days ago an update to console-setup arrived in Sid. I have chosen not to use the default fonts on my consoles and have set FONTFACE and FONTSIZE to empty strings only to have them replaced by other values. The result is a poor quality font on my hardware and I once again must edit console-setup and reboot for my chosen settings to take effect. The package should either not touch locally applied settings, where I presume /etc/default are to be set, or prompt the administrator to approve the changes (if the package does so but is not prompting me, a gentle reminder on how to enable such notifications will be welcome). Thanks. - Nate -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages console-setup depends on: ii console-setup-linux 1.95 ii debconf 1.5.50 ii keyboard-configuration 1.95 ii xkb-data2.5.1-3 console-setup recommends no packages. Versions of packages console-setup suggests: ii locales 2.17-92 ii lsb-base 4.1+Debian12 Versions of packages keyboard-configuration depends on: ii debconf 1.5.50 ii initscripts 2.88dsf-43 ii liblocale-gettext-perl 1.05-7+b1 Versions of packages console-setup-linux depends on: ii kbd 1.15.5-1 ii keyboard-configuration 1.95 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/codeset47: # Latin1 and Latin5 - western Europe and Turkic languages * keyboard-configuration/modelcode: pc105 keyboard-configuration/unsupported_config_options: true console-setup/fontface47: Fixed keyboard-configuration/unsupported_config_layout: true * keyboard-configuration/toggle: No toggling console-setup/fontsize-text47: 8x16 * keyboard-configuration/compose: No compose key * keyboard-configuration/layout: * keyboard-configuration/xkb-keymap: us * keyboard-configuration/variant: English (US) debian-installer/console-setup-udeb/title: * keyboard-configuration/switch: No temporary switch console-setup/charmap47: UTF-8 keyboard-configuration/unsupported_options: true * keyboard-configuration/altgr: The default for the keyboard layout console-setup/framebuffer_only: keyboard-configuration/ctrl_alt_bksp: false console-setup/codesetcode: Lat15 keyboard-configuration/unsupported_layout: true console-setup/guess_font: * keyboard-configuration/variantcode: * keyboard-configuration/model: Generic 105-key (Intl) PC * keyboard-configuration/layoutcode: us console-setup/store_defaults_in_debconf_db: true console-setup/fontsize-fb47: 8x16 * keyboard-configuration/other: * keyboard-configuration/store_defaults_in_debconf_db: true * keyboard-configuration/optionscode: console-setup/use_system_font: console-setup/fontsize: 8x16 ---End Message--- ---BeginMessage--- On Tue, Oct 15, 2013 at 09:02:11AM -0500, Nate Bargmann wrote: * On 2013 22 Aug 06:37 -0500, Anton Zinoviev wrote: Thank you for your bug report. Unfortunately we need more information in order to tell what exactly is the problem. At this time I have no information to provide as I have seen several updates to this package and my local modifications to /etc/default/console-setup have been retained through each upgrade on both an i386 and amd64 installations. Perhaps this was something unrelated, but I see no reason to keep this report open. Thank you for taking your time to write this. For now I am closing this bug report. If the problem reappears, feel free to reopen it or to submit a new bug report. Anton Zinoviev---End Message---
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Hi
I have a very similar problem, adding it here as it seems to have the same
origin. As mentioned by Petter, 1.86 introduced the follwoing change:
grub-installer (1.86) unstable; urgency=low
[ Vincent McIntyre ]
* Support menu selection of GRUB boot disk. Closes: #706112
-- Cyril Brulebois k...@debian.org Mon, 29 Apr 2013 13:53:27 +0200
I used to have a small preseed file and a virt-install invocation
like, described by Guido here, doing a net install:
http://honk.sigxcpu.org/con/Preseeding_Debian_virtual_machines_with_virt_install.html
virt-install --connect=qemu:///system \
--location=http://ftp.us.debian.org/debian/dists/unstable/main/installer\-amd64
\
--initrd-inject=${HOME}/virt/d-i/preseed.cfg \
--extra-args=auto keymap=us hostname=${NAME}
netcfg/get_ipaddress=${IP} suite=${SUITE} -- console=tty0
console=ttyS0,115200n8 \
--name $NAME \
--ram=$RAM \
--disk=pool=default,size=${DISKSIZE},format=qcow2,bus=virtio,cache=writeback
beeing able to quickly do tests in newly created vms, the preeseed.cfg
look like:
cut-cut-cut-cut-cut-cut-
d-i debian-installer/language string en
d-i debian-installer/country string US
d-i debian-installer/locale string en_US.UTF-8
d-i keymapselect us
d-i netcfg/choose_interface select auto
d-i netcfg/disable_autoconfig boolean true
d-i netcfg/get_netmask string 255.255.255.0
d-i netcfg/get_gateway string 192.168.122.1
d-i netcfg/get_domain string unassigned-domain
d-i netcfg/get_nameservers string 192.168.122.1
d-i netcfg/confirm_static boolean true
d-i mirror/countrystring manual
d-i mirror/http/hostname string cdn.debian.net
d-i mirror/http/directory string /debian
d-i mirror/http/proxy string
d-i passwd/make-user boolean false
d-i passwd/root-password password r00tme
d-i passwd/root-password-again password r00tme
d-i time/zone string US/Eastern
d-i clock-setup/utc boolean true
d-i clock-setup/ntp boolean true
d-i partman-auto/method string regular
#d-i partman-auto/method string lvm
d-i partman-lvm/device_remove_lvm boolean true
d-i partman-lvm/confirm boolean true
d-i partman-lvm/confirm_nooverwrite boolean true
d-i partman-auto/choose_recipe select atomic
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true
tasksel tasksel/first multiselect
d-i pkgsel/include string openssh-server
d-i pkgsel/upgrade select full-upgrade
popularity-contest popularity-contest/participate boolean false
d-i grub-installer/only_debian boolean true
d-i grub-installer/with_other_os boolean true
d-i finish-install/reboot_in_progress note
cut-cut-cut-cut-cut-cut-
It happens with both
d-i partman-auto/method string lvm
or
d-i partman-auto/method string regular
The installer stops at the new question: [!] Install the GRUB boot
loader on a hard disk.
Interestingly it stoppend only to work for me some days ago, IIRC it
was one of the days after the wheezy point release (some installer
components where updated then, IIRC). So I don't know (yet) if one
other part of the installer updated is involved causing this.
Regards,
Salvatore
--
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/20131017121754.GA648@eldamar.local
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Petter Reinholdtsen p...@hungry.com (2013-06-20): Package: grub-installer Version: 1.86 Severity: important User: debian-...@lists.debian.org Usertags: debian-edu We discovered this in Debian Edu based on testing using d-i udebs from unstable. See URL: http://jenkins.debian.net/view/edu/job/g-i-installation_debian-edu_jessie_standalone/ for a automatic test of such installation. The change introduced in version 1.86 added a new question in Debian Installer, causing the installation to hang at the end asking where to install grub. This used to work automatically, but now require people to fill in a value, and [enter] do not work. Not in every case, that's why the question was added in the first place! I haven't looked whether one can preseed it like other questions. If it isn't possible, that should be fixed. (Why you're using unstable udebs for a wheezy-based debian-edu isn't obvious to me, by the way.) Mraw, KiBi. signature.asc Description: Digital signature
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
[Cyril Brulebois] Not in every case, that's why the question was added in the first place! How often was the old default wrong? If it was rare, perhaps the question should only show up in expert installs (ie use priority low)? (Why you're using unstable udebs for a wheezy-based debian-edu isn't obvious to me, by the way.) I was tested using Jessie/testing when I discovered this. I did not experience it with Wheezy when I tested it a while back. -- Happy hacking Petter Reinholdtsen -- 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/20131017124433.gr6...@ulrik.uio.no
Bug#712907: grub-installer: No longer installs automatically on a normal machine with one hard drive
Petter Reinholdtsen p...@hungry.com (2013-10-17): [Cyril Brulebois] Not in every case, that's why the question was added in the first place! How often was the old default wrong? If it was rare, perhaps the question should only show up in expert installs (ie use priority low)? More or less everytime the install medium was a USB stick. Mraw, KiBi. signature.asc Description: Digital signature
Bug#726538: partman-md: Should rescan for encrypted volumes on top of raid after assembling it
reassign 726538 rescue-mode retitle 726538 rescue-mode: Should scan for encrypted volumes on top of raid after assembling it found726538 rescue-mode/1.41 forcemerge 484263 726538 thanks On Wed, Oct 16, 2013 at 04:41:08PM +0200, Agustin Martin wrote: Package: partman-md Version: 67 Severity: normal Hi, maintainers, Want to share a minor inconsistency when using crypto on top of RAID, mostly related to rescue mode. First, what works and should be expected, a normal crypto volume, no RAID: * Rescue mode * After selecting time zone d-i notices there is an encrypted volume I am prompted to enter a passphrase for it if I want to have it available for rescue operations. That is the expected behavior. However things work differently when the encrypted volume is on top of a RAID (RAID1 in this case). * Rescue mode * Get the Device to use as root file system dialog, known partitions shown, no RAID is still assembled and of course nothing inside it is shown, just plain /dev/sd* stuff. * I choose Assemble RAID array, tick Automatic and proceed. * However, although a crypto volume is on top of that RAID, that seems not detected and I am not prompted for a passphrase to enable it for rescue. Of course I can open a shell, enable luks volume and the lvm logical volumes it contains, go back and continue, now with all really available choices including those inside the crypto volume. I'd expect the same check that is automaticaly done when the encrypted volume is not on top of a RAID be run right after assembling the RAID so the contents of the encrypted volume (single partion or lvm stuff) become available for the rescue session in a simpler way if the passphrase is provided. Some extra details I forgot to add. In the second case both components of the RAID are detected separately as encrypted volumes and I am asked for their (common) passphrase. If I provide it, volume contents are properly scanned (not sure which lvm stuff is shown, it is replicated in both devices, but only one is shown), but since the RAID is not assembled I'd rather not use them separately. Did not try to mount it. It is the encrypted volume on top of RAID using both devices what is not detected as crypto and so no passphrase is asked for it and not further processed. Anyway, just noticed that this has already been reported as #484263 against rescue-mode. Thus reassigning and merging, sorry for the noise. Regards, -- Agustin -- 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/20131017134246.ga6...@agmartin.aq.upm.es
Processed: Re: Bug#726538: partman-md: Should rescan for encrypted volumes on top of raid after assembling it
Processing commands for cont...@bugs.debian.org: reassign 726538 rescue-mode Bug #726538 [partman-md] partman-md: Should rescan for encrypted volumes on top of raid after assembling it Bug reassigned from package 'partman-md' to 'rescue-mode'. No longer marked as found in versions partman-md/67. Ignoring request to alter fixed versions of bug #726538 to the same values previously set retitle 726538 rescue-mode: Should scan for encrypted volumes on top of raid after assembling it Bug #726538 [rescue-mode] partman-md: Should rescan for encrypted volumes on top of raid after assembling it Changed Bug title to 'rescue-mode: Should scan for encrypted volumes on top of raid after assembling it' from 'partman-md: Should rescan for encrypted volumes on top of raid after assembling it' found726538 rescue-mode/1.41 Bug #726538 [rescue-mode] rescue-mode: Should scan for encrypted volumes on top of raid after assembling it The source rescue-mode and version 1.41 do not appear to match any binary packages Marked as found in versions rescue-mode/1.41. forcemerge 484263 726538 Bug #484263 [rescue-mode] rescue-mode: Does not support RAID+LUKS setups Bug #484263 [rescue-mode] rescue-mode: Does not support RAID+LUKS setups The source rescue-mode and version 1.41 do not appear to match any binary packages Marked as found in versions rescue-mode/1.41. Bug #726538 [rescue-mode] rescue-mode: Should scan for encrypted volumes on top of raid after assembling it Severity set to 'minor' from 'normal' The source rescue-mode and version 1.41 do not appear to match any binary packages Marked as found in versions rescue/1.15. Merged 484263 726538 thanks Stopping processing here. Please contact me if you need assistance. -- 484263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484263 726538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726538 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.13820186256921.transcr...@bugs.debian.org
