← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 00:06 | cait1 joined #koha | |
| 00:44 | dpk__ joined #koha | |
| 02:29 | mtj | paulderscheid[m]++ many thanks for the set_arch() patch 🍻 |
| 02:31 | tcohen: oops, arm64-runner fixed | |
| 10:35 | paulderscheid[m] | Was a Team effort ;) |
| 10:36 | cait joined #koha | |
| 15:43 | bag joined #koha | |
| 17:18 | magnuse_ joined #koha | |
| 17:48 | Col joined #koha | |
| 17:51 | Col | Hello, I am making some progress with moving Koha 3.16 to the latest version, but I am running into an issue with the schema update. The error is related to an invalid Datetime and screenshot can be found here: https://imgur.com/a/iWYIXuL |
| 17:52 | I did some searching on the listserv archives but I wasn't able to find anything that resembles it. I looked at adding an sql mode to allow invalid dates but didn't have any luck. Has anyone seen something like this before during their schema updates> | |
| 19:52 | I made some further progress, I commented out three routines that threw errors from the updatedatabase.pl file, specifically 3.19.00.038, 3.23.00.041,16.06.00.012. Everything else including the zebra index rebuild was successful. The server is working on the newest version and it seems our data is there. I am not really sure how to check if there will be lingering errors due to bypassing those | |
| 19:52 | routines. Log viewer? |
← Previous day | Today | Next day → | Search | Index