Time  Nick                 Message
17:17 MichalKohaCZ[m]      Can I ask what I doing wrong, if in Koha Testing Docker  I’ve default credentials to Bugzilla. I created default.env with correct credentials. But if I try to sign bug I see Joe Doe. Thank for help
16:59 huginn               04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26862 minor, P5 - low, ---, katrin.fischer, Needs Signoff , MARC21 530 is missing from staff interface and has no label
16:59 cait                 Maybe someone wants to have fun wih MARC21 530? bug 26862
15:13 ashimema             that's kinda what this CLA stuff all does
15:13 ashimema             indeed
15:12 cait                 I think often you have to pay to have more rights remain... which seems odd
15:00 ashimema             I must admit.. it all feels rather nasty to me.. I'd love to just see far more copyleft
15:00 ashimema             something like that
15:00 ashimema             it's something to do with that stuff.. like profs write stuff.. it then gets published and the publishers get most of the rights.. but the CLA allow some small amount back to the university
14:59 ashimema             if you work in a university, do your staff, or the university itself, retain any rights over the work they produce?
14:58 cait                 very interesting, not sure if we have anything equivalent to this
14:57 * ashimema           uploaded an image: (70KiB) < https://matrix.org/_matrix/media/v3/download/matrix.org/QkhVKKQbyEvwvkfSgcIYmTRz/image.png >
14:57 ashimema             it's probably rather UK centric
14:56 cait                 oh interesting, I was not aware of that plugin, thx for explaining
14:56 ashimema             often used for ILL where they own a licence for lending but that licence may or may not cover lending to a partner library
14:55 ashimema             it looks up what the libraries rights are for lending a resource
14:55 ashimema             Copyright Licensing Agency
14:55 cait                 ashimema: what is a CLA plugin?
14:55 cait                 but just so you know someone else is here :)
14:49 cait                 domm[m]: sorry, not able to help
14:35 * domm[m]            sent a code block: https://matrix.org/_matrix/media/v3/download/matrix.org/APGevvaUqBACsTTXeiFhRYwf
14:34 domm[m]              followed by lots of certificat info
14:34 domm[m]              * ```... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/OsSqgYdpxAWJOHPDMwJCZudq>)
14:33 domm[m]              ```
14:32 domm[m]              now try with open https://sru.k10plus.de/opac-de-627 (which should work according to https://wiki.k10plus.de/display/K10PLUS/SRU)
14:32 * domm[m]            sent a code block: https://matrix.org/_matrix/media/v3/download/matrix.org/chUkuHEmlpGDiEjBbolnzZkp
14:32 domm[m]              I'm quite sure the problem is related to https:
14:29 domm[m]              to a https service?
14:29 domm[m]              hey, on two instances (upgraded to 22.11 not so long ago) we cannot access SRU servers via https / 443. We had this problem a while ago, and then an upgrade of the yaz package fixed it. We're now using `yaz-5.30.3-1` which according to the changelog should handle SSL. But we just get "No result" (which I know we also get when the connection cannot be established). So, to cut to an actual question: Has anybody got a working SRU config for talking
14:12 cait                 login_attempts = 0...
14:10 cait                 even if auth was successful?
14:10 cait                 differnt question... do we have any functionatliy that woudl not permit login?
14:01 ashimema             afraid that doesn't include me
13:59 cait                 anyone with CAS experience around?
13:58 cait                 I'll try to have a look soon
13:58 ashimema             hopefully it now works as expected
13:58 huginn               04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33028 major, P5 - low, ---, thibaud.guillot, Signed Off , Wrongly formatted monetary amounts in circulation rules break scripts and calculations
13:58 wahanui              i guess bug 33028 is almost ready for testing
13:58 cait                 bug 33028
13:58 ashimema             I redid 33028 again for you
13:58 cait                 it'sturns out to be a very Monday'ish Monday today
13:58 cait                 hehe
13:57 * ashimema           forgets what he wanted to ask cait a few hours ago.. lol
13:57 * ashimema           hugs cait
13:57 ashimema             so far so good cait
13:57 ashimema             only seen one today 🙂
13:47 cait                 hopefully only one cait
13:31 magnuse              ¡hola tcohen!
13:31 tcohen               hi magnuse
13:28 magnuse              o/
13:21 tcohen               \o
13:21 MatthewBlenkinsop[m] o/
13:02 magnuse              hehe
12:30 wahanui              i heard cait around was cait cait1 cait2 cait3 cait4 cait5
12:30 ashimema             cait around?
11:44 tcohen               cait++ # bug wrangling
11:11 tcohen               no laters, that's awesome :-D
11:11 ashimema             morning tcohen
11:11 tcohen               hola #koha o/
11:09 magnuse              cait++
10:53 oleonard             Hi tundunf
10:50 tundunf              hi everyone! :)
10:41 ashimema             indeed.. my inbox is overflowing
10:40 oleonard             cait has been doing a lot of bug-wrangling!
10:34 MichalKohaCZ[m]      Hi Koha
10:31 * ashimema           has been hit by that himself ;P
10:31 marcelr              when you change name of patch, bz does not auto remove it
10:31 ashimema             thanks 🙂
10:30 marcelr              ah i see, corrected
10:30 ashimema             as in.. the removal of the spread
10:30 marcelr              let me look
10:30 ashimema             but the spread patch is still present on the bug
10:30 ashimema             indeed
10:29 marcelr              ashimema: i removed the spread, it triggered an error somewhere
10:26 huginn               ashimema: The operation succeeded.
10:26 ashimema             @later tell marcelr does your spread removal followup need removing again on bug 34092.. I see it's gone PQA, but looks like the spread patch is still there even though you verify it causes an issue?
10:23 oleonard             o/
10:14 krimsonkharne[m]     morning #koha
09:55 ashimema             mornng
09:51 magnuse              hush...
09:42 cait                 wow, that's a quiet Monday
07:05 cait                 we have a few more 23.05 demo installations - Catalyst++
07:01 marcelr              o/
06:58 cait                 good morning #koha
06:27 reiveune             hello