← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 00:00 | dcook | mtj: According to the publicly available information, those packages should be available for a arm64 system |
| 00:01 | I'm wondering if some scripts are just adding to amd64 and i386 for the "koha" repo? | |
| 00:01 | Maybe koha-staging uses something slightly different? | |
| 00:01 | Huh.. | |
| 00:01 | https://debian.koha-community.[…]onf/distributions | |
| 00:02 | That has jammy while the "koha" one doesn't.. | |
| 00:02 | https://debian.koha-community.[…]onf/distributions | |
| 00:02 | I don't think jammy needs anything special though? | |
| 00:02 | Oh I should double check my versions.. | |
| 00:02 | I'm using focal in any case.. | |
| 00:03 | Ah wait "koha" does have jammy too anyway | |
| 00:03 | But I don't think those components actually have anything in them.. | |
| 00:05 | mtj | hmm, i only have access to a deb11 arm64 stm |
| 00:06 | dcook | mtj: Could you just to a 'reprepro' list and let me know what you see on the official apt repo? |
| 00:07 | I might actually just quickly check koha-staging vs koha.. | |
| 00:07 | Yeah so koha-common looks to be installable from koha-staging but not koha | |
| 00:08 | I think some packages just haven't been added for certain architectures in "koha" | |
| 00:08 | Despite being built for "all" | |
| 00:13 | mtj | dcook: ahh, will fix in 5 |
| 00:14 | dcook | mtj: Legend! |
| 00:19 | aleisha joined #koha | |
| 00:20 | aleisha | hey all we're getting a build error that we haven't seen before, hoping some of you can help. it's toward the end of the build-git-snapshot output |
| 00:20 | xsltproc --output /build/koha-22.11.01.000+xxx+20230117170120.52134d4b/debian/tmp/debian/tmp_docbook/ \ | |
| 00:20 | /usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl \ | |
| 00:20 | debian/docs/*.xml | |
| 00:20 | warning: failed to load external entity "/usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl" | |
| 00:20 | cannot parse /usr/share/xml/docbook/stylesheet/docbook-xsl-ns/manpages/docbook.xsl | |
| 00:20 | debian/rules:17: recipe for target 'override_dh_auto_install' failed | |
| 00:21 | make[1]: *** [override_dh_auto_install] Error 4 | |
| 00:21 | anyone seen something like this before? | |
| 00:24 | dcook | aleisha: Yeah I had that the other day |
| 00:24 | The control file in master hasn't been updated from control.in | |
| 00:24 | What I did was just pulled out the control file from the 22.11.01 packages and put that into my git | |
| 00:26 | aleisha | ah interesting. thank you dcook i'll give that a go! |
| 00:27 | dcook | aleisha: No worries. It had me scratching my head for a bit too until I sussed it out! |
| 00:27 | aleisha | any chance it'll be fixed up in the next minor points? |
| 00:27 | dcook | mtj: How are you going with those packages? |
| 00:28 | aleisha: Not sure. I think I opened a ticket or emailed mtj about it. | |
| 00:29 | He just needs to commit the built debian/control and then it should be all good | |
| 00:30 | Looks like I emailed last week | |
| 00:30 | aleisha | looks like possibly related to bug 27315? |
| 00:30 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=27315 minor, P5 - low, ---, a.roussos, Pushed to oldstable , The man pages for the command line utilities do not display properly |
| 00:31 | dcook | aleisha: Yeah I think that's the one |
| 00:35 | mtj | dcook: might be fixed now |
| 00:35 | dcook | mtj: Almost. still getting the error but only for libcgi-compile-perl |
| 00:35 | koha-common : Depends: libcgi-compile-perl (>= 0.25) but it is not going to be installed or | |
| 00:35 | libcgi-compile-perl (< 0.24) but it is not going to be installed | |
| 00:36 | mtj | dcook: what koha version? |
| 00:36 | dcook | 21.11 |
| 00:38 | Ah yeah when I look at https://debian.koha-community.[…]11/Contents-arm64 I can't see it | |
| 00:39 | mtj | https://packages.ubuntu.com/ja[…]bcgi-compile-perl |
| 00:39 | dcook | I'm using focal heh |
| 00:39 | Whichi s .24-1 | |
| 00:39 | mtj | hmm, so theres a problem with libcgi-compile-perl (= 0.24) |
| 00:40 | dcook | I've got 0.25-1 installed for focal on amd64 |
| 00:40 | From the koha apt repo | |
| 00:43 | mtj | dcook: try again |
| 00:44 | i get a clean install on deb11 | |
| 00:45 | aleisha | btw thanks dcook , that was exactly the fix :) appreciate it |
| 00:49 | dcook | mtj: The simulation is looking good. I'll try a real install now. |
| 00:50 | @later tell aleisha I'm glad I was able to save you some pain! | |
| 00:50 | huginn | dcook: The operation succeeded. |
| 00:52 | pastebot | "mtj" at 127.0.0.1 pasted "reprepro list 21.11" (311 lines) at https://paste.koha-community.org/423 |
| 00:52 | mtj | dcook: ^ |
| 00:52 | dcook | Thanks, mtj :D |
| 00:53 | Ok looks like everything installed with no errors.. | |
| 00:55 | Thanks, mtj. Really appreciate you updating the repo :). | |
| 00:55 | mtj | ill set up a gitlab-ci job to test the packages on arm64 |
| 00:55 | dcook | <3 |
| 00:56 | mtj | dcook: np |
| 01:01 | dcook | I'm handing the server off to someone else now to complete things but it's all looking good to me :) |
| 01:05 | mtj | dcook: whats the spec of arm64 server? |
| 01:06 | dcook | mtj: I'm not sure what it's going to be. I was just testing the initial installability as I was told folks weren't able to get it to work. |
| 01:06 | But it's AWS Graviton | |
| 01:07 | mtj | ah yep |
| 01:07 | dcook | I think you've already got it working there with that Docker image you mentioned before? |
| 01:08 | mtj | yeah, im using an aws instance for building/testing stuff |
| 01:09 | a smaller 2cpu/4gb one | |
| 01:14 | dcook | I think this testing one is similar to that |
| 01:14 | But the actual one will probably be quite a bit higher specced | |
| 01:14 | I can report back later to say how it all goes :) | |
| 02:38 | mtj | cheers dcook, i think a few people are interested in aws-graviton |
| 02:38 | dcook | mtj: Makes sense! I've been meaning to try it with Koha for a while but just hadn't gotten around to it |
| 02:39 | I think all of my ARM work has been with mobile phones so far.. | |
| 03:04 | alexbuckley joined #koha | |
| 04:17 | davidnind | dcook++ |
| 04:35 | dcook | Thanks, davidnind. I thought that was one of the fastest patch to report responses around hehe |
| 04:40 | @karma | |
| 04:40 | huginn | dcook: Highest karma: "Joubu" (1152), "cait" (967), and "ashimema" (794). Lowest karma: "-" (-78), "failed" (-52), and "ie" (-40). You (dcook) are ranked 23 out of 1220. |
| 04:41 | dcook | davidnind++ |
| 05:32 | semarie joined #koha | |
| 05:42 | Oak joined #koha | |
| 07:02 | Joubu | mtj: how big is Docker_4? |
| 07:02 | "koha_es_1 exited with code 137" | |
| 07:03 | on Koha_22.05_D11 runs 135 and 137 (at least) | |
| 07:03 | mtj | hi Joubu, i think its a 4gb box |
| 07:04 | Joubu | Docker_3 is back, nice! |
| 07:05 | We need another node where ES jobs can run. At the moment it seems that only Docker_3 is reliable.. :-/ | |
| 07:06 | mtj | meh, looks like 4gb is not enough :/ |
| 07:07 | Joubu | do you confirm that 3 is bigger? |
| 07:08 | ashimema | Man either of you walk one of my colleagues through adding a node today? |
| 07:09 | Can.. | |
| 07:14 | See PM Joubu | |
| 07:23 | mtj | Joubu: node3 has 20gb ram, but alse uses a 10gb tmpfs |
| 07:23 | alos | |
| 07:23 | also | |
| 07:24 | ashimema | 20gb ram.. blimey |
| 07:24 | That is a big box | |
| 07:24 | reiveune joined #koha | |
| 07:25 | mtj | much bigger than it needs to be |
| 07:25 | reiveune | hello |
| 07:25 | ashimema | Why does it need that much? |
| 07:25 | What would you suggest to be sensible specs for running the full builds mtj? | |
| 07:26 | A box that size would be a hard sell here.. we don't go that big for most production machines | |
| 07:27 | mtj | hi reiveune :) |
| 07:27 | Joubu | min 8G RAM, 50G ROM, 2 cores |
| 07:27 | this is docker_7 | |
| 07:27 | mtj | ashimema: probably 6 gigs would be enough to run the full build |
| 07:28 | ashimema | Ta |
| 07:29 | I'll get onto infra today.. get them to get something set up | |
| 07:30 | mtj | its possible to split the full build into smaller parts - core/es/selenium |
| 07:31 | ...so, another option could be to run partial builds, on all nodes | |
| 07:33 | this would remove the need for a monster node | |
| 07:37 | Joubu | I don't think it's possible |
| 07:37 | technically it is, but I don't think it's a good idea | |
| 07:37 | the full run is the real way to test everything IMO | |
| 07:48 | cait joined #koha | |
| 07:51 | thibaud_g joined #koha | |
| 07:55 | alex_ joined #koha | |
| 07:55 | alex_ | Bonjour |
| 08:08 | thibaud_g | hello \o/ |
| 08:25 | magnuse_ joined #koha | |
| 08:39 | magnuse__ joined #koha | |
| 08:54 | mtj | Joubu: i agree with you.. i just offer another solution to work with smaller jenkins nodes :) |
| 09:00 | hi alex_, thibaud_g | |
| 09:06 | ashimema: im about for a while if yall need a hand with the jenkins node | |
| 09:18 | ashimema | coolios |
| 09:19 | we have our usual morning meeting at the moment, but I'll try to get Jake to take a look asap | |
| 09:26 | perplexedtheta | o/ morning ashimema and mtj |
| 09:27 | mtj | hi perplexedtheta |
| 09:27 | perplexedtheta | I can get an 8GB node up and ready shortly |
| 09:28 | ashimema | perplexedtheta++ |
| 09:35 | Joubu | perplexedtheta: I sent you some commands in PM |
| 09:36 | ashimema | thanks Joubu |
| 10:01 | Joubu | @later tell tcohen I've lost my ssh access to the jenkins server, certainly since the move to portainer, can you add me back there please? |
| 10:01 | huginn | Joubu: The operation succeeded. |
| 10:04 | alex_ joined #koha | |
| 10:28 | Joubu | @later tell tcohen forget that, Martin added me! |
| 10:28 | huginn | Joubu: The operation succeeded. |
| 11:21 | oleonard | Hi #koha |
| 11:25 | alex_ joined #koha | |
| 11:29 | Joubu | mtj: Are you planning to work on the "'Simplify' KTD repo to a single" issues you opened in ktd? If so, what's the plan? |
| 11:31 | mtj | Joubu: i have a working repo, that uses a single .tt file to create all Dockerfiles |
| 11:33 | i think the next step would be to flatten/merge all branches, to a single KTD branch | |
| 11:33 | ..if so, we would need to decide on a dir/file structure under ./dists | |
| 11:38 | Joubu | mtj: The last 2 days I have been playing with jenkins, and master builds. If we had only 1 branch, I would have broken the stable builds (or I should have adjusted their config, but it's painful regarding the number of jobs we have) |
| 11:38 | I am not against the idea, but we need to keep in mind that sometimes we need flexibility | |
| 11:41 | mtj | Joubu: hmm, yes, thats another big problem we have with KTD images |
| 11:42 | ..we need to seperate the images that jenkins uses, and the images that developers use | |
| 11:43 | Joubu | another thing: sometimes we need to cpan install a specific module, for master, because it's pushed to Koha master branch but the module is module packaged yet |
| 11:43 | here we would install it for all branches then? | |
| 11:45 | mtj | would be easy to make an exception for a Dockerfile that needed a customized file |
| 11:47 | you could have a IF block in the .tt file | |
| 11:48 | ..or if needed, just have the .tt file skip generating a Dockerfile, for that problematic image | |
| 11:52 | i was thinking of following debian, and have both 'unstable' and 'testing' docker images | |
| 11:53 | currently we have just 'testing' images, that CI and devs both share | |
| 11:54 | not great | |
| 11:55 | the solution could be to have ci/jenkins use another set of 'unstable' images | |
| 11:56 | when the CI build passes with that image - we know that its safe to update 'testing' with that image | |
| 12:01 | then, we can be sure that 'testing' images are tested as functional, for developers to use | |
| 12:06 | Joubu | when do we have unstable images? |
| 12:06 | I don't think it happens very often | |
| 12:19 | mtj | Joubu: it doesnt happen too often, but it does happen |
| 12:20 | Joubu | mtj, ashimema: I've tried jenkins's Pipeline plugin: https://jenkins.koha-community[…]ob/test_pipeline/ |
| 12:20 | ashimema | cool |
| 12:20 | will take a look once I'm out of my meeting | |
| 12:20 | Joubu | The idea is: run full run, if succeeds run D10,D12 (etc but only those 2 for now), at then end run CPAN if all is green |
| 12:21 | mtj | Joubu: and.. its very possible that we break images in the future |
| 12:21 | Joubu | the view is showing D12 is "paused", but actually it's running |
| 12:21 | mtj: us?? break something?! | |
| 12:28 | mtj | 🤓 |
| 12:31 | Joubu: jenkins pipeline is looking great, | |
| 12:35 | Joubu: this 'ktd-arm64' repo has a single branch and template | |
| 12:35 | https://gitlab.com/mjames/ktd-[…]tree/master/dists | |
| 12:35 | https://gitlab.com/mjames/ktd-[…]ter/Dockerfile.tt | |
| 12:36 | this script generates the Dockerfiles... | |
| 12:36 | https://gitlab.com/mjames/ktd-[…]en-dockerfiles.pl | |
| 12:38 | a gitlab-ci.tt file too... | |
| 12:38 | https://gitlab.com/mjames/ktd-[…].gitlab-ci.yml.tt | |
| 12:53 | Oak joined #koha | |
| 13:49 | alex_ joined #koha | |
| 13:59 | magnuse_ joined #koha | |
| 14:05 | magnuse__ joined #koha | |
| 14:34 | Dyrcona joined #koha | |
| 14:35 | lukeg joined #koha | |
| 14:46 | Joubu | bug |
| 14:46 | bug 32650 | |
| 14:46 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=32650 normal, P5 - low, ---, chris, Needs Signoff , Koha/Holds.t is failing randomly |
| 14:46 | Joubu | help jenkins |
| 14:58 | oleonard | Joubu: Any trick to reproducing the failure? |
| 15:01 | Joubu | oleonard: too tedious |
| 15:02 | see the previous failure. Hold id was 996 then 1000, and so we expect [996, 1000] but get [1000, 996] | |
| 15:02 | because perl sort will be alpha, and we need a numeric sort | |
| 15:04 | and this is another one: bug 28670 | |
| 15:04 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=28670 normal, P5 - low, ---, chris, Needs Signoff , api/v1/patrons_holds.t is failing randomly |
| 15:06 | Joubu | and, for those who missed it, I implemented DB persistency in ktd: https://gitlab.com/koha-commun[…]erge_requests/410 |
| 15:11 | and we have a new jenkins node, ptfs-e++ | |
| 15:11 | cait | davidnind: did I miss the meeting? |
| 15:12 | perplexedtheta | o7 happy to contribute the metal! Joubu |
| 15:12 | cait | oh tomorrow! |
| 15:12 | wahanui | tomorrow is the hard part - serials and acq |
| 15:12 | cait | forget tomorrow |
| 15:12 | wahanui | cait: I forgot tomorrow |
| 15:13 | cait | now I kinda regret making them forget tomorrow... |
| 15:23 | oleonard | cait: We can't always put off the hard part until tomorrow! |
| 15:28 | cait | we have this error when placing a hold in 22.11.01: DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Column 'biblionumber' in where clause is ambiguous at /usr/share/koha/lib/Koha/Objects.pm line 394 |
| 15:28 | the hold form doesn't display, but an error 500 and this is in the logs | |
| 15:30 | it's only this line... I am not srue where to look | |
| 15:30 | and it doesn't happen for all records... w ehaven't been able to nail down the difference yet | |
| 15:31 | Joubu | no stacktrace? |
| 15:32 | check koha log, search for the stacktrace there and locate the pl/pm + line number | |
| 15:32 | domm[m] | I also have a weird error (on 22.11.00.001): When an item has no holdingbranch, opac/cgi-bin/opac/opac-detail.pldies with DBIC result _type isn't of the _type Branch at line 682 |
| 15:33 | this seems to be caused by `$item->holding_branch` not working when `$item->holdingbranch` is empty/null (btw, great method names here :-) | |
| 15:33 | Is this a known problem? Should `item->holdingbranch` never be empty? Or should I report a bug? | |
| 15:34 | My workaround currently is to add a few `if $item->holdingbranch` before calling `$item->holding_branch`, but this seems a bit hacky | |
| 15:34 | Joubu | holdingbranch is the DB colum which is actually the library code, holding_branch return the Koha::Library object |
| 15:34 | domm[m] | yeah, I've figured that out by now |
| 15:35 | but if holdingbranch is empty, either _result or _new_from_dbic fails | |
| 15:35 | Joubu | domm[m]: https://paste.koha-community.org/458 |
| 15:35 | this is the correct fix I'd say | |
| 15:36 | domm[m] | ok, I was thinking about something like that, and fixing it there |
| 15:36 | Joubu | but if we assume elsewhere the library should be there it will certainly fail |
| 15:37 | domm[m] | but I was not sure if holdingbranch is allowed to be empty (it seems to be based on DB and UI, but who knows) |
| 15:37 | Joubu | I think it's not supposed to be empty |
| 15:37 | domm[m]: misc/maintenance/search_for_data_inconsistencies.pl | |
| 15:37 | run that | |
| 15:38 | it's the first test there, it's not supposed to be empty. | |
| 15:38 | bug 21011 | |
| 15:38 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=21011 enhancement, P5 - low, ---, jonathan.druart+koha, CLOSED FIXED, Data inconsistencies - items.holdingbranch | items.homebranch |
| 15:38 | domm[m] | It might be empty on purpose, but maybe the librarians misunderstood holdingbranch |
| 15:38 | ok, thanks! | |
| 15:39 | Will discuss this with the librarians, thanks for the feedback! | |
| 15:40 | cait | Joubu: just a 500 page and that is from plack-error-log - what other should we check? |
| 15:42 | plack-opac-error-log dosn't show anything | |
| 15:43 | Joubu | -log ? |
| 15:43 | should be plack-error.log | |
| 15:44 | cait | yeah only that one line |
| 15:46 | Joubu | Don't we have stacktraces in production? |
| 15:46 | cait | no, you can activate it - we do that sometimes for our demo |
| 15:47 | Joubu | how? |
| 15:49 | cait | i have this written down: |
| 15:49 | debian/scripts/koha-plack #environment="deployment"environment="development | |
| 15:49 | well... with line breaks | |
| 15:49 | Joubu | cait: can you recreate on a sandbox? |
| 15:49 | cait | not yet... but we dont see anything unusual about the item or record |
| 15:52 | we have a strack trace now | |
| 15:52 | it's jsut as helpful | |
| 16:02 | reiveune | bye |
| 16:02 | reiveune left #koha | |
| 16:16 | cait | bug 32674 |
| 16:16 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=32674 major, P5 - low, ---, oleonard, NEW , When placing a hold in OPAC page explodes into error 500 |
| 16:22 | Joubu | @later tell lukeg please pick 32269 |
| 16:22 | huginn | Joubu: The operation succeeded. |
| 16:55 | jzairo joined #koha | |
| 17:20 | cait left #koha | |
| 17:38 | bag joined #koha | |
| 18:57 | bag joined #koha | |
| 19:01 | caroline_catlady | lucyvh[m], around? |
| 19:03 | caroline | oh maybe it's too late for her... |
| 19:32 | marie-luce joined #koha | |
| 19:35 | JBoyer joined #koha | |
| 19:58 | fridolin joined #koha | |
| 19:59 | emlam joined #koha | |
| 20:23 | huberto joined #koha | |
| 20:23 | huberto | Hello everyone |
| 21:03 | lukeg joined #koha | |
| 21:17 | mary_ joined #koha | |
| 21:18 | mary_ | Hi I was wondering if anyone had any tips on getting the full title from the MARC record to display in a sql report? |
| 21:29 | caroline | mary_, what do you mean by "the full title"? Do you mean all subfields of 245? |
| 21:30 | mary_ | exactly |
| 21:30 | or at least title and remainder of title | |
| 21:31 | caroline | mary_, well those should be easily acessible in the biblio table, under title and subtitle |
| 21:32 | mary_ | that is what's odd. When I add subtitle nothing appears. |
| 21:33 | cait[m] | is your instalation and old one? |
| 21:33 | which version? | |
| 21:33 | wahanui | which version is thiis? |
| 21:33 | caroline | Ok, I think it might not be mapped to 245$b... it's a newer field (subtitle I mean) and the mapping isn't updated |
| 21:34 | You'll need to do a little bit of work before you can access it | |
| 21:34 | Go to Administration > Koha to MARC mappings | |
| 21:34 | That is where all the mappings live | |
| 21:34 | mary_ | I am attempting and I am on Koha version 22.05.07.000 |
| 21:35 | caroline | Alternatively, if you don't have access to administration and a terminal, you can query the record directly with SQL https://wiki.koha-community.or[…]ibrary#Query_MARC |
| 21:36 | mary_ | Okay on the mapping I see biblio.subtitle245bRemainder of title |
| 21:36 | caroline | ok that's good |
| 21:37 | If you edit the record (click Edit, change nothing and Save), does the subtitle now appear in your report? | |
| 21:39 | mary_ | In the mapping? I do not see an edit on add and remove. Or directly on the record for the item? |
| 21:39 | on=only* | |
| 21:39 | caroline | directly on the record |
| 21:39 | the bibliographic record | |
| 21:41 | mary_ | oddly enough that subtitle is now in the sql report |
| 21:41 | is there a way to do this for all the bib records? | |
| 21:42 | caroline | yes, but you need access to a terminal because it's with a command line |
| 21:42 | you need to run batchRebuildBiblioTables.pl | |
| 21:43 | This will update all the entries in the biblio table with the mappings that you saw in Admin > Koha to MARC | |
| 21:44 | mary_ | okay thank you i will continue on with this tomorrow. You are a treasure thank you for helping me. |
| 21:44 | caroline | I suggest you plan this for the middle of the night if your library is in production, just to make sure the daily operations are not affected |
| 21:44 | mary_ | will do |
| 21:45 | caroline | it was my pleasure! It's not often that we get questions that I can answer here, they are usually more programmer questions :) |
| 21:46 | mary_ | Maybe one day I will evolve to those questions. Thank you again. |
| 21:56 | lukeg | anyone know what is causing Jenkins builds to fail for 22.05 all of the sudden? Im not seeing the problem |
| 22:07 | davidnind | lukeg: I think Joubu and mtj may have been doing stuff last night, so maybe blame them? 🙂 |
| 22:07 | caroline++ | |
| 22:09 | lukeg | davidnind: Thanks. It doesn't appear to be related to something I pushed today. I'll blame Jenkins for now :) |
| 22:55 | mtj | lukeg, the new jenkins node8 seems to have a problem, ive disabled it for now |
| 22:55 | @later tell lukeg: the new jenkins node8 seems to have a problem, ive disabled it for now | |
| 22:55 | huginn | mtj: The operation succeeded. |
← Previous day | Today | Next day → | Search | Index