Problem with migrating from glibc[crypt] to libxcrypt

[eccerr0r]

I had boost die on me at one point saying it couldn't find crypt.h but unfortunately didn't keep the build.log - merged libxcrypt allowed boost to later build.
I didn't see the dep in the ebuild, wonder if it should be there?
Grepping through the sources I got the impression its internal zlib seems to include crypt.h... but didn't totally figure out the logic with wincrypt...

[eccerr0r]

Boo (as in the rasp chant, not for Halloween)

I had gone through a remote libxcrypt upgrade merge and it failed at some apparently unrelated package (same problem as 814140. Little did I know that glibc upgraded to -crypt or something but not openssh/sshd. Due to apparently saving the old glibc that openssh was linked to, it seems to still start fine. However when it tries to fork sshd when someone connects, it fails, I'm thinking it tries to dynamic link to the new glibc with crypt() missing! So I lost access to connect to the remote machine after exiting out of an existing session.

Rebuilding openssh restored operation.

Word of the wise: login to machines multiple times and do not logout until after you verified sshd. Also due to the #*@(#&%!@ing NAT timeout issue, make sure you keepalive everything... *groan*

Got lucky this time but got this close to having to make a service call...

[pjp]

ManOwaR's thread has been split off to: stuck at glibc [crypt] to libxcrypt circular dependency.