tion Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
> Detect hard drives: [E]
>
>
> Comments/Problems:
>
> I connected an usb hard drive (with external power). That hard drive
> was not found. Also e.g. an USB mouse was not powered
On 11/01/2025 at 22:11, Andreas Barth wrote:
If there is anything that would help finding out, please say so. I'm
also happy to try different things if useful (and I'm also available
on IRC).
#debian-boot on OFTC is dedicated to the Debian installer.
Disclaimer: my experience with ARM is very
card:[O]
Configure network: [O]
Detect media: [O]
Load installer modules: [O]
Detect hard drives: [E]
Comments/Problems:
I connected an usb hard drive (with external power). That hard drive
was not found. Also e.g. an USB mouse was not powered within d-i.
After installati
Your message dated Wed, 20 Nov 2024 18:23:12 +
with message-id
and subject line Bug#1087366: Removed package(s) from unstable
has caused the Debian Bug report #319902,
regarding kbd-chooser contains old fork of code from kbd, which is hard to
update
to be marked as done.
This means that you
Your message dated Thu, 06 Jun 2024 20:50:52 +
with message-id
and subject line Bug#1036886: fixed in rootskel-gtk 12.0.3
has caused the Debian Bug report #1036886,
regarding Text input fields very hard to identify in high contrast / dark mode
to be marked as done.
This means that you claim
On Mon, 3 Jun 2024 at 02:22, Cyril Brulebois wrote:
>
> Hi,
>
> Luca Boccassi (2024-06-03):
> > Package: wnpp
> > Severity: wishlist
> > Owner: Luca Boccassi
> > X-Debbugs-Cc: debian-de...@lists.debian.org
> >
> > * Package name: systemd-boot-installer
> > Version : 0.1
> > Upstr
Hi,
Luca Boccassi (2024-06-03):
> Package: wnpp
> Severity: wishlist
> Owner: Luca Boccassi
> X-Debbugs-Cc: debian-de...@lists.debian.org
>
> * Package name: systemd-boot-installer
> Version : 0.1
> Upstream Author : Luca Boccassi
> * URL :
> https://salsa.debian.
On 27/02/2024 at 08:42, Philip Hands wrote:
Matthew Wilcox writes:
I want "use largest contiguous space and set up encrypted LVM".
That would let me reserve 200GB of my SSD as unencrypted free space,
which will improve the write endurance of my SSD.
Can one achieve this by telling LVM to all
Matthew Wilcox writes:
> Package: debian-installer
>
> The partitioner "guided partitioning" offers me:
>
> - use the largest continuous free space
> - use entire disk
> - use entire disk and set up LVM
> - use entire disk and set up encrypted LVM
>
> I want "use largest contiguous space and
On 26/02/2024 at 01:14, Matthew Wilcox wrote:
- create a logical volume in the free VG space
- blkdiscard the logical volume
Last time I checked, dm-crypt did not pass DISCARD requests through to
the underlying device because it's a security hazard.
AFAICS dm-crypt and cryptsetup have suppo
On Mon, Feb 26, 2024 at 12:34:50AM +0100, Pascal Hambourg wrote:
> Not if you do not write anything to them, or if you TRIM them.
You can stop explaining to me how TRIM works.
commit 0c659b82d11e
Author: Matthew Wilcox
Date: Thu Apr 2 10:37:25 2009 -0400
ata: Add TRIM infrastructure
> Yo
On 25/02/2024 at 23:55, Matthew Wilcox wrote:
I want "use largest contiguous space and set up encrypted LVM".
That would let me reserve 200GB of my SSD as unencrypted free space,
which will improve the write endurance of my SSD.
Alternatively, the installer allows to reserve free space in the
On Sun, Feb 25, 2024 at 11:42:37PM +0100, Pascal Hambourg wrote:
> On 25/02/2024 at 05:40, Matthew Wilcox wrote:
> >
> > The partitioner "guided partitioning" offers me:
> >
> > - use the largest continuous free space
> > - use entire disk
> > - use entire disk and set up LVM
> > - use en
On 25/02/2024 at 05:40, Matthew Wilcox wrote:
The partitioner "guided partitioning" offers me:
- use the largest continuous free space
- use entire disk
- use entire disk and set up LVM
- use entire disk and set up encrypted LVM
I want "use largest contiguous space and set up encrypted
Package: debian-installer
The partitioner "guided partitioning" offers me:
- use the largest continuous free space
- use entire disk
- use entire disk and set up LVM
- use entire disk and set up encrypted LVM
I want "use largest contiguous space and set up encrypted LVM".
That would let me r
Hello,
Holger Wansing, le lun. 23 oct. 2023 09:15:57 +0200, a ecrit:
> Samuel Thibault wrote (Mon, 23 Oct 2023 02:00:25
> +0200):
> > I had a hard time getting a border. The simplest might be to just have
> > a black background, as attached. Would that be fine enough? (we
Hi,
Samuel Thibault wrote (Mon, 23 Oct 2023 02:00:25 +0200):
> I had a hard time getting a border. The simplest might be to just have
> a black background, as attached. Would that be fine enough? (we don't
> actually lose any contrast since it's the same blue as before)
A
nput fields to have a border
>> with the same color as the text that would make them clearly
>> identifiable.
>
>I had a hard time getting a border. The simplest might be to just have
>a black background, as attached. Would that be fine enough? (we don't
>actually lo
On 25/06/2023 at 17:44, Ben Hutchings wrote:
On Fri, 2023-06-09 at 17:16 +0200, Anael Mobilia wrote:
Jun 9 14:50:43 kernel: [0.00] x86/fpu: x87 FPU will use FXSAVE
Jun 9 14:50:43 kernel: [0.00] signal: max sigframe size: 1440
Jun 9 14:50:43 kernel: [0.00] BIOS-provided
On Fri, 2023-06-09 at 17:16 +0200, Anael Mobilia wrote:
[...]
> During the launch of the partition (before the installer provide the
> choice on how did I want to partition manually, automatically, ...),
> OOM-killer is called, stopping the installation
>
> Syslog :
> Jun 9 14:50:43 syslogd start
Source: rootskel-gtk
Severity: normal
Tags: a11y
Dear Mantainer,
running the installer in graphical dark / high contrast mode, it’s very
hard to identify text input fields in the installer pages, making it
very difficult to see where things need to be input.
The default theme does a must better
Buster installer hangs at hard disk step with
arabic language
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
Might I suggest bug #990016 for the D-I urgency list; many of my server boards
have ASPEED drivers and I've been surprised how sometimes this bites me and
sometimes not.
Please consider fixing this before releasing the production installer for
Bullseye.
Thank you.
estion in re hard disk
configuration
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 h
Your message dated Fri, 21 Aug 2020 04:58:02 +0200
with message-id <20200821045802.07acb7c9ded347064600d...@mailbox.org>
and subject line Re: Mass-closing old installation-report bugs --- round 5
has caused the Debian Bug report #931587,
regarding installation-reports: Hard freezes before
Your message dated Sun, 2 Aug 2020 12:41:08 +0200
with message-id <20200802124108.56338fb4c14951ee89027...@mailbox.org>
and subject line Re: #868681 installation-reports: UEFI on HP z240 fails; needs
hard-coded EFI path
has caused the Debian Bug report #868681,
regarding installation-r
"David R. Hedges" wrote (17 Jul 2017 16:39:01):
> On 2017-07-17 11:50, Steve McIntyre wrote:
> > Could you try the (better) workaround and install to the
> > removable media path please?
> I moved EFI\debian\grubx64.efi to EFI\boot\bootx64.efi, removed the
> other directories, and yes, the sys
Your message dated Sat, 09 May 2020 21:33:30 +
with message-id
and subject line Bug#954718: fixed in grub-installer 1.170
has caused the Debian Bug report #954718,
regarding grub-installer: update templates for UEFI and other media than hard
disks
to be marked as done.
This means that you
Hi,
Steve McIntyre wrote:
> >
> >I have attached an updated patch, which might be considered.
>
> I think this is better, yes. :-) Taking into account Adrian's
> feedback, maybe s/primary drive/hard disk/ in most places?
No, with Justin as native speaker, we came to
On 3/26/20 2:05 PM, Steve McIntyre wrote:
> I think this is better, yes. :-) Taking into account Adrian's
> feedback, maybe s/primary drive/hard disk/ in most places?
>
> Thanks for this effort - it's definitely good to move away from the
> misleading "MBR" tex
need
>> >to include this well if you want to be comprehensive. And s390x
>> >supports GRUB as well.
>> >
>> >Do you want to include all these, too?
>>
>> ACK. Probably worth using more generic terminology if we can. Instead
>> of talking
an updated patch, which might be considered.
Well, my opinion is still that it's a very bad idea to get rid of the
term "hard disk". I assume more people understand the meaning of "hard
disk" but not the meaning of "primary drive".
In fact, I just asked my 62-year-o
t; >Do you want to include all these, too?
>
> ACK. Probably worth using more generic terminology if we can. Instead
> of talking about MBR or UEFI at all, maybe just aim for "primary
> drive" or similar?
>
> >> - hard disks are no longer the only/
On 3/23/20 5:43 PM, Holger Wansing wrote:
>> It's not always easy to tell reliably if you're installing to a
>> virtual device. It's still a "drive" as far as most people are
>> concerned, so I'd just stick with that.
>
> Just trying to improv
t; >Do you want to include all these, too?
>
> ACK. Probably worth using more generic terminology if we can. Instead
> of talking about MBR or UEFI at all, maybe just aim for "primary
> drive" or similar?
>
> >> - hard disks are no longer the only/
gy if we can. Instead
of talking about MBR or UEFI at all, maybe just aim for "primary
drive" or similar?
>> - hard disks are no longer the only/mainly used storage media (depending on
>> architecture); these days we are installing OS'es on SD cards or USB
&
eed
to include this well if you want to be comprehensive. And s390x
supports GRUB as well.
Do you want to include all these, too?
> - hard disks are no longer the only/mainly used storage media (depending on
> architecture); these days we are installing OS'es on SD cards or USB
&g
Package: grub-installer
Severity: wishlist
Tags: patch
grub-installer contains outdated template strings, which should be updated
in regard of:
- MBR is outdated -> UEFI came as a successor;
- hard disks are no longer the only/mainly used storage media (depending on
architecture); these d
John Paul Adrian Glaubitz writes:
> According to that logic you would have to replace the save icon in every
> desktop application because we're no longer using floppy disks.
Well.. I actually bought a 5 1/4" floppy drive a few weeks ago.
Had been thinking about maybe copying whatever documents
Hi,
John Paul Adrian Glaubitz wrote:
> Normally, you make changes because you have identified a problem
> from user reports. But this is basically backwards, you see the
> need for a change and you're now trying to find a justification
> for it.
Ok, so we will wait until users complain about tha
On Wed, 2020-03-18 at 16:03 +0100, John Paul Adrian Glaubitz wrote:
> On 3/18/20 3:36 PM, Ben Hutchings wrote:
> > > According to that logic you would have to replace the save icon in every
> > > desktop application because we're no longer using floppy disks.
> > [...]
> >
> > That has already hap
John Paul Adrian Glaubitz wrote:
> On 3/18/20 3:26 PM, Justin B Rye wrote:
>> Sure, and indeed I nearly mentioned "floppy" disk. But "hard disk"
>> isn't a case where the new thing has taken over the old meaning;
>> people don't generally say &
Ben Hutchings wrote:
> On Wed, 2020-03-18 at 10:11 +0100, John Paul Adrian Glaubitz wrote:
>> According to that logic you would have to replace the save icon in every
>> desktop application because we're no longer using floppy disks.
>
> That has already happened to many (most?) applications.
One
On 3/18/20 3:36 PM, Ben Hutchings wrote:
>> According to that logic you would have to replace the save icon in every
>> desktop application because we're no longer using floppy disks.
> [...]
>
> That has already happened to many (most?) applications.
I actually just verified that and both Micros
On 3/18/20 3:26 PM, Justin B Rye wrote:
> Sure, and indeed I nearly mentioned "floppy" disk. But "hard disk"
> isn't a case where the new thing has taken over the old meaning;
> people don't generally say "pass me the hard disk" when they mea
On Wed, 2020-03-18 at 10:11 +0100, John Paul Adrian Glaubitz wrote:
> On 3/18/20 9:58 AM, Holger Wansing wrote:
> > while investigating a grub installation failure, I came across the main menu
> > entry of grub-installer:
> > "Install the GRUB boot loader on a hard
John Paul Adrian Glaubitz:>
> On 3/18/20 11:43 AM, Justin B Rye wrote:
>>> The majority of all users is able to perform the cognitive process to
>>> that "hard disk" means "installation device" and "storage medium" here
>>> is v
On 3/18/20 11:43 AM, Justin B Rye wrote:
>> The majority of all users is able to perform the cognitive process to
>> that "hard disk" means "installation device" and "storage medium" here
>> is very confusing since that normally refers to a data d
On 3/18/20 11:07 AM, Holger Wansing wrote:
> Leaving it as is might however lead to the wrong assumption that
> grub can only be installed on a hard disk. Or with other words, grub - for
> some specific reason - does not work on SD cards (or USB thumb drives or ...).
"Leaving
John Paul Adrian Glaubitz wrote:
> On 3/18/20 9:58 AM, Holger Wansing wrote:
>> while investigating a grub installation failure, I came across the main menu
>> entry of grub-installer:
>> "Install the GRUB boot loader on a hard disk"
>>
>> This is
Hi,
John Paul Adrian Glaubitz wrote:
> On 3/18/20 9:58 AM, Holger Wansing wrote:
> > while investigating a grub installation failure, I came across the main menu
> > entry of grub-installer:
> > "Install the GRUB boot loader on a hard disk"
> >
> &g
On 3/18/20 9:58 AM, Holger Wansing wrote:
> while investigating a grub installation failure, I came across the main menu
> entry of grub-installer:
> "Install the GRUB boot loader on a hard disk"
>
> This is no longer optimal, since we have flash/SSD drives, SD car
Hi,
while investigating a grub installation failure, I came across the main menu
entry of grub-installer:
"Install the GRUB boot loader on a hard disk"
This is no longer optimal, since we have flash/SSD drives, SD cards etc. where
OS'es are installed on.
So this sh
Your message dated Mon, 23 Dec 2019 19:35:38 +
with message-id
and subject line Bug#930970: fixed in rootskel 1.132
has caused the Debian Bug report #930970,
regarding rootskel FTCBFS: hard codes the build architecture compiler
to be marked as done.
This means that you claim that the problem
Version: 1.103
Guido Günther (13 Aug 2015):
> On Wed, Apr 01, 2015 at 07:54:52PM +0200, Cyril Brulebois wrote:
> > Hi,
> >
> > and sorry for the lag.
> >
> > Sam McLeod (2015-03-07):
> > > Thanks Cyril, I did indeed miss that, that's great - I'll test it today.
> > >
> > > It looks like the
ate-initramfs without warnings.
(10) I rebooted and was able to log in to Gnome without problems.
I have since reverted Gnome to use Xorg instead of Wayland (Synergy
does not work with Wayland) but the freezes have not recurred.
* What was the outcome of this action?
Consis
Processing control commands:
> tags -1 + pending
Bug #930970 [src:rootskel] rootskel FTCBFS: hard codes the build architecture
compiler
Added tag(s) pending.
--
930970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930970
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Control: tags -1 + pending
Hello,
Helmut Grohne, le dim. 23 juin 2019 20:04:56 +0200, a ecrit:
> rootskel fails to cross build from source, because some Makefile hard
> codes plain gcc. After making it substitutable, rootskel cross builds
> successfully. Please consider applying the
Source: rootskel
Version: 1.131
Tags: patch
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
rootskel fails to cross build from source, because some Makefile hard
codes plain gcc. After making it substitutable, rootskel cross builds
successfully. Please consider applying the attached patch
Processing control commands:
> tags -1 + buster-ignore
Bug #929877 [installation-reports] installation-reports: Buster installer hangs
at hard disk step with arabic language
Added tag(s) buster-ignore.
--
929877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929877
Debian Bug Track
Control: tags -1 + buster-ignore
Hello,
Holger Wansing, le jeu. 20 juin 2019 10:31:39 +0200, a ecrit:
> ButterflyOfFire wrote:
> > I think it is okay for those diacritics.
>
> I have uploaded that fix now.
Thanks!
> Leaving this bug open as a reminder for the "real" problem inside of gtk (?)
Hi,
ButterflyOfFire wrote:
> Hi,
> I think it is okay for those diacritics.
> Regards,
I have uploaded that fix now.
Leaving this bug open as a reminder for the "real" problem inside of gtk (?)
Holger
> ‐‐‐ Original Message ‐‐‐
> Le mardi 18 juin 2019 22:26, Holger Wansing a écrit
Hi,
I think it is okay for those diacritics.
Regards,
‐‐‐ Original Message ‐‐‐
Le mardi 18 juin 2019 22:26, Holger Wansing a écrit :
> Hi,
>
> Samuel Thibault sthiba...@debian.org wrote:
>
> > Hello,
> > Holger Wansing, le mar. 04 juin 2019 20:59:12 +, a ecrit:
> >
> > > Am Sonntag,
Hi,
Samuel Thibault wrote:
> Hello,
>
> Holger Wansing, le mar. 04 juin 2019 20:59:12 +, a ecrit:
> > Am Sonntag, 2. Juni 2019 schrieb Holger Wansing:
> > > Am Sonntag, 2. Juni 2019 schrieb Samuel Thibault:
> > > > ButterflyOfFire, le dim. 02 juin 2019 15:43:41 +, a ecrit:
> > > > > >> "
Hello,
Holger Wansing, le mar. 04 juin 2019 20:59:12 +, a ecrit:
> Am Sonntag, 2. Juni 2019 schrieb Holger Wansing:
> > Am Sonntag, 2. Juni 2019 schrieb Samuel Thibault:
> > > ButterflyOfFire, le dim. 02 juin 2019 15:43:41 +, a ecrit:
> > > > >> "لاحقاً"
> > > >
> > > > This word means "l
ButterflyOfFire, le dim. 02 juin 2019 15:43:41 +, a ecrit:
> >> "لاحقاً"
>
> This word means "later" and can be replaced by "لاحقا".
That avoids the issue here indeed. I however see it used in various
places, notably in the grub installer:
msgid ""
"Warning: If the installer failed to detect
Hi,
>> "لاحقاً"
This word means "later" and can be replaced by "لاحقا".
Samuel Thibault, le dim. 02 juin 2019 17:07:04 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 16:47:49 +0200, a ecrit:
> > But it's translated along the two other pieces "The installer can guide
> > you..." and "If you choose guided..." so the issue might be in those.
>
> It's when I add
Samuel Thibault, le dim. 02 juin 2019 16:47:49 +0200, a ecrit:
> But it's translated along the two other pieces "The installer can guide
> you..." and "If you choose guided..." so the issue might be in those.
It's when I add this piece that gtk starts choking. Any idea?
"الفرصة لاحقاً لرؤية النتا
Samuel Thibault, le dim. 02 juin 2019 16:44:45 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 16:33:03 +0200, a ecrit:
> > Samuel Thibault, le dim. 02 juin 2019 16:06:50 +0200, a ecrit:
> > > Samuel Thibault, le dim. 02 juin 2019 15:56:31 +0200, a ecrit:
> > > > Samuel Thibault, le dim. 02
Samuel Thibault, le dim. 02 juin 2019 16:33:03 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 16:06:50 +0200, a ecrit:
> > Samuel Thibault, le dim. 02 juin 2019 15:56:31 +0200, a ecrit:
> > > Samuel Thibault, le dim. 02 juin 2019 15:47:28 +0200, a ecrit:
> > > > Holger Wansing, le dim. 02
Samuel Thibault, le dim. 02 juin 2019 16:06:50 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 15:56:31 +0200, a ecrit:
> > Samuel Thibault, le dim. 02 juin 2019 15:47:28 +0200, a ecrit:
> > > Holger Wansing, le dim. 02 juin 2019 15:00:09 +0200, a ecrit:
> > > > So, that would come down to
Samuel Thibault, le dim. 02 juin 2019 15:56:31 +0200, a ecrit:
> Samuel Thibault, le dim. 02 juin 2019 15:47:28 +0200, a ecrit:
> > Holger Wansing, le dim. 02 juin 2019 15:00:09 +0200, a ecrit:
> > > So, that would come down to this two commits
> > > (if it's a matter of arabic translations):
> > >
Samuel Thibault, le dim. 02 juin 2019 15:47:28 +0200, a ecrit:
> Holger Wansing, le dim. 02 juin 2019 15:00:09 +0200, a ecrit:
> > So, that would come down to this two commits
> > (if it's a matter of arabic translations):
> > https://salsa.debian.org/installer-team/d-i/commit/1e16f41d79578a47a370c
Holger Wansing, le dim. 02 juin 2019 15:00:09 +0200, a ecrit:
> So, that would come down to this two commits
> (if it's a matter of arabic translations):
> https://salsa.debian.org/installer-team/d-i/commit/1e16f41d79578a47a370c7a47ec49abdcfc7fb52
> https://salsa.debian.org/installer-team/d-i/commi
ButterflyOfFire, le dim. 02 juin 2019 12:12:04 +, a ecrit:
> Tested right now on my laptop, I cannot reproduce the bug. It seems working.
>
> Tested with :
> kvm -cdrom /var/tmp/d-i/debian-buster-DI-rc1-amd64-netinst.iso -drive
> file=blip -m 1G
Hum :/
I tried to rebuild partman-base withou
While ButterflyOfFire reported to be unable to reproduce this, I can indeed
reproduce this with qemu here.
Looking more closely, that bug is there for me with the rc1 installer, however
not with the alpha5 one.
So, that would come down to this two commits
(if it's a matter of arabic translations)
Hi,
Tested right now on my laptop, I cannot reproduce the bug. It seems working.
Tested with :
kvm -cdrom /var/tmp/d-i/debian-buster-DI-rc1-amd64-netinst.iso -drive file=blip
-m 1G
Salutations,
on that I tried in Persian and didn't have the issue,
so that confirms that there is probably something in the Arabic
translation which triggers a bug in gtk.
> While doing some tests, I noticed that when running the installer in
> arabic language, the hard disk detection step hangs. To
that might disturb gtk).
While doing some tests, I noticed that when running the installer in
arabic language, the hard disk detection step hangs. To reproduce:
- dd < /dev/zero > blip bs=1M count=1 seek=1
- kvm -cdrom /var/tmp/d-i/debian-buster-DI-rc1-amd64-netinst.iso -drive
file=b
Your message dated Sun, 03 Jun 2018 21:05:19 +
with message-id
and subject line Bug#344693: fixed in installation-guide 20180603
has caused the Debian Bug report #344693,
regarding installation-guide: paragraph which is hard to transalte with PO file
& poxml
to be marked as done.
This m
; not result in a bootable system. Eventually I found a link[1] instucting me to
> replicate the Debian EFI boot program into EFI/Microsoft/boot/bootmgfw.efi,
> which was successful.
>* What was the outcome of this action?
> After the normal install, the system would not boot into Debian.
tcome of this action?
>After the normal install, the system would not boot into Debian. After
>applying a workaround for a hard-coded EFI path, the system booted.
> * What outcome did you expect instead?
>I expected the system to boot successfully into Debian after running the
>installe
ink[1] instucting me to
replicate the Debian EFI boot program into EFI/Microsoft/boot/bootmgfw.efi,
which was successful.
* What was the outcome of this action?
After the normal install, the system would not boot into Debian. After
applying a workaround for a hard-coded EFI path, the system boote
Processing control commands:
> tags -1 + pending
Bug #344693 [installation-guide] installation-guide: paragraph which is hard to
transalte with PO file & poxml
Added tag(s) pending.
--
344693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=344693
Debian Bug Tracking System
Con
Control: tags -1 + pending
Changwoo Ryu wrote:
> Package: installation-guide
> Severity: normal
>
> While I'm translating installation manual via PO file, I found following
> behavior of xmlpo. in manual/en/welcome/doc-organization.xml:
>
> describes booting into the
> installation system.
On Wed, Jun 28, 2017 at 12:34 AM, Narcis Garcia
wrote:
> When user selects to (yes) install boot manager, the wizard asks where
> to do the grub-install.
> Currently, default option in the dialog is to introduce manually the
> target path. I propose to change default option by the already detecte
When user selects to (yes) install boot manager, the wizard asks where
to do the grub-install.
Currently, default option in the dialog is to introduce manually the
target path. I propose to change default option by the already detected
path.
Geert Stappers (2017-06-27):
> On Tue, Jun 27, 2017 at 10:06:31AM +0200, Narcis Garcia wrote:
> >
> > At final stage of interactive installation, the suggested target for
> > boot manager should be (the only when it's only one) the hard disk drive
> > instead of m
On Tue, Jun 27, 2017 at 10:06:31AM +0200, Narcis Garcia wrote:
>
> At final stage of interactive installation, the suggested target for
> boot manager should be (the only when it's only one) the hard disk drive
> instead of manual introduction.
I don't understand the abo
Package: debian-installer
Version: 20170615
Severity: minor
Tags: d-i
At final stage of interactive installation, the suggested target for
boot manager should be (the only when it's only one) the hard disk drive
instead of manual introduction.
This will make the decision easier to unexperi
On 2016-12-13, peter green wrote:
> On 13/12/16 21:42, peter green wrote:
>> I would guess at this point either a race condition or a power glitch
>> (maybe powering the HDD off one of the USB ports wasn't such a good
>> idea).
>>
> OK, I found that adding ahci-imx.hotplug=1 to the kernel comman
Your message dated Mon, 27 Feb 2017 21:34:36 +0200
with message-id <20170227193436.lt6jbbovu6fpucbm@localhost>
and subject line Closing squeeze-only bugs
has caused the Debian Bug report #645757,
regarding misdetects Dell RAC as hard disk
to be marked as done.
This means that you claim th
Your message dated Sun, 13 Nov 2016 17:56:38 -0800
with message-id <20161114015638.oqpfxshaaoljk...@tomate.cristau.org>
and subject line Re: Bug#614029: pbuilder: Hard to avoid debootstrap failure,
Release signed by unknown key (key id AED4B06F473041FA)
has caused the Debian Bug report #
Your message dated Thu, 7 Jan 2016 21:01:39 -0800
with message-id <20160108050139.ga19...@jirafa.cyrius.com>
and subject line /usr no longer created
has caused the Debian Bug report #640377,
regarding debian-installer: /usr partition is too small, even on hugh hard disk
to be marked as done.
Hi,
On Wed, Apr 01, 2015 at 07:54:52PM +0200, Cyril Brulebois wrote:
> Hi,
>
> and sorry for the lag.
>
> Sam McLeod (2015-03-07):
> > Thanks Cyril, I did indeed miss that, that's great - I'll test it today.
> >
> > It looks like the example pressed hasn't been updated to include this
> > featu
Hi,
and sorry for the lag.
Sam McLeod (2015-03-07):
> Thanks Cyril, I did indeed miss that, that's great - I'll test it today.
>
> It looks like the example pressed hasn't been updated to include this
> feature: https://www.debian.org/releases/jessie/example-preseed.txt
This seems to be fixed
Hi Sam,
On Sat, Mar 07, 2015 at 09:02:17AM +1100, Sam McLeod wrote:
> Thanks Cyril, I did indeed miss that, that's great - I'll test it today.
>
> It looks like the example pressed hasn't been updated to include this
> feature: https://www.debian.org/releases/jessie/example-preseed.txt
This seem
Confirmed working with Jessie -
https://github.com/sammcj/packer-qemu-debian-jessie/commit/12a6dae01f328787dd89621d0bddc34458ac038e
Build log -
https://raw.githubusercontent.com/sammcj/packer-qemu-debian-jessie/master/build_output.log
Thanks again Cyril.
Thanks Cyril, I did indeed miss that, that's great - I'll test it today.
It looks like the example pressed hasn't been updated to include this
feature: https://www.debian.org/releases/jessie/example-preseed.txt
--
Sam McLeod
@s_mcleod[https://twitter.com/s_mcleod]
--
To UNSUBSCRIBE, email to
1 - 100 of 558 matches
Mail list logo
