On Sun, 19 Feb 2023 19:01:22 +0100 Paul Gevers wrote:
> On 2023-02-15 21:04:36 +0100, Sebastian Ramacher wrote:
> >
> > On 2023-02-14 01:01:38 +0100, Daniel Leidert wrote:
> > >
> > > This problem breaks e.g. vmdb2. I can no longer create a Bullseye
> > > system image with vmdb2 on Sid, beca
Processing commands for cont...@bugs.debian.org:
> reassign 1031639 freedom-maker 0.32
Bug #1031639 [freedom-make] e2fsprogs: generates filesystems that grub-install
doesn't recognize
Warning: Unknown package 'freedom-make'
Bug reassigned from package 'freedom-make' to 'freedom-maker'.
No longer
Processing control commands:
> clone -1 -2
Bug #1030939 [e2fsprogs] e2fsprogs: generates filesystems that grub-install
doesn't recognize
Bug 1030939 cloned as bug 1031639
> reassign -2 freedom-make 0.32
Bug #1031639 [e2fsprogs] e2fsprogs: generates filesystems that grub-install
doesn't recognize
Control: clone -1 -2
Control: reassign -2 freedom-make 0.32
Control: clone -1 -3
Control: reassign -3 debos 1.1.1-2
On 2023-02-15 21:04:36 +0100, Sebastian Ramacher wrote:
> Control: clone -1 -2
> Control: reassign -2 vmdb2 0.26-2
>
> On 2023-02-14 01:01:38 +0100, Daniel Leidert wrote:
> > Hi
Processing control commands:
> clone -1 -2
Bug #1030939 [e2fsprogs] e2fsprogs: generates filesystems that grub-install
doesn't recognize
Bug 1030939 cloned as bug 1031415
> reassign -2 fai 6.0
Bug #1031415 [e2fsprogs] e2fsprogs: generates filesystems that grub-install
doesn't recognize
Bug reass
Control: clone -1 -2
Control: reassign -2 fai 6.0
Control: clone -1 -3
Control: reassign -3 grml-debootstrap 0.102
On 2023-02-15 21:04:36 +0100, Sebastian Ramacher wrote:
> Control: clone -1 -2
> Control: reassign -2 vmdb2 0.26-2
>
> On 2023-02-14 01:01:38 +0100, Daniel Leidert wrote:
> > Hi Stev
Processing control commands:
> clone -1 -2
Bug #1030939 [e2fsprogs] e2fsprogs: generates filesystems that grub-install
doesn't recognize
Bug 1030939 cloned as bug 1031364
> reassign -2 vmdb2 0.26-2
Bug #1031364 [e2fsprogs] e2fsprogs: generates filesystems that grub-install
doesn't recognize
Bug
Control: clone -1 -2
Control: reassign -2 vmdb2 0.26-2
On 2023-02-14 01:01:38 +0100, Daniel Leidert wrote:
> Hi Steve,
>
> I believe that your fix to grub2 in Sid is not enough to handle
> #1030939/#1030846.
>
> This problem breaks e.g. vmdb2. I can no longer create a Bullseye
> system image wit
Am Dienstag, dem 14.02.2023 um 16:53 -0500 schrieb Theodore Ts'o:
[snip]
Your arrogant and ignorant attitude is frustrating, to say the least.
You don't care about the mess you create, for a feature, that probably
only a handful of people will ever need (I did a quick search and
didn't find anyth
On Tue, Feb 14, 2023 at 07:35:51PM +0100, Daniel Leidert wrote:
>
> As soon as this version hits testing, you have successfully disabled
> the last working environment to use vmdb2 to create images of Ubuntu
> and Debian. As soon as this version hits Testing, one then can no
> longer build images
Am Dienstag, dem 14.02.2023 um 12:34 -0500 schrieb Theodore Ts'o:
>
[..]
> In any case, a version of grub that will support the csum_seed feature
> will be landing in Bookworm in just a few days. So at that point,
> you'll be able to create VM images for Bookworm and Sid that will work
> with the
There is another issue with vmdb2 if you are using XFS. Starting with
xfsprogs 5.15 (which is already in testing), bigtime is enabled by
default, so that newly created XFS file systems won't be subject to
timestamp overflow in 2038. Grub didn't land support for this feature
until 8b1e5d1936ff ("f
Am Dienstag, dem 14.02.2023 um 14:58 + schrieb Steve McIntyre:
> On Tue, Feb 14, 2023 at 12:50:18PM +0100, Daniel Leidert wrote:
>
>
[..]
> Breakages happen like this,
This breakage is *unnecessary* and it breaks at the momnent *all*
debootstrap installations except for doing a bookworm/sid
On Tue, Feb 14, 2023 at 12:50:18PM +0100, Daniel Leidert wrote:
>Am Dienstag, dem 14.02.2023 um 10:45 + schrieb Steve McIntyre:
>> On Tue, Feb 14, 2023 at 11:34:13AM +0100, Daniel Leidert wrote:
>> > Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
>>
>> ...
>>
>> > > But a gen
Am Dienstag, dem 14.02.2023 um 10:45 + schrieb Steve McIntyre:
> On Tue, Feb 14, 2023 at 11:34:13AM +0100, Daniel Leidert wrote:
> > Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
>
> ...
>
> > > But a generalized requirement that we be able to use debootstrap and
> > > vmdb2
On Tue, Feb 14, 2023 at 11:34:13AM +0100, Daniel Leidert wrote:
>Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
...
>> But a generalized requirement that we be able to use debootstrap and
>> vmdb2 to be able to bootstrap an arbitrarily old distribution doesn't
>> seem to be reaso
Am Montag, dem 13.02.2023 um 21:35 -0500 schrieb Theodore Ts'o:
> On Tue, Feb 14, 2023 at 01:01:38AM +0100, Daniel Leidert wrote:
> > Hi Steve,
> >
> > I believe that your fix to grub2 in Sid is not enough to handle
> > #1030939/#1030846.
> >
> > This problem breaks e.g. vmdb2. I can no longer cr
On Tue, Feb 14, 2023 at 01:01:38AM +0100, Daniel Leidert wrote:
> Hi Steve,
>
> I believe that your fix to grub2 in Sid is not enough to handle
> #1030939/#1030846.
>
> This problem breaks e.g. vmdb2. I can no longer create a Bullseye
> system image with vmdb2 on Sid, because the grub-install ste
Theodore Ts'o (2023-02-10):
> But that problem has already been solved by cloning the bug back to
> e2fpsrogs (#1030939) which will prevent e2fsprogs from transitioning
> to testing, no? So what's the problem.
I never said there was a problem with the current state of things
(indeed, that's one
On Fri, Feb 10, 2023 at 08:31:04AM +0100, Cyril Brulebois wrote:
> > Holding back file system development because grub2 uptsream is super
> > slow doesn't seem like a reasonable way forward, so I really don't
> > want to set this precedent.
>
> The Bookworm freeze has started, we need to be able t
Theodore Ts'o (2023-02-09):
> On Thu, Feb 09, 2023 at 06:55:08PM +0100, Sven Joachim wrote:
> > That is not going to help, because IIUC grub-install is run from the
> > target system that you are installing, and there is no
> > grub2-common-udeb.
>
> Right, but if the conflict in e2fsprogs-udeb p
Hi
On Thu, Feb 09, 2023 at 03:16:15PM -0500, Theodore Ts'o wrote:
> Right, but if the conflict in e2fsprogs-udeb prevents the installer
> from pulling in an overly new version of e2fsprogs-udeb, that woul be
> sufficient, no?
No, it does not. Conflicts have undefined behaviour for udebs.
Bastia
On Thu, Feb 09, 2023 at 06:55:08PM +0100, Sven Joachim wrote:
> >>
> >> Thanks from me as well :-). To prevent e2fsprogs from migrating to
> >> testing before grub2 and breaking d-i, I am reassigning a copy of this
> >> bug back to e2fsprogs. It may be closed once grub2 2.06-8 enters
> >> Bookwor
[Switching over to the cloned bug.]
On 2023-02-09 12:31 -0500, Theodore Ts'o wrote:
> On Thu, Feb 09, 2023 at 06:04:23PM +0100, Sven Joachim wrote:
>>
>> Thanks from me as well :-). To prevent e2fsprogs from migrating to
>> testing before grub2 and breaking d-i, I am reassigning a copy of this
>
24 matches
Mail list logo
