Bug#983435: you all forgot to fix stable

2021-07-22 Thread bugsgrid+deb
Control: found -1 2.02+dfsg1-20+deb10u3 Control: found -1 2.04-10 Control: fixed -1 2.04-19 # adding back versions for reopen Seriously, I reported that the issue exists in sid _too_, just for your convenience, and then you fixed only sid... what is this? If refreshing the patch is so hard to

Bug#983435: confirmed reproducible

2021-03-07 Thread bugsgrid+deb
Control: reassign -1 src:grub2 Control: found -1 2.04-10 Control: notfound -1 2.04-9 Control: found -1 2.02+dfsg1-20+deb10u3 Control: notfound -1 2.02+dfsg1-20+deb10u2 Turned out that the symptom was not specific to grub-efi. It does reproduce on grub-pc too. Short steps to test: 1) rename

Bug#983435:

2021-03-05 Thread bugsgrid+deb
Control: retitle -1 upgrade or grub-install breaks system if udev is not installed May I ask what I'm supposed to do next? As any grub packages in usual debian repositories are no longer working for me, I'm forced to dig up snapshot.debian.org to revert (yes I forgot to save working .deb locally,

Bug#983435: Regarding the backup/restore function

2021-02-27 Thread bugsgrid+deb
Ah, my router doesn't have udev! In osdep/linux/hostdisk.c:sysfs_partition_path(), calling udevadm through grub_util_exec_pipe() will fail and fall through to *unpatched* exit(). Sounds plausible? If my guess is right, perhaps sid is affected too. Sorry I don't have any testbed, if anyone

Bug#983435: Regarding the backup/restore function

2021-02-26 Thread bugsgrid+deb
On Fri, 26 Feb 2021 15:21:59 + Dimitri John Ledkov wrote: >are grub.mo from grub-common somehow excluded on the system? I have no idea, I don't have localepurge installed on that machine. I belive those missing grub.mo's are actually not in debian's grub-common, or rather, not in the entire

Bug#983435: Regarding the backup/restore function

2021-02-25 Thread bugsgrid+deb
Regarding the backup/restore function in the commit bb3205709aa9f83e1c8cb91e7f6f9f110d41b34e, for me it seems bringing in more critical dangers than the safety it provides. The logic is too error prone, it relies on on_exit() absolutely never duped by any fork()'s, meaning it's requiring

Bug#983435: Just a wild guess...

2021-02-25 Thread bugsgrid+deb
Hi mainteners, Given the observations, I feel it very likely being caused by misfiring of restore_backup_on_exit(), and looking around the source tree I found something suspicious: In the commit 5dec0f2f9cd4d4dd0109c25cd2b399a780179020, | unix exec: avoid atexit handlers when child exits |