Bug#204930: libc6 2.3.2-2 upgrade
During my upgrade of libc6 I ran the date command and got the exact same
error listed in this bug. A few minutes later I ran date command again and
it worked fine.
I know it's bad policy for a user to speculate on a bug, but fwiw, I think
this may be some kind of missing mutex problem. I.e. I would guess that
libc6 should upgrade in one swift, and locked (to avoid race conditions
like I think I experienced) change. I don't know if this is feasible
though... if not then I suppose some kind of nice way to recover would be
a sufficient workaround...
Drew Daniels
Reply to: