Tranquil IT Forum

Hello,
I updated everything to WAPT 2.7.
I have one server and four remote repositories.
The server updated without any problems.

However, three out of the four repositories encountered an error during the update, with a missing Python file.
I copied the file from the working repository, and everything is back to normal, but I wanted to keep you informed of the problem:

Oct 02 15:22:53 xxx-wapt-repo systemd[1]: waptservice.service: Deactivated successfully.
Oct 02 15:22:53 xxx-wapt-repo waptservice[542]: ModuleNotFoundError: No module named 'six'
Oct 02 15:22:53 xxx-wapt-repo waptservice[542]: ModuleNotFoundError: No module named 'six'
Oct 02 15:22:53 xxx-wapt-repo waptservice[542]: import six
Oct 02 15:22:53 xxx-wapt-repo waptservice[542]: File "/opt/wapt/lib/python3.11/site-packages/pam/__internals.py", line 2, in
Oct 02 15:22:53 xxx-wapt-repo waptservice[542]: from .__internals import PAM_ACCT_EXPIRED
Oct 02 15:22:53 xxx-wapt-repo waptservice[542]: File "/opt/wapt/lib/python3.11/site-packages/pam/__init__.py", line 9, in
Oct 02 15:22:53 xxx-wapt-repo waptservice[542]: File "
Oct 02 15:22:53 xxx-wapt-repo waptservice[542]: Traceback (most recent call last):

The missing file was therefore this one: /opt/wapt/lib/python3.11/site-packages/six.py

All the repositories are similar; they are Debian Bookworm. I can't really explain what happened during the update; no error occurred, it was just when the service was launched.

Feel free to ask if you have any other questions.

Have a good day,
Guillaume

Hi Guillaume,

the python-pam module removed its explicit dependency declaration for module six (the historical Python 2/Python 3 compatibility module) from its pyproject.toml file in version 2.0.2. Therefore, module six was removed from the requirements.txt file during dependency calculation since no packages required it anymore. This was fixed two weeks ago with version 2.1.0.

In short, there was a mistake in the python-pam project's pyproject.toml file, but I really need to figure out why it wasn't caught during integration testing.

Best regards,

Denis