← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
Time | Nick | Message |
---|---|---|
05:30 | Joubu | mtj: around? |
05:30 | koha-staging no longer have nightly build for master? | |
05:31 | mtj: last notif on koha-bots was on 2023-07-30 - "Koha 04'master' packages pushed to 08'koha-staging' repo 03(2fd6625a)" | |
07:56 | fridolin joined #koha | |
07:56 | fridolin | yellouw |
07:59 | cait joined #koha | |
08:01 | lds joined #koha | |
08:02 | cait1 joined #koha | |
08:03 | cait1 | Joubu: Weblate is not coming up for me this morning - browser is loading endlessly |
08:03 | and good moring all | |
08:04 | fridolin | weblate means "web is late" XD |
08:06 | cait1 | lol |
08:07 | Joubu | same for me |
08:08 | weblate's maintainer submitted a possible fix | |
08:08 | the dev docker image does not contain it yet | |
08:09 | cait | ok |
08:09 | Joubu | there is nothing I can do, postgres is not processing some speficic SELECTs fast enough |
08:09 | there are 5 in the queue, and they take ~30s-2min each | |
08:09 | cait | I am trying to load the page for the manual and it's not coming up |
08:10 | let's hope we can get the fix soon | |
08:10 | it's strange because the test system was so super fast | |
08:10 | maybe becuase it didn#t havee all the data? | |
08:10 | Joubu | yes |
08:11 | there are 15M entries in a table, and the query is not good | |
08:11 | https://github.com/WeblateOrg/[…]discussions/10723 | |
08:20 | the docker image has been updated, I will upgrade weblate | |
08:23 | done | |
08:25 | did-g[m]: yop | |
08:36 | krimsonkharne[m] | morning all |
08:59 | cait | Joubu: I'll give it another go |
08:59 | currently, it's super fast again | |
08:59 | keepig fingers crossed! | |
08:59 | Joubu++ | |
08:59 | weblate_community++ | |
09:10 | Joubu: it's a dream compared to before | |
09:11 | Annelisterman[m]: try Weblate again :) | |
09:11 | ashimema | nice one |
09:12 | Joubu | the problem is that (I think) the problematic queries come from background tasks |
09:13 | so it could happen again randomly | |
09:14 | https://snipboard.io/NEQSh7.jpg - peaks are way lower however! | |
09:21 | cait1 joined #koha | |
09:35 | cait1 joined #koha | |
09:38 | alexted[m] | hi |
09:38 | I need to import several Marc records into a new (empty) installation of Koha (Stage MARC records for import>Manage staged MARC records). | |
09:38 | Is there a way to keep the same biblionumber, biblioitemnumber and itemnumber as the imported records? From an import test I saw that Koha starts numbering everything from 1. Thanks! | |
09:38 | cait1 | not really |
09:39 | well ther eis no configuration switch or similar | |
09:39 | you could set the counter in the database manually, but if your improt contains a record that has been deleted since, it won't work and get out of sync | |
09:39 | hm and it would also only work if we can assume that the records sequence is by biblionumber and they are also imported in that sequence | |
09:40 | alexted[m] | cait1: hi, thanks! |
09:44 | I have this need (of keeping the same biblionumber) because I also have numerous record Marc Serials with related Subscriptions connected | |
09:45 | and other internal links between records | |
09:53 | cait joined #koha | |
09:57 | fridolin joined #koha | |
10:04 | magnuse | alexted[m]: are the records in Koha already? if so you could perhaps export all the relevant db tables from the old koha and import them into the new koha. not something i have ever done, though |
10:12 | alexted[m] | magnuse no, the new installation is empty. The problem is that the source tables are from an old version of Koha and have changed a lot compared to the new version I'm using |
10:13 | magnuse | ah, ok |
10:13 | oh, i meant "are the records in an old version of koha or in some other system" :-) | |
10:14 | ashimema | so the records are coming from an old koha.. |
10:14 | magnuse | how old is the old koha? you could still try to copy over the whole database and do an upgrade |
10:14 | ashimema | do you still have that koha around.. know what version it is.. |
10:14 | I'd just upgrade | |
10:16 | alexted[m] | hi, thanks for your suggestions! The records and the table come from the 17.11.02.000 version, and the new version that i have installed is the 22.11.12 version |
10:17 | Annelisterman[m] | <cait> "Anneli Österman: try Weblate..." <- Much better now. Earlier today it just loaded and loaded and loaded. :) |
10:19 | alexted[m] | <magnuse> "oh, i meant "are the records..." <- yes, the records are in an old version of koha :) |
10:24 | magnuse | alexted[m]: 17.11 to 22.11 should not be an impossible upgrade, worth a try i'd say |
10:25 | PedroAmorim[m] | o/ |
10:25 | davidnind++ | |
10:26 | ashimema | that should be a trivial upgrade |
10:27 | I'd run the db update from the command line | |
10:27 | and watch the output | |
10:27 | Koha stops on errors so you can usually spot and fix them manually in the db.. then re-run the db update sript and it'll pick up where it left off. | |
10:28 | alexted[m] | the problem is that koha 17.11 is running on an old server (Centos) that will be discontinued, while the 22.11 version is on a new server (Ubunt/Debiann): updating koha without the Debian package, on Centos, is a nightmare |
10:29 | ashimema | so perhaps install a 17.11 on the new server |
10:29 | dump the old database and load it into the new server | |
10:29 | then run the upgrade on the new server | |
10:30 | https://debian.koha-community.[…]koha/dists/17.11/ | |
10:30 | packages should exist for it still | |
10:32 | Joubu | install 22.11, drop the db, inject your dump, restart_all, run the update DB script |
10:33 | ashimema | doh.. of course.. that would work |
10:34 | headache | |
10:34 | alexted[m] | ashimema: thanks for the suggestion! the problem is that I just installed Koha 22.11 (https://wiki.koha-community.or[…]i/Koha_on_Debian) on the new server, I should uninstall everything and reinstall |
10:34 | ashimema | do what Joubu just said |
10:34 | drop the existing database | |
10:34 | alexted[m] | Joubu: ah, ok! great! |
10:34 | ashimema | and throw your old one in instead |
10:35 | cait1 joined #koha | |
10:36 | alexted[m] | thanks all for the suggesions! only one question: is there any reference guide for update DB script? |
10:37 | fridolin joined #koha | |
10:43 | cait1 | alexted[m]: trust the process :) |
10:44 | it#s all automated | |
10:44 | cait joined #koha | |
10:44 | cait | it will have the old structure, Koha detects the mismatch of application version and database version and starts the update, this here describes it a bit: kohageek.blogspot.com/2015/08/move-old-koha-database-to-new.html |
10:45 | alexted[m] | cait: thanks! I will try :) |
10:46 | cait | struggling with dicsonnects/bad network today, sorry for the constant renumbering of caits... |
10:48 | you can run the database update on command line as described there, or you could restart and it will also come up in the browser | |
10:48 | for a big update teh cli is maybe a bit easier to work with | |
10:49 | alexted[m] | cait: perfect! I'm downloading the old database right now |
10:59 | cait | alexted[m]: out of interest - where are you from? |
10:59 | alexted[m] | cait: italy :) |
10:59 | cait | ah nice :) |
10:59 | Germany | |
11:00 | alexted[m] | :) |
11:17 | oleonard | o/ |
12:30 | cait | oh wow, from all green to totally broken? |
12:37 | magnuse | "Error while executing command: no such element: Unable to locate element: //*[@id="password"] at /usr/share/perl5/Selenium/Remote/Driver.pm line 411." ? |
12:38 | cait | yeah, right now I am not sure waht caused this |
12:39 | I was hoping to push some more today, but not so sure now | |
12:40 | ashimema, PedroAmorim[m] around? | |
12:40 | PedroAmorim[m] | + |
12:40 | cait | do we have abug for the fail of the erm sushi tests? |
12:40 | https://jenkins.koha-community[…]Build/testReport/ | |
12:41 | PedroAmorim[m] | I'm not entirely sure, had a chat with Matt yesterday about it I think he's on it |
12:41 | cait | any ETA for the patches? :) |
12:42 | https://paste.koha-community.org/34536 | |
12:43 | PedroAmorim[m] | I don't know, there are at least 2 things happening, I believe there's a new 'audited' field coming from the sushi response that needs to be added to our REST API, and there's the 'migrations' thing Joubu mentioned, possibly others. Long story short, it seems the SUSHI response is now different and causing issues. |
12:44 | I'm not actively looking into it after my chat with Matt yesterday, more than one person looking at this would be counter productive | |
12:44 | unless advised otherwise | |
12:45 | cait | yeah, I am trying not to push things while tests are failing - trying to figure out what to do |
12:46 | maybe you can tell him that this shoudl have some priority | |
12:46 | and we should have a bug filed | |
12:47 | also D11 is not even tellin gme waht is failing... that doesn't look great | |
12:52 | Joubu | selenium failure is coming from bug 35070 - I let a note this morning with the "additional_work_needed" flag, and jajm added a patch there |
12:52 | huginn` | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=35070 normal, P5 - low, ---, julian.maurice, Pushed to master , Koha plugins implementing "background_jobs" hook can't provide view template |
12:53 | cait | oh thanks, i had missed the note |
12:54 | so let's see if we can fix D11 a bit | |
12:59 | jajm++ Joubu++ # taking care of that one quickly | |
13:03 | at least passing locally now, going to push | |
13:04 | ashimema | Matt is off ill today |
13:04 | so it won't happen today | |
13:04 | cait | thanks |
13:04 | I'll push a few bugs and the fix for the D11 one, hoping we will get to a bit of a better state with that already | |
13:05 | ashimema | the sushi stuff is very contained.. I wouldn't let it stop you pushing unrelated stuff. |
13:05 | cait | trying to get D11 back from failed first |
13:07 | but I think you are right and knowing the response has changes is also good info | |
13:08 | Joubu | ashimema: the E2E tests (selenium and cypress) are not run when the other tests are failing |
13:09 | cait | pushed |
13:11 | fridolin joined #koha | |
13:19 | cait | Joubu: what is E2E? |
13:19 | or what does it stand for? | |
13:30 | Joubu | end-to-end |
13:30 | cait | ah, ok, that was kind of obvious |
13:37 | I am testing some patches, but will wait with pushing | |
13:44 | cait1 joined #koha | |
13:58 | oleonard | cait++ |
14:13 | Dyrcona joined #koha | |
14:14 | cait1 | D11 is still failing, but not exploding anymore, the erm tests and the known recurring selenium tests failing |
14:34 | marie-luce joined #koha | |
14:38 | magnuse | is https://git.koha-community.org[…]docs/LEEME.Debian still relevant and up to date? pushed 12 years ago, not changed since |
14:40 | cait1 | possibly not? |
14:47 | ashimema: still around? | |
14:49 | lukeg joined #koha | |
14:51 | oleonard | Hi lukeg |
14:54 | cait1 | time to call it a day - have a nice weekend all! |
14:58 | alexted[m] | <Joubu> "install 22.11, drop the db..." <- I just finished the suggested procedure: everything seems to have gone well, I'll do a few more checks, but everything seems ok! Thanks again to everyone for the valuable suggestions |
14:59 | ashimema | hi |
14:59 | magnuse | ashimema: hi |
14:59 | cait1 | alexted[m]: thanks for the feedback :) |
15:01 | magnuse | ashimema: i get this problem when i try to build packages with https://gitlab.com/ptfs-europe/koha-dpkg-docker too: https://gitlab.com/koha-commun[…]docker/-/issues/4 |
15:01 | you don't happen to know if you have found a workaround for it? | |
15:01 | ashimema | erm.. afraid I'm none the wiser |
15:02 | magnuse | i tried le googles, but haven't figured it out yet. one suggestion was to skip dpkg-source, but i can't even figure out where i would do that, it's all a bit too magical yet... |
15:03 | ashimema | I've asked Jake here |
15:03 | hopefully he'll have some clues | |
15:03 | magnuse | coolios! |
15:05 | lukeg | good morning/afternoon/evening! |
15:06 | magnuse | hiya lukeg |
15:06 | ashimema | hmm, I think he might be in a meeting |
15:06 | I'll keep an eye and get back to you magnuse | |
15:07 | magnuse | awesome! |
15:12 | fridolin | nice weekend folks, next week in Marseille whooo |
15:13 | fridolin left #koha | |
15:15 | bag joined #koha | |
15:18 | cait joined #koha | |
15:20 | Joubu | aude_c[m], caroline: https://www.sphinx-doc.org/en/[…]language_filename |
15:22 | in my understanding there is then nothing to do | |
15:23 | caroline | just change it in the conf? |
15:23 | aude_c[m] | Nice. Thank you |
15:23 | So the French manual will know to pick images from the fr file directory? | |
15:24 | Joubu | caroline: if we suffix with .$LANG.png there is nothing to do |
15:24 | caroline | +1 |
15:24 | Joubu | from image.fr.png |
15:24 | aude_c[m] | 👍️ |
15:24 | Joubu | but we could split into different dir (1 per lang) and modify figure_language_filename in the config |
15:25 | ashimema | we lean on community for the translations stuff I'm afraid magnuse |
15:25 | so we don't do that bit outselves in the container | |
15:26 | magnuse | ashimema: the problem here seems to be also with css files that are generated somewhere along the line, and then everything stops because there are uncomitted files in the repo. or so i think. |
15:27 | Joubu | @later tell tcohen Docker_4 has disk space issues |
15:27 | huginn` | Joubu: The operation succeeded. |
16:00 | bag joined #koha | |
16:00 | alexted[m] | <alexted[m]> "I just finished the suggested..." <- I only notice a problem on the database tables. I give an example, but there could be others: the "biblio" table in Koha 17.11 did not have the "subtitle" column and therefore now I find myself having a table with the "subtitle" column empty, even for all the records that in MARC21 have the 245b compiled. Could this be a significant problem? |
16:02 | caroline | Is there a character limit for emails sent to the koha mailing list? I sent a message twice and it still doesn't appear in the archive... https://lists.katipo.co.nz/pub[…]January/date.html |
16:02 | ah there it is... I had to complain ;) | |
16:11 | aude_c[m] | Exciting :) |
16:20 | alexted[m] | <alexted[m]> "I only notice a problem on the..." <- However, I noticed that: if from the Cataloging module I open and Edit a record with the 245b and then save it (without making any changes), the "subtitle" column of the "biblio" table for that record is filled in correctly with the 245b already present in the record . Is there a way to do this batch operation on all records? Thank you! |
16:21 | caroline | alexted[m], you can use the BatchRebuildBiblioTables script |
16:21 | misc/batchRebuildBiblioTables.pl | |
16:24 | alexted[m] | caroline: thanks caroline! :) |
16:24 | do I have to run it from the command line correct? | |
16:24 | caroline | yes |
16:27 | alexted[m] | caroline: thanks! :) |
16:27 | do you suggest running batchRebuildItemsTables.pl as well? | |
16:27 | caroline | If you made changes in the mapping of item fields, then yes. Otherwise it's not necessary |
16:28 | One thing I'm not sure about is the effect of running this in production while operations are ongoing. I always run it at night on production systems just in case | |
16:30 | alexted[m] | caroline: Thanks for the warning :) |
16:30 | caroline: ok! | |
16:30 | caroline | np :) |
16:30 | alexted[m] | just one more question: is there a script for authority tables too? |
16:31 | caroline | the auth_header table doesn't have mappings to marc afaik |
16:34 | alexted[m] | ok! Thanks again for the valuable advice! Have a nice day! :) |
16:34 | caroline | you too! good luck! |
16:34 | alexted[m] | thanks! :) |
16:50 | cait | caroline: just saw the email \o/ |
16:52 | caroline: the newsletter one - so the subscription worked :) | |
16:52 | caroline | yay! |
19:12 | caroline_catlady joined #koha | |
20:17 | caroline_catlady joined #koha | |
20:30 | lukeg joined #koha | |
22:26 | lukeg joined #koha | |
22:44 | dpk joined #koha |
← Previous day | Today | Next day → | Search | Index