IRC log for #koha, 2024-03-01

← Previous day | Today | Next day → | Search | Index

All times shown according to UTC.

Time Nick Message
00:02 dcook \o/
00:02 So I read that as "Iam in Europe" rather than "1am in Europe" hehe
00:02 also hi mtj and bag
00:05 @later tell Joubu How do we want to manage bz 34755? Security bug or regular bug for the backporting?
00:05 huginn` dcook: The operation succeeded.
02:30 jo joined #koha
05:58 hammat joined #koha
07:13 marcelr joined #koha
07:13 marcelr o/
07:16 tcohen joined #koha
07:38 fridolin joined #koha
07:38 fridolin hello
07:42 reiveune joined #koha
07:42 reiveune hello
07:59 marcelr hi fridolin reiveune
07:59 Joubu @later tell dcook we need to attach to 34755 a patch to fix Koha::Token which will be for stables only. Not security per se I'd say
07:59 huginn` Joubu: The operation succeeded.
08:02 lds joined #koha
08:03 cait1 joined #koha
08:05 Joubu mtj: who is supposed to send the release email?
08:10 cait1 Frido
08:11 RMaint1 I think according to the wiki
08:13 cait just got in - were the packages pushed now?
08:14 mtj: ?
08:16 mtj hiya
08:16 cait hello :)
08:17 mtj just waiting for release emails before pushing
08:18 ...but ok to push now, if needed?
08:19 cait I think maybe push as it took a little while last time and we will try to sort the email
08:19 I can publish the website drafts if needed and others can too, they are ready
08:19 a few minutes shoudl not make such a difference
08:21 cait1 joined #koha
08:22 mtj ping frido
08:22 cait1 Joubu: ok?
08:22 mtj: sending an email
08:22 Joubu push all the things
08:23 mtj hi Joubu, thanks for the ping on bz 35614
08:23 fridolin joined #koha
08:23 fridolin Joubu: I'm on it as RMaint1
08:25 cait1 ok, I have a meeting but can follow here
08:25 fridolin++ mtj++
08:32 marcelr ashimema around ?
08:39 alohabot joined #koha
08:52 fridolin mtj: Email annoncement sent
08:54 marcelr fridolin: let the party begin
08:57 paulderscheid[m] Thanks for all the work, community ++
08:57 morning #koha, btw
08:58 mtj hi frido, will upload now
09:11 fridolin joined #koha
09:16 cait drafts published
09:29 puphaus[m] Hello together :)
09:30 If i try to access https://koha-community.org/koh[…]3-05-09-released/ i get redirected to the koha-community.org/
09:30 are there the same bugfixes as in version 23.11.03?
09:32 cait checking
09:33 puphaus[m] thank you :)
09:33 cait puphaus[m]: https://koha-community.org/23-05-09-released/ works
09:33 it's missing the koha-
09:33 not sure if I can change it now, will try
09:34 ok, I updated the permalink,k the first link should work now
09:36 mtj hi folks, pkgs are pushed
09:37 we might need to update tar files at download.kc.org
09:40 cait mtj: they shoudl built automatically once the tags are all pushed to main repos (I think)
09:40 Joubu yes
09:41 yes, what cait said
09:41 mtj aah ok, very nice team
09:47 hammat joined #koha
09:52 RamiKaram[m] Hello, i have deployed 2 virtual machines with koha software installed on both of them, and both these machines are pointing to 1 database server where koha database is installed, but i'm having issues when creating new records, one server can see the record but the other cant, but for patrons creation it is working fine on both
09:55 are there any documentations regarding high availability deployment for koha? where i might find more details?
09:57 cait I am not sure the setup you describe is common - 2 installations using the same database
09:57 what are you trying to achieve?
09:58 RamiKaram[m] i am trying to separate koha application from the database (each component on 1 VM) and to achieve high availability in case app server craches, i willl have another app server deployed and pointing to same database
10:00 cait I haven't heard about that kind of setup so far, but maybe ask on the mailing list if you don't get a reply here
10:03 paulderscheid[m] Is there a canonical way to determine the instance names of all instances on a server?
10:03 As a list?
10:04 RamiKaram[m] cait: i read in some forums that you can change the database host name in the file/etc/koha/sites/koha-db/koha-conf.xml and point it to another server
10:06 paulderscheid[m] I don't think that's necessary Rami Karam, you can just increase the number of plack workers and scale vertically.
10:07 RamiKaram[m] paulderscheid: can you elaborate more about it? thanks again
10:11 paulderscheid[m] Just here in koha-conf.xml:... (full message at <https://matrix.org/_matrix/med[…]mCckSjnzvVGedCcwf>)
10:11 Please correct me community, if I forgot something.
10:12 We do 16 workers for big hosts, I think.
10:12 Just make sure you have the specs to handle it.
10:13 RamiKaram[m] so u mean no need to separate the database? keep koha and database on same server?
10:13 paulderscheid[m] You can do that, the configuration for the db connection is also in koha-conf.xml
10:14 But we don't do it. Just complicates things w/ little benefit (for us, your mileage may vary).
10:15 I think bywater and maybe ptfs are the ones to ask, they also handle large consortia.
10:16 RamiKaram[m] thanks paulderscheid for the help! much appreciated
10:17 paulderscheid[m] Sure thing
10:17 This is the place if there's one :D
10:17 RamiKaram[m] hehehe
10:25 paulderscheid[m] There's koha-list for everyone interested. Great that this exists!
10:36 cait kidclamp: ping?
11:27 cait1 joined #koha
11:31 huberto joined #koha
11:58 cait1 joined #koha
11:59 oleonard joined #koha
12:16 oleonard_ joined #koha
12:33 lds joined #koha
12:37 thibaud_g joined #koha
12:48 tcohen happy friday #koha \o/
12:49 cait tgif? :)
12:58 kidclamp RamiKaram[m]: It sounds like you mght have two search engines - if those are not shared then a new record on one won't be indexed into the other
12:58 You would want a central ES or Zebra that both index into
12:59 you will also want crons to run only on one machine, and things like SIP servers etc - it can be done - just need to consider all the services
13:02 oleonard joined #koha
13:16 Joubu csrf - bug 34478 and friends, pushed to master
13:16 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34478 is not accessible.
13:16 tcohen Joubu++
13:17 cait Joubu++ everyone_involved++
13:17 kidclamp++ tcohen++ marcelr++
13:17 dcook++
13:17 tcohen marcelr++ kidclamp
13:17 kidclamp++ ashimema++
13:17 cait++
13:17 cait the 'big baby' was it?
13:23 oleonard \o/
13:37 khall joined #koha
13:55 Dyrcona joined #koha
13:58 caroline joined #koha
14:00 cait Joubu killed my statistics -maybe pushed more today than I pushed all cycle ;)
14:10 oleonard joined #koha
14:14 cait is it time for confetti?
14:14 tcohen confetti!
14:15 cait tcohen: can I ask an API question?
14:16 I was wondering because it looks like we can only update patron records sending required fields (categorycode, surname, library) - am I misreading things or is there a way around it? It seems to make more sense for adding patrons than for updating
14:16 tcohen sure! happy to help
14:16 you mean sending a PUT for partial updates?
14:17 RESTful guidelines say PUT should be for replacing a resource, whereas PATCH should be used for partial updates
14:17 cait yes, we are looking into updating the userid for an example
14:18 hm
14:18 I think you can partially replace right now with put
14:18 but you sitll need to send the rquired fields
14:19 tcohen I'm not sure how to help you. The best would be for you to GET the patron, amend, and resend with PUT
14:20 cait I was just wondering if there was a way around this limitation
14:21 it seemed a little odd that you need to send data you don't want to update
14:21 Joubu correctly implement PATCH
14:21 tcohen :-D
14:21 cait yeah i guess that's the answer
14:31 or work around it
14:34 tcohen can't you just GET the patron? That's a good workaround :-D
14:35 cait the use case is that we want to limit what externals can see/do
14:36 like limiting which fields someone can edit via API - as always it's more complicated
14:36 tcohen patch Koha to accept PATCH (with it's implications) or write a tiny plugin for that feature, that's what I'd suggest
14:37 cait I think updating the REST API for patch is outside my league right now
14:37 tcohen cait: we didn't implement PATCH exactly because of that: it is impossible to specify attribute level permissions on a request using OpenAPI
14:44 Maybe PUT /patrons/:patron_id/userid, with a specific permission is the only way to do what you seem to need
14:54 Joubu: around?
14:55 kidclamp: I was looking at doing the CSRF stuff fro parcel.pl, which I did. But I found receiving is not working. Should I file individual bugs for those?
14:59 Joubu read the email Nick sent to the list
15:00 there are bugs opened already, linked to the pad
15:00 there is one "bug testing", for unknown bugs
15:00 bug 36195
15:00 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=36195 critical, P5 - low, ---, koha-bugs, NEW , CSRF - testing reports
15:00 Joubu if not clear enough please add info to the pad
15:37 wizzyrea joined #koha
16:00 bag joined #koha
16:02 reiveune bye
16:02 reiveune left #koha
16:05 cait taking bug 36195 as an example - if we put all patches on omnibus bugs, how do we handle testing/signoff and is the patch attached there pushed or still waiting?
16:05 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=36195 critical, P5 - low, ---, koha-bugs, NEW , CSRF - testing reports
16:05 cait and who is going to take care of it next? (bug remains as new)
16:07 kidclamp I don't think we need full sign off/QA , most are straightforward,
16:08 The idea was just to push patches as they are submitted, with some review from the pusher
16:08 As there are expected to be many small ones in the beginning
16:08 cait ok - will that be me?
16:08 but I won't get alerted on new patches attached to those bugs
16:08 unless i keep checking all the omnibus constantly
16:08 kidclamp You or joubu or Martin
16:09 Cc yourself on them :-)
16:09 cait I do follow the bugs - but I'd prefer a status
16:09 if you put something on the bug, maybe you shoudl set it to PQA
16:10 we can obsolete anything pushed
16:11 on the bug maybe, so it gets easier to pick up what hasn't been pushed yet
16:11 any good best practice there?
16:13 It is pushed, maybe we will just sleep over it and things will be more clear Monday
16:13 oleonard joined #koha
16:13 kidclamp that sounds reasonable, it is the RM decision in the end :-)
16:14 cait just to be clear: I want to push those fast, make sure we don't miss anything - I just wonder about what the best process is to achieve that :)
16:14 and preferrably not break more than we fix :)
16:15 I think we have the same goals, we just need to figure out how we can best work together to get there :)
16:16 lukeg joined #koha
16:17 cait I for now, if you have patches put them on the bugs as suggested and we will deal with it after the weekend
16:19 and try the multi-omnibus bug approach for a bit
16:20 long week for us all - have a happy weekend!
16:25 wizzyrea joined #koha
16:56 cait joined #koha
17:16 lukeg joined #koha
17:29 JasonGreene[m] looking for instructions on how to modify sever books at the same time.   Several books are "Not for loan" so I can't check them out.
17:30 or how can one make the change to ALL items
17:34 s/sever/several/
17:35 caroline JasonGreene[m], https://koha-community.org/man[…]tch-editing-items
17:36 you can use the item search to get all the not for loan items and from there export a barcode file
17:37 JasonGreene[m] thanks
17:52 In that area, where should  #7 - Not for loan   be change to?  "Add the bundle    "Not for load   "Ordered   "Staff Collection  We just want to make them check out-able
17:53 khall_ joined #koha
17:57 caroline JasonGreene[m], in the batch edit tool, if you check the box next to the field, it will empty it. This is what you want, $7 should be empty for the item to be available
18:00 JasonGreene[m] That make since
18:38 It didn't work and then I found out why...the  Item type needed to be Modified ... I changed the item type 'REF' and it worked
19:25 khall joined #koha
19:36 khall_ joined #koha
21:15 khall joined #koha
21:51 khall joined #koha
23:02 fredericd joined #koha

← Previous day | Today | Next day → | Search | Index

koha1