use-python3-shebang.patch (Update shebang to Python 3 to fix Lintian warnings)

[iikrllx]

Description

Hi, I am trying to add your software to Debian package and I found some warnings from Lintian utility.

Description: Update shebang to Python 3 to fix Lintian warnings

• unusual-interpreter python
• executable-not-elf-or-script

This patch fix it:

--- vim-vimtex-2.16.orig/autoload/vimtex/complete/tools/convert-cwl
+++ vim-vimtex-2.16/autoload/vimtex/complete/tools/convert-cwl
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/env python3
 """Convert texstudio cwl files to VimTeX format"""
 import os
 import re
--- vim-vimtex-2.16.orig/autoload/vimtex/complete/tools/symbols-merge.py
+++ vim-vimtex-2.16/autoload/vimtex/complete/tools/symbols-merge.py
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/env python3
 """Add symbols to complete files"""
 import os
 
--- vim-vimtex-2.16.orig/autoload/vimtex/complete/tools/symbols-parse-json.py
+++ vim-vimtex-2.16/autoload/vimtex/complete/tools/symbols-parse-json.py
@@ -1,3 +1,4 @@
+#!/usr/bin/env python3
 """Blahrg."""
 import json

Steps to reproduce

No response

Expected behavior

No response

Actual behavior

No response

Do you use a latexmkrc file?

No

VimtexInfo

System info:
  OS: Debian GNU/Linux trixie/sid
  Vim version: VIM 9.1 (1-948, 950-967)
  Has clientserver: false

VimTeX project: example
  base: example.tex
  root: /home/builder
  tex: /home/builder/example.tex
  main parser: current file verified
  document class: article
  compiler: latexmk
    engine: -pdf
    options:
      -verbose
      -file-line-error
      -synctex=1
      -interaction=nonstopmode
    callback: 1
    continuous: 1
    executable: latexmk
  viewer: Zathura
    xwin id: 0
  qf method: LaTeX logfile

[lervag]

Hi, I am trying to add your software to Debian package and I found some warnings from Lintian utility.

Huh, I'm curious, why do you want to do that?

In my humble, but strong, opinion, you really should not put Vim/neovim plugins in distribution packages. Users should install plugins explicitly in their own configuration.

The main reason I have this strong opinion: When users install plugins through package managers (e.g. with Debian, Ubuntu, etc), they are often not really aware of which packages they have. They may later try to install things manually or in a different way and then experience conflicts that are hard to notice. These conflicts are hard to notice because the user often forgets about the packages installed in the system. For instance, if I were to ask for their Vim configuration, they show me their .vimrc or .config/neovim/init.lua - things look right, but still don't work as expected. They have to use e.g. :scriptnames before I notice that there are surprising scripts being loaded.

It's hard to find among ~3000 issues, but here are some issues related to people not being aware they had conflicting packages installed:

• How do I get rid of a "latexmk is not executable" error? #2965
• Error detected while processing function Tex_RunLaTeX #1111
• Viewer always defaults to evince instead of zathura #2802

I am quite confident that there are more of those.