On February 27, 2021 8:44:44 PM UTC, Lucas Nussbaum wrote:
>On 27/02/21 at 15:16 +0100, Evgeni Golov wrote:
>> On Fri, Feb 26, 2021 at 10:54:32PM +0100, Lucas Nussbaum wrote:
>> > Tentative patch:
>> > https://salsa.debian.org/cloud-team/debian-vagrant-images/-/commit/b82d522f65b507767f909b2b94
On 27/02/21 at 15:16 +0100, Evgeni Golov wrote:
> On Fri, Feb 26, 2021 at 10:54:32PM +0100, Lucas Nussbaum wrote:
> > Tentative patch:
> > https://salsa.debian.org/cloud-team/debian-vagrant-images/-/commit/b82d522f65b507767f909b2b9471c5a9ade75e05
>
> Thanks Lucas! That looks quite like the "first-
On 27/02/21 at 20:01 +0100, Emmanuel Kasper wrote:
> Le 26/02/2021 à 22:54, Lucas Nussbaum a écrit :
> > Tentative patch:
> > https://salsa.debian.org/cloud-team/debian-vagrant-images/-/commit/b82d522f65b507767f909b2b9471c5a9ade75e05
>
> This approach is IMHO the easier way forward.
>
> However I
Le 26/02/2021 à 22:54, Lucas Nussbaum a écrit :
> On 26/02/21 at 20:07 +0100, Lucas Nussbaum wrote:
>> On 14/02/21 at 08:48 +0100, Evgeni Golov wrote:
>>> On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
IMO we cannot know which device name is used by the users virtualisation
>>
On Fri, Feb 26, 2021 at 10:54:32PM +0100, Lucas Nussbaum wrote:
> On 26/02/21 at 20:07 +0100, Lucas Nussbaum wrote:
> > On 14/02/21 at 08:48 +0100, Evgeni Golov wrote:
> > > On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
> > > > IMO we cannot know which device name is used by the us
On 26/02/21 at 20:07 +0100, Lucas Nussbaum wrote:
> On 14/02/21 at 08:48 +0100, Evgeni Golov wrote:
> > On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
> > > IMO we cannot know which device name is used by the users virtualisation
> > > environment.
> > > So, what is the be setting
On 26/02/21 at 22:30 +0100, Thomas Goirand wrote:
> This could well be in another bug report, if someone hasn't opened it yet.
There's #982182, but it's a bit different from what you are saying here.
Lucas
On 2/26/21 8:07 PM, Lucas Nussbaum wrote:
> On 14/02/21 at 08:48 +0100, Evgeni Golov wrote:
>> On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
>>> IMO we cannot know which device name is used by the users virtualisation
>>> environment.
>>> So, what is the be setting without knowing
On 14/02/21 at 08:48 +0100, Evgeni Golov wrote:
> On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
> > IMO we cannot know which device name is used by the users virtualisation
> > environment.
> > So, what is the be setting without knowing the device name?
> >
> > Or is /dev/sda use
On Mon, Feb 15, 2021 at 09:21:30AM +0100, Thomas Lange wrote:
> One solution would be to not set it for cloud images, but during first
> boot check if it's unset and then try to determine the device name and
> fill debconf to make grub happy.
The cloud images don't use grub-pc at all since Buster!
> On Sun, 14 Feb 2021 23:09:54 +0100, Thomas Goirand said:
> (see my example with virtio-blk and virtio-scsi). The safest approach
> was to have no default device set, though now it fails...
It's very anoying that the grub prople changed this in a point
release.
One solution would be
On 2/14/21 8:48 AM, Evgeni Golov wrote:
> On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
>> IMO we cannot know which device name is used by the users virtualisation
>> environment.
>> So, what is the be setting without knowing the device name?
>>
>> Or is /dev/sda used in most envi
On Sat, Feb 13, 2021 at 11:57:52PM +0100, Thomas Lange wrote:
> IMO we cannot know which device name is used by the users virtualisation
> environment.
> So, what is the be setting without knowing the device name?
>
> Or is /dev/sda used in most enviroments?
For VirtualBox sda is a pretty safe
Le 12/02/2021 à 19:14, Evgeni Golov a écrit :
> On Fri, Feb 12, 2021 at 06:55:35PM +0100, Emmanuel Kasper wrote:
>> Le 12/02/2021 à 12:36, Evgeni Golov a écrit :
>>> On Fri, Feb 12, 2021 at 10:03:08AM +0100, Thomas Lange wrote:
This behaviour was also reported as #982182
>>>
>>> Interesting, t
On Fri, Feb 12, 2021 at 06:55:35PM +0100, Emmanuel Kasper wrote:
> Le 12/02/2021 à 12:36, Evgeni Golov a écrit :
> > On Fri, Feb 12, 2021 at 10:03:08AM +0100, Thomas Lange wrote:
> >> This behaviour was also reported as #982182
> >
> > Interesting, thanks!
> >
> > To me the GRUB change seems reas
Le 12/02/2021 à 12:36, Evgeni Golov a écrit :
> On Fri, Feb 12, 2021 at 10:03:08AM +0100, Thomas Lange wrote:
>> This behaviour was also reported as #982182
>
> Interesting, thanks!
>
> To me the GRUB change seems reasonable, even if a tad unexpected in a
> point release.
>
> You change to FAI [
On Fri, Feb 12, 2021 at 10:03:08AM +0100, Thomas Lange wrote:
> This behaviour was also reported as #982182
Interesting, thanks!
To me the GRUB change seems reasonable, even if a tad unexpected in a
point release.
You change to FAI [1] looks pretty much how I would envision a correct
fix in the
This behaviour was also reported as #982182
--
viele Grüße Thomas
Package: cloud.debian.org
Ohai,
when trying to update a VM based on the debian/buster64 box from 10.4 to
10.8, grub-pc can't be upgraded non-interactively because it doesn't
know which devices to install GRUB to (grub-pc/install_devices debconf
question is empty) and that's a fatal error for GRUB
19 matches
Mail list logo
