Dear Stuart,

On Wed, 22 Oct 2025 18:00:19 +0100 Stuart Henderson wrote:
> On 2025/10/22 17:48, Marco van Hulten wrote:
> > On Tue, 21 Oct 2025 16:08:23 +0100 Stuart Henderson wrote:  
> > > try this one instead. it produces a binary, at least...  
> > 
> > Thanks for all the effort.  I can install and run it.  I'm fine with
> > committing it as is, but here are some caveats:
> > 
> > 
> > [...]
> 
> > 
> > mvanhult@detekti:/tmp/detect_grid_specs.git-lfs-3.7$ git-lfs pull
> > batch request: bash: line 1: git-lfs-authenticate: command not found: exit status 127
> > Failed to fetch some objects from 'https://jureca//p/largedata2/detectdata/CentralDB/projects/z04/detect_grid_specs.git/info/lfs'
> > 
> > I'm don't know yet if this missing 'authenticate' command is an issue
> > specific to the problem that I have at hand or general.  
> 
> Seems you need to provide your own?
> https://github.com/git-lfs/git-lfs/issues/4388

Yes, it appears so.  I have not tested this.  It did not understand the
local path, but I suppose this is all expected behaviour.

I have been using existing Git LFS repos and also created them on
remotes that support Git LFS and with success with our port of git-lfs
3.7.0 (ref. patch in your e-mail of Tue, 21 Oct 2025 16:08:23 +0100).

> > Version 3.7.1 is released.  Updating the version number obviously
> > doesn't work because of the additional -vendor package.  Do such
> > additional packages make updating ports not difficult or unsustainable?  
> 
> Yes, of course, this is pretty common for go software though.
> Hopefully unless they have a bigger change it will just be a case
> of generating and hosting it though.

Could you bump the version to 3.7.1 and generate the vendor dist
package?  The patch release addresses security problems.

 Marco