Sorry I forgot to include how I started QEMU:
#!/bin/sh
ARCH=arm64
IMAGE=/var/tmp/qemu-disk-${ARCH}.qcow2
CDROM=/var/tmp/debian-bullseye-DI-alpha3-${ARCH}-netinst.iso
rm -f $IMAGE
qemu-img create -f qcow2 -o compat=1.1 -o lazy_refcounts=on -o
preallocation=off $IMAGE 20G
cd /var/tmp
cp /usr/shar
Package: debian-installer
Version: 20201202
Severity: normal
Dear Maintainer,
I tried to use Debian Bullseye arm64 d-i Alpha 3 to install Bullseye
to a QEMU disk. I tried -device ramfb and -device virtio-gpu-pic
for graphical installation by d-i Alpha 3. But neither of them were
used by the Alpha
Hi,
Holger Wansing wrote:
> > > I think the locale entry is wrong, as discussed above, it should be
> > > kab_DZ instead of kab_DZ.UTF-8. Just like then entries around are ks_IN
> > > or km_KH.
> >
> > Ah, ok. Thanks for the pointer, I will give that a try.
>
> That does not change anything, sa
Control: reopen -1
Control: notfound -1 3.61
[Re-sending this to the correct bug now]
nicoo wrote:
> Control: clone -1 -2
> Control: retitle -2 tasksel --new-install fails
> Control: severity -2 normal
>
> Hi,
>
> On Thu, Nov 19, 2020 at 10:21:29AM +0100, Holger Wansing wrote:
> > Swen Joach
Your message dated Mon, 7 Dec 2020 21:51:58 +0100
with message-id <20201207215158.e3085b785ecff4ea6e798...@mailbox.org>
and subject line Re: [tasksel] tasksel suggests the use of mktemp instead of
tempfile
has caused the Debian Bug report #972076,
regarding tasksel suggests the use of mktemp inste
Processing control commands:
> reopen -1
Bug #975233 {Done: Sven Joachim } [tasksel] tasksel
--new-install fails
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in
Hi,
Alper Nebi Yasak wrote:
> On 07/12/2020 19:57, john doe wrote:
> > On 12/7/2020 5:18 PM, Alper Nebi Yasak wrote:
> >> On 06/12/2020 23:11, Holger Wansing wrote:
> >>> +
> >>> +
> >>> +For this architecture the &d-i; supports two different user interfaces: a
> >>> +graphical one and a characte
Hi,
Alper Nebi Yasak wrote:
> On 06/12/2020 23:11, Holger Wansing wrote:
> > Hi,
> >
> > I read in alpha3 release-notes about the activation of the graphical
> > installer for arm64.
> >
> > This needs to be documented in the installation-guide then.
> >
> > I have prepared a first patch for t
On 07/12/2020 19:57, john doe wrote:
> On 12/7/2020 5:18 PM, Alper Nebi Yasak wrote:
>> On 06/12/2020 23:11, Holger Wansing wrote:
>>> +
>>> +
>>> +For this architecture the &d-i; supports two different user interfaces: a
>>> +graphical one and a character-based one. The graphical interface is
>>>
On 12/7/2020 5:18 PM, Alper Nebi Yasak wrote:
On 06/12/2020 23:11, Holger Wansing wrote:
+
+
+For this architecture the &d-i; supports two different user interfaces: a
+graphical one and a character-based one. The graphical interface is
+used by default unless you select an Install
+option in th
On 06/12/2020 23:11, Holger Wansing wrote:
> Hi,
>
> I read in alpha3 release-notes about the activation of the graphical
> installer for arm64.
>
> This needs to be documented in the installation-guide then.
>
> I have prepared a first patch for this, attached.
>
> There are two points remaini
This just bit me on Debian 10, although it seems to affect only
scripts run via in-target (i.e. `wget ...` works as expected,
`in-target wget ...` doesn't).
Over the years the relevant lines have been changed slightly and moved
to /lib/chroot-setup.sh:
https://salsa.debian.org/installer-team/debia
Package: flash-kernel
Version: 3.103
Severity: normal
Dear Maintainer,
I have done some changes to boot kirkwood-qnap from USB if a prepared USB drive
is found,
so we are able to run bullseye on this devices.
I have test in on TS-2019P+.
Patch is attachted.
-- System Information:
Debian Releas
13 matches
Mail list logo
