Re: Make sure to have hurd 1:0.9.git20220301-2 before upgrading glibc to 2.34... (Was: glibc transition ongoing)
Hello,
Samuel Thibault, le jeu. 18 août 2022 22:11:03 +0200, a ecrit:
> Samuel Thibault, le mar. 09 août 2022 16:37:24 +0200, a ecrit:
> > Samuel Thibault, le mar. 09 août 2022 15:06:03 +0200, a ecrit:
> > > Richard Braun, le mar. 09 août 2022 14:18:44 +0200, a ecrit:
> > > > On Mon, Aug 08, 2022 at 09:31:31PM +0200, Samuel Thibault wrote:
> > > > > There's a glibc transition which is ongoing, whose consequence is
> > > > > that upgrading libc0.3-dev to 2.34-3
> > > > I've upgraded on darnassus.sceen.net and the system cannot boot properly
> > > > any more.
> > >
> > > Oh? I'm not getting the issue on my box.
> >
> > But it happens on exodar too indeed. The boot CD there allows to chroot
> > into the system. I tried dpkg-reconfigure hurd, that didn't help.
>
> Ok, now I see the issue, it's indeed on basically all boxes except mine
> because I tinkered with /dev/random.
I have uploaded hurd version 1:0.9.git20220301-2 which sort things out.
If you have a system which is hosed, you can easily make it boot again
with
rm /dev/random /dev/urandom
and then it should boot fine, and you can upgrade hurd to version
1:0.9.git20220301-2 and let it recreate them.
I will uploaded another glibc 2.34 which adds a Breaks so that upgrading
to it will also upgrade the hurd package alongside.
Samuel
Reply to: