← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
Time | Nick | Message |
---|---|---|
00:08 | schnydszch joined #koha | |
04:51 | lmstrand joined #koha | |
04:56 | schnydszch joined #koha | |
06:48 | reiveune joined #koha | |
06:48 | reiveune | hello |
07:06 | thibaud_g joined #koha | |
07:21 | magnuse joined #koha | |
08:00 | cait joined #koha | |
08:04 | cait1 joined #koha | |
08:26 | cait1 | good morning all! |
08:33 | schnydszch joined #koha | |
09:13 | ashimema | morning |
09:25 | PedroAmorim[m] | \o |
09:26 | * cait1 | waves |
09:27 | cait | about to push some easier patches today - I'll go chronologically soon, but still practicing :) |
09:27 | ashimema | nice one |
09:43 | cait | working on the master branch feels SO weird |
09:51 | ashimema | hehe |
09:51 | it really does | |
09:52 | I set myself some extra safeguards when i was doing it | |
09:52 | though I can't entirely remember how I did it | |
09:53 | I think I had two repo's set.. 'origin' which I set the read only http url and 'upstream' which i set to the keyed push url | |
09:53 | then I tracked origin | |
09:54 | so pull all worked fine as is.. but for push I had to explicitly state 'upstream'.. and I also stuck a password on it somehow at my end | |
09:54 | basically.. it acted as an 'are you sure.. are you sure your sure' mechanism | |
09:54 | cait | yep, I set it up like that yesterday, Joubu had pointed it out |
09:54 | well not the password, but a separate remote to push | |
10:01 | ashimema | it's nice |
10:02 | keeps it all very clean in your mind | |
10:25 | cait | hm I pushed, a git fetch origin git status now shows "up to date with master" - but gitea is not showing the commits |
10:25 | https://git.bsz-bw.de/koha/koh[…]r/?ref_type=HEADS | |
10:26 | ok... wrong link | |
10:26 | https://git.koha-community.org[…]its/branch/master | |
10:26 | it did look slightly odd... just nervous here :) | |
10:43 | working on the bugzilla updates | |
11:12 | QA queue 42 > 30 | |
11:13 | ashimema++ # thanks for pointing me in the right direction for the bugzilla scripts | |
11:27 | khall joined #koha | |
11:35 | cait1 joined #koha | |
11:40 | tcohen[m] | Morning |
11:40 | Your push looks great, cait | |
11:43 | paulderscheid[m] | Hi #koha |
11:43 | See cait, you got it! | |
11:45 | I was testing the docker compose files w/ podman yesterday and it basically works, but I got random failures of plack with exit 0 - signal was 9. Any idea tcohen? | |
11:46 | Did you ever run in to something like this? | |
11:47 | As 9 means kill, what could the reasons be? I also ran into killed webpack processes a bunch of times. Does that also sound like a problem w/ resource allocation to you? | |
11:50 | tcohen[m] | Permissions? |
11:51 | paulderscheid[m] | That was the first problem I had, but I didn't run into any actual permission errors anymore when switching to a rootful podman machine. |
11:52 | The koha container basically works, it just kills plack seemingly at random. | |
11:54 | I will document the process in the wiki of setting it up, you can try it sometime if you're interested and can find the time. | |
12:04 | tcohen[m] | I haven't used podman before. But I'm interested in looking at this |
12:04 | magnuse | gah! shibboleth is driving me crazy! logging in at the idp looks ok, the shib logs on the koha server says a session is created and my username is there, but then koha doesn't think there is a session after all. and /Shibboleth.sso/Session also says there is no session either. so maybe the session is started ok, but then terminated immediately? |
12:17 | cait | thanks tcohen and paulderscheid[m] :) |
12:18 | tcohen[m] | Oh, matrix bridge is working today haha. Awesome |
12:20 | ashimema | mm |
12:21 | I'm disappointing that the matrix bridge seems to have become more unreliable again of late.. | |
12:21 | I was really singing it's praises and trying to get people to adopt it.. but alas I'm down about it again now | |
12:23 | cait | tcohen[m]: pm? :) |
12:32 | khall joined #koha | |
12:33 | ashimema | anyone else find git-bz is spitting out a load of crap on apply? |
12:34 | pastebot | "ashimema" at 127.0.0.1 pasted "git-bz noise" (28 lines) at https://paste.koha-community.org/31902 |
12:39 | krimsonkharne[m] | heyyy #koha |
12:41 | cait | hm it didn't for me earlier at least |
12:42 | ashimema | maybe a system change my end |
12:42 | I did update | |
12:52 | krimsonkharne[m] | just tested a git bz apply .... and it responded as usual for me, no "invalid escape sequences"... |
12:52 | ashimema | maybe a python change |
12:56 | cait | tcohen++ |
13:27 | domm[m] | Sorry, slightly complex question (if better suited for mailing list, please tell me): User creates new biblio via SRU from DNB (german national lib). This contains eg the author in 100, and contains the GND-ID in 100$0. Now we already have an auth_record which has that number in 024$a. So it would be preferable to do direct lookup for that number instead of doing a sligthly fuzzy search based on eg author name and date. |
13:27 | As far as I can see from the source code there is no option currently do this? | |
13:28 | cait | I think you are correct--- you are referring to the auto-linking feature? |
13:28 | domm[m] | yes |
13:28 | cait | as Koha doesn#t use $0, I am not sure if there is even a standard index on it |
13:29 | domm[m] | Yeah, it seems that this is not at all possible ATM. |
13:29 | cait | I think you'd probably make some German libraries quite happy with this feature |
13:29 | but itmight work for LOC data too? | |
13:29 | @marc 024 | |
13:29 | huginn` | cait: A standard number or code published on an item which cannot be accommodated in another field (e.g., field 020 (International Standard Book Number), 022 (International Standard Serial Number) , and 027 (Standard Technical Report Number)). The type of standard number or code is identified in the first indicator position or in subfield $2 (Source of number or code). (Repeatable) [a,c, |
13:29 | domm[m] | So I guess we'll do an ad-hoc implementation for that customer and work from that to hopefully get it in a form that can be included in Koha :-) |
13:30 | cait | hm i think that was 024 bibliographic, plz ignore |
13:31 | domm[m] | I think it's more or less the same in auths: https://www.loc.gov/marc/authority/ad024.html |
13:31 | cait | hm so other national libraries probably have their own field (loc at least) |
13:32 | domm[m] | Maybe 035$a would be an even better candidate (but it's repeatable, which makes the direct lookup a bit harder) |
13:32 | cait | I was wondering about hardcoding the lookup... but maybe one could also use something like field: index in a yaml style? |
13:32 | domm[m] | I guess I'll start with hardcoding, and think about putting it into some kind of config later |
13:32 | Dyrcona joined #koha | |
13:32 | cait | makes sense |
13:34 | domm[m] | In that library we also added a nice hack to the auth-tables (actually when we first migrated it) to materialize the value of 024$a into a column (which also has an index, so lookups are very easy and fast) |
13:34 | cait | it looks like I broke D11... |
13:34 | hm yeah, we don't have a koha-to-marc mapping for authorities | |
13:34 | maybe we should have one | |
13:34 | we do map 001 to ean in our installatons usually, for similar reasons | |
13:35 | khall joined #koha | |
13:37 | khall_ joined #koha | |
13:41 | cait | it looks like all "hook" related tests are failing on D11 - also some random and a shibboleth one (35506 35507) |
13:42 | ashimema | i have a meeting to head into shortly.. but can look at those tests after |
14:21 | schnydszch joined #koha | |
14:31 | cait | I need to leave in an hour or so - but will be bakc on it tomorrow morning |
15:37 | cait left #koha | |
15:47 | Dyrcona joined #koha | |
15:48 | tcohen[m] | It is not on D11, it is on the full test suite |
15:49 | at least that's what it looks like | |
15:49 | paulderscheid[m] | Hi tcohen, I just added a section on getting koha-testing-docker to work w/ podman if you want to try it out https://wiki.koha-community.or[…]ocker_with_podman. |
15:49 | tcohen[m] | Ok! |
15:49 | paulderscheid[m] | The issue w/ the random -9s was indeed related to memory, increasing the memory in the config file for qemu solved it. |
15:50 | Or rather signal 9s and -1s | |
15:53 | Currently running all tests to check whether something is broken. | |
16:00 | bag joined #koha | |
16:20 | reiveune | bye |
16:22 | reiveune left #koha | |
16:22 | pastebot | "paulderscheid[m]" at 127.0.0.1 pasted "Test results of koha-testing-docker w/ podman" (348 lines) at https://paste.koha-community.org/31929 |
16:23 | paulderscheid[m] | Here are the test results. I have to double check if the setup is correct. Some of those might be false positives. |
17:01 | lukeg joined #koha | |
17:02 | paulderscheid[m] | Noticed that I had a language and some sysprefs enabled, second run already looks better. |
17:04 | PedroAmorim[m] | anyone able to confirm if koha-translate works on k-t-d? |
17:04 | running koha-translate --install fr-FR says the selected language is not currently available and koha-translate --list --available returns empty | |
17:05 | paulderscheid[m] | Try de-DE, worked for me yesterday. |
17:05 | Ah, didn't read the second half of that sentence. | |
17:05 | That's dubious. | |
17:07 | pastebot | "paulderscheid[m]" at 127.0.0.1 pasted "Test results of koha-testing-docker w/ podman, second run w/ no additional language installed and default sysprefs" (352 lines) at https://paste.koha-community.org/31934 |
17:08 | paulderscheid[m] | Second run looks eerily similar. |
17:09 | That's odd, koha-translate -l -a returns everything for me. | |
17:10 | PedroAmorim[m] | thanks Paul, I probably need to pull ktd |
17:10 | tcohen[m] | You need --dev |
17:19 | JasonGreene[m] | hello all. is there a manual page that shows how the replace the upper left KOHA pic on the Library user page? |
17:21 | that one | |
17:21 | * JasonGreene[m] | uploaded an image: (24KiB) < https://matrix.org/_matrix/med[…]DuSn/koha-pic.PNG > |
17:25 | paulderscheid[m] | I just noticed that my guide relies on an old version of koha-testing-docker (65 commits behind) |
17:25 | Will update | |
17:29 | Alright, seems to make no difference | |
18:16 | Jason Greene you still there? | |
18:16 | JasonGreene[m] | yes |
18:17 | Dyrcona joined #koha | |
18:17 | paulderscheid[m] | Sorry, didn't want to ignore you there, was just doing something. |
18:17 | What version of koha are you running? | |
18:17 | JasonGreene[m] | 21 |
18:17 | i thnk | |
18:17 | paulderscheid[m] | 21.05 or 21.11? |
18:17 | Should show up in the lower right corner of the staff interface. | |
18:17 | JasonGreene[m] | nope... Koha 23.05.04 |
18:18 | paulderscheid[m] | Ok |
18:18 | Let's take a look | |
18:22 | The logo is set by css, specifically this line: background: transparent url("../images/koha-green-logo.svg") no-repeat scroll 0%; | |
18:23 | What you could do is to override that line in OPACUserCSS with something like this: `#logo { background: transparent url("../images/<YOUR_LOGO_URL>.<YOUR_FORMAT>") no-repeat scroll 0%; }` | |
18:24 | You can also use urls to your resources if they live somewhere else for example `https://<YOUR_DOMAIN>.<TLD>/<YOUR_IMAGE>.<YOUR_FORMAT>` | |
18:25 | JasonGreene[m] | ok, thanks. I'm not a code writer so I'll give that a try, where is that file? |
18:27 | paulderscheid[m] | It's not a file but rather a system preference. You'll find it under Administration -> System Preferences -> OPAC -> OPACUserCSS. |
18:28 | There you can just hit 'Click to edit' and enter this line `#logo { background: transparent url("<YOUR_URL>") no-repeat scroll 0%; }` | |
18:29 | Then you just have to replace <YOUR_URL> with a valid URL that points to an image. | |
18:29 | Have I made that clear enough? Or should I explain a bit more? | |
18:30 | JasonGreene[m] | yes, I hope, I'll look ... thanks |
18:30 | paulderscheid[m] | Anytime :D |
18:35 | dcook_ joined #koha | |
18:37 | JasonGreene[m] | in the <YOUR_URL> can I use a local KOHA server .gif pic something like "/etc/apache2/sites-enabled/logo.gif> |
18:37 | paulderscheid[m] | It has to be accessible from the OPAC so this will not work. |
18:38 | You wouldn't want users to access your server configuration under /etc from the web, right :D | |
18:38 | JasonGreene[m] | or put it in "../images" folder |
18:38 | paulderscheid[m] | That will work |
18:38 | That should be where the koha-green-logo.svg lives. | |
18:39 | JasonGreene[m] | ok, I'll look |
18:39 | paulderscheid[m] | This is the path to that directory: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/images |
18:40 | JasonGreene[m] | maybe just leave the code and rename the files |
18:41 | paulderscheid[m] | Nah, you can do it. Just add the file and adjust the path to "../images/<YOUR_FILENAME>". |
18:41 | JasonGreene[m] | :-) |
18:41 | paulderscheid[m] | Hereby I mean the path in the line of css. |
18:42 | JasonGreene[m] | ok, I'll do it and let you know how it works |
18:42 | paulderscheid[m] | Great! |
18:42 | JasonGreene[m] | Thanks again |
18:43 | paulderscheid[m] | You're welcome |
18:49 | davidnind | if you replace the Koha logo file with your own on the file system, it will most probably be overwritten with upgrades - so it is best to either have a separate file for your logo, or use a URL to your organisation's logo (for example, on the main site) |
18:49 | paulderscheid++ | |
19:03 | fridolin joined #koha | |
19:35 | caroline | paulderscheid++ |
19:38 | fridolin left #koha | |
21:03 | khall joined #koha | |
21:04 | khall_ joined #koha | |
21:10 | JasonGreene[m] | I made the change and the area went blank and clickable... then I took it out and it stayed blank |
21:17 | cait joined #koha | |
21:19 | JasonGreene[m] | I even tried changing the name of the pics after I removed the CSS . it stays blank |
21:21 | gotta leave work... I'll pick up later. thanks for the help | |
21:38 | zb joined #koha | |
22:32 | cait joined #koha | |
22:39 | cait joined #koha | |
23:08 | cait joined #koha | |
23:29 | lukeg joined #koha |
← Previous day | Today | Next day → | Search | Index