Hi,
Am Dienstag, 17. März 2020 schrieb Steve McIntyre:
> On Tue, Mar 17, 2020 at 12:06:45PM +, Steve McIntyre wrote:
> >
> >I can see from your log that you're just using ext4 for the new
> >system, and you're booting in BIOS mode. Any other disks attached to
> >the system?
> >
> >Testing at t
Processing commands for cont...@bugs.debian.org:
> tags 954079 + sid bullseye
Bug #954079 [magic-wormhole] magic-wormhole: Fails to send with a type error
Added tag(s) bullseye and sid.
> notfound 954100 3.0.4
Bug #954100 [src:gdcm] Error: A deprecated csdestruct_derived typemap was found
for vtk
On Tue, Mar 17, 2020 at 12:06:45PM +, Steve McIntyre wrote:
>
>I can see from your log that you're just using ext4 for the new
>system, and you're booting in BIOS mode. Any other disks attached to
>the system?
>
>Testing at the weekend didn't show any problems for me or Andy. I'm
>doing an expl
Hi,
Am Dienstag, 17. März 2020 schrieb Steve McIntyre:
> >Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown
> >filesystem.
>
> I can see from your log that you're just using ext4 for the new
> system, and you're booting in BIOS mode. Any other disks attached to
> the sys
Hi Holger,
On Tue, Mar 17, 2020 at 11:13:27AM +0100, Holger Wansing wrote:
>
>Holger Wansing wrote:
>> >
>> > I will sent installation logs shortly.
>>
>> Logs attached.
>
>The relevant part seems to be:
...
>Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size
>Mar 16
On 3/17/20 12:49 PM, Holger Wansing wrote:
> However:
>
>> Mar 16 09:55:43 main-menu[285]: (process:1258): grub-probe: error: unknown
>> filesystem.
> [...]
>> Mar 16 09:55:43 main-menu[285]: (process:1258): corrupted size vs. prev_size
>> Mar 16 09:55:43 main-menu[285]: (process:1258): Aborted
>
Hi,
Am Dienstag, 17. März 2020 schrieb John Paul Adrian Glaubitz:
> On 3/17/20 11:05 AM, Holger Wansing wrote:
> > Logs attached.
>
> grub-installer did not report any problems:
>
> Mar 16 09:55:41 grub-installer: info: Installing grub on '/dev/sda'
> Mar 16 09:55:41 grub-installer: info: grub-i
On 3/17/20 11:05 AM, Holger Wansing wrote:
> Logs attached.
grub-installer did not report any problems:
Mar 16 09:55:41 grub-installer: info: Installing grub on '/dev/sda'
Mar 16 09:55:41 grub-installer: info: grub-install does not support --no-floppy
Mar 16 09:55:41 grub-installer: info: Running
Hi,
Holger Wansing wrote:
> >
> > I will sent installation logs shortly.
>
> Logs attached.
The relevant part seems to be:
Mar 16 09:55:41 grub-installer: info: Installing grub on '/dev/sda'
Mar 16 09:55:41 grub-installer: info: grub-install does not support --no-floppy
Mar 16 09:55:41 grub-
Holger Wansing wrote:
>
> I will sent installation logs shortly.
Logs attached.
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
installer.tar.gz
Description: application/gzip
Package: debian-installer
Severity: grave
While testing the alpha2 netinst image on a spare Thinkpad, I found that grub
cannot be installed successfully (and rebooting into the new installation
fails as well). This was ok in alpha1.
This might look like an grub-installer issue, however there wer
On 3/17/20 10:38 AM, Simon McVittie wrote:
> On Tue, 17 Mar 2020 at 09:13:33 +0100, John Paul Adrian Glaubitz wrote:
>> I think enabling vi in the busybox configuration is actually the best
>> approach
>> to address this problem as this way we continue to ship vi with
>> debian-installer
>> and a
On Tue, 17 Mar 2020 at 09:13:33 +0100, John Paul Adrian Glaubitz wrote:
> I think enabling vi in the busybox configuration is actually the best approach
> to address this problem as this way we continue to ship vi with
> debian-installer
> and at the same time get rid of the vim dependency which i
Hi Simon!
On 3/16/20 12:31 PM, Simon McVittie wrote:
> Steps to reproduce:
>
> - Install a chroot/container
> - Install busybox
>
> Expected results:
>
> - If a more fully-featured vi is installed (vim, vim-*, nvi, etc.) then it
> provides the vi and view commands in PATH
> - Otherwise, "vi f
14 matches
Mail list logo
