Hi Apollon, On Thu, May 25, 2023 at 10:14:57PM +0300, Apollon Oikonomopoulos wrote: > Hi Salvatore, > > Thanks for the quick response! > > On 19:12 Thu 25 May , Salvatore Bonaccorso wrote: > > Control: tags -1 + confirmed pending > > > > I'm not yet certain, that critical severity is right, and making it > > RC. But will look into the issue today. > > Well, technically it is a regression and it does break userspace, > although I admit it probably does so only for a handful of edge-cases. > Anyway, critical is probably an overstatement, so feel free to downgrade > if you wish.
Thanks. I still cannot overview the exact/major imapct if it so does only for a handful edge cases (your for ganeti beeing one) but we can defintively keeping it as RC, thanks to you (and Rudolph Bott) for reporting the issue. > > Defitnively the issue will be fixed. Just at this stage for the > > bookworm release I will pick it for the first upload after the release > > in a point release update or a security update (whatever will come > > first likely). > > I understand that it is late in the release cycle and it would be a > shame to delay the Bookworm release for this. As far as Ganeti is > concerned, we can let people know that they should wait for the first > point release before upgrading their clusters. Ack. I'm trying to check now with release team if we still should cherry-pick the commit or going to just have to include it in the first point release. it might be worth mentioning the known issue on release though in the later case. If you have a good wording for that, that would be welcome. > Again, thanks for your work! You are welcome, and feel sorry that a breakage was introduced that late in the process for bookworm. Regards, Salvatore
