On Fri, Feb 20, 2026 at 12:31 AM Andy Shevchenko <[email protected]> wrote: > > On Fri, Feb 20, 2026 at 12:06:15AM -0800, Chris Li wrote: > > On Thu, Feb 19, 2026 at 11:20 AM Andy Shevchenko > > <[email protected]> wrote: > > > > > > On Thu, Feb 19, 2026 at 09:06:23AM -0800, Chris Li wrote: > > > > On Thu, Feb 19, 2026 at 9:00 AM Daniel Gomez <[email protected]> > > > > wrote: > > > > > > > > > > Can you please take a look? If Al patch is the correct approach, any > > > > > chance you can send it and fix this? > > > > > > > > I am asking in another thread should I pull Al's git repo instead. > > > > There are a few good commits there. > > > > > > Please, pull Al's work, My colleagues and I use his version of sparse for > > > a few > > > weeks without noticing any downsides. > > > > Thanks for the heads up. I just pulled Al's sparse repo. > > Can you also issue a new tag (say 0.6.5) so the distros can really be pushed > to > update the quite outdated sparse in their repos?
Sure. I can give it a spin this weekend and keep you posted. There is one risk on my signing key, it might be expired and I need to sort that out. Meanwhile, please give the current sparse repo some good tests. Chris
