Suggestion - have a file with a list of tool version numbers needed to process shows etc. #245
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: HPR/hpr_generator#245
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As a Gentoo user, the current stable version of Mariadb is 10.6, but the current version being used to dump the database into hpr.sql is 10.11. The latter is available in Gentoo, but is marked with the unstable flag (note - if you are not familiar with Gentoo - this is not an issue, but you need to take action to install the unstable version). I came across this problem, as the database dump from version 10.11 cannot be imported using version 10.6, as it baulks at the first line (complains about '-').
As different janitors will probably be using different distributions, Do you think it would be good to record the version numbers of tools currently used to process shows, and keep the list in the HPR repositories? I guess some tools are much more sensitive to version numbers than others, but we could make this clear in such a list.
I think we are supporting both MySQL and sqlite from the hpr.sql dump. This should only be sqlite.
While we use MySQL on the server, (we should switch to postgres) it should only be sqlite for the hpr_generation
Fair enough - I went through the process of generating the website locally, and used sqlite in the end rather than mySQL. Perhaps we should update the documentation to make it clear that sqlite is the preferred tool, as this appears to remove the problem I had above, and with the scripts in the utils directory it is painless.
See my comment. It should probably be added to the FAQ section somewhere. Any idea where that would fit without cluttering people with too much information ?
Since working on the README and GETTING_STARTED, I now recognise that there is a comment about the SQLite version in the readme. We could simply add a similar comment for MySQL, and be done. There doesn't appear to be any other tools which need to be at particular versions.
So I propose the following: I add a comment to the README.md requiring version MySQL 10.11, IF (and only if) it is decided not to remove reference to MySQL (see #250).
if agreed, we can close this issue.
@paulj please close if done