-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debian 12 Bookworm Support? #27
Comments
We do actually use this code on Debian 12 in production on tile.openstreetmap.de. |
@giggls We are talking about the servers for tile.openstreetmap.de here. ;) They broke after sklearn went into deprecation mode: https://pypi.org/project/sklearn/ The approach with the Debian package is becoming problematic because it requires dependencies that are not provided by Debian. Custom Python packages need a virtualenv and that is not compatible with a Debian installed systemd script. My suggestion here would be to have the setup to create luarocks and pip packages instead and drop the Debian approach. What do you think? |
Ähm if you already knew the problem you should have reported it this way. The problem description here looked like my software is not running on Debian 12 which I can not confirm. The missing sklearn dependency is not a Debian 12 issue but a tltk one. Did I already report this there? I might have. If I understand this correctly Debian does not remove deprecated packages from stable release so I tend to relax here a little bit as tltk is not orphaned AFAIK and did not need sklearn in older versions anyway. If we go for them we would not even need sklearn. |
BTW I think about moving deployment of the python daemon into a podman/docker container rather than a Debian package. As the Debian package in its current form is somewhat broken anyway. |
This is a bad idea imo. Docker is a tool for deployment. It is not a replacement for proper installation procedures. Leave the decision if somebody wants to use docker or not to the user. |
Debian 12 installs scikit-learn when installing the python3-sklearn package:
That's why |
There is no replacement as far as I know. Deprecating tltk would mean deprecating Thai language support. This said I do not consider tltk deprecated. Latest release is from may. https://pypi.org/project/tltk/ |
A proper build container is arguably better than a broken Debian package. I know that the cleanest way would be to have all the needed Python modules as Debian packages instead of using pip. |
Pip is fine, no problem with that from my side. The fix seems available and a simple one liner https://github.com/attapol/tltk/pull/8/files let's hope... |
This tltk repo is obviously not where the development happens (issues filed there seem to be ignored). |
The dependency problem seems to be fixed with the release of tltk 1.7 which switched from sklearn to scikit-learn. |
Nice! |
1.8 seems to be the latest release |
OK, closing this as sklearn is now gone with release 1.2.0 |
Thank you for the detailed instructions for Debian 11: https://github.com/giggls/osml10n/blob/master/INSTALL.md.
I have tested this for Debian 12 (Bookworm). Install on Debian 11 and update to Debian 12 is fine.
The first part worked fine in a new install, too:
But then I get into trouble
PIP
pip install
is no longer possible because of https://peps.python.org/pep-0668/Virtual environment
First I tried it with a virtual environment. Then I ran into the problems described here:
attapol/tltk#7
--break-system-packages
With the parameter
--break-system-packages
I could install everything. There were warnings.Debian Pakete
Then I created the Debian packages and get the message
Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 145.
Line 145 of the file
/usr/bin/deb-systemd-invoke
is the one in this if-statement:This is my whole file
/usr/bin/deb-systemd-invoke
.sudo journalctl -u osml10n
looks like this:Are you using this repo under Debian 12 Bookworm? Am I doing something wrong? Which procedure do you recommend?
Could it be that I have a similar problem as in #25
The text was updated successfully, but these errors were encountered: