| Time |
S |
Nick |
Message |
| 00:12 |
|
koha-jenkins |
Project Koha_19.11_D10 build #255: SUCCESS in 29 min: https://jenkins.koha-community[…]ha_19.11_D10/255/ |
| 00:42 |
|
koha-jenkins |
Project Koha_19.11_D10 build #256: UNSTABLE in 29 min: https://jenkins.koha-community[…]ha_19.11_D10/256/ |
| 02:37 |
|
|
fridolin joined #koha |
| 03:23 |
|
huginn |
News from kohagit: Bug 30797: (follow-up) Hide default Flatpickr clear-field button <https://git.koha-community.org[…]1d9a765764db8678e> |
| 03:23 |
|
huginn |
News from kohagit: Bug 30797: Add the calendar.inc include to addbiblio.tt <https://git.koha-community.org[…]c90aff658c20b88e5> |
| 03:23 |
|
huginn |
News from kohagit: Bug 30776: import missing subroutine to fix import_webservice_batch.pl <https://git.koha-community.org[…]e1283e6eb523afc05> |
| 03:24 |
|
huginn |
News from kohagit: Bug 30735: Fix filtering by patron attribute with AV in overdues report <https://git.koha-community.org[…]40a141364ea3470c5> |
| 03:24 |
|
huginn |
News from kohagit: Bug 30714: Do no log update to holdingbranch <https://git.koha-community.org[…]e0f7d9facc94c4118> |
| 03:24 |
|
huginn |
News from kohagit: Bug 30714: Unit test <https://git.koha-community.org[…]0b30187160061dadd> |
| 03:24 |
|
huginn |
News from kohagit: Bug 30640: Focus does not always move to correct search header form field <https://git.koha-community.org[…]4306368f5531bf39f> |
| 03:24 |
|
huginn |
News from kohagit: Bug 30009: Do not set MARCNOTES to empty list in list context <https://git.koha-community.org[…]5b5cf21d3cc03aecf> |
| 03:45 |
|
alohabot |
🎠🦄 Koha 'master' packages pushed to 'koha-staging' repo 🥯ðŸ…🲠|
| 04:03 |
|
koha-jenkins |
Project Koha_Master_D9 build #1976: SUCCESS in 39 min: https://jenkins.koha-community[…]a_Master_D9/1976/ |
| 04:08 |
|
koha-jenkins |
Project Koha_Master_D11_My8 build #842: SUCCESS in 45 min: https://jenkins.koha-community[…]ster_D11_My8/842/ |
| 04:26 |
|
koha-jenkins |
Project Koha_Master_U20 build #408: SUCCESS in 1 hr 2 min: https://jenkins.koha-community[…]a_Master_U20/408/ |
| 04:42 |
|
koha-jenkins |
Project Koha_Master_D11_MDB_Latest build #924: SUCCESS in 38 min: https://jenkins.koha-community[…]1_MDB_Latest/924/ |
| 04:46 |
|
Joubu |
@later tell fridolin About 30781 you need to use: warning_is { your_subroutine_call() } {} |
| 04:46 |
|
huginn |
Joubu: The operation succeeded. |
| 04:48 |
|
|
reiveune joined #koha |
| 04:55 |
|
koha-jenkins |
Project Koha_Master_U22 build #68: SUCCESS in 47 min: https://jenkins.koha-community[…]ha_Master_U22/68/ |
| 04:56 |
|
koha-jenkins |
Project Koha_Master build #2030: STILL UNSTABLE in 1 hr 12 min: https://jenkins.koha-community[…]Koha_Master/2030/ |
| 05:14 |
|
reiveune |
hello |
| 05:14 |
|
wahanui |
hey, reiveune |
| 05:18 |
|
koha-jenkins |
Project Koha_Master_D12 build #143: SUCCESS in 35 min: https://jenkins.koha-community[…]a_Master_D12/143/ |
| 05:26 |
|
koha-jenkins |
Project Koha_Master_D10 build #654: SUCCESS in 1 hr 0 min: https://jenkins.koha-community[…]a_Master_D10/654/ |
| 05:32 |
|
Joubu |
ashimema: you didn't add middle_name to sysprefs.sql, did you forget or was it on purpose? Please double check the last patch |
| 05:39 |
|
ashimema |
Oops, thanks Joubu |
| 05:40 |
|
ashimema |
Got kids duties for another hour or so this morning then will add a follow-up. |
| 05:40 |
|
ashimema |
Can't believe I forgot that one 😃 |
| 05:43 |
|
koha-jenkins |
Project Koha_Master_D11_MDB_Latest build #925: SUCCESS in 55 min: https://jenkins.koha-community[…]1_MDB_Latest/925/ |
| 05:50 |
|
Joubu |
I've added the follow-up ;) |
| 05:57 |
|
Joubu |
dcook: 20582 - quoting yourself "I'm intrigued but I'm pretty invested in sticking to the mainstream :/." vs "Finally, I don't actually see myself using KOHA_MOJO_APP in koha-testing-docker unless I was testing to see how a transition to using it in production would work?" |
| 05:57 |
|
Joubu |
not sure I understand what you want then... |
| 05:57 |
|
dcook |
Joubu: I'm not sure I follow? |
| 05:58 |
|
Joubu |
what do you want? |
| 05:58 |
|
dcook |
Ah fair! |
| 05:58 |
|
Joubu |
yes, you want it to work in production, ok, but it won't come like that |
| 05:58 |
|
dcook |
I want to use the same thing everyone else is using haha |
| 05:58 |
|
dcook |
I don't necessarily want it to work in production |
| 05:58 |
|
dcook |
If it were, that could be cool/interesting |
| 05:58 |
|
Joubu |
then there is a PR for ktd |
| 05:58 |
|
dcook |
But I think Starman is fine too |
| 05:59 |
|
dcook |
I think it's a tough one... |
| 05:59 |
|
dcook |
On one hand, if we don't run it as a Mojo app in ktd, we won't run it in prod... |
| 05:59 |
|
Joubu |
the idea was to have it easy to setup in ktd to let devs/us enable it for our daily work and catch bugs |
| 05:59 |
|
dcook |
But then I don't want to run it in ktd, if we're not running it in prod :S |
| 05:59 |
|
Joubu |
but this PR never got merged |
| 06:00 |
|
dcook |
As I want dev and prod to be as close together as possible |
| 06:00 |
|
Joubu |
lol.... ok |
| 06:00 |
|
Joubu |
hard life |
| 06:00 |
|
dcook |
ikr haha |
| 06:00 |
|
dcook |
I think though that paradox applies to a lot of things.. |
| 06:00 |
|
dcook |
Hard to break from the inertia of the status quo... |
| 06:01 |
|
dcook |
I actually don't know much about the benefits of running as a Mojo app tbh |
| 06:01 |
|
dcook |
Or... I think I used to know but I forgot |
| 06:01 |
|
dcook |
I think you get things like websockets.. |
| 06:01 |
|
dcook |
And non-blocking handling.. |
| 06:02 |
|
dcook |
Right now we're using Mojolicious via Mojo::Server::PSGI which I think does hamstring it a bit.. |
| 06:02 |
|
Joubu |
There is a "This has several benefits" block in the commit message, that could be a start |
| 06:02 |
|
dcook |
True haha |
| 06:03 |
|
dcook |
I don't know. I had like 5 hours of back to back Zoom calls today. My brain is tired. |
| 06:03 |
|
Joubu |
the main jajm's motivation was to "get rid of cgi" |
| 06:03 |
|
Joubu |
iirc |
| 06:03 |
|
dcook |
I do hate CGI... *strokes beard* |
| 06:03 |
|
dcook |
Maybe that's what got me excited about it too.. |
| 06:03 |
|
dcook |
Because my other ideas for getting rid of CGI involve just using Mojo::Server::PSGI.. |
| 06:03 |
|
dcook |
So running it as a Mojolicious app would probably be preferable.. |
| 06:03 |
|
dcook |
Hmmmmmmm |
| 06:04 |
|
dcook |
Of course, I think I've downgraded those dreams.. |
| 06:04 |
|
* dcook |
looks at his notes |
| 06:04 |
|
dcook |
I think I'm more interested in getting a Template::Toolkit WRAPPER in and potentially helping out with the Vue3 stuff |
| 06:05 |
|
dcook |
But that was partially because I felt alone in my efforts... maybe jajm and I could collaborate more.. |
| 06:05 |
|
dcook |
Although some of my ideas for using Mojolicious could just be replaced by using the task queue more |
| 06:06 |
|
dcook |
For example, export.pl. I did a version using Mojolicious that prevented timeouts for large exports, but really it would be nicer to just stuff that task in the task queue and alert the user when their export is ready to download... |
| 06:06 |
|
dcook |
Although I suppose both have their pros and cons... |
| 06:06 |
|
dcook |
And I'm ranting again :( |
| 06:06 |
|
dcook |
Thanks for the suggestion, Joubu :) |
| 06:11 |
|
Joubu |
We will need to implement a way to let tasks generate artifacts, but yes that would be great |
| 06:11 |
|
dcook |
I like the idea but then that could take a lot of disk space and we'd have to worry about cleanup too.. |
| 06:12 |
|
dcook |
Apparently nothing makes me happy >_< |
| 06:13 |
|
dcook |
I took a look at the commit message but I don't know if I necessarily agree with all those benefits.. |
| 06:13 |
|
dcook |
The move away from CGI.. yeah we need to refactor the authentication code and templates.. |
| 06:14 |
|
dcook |
I think you actually did do a bit on the authentication that was helpful but I think there's still a little ways to go.. |
| 06:14 |
|
dcook |
But if we do move towards Vue3 in general, switching things to Mojolicious becomes less useful |
| 06:14 |
|
Joubu |
we are (very) far from that |
| 06:15 |
|
dcook |
I just wish I could get work time to work on refactoring auth and templates.. |
| 06:15 |
|
dcook |
I don't have the energy outside of work anymore.. |
| 06:15 |
|
dcook |
Or energy/motivation maybe.. |
| 06:15 |
|
dcook |
Although we are going into winter in Australia... |
| 06:16 |
|
* dcook |
is still trying to get oleonard to take a look at his WRAPPER patch |
| 06:16 |
|
dcook |
It still needs a bit of work but it would make the templates so much easier to manage... |
| 06:17 |
|
dcook |
If I'm lucky, I might actually get some work time to resurrect the OAI-PMH harvester.. |
| 06:18 |
|
dcook |
Well resurrect the concept. I wouldn't go the POE route again.. |
| 06:18 |
|
Joubu |
"a bit"? All templates will need to be updated, that's quite a lot of work |
| 06:18 |
|
dcook |
Oh I meant in terms of getting the WRAPPER prod ready |
| 06:18 |
|
dcook |
We wouldn't have to switch all templates over right away |
| 06:18 |
|
dcook |
We could slowly replace them |
| 06:18 |
|
|
fridolin joined #koha |
| 06:18 |
|
Joubu |
did you try for the staff-side as well? |
| 06:19 |
|
Joubu |
no, slowly does not work |
| 06:19 |
|
dcook |
Nah, I just did it for the OPAC |
| 06:19 |
|
dcook |
No? I've already done it locally heh |
| 06:19 |
|
Joubu |
it's all in one go or things never get done |
| 06:19 |
|
dcook |
Ah that's a good point |
| 06:19 |
|
dcook |
I decided to start using it locally to prove that it works, and hopefully figure out some problems in the meantime |
| 06:19 |
|
dcook |
The OPAC doesn't have too many pages |
| 06:19 |
|
dcook |
The staff interface... yeah that might not be as doable |
| 06:20 |
|
dcook |
I think OPAC is < 100 and staff side is like > 500 |
| 06:20 |
|
dcook |
But when you put it that way... maybe I should abandon getting it into the community then |
| 06:20 |
|
dcook |
I think it's still useful locally for me at least |
| 06:20 |
|
Joubu |
I would reach Tomas and ask him to focus on it next cycle. You need to find someone else for testing, then submit a patch, they test, I QA and that's done. Early push next cycle |
| 06:21 |
|
dcook |
Well, I really want to talk to Owen about it to get his opinion on what is good and what is bad with my approach |
| 06:21 |
|
dcook |
I don't understand all the Bootstrap choices he's made in different places |
| 06:21 |
|
dcook |
It seems a bit inconsistent at times, and I don't know if I need to account for that, or if we can plaster over some differences.. |
| 06:22 |
|
dcook |
I've been using Template::Toolkit WRAPPER for 7+ years on a different project, and it's so handy |
| 06:22 |
|
Joubu |
which inconsistencies did you find? |
| 06:22 |
|
dcook |
Mostly with classes and IDs I think |
| 06:23 |
|
Joubu |
@later tell oleonard by chances did you have a look at 30289 already? |
| 06:23 |
|
huginn |
Joubu: The operation succeeded. |
| 06:23 |
|
|
marcelr joined #koha |
| 06:23 |
|
marcelr |
hi #koha |
| 06:23 |
|
dcook |
hola marcelr |
| 06:23 |
|
Joubu |
that's certainly coming from historical debts, not necessarily his choice |
| 06:23 |
|
Joubu |
thanks, marcelr! |
| 06:23 |
|
dcook |
Joubu: That's what I was hoping |
| 06:23 |
|
marcelr |
o/ |
| 06:26 |
|
ashimema |
I'm also game for WRAPPER support early next cycle if we want to pursue it. |
| 06:27 |
|
marcelr |
dcook will write lots of patches :) |
| 06:27 |
|
ashimema |
As for mojo.. I've not read the commit for a while.. for me a big win for mojo would be having an event loop built in.. then we can start to code in a non-blocking fashion |
| 06:27 |
|
dcook |
marcelr: Why do you hate me so, marcel... haha |
| 06:27 |
|
marcelr |
lol |
| 06:27 |
|
ashimema |
But that a way off.. |
| 06:27 |
|
dcook |
ashimema: That's great to hear about your support though. Add your name to the report? |
| 06:28 |
|
dcook |
And yeah the event loop... I'm trying to remember if I got that even when using Mojo::Server::PSGI... |
| 06:28 |
|
ashimema |
I've not compared the current mojo approach to the current plack approach for performance.. be interesting to do that comparison |
| 06:28 |
|
Joubu |
dcook: put 30707 somewhere in your head, for staff-side |
| 06:28 |
|
dcook |
ashimema: bug 26791 |
| 06:28 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=26791 enhancement, P5 - low, ---, dcook, NEW , Build Mojolicious controller replacement for export.pl |
| 06:28 |
|
ashimema |
I should really flick the switch and start using ktd with mojo |
| 06:28 |
|
dcook |
Joubu: I'll add my CC |
| 06:31 |
|
Joubu |
fridolin: did you investigate the failure on Koha_Master? |
| 06:32 |
|
dcook |
ashimema: I never did finish that export.pl replacement as there was just too much to do.. |
| 06:32 |
|
fridolin |
Joubu: not yet |
| 06:32 |
|
ashimema |
We have someone here on the infra side whose keen to start looking at how we can break our packages down a bit further too.. he'd love to see koha-common not require Apache and have a koha-apache and koha-nginx package so we could optionally support either webserver |
| 06:33 |
|
dcook |
Ah right... $c->$drain... did that work non-blocking.. can't remember.. |
| 06:33 |
|
ashimema |
We should start building a roadmap for 22.11 ;-) |
| 06:33 |
|
ashimema |
Will take a look after kids duties done ;) |
| 06:33 |
|
dcook |
ashimema: They could look at koha-core? |
| 06:33 |
|
ashimema |
Indeed |
| 06:34 |
|
Joubu |
ashimema: koha-core? |
| 06:34 |
|
ashimema |
Did that actually start gettin traction yet.. |
| 06:34 |
|
dcook |
Not that I know of |
| 06:34 |
|
Joubu |
yes he said |
| 06:34 |
|
dcook |
Someone here accidentally installed it recently and I uninstalled it in favour of koha-common.. heh |
| 06:34 |
|
ashimema |
I know we discussed it but don't remember where it got to... |
| 06:34 |
|
dcook |
Btw I've been doing a bunch of work on Debian packaging for non-Koha projects, so I'm always keen to chat packaging... |
| 06:34 |
|
* ashimema |
seems to always be juggling too many projects in Koha . |
| 06:34 |
|
dcook |
Hard relate |
| 06:34 |
|
dcook |
Plus other projects.. |
| 06:34 |
|
* dcook |
laughs and cries at the same time |
| 06:35 |
|
dcook |
But yeah it would be cool to use either Apache or Nginx.. |
| 06:35 |
|
dcook |
And have koha-create automagically handle it.. |
| 06:35 |
|
ashimema |
Exactly |
| 06:36 |
|
dcook |
Although.. |
| 06:36 |
|
dcook |
I think you'd still need to default to one |
| 06:36 |
|
dcook |
maybe something in /etc/default/koha to choose which webserver you want to use |
| 06:36 |
|
Joubu |
"misc/release_notes/release_notes_20_11_00.md:> Two new Koha packages have been created: `koha-full` and `koha-core`;Â Both packages are currently considered as experimental, and are not recommended for production use until further notice. We will be testing them during the 20.11 release cycle." |
| 06:36 |
|
ashimema |
So koha-create and various other Debian scripts would come in the koha-nginx package for example.. instead of loha-core |
| 06:36 |
|
dcook |
So koha-apache and koha-nginx wouldn't be mutually exclusive.. |
| 06:36 |
|
Joubu |
who was this "we"? :D |
| 06:36 |
|
ashimema |
Ha |
| 06:37 |
|
dcook |
ashimema: Oh I don't know if I like that.. |
| 06:37 |
|
Joubu |
well, it should work, no need for other packages |
| 06:37 |
|
dcook |
Joubu: Maybe me and Tomas O_O |
| 06:37 |
|
dcook |
Optimistic I guess |
| 06:37 |
|
dcook |
Actually, that goes back to that earlier thing.. |
| 06:37 |
|
dcook |
koha-core would be great to use in ktd |
| 06:38 |
|
Joubu |
mtj[m] worked on that, and he knows what to do when it's package related |
| 06:38 |
|
dcook |
And then have a RabbitMQ container instead of in the same container.. |
| 06:38 |
|
Joubu |
I am trusting him for that |
| 06:38 |
|
marcelr |
could we stop with marc too soon ? |
| 06:38 |
|
dcook |
marcelr: I should send you this great Bibframe vs MARC meme I saw the other day.. |
| 06:39 |
|
ashimema |
Lol |
| 06:39 |
|
marcelr |
dcook not to talk about ifla-lrm |
| 06:40 |
|
marcelr |
that off switch is great |
| 06:40 |
|
dcook |
National libraries in Canada and Australia seem to be falling apart too.. |
| 06:40 |
|
dcook |
How about other countries? |
| 06:40 |
|
dcook |
Australia they're cutting services and raising prices |
| 06:40 |
|
dcook |
I've heard from friends in Canada that they're having massive cuts as well |
| 06:40 |
|
marcelr |
i heard such things from US |
| 06:41 |
|
dcook |
That's scary.. |
| 06:41 |
|
marcelr |
Netherlands is always 50 years later |
| 06:41 |
|
dcook |
So they're funded for years yet? Hehe |
| 06:41 |
|
Joubu |
dcook: no account on gitlab? |
| 06:42 |
|
dcook |
Joubu: Me? |
| 06:42 |
|
wahanui |
it has been said that dcook is afraid I don't understand the question |
| 06:42 |
|
dcook |
Got that right... |
| 06:42 |
|
|
alex_ joined #koha |
| 06:42 |
|
dcook |
yeah nah I have an account |
| 06:42 |
|
dcook |
I'll share it with you |
| 06:43 |
|
dcook |
Joubu: ^ |
| 06:43 |
|
Joubu |
https://gitlab.com/koha-commun[…]cker/-/issues/297 |
| 06:44 |
|
dcook |
My stats look way worse without the private projects.. lol |
| 06:44 |
|
Joubu |
I've created this issue, but your name didn't autocomplete |
| 06:44 |
|
dcook |
Nice |
| 06:46 |
|
dcook |
Commenting now.. |
| 06:52 |
|
Joubu |
would be nice to have a roadmap for 22.11.. |
| 06:53 |
|
Joubu |
@later tell tcohen would be nice to start a roadmap for 22.11? |
| 06:53 |
|
huginn |
Joubu: The operation succeeded. |
| 06:54 |
|
marcelr |
how many percent of the 22.05 roadmap did we get in btw ? |
| 06:55 |
|
Joubu |
a 22.05 roadmap? |
| 06:55 |
|
marcelr |
yes |
| 06:56 |
|
marcelr |
didnt you create one |
| 06:56 |
|
Joubu |
I am not aware of any |
| 06:56 |
|
marcelr |
i think we should remove effective itemtype and that pref |
| 06:56 |
|
marcelr |
just to mention an example :) |
| 06:57 |
|
fridolin |
no sorry i did not made one |
| 06:57 |
|
Joubu |
inded, topic "My dev list for 22.05" on koha-devel |
| 06:57 |
|
marcelr |
fridolin: why use a roadmap if you know the way haha |
| 06:58 |
|
fridolin |
so much to do and so little time ;) |
| 06:58 |
|
Joubu |
marcelr: I had a look at it at the beginning of the cycle. I didn't write anything because of the rename of the DB column |
| 06:58 |
|
fridolin |
i hope more will be acheived in 22.11 |
| 06:58 |
|
Joubu |
and I understood it would be a nightmare to get it in, as it would break the reports |
| 06:58 |
|
Joubu |
and people are conservative when it comes to reports... |
| 06:59 |
|
marcelr |
dont touch my reports ! |
| 06:59 |
|
fridolin |
we add Recalls in the goals, it is in |
| 06:59 |
|
marcelr |
thats great |
| 06:59 |
|
Joubu |
marcelr: but you could go without the columns rename |
| 07:00 |
|
dcook |
Joubu: It looks like testing koha-core could actually be easier than I used to think.. |
| 07:00 |
|
Joubu |
apt install koha-core, yes that's easy :D |
| 07:01 |
|
|
cait joined #koha |
| 07:04 |
|
dcook |
If you've already installed koha-common, I think you'll have fun |
| 07:04 |
|
marcelr |
and fridolin we have 2FA ! |
| 07:04 |
|
* dcook |
had to do an interesting mix of install/uninstall to install koha-common after koha-core had been installed.. |
| 07:04 |
|
marcelr |
fridolin the brave RM that pushed Recalls and 2FA ! |
| 07:05 |
|
marcelr |
koha-common should be renamed to koha-fun |
| 07:05 |
|
marcelr |
only to be installed in a container |
| 07:06 |
|
dcook |
I have thought a bit lately of trying to run a Koha in containers in prod but.. haven't had the guts yet |
| 07:06 |
|
dcook |
And time is going so fast. Too bad talking to you folk instead of finishing up work :p |
| 07:09 |
|
marcelr |
dcook: i am running Koha for years in containers |
| 07:09 |
|
marcelr |
in prod |
| 07:09 |
|
dcook |
marcelr: Oh cool. How many instances do you have? Is it just the one? |
| 07:09 |
|
marcelr |
yeah i only do rijks |
| 07:09 |
|
dcook |
That's so cool |
| 07:10 |
|
dcook |
I have a lot of instances running across a bunch of servers.. so try to keep them all on the same model and not too adventurous. |
| 07:10 |
|
dcook |
But I keep thinking about singling one out... |
| 07:10 |
|
dcook |
How do you handle the DB? |
| 07:10 |
|
dcook |
Container as well or separate DB server or? |
| 07:10 |
|
marcelr |
sql container |
| 07:11 |
|
dcook |
Named volume for the data volume? |
| 07:11 |
|
marcelr |
right |
| 07:11 |
|
dcook |
Cool |
| 07:11 |
|
dcook |
What about for /var/lib and /etc/koha? |
| 07:11 |
|
dcook |
/var/lib/koha* |
| 07:11 |
|
marcelr |
var/lib is on a volume too |
| 07:11 |
|
marcelr |
etc/koha isnt |
| 07:11 |
|
dcook |
I just haven't put all the thought into what needs to be mounted volumes and what can just be image |
| 07:12 |
|
marcelr |
var/log could be too but i didnt |
| 07:12 |
|
marcelr |
i pull the logs from it every night |
| 07:12 |
|
dcook |
How do you handle the koha-conf.xml? |
| 07:13 |
|
marcelr |
my docker setup is mangling extensively with it |
| 07:13 |
|
dcook |
Hehe |
| 07:13 |
|
marcelr |
all sed |
| 07:13 |
|
dcook |
Have you talked to Tomas about it? |
| 07:13 |
|
marcelr |
no i dont talk to him lol |
| 07:13 |
|
dcook |
I know he and Agustin were doing a bunch with Docker/Kubernetes a while back.. |
| 07:13 |
|
dcook |
No? Haha |
| 07:13 |
|
marcelr |
kidding |
| 07:13 |
|
dcook |
I was wondering if I'm just that oblivious... |
| 07:14 |
|
marcelr |
my setup keeps me away from ktd |
| 07:14 |
|
dcook |
Oh I meant for Theke stuff rather than ktd per se |
| 07:14 |
|
marcelr |
i have prod and test on same setup and master on similar setip |
| 07:15 |
|
marcelr |
setup |
| 07:17 |
|
dcook |
That's awesome |
| 07:17 |
|
dcook |
I have all my dev for everything in Docker so I'm always thinking it would be nice to start using Docker in prod.. |
| 07:18 |
|
dcook |
Use Docker for a lot of internal processes but not necessarily anything public facing.. |
| 07:18 |
|
dcook |
Oh that's not entirely true.. |
| 07:18 |
|
dcook |
Our Discourse is on Docker |
| 07:19 |
|
dcook |
Actually, I have a project where we need to execute a task once a month, and I set it up to run on AWS ECS.. it costs $0/month |
| 07:20 |
|
dcook |
It's great. I think there is a $0.01/month charge to host the Docker image in AWS ECR but that's pretty trivial |
| 07:20 |
|
dcook |
But yes roadmap! |
| 07:20 |
|
dcook |
I'm hoping to revisit OAI-PMH stuff, although I think it might just end up being local... |
| 07:21 |
|
dcook |
But happy to work on T::T WRAPPER, Vue3, Debian packaging.. |
| 07:21 |
|
marcelr |
i would say lets choose 6 things for the roadmap for 6 months |
| 07:21 |
|
dcook |
marcelr: I really like that idea |
| 07:21 |
|
Joubu |
choose ONE thing |
| 07:21 |
|
marcelr |
now everyone wants his stuff on the roadmap |
| 07:21 |
|
dcook |
Joubu: Ugh even better haha |
| 07:21 |
|
Joubu |
then choose another one when it's done |
| 07:21 |
|
marcelr |
and we end up with 22 things |
| 07:21 |
|
dcook |
marcelr: So true |
| 07:21 |
|
marcelr |
or 33 |
| 07:22 |
|
dcook |
And I'm guilty of that. I want my stuff on the roadmap but it's too pie in the sky |
| 07:22 |
|
* dcook |
is a dreamer... |
| 07:22 |
|
dcook |
But yes... I'm all for a RM with an iron fist |
| 07:22 |
|
marcelr |
dcook you could be RM |
| 07:22 |
|
dcook |
marcelr: I think about it sometimes |
| 07:22 |
|
marcelr |
you have all the qualities |
| 07:22 |
|
* dcook |
waits for the punch line |
| 07:22 |
|
marcelr |
2023 is your year |
| 07:23 |
|
marcelr |
23.05 and 23.11 |
| 07:23 |
|
wahanui |
46.16 |
| 07:23 |
|
marcelr |
haha |
| 07:23 |
|
marcelr |
who taught you that wahanui |
| 07:23 |
|
dcook |
Sometimes I do wonder how I'd manage as RM |
| 07:24 |
|
dcook |
"Sorry everyone. Your patches shall be ignored, because it doesn't adhere to my roadmap where I want to move through things 1 by 1." |
| 07:24 |
|
Joubu |
badly if you don't have time |
| 07:24 |
|
dcook |
^ |
| 07:24 |
|
dcook |
I'd be famous like Nero for all the wrong reasons... |
| 07:24 |
|
dcook |
23.05 is that release where dcook just let everyone down |
| 07:24 |
|
dcook |
"Let them eat code" |
| 07:24 |
|
dcook |
I may be mixing up my rulers... |
| 07:25 |
|
marcelr |
its a great theme |
| 07:26 |
|
ashimema |
RM is challenging... Like herding cats |
| 07:26 |
|
ashimema |
And you can lead a horse to water but can't make it srink |
| 07:26 |
|
ashimema |
Drink . Even.. haha |
| 07:26 |
|
marcelr |
shrinking a horse ? |
| 07:27 |
|
marcelr |
Shrink a horse, install Koha 23.05 ! |
| 07:27 |
|
ashimema |
I'd love for a roadmap to be globally agreed and adhered too.. but have come to the conclusion that there are just too many parties moving in so many different directions |
| 07:27 |
|
|
cait joined #koha |
| 07:27 |
|
Joubu |
Can't make it drink, neither with carrots or sticks :D |
| 07:27 |
|
ashimema |
You can usually get concentration on the side for at least one, maybe two projects per cycle |
| 07:28 |
|
ashimema |
The rest of the stuff that goes in is really just what happens happens |
| 07:28 |
|
marcelr |
sure |
| 07:28 |
|
marcelr |
but you could have a focus on one item for a month or so ? |
| 07:28 |
|
Joubu |
not if you are alone |
| 07:28 |
|
Joubu |
well, at least not me, not anymore |
| 07:28 |
|
marcelr |
Joubu your stuff always gets in |
| 07:28 |
|
ashimema |
As Joubu said.. pick one thing, grab a group of interested parties and keep pushing on that one thing till it's in.. then move on to your next thing.. seems to work better. |
| 07:28 |
|
ashimema |
As painful as it may be |
| 07:28 |
|
Joubu |
f**** rebases |
| 07:29 |
|
dcook |
I mean... there are a lot of parties moving in a lot of directions, but surely the RM will should matter above all? |
| 07:29 |
|
Joubu |
always? lol |
| 07:29 |
|
marcelr |
almost |
| 07:29 |
|
dcook |
That 1 thing at a time would be top priority |
| 07:29 |
|
dcook |
Could do a monthly newsletter. "This is what we're doing this month." |
| 07:29 |
|
dcook |
Actually, that's not a bad idea.. |
| 07:29 |
|
Joubu |
3 of us one the same thing at the same time is 10x faster than 3 of us one 3 different things |
| 07:30 |
|
dcook |
I have a non-Koha Perl project where we do have a monthly meeting to set the priorities for that month |
| 07:30 |
|
dcook |
Joubu: 100% |
| 07:30 |
|
ashimema |
Haha, not always dcook.. it's almost like politics.. terms are short so you tend to play nice with other people's stuff so you stand a chance of getting your own goals done |
| 07:30 |
|
cait |
ok, now I had to read back because I just came in on the horse comment |
| 07:30 |
|
ashimema |
Hmm, I'm game to try |
| 07:31 |
|
marcelr |
it was kind of not quiet here cait |
| 07:31 |
|
cait |
the problem is |
| 07:31 |
|
ashimema |
Devs tend to have managers with their own ideas though :p |
| 07:31 |
|
cait |
people don't get funding like that |
| 07:31 |
|
Joubu |
Aren't we tryiing that for years? :D |
| 07:31 |
|
cait |
they don't get funding to push a month on someone else's priority... |
| 07:31 |
|
ashimema |
Indeed |
| 07:31 |
|
cait |
gathering interested parties and keep the number of 'big building sites' low still woudl be a nice thing |
| 07:31 |
|
marcelr |
point is too that a long roadmap is the same as no roadmap |
| 07:31 |
|
ashimema |
How international is your other project dcook |
| 07:32 |
|
ashimema |
And how many stakeholders are there? |
| 07:32 |
|
dcook |
ashimema: Shhh :p |
| 07:32 |
|
dcook |
Such an interesting conversation but I have to take a call.. |
| 07:32 |
|
marcelr |
sure |
| 07:32 |
|
ashimema |
Haha |
| 07:32 |
|
dcook |
It's true that's not how funding works but I think that still comes down to priorities |
| 07:32 |
|
dcook |
People are free to work on whatever they want to work on |
| 07:33 |
|
cait |
well, but they aren't |
| 07:33 |
|
dcook |
And that's just part of the loose community |
| 07:33 |
|
cait |
not here at least.. mostly |
| 07:33 |
|
dcook |
Like my boss pays me to work on stuff which may never make it in and that's just life |
| 07:33 |
|
dcook |
But for us to come together as a community (at least of core contributors?) and make some priorities.. |
| 07:33 |
|
dcook |
I'm sure I'd be more useful doing a bit of work on a RM priority here and there rather than just spinning my wheels on my own dream projects... |
| 07:34 |
|
cait |
well, I am maybe slightly too negative, I gues smost of us do get some time for community only, but I know that customer demands can quickly take away from that time |
| 07:34 |
|
dcook |
I have no time for community only hehe |
| 07:34 |
|
* dcook |
has replaced coding on his own time with Muay Thai... |
| 07:35 |
|
dcook |
I think I find just some moments here and there |
| 07:35 |
|
dcook |
Anyway, don't mind me heh |
| 07:35 |
|
* dcook |
takes his call |
| 07:35 |
|
ashimema |
I build it into our contracts now.. but even then it's hard |
| 07:36 |
|
dcook |
Oh I think I understand.. |
| 07:36 |
|
dcook |
ashimema: You mean client contracts? |
| 07:36 |
|
dcook |
And cait do you mean funding in terms of people being paid by clients to work on projects? |
| 07:38 |
|
ashimema |
I mean employee contracts |
| 07:38 |
|
ashimema |
I'm in charge of hiring Devs now.. problem is.. they're all so expensive now |
| 07:40 |
|
ashimema |
Community work is now part of the job description |
| 07:41 |
|
ashimema |
School run time, bbiab |
| 07:42 |
|
ashimema |
We've changed tact.. going for small contracts now instead for a bit.. just to plug the gap |
| 07:43 |
|
ashimema |
My team is mostly on Aspen stuff in the immediate future though.. leaves just me juggling our koha commitments |
| 07:43 |
|
dcook |
:O |
| 07:43 |
|
dcook |
Aspen is taking off more outside the US? |
| 07:44 |
|
Nemo_bis |
https://www.aspeninstitute.org ? |
| 07:47 |
|
ashimema |
https://bywatersolutions.com/p[…]s/aspen-discovery |
| 07:47 |
|
ashimema |
It started as a vuFind fork but is much more now.. unrecognisable really |
| 07:48 |
|
ashimema |
Yeah, it's taking off in the UK. |
| 07:48 |
|
ashimema |
Has a lot of potential I think |
| 07:51 |
|
|
m23_ joined #koha |
| 08:02 |
|
dcook |
I haven't looked at Aspen in a while... |
| 08:03 |
|
dcook |
We've been doing our own discovery layer lately |
| 08:04 |
|
dcook |
Wow the Aspen team at Bywater has sure grown |
| 08:05 |
|
ashimema |
It's selling like crazy over there and we're not far behind.. pretty much everyone we show it to wants it. |
| 08:06 |
|
dcook |
Huh.. I'd like to hear more about that sometime |
| 08:06 |
|
dcook |
I'd be curious for some more technical notes on it |
| 08:07 |
|
dcook |
Must've been years ago I looked at it now that I think about it |
| 08:13 |
|
dcook |
ashimema: Is this the canonical repo? https://github.com/mdnoble73/aspen-discovery |
| 08:15 |
|
dcook |
Not loving that codebase.. |
| 08:15 |
|
* dcook |
wishes sometimes that there was more rigid guidelines for website codebase layouts.. |
| 08:15 |
|
ashimema |
Our Devs are finding a little challenging to get up to speed. But none of us has done much java in recent years |
| 08:16 |
|
dcook |
I was wondering about that 15.5% Java |
| 08:16 |
|
cait |
is that the solr/lucene bits? |
| 08:16 |
|
dcook |
Java is actually getting interesting again... not that I've coded much with it lately but I read stuff.. |
| 08:17 |
|
dcook |
Red Hat are pushing Quarkus and they've got Keycloak running on that lately |
| 08:17 |
|
dcook |
Apparently GraalVM is the new hotness.. |
| 08:18 |
|
dcook |
cait: I see some jars for "Turning Leaf Technologies"? |
| 08:18 |
|
dcook |
Interesting that they're storing JARs in the Git.. |
| 08:19 |
|
dcook |
Yeah I can see why it would take a while to get up to speed. There's a lot there... |
| 08:19 |
|
dcook |
Think we'll stick to our own discovery layer.. |
| 08:20 |
|
dcook |
I better run... but I'd be keen to see Joubu and marcelr 's idea of a few priorities come about |
| 08:21 |
|
dcook |
I still think a globally agreed to roadmap could be a good thing. While everyone has their own priorities, it would be nice to have a few things that are like the "theme" of the release or something... |
| 08:21 |
|
* dcook |
says hoping that those priorities align with his own interests >_> |
| 08:22 |
|
dcook |
Anyway, hope you all enjoy your day. Night night... |
| 08:32 |
|
ashimema |
everyone hopes those priorities align with their own. |
| 08:32 |
|
ashimema |
or more importantly.. their employers 😜 |
| 08:32 |
|
ashimema |
getting the companies on side is key really for a roadmap.. and we're getting better there slowly.. |
| 08:32 |
|
ashimema |
the big three talk to each other and collaborate more and more again in recent times. |
| 08:46 |
|
|
bshum joined #koha |
| 08:55 |
|
marcelr |
ashimema: The big three and the seven dwarfs only need a goalie |
| 09:02 |
|
|
simon_ joined #koha |
| 09:02 |
|
simon_ |
hi everyone |
| 09:02 |
|
simon_ |
i get an error when trying to upgrade from 19.05 to 21.11: |
| 09:02 |
|
simon_ |
Upgrading database schema for zenon {UNKNOWN}: DBI Exception: DBD::mysql::db do failed: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the m anual. You have to change some columns to TEXT or BLOBs at /usr/share/perl5/DBIx/Class/Schema.pm line 1118. DBIx::Class::Schema::throw_exception(Koha::Schema=HASH(0x55a12a5d11f8), "DBI Exception: DBD::mysql::db do failed: |
| 09:03 |
|
simon_ |
there is an exsting bug https://bugs.koha-community.or[…]_bug.cgi?id=28267 |
| 09:03 |
|
huginn |
Bug 28267: critical, P1 - high, ---, koha-bugs, NEW , Koha-common package upgrade problem from 20.05.xx to 20.11.04-1 |
| 09:04 |
|
Joubu |
saw comment 20? |
| 09:04 |
|
ashimema |
I think comment 15 is probably your best bet for a quick fix simon_ |
| 09:04 |
|
simon_ |
i ran ALTER TABLE `deleteditems` ROW_FORMAT=DYNAMIC; ALTER TABLE `items` ROW_FORMAT=DYNAMIC; |
| 09:04 |
|
ashimema |
sorry.. comment 20.. Joubu is right |
| 09:04 |
|
simon_ |
but it seems it is another table |
| 09:04 |
|
ashimema |
15 does it for one table.. 20 loops |
| 09:06 |
|
|
alohabot joined #koha |
| 09:06 |
|
simon_ |
ok so it is recommended to do that for all tables? |
| 09:06 |
|
ashimema |
I think i would |
| 09:06 |
|
ashimema |
fresh installs are done with dynamic for all |
| 09:10 |
|
simon_ |
ok thx |
| 09:14 |
|
|
magnuse_ joined #koha |
| 09:17 |
|
|
alex__ joined #koha |
| 09:53 |
|
|
magnuse__ joined #koha |
| 10:03 |
|
|
davidnind joined #koha |
| 10:18 |
|
simon_ |
after upgrading to 21.11 and elasticseach 7 i get the following message when running the rebuild with -d flag: |
| 10:19 |
|
simon_ |
Unable to update mappings for index "koha_test_biblios". Reason was: "Types cannot be provided in put mapping requests, unless the include_type_name parameter is set to true.". Index needs to be recreated and reindexedSomething went wrong rebuilding indexes for test. |
| 10:22 |
|
cait |
i think there were some elasticsearch 7 bugs around |
| 10:22 |
|
cait |
tuxayo: maybe? |
| 10:23 |
|
cait |
simon_: could it be bug 25669? |
| 10:23 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=25669 normal, P5 - low, ---, kevin.carnes, In Discussion , ElasticSearch 6: [types removal] Specifying types in put mapping requests is deprecated (incompatible with 7) |
| 10:24 |
|
cait |
people lean towards the alternatve patch -maybe something you coudl try |
| 10:24 |
|
cait |
It appears to be the only missing dependency from the elasticsearch 7 omnibus bug atm |
| 10:25 |
|
cait |
bug 25439 |
| 10:25 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=25439 critical, P5 - low, ---, koha-bugs, NEW , [Omnibus] Prepare Koha to ElasticSearch 7 - ES7 |
| 10:26 |
|
oleonard |
o/ |
| 10:27 |
|
oleonard |
Joubu: I've only looked quickly at Bug 30289. Too many other things going on to look in detail right now. |
| 10:27 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=30289 enhancement, P5 - low, ---, dcook, In Discussion , Use Template::Toolkit WRAPPER to reduce template boilerplate |
| 10:28 |
|
cait |
hi oleonard |
| 10:28 |
|
wahanui |
hi oleopard |
| 10:28 |
|
cait |
oleonard++ |
| 10:32 |
|
simon_ |
https://bugs.koha-community.or[…]_bug.cgi?id=25669 seems to be it |
| 10:32 |
|
huginn |
Bug 25669: normal, P5 - low, ---, kevin.carnes, In Discussion , ElasticSearch 6: [types removal] Specifying types in put mapping requests is deprecated (incompatible with 7) |
| 10:36 |
|
paulderscheid[m] |
Hi Koha, is it wrong to define new query parameters for new api-endpoints? I just re-read the api docs and am not quite sure what the q param is used for. |
| 10:37 |
|
ashimema |
q allows you to search on any exposed fields |
| 10:38 |
|
ashimema |
you read this https://api.koha-community.org[…]ltering-responses bit of the docs right? |
| 10:38 |
|
paulderscheid[m] |
yeah |
| 10:38 |
|
ashimema |
so q is a json encoded search query |
| 10:39 |
|
ashimema |
what query params are you wanting to add ? |
| 10:39 |
|
ashimema |
tcohen is the api pro.. but I may be able to guide |
| 10:40 |
|
cait |
paulderscheid[m]: unrelated question -will you be in Leipzig? |
| 10:42 |
|
paulderscheid[m] |
It's a whole bunch for 4 new endpoints that I created. These are all just basic integers and strings with a discernible name that I use in my controllers. |
| 10:42 |
|
paulderscheid[m] |
An example would be... (full message at https://matrix.org/_matrix/med[…]xodGKBKcsuQaMNPh) |
| 10:43 |
|
ashimema |
so it's a paging param basically |
| 10:43 |
|
ashimema |
do you actually need a new controller for it..? |
| 10:43 |
|
ashimema |
are there not already API's returning that data if passed the right query? |
| 10:44 |
|
paulderscheid[m] |
cait: No, but LMSCloud will be there at the EKZ booth. |
| 10:44 |
|
ashimema |
i.e. we do have a biblios endpoint |
| 10:44 |
|
paulderscheid[m] |
ashimema: Let me take a look |
| 10:48 |
|
cait |
paulderscheid[m]: I know, we have a booth as well - I plan to visit |
| 10:48 |
|
paulderscheid[m] |
ashimema: I needed a new controller for a new model that provides data based on position within itemcallnumbers. |
| 10:49 |
|
paulderscheid[m] |
cait: Yeah, I guessed that you already knew that. But i won't be there. |
| 10:50 |
|
cait |
I guessed so... but was still hoping to meet in person after missing out in Marseille - there will be another time |
| 10:50 |
|
ashimema |
you can order the query |
| 10:50 |
|
ashimema |
so wouldn't it just be a sort on call_number_sort ? |
| 10:51 |
|
ashimema |
tcohen may be able to offer some better guidance once he's about |
| 10:51 |
|
ashimema |
https://api.koha-community.org[…]tion/deleteBiblio |
| 10:51 |
|
ashimema |
we're bad at that area's of documentation still â˜¹ï¸ |
| 10:53 |
|
paulderscheid[m] |
ashimema: I should test that. |
| 10:53 |
|
paulderscheid[m] |
No problem, writing comprehensive documentation on that scale is always a pain. |
| 10:55 |
|
simon_ |
what is the best way to search bugzilla? its almost always that i try to search there, find nothing, come here and someone points me to a bug already existing :D |
| 10:55 |
|
paulderscheid[m] |
I'm just asking because I want to reduce redundancy as much as possible and use the way you intended. |
| 10:55 |
|
ashimema |
I have a feeling you may find the _match stuff helpful too.. |
| 10:55 |
|
ashimema |
like 'starts_with' instead of 'exact' match for example |
| 10:55 |
|
oleonard |
simon_: What are you looking for? |
| 10:55 |
|
ashimema |
no, it's great that you'r asking paulderscheid |
| 10:56 |
|
ashimema |
and if there's things missing it's certainly something we should account for.. your a real use case 🙂 |
| 10:56 |
|
simon_ |
i now got [illegal_argument_exception] Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [location__facet] in order to load field data by uninverting the inverted index. when running an intranet search |
| 10:56 |
|
ashimema |
tomas and I are always looking for feedback so we can improve this stuff to work for people |
| 10:56 |
|
simon_ |
(plack-intranet-error.log) |
| 10:57 |
|
ashimema |
wow.. |
| 10:57 |
|
paulderscheid[m] |
ashimema: Thanks for the pointers. I'm gonna evaluate if these fit my use case. |
| 10:57 |
|
ashimema |
did I just read that right.. |
| 10:57 |
|
ashimema |
we have 'get biblio'.. but haven't implimented 'list' for bibs yet? |
| 10:57 |
|
ashimema |
that's a massive oversight |
| 10:58 |
|
paulderscheid[m] |
ashimema: Would be kinda helpful ^^ |
| 10:58 |
|
cait |
we have a few 'holes' |
| 10:58 |
|
cait |
like we can list checkout setc. but we can't make one :) |
| 10:59 |
|
cait |
recently ran into that for a workshop question |
| 10:59 |
|
ashimema |
I suppose it's not been a dire need because many people already use the sru or other things for that. |
| 10:59 |
|
cait |
maybe |
| 10:59 |
|
davidnind |
https://bugs.koha-community.or[…]_bug.cgi?id=30790 |
| 10:59 |
|
huginn |
Bug 30790: enhancement, P5 - low, ---, julian.maurice, Needs Signoff , Add REST API route to list biblios |
| 11:00 |
|
ashimema |
well.. we should probably get working on it somehow.. I suppose it's a much more complicated case because it's not DB fields as much as it's a whole search engine |
| 11:01 |
|
ashimema |
oh cool |
| 11:05 |
|
tcohen |
hola #koha |
| 11:10 |
|
tcohen |
jajm++ # bib routes |
| 11:13 |
|
ashimema |
we don't have any guidelines as to when a patron name should be linked vs not linked do we |
| 11:13 |
|
ashimema |
or consistency guidelines on what forms should be used in various locations? |
| 11:14 |
|
oleonard |
I would say patron names should usually be linked unless there's a compelling reason not to |
| 11:15 |
|
oleonard |
I'm not sure I understand your second question |
| 11:15 |
|
ashimema |
so for the first one... |
| 11:15 |
|
ashimema |
take the 'Set patron permissions' page.. |
| 11:16 |
|
ashimema |
we embed the patron name into the breadcrumb.. the overall link is to the current page -- seems sane to me |
| 11:16 |
|
ashimema |
we also add the name into the 'h1' |
| 11:16 |
|
ashimema |
in that case it's not linked.. |
| 11:16 |
|
ashimema |
should it be? |
| 11:17 |
|
ashimema |
as for the second question |
| 11:17 |
|
oleonard |
My practice is to avoid links in headings |
| 11:17 |
|
ashimema |
I agree oleonard.. so that would be a good rule to have |
| 11:17 |
|
ashimema |
or guideline I mean |
| 11:17 |
|
ashimema |
the other half of the question is around all the options one can now send to the patron-title.inc |
| 11:18 |
|
oleonard |
The patron permissions page breadcrumbs would be improved by an additional link between "Patrons" and "Set permissions..." which links to the patron |
| 11:18 |
|
|
davidnind left #koha |
| 11:19 |
|
ashimema |
there's a bunch of options listed here: https://bugs.koha-community.or[…]_bug.cgi?id=30568 |
| 11:19 |
|
jajm |
tcohen, not sure if they follow best practices but hey, it works :) i'm open to suggestions |
| 11:19 |
|
huginn |
Bug 30568: enhancement, P5 - low, ---, koha-bugs, NEW , Make patron name fields more flexible |
| 11:19 |
|
ashimema |
which is the omnibus I'm working on at the minute |
| 11:19 |
|
tcohen |
jajm: that can be worked on as a team |
| 11:19 |
|
tcohen |
and we need more fine-grained guidelines written |
| 11:20 |
|
ashimema |
so you would put `Home > Patrons > Patron name > Set permissions` oleonard? |
| 11:20 |
|
tcohen |
Joubu: I'll try to work on the roadmap over the weekend, I'm open to suggestions |
| 11:21 |
|
ashimema |
I think I like that.. would be great to go through and make those breadcrumbs more consistent like this |
| 11:21 |
|
oleonard |
the problem with breadcrumbs on patron pages is that we have two options for what is the "canonical" view for patrons. The checkout page (the practical option) or the detail page (the technically-correct option) |
| 11:21 |
|
ashimema |
true |
| 11:22 |
|
ashimema |
so maybe that's one for another bug.. lol |
| 11:22 |
|
oleonard |
At one time I tried to create a preference for picking one or the other views as default, but that effort died |
| 11:22 |
|
ashimema |
but still.. do you have any thoughts on when patron-title should be called with 'no_title' for example |
| 11:22 |
|
|
m23 joined #koha |
| 11:23 |
|
ashimema |
I personally think we could perhaps limit ourselves to two clear options 'concise' and 'full' |
| 11:23 |
|
ashimema |
with 'no_html' or 'no_link' options on them on top? |
| 11:24 |
|
ashimema |
ha.. that's kinda where I'm going with this.. but the first step I believe is to actually get our use of patron-title.inc happening everywhere |
| 11:24 |
|
ashimema |
problem I'm running in to is there are so many options and it becomes a bit of a minefield trying to pick |
| 11:24 |
|
oleonard |
Yeah that list of options is... long |
| 11:24 |
|
ashimema |
and growing 😜 |
| 11:25 |
|
oleonard |
My gut reaction is to say that we should have two main ways to display patron names: "Full details" used in headings/subheadings, and "Brief details" used in links. |
| 11:25 |
|
oleonard |
But obviously that is an oversimplification. |
| 11:26 |
|
ashimema |
so you pretty much are agreeing with my 'concise' and 'full' options |
| 11:26 |
|
oleonard |
(within those two primary modes, you would also have surname,firstname or firstname surname |
| 11:26 |
|
oleonard |
) |
| 11:27 |
|
ashimema |
see.. I don't think we should give that as an option on the include.. but rather make that a global pref |
| 11:27 |
|
ashimema |
so 'concise' might be 'firstname surname' OR 'surname, firstname' depending on the pref value |
| 11:27 |
|
ashimema |
but it would be consistent everywhere.. rather than each template picking the order |
| 11:28 |
|
oleonard |
Yeah I could see there being no surname,firstname option for the full option, since it would be generally used in headings |
| 11:28 |
|
ashimema |
yup, seems sensible to me |
| 11:29 |
|
oleonard |
the brief surname,firstname option is, to me, the "data" view. Where names are used as data rather than in a natural-language context |
| 11:29 |
|
ashimema |
in fact.. I'm kinda thinking the pref would be for the two formats.. but would just be an open tt or otherwise customisable format based on patron fields |
| 11:30 |
|
ashimema |
so if they really wanted 'full' to be 'title firstname middlename surname (othernames) - preferedname [cardnumber]' they could. |
| 11:30 |
|
ashimema |
haha |
| 11:31 |
|
oleonard |
Did you make up "preferredname" or did I miss a bug report? |
| 11:32 |
|
ashimema |
that is a bug |
| 11:36 |
|
oleonard |
We've always treated othernames as preferredname |
| 11:37 |
|
ashimema |
bug 28633 |
| 11:37 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=28633 enhancement, P5 - low, ---, nick, Failed QA , Add a preferred_name field and an effective_name method to patrons |
| 11:37 |
|
ashimema |
yeah, it's failed qa right now |
| 11:37 |
|
ashimema |
because a) it's confusing and b) i'm not really sure about the implementation details.. it feels rather funky |
| 11:43 |
|
|
oleonard_ joined #koha |
| 11:43 |
|
oleonard_ |
oi |
| 11:47 |
|
oleonard |
Yeah you better run |
| 11:52 |
|
oleonard |
Why does this kill my ktd? "koha-koha-1 | Database is not empty! at /kohadevbox/misc4dev/populate_db.pl line 101." |
| 11:53 |
|
oleonard |
it kills koha-koha-1 anyway. |
| 11:53 |
|
paulderscheid[m] |
Did you 'kd'? |
| 11:54 |
|
oleonard |
I Ctrl-C'ed it, did not then 'kd' |
| 11:54 |
|
paulderscheid[m] |
You should |
| 11:55 |
|
domm[m] |
Hey, me again with another weird question: |
| 11:55 |
|
domm[m] |
Our librarians want to store the plain ISBN and an ISBN with dashes, both in 020, where the normal ISBN goes into 020$a, and the dashed ISBN into 020$9 (as suggested here https://koha-wiki.thulb.uni-je[…]buchnummer-isbn/) |
| 11:55 |
|
domm[m] |
But when they only enter something in 020$9, it is not stored, only when there is some value in any other 020 subfield. |
| 11:55 |
|
domm[m] |
I also tested this with 022$9, same effect |
| 11:56 |
|
domm[m] |
is there some internal magic that deletes $9 if no other subfield is set? |
| 11:56 |
|
domm[m] |
This would make sense as $9 is often used to store koha-ids.. |
| 11:56 |
|
domm[m] |
So is the best solution to use a different subfield (thats not used in the MARC21 spec)> |
| 11:57 |
|
domm[m] |
(For fun, I added a subfield 020$7, and this field is stored even if there is no other data) |
| 12:00 |
|
simon_ |
do i need to set a elasticsearch mapping before running koha-elasticsearch --rebuild ? |
| 12:00 |
|
caroline |
domm[m], it seems like a bugs, but is there a particular reason for storing the ISBN both with and without hyphens? |
| 12:02 |
|
domm[m] |
caroline: huh, no idea, I guess it's only a cosmetic issue. |
| 12:02 |
|
domm[m] |
simon_: Koha comes with default elasticsearch mappings |
| 12:02 |
|
simon_ |
currently elasticsearch has no indices |
| 12:03 |
|
domm[m] |
Did you run rebuild_elasticsearch.pl ? |
| 12:03 |
|
domm[m] |
I think they will be created during the first run |
| 12:03 |
|
simon_ |
i run sudo koha-elasticsearch --rebuild -v -p 2 <name> |
| 12:04 |
|
simon_ |
current result is |
| 12:04 |
|
simon_ |
[9188] Checking state of biblios index Unable to update mappings for index "koha_zenon_biblios". Reason was: "Types cannot be provided in put mapping requests, unless the include_type_name parameter is set to true.". Index needs to be recreated and reindexedSomething went wrong rebuilding indexes for zenon |
| 12:06 |
|
domm[m] |
What version of ES are you using? |
| 12:06 |
|
simon_ |
7.17.3 |
| 12:06 |
|
simon_ |
but i upgraded from 5 |
| 12:06 |
|
simon_ |
so i deleted the old indices |
| 12:06 |
|
domm[m] |
ok, I think Koha only works with 6 |
| 12:07 |
|
domm[m] |
ES did some incompatible changes between 6 and 7 |
| 12:07 |
|
domm[m] |
AFAIK there is work going on to make Koha work with 7 (and later) |
| 12:07 |
|
simon_ |
ah ok, did i misread https://koha-community.org/koh[…]1-11-05-released/ ? |
| 12:07 |
|
domm[m] |
And the error you posted falls exactly into these changes... |
| 12:08 |
|
simon_ |
ok, then i'll try a downgrade |
| 12:08 |
|
domm[m] |
oh, ok, sorry, we're still on 21.05 |
| 12:09 |
|
domm[m] |
So maybe that's a bug in the Koha/ES7 integration |
| 12:10 |
|
domm[m] |
See (maybe?) also here: https://bugs.koha-community.or[…]_bug.cgi?id=25669 |
| 12:10 |
|
huginn |
Bug 25669: normal, P5 - low, ---, kevin.carnes, In Discussion , ElasticSearch 6: [types removal] Specifying types in put mapping requests is deprecated (incompatible with 7) |
| 12:23 |
|
ashimema |
oh.. we probably still need our 22.11 release team patch before release.. |
| 12:27 |
|
oleonard |
I wonder why we never added MARC documentation links to the authority record editor... |
| 12:27 |
|
ashimema |
an oversighT? |
| 12:28 |
|
caroline |
I could've sworn they were there... |
| 12:29 |
|
caroline |
I remember when MarcFieldDocURL was added, I had noticed it didn't work with authority fields |
| 12:32 |
|
oleonard |
Oh look at that... Bug 10941 |
| 12:32 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=10941 enhancement, P5 - low, ---, tomascohen, NEW , MARC21 documentation links while adding an authority |
| 12:44 |
|
ashimema |
bug 30808 🙂 |
| 12:44 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=30808 normal, P5 - low, ---, martin.renvoize, Needs Signoff , Release team 22.11 |
| 12:46 |
|
|
marie-luce joined #koha |
| 12:56 |
|
|
Dyrcona joined #koha |
| 12:57 |
|
tcohen |
hi #koha. for the release notes |
| 12:58 |
|
tcohen |
do you think we could set some thereshold, like, 70% after which we consider translations complete |
| 12:58 |
|
tcohen |
and then we have two lists: 'Koha is translated into this languages' and 'partially translated into this languages' |
| 12:58 |
|
tcohen |
without the percentage? |
| 12:59 |
|
tcohen |
we've been struggling with translating the daily quotes into spanish, to put an example |
| 12:59 |
|
tcohen |
and it is so silly to say it is 99% translated |
| 13:00 |
|
tcohen |
and now we have the whole bunch of UNIMARC framework labels... which will clearly make this worse |
| 13:00 |
|
* oleonard |
thinks translating quotes from terrible US presidents is not worth anyone's time |
| 13:03 |
|
tcohen |
heh |
| 13:03 |
|
tcohen |
and UNIMARC? |
| 13:03 |
|
wahanui |
i heard UNIMARC was UNIMARC ... |
| 13:03 |
|
tcohen |
which no spanish-speaking library uses? |
| 13:07 |
|
oleonard |
Perhaps... Exclude UNIMARC from the percentage unless the language is fr-* ? |
| 13:11 |
|
tcohen |
I think we hurt ourselves (the project image) with nonsense with those percentages |
| 13:11 |
|
tcohen |
above X should me marked as 'translated into' and lower 'partially translated into' |
| 13:12 |
|
tcohen |
and maybe a link to pootle for each language so people can check completion and even get encouraged to complete it |
| 13:16 |
|
oleonard |
It sounds like a good idea to me, but I'm not someone who has faced the prospect of installing partially-translated software |
| 13:17 |
|
* oleonard |
bbl |
| 13:18 |
|
|
Dyrcona joined #koha |
| 13:24 |
|
tcohen |
oleonard-away: right, but what do we call partially? |
| 13:27 |
|
ashimema |
I feel like quote of the day should be moved |
| 13:29 |
|
ashimema |
feels like they could go from en/optional into localization/en-US |
| 13:29 |
|
ashimema |
and that would get rid of them from the translation debt |
| 13:29 |
|
ashimema |
that's an easy win |
| 13:35 |
|
|
lukeg joined #koha |
| 13:36 |
|
oleonard |
ashimema: I agree 100% |
| 13:36 |
|
Joubu |
tcohen: I was suggesting yesterday to cait that we could retrieve the % for the 10 entries, add the 9 that are not framework, the /9 |
| 13:37 |
|
Joubu |
https://translate.koha-community.org/de/22.05/ |
| 13:37 |
|
Joubu |
that would show as "100% translated except unimarc framework" |
| 13:37 |
|
ashimema |
@quote 123 |
| 13:37 |
|
huginn |
ashimema: I've exhausted my database of quotes |
| 13:37 |
|
oleonard |
@quote get 123 |
| 13:37 |
|
huginn |
oleonard: Quote #123: "rangi: #thingsihavelearnt if there is a mad scheme a library somewhere will be doing it ... except madder" (added by wizzyrea at 09:20 PM, March 30, 2011) |
| 13:37 |
|
wahanui |
i already had it that way, huginn. |
| 13:37 |
|
Joubu |
the*n* /9 |
| 13:37 |
|
tcohen |
Joubu: I like that. Still feel like the percentage is misleading, for those above 90% |
| 13:38 |
|
tcohen |
specially around 99% |
| 13:38 |
|
tcohen |
haha |
| 13:38 |
|
Joubu |
I don't understand, you want to show "fully translated" when it's actually "partially translated" |
| 13:39 |
|
Joubu |
and "partially" when it's "almost not translated".. |
| 13:39 |
|
Joubu |
translate to 100% and you will get 100% :D |
| 13:39 |
|
Joubu |
(if you exclude unimarc fws) |
| 13:39 |
|
cait |
quotes = moving them would make sense, we actually just copied them as I didn't want to risk a wrong trnslation of a famous quote someone actually said. |
| 13:39 |
|
cait |
UNIMARC/MARC21 = Maybe we should not count frameworks in general? |
| 13:39 |
|
ashimema |
I think rather than fudge the percentages we should go through and move things out that don't make sense to translate.. and do what Joubu said above about framework. |
| 13:39 |
|
cait |
For a lot of users it might be interesting to see OPAC vs. staff actually |
| 13:40 |
|
oleonard |
That's a good point cait |
| 13:40 |
|
ashimema |
very good point cait |
| 13:40 |
|
cait |
we get asked about that: can we activate the OPAC in... ? |
| 13:41 |
|
cait |
also complete and partial make sense |
| 13:41 |
|
Joubu |
Don't *-messages-js.po and *-messages.po contain strings for both opac and staff? |
| 13:41 |
|
cait |
but looking at opac files might list some more langauges, that fall out right now |
| 13:42 |
|
cait |
yes, but they are a small percentage of strings |
| 13:42 |
|
Joubu |
yes, but supposed to be used more widely |
| 13:42 |
|
cait |
so we could either not count them or count them for both and they woudl probably not have a huge effect |
| 13:42 |
|
* ashimema |
like |
| 13:43 |
|
cait |
sorting on pootle is broken :) but: |
| 13:43 |
|
cait |
https://translate.koha-community.org/de/22.05/ |
| 13:43 |
|
cait |
staff alone is roughly 50% I'd day? |
| 13:43 |
|
cait |
so if we split... we would promote people who have done the work for OPAC; which I'd really like |
| 13:44 |
|
cait |
doing the staff side... is a quite gigantic task |
| 13:47 |
|
tcohen |
Maybe I'm too pragmatic at the moment, but I feel like the release notes contain too much noise |
| 13:47 |
|
tcohen |
and those percentages, in general, are noise |
| 13:48 |
|
tcohen |
I will go do my 100% for es-ES with bgkriegel, that's not the problem |
| 13:48 |
|
ashimema |
lets really improve the release notes stuff next cycle 😉 |
| 13:51 |
|
tcohen |
no, lets change everything last minute before the release, what could go wrong LOL |
| 13:53 |
|
ashimema |
are we safe to switch bug 30275 back to PQA Joubu? |
| 13:53 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=30275 enhancement, P5 - low, ---, martin.renvoize, Signed Off , Checkout renewals should be stored in their own table |
| 13:53 |
|
domm[m] |
caroline: It seems that DNB (German National Library) also uses 020$9 for ISBNs-with-hyphen, and we use their SRU for cataloguing. |
| 13:53 |
|
ashimema |
before I forget about it again.. haha |
| 13:54 |
|
domm[m] |
So is this a known bug (020$9 being deleted if there is no data in other subfields)? or shall I report a new one? |
| 13:54 |
|
ashimema |
report it.. bugzilla will try and find a dupe for you when you try to come up with a title line for it |
| 13:55 |
|
Joubu |
ashimema: I guess so, haven't done a full review however but it was PQA already |
| 13:55 |
|
ashimema |
I'm happy to wait.. was more of a 'what state are we at with it' |
| 13:55 |
|
Joubu |
switch back to PQA |
| 13:55 |
|
ashimema |
ta 🙂 |
| 14:00 |
|
|
alex_ joined #koha |
| 14:02 |
|
domm[m] |
ashimema: here you go: https://bugs.koha-community.or[…]_bug.cgi?id=30812 |
| 14:02 |
|
huginn |
Bug 30812: normal, P5 - low, ---, koha-bugs, NEW , subfield 9 deleted if no other data is available |
| 14:02 |
|
ashimema |
brill, thanks 🙂 |
| 14:02 |
|
ashimema |
your up marcelr 😜 ^ |
| 14:46 |
|
|
Triveni joined #koha |
| 14:56 |
|
|
bag joined #koha |
| 15:17 |
|
cait |
tcohen: I agree with partial and complete, just think listing OPAC woudl give helpful info and award more languages |
| 15:19 |
|
cait |
domm[m] i believe they do a without and 9 with hyphens? at least that's how we get the data from our union catlaog. the $9 is a German agreement |
| 15:19 |
|
cait |
or german-spaking |
| 15:19 |
|
|
cait left #koha |
| 15:49 |
|
|
cait joined #koha |
| 15:50 |
|
ashimema |
@later tell fridolin bug 30730 might still be a candidate for release.. no strings changed and it's a major |
| 15:50 |
|
huginn |
ashimema: The operation succeeded. |
| 15:50 |
|
oleonard |
Bug 30730 |
| 15:50 |
|
huginn |
Bug https://bugs.koha-community.or[…]_bug.cgi?id=30730 major, P5 - low, ---, shi-yao.wang, Passed QA , Holds to Pull should not list items with a notforloan status |
| 15:50 |
|
ashimema |
it got my in a right brain melt |
| 15:50 |
|
ashimema |
but it's actually a really trivial patch in the end |
| 15:51 |
|
ashimema |
the prefs confuse things.. in this case I think they're all irrelevant in effect. |
| 15:51 |
|
ashimema |
though I'd love to clear that up in the pref descriptions/manual as cleary david found them confusing |
| 15:55 |
|
domm[m] |
cait: yes, ISBN without hypens is in 020$a, but when manually cataloguing, the seem to only fill out $9, which then is lost |
| 15:55 |
|
cait |
domm[m] i tihnk that's linked to the fact that Koha uses $9 for authorities somehow |
| 15:56 |
|
cait |
an authority link without $a woudl not make sense... but not sure what a fix could be if that's it |
| 15:56 |
|
cait |
maybe it would need to check if it's actually a field linked to an authority |
| 16:00 |
|
cait |
sorry, had to flee from the rain in between my previous comment and now :) |
| 16:19 |
|
oleonard |
I try to do just a small tweak or two to the additem template and fall down a deep rabbit hole |
| 16:24 |
|
|
oleonard_ joined #koha |
| 16:54 |
|
|
michal joined #koha |
| 17:20 |
|
reiveune |
bye |
| 17:20 |
|
|
reiveune left #koha |
| 17:34 |
|
michal |
hey guys, i keep trying to install koha but it keeps failing on me with the same error message |
| 17:35 |
|
oleonard |
How are you installing? |
| 17:35 |
|
michal |
i'm trying to run koha-testing-docker |
| 17:36 |
|
oleonard |
What is the host machine OS? And what is the error you're getting? |
| 17:36 |
|
michal |
i have koha cloned |
| 17:36 |
|
michal |
its a windows machine and I'm using docker |
| 17:36 |
|
michal |
here's the error message |
| 17:36 |
|
michal |
koha-db-1 | 2022-05-19 17:27:32 3 [Warning] Aborted connection 3 to db: 'unconnected' user: 'unauthenticated' host: '172.18.0.6' (This connection closed normally without authentication) |
| 17:36 |
|
michal |
koha-koha-1 | /kohadevbox/run.sh: /usr/sbin/koha-create: /bin/bash^M: bad interpreter: No such file or directory |
| 17:36 |
|
michal |
koha-koha-1 exited with code 126 |
| 17:37 |
|
oleonard |
I don't think I've seen that error before. I wonder if there are other koha-db-1 errors further back? |
| 17:38 |
|
michal |
i'll look |
| 17:41 |
|
michal |
no other errors for koha-db-1 |
| 17:42 |
|
michal |
i think there might be something with the koha-koha-1 error as well, because i'm not sure why it's trying to access bash^M instead of bash.eve |
| 17:42 |
|
michal |
bash.exe* |
| 17:44 |
|
oleonard |
I think that refers to bash inside the container, not on your host machine. I could be wrong. |
| 18:01 |
|
paulderscheid[m] |
Hi Michal, what version of Windows are you on? Maybe I can reproduce the problem. |
| 18:02 |
|
paulderscheid[m] |
Are you using Docker Desktop for Windows? michal |
| 18:03 |
|
michal |
I'm using windows 11 |
| 18:03 |
|
michal |
build 22621.1 |
| 18:05 |
|
michal |
also yes i'm using docker desktop |
| 18:06 |
|
paulderscheid[m] |
Ok, I have a machine running 22000.675 |
| 18:06 |
|
paulderscheid[m] |
Testing... |
| 18:06 |
|
wahanui |
testing is, like, important :) |
| 18:08 |
|
michal |
lol yeah it is |
| 18:08 |
|
michal |
let me know if the same thing happens |
| 18:30 |
|
michal |
0. |
| 18:33 |
|
|
davidnind joined #koha |
| 18:35 |
|
paulderscheid[m] |
I get the same error. |
| 18:35 |
|
paulderscheid[m] |
Let's find a solution. |
| 18:45 |
|
paulderscheid[m] |
The ^M is the carriage return on Windows. We'll have to parse that out of run.sh somehow. |
| 18:52 |
|
|
m23 joined #koha |
| 19:01 |
|
michal |
how can i access the run.sh file |
| 19:02 |
|
michal |
from docker, it says that the directories are copied from kohadevbox |
| 19:03 |
|
paulderscheid[m] |
It's copied from koha-testing-docker/files/run.sh |
| 19:03 |
|
paulderscheid[m] |
So you can edit this file. |
| 19:09 |
|
paulderscheid[m] |
Ah right, we can't edit the file there. Instead we have to generate a new koha image with run.sh already modified to be compatible with unix. |
| 19:09 |
|
paulderscheid[m] |
I'll test one other thing first, then I will try that. |
| 19:14 |
|
paulderscheid[m] |
Wait, no need. |
| 19:15 |
|
paulderscheid[m] |
I spun up a new wsl2 debian and did everything on the terminal. |
| 19:15 |
|
paulderscheid[m] |
Now it works. |
| 19:15 |
|
paulderscheid[m] |
I think it's important that you clone the repo on linux, so the unix like carriage return is used. |
| 19:16 |
|
paulderscheid[m] |
<paulderscheid[m]> "Ah right, we can't edit the file..." <- This would've probably failed. |
| 19:16 |
|
paulderscheid[m] |
paulderscheid[m]: by git |
| 19:17 |
|
michal |
so i should install the repo again but using wsl/ |
| 19:17 |
|
paulderscheid[m] |
michal: |
| 19:17 |
|
paulderscheid[m] |
right |
| 19:18 |
|
michal |
koha-testing-docker but not koha itself |
| 19:18 |
|
paulderscheid[m] |
do everything from within a linux instance on wsl2 |
| 19:18 |
|
paulderscheid[m] |
I cloned the koha repo again just to be safe. |
| 19:18 |
|
michal |
okay sounds good |
| 19:18 |
|
michal |
what about the db error |
| 19:19 |
|
paulderscheid[m] |
But you can set your environment vars to /mnt/c/and/so/on |
| 19:19 |
|
paulderscheid[m] |
michal: The db error always shows up. |
| 19:19 |
|
paulderscheid[m] |
At least for me. |
| 19:20 |
|
paulderscheid[m] |
If you see that zebra starts to index then the db is setup right. |
| 19:20 |
|
michal |
gotchu, so it should run fine with that error, it's the run.sh file that was messing up |
| 19:20 |
|
paulderscheid[m] |
Exactly |
| 19:21 |
|
michal |
perfect, i'll try reinstalling now |
| 19:21 |
|
paulderscheid[m] |
Ping me if it works now |
| 19:21 |
|
paulderscheid[m] |
I'm eager to know ^^ |
| 19:22 |
|
michal |
oki doki |
| 19:27 |
|
|
enkidu joined #koha |
| 20:03 |
|
|
liliputech joined #koha |
| 20:41 |
|
|
m23 joined #koha |
| 20:44 |
|
|
m23 joined #koha |
| 21:27 |
|
michal |
paulerscheid[m]: |
| 21:27 |
|
michal |
i've got a new error when i cloned the directory and set up koha-testing-docker again |
| 21:27 |
|
michal |
koha-koha-1 | Base class package "Auth::GoogleAuth" is empty. |
| 21:27 |
|
michal |
koha-koha-1 | (Perhaps you need to 'use' the module which defines that package first, |
| 21:27 |
|
michal |
koha-koha-1 | or make that module available in @INC (@INC contains: /kohadevbox/koha /kohadevbox/koha/lib /kohadevbox/qa-test-tools /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.32.1 /usr/local/share/perl/5.32.1 /usr/lib/x86_64-linux-gnu/perl5/5.32 /usr/share/perl5 |
| 21:27 |
|
michal |
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.32 |
| 21:27 |
|
michal |
/usr/share/perl/5.32 /usr/local/lib/site_perl). |
| 21:49 |
|
paulderscheid[m] |
That's odd. |
| 21:49 |
|
paulderscheid[m] |
It's almost midnight so I'll have to look into that tomorrow. |
| 21:51 |
|
paulderscheid[m] |
The error message basically says that a perl package called Auth::GoogleAuth isn't installed. |
| 21:51 |
|
paulderscheid[m] |
Never saw that one before. |
| 21:59 |
|
davidnind |
maybe do a docker-compose pull to get the latest images? |
| 22:10 |
|
|
michal joined #koha |
| 23:13 |
|
tuxayo |
michal: hi :) here are some notes I took from some people's experience to run ktd on Windows: https://gitlab.com/koha-commun[…]cker/-/issues/293 |
| 23:14 |
|
tuxayo |
My opinion is that if you have a Linux machine or dual boot or virtual machine that you are confortable to use, it's certain that running ktd on Linux will get you less issues. |
| 23:14 |
|
tuxayo |
If you never touched Linux, there is no obvious good path for ktd I think. |
| 23:17 |
|
dcook |
I try to be useful heh |
| 23:18 |
|
dcook |
Cloning on Windows has a few problems. One is line endings although Git can be configured to get around it. The real problem is file permissions if I recall correctly. |
| 23:29 |
|
michal |
yeah i remember you told me to get a virtual machine, i'm going to try it on there instead of with wsl2 |
| 23:50 |
|
tuxayo |
dcook: the notes on the ticket are your feedback, thanks again ^^ |
| 23:50 |
|
dcook |
tuxayo: Yeah I saw my name and smiled haha |
| 23:50 |
|
dcook |
I'm actually tempted to try wsl2 sometime.. |
| 23:51 |
|
dcook |
I've been using WSL since it came out, so I'm still on WSL1 on this machine.. |
| 23:51 |
|
dcook |
Although my Docker Desktop uses Hyper-V, because I've also been using Docker Desktop a very long time.. |
| 23:51 |
|
tuxayo |
dcook: «tempted to try wsl2» yes, if you know a way to roll back in case that break everything |
| 23:51 |
|
dcook |
tuxayo: Oh I meant WSL2 in general not for WSL2 heh |
| 23:52 |
|
dcook |
In terms of rolling back... I think it's quite a manual process |
| 23:52 |
|
dcook |
And it would vary from person to person |
| 23:52 |
|
dcook |
Since I use Docker Desktop for many things and not just Koha, it would be a huge process for me |
| 23:52 |
|
dcook |
I mean... I think I routinely backup about 5 Docker volumes, but there are so many images I wouldn't want to re-download... but backing those up also feels annoying... |
| 23:52 |
|
dcook |
All automatable but takes time and energy I suppose.. |
| 23:58 |
|
dcook |
Actually, I suppose the rollback would be similar to the migration anyway, so it's really just about downtime in the end.. |
| 23:59 |
|
tuxayo |
On the other hand before trying wsl2 stuff: everyone try on Linux first for the sake of libre software! And to stay away as much as possible from the horrible actor that is Microsoft. |
| 23:59 |
|
tuxayo |
I can't believe that I took time to try ktd on Windows with people. Microsoft took libre software (Linux and stuff) to make their WSL and now we are happily making efforts to stay confortable on the jail that is Windows to directly run Koha on it. Well done MS for making WSL to make people stay on Windows. |
| 23:59 |
|
* tuxayo |
is suddenly more lucid about the situation due to being the whole at a partly libre-software convention. |
