date:20140303

Bug#734690: Language-chooser: C is not a language

2014-03-03 Thread martin f krafft

also sprach Cyril Brulebois k...@debian.org [2014-03-02 23:18 +0100]:
 Err, please clarify what “that was not the case, it just said C”
 means. I'm attaching a screenshot of the current state. (And
 Christian mentioned that was the case, so it's not clear to me
 what you're trying to say.)

I am not using GTK, but dialog. Here's the screenshot:

┌───┤ [!!] Select a language ├┐
│ │
│ Choose the language to be used for the installation process. The│
│ selected language will also be the default language for the installed   │
│ system. │
│ │
│ Language:   │
│ │
│   C │
│   English   │
│ │
│ Go Back   │
│ │
└─┘

  Tab moves; Space selects; Enter activates buttons

Sure, English is preselected and most people won't expend a second
thought, but C is not a language, and I don't think it should appear
in the list of choices.

-- 
 .''`.   martin f. krafft madduck@d.o  Related projects:
: :'  :  proud Debian developer   http://debiansystem.info
`. `'`   http://people.debian.org/~madduckhttp://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems
 
if a man treats life artistically, his brain is his heart.
-- oscar wilde


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#740271: d-i fails to purge LVM despite preseeding

2014-03-03 Thread Dimitri John Ledkov

On 2 March 2014 22:29, Cyril Brulebois k...@debian.org wrote:
martin f krafft madd...@debian.org (2014-02-27):
Package: debian-installer
Version: 20130613+deb7u1+b2
Severity: normal

Despite

d-i partman-auto/purge_lvm_from_device boolean true
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 fails to install a machine when libvirt passes it a storage
volume that has previously been used as PV by another host.

What happens (in my case) is that partman creates a new GPT, but
often that will be exactly the same as the one used by the previous
host using the volume. Therefore, /dev/vda3 will be a valid LVM PV,
meaning that LVM will find the previous VG.

Now, depending on whether the hostname is (a) the same, or (b)
different, d-i will fail to install claiming

(a) a VG with the same name is already present;
(b) the PV is already in use by another VG.

Logs would be helpful.

Not necessary, as it's easy to reproduce and a known bug (i've tried
and fixed couple symptoms but not all).
Indeed just use an lvm-preseed, twice in a row, and delete partition
table between the two runs.
Furthermore, those that install Virtual Machines, with hard-drives
provisioned by LVM volumes on the host, may find shadow effects
where deleted freshly created lvm-volume for the repeat install
still has left-over guest lvm metadata from previous incarnations.

wiping / zeroing out the drive before installation would be slow, but
would fix this...

--
Regards,

Dimitri.

--
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/CANBHLUiCt2LygtJy0KcyVr=zn8vh80nq7mfi+74ppaeppy6...@mail.gmail.com

38 matches

Mail list logo