Op zo 4 jul. 2021 om 00:42 schreef Colin Watson <[email protected]>: > Sorry for my delay - it took me a while to spot the problem. libc6's > postinst does arrange to restart services where needed, but in this case > it doesn't realize that you have the ssh service installed because you > only have the openssh-server package installed, not the ssh metapackage > (i.e. the package with the same name as the service). > > I've proposed > https://salsa.debian.org/glibc-team/glibc/-/merge_requests/3 to fix > this. glibc maintainers, if there's any way to get this into bullseye, > I'm sure it would help avoid some people upgrading remote systems ending > up being unable to fix them if something goes wrong between configuring > libc6 and configuring openssh-server. Also CCing debian-release for > their information, as I know it's pretty late for glibc changes.
Thanks Colin! I assume openssh-server would then be restarted after the "There are services installed on your system which need to be restarted when certain libraries, such as libpam, libc, and libssl, are upgraded." question. But ssh is already 'down' when that question is being asked, so wouldn't there still be a time window, with required user interaction, where ssh would be 'down'? -- Olaf
