Hey again,
Cyril Brulebois <k...@debian.org> (2018-07-06):
> For the sake of completeness, here's an extra data point. If someone
> ends up with two peers with versions 2.48.3-1 vs. 2.48.3-1+b1 (hosts
> with s-p-u enabled, but not dist-upgraded at the same time), one can
> get this very issue:
> | Uncaught exception Failure("input_value: bad bigarray kind")
>
> with extra unfriendly debug messages (hey, look at those in the github
> bug tracker, the ones we wanted to get rid of).
>
> I thought I'd mention the possibly surprising outcome for people not
> following debian-release@ closely.Also, that seems to completely invalidate the on-disk cache, which is likely the reason why the first run with an upgraded version (on either side, by the way) can take several (dozens of) minutes instead of a couple of seconds. It might have been a good idea to mention that in the binNMU request. It might also be a good idea to document those consequences in some way. Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
