IMPORTANT Announcement

[pete4abw]

For over 19 years I have worked on the lrzip and lrzip-next projects. This project has not had the same level of contributions or even issue reports as lrzip. In addition, there is no push for improvements, and few reports of bugs. The lzma SDK releases do not really apply to the library or offer improvements to lrzip-next functionality. And, other standalone compression programs have really improved. Even the rzip preprocessing phase, which made lrzip so special in the past, is not a unique feature anymore.

I am very proud of how lrzip-next has evolved, and indeed it remains very usable and beneficial. I just don't know where to go from here. And I am tired of working alone. So, a break is in order. I will continue to monitor any Issues that may pop up, but as for improvements, I will monitor for suggestions? Six years ago, I posted a Help Wanted to get Zpaq to show progress. No help came.

[AlleyPally]

Thank you for your dedication and hard work for all this time! <3

To me, it appears that lrzip-next didn't receive the same online coverage that lrzip did, despite it having more features and better performance. I guess compression fanaticism and the like has died down? It frankly saddens me, as this is a very polished and well thought out compression program. Your work and Kolivas' on lrzip and, subsequently, it's fantastical compression, was the main reason why zstd decided to add a --long flag! It was also mentioned when implementing their rolling hash, as far as I can tell, so your work was phenomenal! That and I haven't seen anything compress as well as it does.

It is sad but it is fair, seeing that there haven't been that many issues nor help. Nevertheless, I can't wait to see what else you might have in store in the future!

May all go well for you. You deserve nothing but the best! Thank you again!

[God-damnit-all]

And here I was hoping for an eventual Windows release, it's why I had this project starred.

Have you thought about simply moving the project to the lrzip repo, making it the "next" branch and default, and then creating a new repo for the older lrzip? That would get the project some more attention for when you next feel like working on it.

Have a good one!

[pete4abw]

Thank you for the comment! Con and I disagreed on features and direction. This is why I forked off in 2019. I never intended for this to work under Windows. You are welcome to enjoy the features or try and convince another developer (or yourself) to continue development.

…

-- Peter Hyman On April 17, 2026, at 13:12, God-damnit-all ***@***.***> wrote: And here I was hoping for an eventual Windows release, it's why I had this project starred. Have you thought about simply moving the project to the lrzip repo, making it the "next" branch and default, and then creating a new repo for the older lrzip? That would get the project some more attention for when you next feel like working on it. Have a good one! — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***> [ { ***@***.***": "<a href="http://schema.org">http://schema.org</a>", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "<a href="#171?email_source=notifications">https://github.com/pete4abw/lrzip-next/discussions/171?email_source=notifications</a>\u0026email_token=ACPBHBNHWM7EOPH4IR2AYOD4WJXX7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGA3DAOBVUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVNTW2YLJNRPWG3DJMNVQ#discussioncomment-16606085", "url": "<a href="#171?email_source=notifications">https://github.com/pete4abw/lrzip-next/discussions/171?email_source=notifications</a>\u0026email_token=ACPBHBNHWM7EOPH4IR2AYOD4WJXX7A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGA3DAOBVUZZGKYLTN5XKMYLVORUG64VFMV3GK3TUVNTW2YLJNRPWG3DJMNVQ#discussioncomment-16606085", "name": "View Discussion" }, "description": "View this Discussion on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "<a href="https://github.com">https://github.com</a>" } } ]