less (551-1) sid; urgency=low
* move binaries back to /usr/bin (closes: #500092)
is almost certainly related. If during the upgrade process the new 'less' package is unpacked but not configured yet, there's a window where the pager alternative points to the wrong location.
I can't see an easy way to fix this. What the linked Debian bug suggests, that is: make dpkg fallback to more(1) if $PAGER is not available, is probably the right balance between making dpkg solid and not adding an overly complex logic for what basically is a one-off failure.
Hi! I agree, this:
less (551-1) sid; urgency=low
* move binaries back to /usr/bin (closes: #500092)
is almost certainly related. If during the upgrade process the new 'less' package is unpacked but not configured yet, there's a window where the pager alternative points to the wrong location.
I can't see an easy way to fix this. What the linked Debian bug suggests, that is: make dpkg fallback to more(1) if $PAGER is not available, is probably the right balance between making dpkg solid and not adding an overly complex logic for what basically is a one-off failure.