Re: [lmi] Should we update libxml and its kin?

[Greg Chicares]

On 2022-03-18 15:05, Greg Chicares wrote:
[...]
> How do I resolve git-status's complaint below? The last time
> I saw something like this, I committed it explicitly, which
> IIRC was exactly the wrong thing to do; but last time, again
> IIRC, the "untracked" complaint went away when I pushed, yet
> I have pushed and it still occurs:
> 
> /opt/lmi/src/lmi[0]$git status      
> On branch master
> Your branch is ahead of 'origin/master' by 1 commit.
>   (use "git push" to publish your local commits)
> 
> Changes not staged for commit:
>   (use "git add <file>..." to update what will be committed)
>   (use "git restore <file>..." to discard changes in working directory)
>   (commit or discard the untracked or modified content in submodules)
>         modified:   third_party/libxml2 (untracked content)
> 
> no changes added to commit (use "git add" and/or "git commit -a")

More information:

  /opt/lmi/src/lmi[0]$git -C third_party/libxml2 status                         
  HEAD detached at 8d06ccd4
  Untracked files:
    (use "git add <file>..." to include in what will be committed)
          configure~
  nothing added to commit but untracked files present (use "git add" to track)

This 'configure\~' file seems to be an undesired backup of
the prior version of a generated file. My guess is that it
can just be deleted manually, but I don't want to do anything
manually in all my various chroots. What's the tasteful way
to suppress this thing automatically?