Re: 11.8 planning

2023-06-19 Thread Cyril Brulebois
Hi, Jonathan Wiltshire (2023-06-19): > I'm sending this separately to a similar mail for 12.1. That's because the > timings are far enough out that they would make sense on separate weekends, > but they could also be stretched[1] and combined. > > Two months from 29th April is around the 1st Ju

Re: 12.1 planning

2023-06-19 Thread Cyril Brulebois
Hi, Jonathan Wiltshire (2023-06-19): > The promised 4-6 weeks following release for 12.1 looks like: > > 8th July (4) > 15th July (5) > 22nd July (6) > > The first of them would combine with a very stretched 11.8; SRM might > prefer to get 11.8 done earlier and leave more time for 12.1 to matu

11.8 planning

2023-06-19 Thread Jonathan Wiltshire
Hi, I'm sending this separately to a similar mail for 12.1. That's because the timings are far enough out that they would make sense on separate weekends, but they could also be stretched[1] and combined. Two months from 29th April is around the 1st July, so I propose: 1st July 8th July 15th Ju

12.1 planning

2023-06-19 Thread Jonathan Wiltshire
Hi, The promised 4-6 weeks following release for 12.1 looks like: 8th July (4) 15th July (5) 22nd July (6) The first of them would combine with a very stretched 11.8; SRM might prefer to get 11.8 done earlier and leave more time for 12.1 to mature. Thanks, -- Jonathan Wiltshire

Re: 12.1 planning

2023-06-19 Thread Donald Norwood
Hi On 6/19/23 17:04, Jonathan Wiltshire wrote: Hi, The promised 4-6 weeks following release for 12.1 looks like: 8th July (4) 15th July (5) 22nd July (6) If the 8th is doable Press can do it and the 15th, would prefer the 15th or 22nd. -- Be well, -Donald -- - ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Donal

Re: 11.8 planning

2023-06-19 Thread Donald Norwood
Hi, On 6/19/23 17:02, Jonathan Wiltshire wrote: Hi, I'm sending this separately to a similar mail for 12.1. That's because the timings are far enough out that they would make sense on separate weekends, but they could also be stretched[1] and combined. Two months from 29th April is around the

Bug#1038612: The hanging is of invoking another script

2023-06-19 Thread Budi
The hanging is of invoking another script, so need to trace it by inserting set-x in /usr/lib/os-probes/50mounted-tests the trace: + partition=/dev/sda1 + . /usr/share/os-prober/common.sh ++ cleanup_tmpdir=false ++ progname= ++ type mapdevfs ++ fs_type /dev/sda1 ++ local fstype= ++ type lsblk ++