Time Nick Message
22:27 mtj looks like its working for me, on master - after i fixed that l10n issue
22:25 mtj hi caroline, try 'ktd pull' again
22:25 mtj ta, looks to have fixed that ^
22:24 mtj $ sudo chown -R kohadev-koha:kohadev-koha misc/translator/po
22:21 davidnind Joubu added some notes about problems with translations to the KTD readme: https://gitlab.com/koha-community/koha-testing-docker#another-problems
22:17 davidnind maybe delete the misc/translator/po directory - ktd will git pull the koha-i10n repository when it starts up
22:10 mtj koha-koha-1 | Fetching koha-l10n...
21:39 davidnind good thanks mtj!
21:37 mtj caroline: gimme 5 mins, i will test..
21:32 mtj hi davidnind, hope you are well :)
21:27 davidnind hi mtj!
21:22 caroline I don,t know if it was the master one. I guess so, I don't do fancy things or anything
21:17 caroline Ok that's what I thought, like git pull, it only pulls the changes. But I had at least 6 of each
21:17 mtj ...the master one?
21:17 mtj caroline: which ktd image are you having problems with?
21:16 mtj docker will then try to only downlown the 'layers' of the image that have changed
21:15 mtj its likely a new image was built, since you last pulled
21:15 caroline lol!
21:15 mtj caroline: good news... a ktd pull wont always create a new image
21:15 mtj aah, yes... ktd pull
21:14 caroline yes! I was talking about ktd pull
21:13 mtj caroline: good news... a git pull wont always create a new image
21:13 caroline hi mtj!
21:13 mtj hi davidnind, caroline
20:45 caroline docker image rm <id> cleared about 40% of my 100G disk
20:40 caroline I didn't realize every ktd pull created a new image. I thought it was like git pull where it updates whatever you already have
20:40 caroline oh yeah I had that recently
20:39 davidnind the other problem I've had in the past is not enough disk space (I only have a 256GB drive): df -h /
20:37 davidnind it's always very annoying when things don't work as they should!
20:30 caroline It's still bugging about something now lol
20:30 caroline Mine is 22.04 too, I might-ve done automatic updates
20:28 davidnind I vaguely remember seeing a docker update in the last week (my desktop is Ubuntu 22.04)
20:28 caroline it stopped again... :( I will try restarting my computer later
20:26 blawlor[m] I've seen that and think it was related to Windows/Docker updates and rebooting resolved it
20:24 emlam oof...when mine does that, restarting the computer usually fixes it if ktd down + pull things doesn't.
20:19 davidnind I don't think I have seen any recent ktd git or image changes, so I would be confused as well!
20:18 caroline it was working fine yesterday, which is why I'm a bit confused
20:15 davidnz good luck!
20:15 davidnz Mine is currently working OK, before the KTD stuff I normally git pull for koha and make sure I'm on the master branch
20:14 caroline it's worth a try!
20:14 davidnz For KTD I normally do a git pull, ktd pull, then ktd up - if I have trouble I normally delete all the docker images and volumes and do a fresh ktd pull
20:12 caroline once it stopped when trying to do stuff with apache, but I think that's the time when I did ktd up and then locked my computer
20:11 caroline I tried like 5 times today and it's always the same
20:11 caroline anyone else have problems with ktd dying when going up? I do `ktd down`, then `ktd up` and after a while it says koha-1 exited with code 1. It's usually right after "Inserting /kohadevbox/koha/installer/data/mysql/mandatory/account_offset_types.sql..."
19:28 reiveune bye
18:23 tcohen ashimema: do you have the link for the perldoc stuff at hand?
18:23 tcohen back
18:01 ashimema Matt's going to blitz what he can on erm bugs tomorrow, that'll clear a few too
17:43 oleonard ashimema++
17:23 ashimema but.. on that note. I now need to clock out
17:23 ashimema still 150 including enhancements though.. that's rather higher than I'd like
17:23 ashimema QA queue (for bugs at least) down to 28...
17:21 caroline Like a howler letter in harry potter? lol
17:21 cait but with that... I am gone for today :) bye all!
17:21 cait we could also add it as mistake to the frameworks test
17:21 cait maybe... or make it shout at you?
17:18 caroline should we make it impossible to change 952$y to *not* mandatory? Clients change the marc framework, don't enter item types and then Koha explodes everywhere (latest I found is reception page in acq)
16:56 cait :)
16:42 oleonard cait: No, no school runs unless there are unusual circumstances :)
15:51 cait oleonard: do you still have school runs?
15:51 cait ;)
15:50 cait I feel left out now... no school runs...
15:39 tcohen cya!
15:39 tcohen lunch + school drop
15:31 ashimema School run, brb
15:30 ashimema Cron prefe
15:30 cait ?
15:30 cait spare timeß
15:30 ashimema Yup
15:30 ashimema Not that there's much of that these days
15:30 ashimema I'm building a crown manager plugin in my spare time
15:30 cait we could make it easier by moving more options into prefs/config outside cLI params
15:30 ashimema Indeed
15:29 cait it works :)
15:29 cait but we have some extras handled with ansible and a central configuration file - I don't know much about that part of the magic tho
15:29 ashimema Which is a nightmare
15:29 ashimema We also struggled to get the different tenants to agree on an upgrade date.. they were all too used to being able to pick their own date
15:29 cait cron is mostly standardized
15:28 ashimema Like a decade plus
15:28 ashimema Its been a very slow process weening people off those
15:28 ashimema And all the customisations we used to support
15:28 ashimema It's Cron that we come unstuck
15:27 ashimema Yup, though indexing configs work nicely in multi-tenant already if you know how
15:27 cait done a full "LTS cycle"
15:27 cait yeah, we will see if it works out if we have a second one, I agree
15:26 ashimema We're yet to see an LTS actually go into lts time
15:26 cait the RM kinda came in between
15:26 cait I offered to do that if you remember
15:26 cait index config etc. is the same for all our ones
15:26 ashimema Lol, you guys better start thinking about stepping up to rmaint then 😉
15:26 cait what kind of configs?
15:26 ashimema Though we might go back if we can
15:26 cait we do multi-tenant as well for the smaller ones
15:25 ashimema Oh, you multi-tenant do you.. we struggled with that.. people wanted configs too different
15:25 cait we are on the opposite side right now in terms of update cycle, we used to once a year, but hope to jump from LTS to LTS now
15:25 ashimema I want a rolling release next though . In community
15:25 caroline we do a couple of clients at first, volunteers to be our testers, and then we upgrade server by server (so 10-20 clients at a time)
15:24 ashimema As for a talk, not a bad idea though I don't know how good it is for a community aspect . We nearly always run a little ahead of the stables
15:24 ashimema ByWater are moving that way this year I believe
15:23 ashimema Certainly for part of the customer base at least
15:23 ashimema Once we have that I think we might push for 05 and 11
15:23 ashimema Usually around .02 for the early birds and then later as and when we upgrade people. We're moving to doing more upgrades at the same time rather than handling them individually as we have been
15:22 cait we got it all covered between us ;)
15:22 ashimema We were a .11 shop
15:21 cait LTS we hope...
15:16 caroline We usually wait until xx.05.05 to make sure the main bugs have been fixed
15:16 caroline We only do .05
15:16 caroline Do you think it would be pertinent to share your process ashimema, in a conference talk for example? ;)
15:15 ashimema Or do you do both
15:15 ashimema Are you an .05 shop caroline
15:15 ashimema We're really starting to refine our package building process.. it's great to see Jenkins taking the load for us there
15:15 caroline us either, we're just finishing our 23.05 updates and no one has been complaining about the design afaik
15:15 ashimema Excellent
15:14 cait but we are quite happy so far - and there have been no issues so far with the new GUI reported
15:14 ashimema Fun
15:14 cait we are in the middle of 22.11 go lives...
15:14 ashimema Our 23.11's start going live next week
15:12 cait hope the effect is also as expected, fingers crossed!
15:12 ashimema Excellent
15:12 caroline +1 I just tried it on our 23.05 and Iit seems to apply cleanly
15:12 ashimema So I envisage it being trivial on 23.05
15:11 ashimema We have that set backported to our 22.11 branch btw Caroline
14:52 caroline oh right, I hadn't thought of new installs :)
14:51 ashimema unless you're also using that branch for new installs
14:51 ashimema agreed
14:36 caroline I don't think I need to bother with the ones that affect the sample notices
14:36 caroline so the four "depends on"
14:35 ashimema they're all closely related
14:35 ashimema you'll probably want the tree, not just the one bug
14:33 caroline yeah unfortunately we don't work that way :) I'll just backport the patch onto our version if that is possible. If not I'll ask one of our devs to make it so that it applies
14:33 cait but the fix itself is also not very big
14:33 cait the fix shoudl be in 23.05.06 - so maybe you could consider an update
14:32 cait generates a br
14:32 cait every \n in the table markup
14:31 caroline I'll see if I can take the patch onto our version... I'm not so keen on removeing all the line breaks from the html and make it completely unreadable
14:31 ashimema another tree that didn't quite all go through
14:31 Joubu I don't understand how caroline's content can generate so much spaces between the logo and the table
14:31 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35285 enhancement, P5 - low, ---, martin.renvoize, Signed Off , Centralise notice content wrapping for html output
14:31 ashimema looks like bug 35285 still needs a QA eye
14:30 cait and I almost had to fight for it :)
14:30 cait if it's html, we don't add any br now
14:30 cait Joubu: that#s what we fixed
14:30 cait if you only print, you could remove the br... for the line breaks... just do one or the other
14:30 Joubu we should not add <br> when html is ticked
14:29 caroline ew
14:29 ashimema that one give's more clues to how involved it was
14:29 cait leave the html in, but put everything on one line...
14:29 ashimema https://bugs.koha-community.org/bugzilla3/showdependencytree.cgi?id=34704&hide_resolved=1
14:29 cait you have to remove the line breaks
14:29 huginn` 04Bug 34704: normal, P5 - low, ---, matt.blenkinsop, Pushed to oldstable , Print templates are formatted incorrectly
14:29 cait https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34704
14:29 caroline I have to put the image in a <p> or something like that?
14:28 cait but there is another sec
14:28 cait that was me going through the sample notices
14:28 cait it's the tree
14:28 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35187 trivial, P5 - low, ---, katrin.fischer, Pushed to oldstable , Fix line breaks in some HTML notices, including WELCOME
14:28 caroline is it bug 35187?
14:28 cait so lots of breaks
14:28 cait there was a "bug" that newlines were turned into br... and br were br
14:28 caroline 23.05
14:27 cait yeah, what ashimema said
14:27 cait caroline: which version are you on?
14:27 Joubu if it is relevant for the next one :)
14:27 Joubu you can use it
14:27 aude_c[m] Apologies for not realising I shouldn't be using action in General meetings
14:26 caroline 23.05 (.05 i think?)
14:26 ashimema we went to pains to fix that recently
14:26 ashimema what Koha version
14:26 aude_c[m] Joubu: both these are done anyway
14:26 caroline rendering in pdf https://snipboard.io/w4liyq.jpg
14:26 caroline Notice html for the print notice https://snipboard.io/oU6FGB.jpg
14:26 caroline anyone have an idea why (a lot of) extra `<br>` would be added to an html notice when rendering?
14:25 Joubu https://wiki.koha-community.org/wiki/General_IRC_meeting_15_May_2024
14:25 Joubu aude_c to let cait know there is no Jitsi link for next week's development meeting ashimema to open a new bug to collect suggestions, so a vote can take place at a future meeting.
14:25 Joubu Actions from last meeting
14:25 Joubu "Actions" part is not relevant for general meeting however
14:25 Joubu cait: done
14:15 tuxayo ashimema++ thanks it works :)
14:14 tuxayo 🦓💤
14:12 cait I think he is not mean... he just does want the Zebra to rest when it's not needed
14:11 * cait waves at domm
14:11 cait please :)
14:09 cait Joubu: could you run the script for the general IRC meeting?
14:06 ashimema done
14:04 aude_c[m] yes
14:04 krimsonkharne[m] aude_c: around?
14:03 krimsonkharne[m] I like no-sandbox
14:03 tuxayo Anyone else got a preference?
14:02 tuxayo ^^"
14:02 tuxayo ashimema: not-testable-on-sandbox, not_testable_on_sandbox, no-sandbox ?
13:55 ashimema give me a word and I'll add it for you
13:55 tuxayo And if they can't test, then they could leave a keyword to spare time to another sandbox user. Or just to allow another sandbox user to skip the bug even if they don't know how to assess testability. Which would be most people.
13:47 tuxayo The sandbox keyword wouldn't likely be placed by a sandbox user. They would test the bug right away (if they can assess testability)
13:44 tuxayo ashimema: «we have the oposite» «a 'sandbox' ketword to try and point out easily testable via sandboxes» Yes and it's not the same use case. Here it's to not go over the same ticket again after assessing that it's not testable.
13:41 tcohen and make koha-list aware
13:40 Joubu yes, we should have a --disable flag
13:40 tcohen it seems we never added a way to disable it!
13:40 tcohen why are you so mean, poor zebra
13:39 domm[m] And is there a way to stop Zebra from starting after reboot?
13:34 Joubu no
13:31 domm[m] Will koha-zebra --stop prevent Zebra from starting after a reboot?
13:07 cait1 I heard someone was trying to do some blue sky thinking there? ;)
13:07 cait1 the mysteries of acq
13:06 PedroAmorim[m] o/
13:01 tcohen hola #koha
12:56 ashimema at least.. it's the same permission that's checked in either case
12:56 ashimema but I'm told I was wrong
12:56 ashimema well that's what I thought was the case 😜
12:54 cait1 in theory... can the users use and the owner edit the fund?
12:52 ashimema a 'sandbox' ketword to try and point out easily testable via sandboxes
12:52 ashimema we have the oposite
12:45 tuxayo The description of the keyword could point to https://wiki.koha-community.org/wiki/Sandboxes#What_is_testable_or_not_in_a_sandbox
12:44 tuxayo hi :) can we have a bugzilla keyword like not-testable-on-sandbox ? To not go over the same ticket again after assessing that it's not testable.
11:58 Annelisterman[m] Joubu: thanks! I'll try again.
11:55 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35387 trivial, P5 - low, ---, oleonard, RESOLVED FIXED, Capitalization: Labels in preservation module are not capitalized
11:55 Joubu Annelisterman[m]: bug 35387
11:55 Joubu I think it's fixed
11:52 Annelisterman[m] In Preservation module in Trains there are two words "barcode:" and "name:" that I cannot find from translations/po files. Still they are translated correctly. They are written in lowercase which bothers me and I would have wanted to change the translation to start with uppercase letter. :D
11:36 Joubu upgrading weblate in a couple of minutes
11:34 ashimema i see
11:34 ashimema I'd always assumed, without having read the docs around it, that an 'owner' was who set it up and managed the overall amount assigned to it.. and the 'users' were those that could assign orders to it.. haha
11:34 Joubu there is also a dropdown list "restrict access to " on the edit page
11:33 Joubu I think it's just to highlight that one user is more involved than others, they are the "owner".
11:32 ashimema so it's fine
11:32 ashimema but you've just pointed out that in code that is not the case
11:32 ashimema not duplicated
11:32 ashimema thus.. I thought the hint should be different
11:31 ashimema I had presumed the users that could be assigned as the budget owner and the users that could be assigned as budget users were different lists of poeple basically
11:30 ashimema I don't really understand the difference between a 'user' and 'manager' on a fund
11:30 ashimema I'm likely just showing my lack of knowledge around acquisitions
11:29 Joubu I don't get what you mean
11:28 ashimema at least I'm being thorough 😜
11:28 ashimema lol
11:28 ashimema this is so involved
11:28 Joubu 93 my $patrons_rs = Koha::Patrons->search->filter_by_have_permission('acquisition.budget_modify');
11:28 ashimema ah.. ok
11:28 Joubu 69 my $patrons_rs = Koha::Patrons->search->filter_by_have_permission('acquisition.budget_modify');
11:28 ashimema I thought only the owner was able to manage the budget, whilst the users was the list of acq people able to use that budget
11:28 Joubu see Koha/REST/V1/Acquisitions/Funds.pm
11:28 Joubu nope, the list is filtered
11:27 ashimema I actually thought the hint missing on 'users' for the buget page was correct?
11:26 Joubu 2. on the basket manager search there is no hint, but it is missing on master as well (hence the new bug)
11:26 Joubu 1. on the fund edit there are "owner" and "users". There is a regression here: users didn't have the hint
11:25 Joubu ashimema: there are 2 things:
11:25 ashimema should bug 35865 be a dependancy for bug 35329 then
11:24 saa can anyone provide a clue to sort this error
11:24 saa [proxy:warn] [pid 3092] AH03408: HTTP: reusable backend connection is not empty: forcibly closed
11:24 saa we enabled opac with https support. When we try to see MARC record we receive error as AH01114: HTTP: failed to make connection to backend: httpd-UDS, referer: https://opac.ncl.res.in/cgi-bin/koha/opac-search.pl?q=su%3A%22Test%22
11:23 ashimema what does Yes, this is a bug, fixed in "Fix filter vars scope". fix then?
11:22 ashimema my mistake
11:22 ashimema oh, ok.. so you did that one on a separate bug
11:21 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35865 normal, P5 - low, ---, jonathan.druart+koha, Signed Off , Missing hint about permissions when adding managers to a basket
11:21 Joubu bug 35865, it's on master
11:21 ashimema you added a commit to fix it, but I'm still not seeing the message where I would expect
11:21 Joubu I don't think so, see the related bug
11:21 ashimema this one: We should have a message similar to that on the funds ownership search in the basket manager search.. we limit that search to users with particular permissions too.
11:21 Joubu which one? :)
11:20 huginn` 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35329 enhancement, P5 - low, ---, jonathan.druart+koha, Signed Off , Move patron searches to a modal
11:20 ashimema I think you may have mis-understood my blocker comment on bug 35329
11:20 Joubu yes
11:19 ashimema Joubu still around?
10:55 cait1 ashimema: I had thoght the same :) I think he gave us wrong dates! :)
09:47 Joubu too short as usual but excellent ;)
09:43 ashimema hope you had a good break
09:43 ashimema okies, I mis-understood
09:40 Joubu from last Wednesday to yesterday
09:40 ashimema ho.. i thought you were out for the whole week
09:39 Joubu break is over :D
09:39 Joubu If I uncheck all and save I get flags=0 in DB
09:39 ashimema go enjoy your break (but thanks for the enlightenment)
09:39 ashimema how come your here Joubu.. though you were off this week 😜
09:39 ashimema my brain
09:39 ashimema so 'NULL' and '0' are equivilent.
09:39 ashimema ah..
09:39 ashimema oh my.. I'm an idiot 😉
09:39 Joubu nothing checked?
09:38 ashimema what set's '0' then?
09:38 Joubu 2^0
09:38 ashimema I thought it was '0'
09:38 ashimema oh.. OK
09:38 ashimema (0,'superlibrarian','Access to all librarian functions',0)
09:38 Joubu superlibrarian => flags = 1
09:38 ashimema and unsetting it, (and not setting any other perms) set it to 'NULL'
09:38 Joubu = 1
09:37 ashimema shouldn't setting 'superlibrarian' result in 'borrowers.flags = 0'
09:37 ashimema I'm baffled about userpermissions/flags
09:22 krimsonkharne[m] morning all
09:13 paulderscheid[m] morning #koha
08:14 cait good morning all
08:13 huginn` Joubu: The operation succeeded.
08:13 Joubu @later tell marcelr Hea - first would be to add the missing ones... see bug 23849
08:03 Joubu plop
07:34 reiveune hello