IRC log for #koha, 2024-03-21

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

All times shown according to UTC.

Time Nick Message
01:33 schnydszch joined #koha
03:59 AndroUser2 joined #koha
04:35 thd joined #koha
04:37 thd davidnind: I confirmed an email account yesterday for someone reporting no confirmation message.
04:38 davidnind: I may have to set a password for her on the command line.
04:43 davidnind: Running a test with my own an email address of my own just now, the problem may be that the mail server reported as sending messages for the wiki does not seem to have a DMARC record nor does the confirmation email have a DKIM signature.
04:48 davidnind:  Mostly library organisation email systems which people use allow messages to pass without DKIM or DMARC but this person's system may be an exception.  I will ask tcohen about at least adding an appropriate DNS line for DMARC for the domain purporting to send email for the wiki.
05:01 Joubu cait: meeting script done
05:02 thd Joubu: Do you know what secure-mailgate.com is?
05:03 Joubu yes
05:03 our community SMTP server is hosted by this service
05:06 thd The system running the community does not add a DKIM signature to messages sent by the wiki nor is there a DMARC line for the DNS record for koha-community.org .
05:07 Joubu: Do you have access to the DNS configuration for koha-community.org?
05:07 Joubu no, only rangi has
05:09 thd Maybe secure-mailgate.com is the domain which needs the DMARC line in DNS.  It is surprising that there would not be one for an email service in 2024.
05:12 Joubu: Do you know what mailcloud.dogado.net is?
05:13 Joubu it's related, same things
05:14 thd None of them have a DMARC line in DNS.
05:15 These things seem not to matter for most of the institutional email systems which most of the Koha community is using.
05:16 However, I have been communicating with someone who seems not to have received an email confirmation message from the wiki.  I can activate her account and set her password manually on the command line.
05:20 Lack of DKIM signature and DMARC for the message sent from the wiki could be the problem for her.  The wiki just passes the message along to the SMTP server.  The SMTP server has to be configured to DKIM sign messages and some server should have a DMARC line in DNS.
05:22 Joubu: Who manages the secure-mailgate.com SMTP settings?
05:23 Joubu The dogado service, and I am pretty sure they are doing things correctly. It's their job
05:24 https://www.dogado.de/
05:24 if there is something missing it might be in our DNS, in that case you should contact Chris
05:26 thd They may be doing things correctly, but we may need to configure something with the SMTP account for a message to be signed with a DKIM signature.
05:38 Joubu I can ask
05:39 but I think they told me they don't have any kind of settings
05:42 wajasu don't forget SPF
05:42 dcook We've got SPF
05:42 dig koha-community.org TXT
05:43 rangi could add a DMARC record for koha-community.org too
05:43 DKIM is harder. That would require working with the mail server folks
05:43 The DKIM header in the email will mention a selector, and that selector is used to look up the DKIM public key against koha-community.org as well
05:44 Although... I say that...
05:44 Looks like we probably have a few domains that need things
05:44 lists.koha-community.org
05:44 I don't know what the wiki uses
05:44 * dcook disappears and hides again
05:45 wajasu do you guys need google-site-verification and facebook-domain-verification
05:46 thd dcook: The wiki is running in Docker container with no mail services other than some PHP code which passes the messages to mx01.secure-mailgate.com.
05:52 dcook Maybe I'm not totally hidden >_>
05:52 Let me see if I have a wiki email laying around
05:52 * dcook has been doing a bunch with SMTP lately
05:53 thd dcook: lists.koha-communiy.org has a DKIM signature but people at BibLibre have not had time to fix their SMTP to ensure all messages are sent with the lists.koha-community.org signatue.  I have supplied detailed instructions for a likely fix but we have a free ride their from the original message author's DKIM signature on the mailing lists.
05:53 dcook Ok... I got an email from "Koha Wiki <admin@koha-community.org>"
05:54 What do you mean by original message author's DKIM signature?
05:55 thd MediaWiki config array $wgSMTP does not have an option for specifying use of a DKIM signature.
05:55 dcook It wouldn't need to
05:56 secure-mailgate.com should be providing the DKIM signature
05:56 thd Exactly.
05:56 dcook Looking at the email from the wiki, I see it's not signed
05:56 As for the DMARC, that's something we could do ourselves without them
05:56 As that's just a policy
05:57 thd I tested last night and email confirmation messages from the Koha wiki do not have a DKIM signature.
05:57 wajasu i think the outgoing mail server does that.  i am trying to recall from ayear ago.  my mailserver company had <2048 byte keys, and thats wat google prefers. but the mailserver vender wouldn't change since its an ancient server.
05:58 dcook An ancient server wouldn't have dkim keys..
05:58 signatures*
05:58 Not much info on secure-mailgate.com out there
05:58 schnydszch joined #koha
05:59 dcook Alas, only someone with secure-mailgate.com admin will be able to investigate this further
05:59 thd The outgoing mail server is set as 'host' => 'ssl://mx01.secure-mailgate.com' in this case.
05:59 dcook ^
05:59 Yeah, it's a pretty simple setup
06:01 Going back to things like SPF and DMARC, they're going to be for the domain that the email is sent "as"
06:01 Like the SPF authorizes secure-mailgate.com to send email for koha-community.org
06:02 Then the mail server can look up the DMARC
06:02 thd Joubu may have some access to the secure-mailgate.com access, however, he seemed to remember that they had previously told him there was nothing to configure.  Maybe he needs to ask specifically about how to ensure that messages sent by the service are DKIM signed.
06:02 dcook In the case of lists.koha-community.org: it's just an empty policy: dig _dmarc.lists.koha-community.org TXT
06:02 Yeah, it could be that secure-mailgate.com doesn't know what they're doing or just didn't understand the question
06:03 wajasu won't they havd DKIM signatures in the email headers
06:03 dcook wajasu: They're not signing them so no
06:03 But they should be
06:03 wajasu oh
06:03 dcook They'd be signing with a private key and we'd put the public key on our DNS
06:04 I'll look to see if I can find a quick example..
06:04 thd dcook: Yes, surprisingly secure-mailgate.com has no DMARC line in DNS nor does koha-community.org but I think that secure-mailgate.com as the actual message sender may be the relevant domain.
06:05 dcook So I wouldn't expect secure-mailgate.com to have DMARC
06:05 We'd need the DMARC
06:05 Example:  dig _dmarc.lists.koha-community.org TXT
06:05 If you look that up, you'll see the DMARC is on lists.koha-community.org
06:05 Looks like lists.koha-community.org isn't DKIM signed either
06:07 It looks like a lot of the community email domains aren't using DMARC or DKIM
06:07 thd DMARC is supposed to authenticate the actual sender but if mx01.secure-mailgate.com is configured as the mx service for koha-community.org DNS.
06:08 lists.koha-community.org is using DMARC.
06:08 dcook thd: it is
06:08 Although it's a policy of "none" heh
06:08 bugs.koha-community.org is not using DMARC
06:08 No, DMARC isn't about authenticating the sender
06:08 That's DKIM
06:08 DMARC is just a  policy about what to do with failures
06:09 So in this case if lists.koha-community.org failed a check, the mail server is being instructed not to worry about it
06:09 thd policy none is safest and reduces rejection from the receiver.
06:09 dcook The MX doesn't matter so long as it passed the SPF check
06:09 thd We have SPF for everything.
06:09 dcook Which is good
06:09 It means we're all set to use DKIM
06:10 We just aren't yet
06:10 Certainly something to investigate
06:10 But I got to run!
06:10 wajasu i had the DMARC reports sent to me for my site. but I was afraid to reject, so i left it in report mode.  it's been a year, so maybe i should change the policy to be more strict
06:11 thd dcook:  System administrators are too busy to fix DKIM despite detailed instructions which I sent.
06:15 wajasu: I am afraid to reject because it seems to affect how strictly a recipient mail system of messages from your mail system treat your messages.  Being strict is asking for rejection even if that is the intended purpose.  Policy of 'none' or 'report' may minimise rejection when you send messages.
06:22 wajasu i did report on my system.  the system was sending login verification emails.  didn't want those lost.
06:23 when i dug into my mailhost provider, they had <2048 byte signature keys.  google prefers 2048 today, so i was afraid my score was impacted.
06:25 i actually setup my app server to sent mail directly, and added its static ip address and ipv6 address to my dns spf line, after the mailhost include.  but things never got bad enought to switch away fromthe mailhost.
06:45 reiveune joined #koha
06:46 reiveune hello
06:47 thd reivenue: hello
06:47 reiveune: hello
06:47 cait joined #koha
07:04 cait joined #koha
07:05 cait joined #koha
07:07 cait joined #koha
07:22 thibaud_g joined #koha
07:22 magnuse \o/
07:23 next gbsd is https://wiki.koha-community.or[…]bug_squashing_day
07:25 i tried the script from https://wiki.koha-community.or[…]tabase_row_format last night, but all i could get was: ERROR 1045 (28000): Access denied for user 'myuser'@'localhost' (using password: NO)
07:26 or the same message but with "'root'@'localhost'" if i ran it with sudo
07:28 hm, looks like i can't do "sudo mysql -u root" either, maybe that is the problem
07:45 Joubu ashimema: around?
07:51 cait joined #koha
08:00 ashimema Not properly yet
08:00 I'm on the phone whilst doin school and kids duties
08:09 Joubu ok, ping me when you are available, nothing urgent ;)
08:20 ashimema Okies, should be around proper within half an hour
08:35 cait joined #koha
08:37 ashimema Just seen your ktd git hook merge request Joubu
08:37 Much nicer than mine.. I was contemplating a file listing files, but it felt mucky.. I think I prefer your find a comment approach
08:38 * cait waves
08:38 ashimema Morning cait
08:38 magnuse is there any way to show the full status in bz search results? it's confusing when "Needs signoff" and "Needs documenting" both show as "Need"
08:38 cait in meetings all morning, but I will try to catch up in the afternoon and no meetings for GBSD Friday
08:38 magnuse yay!
08:38 cait magnuse: I think there isa b ug about this
08:39 * ashimema is still on school run, but enjoying the warm sun and walking this morning
08:39 ashimema No
08:39 There's not right now magnuse
08:39 magnuse ok
08:39 ashimema It's really annoying
08:39 cait Maybe ew could rename the "needs documenting"
08:39 as a workaround
08:39 magnuse could we rename one of them? "Documenting needed" or something
08:40 jinx
08:40 cait To document?
08:40 not sure
08:40 ashimema Not easily
08:40 It would be a dB level thing needing server access
08:40 There's no way to do it in the ui
08:40 I've tried
08:40 cait if we agree on something i could try and negotiate that with rangi
08:41 magnuse ah, ok
08:41 cait although I think others might have db access too?
08:41 ashimema Only rangi
08:41 cait ok
08:41 but need a name suggestion first, maybe ask the documentation team
08:41 ashimema Well, I have it if I hack
08:41 cait in ohter news: we have several new fails on Jenkins
08:42 ashimema I can read the dB via commits to the dashboard.. but it's not an easy option
08:42 cait as I am heading into meetings, I haven't investigated closely yet. If someone is looking fora  way to help out, that would be a great spot :)
08:44 Joubu cait: bug 34655
08:44 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=34655 normal, P5 - low, ---, chris, NEW , system_preferences_search.t is failing randomly
08:44 ashimema Bugzilla actually cuts the data before it's returns to the browser, so there's really no way to get the full string.. I do have an open pr for that upstream though.. but there's so many other higher priority things happening in bz world at the moment
08:44 Harmony is edging closer
08:45 cait it's cool to hear that they are moving
08:45 fingers crossed!
08:45 ashimema I pushed.. and pushed.. in a friendly way
08:46 Joubu cait: bug 32671 for basic_workflow, I let a comment
08:46 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=32671 normal, P5 - low, ---, jonathan.druart, Pushed to oldstable , basic_workflow.t is failing on slow servers
08:46 ashimema I have 3 PRs open with them and that's prompted them to fix their test suit.. next challenge is to build the release notes for them going through the divergent branches to work out what's missing in the two main branches
08:46 cait thanks!
08:46 ashimema That's a big job.. but once that's done they should be in a place to release bz 5.2 proper and bz 6.0..  it's 6.0 we want to upgrade to
08:47 cait did you also investigate the perlcritic one?
08:48 ashimema BZ woes basically all stem from a breakup between bugzilla and mozilla
08:56 Joubu cait: bug 36381
08:56 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=36381 major, P5 - low, ---, chris, NEW , "not a tree object" error from Jenkins
08:57 Joubu this one is certainly bad, because I think Jenkins is missing some tests
08:57 cait ok
08:57 meeting now :( will be back in between
08:58 Joubu++ thanks for the help
09:05 ashimema Back now Joubu
09:06 Joubu still around :)
09:06 ashimema sorry.. I meant I'm back proper now
09:06 😉
09:07 Joubu If you are happy with the "tidy me" comment, I think the QA and git hook merge requests are ready
09:07 the Koha part still needs to be fixed (2 files to tidy in modals/)
09:09 ashimema yeah, I think the 'tidy me' comment is probably the most pragmatic approach.. hopefully at some point all files will eventually be tidy and we won't need such comments
09:10 but it's a good middle ground.
09:10 Joubu A next step would be to ensure the comment is there for new files
09:11 ashimema yeah.. that would be great
09:25 magnuse ashimema++ for pushing bz
09:40 vfernandes[m] hi #koha-community:matrix.org
09:41 ashimema we have no vue guidelines and no js prettier guidelines at all yet ☹️
09:46 vfernandes[m] I hope i'm not interrupting any meeting... How we can have/manage in Koha two or more libraries in different timezones?
09:46 Example: lib1 in GMT, lib2 em GMT+5
09:47 Joubu ashimema: https://wiki.koha-community.or[…]ettier_JavaScript
09:48 ha you just added it :D
09:48 ashimema lol
09:48 I did
09:48 was just coming here to ask you to review it 😉
09:48 you beat me to it
09:49 there's timezone stuff in the koha-conf.xml vfernandes
09:49 Joubu, I have a feeling the .vue files have a slightly different prettier line right?
09:49 Joubu maybe one thing is consusing: .vue and .ts don't need the flag comment
09:49 ashimema so that probably needs adding to the guideline
09:49 true
09:49 Joubu yes, we don't ask for the semicolon for .vue
09:50 ashimema may just drop the TS/Vue bit.. those should be tidy already anyway right?
09:50 Joubu we can have something on the guideline, but really it's almost impossible to reach master, with the QA+git hook
09:50 ashimema indeed
09:51 this is more for QA people to be able to point to if people argue 😜
09:51 Joubu and it will be caugh by the xt test anyway gniark gniark
09:51 ashimema yup
09:53 cait vfernandes[m]: at the moment you can only set a timezone per instance, not for indidivual libraries, I believe there is a bug in bugzilla asking about this, but it would not be an easy change
09:54 ashimema oh..
09:54 I misunderstood that question
09:54 yes.. per instance, not per 'branch'
09:54 that could be 'fun' development
09:57 paulderscheid[m] Morning #koha
09:59 vfernandes[m] Thanks cait and ashimema... (full message at <https://matrix.org/_matrix/med[…]htlyoJJYfBojNXwwu>)
10:00 ashimema I don't think there is a bug
10:00 You an report one
10:01 I don't think it'll be as simple as a little tweak to dateutils.. you'll need to handle cross branch cross timezone calculations
10:01 magnuse oh look, gbsd just started in Kiribati! https://wiki.koha-community.or[…]bug_squashing_day
10:04 ashimema 🙂
10:05 cait I am in a meeting, but I think i saw a bug, look for timezone
10:06 magnuse look for timezone?
10:06 cait hm in bz, but I am not finding it either right now, it might be hiding as a comment on an other bug
10:08 magnuse ah, sorry. i thought gbsd had a bug...
10:18 paulderscheid joined #koha
10:19 paulderscheid morning #koha
10:19 does oftc not support tls?
10:19 oleonard o/
10:19 paulderscheid o/
10:23 paulderscheid[m] That's so weird, I have been reconnected by the OFTC IRC bridge w/o doing anything an hour after my last command.
10:23 At least I have a fallback now.
10:25 Joubu you there?
10:26 I wanted to suggest yesterday that there should be one prettier config file (there are a myriad of possible format) for everything js/ts related in koha to centralise the formatting.
10:26 But only matrix users could see the message.
10:26 And let's also use the prettier cache feature.
10:34 ashimema ++
10:34 * ashimema is looking into conform.nvim at the moment
10:41 paulderscheid[m] conform.nvim seems very efficient
10:42 paulderscheid joined #koha
10:43 ashimema I need to disable some of the auto-tidy stuff though
10:44 it's currently doing too much and making my commits contain more than they should
10:44 I like Lazy and how quickly it got my up and running but actually it does a LOT
10:44 and I don't need all that
10:47 Joubu paulderscheid[m]: yes
10:51 paulderscheid[m] I like lazy because it has the best defaults. If you want my opinion: keep it and disable what you don't need. Building a config from scratch can take weeks (I don't even have hours :D)
10:53 Joubu: you could keep everything as is, but instead of passing the options inline you can just use prettier --config <CONFIG> instead.
10:54 Joubu yes, but remember how hard it was to make the IDE use the config file?
10:55 ashimema yeah.. that's why I ended up on Lazy
10:55 Joubu but yes, we need a single place to put the config, I agree
10:55 ashimema getting my own config right was just taking too long
10:55 paulderscheid[m] IIRC prettier is able to ingore the .editorconfig w/ --no-editorconfig
10:56 I do remember it :D
10:59 Joubu to be honest I simply rely on the git hook to pretty everything for me when I commit, and I don't mind about indent and stuffs when I write the code
11:02 paulderscheid[m] that's perfectly fine, I rarely use the editor for formatting, rather the prettier cli.
11:03 The thing is that sometimes the code one writes just gets so messy that you have to format and then it's useful to have the config in the project root for the cli (or the editor).
11:03 We could also suggest just to use the cli, which will work independently of the editor (but if setup correctly there should be no difference).
11:06 You know what. I will just try it out later and test w/ vim, neovim, vscode and oss forks.
11:37 jzairo joined #koha
11:44 oleonard Hi jzairo!
12:28 Dyrcona joined #koha
12:30 jzairo hi oleonard!
12:41 khall joined #koha
12:51 tcohen Joubu: did lukeg contact you about the failing CSRF tests in 23.05?
12:52 Joubu I don't think so
12:56 tcohen @seen marcelr
12:56 huginn` tcohen: marcelr was last seen in #koha 6 days, 1 hour, 54 minutes, and 19 seconds ago: <marcelr> ashimema: what is the LCF of MARC21 btw
12:56 tcohen @later tell marcelr is what I submitted on bug 35129 what you expected?
12:56 huginn` tcohen: The operation succeeded.
13:17 JBoyer joined #koha
13:21 AndroUser2 joined #koha
13:36 AndroUser2 joined #koha
13:45 AndroUser2 joined #koha
13:53 AndroUser2 joined #koha
14:06 khall_ joined #koha
14:06 schnydszch joined #koha
14:27 magnuse hm, weblate isn't all that clever about reused translations: Other source strings: “Authorized users”, “Authorized values ”
14:58 cait hm i believe the suggestions where not that clever, but just from shared "parts" they are probably similar
15:10 lukeg joined #koha
15:32 bag joined #koha
15:46 khall_ wiki is down? https://downforeveryoneorjustm[…]oha-community.org
15:50 oleonard Not just down but a 404 error
15:54 Let me just check the wiki to find out who runs that site :D
15:56 thd tcohen: portainer.koha-community.org seems to be down with services showing 404 and docker ps not returning anything.
15:58 Not just the wiki.  I believe that multiple services run from the same system but nothing seems to be restarting.
16:04 tcohen: Now the portainer.koha-community.org system seems to also be inaccessible from ssh.
16:06 khall joined #koha
16:10 thd ssh error message: Connection reset by 75.119.140.119 port 22
16:16 oleonard When looking at a patron's notices (/members/notices.pl) what is the difference between "time created" and "time updated" ? Is a notice "updated" after it is sent?
16:16 thd tcohen: Now ssh has no route to host for portainer.koha-community.org even via 75.119.140.119 IP address .
16:19 caroline oleonard, that seems to be the case. I'm looking at a patron in production and the time created is when the advance notices cron was run and the time updated is when the process message queue cron was run
16:20 oleonard So if I have a "time created" of 2024-03-09 and "updated on" of 2024-03-20 then something has gone wrong
16:20 11 days in the queue for some reason.
16:21 tcohen 16106
16:21 there's a hardware problem again
16:21 thd, cait Joubu
16:21 I'll try to deploy everything somewhere else
16:21 in the meantime I'm contacting support
16:21 thd What type of hardware problem?
16:27 caroline Since the wiki is down, does anyone know the correct terminology for branchcode in the staff interface? Would it be Library code?
16:36 tcohen thd: I only have a web UI in which they tell me there was an error trying to start the server. And the VNC terminal that can connect to the Qemu hypervisor terminal
16:37 is giving an error
16:37 thd caroline: Yes, according to https://git.koha-community.org[…]admin/branches.tt .
16:37 tcohen so it is an infrastructure error
16:37 caroline perfect, thanks thd
16:43 thd tochen:  VNC needs routing so it could still be a switch rather than the server hardware.
16:44 tcohen the panel gives an error starting the server
16:47 thd :(
16:48 schnydszch joined #koha
16:52 caroline Does anyone know what makes a vendor appear in the ERM module "New agreement" page?
16:53 cait could it be the type setting?
16:53 caroline I have a client who has 600+ vendors in acquisitions, but there are only 20 that are in the agreement dorpdown
16:53 I thought the type was optional though?
16:54 i'll try in master... 20 results is suspicious, like only one page
17:07 paulderscheid[m] I bet you already tried whether RESTDefaultPageSize affects the results caroline?
17:07 If so it sounds like a bug.
17:34 cait joined #koha
17:37 jzairo i can confirm caroline, I only get the first 20 vendors in agreements
17:37 khall_ joined #koha
17:50 tcohen I'm sorry folks, I'll do my best to find a way to recover the server status
17:59 I've made a support request
17:59 but they are german
18:01 caroline paulderscheid[m], thanks I didn't know about that one. I changed it to 50 and now see 50 results in the dropdown. I wonder what else is affected
18:02 paulderscheid[m] Yeah, that's seems to be a bug but to be sure: Joubu.
18:02 caroline I found bug 32468 but it says it was in 23.05.00 and I have 23.05.05 so I don't understand why i only see 20
18:02 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=32468 major, P5 - low, ---, jonathan.druart, CLOSED FIXED, Vendors select only allows selecting from first 20 vendors by default
18:04 paulderscheid[m] I honestly do not know the protocol in such cases. I think adding a comment and reopening it?
18:05 caroline I'll ask my colleague first to see if it's like something we need to change on the server or something. I don't really understand what the patch does
18:07 paulderscheid[m] I think it uses a trick: specifying -1 for the page size, resulting in all entries being displayed (just a guess, though)
18:07 caroline btw hi jzairo! You're not often around it's good to see you! :)
18:08 paulderscheid[m] If that is indeed a trick to get the full table, it should be documented in the API docs.
18:08 jzairo hi! caroline :)
18:09 caroline paulderscheid[m], you mean putting -1 in the pref?
18:09 paulderscheid[m] Nah, in the first patch on that bug.
18:10 They add the query parameter ?_per_page=-1
18:10 caroline ah ok
18:10 paulderscheid[m] To all api paths.
18:10 caroline I also found bug 32474 but that is only in 24.05
18:10 huginn` 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=32474 enhancement, P5 - low, ---, matt.blenkinsop, Pushed to master , Implement infinite scroll in vue-select
18:12 paulderscheid[m] Paulderscheid::Exception::TooManyComments :D
18:13 caroline lol
18:21 tcohen ahahahah
18:41 reiveune bye
18:41 reiveune left #koha
19:35 lukeg joined #koha
19:42 alexbuckley joined #koha
20:07 khall joined #koha
20:33 alexbuckley hi everyone!
20:33 caroline hi alexbuckley!
20:33 alexbuckley hi caroline!!
21:08 khall joined #koha
21:16 davidnind hi alexbuckley
21:17 alexbuckley hey davidnind! good to see you and caroline :)
21:17 davidnind nice blog post! (https://www.catalyst.net.nz/bl[…]e-patron-emailer)
21:20 alexbuckley thanks so much davidnind!!
21:20 I love writing Koha blog posts :)
21:26 davidnind alexbuckley++
22:16 alexbuckley thanks davidnind :)
22:17 AndroUser2 joined #koha
22:25 dcook .
23:06 schnydszch joined #koha
23:13 dcook Bit of Koha infrastructure down today it seems
23:25 AndroUser2 joined #koha
23:34 AndroUser2 joined #koha
23:48 cait joined #koha

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

koha1