← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
Time | Nick | Message |
---|---|---|
00:07 | tuxayo | rangi[m] or gmcharlt around? I read that you have admin access to our Gitea. |
00:07 | rangi[m] | i dont |
00:08 | at least im 99% sure i dont | |
00:08 | only to gitlab | |
00:08 | tuxayo | lol then I can remove you from the list: https://wiki.koha-community.or[…]dministration#git.koha-community.org |
00:08 | The people locked outside at this hours won't come bother you :P | |
00:09 | *So people locked outside | |
00:09 | rangi[m] | lemme check if i can reset my password and get in |
00:09 | i think last time i tried this it never sent me the email to reset it | |
00:09 | tuxayo | thanks for checking 🙏 |
00:10 | rangi[m] | but will wait and see |
04:55 | Oak joined #koha | |
05:00 | PULibrary joined #koha | |
05:01 | oleonard joined #koha | |
06:23 | fridolin joined #koha | |
06:58 | fridolin1 joined #koha | |
07:28 | fridolin1 left #koha | |
07:41 | ashimema | I updated gittea for you tuxayo |
07:42 | reiveune joined #koha | |
07:42 | reiveune | hello |
07:49 | tuxayo | ashimema: thanks a lot! It goes a step further. Now it tell me "Gitea: Not allowed to push to protected branch 21.05.x" |
07:49 | ashimema | hmm |
07:50 | I need to reboot quickly, then will take another look | |
07:59 | ah.. looks to me like teams were updated but not the branches they're attached to | |
07:59 | I'm being called for breakfast.. will get that fixed as soon as I've eaten | |
08:01 | lds joined #koha | |
08:01 | thibaud_g joined #koha | |
08:01 | cait joined #koha | |
08:03 | cait1 joined #koha | |
08:04 | tuxayo | 👍️ |
08:04 | alex_ joined #koha | |
08:08 | ashimema | done tuzayo |
08:08 | tuxayo even | |
08:14 | Joubu | tuxayo: I removed you from 21.05 as you are not part of RMaint list for 23.05 |
08:14 | ashimema | except he hadn't done his final release yet Joubu |
08:15 | so I re-added him temporarily to get that one out of the door | |
08:15 | then we can remove again | |
08:15 | Joubu | yep, just explaining why he got removed ;) |
08:15 | ashimema | ah,, indeed |
08:15 | you were too efficient this change over.. hehe 🙂 | |
08:15 | Joubu | I didn't check everything was released, my bad |
08:15 | * ashimema | hand't actually noticed it hadn't been released yet either |
08:16 | ashimema | like I hadn't noticed we'd EOL U18 support with the release of 22.11 🙂 |
08:16 | I'm just fixing the dashboard to remove that build.. then I'll have a nice green row I hope | |
08:17 | tuxayo | My mistake, I only warned tomas and Mason that I still had some patch queue and a lot of BZ notification to sort in case of backport request. |
08:20 | Joubu | rangi[m]: you have admin access to gitea since the first day it has been installed ;) |
08:21 | admins on gitea are rangi[m], gmcharlt, ashimema, tcohen and me | |
08:25 | ashimema | I think he struggled to get in.. password reset didn't send an email |
08:28 | * ashimema | goes back to fighting with sandboxes... again |
08:29 | ashimema | something funky going on.. on all of them. |
08:31 | Joubu, do you remember.. what did you do to get https working on the biblibre sandboxes? | |
08:34 | Joubu | I have a "Issue #56" commit |
08:35 | Then I cannot remember, I think it's done at nginx level | |
08:36 | but not on this server, biblibre's sysop dealt with that | |
08:36 | ashimema | ah, I see |
08:36 | okies | |
08:41 | alex__ joined #koha | |
08:57 | tuxayo | > something funky going on.. on all of them. |
08:57 | indeed ashimema 😱😱😱 | |
08:58 | Triple redundancy doesn't do anything against big recent changes T_T | |
08:59 | ashimema | I may have just fixed the ptfs-e ines |
09:00 | Need to check the result when I get home | |
09:00 | Joubu | what's wrong with the sandboxes, |
09:00 | ? | |
09:02 | Emailing on git.koha-community.org should be fixed now. We are using gmail smtp but they disabled the auth by login/pwd. You now need a "App password". | |
09:07 | cait1 | Joubu: sandboxes don't come up - gives an error after finishing provisioning when you click on OPAC/staff - ashimema might know details, but it shows the same on bywater and ptfs-e ones |
09:08 | Joubu | ashimema: [webpack-cli] [Error: EACCES: permission denied, open '/kohadevbox/koha/koha-tmpl/intranet-tmpl/prog/js/vue/dist/main.js.LICENSE.txt'] { |
09:08 | I am seeing this | |
09:09 | ashimema: I think tcohen and I agreed on committing this file. I thought it was done actually | |
09:09 | We should ask Tomas to commit and push it | |
09:10 | I guess it will fix the problem | |
09:10 | tuxayo | Weird that it does a "EACCES: permission denied" |
09:15 | ashimema: «I may have just fixed the ptfs-e ines» nope :( | |
09:17 | ashimema | seems not |
09:17 | I've fixed one issue, but it's just highlighted another ☹️ | |
09:18 | I think ansible has changed some things beneath us | |
09:19 | the initial issue was that the python-apt packages was suddenly missing.. so all the apt: sections in the ansible yaml's were failing | |
09:20 | Joubu | ashimema: did you see the permission error? I am seeing this on biblibre's ones |
09:20 | ashimema | where are you seeing that error about licence.txt |
09:20 | Joubu | which one do you get on ptfs's? |
09:20 | ashimema | I see TASK [Checkout origin/master in docker container] ****************************** |
09:20 | fatal: [localhost -> koha-test]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo ~/.ansible/tmp `\"&& mkdir \"` echo | |
09:20 | ~/.ansible/tmp/ansible-tmp-1669884055.381836-20735-7675989363772 `\" && echo ansible-tmp-1669884055.381836-20735-7675989363772=\"` echo ~/.ansible/tmp/ansible-tmp-1669884055.381836-20735-7675989363772 `\" ), exited with result 1", "unreachable": true} | |
09:21 | in the provision logs | |
09:21 | Joubu | that's misleading |
09:21 | this error appears when the container crashes | |
09:21 | it's a generic error | |
09:21 | ashimema | ah.. ok |
09:21 | Joubu | you need to tail -f the container's log when it's running |
09:21 | docker logs koha-xxx -f | |
09:22 | the real error is the permission error | |
09:22 | but... why is it failing on sandboxes not on jenkins and or dev env? this is the weird bit | |
09:23 | ashimema | I had to install 'python-apt' package on the host to get past the first errors |
09:23 | Joubu | I would commit the LICENSE file, especially becasue it has a reference in main.js |
09:23 | ashimema | mm, very strange |
09:23 | Joubu | I discussed that with tcohen a couple of days ago, and I think we decided we should push it |
09:31 | ashimema: I pushed it | |
09:32 | @later tell tcohen I pushed the main.js.LICENSE.txt file, it may fix the sandboxes | |
09:32 | huginn | Joubu: The operation succeeded. |
09:33 | Joubu | @later tell tcohen I pushed the main.js.LICENSE.txt file, it may fix the sandboxes |
09:33 | huginn | Joubu: The operation succeeded. |
09:33 | Joubu | ooops |
09:34 | it passed the webpack step \o/ | |
09:36 | ashimema, tuxayo: fixed - https://staff-xxx.sandboxes.biblibre.eu/ | |
09:37 | ashimema | nice one |
09:37 | thanks Joubu | |
09:39 | cait1 | Joubu++ :) |
09:40 | tuxayo | Joubu++ |
09:40 | still something wrong with the ptfs-e one , 503 again on a fresh one | |
09:41 | alex_ joined #koha | |
09:42 | Joubu | It's looping, container is restarted |
09:42 | it happens when the container is not stopped because up | |
09:42 | something about port in apache config | |
09:43 | https://gitlab.com/koha-commun[…]ocker/-/issues/63 | |
09:44 | ashimema: I do have the "Issue #63 - Don't restart KTD container on startup error" commit applied | |
09:44 | ashimema | we should merge that.. |
09:45 | I'm just reading through.. I missed a bunch of these enhancements you made to ktd back when you made them ☹️ | |
09:45 | always so busy these days | |
09:45 | Joubu | well it won't fix the problem, but it will prevent the container to restart endlessly |
09:59 | ashimema | I've merged that one.. it's a sane change |
09:59 | and yeah.. at least it should expose the actual error for me. | |
10:00 | tuxayo | What should Kyle do for the ByWater sandboxes? Since it's wasn't just in Koha's code. |
10:04 | ashimema | I'll catch him later when he wakes up |
10:06 | lol.. | |
10:06 | your patch fixed it Joubu | |
10:07 | whatever the error was just went away when i pulled that | |
10:07 | weird | |
10:07 | Joubu | \o/ |
10:17 | tuxayo | Thanks Joubu and ashimema , I'm saved for tomorrow :) |
10:17 | ashimema | 🙂 |
10:18 | mtj | hi #koha |
10:18 | cait1 | hi mtj .) |
10:18 | ashimema | It was right at the top of my list for this morning to ensure you had working sandboxes for tomorrow 😛 |
10:18 | so glad Joubu jumped in though.. he saved me some real headaches 🙂 | |
10:18 | morning mtj | |
10:18 | cait1 | in case you didn't see it yesterday: thx for the translation fixed patches - got feedback from a library that updated right away that now all works again :) |
10:18 | mtj | bz 32349 |
10:18 | cait1 | well actually 2 libraries |
10:18 | ashimema | bug 32349 |
10:18 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=32349 enhancement, P5 - low, ---, jonathan.druart+koha, Needs Signoff , Remove TEST_QA |
10:24 | mtj | hi Joubu, patch for 32349 looks good :) |
10:24 | sandboxes are happy now? | |
10:24 | ashimema | they are for biblibre and ptfs-e |
10:24 | bywater will need to pull when they wake up 🙂 | |
10:27 | mtj | awesome |
11:32 | paulderscheid[m] | Check this out: https://chat.openai.com/chat |
11:32 | It has some problem, but is insane nevertheless 😳 | |
11:34 | oleonard | o/ |
11:37 | paulderscheid[m]: What is it? | |
11:38 | paulderscheid[m] | It's a Chatbot that uses OpenAI's GPT-model to answer any of your questions. |
11:39 | Just ask something about SCSS or Bootstrap, you'll be amazed. It just wrote my entire tsconfig.json | |
11:39 | oleonard | :O |
11:39 | paulderscheid[m] | It even explained some of the choices it made. |
11:41 | davidnind | Also see this example https://twitter.com/openlibrar[…]98235277558165504 |
11:45 | oleonard | paulderscheid[m]: That is very cool! |
11:46 | If we flood an incorrect answer on Stack Overflow with upvotes will it contaminate it's mind? :D | |
11:47 | paulderscheid[m] | It just told me, that the cutoff date for the data it has been trained on was late 2021. |
11:48 | * oleonard | uses this to write all my HARDCORE code at my new job at Twitter ;) |
11:48 | davidnind | LOL! |
11:48 | tuxayo | XD |
12:17 | tcohen | hola #koha |
12:27 | alex_ joined #koha | |
13:05 | cait1 | paulderscheid++ :) |
13:06 | paulderscheid[m] | Haha, community++ cait++ cait1++ |
13:07 | cait1 | community++ |
13:09 | oleonard | cait1: Did you figure out what was going on with DataTables saved state? |
13:10 | cait1 | didn't have the time really - was just runnign through features for screenshots |
13:10 | does it work for you? | |
13:10 | i was testing on a local ktd installaton and the table was items on detail page ins taff | |
13:14 | oleonard | cait1: It's not global. Bug 22276 only implemented it for the libraries admin page |
13:14 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=22276 enhancement, P5 - low, ---, oleonard, RESOLVED FIXED, Add client storage of user-selected DataTables configuration |
13:14 | oleonard | The next step is to make it more widely applicable |
13:14 | cait1 | oh |
13:14 | absolutely | |
13:14 | tbh, the title of that bug was misleading me! | |
13:16 | should we file a new bug? | |
13:16 | and is this a one by one thing or can we do all theothers? | |
13:18 | oleonard | cait1: The bug laid the groundwork for wider implementation and did the libraries page as a proof of concept. |
13:19 | It requires case-by-case modification right now, but there's probably a smarter way to do it. | |
13:19 | I could see us having "Save state" an option in table settings | |
13:20 | cait1 | maybe having a clear option too |
13:20 | but it hink just keeping it would be nice already | |
13:35 | just adversiting a feature that is waiting for sign-off: geographic search: https://geosearch-opac.koha-su[…]l&weight_search=1 | |
13:36 | bug 31652 | |
13:36 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=31652 new feature, P5 - low, ---, domm, Needs Signoff , Add geo-search |
13:36 | cait1 | just had a nice presentation about this at our user meeting :) |
13:36 | oleonard | That looks very nice! |
13:37 | cait1 | check the advanced search |
13:37 | you can search for a place and km aroudn it and get results for it | |
13:38 | hm ok, not place yet, but coordinates, but still a pretty nice start :) | |
13:39 | uses @marc 034 | |
13:39 | @marc 034 | |
13:39 | huginn | cait1: The coded form of the mathematical data contained in field 255 (Mathematical Data Area) of the bibliographic record. (Repeatable) [a,b,c,d,e,f,g,h,j,k,m,n,p,r,s,t,x,y,z,2,6,8] |
13:39 | oleonard | Everyone knows the coordinates to all their favorite libraries :D |
13:40 | cait1 | i guess translating a place name to coordnates woudl be logical next step :) |
13:45 | ashimema | that is pretty cool |
13:45 | cait1 | they mentioned using authorities with coorrdinates too - nto sure if that was implemented yet or not, but it would make addng places etc. easy in cataloguing |
13:46 | domm[m]: ? | |
13:59 | domm[m] | not implemented yet |
13:59 | Dyrcona joined #koha | |
14:00 | domm[m] | translating place name to coord will be done via https://www.geonames.org/ |
14:00 | but also not implemented yet | |
14:01 | The current patch is the basic proof-of-concept that we can index geo-points and search/find them | |
14:11 | cait1 | keeping things smaller is a good thing - but was lso hopin you had more planned :) |
14:28 | lds joined #koha | |
14:57 | khall joined #koha | |
15:03 | lukeg joined #koha | |
15:14 | khall joined #koha | |
15:17 | khall_ joined #koha | |
15:29 | lukeg joined #koha | |
15:30 | khall joined #koha | |
15:33 | khall_ joined #koha | |
16:00 | bag joined #koha | |
16:02 | khall joined #koha | |
16:26 | reiveune | bye |
16:26 | reiveune left #koha | |
16:43 | MatthewRoss[m] joined #koha | |
16:46 | MatthewRoss[m] | Good Morning. We are using Koha's Stable releases on a Debian VM, and just upgraded to 22.11. Now I'm being asked to login to the admin interface, but none of our prevoius logins are working. Neither are my original admin credentials (documented from original install years ago), nor any of the listed users/password in the koha-conf.xml file. Are there Debian specific upgrade instructions? |
16:47 | Oh, and the admin interfce is showing the Web Installer. Hopefully, the upgrade did not wipe our system, and this is just part of the upgrade procedure... | |
17:17 | caroline | MathewWood[m], when I get the web installer, its because the database didn't update. I manually run updatedatabase.pl and then I get the normal login screen... Maybe confirm with someone else to make sure since it may not be the same situation as me |
17:22 | MatthewRoss[m] | I just tried running updatedatabase.pl... Got a Perl error: "Can't locate C4/Context.pm in @INC (you may need to install the C4::Context module)" I'm not perl guru, but I'll find how to get that installed and try running it again. |
17:23 | caroline | that seems like a basic thing to be missing... |
17:24 | MatthewRoss[m] | I am running Debian 9 (Stretch). |
17:29 | oleonard | MatthewRoss[m]: C4/Context.pm is part of Koha itself, not a dependency which needs to be installed. |
17:30 | caroline | do we know if 22.11 is compatible with Debian 9? I know we had to upgrade from 10 to 11 for 22.05, but it might just have been regular upkeep... I'm not a dev nor a sysadmin, so I don't really know |
17:30 | MatthewRoss[m] | Okay. That make sense as all my googlefu is returning Koha results. |
17:30 | ashimema | ah.. |
17:31 | we're no longer testing against D9 for 22.11.. as D9 is EOL | |
17:31 | I've not actually tried to be honest... | |
17:32 | MatthewRoss[m] | Okay. Thanks. I'll backup my databases and try to upgrade debian. |
17:32 | ashimema | mtj may be able to help more there.. he has been in charge of the packaging for that |
17:32 | sorry Matthew.. never Iike being the bearer of potentially bad news | |
17:32 | MatthewRoss[m] | No worries. I have snapshots from before the upgrade. Worst case cenario is going back to 21.xx |
17:33 | ashimema | my team are just getting up to speed again having taken on release maintenance for 22.11.. great to see an early adopter.. but beware this was a huge release so there are likely to be at least a few UI bugs (the new staff interface touched a huge amount).. |
17:33 | I'd love to have some early adopters.. but please report the bugs you find so we can get them fixed up nice and quick 🙂 | |
17:35 | MatthewRoss[m] | No problem. Where's the right place to report bugs? Oh, I see you have a bugzilla. Got it. |
17:38 | ashimema | perfect 🙂 |
17:38 | thankyou 😄 | |
17:40 | * cait[m] | waves |
17:40 | caroline | thanks oleonard and ashimema! |
17:42 | cait[m], did you finish your presentation? | |
17:45 | cait[m] | yes :) |
17:46 | we had a good outcome today too up to 170 people for the german speaking users meeting | |
17:47 | caroline | wow! that's awesome! |
17:48 | ashimema | Well done Cait m wow |
17:48 | davidnind | cait++ |
17:57 | cait[m] | it was our 5th event, it's a team effort, people from different organisations organizing |
17:59 | but really happy we had so many people attending :) | |
18:35 | khall joined #koha | |
19:11 | tuxayo | > up to 170 people for the german speaking users meeting |
19:11 | koha-de++ | |
19:45 | MatthewRoss[m] | Quick update for the currious: I tried to update Debian 9 -> 11 using info here: https://www.debian.org/release[…]upgrading.en.html - Upgrade was successful, but I was still receiving errors. I was able to login to the Web Updater, but it had it's own errors during database update. (Referencing Bug 29144, "Row Size too large.") I at this point abandoned the upgrade and restored my VM from earlier snapshot. I'll |
19:45 | be looking to do an upgrade via a clean install during winter break, or possibly transision to a hosted Koha. | |
19:45 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=29144 enhancement, P5 - low, ---, m.de.rooy, RESOLVED FIXED, Move branches.opac_info to AdditionalContents allowing multi language |
20:18 | fridolin joined #koha | |
20:21 | emlam joined #koha | |
20:54 | khall joined #koha | |
21:13 | bone joined #koha | |
21:23 | fridolin left #koha | |
22:28 | tuxayo | Matthew Ross: «it had it's own errors during database update» So you are also updating Koha and not only the OS |
22:29 | The OS upgrade might or might not be related. | |
22:31 | Matthew Ross: "Row Size too large." Just a guess: you can compared the structure of the failing table(s) to the expected one: https://git.koha-community.org[…]kohastructure.sql | |
22:32 | Choose the right branch before comparing: pick the same version as you current version | |
22:33 | Sometime old installs have some differences in the structure. Like a column could be of a wrong type because a past database upgrade have something wrong. | |
22:41 | dcook | Old Debian databases also have a structural issue |
22:41 | Using... COMPACT instead of DYNAMIC or something | |
22:42 | bug 28267 | |
22:42 | huginn | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=28267 critical, P1 - high, ---, koha-bugs, NEW , Koha-common package upgrade problem from 20.05.xx to 20.11.04-1 |
← Previous day | Today | Next day → | Search | Index