Skip to content
Discussion options

You must be logged in to vote

Traced this down to an issue in configuration.py. Didn't affect 4.5.2 but seemed to have caused issues with 4.5.3 and above. Rebuilt configuration.py from the supplied example and no issues showing up during ./upgrade.sh execution. Again appreciate the work in that reply.

Replies: 1 comment 2 replies

Comment options

You must be logged in to vote
2 replies
@uck9
Comment options

@uck9
Comment options

Answer selected by uck9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants