Depreciation warning on Debian 13 (Trixie) slim container

[adrianparilli]

Hello everyone,

I'm testing to build the docker image of the current version (2.35) from debian-slim:trixie. It builds just fine, but when I try any command from virtnbdbackup, virtnbdrestore, and virtnbdmap, so far; it throws the following warning before to proceed:

/usr/local/bin/virtnbdbackup:4: DeprecationWarning: pkg_resources is deprecated as an API. See https://setuptools.pypa.io/en/latest/pkg_resources.html
  __import__('pkg_resources').run_script('virtnbdbackup==2.35', 'virtnbdbackup')

Running with no errors, apparently...

When a backup is made in auto mode, the same warning is repeated a second time, at the very end before to exit.

It even appears when using something so basic as --version flag.

Certainly, this is not happening with the official docker image (ATM built from debian-slim:bookworm), therefore not an issue right now (and the reason I'm opening this discussion instead of an issue).

However, the docker image will need to be eventually updated to Trixie, and it would become an annoying warning that disrupts logs, at least.

The link provided by the deprecation warning asks to refrain about using pkg_resources. Unfortunately I'm not used with Python so can't say if it's just an annoyance, or an eventual cause of issues in the short or mid term...

The only clues I can provide right now are:

• Python version inside Trixie container is 3.13.5 (default provided by apt). I have not tested yet in a non-containerized Debian 13 environment (fresh or upgraded from version 12) but I presume this is replicable outside containers, at least in Debian

• I tried a quick test building/installing virtnbdbackup 2.34 in my local (Archlinux) from this AUR pkgbuild. Turns out the fact I don't see that warning, and my python version is 3.13.7!

So, is not that simple as python version. Maybe a punctual dependency, is a problem specific with Debian 13, or just a matter to fix that into the code.

Any ideas?

[abbbi]

did you install via python setup.py or pip install .?

I think it can be solved by installing via pip install as outlined:

https://github.com/abbbi/virtnbdbackup?tab=readme-ov-file#python-package

The official docker images use bookworm, where the python setup.py installation method is not yet treated as deprecated.

Its another setup.py is deprecated thing, i guess.

[adrianparilli]

Hello again @abbbi, and thank you for your quick reply!

Indeed the Dockerfile uses setup.py and there's no other changes but the source debian image (from bookworm to trixie slim.

I will try pip install and tinker with this asap, and will let you know how it goes.

Have a good day!

[adrianparilli]

Hello @abbbi,

The warning is gone...

The only way that pip builds for me and makes virtnbdbackup tools globally available, is by using --break-system-packages option.

Remaining dependencies provided by Debian not present as of now (python3-cffi and python3-pycparser) differ just slightly compared with PyPI versions, but in either case, builds and seems to work fine.

Here's the relevant output as I'm building now (with all dependencies from Debian):

root@737e250b4c35:/tmp/virtnbdbackup# pip install  --break-system-packages .
Processing /tmp/virtnbdbackup
  Preparing metadata (setup.py) ... done
Requirement already satisfied: libvirt-python>=6.0.0 in /usr/lib/python3/dist-packages (from virtnbdbackup==2.36) (11.3.0)
Requirement already satisfied: tqdm in /usr/lib/python3/dist-packages (from virtnbdbackup==2.36) (4.67.1)
Requirement already satisfied: lz4>=2.1.2 in /usr/lib/python3/dist-packages (from virtnbdbackup==2.36) (4.4.0+dfsg)
Requirement already satisfied: lxml in /usr/lib/python3/dist-packages (from virtnbdbackup==2.36) (5.4.0)
Requirement already satisfied: paramiko in /usr/lib/python3/dist-packages (from virtnbdbackup==2.36) (3.5.1)
Requirement already satisfied: typing_extensions in /usr/lib/python3/dist-packages (from virtnbdbackup==2.36) (4.13.2)
Requirement already satisfied: colorlog in /usr/lib/python3/dist-packages (from virtnbdbackup==2.36) (6.9.0)
Requirement already satisfied: bcrypt>=3.2 in /usr/lib/python3/dist-packages (from paramiko->virtnbdbackup==2.36) (4.2.0)
Requirement already satisfied: cryptography>=3.3 in /usr/lib/python3/dist-packages (from paramiko->virtnbdbackup==2.36) (43.0.0)
Requirement already satisfied: pynacl>=1.5 in /usr/lib/python3/dist-packages (from paramiko->virtnbdbackup==2.36) (1.5.0)
Requirement already satisfied: cffi>=1.4.1 in /usr/lib/python3/dist-packages (from pynacl>=1.5->paramiko->virtnbdbackup==2.36) (1.17.1)
Requirement already satisfied: pycparser in /usr/lib/python3/dist-packages (from cffi>=1.4.1->pynacl>=1.5->paramiko->virtnbdbackup==2.36) (2.22)
Building wheels for collected packages: virtnbdbackup
  DEPRECATION: Building 'virtnbdbackup' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'virtnbdbackup'. Discussion can be found at https://github.com/pypa/pip/issues/6334
  Building wheel for virtnbdbackup (setup.py) ... done
  Created wheel for virtnbdbackup: filename=virtnbdbackup-2.36-py3-none-any.whl size=107863 sha256=03353929649ad51420d5d1d8b33e9a0badc75adffc0c96148fc20feb0ca0774b
  Stored in directory: /tmp/pip-ephem-wheel-cache-6fzo96l0/wheels/f6/0f/a5/1b6ca271df69577cc12161b095c3250d07f3c457b69bf3a305
Successfully built virtnbdbackup
Installing collected packages: virtnbdbackup
Successfully installed virtnbdbackup-2.36
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager, possibly rendering your system unusable. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv. Use the --root-user-action option if you know what you are doing and want to suppress this warning.

root@737e250b4c35:/tmp/virtnbdbackup# virtnbdbackup --version
2.36

I'll test it for a while, and if I don't find issues in a reasonable amount of time, will do the pull request.

If you don't have any observations, feel free to close the discussion ;)

Thank you very much for your time!

[abbbi]

This is to be expected, as Debian has changed how it deals with non packaged python installations, so have other distributors..

Pls consider sponsoring the project,

thanks