control: tags -1 moreinfo This error is not plausible given what libk5crypto3 does and given the change between u2 and u3, which didn't impact libk5crypto3 at all. I'd need to see some actual errors linking the problem to libk5crypto3, not just circumstantial evidence that the problem happens with the new packages and not the old. I mean I appreciate that looks interesting, but it could be related to some other environmental factor, like changes in the filesystem caused by running apt.
No, that's not very likely, but nor is it that a libk5crypto3 change (especially when there were no code changes to libk5crypto3 between u2 and u3) would cause a drm problem.
