← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
Time | Nick | Message |
---|---|---|
02:16 | koha-jenkins | Project Koha_Master build #1805: STILL UNSTABLE in 1 hr 3 min: https://jenkins.koha-community[…]Koha_Master/1805/ |
02:34 | David joined #koha | |
03:11 | mtj | hi pabloab, tuxayo - i really like the idea of discouse software :) |
03:12 | is it possible to run both discouse and mailman at the same time? - or would we need to do a hard-switch to discourse? | |
03:17 | tuxayo | mtj discourse can work as a mailing list. IIUC: Make account, go to a category (~sub forum) and subscribe to it selecting to be notified to everything |
03:17 | It's even possible to answer email | |
03:17 | mtj | ah yes, that makes sense |
03:17 | tuxayo | *via email |
03:20 | mtj | i'd be keen to help setting up a discourse |
03:20 | tuxayo | :D |
03:21 | I think that's the missing thing. Because otherwise the idea has been well received. | |
03:27 | For the record (or other projects than Koha), in case we don't have the time resources to host a Discouse I was starting to think of a fallback with our forge, Gitea. | |
03:28 | Because the issue tracker is a forum and a mailing list. Just create a few projects without a repo and only the issue tracker and voilà. I've seen projects do this | |
03:28 | For many project forges are really great, host/find and instance of Gitea or Gitlab, get a git server, an issues tracker, a forum&ML and a wiki! | |
03:29 | mtj | hmmm, thats an interesting usage of a self-hosted gitlab |
03:38 | tuxayo | I wasn't serious about it since there was (and is more than before!) hope that someone could have the time to setup and maintain a Discourse. |
03:38 | But actually, would there be a significant advantage to justify the hosting of Discourse compared to using our Gitea? Considering that you don't lack of things to do :P | |
03:38 | (assuming the OOM of Gitea are solvable!) | |
03:41 | Here is my example of issue tracker powered ML&forum : https://github.com/liberapay/s[…]-this-salon-works | |
05:13 | lmstrand joined #koha | |
05:29 | mtj | i think using github would be a no-go, as we cant self-host it |
05:31 | i think importing a mailman repo into discourse, is probably a much more 'solved' problem than into gitea | |
05:51 | chriss joined #koha | |
06:01 | lds joined #koha | |
06:06 | reiveune joined #koha | |
06:37 | cait joined #koha | |
07:11 | * cait | waves |
07:28 | cait | bbl |
07:31 | reiveune | hello |
07:31 | wahanui | niihau, reiveune |
08:00 | alex_a joined #koha | |
08:10 | cait joined #koha | |
08:19 | ashimema | mornin' #koha |
08:21 | Joubu | mtj, tuxayo: It would be a move from mailman to discourse. I am "on it". Not at the moment but will be back to it after the release. |
08:21 | I am still waiting for BibLibre to confirm they will provide us the server | |
08:24 | * ashimema | would love to see issues handled through gittea instead of bugzilla.. but that's any entirely different discussion. |
08:25 | likes branches and merges requests.. I find the huge numbers of 'you attached this' messages in bugzilla really distracting and difficult | |
08:25 | ashimema | and commenting on code out of context all the time is a pain. |
08:25 | plus, bz just "looks dated" so puts new developers off the project as a whole | |
08:25 | anywho.. soapbox moment done | |
08:27 | cait | I really like Bugzilla's strong search capabilities |
08:27 | haven't seen that in any issue tracker so far | |
08:27 | they all usually appear to have quite basic searches | |
08:27 | and with the amount of bugs we have, that is a real plus for me | |
08:28 | ashimema | understandable |
08:28 | I know the strengths of bugzilla too | |
08:29 | Joubu | we already have the mailing list and the wiki (I also have a "split and shrink git repo" somewhere) |
08:29 | to move | |
08:29 | ashimema | yup |
08:29 | one thing at a time 😉 | |
08:32 | mtj | i wonder if splitting the koha git repo could help with the gitea OOM problem? |
08:34 | Joubu | did it happen again? |
08:34 | hugoagud joined #koha | |
08:34 | hugoagud | good morning, I have an issue with fines.pl, anybody knows when and why fines.pl generate overdue_decrease? |
08:35 | I am trying to adjust a fine directly from mysql, but koha adjusts the fine with overdue_decrease | |
08:48 | Joubu | Hi hugoagud, ashimema is our "accounts" expert |
08:56 | cait | hea is up to 17.065 + 600 from last month :) |
08:57 | Joubu | I should have a look at the DB, one day.. |
08:57 | cait | hugoagud: koha calculates the fine everyday according to your circulation rules |
08:57 | as long as the item is not return, adjusting the fine with SQL won't work | |
08:57 | it will be recalculatedwith every run of the script | |
08:57 | have a look at your fine settings in the circulation rules | |
08:58 | if you want to freeze the fine, you'll have to reutrn the item and check it out again | |
09:16 | ashimema | What cait said basically |
09:17 | You 'fix' the fine by marking the item as 'returned'.. though that could of course be one of the lost states | |
09:17 | If it's not returned the fine rules come into play and the fine is recalculated from scratch with every run of the script | |
09:18 | The offsets, decrease/increase just reflect the change since the last run.. so if your rules have changed to reduce the amount per day and then the script runs.. it'll result in a decrease. | |
09:20 | Decreases were really designed for calculate at check-in fine.. I e the scripts run daily . Someone returns the item on a closed day.. the script runs and increments the fine.. next day staff do a backdated return and the fine is recalculated for the previous day.. thus decreased again. | |
09:20 | Hope that makes sense | |
09:23 | mtj | Joubu: no, no OOM that i know of :) |
09:31 | hugoagud | HI, that makes a lot of sense... thank you very much.. sorry for the delay I was out of the desktop ;) |
09:32 | * ashimema | apologies for any typos.. I was on the school run |
09:36 | cait | ashimema is the accounts expert... but fines are also one of my things... sadly |
10:15 | magnuse joined #koha | |
10:16 | magnuse_ joined #koha | |
10:25 | magnuse joined #koha | |
10:26 | magnuse | bag: can you make some more ops, please? |
10:26 | ashimema | ? |
10:27 | magnuse | looks like he os the only ops in the channel? |
10:27 | op? ops? | |
10:31 | ashimema | I thought you were one lol |
10:34 | * oleonard | wonders who magnuse wants to kick :D |
10:37 | IgorAS joined #koha | |
10:50 | alex_a joined #koha | |
10:57 | Joubu | tuxayo: I published 20.05.17 release notes, it was still a draft |
11:13 | tcohen | hola #koha |
11:24 | oleonard | Hi tcohen |
11:32 | Joubu | bug 29386 - would it make sense to switch to MEDIUMTEXT then later LONGTEXT if still not enough? |
11:33 | huginn` | Bug https://bugs.koha-community.or[…]_bug.cgi?id=29386 normal, P5 - low, ---, koha-bugs, NEW , background jobs table data field is a TEXT which is too small |
11:33 | Joubu | or do we go with LONGTEXT directly? |
11:40 | Dyrcona joined #koha | |
11:46 | magnuse | ashimema: looks like i lost it |
11:51 | cait | magnuse: maybe you need to identify? |
12:21 | oleonard | I wonder if there's any reason to show imported records in the "Records found in reservoir" table |
12:21 | khall_ joined #koha | |
12:28 | Dyrcona joined #koha | |
12:54 | magnuse | cait: i did, but it made no difference |
12:54 | oleonard | Shower me with your reservoir opinions |
12:54 | magnuse | i think reservoir dogs is a move by quentin tarantino |
12:54 | s/move/movie/ | |
12:55 | oleonard | In your humble opinion |
12:55 | tcohen | hahaa, a great movie |
12:56 | oleonard | What do you think Tarantino would have thought about excluding imported records from reservoir search results? |
12:56 | tcohen | Mr. Brown would've cleaned all the scene |
13:08 | oleonard | Bug 29391 |
13:08 | huginn` | Bug https://bugs.koha-community.or[…]_bug.cgi?id=29391 enhancement, P5 - low, ---, koha-bugs, ASSIGNED , Improve output of reservoir search |
13:17 | NateC joined #koha | |
13:20 | koha-jenkins | Project Koha_21.05_U_Stable build #84: SUCCESS in 35 min: https://jenkins.koha-community[…]1.05_U_Stable/84/ |
13:28 | Project Koha_21.05_U16 build #92: SUCCESS in 43 min: https://jenkins.koha-community[…]oha_21.05_U16/92/ | |
13:32 | khall joined #koha | |
13:34 | jzairo joined #koha | |
13:42 | koha-jenkins | Project Koha_21.05_U20 build #94: SUCCESS in 58 min: https://jenkins.koha-community[…]oha_21.05_U20/94/ |
13:43 | Project Koha_21.05_U21 build #14: SUCCESS in 58 min: https://jenkins.koha-community[…]oha_21.05_U21/14/ | |
13:48 | Project Koha_21.05_D10 build #131: SUCCESS in 1 hr 4 min: https://jenkins.koha-community[…]ha_21.05_D10/131/ | |
13:49 | cait | oleonard-away: i think imported make more sense there than the z39.50 ones |
13:50 | i can imagine workflows for uplaoding a data set froma vendor and wanting to use it in cataloguing | |
13:50 | but random searches from z39.50 seem more lunlikely | |
13:50 | or do you mean imported vs. staged? then I withdraw... | |
13:54 | koha-jenkins | Project Koha_21.05_D12 build #23: SUCCESS in 33 min: https://jenkins.koha-community[…]oha_21.05_D12/23/ |
13:57 | Project Koha_21.05_U18 build #85: SUCCESS in 1 hr 12 min: https://jenkins.koha-community[…]oha_21.05_U18/85/ | |
14:12 | Project Koha_21.05_D9 build #88: UNSTABLE in 43 min: https://jenkins.koha-community[…]Koha_21.05_D9/88/ | |
14:25 | oleonard | cait: A record which has been imported is probably still in your catalog unless it was since deleted |
14:35 | koha-jenkins | Project Koha_21.05_D11 build #108: SUCCESS in 52 min: https://jenkins.koha-community[…]ha_21.05_D11/108/ |
14:35 | Oak joined #koha | |
14:36 | cait | oleonard: ok, imported makes sense - sorry, I was thinking of staged ones |
14:37 | kidclamp: any opinion on 29010? | |
14:37 | i see that you cc'd yourself :) | |
14:38 | baground jobs... bag's round jobs? :) | |
14:39 | koha-jenkins | Project Koha_21.05_D12 build #24: SUCCESS in 55 min: https://jenkins.koha-community[…]oha_21.05_D12/24/ |
14:43 | cait | sorry... that probably is all a little delayed, just catching up on today's work |
14:52 | oleonard: what do you think of https://wiki.koha-community.or[…]sses_for_KohaCons (tuyayo's work) | |
14:53 | ashimema, Joubu and others ^ | |
15:05 | Joubu | @later tell tuxayo did you send us the mail you received from the kohacon's organisers? I haven't received it |
15:05 | huginn` | Joubu: The operation succeeded. |
15:08 | Joubu | cait: yes, make sense! |
15:15 | oleonard: didn't I open a bug to remove the flatpickr instantiations from .tt files? | |
15:16 | oleonard | Joubu: I think it's not in its own bug |
15:17 | Bug 29240 | |
15:17 | huginn` | Bug https://bugs.koha-community.or[…]_bug.cgi?id=29240 major, P5 - low, ---, martin.renvoize, RESOLVED FIXED, Flatpickr - error in the console when a date is selected |
15:17 | Joubu | oleonard: I've created bug 29394 |
15:17 | huginn` | Bug https://bugs.koha-community.or[…]_bug.cgi?id=29394 normal, P5 - low, ---, oleonard, NEW , Remove flatpickr instantiations from .tt files |
15:23 | NateC_ joined #koha | |
15:26 | koha-jenkins | Yippee, build fixed! |
15:26 | wahanui | Congratulations! |
15:26 | koha-jenkins | Project Koha_21.05_D9 build #89: FIXED in 1 hr 13 min: https://jenkins.koha-community[…]Koha_21.05_D9/89/ |
15:53 | ashimema | hmm.. |
15:53 | problem with doing lots of SO and QA... | |
15:53 | my inbox gets mailbombed at push | |
15:55 | huginn` | News from kohagit: Bug 28263: DBRev 21.06.00.040 <https://git.koha-community.org[…]da7ac2a4032080b2d> |
15:55 | News from kohagit: Bug 28901: Compiled CSS <https://git.koha-community.org[…]37bbe1e8fd5abdf1c> | |
15:55 | News from kohagit: Bug 28904: Fix typo and display <https://git.koha-community.org[…]3aef3a2cde961ee09> | |
15:55 | News from kohagit: Bug 28263: (QA follow-up) Use new atomicupdate code style <https://git.koha-community.org[…]2cb12afa7660877c9> | |
15:55 | News from kohagit: Bug 28729: Additions to POD <https://git.koha-community.org[…]10eafbe5208c96126> | |
15:55 | News from kohagit: Bug 29356: Pickup location dropdowns should perform 'contains' searches <https://git.koha-community.org[…]18b3a23e579816bfa> | |
15:55 | News from kohagit: Bug 29355: Make pickup location dropdowns RESTdefaultPageSize agnostic <https://git.koha-community.org[…]a61bab551092a920c> | |
15:55 | News from kohagit: Bug 29328: Add missing list parameter to reports parameter menu <https://git.koha-community.org[…]b94517cf2e8a756f4> | |
15:55 | News from kohagit: Bug 29352: Runtime parameter labels should not be said to be optional <https://git.koha-community.org[…]cf48aa99a3c217e70> | |
15:55 | News from kohagit: Bug 29351: Add missing cn_source parameter to reports parameter menu <https://git.koha-community.org[…]b385aaa5b9a42e960> | |
15:55 | News from kohagit: Bug 28904: Update team list to include newsletter editors <https://git.koha-community.org[…]636c70f639f6b12e6> | |
15:55 | News from kohagit: Bug 28904: Add newsletter editor to about page display <https://git.koha-community.org[…]980253df9a6109856> | |
15:55 | News from kohagit: Bug 29329: Remove stray character in opac-detail.tt <https://git.koha-community.org[…]46eee65f779cb35b2> | |
15:55 | News from kohagit: Bug 28729: Make Koha::Email->send_or_die handle returnpath <https://git.koha-community.org[…]28cf8c171233d6d20> | |
15:55 | News from kohagit: Bug 28729: Unit tests <https://git.koha-community.org[…]df6cde62c779fe3c7> | |
15:55 | News from kohagit: Bug 29242: Flatpickr - Should autocomplete be turned off? <https://git.koha-community.org[…]b175296b419ad4ff7> | |
15:55 | News from kohagit: Bug 27884: Add tests <https://git.koha-community.org[…]c7436dafb46092912> | |
15:55 | News from kohagit: Bug 28263: Fix too_many auto renewal message <https://git.koha-community.org[…]3b1f9d2421af96832> | |
15:55 | News from kohagit: Bug 27884: Add html support for report mails <https://git.koha-community.org[…]2dd3c1ef66590e3a9> | |
15:55 | News from kohagit: Bug 25459: Makes barcode position respect units in patron cards layout <https://git.koha-community.org[…]f8acb4599476b95c3> | |
16:06 | reiveune | bye |
16:06 | reiveune left #koha | |
16:25 | cait left #koha | |
16:30 | koha-jenkins | Project Koha_Master_D11 build #435: UNSTABLE in 34 min: https://jenkins.koha-community[…]a_Master_D11/435/ |
16:32 | Project Koha_Master_U20 build #231: FAILURE in 33 min: https://jenkins.koha-community[…]a_Master_U20/231/ | |
16:40 | Project Koha_Master_U21 build #14: UNSTABLE in 42 min: https://jenkins.koha-community[…]ha_Master_U21/14/ | |
16:47 | Project Koha_Master_D11_MDB_Latest build #717: UNSTABLE in 51 min: https://jenkins.koha-community[…]1_MDB_Latest/717/ | |
16:54 | Project Koha_Master_D11_CPAN build #465: UNSTABLE in 55 min: https://jenkins.koha-community[…]ter_D11_CPAN/465/ | |
16:56 | Joubu | So, as you can see master is broken (more precisely date handling for the REST API) |
16:56 | See bug 24850, last comments | |
16:56 | huginn` | Bug https://bugs.koha-community.or[…]_bug.cgi?id=24850 major, P5 - low, ---, martin.renvoize, Pushed to master , Koha::DateUtils ignores offsets in RFC3339 datetimes |
16:57 | Joubu | there is a workaround if you are stuck |
16:57 | koha-jenkins | Project Koha_Master_U_Stable build #303: UNSTABLE in 1 hr 0 min: https://jenkins.koha-community[…]ter_U_Stable/303/ |
17:00 | pabloab joined #koha | |
17:04 | koha-jenkins | Project Koha_Master_D11_My8 build #683: UNSTABLE in 34 min: https://jenkins.koha-community[…]ster_D11_My8/683/ |
17:22 | Project Koha_Master_D9 build #1811: UNSTABLE in 41 min: https://jenkins.koha-community[…]a_Master_D9/1811/ | |
17:28 | Project Koha_Master_D12 build #16: UNSTABLE in 56 min: https://jenkins.koha-community[…]ha_Master_D12/16/ | |
17:29 | cait joined #koha | |
17:54 | koha-jenkins | Project Koha_Master_D12 build #17: STILL UNSTABLE in 56 min: https://jenkins.koha-community[…]ha_Master_D12/17/ |
17:56 | ashimema | Will look at all the date related test failures tomorrow Joubu |
17:57 | koha-jenkins | Project Koha_Master build #1806: STILL UNSTABLE in 1 hr 3 min: https://jenkins.koha-community[…]Koha_Master/1806/ |
18:01 | khall_ joined #koha | |
18:33 | oleonard-away | Manage ILL request.... a whole set of buttons with English labels coming from Illrequest.pm... |
18:58 | koha-jenkins | Project Koha_Master build #1807: STILL UNSTABLE in 1 hr 1 min: https://jenkins.koha-community[…]Koha_Master/1807/ |
19:53 | davidnind left #koha | |
21:01 | tuxayo | @later tell Joubu , oh my post was still a draft :o thanks a lot!!! |
21:01 | huginn` | tuxayo: The operation succeeded. |
21:05 | tuxayo | @later tell ashimema I think what we are missing the most to switch from BZ to Gitea would be dependencies between tickets. We could push for that with a bounty on https://github.com/go-gitea/gitea/issues/8794 |
21:05 | huginn` | tuxayo: The operation succeeded. |
21:18 | tuxayo | @later tell ashimema wait it's only the graph part that is missing! There basic feature is actually there! :D https://github.com/go-gitea/gitea/pull/2531 |
21:18 | huginn` | tuxayo: The operation succeeded. |
22:07 | alexbuckley joined #koha | |
23:23 | jzairo joined #koha | |
23:28 | pabloab | tuxayo: There is no consensus to move from the old BZ to the modern GitLab? |
23:28 | tuxayo | pabloab: GitLab, certainly not. Last time I checked, dependency between tickets was only doable in the non-libre version of GitLab... |
23:30 | Maybe it changed. I recall that a few things where non-libre at first and some time after ended up in the libre version | |
23:31 | More importantly, there is really a lack of workforce for that topic. Updating the version of the wiki + getting rid of mailman is already a lot. | |
23:35 | pabloab | Sure. Sad to hear that abouth GitLab. The only available relationship is "relates to". "blocks" and "is blocked by" only on Premium https://docs.gitlab.com/ee/use[…]dd-a-linked-issue |
23:36 | I wonder if a huge project like GNOME (which moved to GitLab) just don't use that feature. | |
23:51 | Putti joined #koha | |
23:58 | tuxayo | > Updating the version of the wiki + getting rid of mailman is already a lot. |
23:58 | Oh and also maybe moving from Pootle to Weblate | |
23:59 | > "relates to". "blocks" and "is blocked by" | |
23:59 | Perfect, that's what we use on BZ |
← Previous day | Today | Next day → | Search | Index