[Koha-devel] String Freeze Notice

[Joy Nelson]

 Greetings!

Just a quick note that string freeze will go into effect on 3/15/2020 for
the maintenance branches.

Maintenance releases scheduled for the 24th.


-- 
Joy Nelson
President, Koha Division

ByWater Solutions 
Support and Consulting for Open Source Software
Phone/Fax (888)900-8944
What is Koha? 
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] remote training on Koha & covid-19

[Andrew Fuerste-Henry]

Hi Paul!
Kelly, Donna, and I will find some time here to pool what experience we
have.
Andrew

On Fri, Mar 13, 2020 at 12:33 PM Paul Poulain 
wrote:

> Hello all,
>
> In France, we always move to the library for training. With the covid-19
> we may have to do some remote training. Have you experimented remote
> training ? How does it go ? How do you organise the training ? Any hints ?
>
> Thanks for anything shared, that will be helpful for us !
>
> --
> Paul Poulain, Associé-gérant / co-owner
> BibLibre, Services en logiciels libres pour les bibliothèques
> BibLibre, Open Source software and services for libraries
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/
> git : http://git.koha-community.org/
> bugs : http://bugs.koha-community.org/
>


-- 
Andrew Fuerste-Henry
Educator
(he/him/his)
ByWater Solutions
bywatersolutions.com
Phone:(888)900-8944 <(888)%20900-8944>

What is Koha? 
___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

[Koha-devel] remote training on Koha & covid-19

[Paul Poulain]

Hello all,

In France, we always move to the library for training. With the covid-19 
we may have to do some remote training. Have you experimented remote 
training ? How does it go ? How do you organise the training ? Any hints ?


Thanks for anything shared, that will be helpful for us !

--
Paul Poulain, Associé-gérant / co-owner
BibLibre, Services en logiciels libres pour les bibliothèques
BibLibre, Open Source software and services for libraries

___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] Koha packaging problems (Deb10/Buster)

[Mason James]

we need to pin on buster because the current combination of 
libmojolicious-plugin-openapi-perl (1.15~koha) and libmojolicious-perl (8.12) 
packages that buster pulls are incompatible with each other - even with bz 
22522 applied, this problem still exists on buster

we can fix buster by uploading a new version of 
libmojolicious-plugin-openapi-perl (2.20) to the koha repo, but this breaks 
jessie - so we cant do that until 30th june

...or do we decide to upload a new version of 
libmojolicious-plugin-openapi-perl to the koha repo now, and break jessie to 
fix buster?


any other ideas?


On 13/03/20 11:36 am, dc...@prosentient.com.au wrote:
> Wait a minute... why do we need to pin libmojolicious-perl? 
>
> Thanks to Ere's work on 
> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22522, Koha should 
> be able to work with Mojolicious 8 now (and Mojolicious::Plugin::OpenAPI 2.21 
> and JSON::Validator 3.18). Admittedly it's only in master right now, but I'm 
> using his patches on 18.11 and 19.11 already with Mojolicious 8, and they're 
> working well so far. So hopefully people start pushing that code to stable 
> branches ASAP. 
>
> David Cook
> Systems Librarian
> Prosentient Systems
> 72/330 Wattle St
> Ultimo, NSW 2007
> Australia
>
> Office: 02 9212 0899
> Direct: 02 8005 0595
>
> -Original Message-
> From: Koha-devel  On Behalf Of 
> Mason James
> Sent: Thursday, 12 March 2020 8:20 PM
> To: Koha Devel 
> Subject: Re: [Koha-devel] Koha packaging problems (Deb10/Buster)
>
> On 12/03/20 12:43 am, Mason James wrote:
>> On 10/03/20 8:08 pm, Mason James wrote:
>>> Hi Koha devs
>>>
>>> We have a dependency problem with the release of debian-10 and the 
>>> following packages. (debian-11 is ok)
>>>
>>>  libmojolicious-perl
>>>  libmojolicious-plugin-openapi-perl
>>>  libyaml-libyaml-perl
>>> Two other options...
>>>  1/ use kc.org debian packages, with cpanminus (or similar) providing 
>>> the distro specific packages (extra installation steps and 
>>> complexity)
>>>  2/ ignore the problem for now, and accept that older koha/distro 
>>> combinations will be forced to break
>> some other points i didnt mention...
>>
>> koha on buster has a security bug. the solution requires some packages 
>> to be updated
>>
>> i can push the packages to the koha repo to fix this problem, but... 
>> (there's always a but) the new packages will break jessie :/ when 
>> jessie-lts support officially finishes on 30th june 2020, i can 
>> happily push these packages - but between now and 30th june we need to 
>> decide on a fix for the security bug on buster
>>  https://wiki.debian.org/LTS
>>
>> some other options...
>>  3/ do nothing and tell people to not use buster, until june
>>  4/ provide buster packages in an separate repo, until june
>>  5/ provide instructions to add buster packages using cpanm, until 
>> june
>>  6/ update koha repo to fix buster, and provide jessie packages in an 
>> separate repo
>>  7/ update koha repo to fix buster, and provide instructions to add 
>> jessie packages using cpanm
>>  8/ submit required buster packages to debian buster-backports repo 
>> (not sure how difficult this is)
>>
>> i prefer option 4/, as its the least disruptive for users, and only 
>> requires an extra sources.list line to implement
>>
>> also... i think we should hold off on redesigning the koha apt 
>> repository until *after* this buster security issue is fixed
>>
>> cheers, Mason
> hmm, i had forgotten another...
> its possible to tell apt to prefer koha's older mojo v7 package, rather than 
> the newer debian/buster mojo v8 package
>
> running the following command before 'apt install koha-common' makes it 
> possible to run the various koha releases on debian 10
>
> $ sudo cat << EOF > /etc/apt/preferences.d/koha-1001
> Package: libjson-validator-perl
> Pin-Priority: 1001
> Pin: release o=Koha
>
> Package: libmojolicious-perl
> Pin-Priority: 1001
> Pin: release o=Koha
> EOF
>
>
> for me, this option is probably the easiest workaround for koha on debian 10
>
> if nobody objects? - i am happy to update the koha wiki with this workaround
>
> cheers, Mason
>
> ___
> Koha-devel mailing list
> Koha-devel@lists.koha-community.org
> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
> website : http://www.koha-community.org/ git : http://git.koha-community.org/ 
> bugs : http://bugs.koha-community.org/
>


___
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Re: [Koha-devel] REST API not working in koha-testing-docker?

[dcook]

Ah, interesting. I haven’t drilled down that far yet. I’ve been doing lots of 
multitasking and out of the office. Probably won’t have a chance to look at 
this again for at least a few days minimum.

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: Agustin Moyano  
Sent: Friday, 13 March 2020 4:36 PM
To: dc...@prosentient.com.au
Cc: Tomas Cohen Arazi ; koha-devel 

Subject: Re: [Koha-devel] REST API not working in koha-testing-docker?

 

As Tomas says, I've seen in many endpoint controllers that the code is wrapped 
by a try, but in the catch section $_ is ignored, and a 500 is returned. 

 

I believe that Tomas means is that you should concat $_ to the message of the 
500 error in that catch section.

 

Regards.

 

On Thu, Mar 12, 2020 at 8:05 PM mailto:dc...@prosentient.com.au> > wrote:

Hey Tomas,

 

I listed some steps to reproduce at 
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24862. I haven’t 
drilled down deep enough yet, but I’m thinking it might relate to cookies for 
anonymous sessions. 

 

Can you elaborate on what you mean by “concat $_ to the case of 500”? 

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: Koha-devel mailto:koha-devel-boun...@lists.koha-community.org> > On Behalf Of Tomas Cohen 
Arazi
Sent: Friday, 13 March 2020 9:52 AM
To: koha-devel mailto:koha-devel@lists.koha-community.org> >
Subject: Re: [Koha-devel] REST API not working in koha-testing-docker?

 

Hi all.

 

Cookie auth shouldn't be a problem per se. We only use the cookie for getting 
the user and then the code is the same no matter the autentication method.

 

But

 

There's always a 'but', right?

 

I've been fighting some devs that introduce the use of C4::Context->userenv and 
then probably have side effects of a cookie is found ... Even if the api is 
called using (say) oauth.

 

We should get rid of this side effects from our codebase. In the meantime, 
share some more info on the endpoint you're hitting so we can debug it and fix 
it!

 

Cheers

 

PS I need to submit some work I did for handling unhandled exceptions in a more 
useful way. I suggest you concat $_ to the case of 500 on the endpoint you're 
using to get more info.

 

El jue., 12 de marzo de 2020 19:31, mailto:dc...@prosentient.com.au> > escribió:

Hi Arthur,

 

Thanks for your comprehensive reply. Sorry I just noticed it after replying to 
everyone else who CCed me directly.

 

I’m not interested in using browser extensions, but thanks for sharing your 
experience. 

 

It looks like the 500 Internal Server Errors probably related to Koha not 
handling a cookie/browser session as expected. The errors went away if I used a 
different browser or an Incognito mode. (Hence why it also worked with curl.) I 
suppose that could be a bug in Koha, but probably not a significant enough one 
to deal with right now. 

Sure enough, when I log into the http://localhost:8080, I can now get the 
output of http://localhost:8080/api/v1/libraries because of the cookie 
indicating my browser session. If I log out, I now get ‘{"error":"Something 
went wrong, check the logs."}’, when really I should probably get a 401. Raised 
this issue for it 
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24862. 

 

The RESTPublicAPI thing also looks like a bug as I keep getting this error: 
{"error":"Authorization failure. Missing required 
permission(s).","required_permissions":null}. At least when I try using 
RESTBasicAuth. I haven’t tried with RESTOAuth2ClientCredentials or cookie 
authentication. I’ll probably just end up blocking RESTPublicAPI anyway, but 
I’ve raised a ticket anyway 
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24861. 

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: Koha-devel mailto:koha-devel-boun...@lists.koha-community.org> > On Behalf Of Arthur 
Suzuki
Sent: Thursday, 12 March 2020 8:23 PM
To: koha-devel@lists.koha-community.org 
 
Subject: Re: [Koha-devel] REST API not working in koha-testing-docker?

 

Hi David,

To test Rest API I strongly recommend the use of "RESTer" which is an extension 
for Firefox.

I'm sending here the "requests collection" I've made for my own use.

When you open RESTer, there is a menu on the right (if not, click on the top 
left 3-bar icon).

First thing is to go on "Organize" and import the request collection.

2nd step : Click on "Environment", then + button in the lower right corner.

For the requests in the collection to work you'll want to define an environment 
called "koha" with a key called "baseurl" containing... the base url of the 
koha instance you want to test, for koha-testing-docker this