Comment # 2 on bug 1140733 from Tristan Miller

Not sure why this issue has been assigned to me -- I had agreed to maintain the
package only as a "last resort" in the event that the existing maintainers had
gone AWOL, which does not seem to be the case.

Nonetheless, I took a look at the lbzip2 commit in question, which is from
October 2017.  It doesn't look trivial to apply this to the stable version
2.25, which was released in March 2014; there are a lot of intervening changes
to the code.  Simply applying that 2017 commit as a patch to 2.25 fails in a
couple of places; even if it had succeeded, I wouldn't feel confident in the
correctness of the resulting code due to other changes in the other data
structures since 2.25.

IMHO this problem would better be fixed by someone who is already familiar with
the lbzip2 source, or who has the time to develop such a familiarity.  In the
best case the patch should be made upstream and a new version of lbzip2
released.  I have suggested this to the upstream maintainers here:
https://github.com/kjn/lbzip2/commit/b6dc48a7b9bfe6b340ed1f6d72133608ad57144b#commitcomment-34235235