Comment # 3 on bug 1140733 from
(In reply to Tristan Miller from comment #2)
> 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.

Hello Tristan, I've assigned this bug to you, because you are listed as a
maintainer of lbzip2:

# osc maintainer -e lbzip2
Defined in package: Archiving/lbzip2 
  bugowner of lbzip2 : 
   -

  maintainer of lbzip2 : 
   psychonaut@nothingisreal.com


If this is not true, then feel free to reassign it to the responsible person
and reset your maintainership. Thanks!

> 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

This is probably a typo here. The current version we have both in Leap and
Tumbleweed is 2.5, not 2.25. However, it really seems that the patch can't be
applied as is and it needs some adjustments anyway. I would let it up to
maintainers if they want to wait for the new version 2.6 or if they decide to
backport this patch.


You are receiving this mail because: