From laurent.ducos at biblibre.com Fri Dec 1 15:15:59 2017 From: laurent.ducos at biblibre.com (Laurent Ducos) Date: Fri, 1 Dec 2017 15:15:59 +0100 Subject: [Koha-devel] no acces to debian.koha-community.org Message-ID: <20171201141559.GA3614@lducos-Latitude-E5450> Hello Since about 1 hour I do not have access to debian.koha-community.org from our public ip 91.121.55.79 Can you give us access again please? since others ip everything is ok -- From laurent.ducos at biblibre.com Fri Dec 1 15:18:23 2017 From: laurent.ducos at biblibre.com (Laurent Ducos) Date: Fri, 01 Dec 2017 14:18:23 +0000 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: <20171201141559.GA3614@lducos-Latitude-E5450> References: <20171201141559.GA3614@lducos-Latitude-E5450> Message-ID: I correct what I just wrote. I have access from nowhere. Laurent Ducos Administrateur Syst?mes et R?seaux 0974770716 1 d?cembre 2017 15:16 "Laurent Ducos" a ?crit: > Hello > > Since about 1 hour I do not have access to debian.koha-community.org from our public ip > 91.121.55.79 > Can you give us access again please? > since others ip everything is ok > > -- > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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 From mik at adminkuhn.ch Fri Dec 1 15:27:27 2017 From: mik at adminkuhn.ch (Michael Kuhn) Date: Fri, 1 Dec 2017 15:27:27 +0100 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: References: <20171201141559.GA3614@lducos-Latitude-E5450> Message-ID: <0ef7cde4-b1ad-1eea-c954-27fe576d1d6a@adminkuhn.ch> Hi >> Since about 1 hour I do not have access to debian.koha-community.org >> from our public ip 91.121.55.79 >> Can you give us access again please? >> since others ip everything is ok > > I correct what I just wrote. I have access from nowhere. I cannot access http://debian.koha-community.org/ via webbrowser either. The webbrowser will just try try try but giving no response (or at least I didn't have the patience waiting long enough). But the address itself is immediately accessible on port 80 when using telent: $ telnet debian.koha-community.org 80 Trying 67.220.127.145... Connected to kohawiki.esilibrary.com. Escape character is '^]'. Maybe this will help someone to solve the problem. Best wishes: Michael -- Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch From mik at adminkuhn.ch Fri Dec 1 15:28:47 2017 From: mik at adminkuhn.ch (Michael Kuhn) Date: Fri, 1 Dec 2017 15:28:47 +0100 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: References: <20171201141559.GA3614@lducos-Latitude-E5450> Message-ID: <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> Hi >> Since about 1 hour I do not have access to debian.koha-community.org from our public ip >> 91.121.55.79 >> Can you give us access again please? >> since others ip everything is ok Right now, http://debian.koha-community.org/ can be accessed again. Best wishes: Michael -- Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch From laurent.ducos at biblibre.com Fri Dec 1 15:36:40 2017 From: laurent.ducos at biblibre.com (Laurent Ducos) Date: Fri, 01 Dec 2017 14:36:40 +0000 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> References: <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> <20171201141559.GA3614@lducos-Latitude-E5450> Message-ID: always closed, Port 80 seems closed telnet debian.koha-community.org 80 Trying 67.220.127.145... ............ timeout Laurent Ducos Administrateur Syst?mes et R?seaux 0974770716 1 d?cembre 2017 15:28 "Michael Kuhn" a ?crit: > Hi > >>> Since about 1 hour I do not have access to debian.koha-community.org from our public ip >>> 91.121.55.79 >>> Can you give us access again please? >>> since others ip everything is ok > > Right now, http://debian.koha-community.org can be accessed again. > > Best wishes: Michael > -- > Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis > Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz > T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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 From gmc at equinoxinitiative.org Fri Dec 1 15:37:32 2017 From: gmc at equinoxinitiative.org (Galen Charlton) Date: Fri, 1 Dec 2017 09:37:32 -0500 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: References: <20171201141559.GA3614@lducos-Latitude-E5450> <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> Message-ID: Hi, I'm taking a look at this now; the VM appears to have fallen over after a DOS. Regards, Galen On Fri, Dec 1, 2017 at 9:36 AM, Laurent Ducos wrote: > always closed, Port 80 seems closed > > telnet debian.koha-community.org 80 > Trying 67.220.127.145... > ............ > timeout > Laurent Ducos > Administrateur Syst?mes et R?seaux > 0974770716 > 1 d?cembre 2017 15:28 "Michael Kuhn" a ?crit: >> Hi >> >>>> Since about 1 hour I do not have access to debian.koha-community.org from our public ip >>>> 91.121.55.79 >>>> Can you give us access again please? >>>> since others ip everything is ok >> >> Right now, http://debian.koha-community.org can be accessed again. >> >> Best wishes: Michael >> -- >> Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis >> Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz >> T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://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 at lists.koha-community.org > http://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/ -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: gmc at equinoxInitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366 From mik at adminkuhn.ch Fri Dec 1 15:40:39 2017 From: mik at adminkuhn.ch (Michael Kuhn) Date: Fri, 1 Dec 2017 15:40:39 +0100 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: References: <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> <20171201141559.GA3614@lducos-Latitude-E5450> Message-ID: Hi Laurent Am 01.12.2017 um 15:36 schrieb Laurent Ducos: > always closed, Port 80 seems closed > > telnet debian.koha-community.org 80 > Trying 67.220.127.145... > ............ > timeout Yes, I can confirm this. NOW there is a timeout of abou 2 minutes and no connection is possible anymore (but some minutes ago I was able to access the address on port 80 as shown in the previous e-mail). $ telnet debian.koha-community.org 80 Trying 67.220.127.145... telnet: Unable to connect to remote host: Connection timed out Best wishes: Michael -- Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch From gmc at equinoxinitiative.org Fri Dec 1 15:43:42 2017 From: gmc at equinoxinitiative.org (Galen Charlton) Date: Fri, 1 Dec 2017 09:43:42 -0500 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: References: <20171201141559.GA3614@lducos-Latitude-E5450> <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> Message-ID: Hi, It is now back up. Regards, Galen On Fri, Dec 1, 2017 at 9:37 AM, Galen Charlton wrote: > Hi, > > I'm taking a look at this now; the VM appears to have fallen over after a DOS. > > Regards, > > Galen > > On Fri, Dec 1, 2017 at 9:36 AM, Laurent Ducos > wrote: >> always closed, Port 80 seems closed >> >> telnet debian.koha-community.org 80 >> Trying 67.220.127.145... >> ............ >> timeout >> Laurent Ducos >> Administrateur Syst?mes et R?seaux >> 0974770716 >> 1 d?cembre 2017 15:28 "Michael Kuhn" a ?crit: >>> Hi >>> >>>>> Since about 1 hour I do not have access to debian.koha-community.org from our public ip >>>>> 91.121.55.79 >>>>> Can you give us access again please? >>>>> since others ip everything is ok >>> >>> Right now, http://debian.koha-community.org can be accessed again. >>> >>> Best wishes: Michael >>> -- >>> Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis >>> Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz >>> T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> http://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 at lists.koha-community.org >> http://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/ > > > > -- > Galen Charlton > Infrastructure and Added Services Manager > Equinox Open Library Initiative > phone: 1-877-OPEN-ILS (673-6457) > email: gmc at equinoxInitiative.org > web: https://equinoxInitiative.org > direct: +1 770-709-5581 > cell: +1 404-984-4366 -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: gmc at equinoxInitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366 From laurent.ducos at biblibre.com Fri Dec 1 15:43:55 2017 From: laurent.ducos at biblibre.com (Laurent Ducos) Date: Fri, 01 Dec 2017 14:43:55 +0000 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: References: <20171201141559.GA3614@lducos-Latitude-E5450> <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> Message-ID: <2abbb5631515a7f21b4953d2d2b7d87e@webmail.biblibre.com> Acc?s is ok now :) Thanks Galen Laurent Ducos Administrateur Syst?mes et R?seaux 0974770716 1 d?cembre 2017 15:37 "Galen Charlton" a ?crit: > Hi, > > I'm taking a look at this now; the VM appears to have fallen over after a DOS. > > Regards, > > Galen > > On Fri, Dec 1, 2017 at 9:36 AM, Laurent Ducos > wrote: > >> always closed, Port 80 seems closed >> >> telnet debian.koha-community.org 80 >> Trying 67.220.127.145... >> ............ >> timeout >> Laurent Ducos >> Administrateur Syst?mes et R?seaux >> 0974770716 >> 1 d?cembre 2017 15:28 "Michael Kuhn" a ?crit: >>> Hi >>> >>>>> Since about 1 hour I do not have access to debian.koha-community.org from our public ip >>>>> 91.121.55.79 >>>>> Can you give us access again please? >>>>> since others ip everything is ok >>> >>> Right now, http://debian.koha-community.org can be accessed again. >>> >>> Best wishes: Michael >>> -- >>> Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. Fachausweis >>> Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz >>> T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> http://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 at lists.koha-community.org >> http://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 > > -- > Galen Charlton > Infrastructure and Added Services Manager > Equinox Open Library Initiative > phone: 1-877-OPEN-ILS (673-6457) > email: gmc at equinoxInitiative.org > web: https://equinoxInitiative.org > direct: +1 770-709-5581 > cell: +1 404-984-4366 From joy at bywatersolutions.com Fri Dec 1 19:22:50 2017 From: joy at bywatersolutions.com (Joy Nelson) Date: Fri, 1 Dec 2017 12:22:50 -0600 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: References: <20171201141559.GA3614@lducos-Latitude-E5450> <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> Message-ID: Galen, Are you also working on the wiki.koha-community.org site? This is still down. -Joy On Fri, Dec 1, 2017 at 8:43 AM, Galen Charlton wrote: > Hi, > > It is now back up. > > Regards, > > Galen > > On Fri, Dec 1, 2017 at 9:37 AM, Galen Charlton > wrote: > > Hi, > > > > I'm taking a look at this now; the VM appears to have fallen over after > a DOS. > > > > Regards, > > > > Galen > > > > On Fri, Dec 1, 2017 at 9:36 AM, Laurent Ducos > > wrote: > >> always closed, Port 80 seems closed > >> > >> telnet debian.koha-community.org 80 > >> Trying 67.220.127.145... > >> ............ > >> timeout > >> Laurent Ducos > >> Administrateur Syst?mes et R?seaux > >> 0974770716 > >> 1 d?cembre 2017 15:28 "Michael Kuhn" a ?crit: > >>> Hi > >>> > >>>>> Since about 1 hour I do not have access to debian.koha-community.org > from our public ip > >>>>> 91.121.55.79 > >>>>> Can you give us access again please? > >>>>> since others ip everything is ok > >>> > >>> Right now, http://debian.koha-community.org can be accessed again. > >>> > >>> Best wishes: Michael > >>> -- > >>> Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. > Fachausweis > >>> Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz > >>> T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch > >>> _______________________________________________ > >>> Koha-devel mailing list > >>> Koha-devel at lists.koha-community.org > >>> http://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 at lists.koha-community.org > >> http://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/ > > > > > > > > -- > > Galen Charlton > > Infrastructure and Added Services Manager > > Equinox Open Library Initiative > > phone: 1-877-OPEN-ILS (673-6457) > > email: gmc at equinoxInitiative.org > > web: https://equinoxInitiative.org > > direct: +1 770-709-5581 > > cell: +1 404-984-4366 > > > > -- > Galen Charlton > Infrastructure and Added Services Manager > Equinox Open Library Initiative > phone: 1-877-OPEN-ILS (673-6457) > email: gmc at equinoxInitiative.org > web: https://equinoxInitiative.org > direct: +1 770-709-5581 > cell: +1 404-984-4366 > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -- Joy Nelson Vice President, Director of Implementations ByWater Solutions Support and Consulting for Open Source Software Office: Fort Worth, TX Phone/Fax (888)900-8944 What is Koha? -------------- next part -------------- An HTML attachment was scrubbed... URL: From barton at bywatersolutions.com Fri Dec 1 21:19:16 2017 From: barton at bywatersolutions.com (Barton Chittenden) Date: Fri, 1 Dec 2017 15:19:16 -0500 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: References: <20171201141559.GA3614@lducos-Latitude-E5450> <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> Message-ID: Can confirm. Still down. On Fri, Dec 1, 2017 at 1:22 PM, Joy Nelson wrote: > Galen, > Are you also working on the wiki.koha-community.org site? This is still > down. > > -Joy > > On Fri, Dec 1, 2017 at 8:43 AM, Galen Charlton > wrote: > >> Hi, >> >> It is now back up. >> >> Regards, >> >> Galen >> >> On Fri, Dec 1, 2017 at 9:37 AM, Galen Charlton >> wrote: >> > Hi, >> > >> > I'm taking a look at this now; the VM appears to have fallen over after >> a DOS. >> > >> > Regards, >> > >> > Galen >> > >> > On Fri, Dec 1, 2017 at 9:36 AM, Laurent Ducos >> > wrote: >> >> always closed, Port 80 seems closed >> >> >> >> telnet debian.koha-community.org 80 >> >> Trying 67.220.127.145... >> >> ............ >> >> timeout >> >> Laurent Ducos >> >> Administrateur Syst?mes et R?seaux >> >> 0974770716 >> >> 1 d?cembre 2017 15:28 "Michael Kuhn" a ?crit: >> >>> Hi >> >>> >> >>>>> Since about 1 hour I do not have access to >> debian.koha-community.org from our public ip >> >>>>> 91.121.55.79 >> >>>>> Can you give us access again please? >> >>>>> since others ip everything is ok >> >>> >> >>> Right now, http://debian.koha-community.org can be accessed again. >> >>> >> >>> Best wishes: Michael >> >>> -- >> >>> Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. >> Fachausweis >> >>> Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz >> >>> T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch >> >>> _______________________________________________ >> >>> Koha-devel mailing list >> >>> Koha-devel at lists.koha-community.org >> >>> http://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 at lists.koha-community.org >> >> http://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/ >> > >> > >> > >> > -- >> > Galen Charlton >> > Infrastructure and Added Services Manager >> > Equinox Open Library Initiative >> > phone: 1-877-OPEN-ILS (673-6457) >> > email: gmc at equinoxInitiative.org >> > web: https://equinoxInitiative.org >> > direct: +1 770-709-5581 <(770)%20709-5581> >> > cell: +1 404-984-4366 <(404)%20984-4366> >> >> >> >> -- >> Galen Charlton >> Infrastructure and Added Services Manager >> Equinox Open Library Initiative >> phone: 1-877-OPEN-ILS (673-6457) >> email: gmc at equinoxInitiative.org >> web: https://equinoxInitiative.org >> direct: +1 770-709-5581 <(770)%20709-5581> >> cell: +1 404-984-4366 <(404)%20984-4366> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://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/ >> > > > > -- > Joy Nelson > Vice President, Director of Implementations > > ByWater Solutions > Support and Consulting for Open Source Software > Office: Fort Worth, TX > Phone/Fax (888)900-8944 > What is Koha? > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at bywatersolutions.com Sat Dec 2 17:43:19 2017 From: info at bywatersolutions.com (Brendan Gallagher) Date: Sat, 02 Dec 2017 16:43:19 +0000 Subject: [Koha-devel] no acces to debian.koha-community.org In-Reply-To: References: <20171201141559.GA3614@lducos-Latitude-E5450> <1e416999-d4cf-6fa7-d512-3fefb1461deb@adminkuhn.ch> Message-ID: Looks like it?s back up On Fri, Dec 1, 2017 at 12:19 PM Barton Chittenden < barton at bywatersolutions.com> wrote: > Can confirm. Still down. > > On Fri, Dec 1, 2017 at 1:22 PM, Joy Nelson > wrote: > >> Galen, >> Are you also working on the wiki.koha-community.org site? This is still >> down. >> >> -Joy >> >> On Fri, Dec 1, 2017 at 8:43 AM, Galen Charlton > > wrote: >> >>> Hi, >>> >>> It is now back up. >>> >>> Regards, >>> >>> Galen >>> >>> On Fri, Dec 1, 2017 at 9:37 AM, Galen Charlton >>> wrote: >>> > Hi, >>> > >>> > I'm taking a look at this now; the VM appears to have fallen over >>> after a DOS. >>> > >>> > Regards, >>> > >>> > Galen >>> > >>> > On Fri, Dec 1, 2017 at 9:36 AM, Laurent Ducos >>> > wrote: >>> >> always closed, Port 80 seems closed >>> >> >>> >> telnet debian.koha-community.org 80 >>> >> Trying 67.220.127.145... >>> >> ............ >>> >> timeout >>> >> Laurent Ducos >>> >> Administrateur Syst?mes et R?seaux >>> >> 0974770716 >>> >> 1 d?cembre 2017 15:28 "Michael Kuhn" a ?crit: >>> >>> Hi >>> >>> >>> >>>>> Since about 1 hour I do not have access to >>> debian.koha-community.org from our public ip >>> >>>>> 91.121.55.79 >>> >>>>> Can you give us access again please? >>> >>>>> since others ip everything is ok >>> >>> >>> >>> Right now, http://debian.koha-community.org can be accessed again. >>> >>> >>> >>> Best wishes: Michael >>> >>> -- >>> >>> Gesch?ftsf?hrer ? Diplombibliothekar BBS, Informatiker eidg. >>> Fachausweis >>> >>> Admin Kuhn GmbH ? Pappelstrasse 20 ? 4123 Allschwil ? Schweiz >>> >>> T 0041 (0)61 261 55 61 ? E mik at adminkuhn.ch ? W www.adminkuhn.ch >>> >>> _______________________________________________ >>> >>> Koha-devel mailing list >>> >>> Koha-devel at lists.koha-community.org >>> >>> http://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 at lists.koha-community.org >>> >> http://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/ >>> > >>> > >>> > >>> > -- >>> > Galen Charlton >>> > Infrastructure and Added Services Manager >>> > Equinox Open Library Initiative >>> > phone: 1-877-OPEN-ILS (673-6457) >>> > email: gmc at equinoxInitiative.org >>> > web: https://equinoxInitiative.org >>> > direct: +1 770-709-5581 <(770)%20709-5581> >>> > cell: +1 404-984-4366 <(404)%20984-4366> >>> >>> >>> >>> -- >>> Galen Charlton >>> Infrastructure and Added Services Manager >>> Equinox Open Library Initiative >>> phone: 1-877-OPEN-ILS (673-6457) >>> email: gmc at equinoxInitiative.org >>> web: https://equinoxInitiative.org >>> direct: +1 770-709-5581 <(770)%20709-5581> >>> cell: +1 404-984-4366 <(404)%20984-4366> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> http://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/ >>> >> >> >> >> -- >> Joy Nelson >> Vice President, Director of Implementations >> >> ByWater Solutions >> Support and Consulting for Open Source Software >> Office: Fort Worth, TX >> Phone/Fax (888)900-8944 >> What is Koha? >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://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 at lists.koha-community.org > http://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/ -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Mon Dec 4 00:05:18 2017 From: dcook at prosentient.com.au (David Cook) Date: Mon, 4 Dec 2017 10:05:18 +1100 Subject: [Koha-devel] SIG DIE in returns.pl In-Reply-To: References: <7c8f95aa-2d42-2ceb-5177-f742ad64bf90@biblibre.com> <5a9952fd-4ea9-a749-6667-048896afbb31@oha.it> Message-ID: <019901d36c8b$2ff86be0$8fe943a0$@prosentient.com.au> Looks like debug code to me. I?ve used things like that before in development, but I don?t know why you?d have it in production code? 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-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Tomas Cohen Arazi Sent: Thursday, 30 November 2017 9:20 PM To: Francesco Rivetti Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] SIG DIE in returns.pl We need to get rid of that. El jue., 30 de nov. de 2017 7:05 a. m., Francesco Rivetti > escribi?: On 30. nov. 2017 09:57, Fridolin SOMERS wrote: > use Carp 'verbose'; > $SIG{ __DIE__ } = sub { Carp::confess( @_ ) }; I think it will be applied to all pages (and everything) _AFTER_ this is run the first time on that forked process F _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org http://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/ -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From johan at spbcu.ru Mon Dec 4 09:18:43 2017 From: johan at spbcu.ru (Johan Seyfferdt) Date: Mon, 4 Dec 2017 11:18:43 +0300 Subject: [Koha-devel] newbie would appreciate help! Message-ID: Hello. Thank you for adding me to this mailing list. I have a question. I am a sysadmin in St Petersburg, Russia and we are in the process of moving to Koha. So I am a newbie :) I chosed the unimarc option as our database is in rusmarc. We have our database in .mrc format, it is about 27 000 books in cyrilic, english and german. I was able to setup koha import that database but the search function does not work. I did a lot of googling, i tried kooha 16.05, 16.11, 17.05 on Debain 8 and 9 but without avail... Any help will be truly appreciated! as i am truly stuck. Johan Seyfferdt -------------- next part -------------- An HTML attachment was scrubbed... URL: From michael.hafen at washk12.org Mon Dec 4 18:32:25 2017 From: michael.hafen at washk12.org (Michael Hafen) Date: Mon, 4 Dec 2017 10:32:25 -0700 Subject: [Koha-devel] newbie would appreciate help! In-Reply-To: References: Message-ID: There are a couple things I would recommend. First is to make sure the field of the record you are searching for made it into the database. If you aren't familiar with database you may need some help from someone who is. I believe the database schema is still in isntaller/data/mysql/kohastructure.sql. You are probably looking for biblio.title or biblio.seriestitle or biblioitems.isbn or items.barcode. The second thing is to make sure the search engines database got populated too. You are probably using the idzebra search engine. So make sure /usr/bin/zebrasrv is running, make sure you have run the bin/migration_tools/rebuild_zebra.pl script right, and make sure the value you are searching for is in the idzebra database. The way I would do that is with the yaz-client. I have a simple yaz script for that purpose that looks like this: set_cclfile /usr/local/koha3.2/etc/zebradb/ccl.properties set_cqlfile /usr/local/koha3.2/etc/zebradb/cql.properties authentication kohauser:zebrastripes open unix:/usr/local/koha3.2/var/run/zebradb/bibliosocket base biblios format xml elements marcxml querytype ccl2rpn find kw,wrdl="Maze Runner" and branch=703 and mc-itype,phr=F show 2 delete close exit Of course you will have to change the properties and socket paths to match your install. Then run this with `yaz-client -f /tmp/yaz-zebra-test.txt`. Sometimes I've had to put the auth and property files commands on the command line to get that to work, which looks like `yaz-client -u kohauser:zebrastripes -c /usr/local/koha3.2/etc/zebradb/ccl.properties -q /usr/local/koha3.2/etc/zebradb/cql.properties -f /tmp/yaz-zebra-test.txt unix:/usr/local/koha3.2/var/run/zebradb/bibliosocket`, again changing the paths to match your install. On Mon, Dec 4, 2017 at 1:18 AM, Johan Seyfferdt wrote: > Hello. > > Thank you for adding me to this mailing list. > > I have a question. > > I am a sysadmin in St Petersburg, Russia and we are in the process of > moving to Koha. So I am a newbie :) > > I chosed the unimarc option as our database is in rusmarc. We have our > database in .mrc format, it is about 27 000 books in cyrilic, english and > german. > > I was able to setup koha import that database but the search function does > not work. > > I did a lot of googling, i tried kooha 16.05, 16.11, 17.05 on Debain 8 and > 9 but without avail... > > Any help will be truly appreciated! as i am truly stuck. > > Johan Seyfferdt > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -- Michael Hafen Washington County School District Technology Department Systems Analyst -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Mon Dec 4 20:09:19 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Mon, 04 Dec 2017 19:09:19 +0000 Subject: [Koha-devel] SIG DIE in returns.pl In-Reply-To: <7c8f95aa-2d42-2ceb-5177-f742ad64bf90@biblibre.com> References: <7c8f95aa-2d42-2ceb-5177-f742ad64bf90@biblibre.com> Message-ID: See bug 19746, please SO+QA On Thu, 30 Nov 2017 at 05:57 Fridolin SOMERS wrote: > Hie, > > With plack when some code fails, there is always in log a reference to > circ/returns.pl o_O at start of stack trace. > > I found that there is in this page : > > use Carp 'verbose'; > $SIG{ __DIE__ } = sub { Carp::confess( @_ ) }; > > Added by commit bb6277ffcc593685554112d770ac273c9efeda33 > Bug 14464: Add ability to cancel waiting holds from checkin screen > > Is this for debug purpopse only ? > Why only this page ? > Should it be moved to plack.psgi ? > > Regards, > > -- > Fridolin SOMERS > BibLibre - software and system maintainer > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Tue Dec 5 00:49:14 2017 From: dcook at prosentient.com.au (David Cook) Date: Tue, 5 Dec 2017 10:49:14 +1100 Subject: [Koha-devel] newbie would appreciate help! In-Reply-To: References: Message-ID: <024501d36d5a$7dabc650$790352f0$@prosentient.com.au> Hi Johan, Which instructions did you use for installing Koha? That will likely determine how best we can help you : ). 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-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Johan Seyfferdt Sent: Monday, 4 December 2017 7:19 PM To: koha-devel at lists.koha-community.org Subject: [Koha-devel] newbie would appreciate help! Hello. Thank you for adding me to this mailing list. I have a question. I am a sysadmin in St Petersburg, Russia and we are in the process of moving to Koha. So I am a newbie :) I chosed the unimarc option as our database is in rusmarc. We have our database in .mrc format, it is about 27 000 books in cyrilic, english and german. I was able to setup koha import that database but the search function does not work. I did a lot of googling, i tried kooha 16.05, 16.11, 17.05 on Debain 8 and 9 but without avail... Any help will be truly appreciated! as i am truly stuck. Johan Seyfferdt -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Tue Dec 5 20:59:08 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Tue, 05 Dec 2017 19:59:08 +0000 Subject: [Koha-devel] REST api developments In-Reply-To: References: Message-ID: Dear Bob et al, I worked on the patrons endpoint and it is ready for testing. Beware new bug dependencies. I'll be looking forward to those reviews from you! Tom?s El mi?., 22 nov. 2017 a las 20:26, Bob Birchall () escribi?: > On 23/11/17 06:11, Tomas Cohen Arazi wrote: > > Dear friends, I write this email to let you know me and the ByWater > friends are committed to getting endpoints written, so development projects > you are working on can succeed. > > With recent additions and specially all enhancements surrounding bug > 19410, we should be able to start writing endpoints faster and easier. The > REST api is top priority for us, and making it easier to code, one of our > short-term goals. > > Let us know the endpoints your project might benefit from, we can commit > to writing those endpoints, or help you in the process. We still need to > have better documentation, but we'll be looking for 'REST api' tagged bugs > trying to help. > > Kind regards > > > Hi Tomas, > We need bug 16330 > to > progress. We can help with testing and sign-offs. > Thanks, > Bob > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob at calyx.net.au Wed Dec 6 07:39:13 2017 From: bob at calyx.net.au (Bob Birchall) Date: Wed, 6 Dec 2017 17:39:13 +1100 Subject: [Koha-devel] Fwd: Re: REST api developments In-Reply-To: References: Message-ID: Tomas this is awesome, thank you. I expect we'll be able to review this tomorrow morning (AEST). This is not my area, but the Identity Provider we are working with towards account provisioning drew my attention to a new standard from IETF . Apparently SCIM2 is now complete and is the relevant standard for this type of thing. There is full information here: http://www.simplecloud.info/ Have we heard of this and is it relevant to the work on bug 16330 ? Bob -------- Forwarded Message -------- Subject: Re: [Koha-devel] REST api developments Date: Tue, 05 Dec 2017 19:59:08 +0000 From: Tomas Cohen Arazi To: Bob Birchall CC: koha-devel at lists.koha-community.org Dear Bob et al, I worked on the patrons endpoint and it is ready for testing. Beware new bug dependencies. I'll be looking forward to those reviews from you! Tom?s El mi?., 22 nov. 2017 a las 20:26, Bob Birchall (>) escribi?: On 23/11/17 06:11, Tomas Cohen Arazi wrote: > Dear friends, I write this email to let you know me and the > ByWater friends are committed to getting endpoints written, so > development projects you are working on can succeed. > > With recent additions and specially all enhancements surrounding > bug 19410, we should be able to start writing endpoints faster and > easier. The REST api is top priority for us, and making it easier > to code, one of our short-term goals. > > Let us know the endpoints your project might benefit from, we can > commit to writing those endpoints, or help you in the process. We > still need to have better documentation, but we'll be looking for > 'REST api' tagged bugs trying to help. > > Kind regards Hi Tomas, We need bug 16330 to progress. We can help with testing and sign-offs. Thanks, Bob _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org http://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/ -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From oha at oha.it Wed Dec 6 09:58:27 2017 From: oha at oha.it (Francesco Rivetti) Date: Wed, 6 Dec 2017 09:58:27 +0100 Subject: [Koha-devel] REST api developments In-Reply-To: References: Message-ID: On 22. nov. 2017 20:11, Tomas Cohen Arazi wrote: > Dear friends, I write this email to let you know me and the ByWater > friends are committed to getting endpoints written, so development > projects you are working on can succeed. This is great, thank you! F From tomascohen at gmail.com Wed Dec 6 16:13:13 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 06 Dec 2017 15:13:13 +0000 Subject: [Koha-devel] REST api: some needed changes / vote proposal Message-ID: Hi everyone, we've moved forward with the REST api devs, and some decisions we made at the beginning should be dealt with now, before it is too late :-D Right now the so-called REST api consists in 5 endpoints. Vendors: - /acquisitions/vendors - /acquisitions/vendors/{vendor_id} Cities: - /cities - /cities/{cityid} Holds: - /holds - /holds/{reserve_id} Patrons: - /patrons - /patrons/{borrowernumber} Illrequests: - /illrequests When implementing the vendors endpoint, I followed the api first approach, which implies we first think of the api itself, and how it is going to be used, and then think about the implementation. The result is that the exposed attribute names don't match the DB columns (because we picked more meaningful names), and (for example) unused attributes aren't even exposed. When it comes to the previously integrated endpoints, they mostly mimick the DB structure and thus the external api consumers see things that are highly inconsistent: We call them holds, but the ID is reserve_id instead of just hold_id, same for borrowernumber instead of patron_id. New endpoints are being developed with this in mind, but the already implemented ones need to get fixed. As the REST api is already at its first stages I suggest we just change those attributes and notify on the release notes about the change, but it is worth being voted. So I added it to next's dev meeting agenda. It is an urgent decision, as some of fields that would be renamed, are FK for the new endpoints being developed. I hope everyone interested on this gets involved in the discussion on this thread, and we can move forward just voting on the dev meeting. Thanks in advance! -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From josef.moravec at gmail.com Thu Dec 7 08:54:57 2017 From: josef.moravec at gmail.com (Josef Moravec) Date: Thu, 07 Dec 2017 07:54:57 +0000 Subject: [Koha-devel] REST api: some needed changes / vote proposal In-Reply-To: References: Message-ID: Hi Tomas (and all ;) thank you for the work on API! I like this approach. I think as the capabilities of the API is still just small amount of Koha capabilities, and as it is fairly new, we could take this approach and just change the naming conventions in current endpoints. Better do it now and right. Regards Josef st 6. 12. 2017 v 16:13 odes?latel Tomas Cohen Arazi napsal: > Hi everyone, we've moved forward with the REST api devs, and some > decisions we made at the beginning should be dealt with now, before it is > too late :-D > > Right now the so-called REST api consists in 5 endpoints. > > Vendors: > - /acquisitions/vendors > - /acquisitions/vendors/{vendor_id} > Cities: > - /cities > - /cities/{cityid} > Holds: > - /holds > - /holds/{reserve_id} > Patrons: > - /patrons > - /patrons/{borrowernumber} > Illrequests: > - /illrequests > > When implementing the vendors endpoint, I followed the api first approach, > which implies we first think of the api itself, and how it is going to be > used, and then think about the implementation. The result is that the > exposed attribute names don't match the DB columns (because we picked more > meaningful names), and (for example) unused attributes aren't even exposed. > > When it comes to the previously integrated endpoints, they mostly mimick > the DB structure and thus the external api consumers see things that are > highly inconsistent: > > We call them holds, but the ID is reserve_id instead of just hold_id, same > for borrowernumber instead of patron_id. > > New endpoints are being developed with this in mind, but the already > implemented ones need to get fixed. As the REST api is already at its first > stages I suggest we just change those attributes and notify on the release > notes about the change, but it is worth being voted. So I added it to > next's dev meeting agenda. It is an urgent decision, as some of fields that > would be renamed, are FK for the new endpoints being developed. > > I hope everyone interested on this gets involved in the discussion on this > thread, and we can move forward just voting on the dev meeting. > > Thanks in advance! > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Thu Dec 7 13:15:36 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 07 Dec 2017 12:15:36 +0000 Subject: [Koha-devel] REST api: some needed changes / vote proposal In-Reply-To: References: Message-ID: See also the previous discussion on that topic - http://lists.koha-community.org/pipermail/koha-devel/2017-March/043576.html On Wed, 6 Dec 2017 at 12:13 Tomas Cohen Arazi wrote: > Hi everyone, we've moved forward with the REST api devs, and some > decisions we made at the beginning should be dealt with now, before it is > too late :-D > > Right now the so-called REST api consists in 5 endpoints. > > Vendors: > - /acquisitions/vendors > - /acquisitions/vendors/{vendor_id} > Cities: > - /cities > - /cities/{cityid} > Holds: > - /holds > - /holds/{reserve_id} > Patrons: > - /patrons > - /patrons/{borrowernumber} > Illrequests: > - /illrequests > > When implementing the vendors endpoint, I followed the api first approach, > which implies we first think of the api itself, and how it is going to be > used, and then think about the implementation. The result is that the > exposed attribute names don't match the DB columns (because we picked more > meaningful names), and (for example) unused attributes aren't even exposed. > > When it comes to the previously integrated endpoints, they mostly mimick > the DB structure and thus the external api consumers see things that are > highly inconsistent: > > We call them holds, but the ID is reserve_id instead of just hold_id, same > for borrowernumber instead of patron_id. > > New endpoints are being developed with this in mind, but the already > implemented ones need to get fixed. As the REST api is already at its first > stages I suggest we just change those attributes and notify on the release > notes about the change, but it is worth being voted. So I added it to > next's dev meeting agenda. It is an urgent decision, as some of fields that > would be renamed, are FK for the new endpoints being developed. > > I hope everyone interested on this gets involved in the discussion on this > thread, and we can move forward just voting on the dev meeting. > > Thanks in advance! > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jonathan.druart at bugs.koha-community.org Thu Dec 7 16:43:13 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Thu, 07 Dec 2017 15:43:13 +0000 Subject: [Koha-devel] Update koha-misc4dev Message-ID: Hi devs, If you are using the koha-misc4dev (in a devbox for instance), you should update it to use the new commit I have just pushed. It will fix an error caused by bug 19724 In a dev box: `cd /home/vagrant/misc4dev; git fetch origin; git rebase origin/master` should do the job Cheers, Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From oleonard at myacpl.org Thu Dec 7 18:46:43 2017 From: oleonard at myacpl.org (Owen Leonard) Date: Thu, 7 Dec 2017 12:46:43 -0500 Subject: [Koha-devel] Bug 19767: serial-issues.pl unused? Message-ID: Bug 19767 - serial-issues.pl is unused and should be removed https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19767 I think serial-issues.pl, serial-issues.tt, and serial-issues-full.tt are obsolete and should be removed. Does anyone know of any reason not to? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From josef.moravec at gmail.com Fri Dec 8 07:56:12 2017 From: josef.moravec at gmail.com (Josef Moravec) Date: Fri, 08 Dec 2017 06:56:12 +0000 Subject: [Koha-devel] Bug 19767: serial-issues.pl unused? In-Reply-To: References: Message-ID: I agree, it's not linked from anywhere as I can say, and looks like it's not even fully functional... at least in 17.05 where I make quick test Best Josef ?t 7. 12. 2017 v 18:46 odes?latel Owen Leonard napsal: > Bug 19767 - serial-issues.pl is unused and should be removed > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19767 > > I think serial-issues.pl, serial-issues.tt, and serial-issues-full.tt > are obsolete and should be removed. > > Does anyone know of any reason not to? > > -- Owen > > -- > Web Developer > Athens County Public Libraries > http://www.myacpl.org > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Fri Dec 8 14:59:23 2017 From: paul.poulain at biblibre.com (Paul Poulain) Date: Fri, 8 Dec 2017 14:59:23 +0100 Subject: [Koha-devel] newbie would appreciate help! In-Reply-To: References: Message-ID: <9caaa0c8-1c51-95d7-ae52-88cac618b18b@biblibre.com> Hi Johan, The most common case when search does not work is because there's some mix between UNIMARC and MARC21 (for example, zebra configured MARC21 and Koha UNIMARC). But there can be other reasons. So we need details on how you installed Koha. Le 04/12/2017 ? 09:18, Johan Seyfferdt a ?crit?: > Hello. > > Thank you for adding me to this mailing list. > I have a question. > I am a sysadmin in St Petersburg, Russia and we are in the process of > moving to Koha.? So I am a newbie :) > I chosed the unimarc option as our database is in rusmarc. We have our > database in .mrc format,? it is about 27 000 books in cyrilic, english > and german. > I was able to setup koha import that database but the search function > does not work. > I did a lot of googling, i tried kooha 16.05, 16.11, 17.05 on Debain 8 > and 9 but without avail... > Any help will be truly appreciated! as i am truly stuck. -- Paul Poulain, Associ?-g?rant / co-owner BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Open Source software and services for libraries From tomascohen at gmail.com Fri Dec 8 15:27:34 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 08 Dec 2017 14:27:34 +0000 Subject: [Koha-devel] Patrons endpoint help needed Message-ID: Hi everyone, I've submitted a patchset to bug 19784 [1]. This is my starting point for the umbrella bug (19774). Next endpoints to fix are /acquisitions/vendors, /cities, /holds and /illrequests. Those are easier IMHO. On the /patrons one, I already changed - borrowernumber -> patron_id - branchcode -> library_id - categorycode -> category_id The needed code for this (or any) attribute rename is already done. The remaining work is mostly adding the mappings we would like to add, to the _to_model and _to_api functions. I now need help from you on the parameter names (patrons have really misleading attribute names, and they don't match the UI most of the time). Please comment here, and preferably on the bug itself. If you contribute a patch for your proposed change, please add a test on the specific attribute on one of the GET tests too. We try to cover all the special cases with tests. Ah, snake case was picked at some point, so 'cardnumber' could become 'card_number', for example. Thanks for any input. [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19784 -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Fri Dec 8 15:42:42 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 08 Dec 2017 14:42:42 +0000 Subject: [Koha-devel] Patrons endpoint help needed In-Reply-To: References: Message-ID: I forgot to mention we have coding guidelines for the REST api [1] which say the terminology we use, should be the less Koha-specific we can. Please keep that in mind! Thanks! [1] https://wiki.koha-community.org/wiki/Coding_Guidelines_-_API#SWAGGER1.2:_Resource_names El vie., 8 dic. 2017 a las 11:27, Tomas Cohen Arazi () escribi?: > Hi everyone, I've submitted a patchset to bug 19784 [1]. This is my > starting point for the umbrella bug (19774). Next endpoints to fix are > /acquisitions/vendors, /cities, /holds and /illrequests. Those are easier > IMHO. > > On the /patrons one, I already changed > - borrowernumber -> patron_id > - branchcode -> library_id > - categorycode -> category_id > > The needed code for this (or any) attribute rename is already done. The > remaining work is mostly adding the mappings we would like to add, to the > _to_model and _to_api functions. > > I now need help from you on the parameter names (patrons have really > misleading attribute names, and they don't match the UI most of the time). > Please comment here, and preferably on the bug itself. If you contribute a > patch for your proposed change, please add a test on the specific attribute > on one of the GET tests too. We try to cover all the special cases with > tests. > > Ah, snake case was picked at some point, so 'cardnumber' could become > 'card_number', for example. > > Thanks for any input. > > [1] https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19784 > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From mirko at abunchofthings.net Fri Dec 8 15:59:35 2017 From: mirko at abunchofthings.net (Mirko Tietgen) Date: Fri, 8 Dec 2017 15:59:35 +0100 Subject: [Koha-devel] Koha 17.11.00 package / repository rollover Message-ID: Good news everyone, the Debian package for Koha 17.11.00 is now available from the community repository. With the new major release, the repository structure will change slightly. Koha 17.11 is now 'stable'. Koha 17.05 is now 'oldstable' Koha 16.11 is still maintained, but no futher Debian packages are provided. The last packaged version 16.11.14 is available from the 16.11 pocket of the repository. Koha 16.05 has had its last release two weeks ago and is no longer maintained. The final version 16.05.19 is now available from the 16.05 pocket of the repository. Please check the wiki for detailed apt configuration information: https://wiki.koha-community.org/wiki/Koha_on_Debian#Set_up_package_sources Have a nice weekend, Mirko From tomascohen at gmail.com Fri Dec 8 17:38:44 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 08 Dec 2017 16:38:44 +0000 Subject: [Koha-devel] Koha 17.11.00 package / repository rollover In-Reply-To: References: Message-ID: Great news, Mirko! Thanks El vie., 8 de dic. de 2017 11:59 a. m., Mirko Tietgen < mirko at abunchofthings.net> escribi?: > Good news everyone, > > the Debian package for Koha 17.11.00 is now available from the > community repository. > > With the new major release, the repository structure will change > slightly. > > Koha 17.11 is now 'stable'. > Koha 17.05 is now 'oldstable' > > Koha 16.11 is still maintained, but no futher Debian packages are > provided. The last packaged version 16.11.14 is available from the > 16.11 pocket of the repository. > > Koha 16.05 has had its last release two weeks ago and is no longer > maintained. The final version 16.05.19 is now available from the > 16.05 pocket of the repository. > > Please check the wiki for detailed apt configuration information: > https://wiki.koha-community.org/wiki/Koha_on_Debian#Set_up_package_sources > > Have a nice weekend, > > Mirko > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From josef.moravec at gmail.com Fri Dec 8 18:20:47 2017 From: josef.moravec at gmail.com (Josef Moravec) Date: Fri, 08 Dec 2017 17:20:47 +0000 Subject: [Koha-devel] [Koha] Koha 17.11.00 package / repository rollover In-Reply-To: References: Message-ID: Nice, thank you Mirko! p? 8. 12. 2017 v 17:39 odes?latel Tomas Cohen Arazi napsal: > Great news, Mirko! > > Thanks > > El vie., 8 de dic. de 2017 11:59 a. m., Mirko Tietgen < > mirko at abunchofthings.net> escribi?: > > > Good news everyone, > > > > the Debian package for Koha 17.11.00 is now available from the > > community repository. > > > > With the new major release, the repository structure will change > > slightly. > > > > Koha 17.11 is now 'stable'. > > Koha 17.05 is now 'oldstable' > > > > Koha 16.11 is still maintained, but no futher Debian packages are > > provided. The last packaged version 16.11.14 is available from the > > 16.11 pocket of the repository. > > > > Koha 16.05 has had its last release two weeks ago and is no longer > > maintained. The final version 16.05.19 is now available from the > > 16.05 pocket of the repository. > > > > Please check the wiki for detailed apt configuration information: > > > https://wiki.koha-community.org/wiki/Koha_on_Debian#Set_up_package_sources > > > > Have a nice weekend, > > > > Mirko > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at lists.koha-community.org > > http://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/ > > > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > _______________________________________________ > Koha mailing list http://koha-community.org > Koha at lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Sun Dec 10 21:54:00 2017 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Sun, 10 Dec 2017 21:54:00 +0100 Subject: [Koha-devel] Bug 19767: serial-issues.pl unused? In-Reply-To: References: Message-ID: <208e308f-e6c0-fa6b-4c01-ff5917374de8@web.de> +1 for removing the dead pages and code On 08.12.2017 07:56, Josef Moravec wrote: > I agree, > > it's not linked from anywhere as I can say, and looks like it's not > even fully functional... at least in 17.05 where I make quick test > > Best > > Josef > > ?t 7. 12. 2017 v 18:46 odes?latel Owen Leonard > napsal: > > Bug 19767 - serial-issues.pl is unused > and should be removed > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19767 > > I think serial-issues.pl , > serial-issues.tt , and > serial-issues-full.tt > are obsolete and should be removed. > > Does anyone know of any reason not to? > > ?-- Owen > > -- > Web Developer > Athens County Public Libraries > http://www.myacpl.org > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > http://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 at lists.koha-community.org > http://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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Mon Dec 11 09:28:10 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Mon, 11 Dec 2017 09:28:10 +0100 Subject: [Koha-devel] Koha 17.11.00 package / repository rollover In-Reply-To: References: Message-ID: <45e43ae7-a679-9955-d256-4011d47a44f7@biblibre.com> Thanks a lot Mirko. We where waiting this like children for Santa the 25th ;) Kind regards, Le 08/12/2017 ? 15:59, Mirko Tietgen a ?crit?: > Good news everyone, > > the Debian package for Koha 17.11.00 is now available from the > community repository. > > With the new major release, the repository structure will change > slightly. > > Koha 17.11 is now 'stable'. > Koha 17.05 is now 'oldstable' > > Koha 16.11 is still maintained, but no futher Debian packages are > provided. The last packaged version 16.11.14 is available from the > 16.11 pocket of the repository. > > Koha 16.05 has had its last release two weeks ago and is no longer > maintained. The final version 16.05.19 is now available from the > 16.05 pocket of the repository. > > Please check the wiki for detailed apt configuration information: > https://wiki.koha-community.org/wiki/Koha_on_Debian#Set_up_package_sources > > Have a nice weekend, > > Mirko > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -- Fridolin SOMERS BibLibre - software and system maintainer From fridolin.somers at biblibre.com Mon Dec 11 09:31:10 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Mon, 11 Dec 2017 09:31:10 +0100 Subject: [Koha-devel] SIG DIE in returns.pl In-Reply-To: References: <7c8f95aa-2d42-2ceb-5177-f742ad64bf90@biblibre.com> Message-ID: Cool, thanks for creating the post on bugzilla. I see it is Passed QA Le 04/12/2017 ? 20:09, Jonathan Druart a ?crit?: > See bug 19746, please SO+QA > > On Thu, 30 Nov 2017 at 05:57 Fridolin SOMERS > wrote: > >> Hie, >> >> With plack when some code fails, there is always in log a reference to >> circ/returns.pl o_O at start of stack trace. >> >> I found that there is in this page : >> >> use Carp 'verbose'; >> $SIG{ __DIE__ } = sub { Carp::confess( @_ ) }; >> >> Added by commit bb6277ffcc593685554112d770ac273c9efeda33 >> Bug 14464: Add ability to cancel waiting holds from checkin screen >> >> Is this for debug purpopse only ? >> Why only this page ? >> Should it be moved to plack.psgi ? >> >> Regards, >> >> -- >> Fridolin SOMERS >> BibLibre - software and system maintainer >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://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/ >> > -- Fridolin SOMERS BibLibre - software and system maintainer From johan at spbcu.ru Mon Dec 11 09:50:25 2017 From: johan at spbcu.ru (Johan Seyfferdt) Date: Mon, 11 Dec 2017 11:50:25 +0300 Subject: [Koha-devel] error with Z39.50 Message-ID: Hello, sorry for asking another question We ran into another error this time with z39.50. We added several servers but when trying to use this service we get the following error. Unsupported UNIMARC character encoding [] for XML output for UNIMARC; 100$a -> at /usr/share/perl5/MARC/File/XML.pm line 568. For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error. Any help will be greatly appreciated! Johan -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Mon Dec 11 16:11:05 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Mon, 11 Dec 2017 16:11:05 +0100 Subject: [Koha-devel] error with Z39.50 In-Reply-To: References: Message-ID: <6a359b80-c34c-2e2a-b265-d52a6df3507c@biblibre.com> Hi, Which is the MARC flavour or your catalog ? Which z39.50 server fails ? You can not mix UNIMARC / MARC21. Only if you transform the results. Regards, Le 11/12/2017 ? 09:50, Johan Seyfferdt a ?crit?: > Hello, sorry for asking another question > > We ran into another error this time with z39.50. > > We added several servers but when trying to use this service we get the > following error. > > Unsupported UNIMARC character encoding [] for XML output for UNIMARC; 100$a > -> at /usr/share/perl5/MARC/File/XML.pm line 568. > For help, please send mail to the webmaster ([no address given]), giving > this error message and the time and date of the error. > > Any help will be greatly appreciated! > > Johan > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -- Fridolin SOMERS BibLibre - software and system maintainer From fridolin.somers at biblibre.com Mon Dec 11 16:14:39 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Mon, 11 Dec 2017 16:14:39 +0100 Subject: [Koha-devel] Bug 19767: serial-issues.pl unused? In-Reply-To: References: Message-ID: Cool, Also opac/opac-serial-issues.pl ? Regards, Le 07/12/2017 ? 18:46, Owen Leonard a ?crit?: > Bug 19767 - serial-issues.pl is unused and should be removed > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19767 > > I think serial-issues.pl, serial-issues.tt, and serial-issues-full.tt > are obsolete and should be removed. > > Does anyone know of any reason not to? > > -- Owen > -- Fridolin SOMERS BibLibre - software and system maintainer From ephetteplace at cca.edu Mon Dec 11 18:29:00 2017 From: ephetteplace at cca.edu (Eric Phetteplace) Date: Mon, 11 Dec 2017 09:29:00 -0800 Subject: [Koha-devel] Bug 19767: serial-issues.pl unused? In-Reply-To: References: Message-ID: It looks like opac-serial-issues.pl is linked at the bottom of the Subscriptions tab in the OPAC detail view. I can't say we're actively using it but I know I've pointed it out as a tool for staff to show patrons, just a different way of browsing which issues we have. I wouldn't want it removed without a larger discussion around whether it's worth having. Best, ERIC PHETTEPLACE Systems Librarian libraries.cca.edu | vault.cca.edu | 510.594.3660 5212 Broadway, Oakland, CA 94618 1111 8th St., San Francisco, CA 94107 Preferred Pronoun(s): he/him :(){ :|: & };: On Mon, Dec 11, 2017 at 7:14 AM, Fridolin SOMERS < fridolin.somers at biblibre.com> wrote: > Cool, > > Also opac/opac-serial-issues.pl ? > > Regards, > > Le 07/12/2017 ? 18:46, Owen Leonard a ?crit : > >> Bug 19767 - serial-issues.pl is unused and should be removed >> https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19767 >> >> I think serial-issues.pl, serial-issues.tt, and serial-issues-full.tt >> are obsolete and should be removed. >> >> Does anyone know of any reason not to? >> >> -- Owen >> >> > -- > Fridolin SOMERS > BibLibre - software and system maintainer > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From pianohacker at gmail.com Tue Dec 12 00:27:38 2017 From: pianohacker at gmail.com (Jesse) Date: Mon, 11 Dec 2017 16:27:38 -0700 Subject: [Koha-devel] SIG DIE in returns.pl In-Reply-To: References: <7c8f95aa-2d42-2ceb-5177-f742ad64bf90@biblibre.com> Message-ID: Just to confirm, that was added as a debugging aid and I forgot to take it out when I was done. Thanks for catching it! 2017-12-11 1:31 GMT-07:00 Fridolin SOMERS : > Cool, thanks for creating the post on bugzilla. > I see it is Passed QA > > > Le 04/12/2017 ? 20:09, Jonathan Druart a ?crit : > >> See bug 19746, please SO+QA >> >> On Thu, 30 Nov 2017 at 05:57 Fridolin SOMERS < >> fridolin.somers at biblibre.com> >> wrote: >> >> Hie, >>> >>> With plack when some code fails, there is always in log a reference to >>> circ/returns.pl o_O at start of stack trace. >>> >>> I found that there is in this page : >>> >>> use Carp 'verbose'; >>> $SIG{ __DIE__ } = sub { Carp::confess( @_ ) }; >>> >>> Added by commit bb6277ffcc593685554112d770ac273c9efeda33 >>> Bug 14464: Add ability to cancel waiting holds from checkin screen >>> >>> Is this for debug purpopse only ? >>> Why only this page ? >>> Should it be moved to plack.psgi ? >>> >>> Regards, >>> >>> -- >>> Fridolin SOMERS >>> BibLibre - software and system maintainer >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> http://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/ >>> >>> >> > -- > Fridolin SOMERS > BibLibre - software and system maintainer > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -- Jesse Weaver -------------- next part -------------- An HTML attachment was scrubbed... URL: From oleonard at myacpl.org Tue Dec 12 14:35:53 2017 From: oleonard at myacpl.org (Owen Leonard) Date: Tue, 12 Dec 2017 08:35:53 -0500 Subject: [Koha-devel] Bug 19767: serial-issues.pl unused? In-Reply-To: References: Message-ID: > It looks like opac-serial-issues.pl is linked at the bottom of the Subscriptions tab in the OPAC detail view. Agreed. I won't be touching that one. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From julian.maurice at biblibre.com Wed Dec 13 14:34:07 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Wed, 13 Dec 2017 14:34:07 +0100 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context Message-ID: Hi developers, I stumbled upon a line of code recently and I can't figure out why it has be done this way. I hope you can help me :) The line in question is in Koha::Objects::find: croak 'Cannot use "->find" in list context' if wantarray; I read the two bugs (18539 and 18179) and the link given by Jonathan but I still don't understand why the call in list context has been forbidden. Why not simply return undef (an explicit undef) when no records have be found ? It would work as expected in scalar and list contexts. Here is a possible rewrite of 'find' to better explain what I mean: sub find { my ( $self, @pars ) = @_; my $object = undef; @pars = grep { defined } @pars; if (@pars) { my $result = $self->_resultset()->find(@pars); if ($result) { $object = $self->object_class()->_new_from_dbic($result); } } return $object; } @a = Koha::Patrons->find('foo'); # would result in @a = (undef) {a => K::P->find('foo'), b => 'bar'}; # would result in {a => undef, b => 'bar'} Please tell me what you think. -- Julian Maurice BibLibre From M.de.Rooy at rijksmuseum.nl Wed Dec 13 14:50:21 2017 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Wed, 13 Dec 2017 13:50:21 +0000 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context In-Reply-To: References: Message-ID: Find is supposed for retrieving one result not multiple ones. Use search instead. Using find in a list context is not correct. ________________________________ Van: koha-devel-bounces at lists.koha-community.org namens Julian Maurice Verzonden: woensdag 13 december 2017 14:34:07 Aan: koha-devel at lists.koha-community.org Onderwerp: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context Hi developers, I stumbled upon a line of code recently and I can't figure out why it has be done this way. I hope you can help me :) The line in question is in Koha::Objects::find: croak 'Cannot use "->find" in list context' if wantarray; I read the two bugs (18539 and 18179) and the link given by Jonathan but I still don't understand why the call in list context has been forbidden. Why not simply return undef (an explicit undef) when no records have be found ? It would work as expected in scalar and list contexts. Here is a possible rewrite of 'find' to better explain what I mean: sub find { my ( $self, @pars ) = @_; my $object = undef; @pars = grep { defined } @pars; if (@pars) { my $result = $self->_resultset()->find(@pars); if ($result) { $object = $self->object_class()->_new_from_dbic($result); } } return $object; } @a = Koha::Patrons->find('foo'); # would result in @a = (undef) {a => K::P->find('foo'), b => 'bar'}; # would result in {a => undef, b => 'bar'} Please tell me what you think. -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org http://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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Wed Dec 13 14:55:01 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Wed, 13 Dec 2017 14:55:01 +0100 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context In-Reply-To: References: Message-ID: <954b9a6f-0e7c-6ca4-8cbd-95772c93f1df@biblibre.com> I know that find is supposed to retrieve only one result. That's why we shouldn't have to care about the context, it's never ambiguous. I should be allowed to write push @patrons, Koha::Patrons->find($borrowernumber); without specifying that I only want one record (using 'scalar') Le 13/12/2017 ? 14:50, Marcel de Rooy a ?crit?: > Find is supposed for retrieving one result not multiple ones. Use search > instead. > > Using find in a list context is not correct. > > ------------------------------------------------------------------------ > *Van:* koha-devel-bounces at lists.koha-community.org > namens Julian Maurice > > *Verzonden:* woensdag 13 december 2017 14:34:07 > *Aan:* koha-devel at lists.koha-community.org > *Onderwerp:* [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls > in list context > ? > Hi developers, > > I stumbled upon a line of code recently and I can't figure out why it > has be done this way. I hope you can help me :) > > The line in question is in Koha::Objects::find: > > ??? croak 'Cannot use "->find" in list context' if wantarray; > > I read the two bugs (18539 and 18179) and the link given by Jonathan but > I still don't understand why the call in list context has been > forbidden. Why not simply return undef (an explicit undef) when no > records have be found ? It would work as expected in scalar and list > contexts. > > Here is a possible rewrite of 'find' to better explain what I mean: > > ??? sub find { > ??????? my ( $self, @pars ) = @_; > > ??????? my $object = undef; > > ??????? @pars = grep { defined } @pars; > ??????? if (@pars) { > ??????????? my $result = $self->_resultset()->find(@pars); > ??????????? if ($result) { > ??????????????? $object = $self->object_class()->_new_from_dbic($result); > ??????????? } > ??????? } > > ??????? return $object; > ??? } > > @a = Koha::Patrons->find('foo'); # would result in @a = (undef) > {a => K::P->find('foo'), b => 'bar'}; # would result in {a => undef, b > => 'bar'} > > Please tell me what you think. > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ -- Julian Maurice BibLibre From paul.poulain at biblibre.com Wed Dec 13 14:56:18 2017 From: paul.poulain at biblibre.com (Paul Poulain) Date: Wed, 13 Dec 2017 14:56:18 +0100 Subject: [Koha-devel] Koha and Elastic Search used in production ? Message-ID: <4737400f-0476-7c76-eca9-b79344abe3f8@biblibre.com> Hello all, Is there someone using Koha with ES in production ? bywater, PTFS-E, Catalyst-NZ, Theke, or any other support company, what's your plan ? BibLibre is planning to invest some effort to work on Koha-ES with UNIMARC in the next months, if there are things to share, we would be more than happy ! -- Paul Poulain, Associ?-g?rant / co-owner BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Open Source software and services for libraries From jonathan.druart at bugs.koha-community.org Wed Dec 13 14:58:38 2017 From: jonathan.druart at bugs.koha-community.org (Jonathan Druart) Date: Wed, 13 Dec 2017 13:58:38 +0000 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context In-Reply-To: References: Message-ID: Hi Julian, > @a = Koha::Patrons->find('foo'); # would result in @a = (undef) And that leads to issues: if ( @a ) { # = 1 say $a[0]->borrowernumber; # BOOM } See also https://perlmaven.com/how-to-return-undef-from-a-function (was it the link you were talking about?) Cheers, Jonathan On Wed, 13 Dec 2017 at 10:34 Julian Maurice wrote: > Hi developers, > > I stumbled upon a line of code recently and I can't figure out why it > has be done this way. I hope you can help me :) > > The line in question is in Koha::Objects::find: > > croak 'Cannot use "->find" in list context' if wantarray; > > I read the two bugs (18539 and 18179) and the link given by Jonathan but > I still don't understand why the call in list context has been > forbidden. Why not simply return undef (an explicit undef) when no > records have be found ? It would work as expected in scalar and list > contexts. > > Here is a possible rewrite of 'find' to better explain what I mean: > > sub find { > my ( $self, @pars ) = @_; > > my $object = undef; > > @pars = grep { defined } @pars; > if (@pars) { > my $result = $self->_resultset()->find(@pars); > if ($result) { > $object = $self->object_class()->_new_from_dbic($result); > } > } > > return $object; > } > > @a = Koha::Patrons->find('foo'); # would result in @a = (undef) > {a => K::P->find('foo'), b => 'bar'}; # would result in {a => undef, b > => 'bar'} > > Please tell me what you think. > > -- > Julian Maurice > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From julian.maurice at biblibre.com Wed Dec 13 15:07:11 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Wed, 13 Dec 2017 15:07:11 +0100 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context In-Reply-To: References: Message-ID: Ok, but the proposed fix doesn't fix this code: @a = scalar Koha::Patrons->find('foo'); if (@a) { # still equals to 1 say $a[0]->borrowernumber; # still BOOM } And yes, that was the link ;) Le 13/12/2017 ? 14:58, Jonathan Druart a ?crit?: > Hi Julian, > > >> @a = Koha::Patrons->find('foo'); # would result in @a = (undef) > > And that leads to issues: > if ( @a ) { # = 1 > ? say $a[0]->borrowernumber; # BOOM > } > > See also https://perlmaven.com/how-to-return-undef-from-a-function (was > it the link you were talking about?) > > Cheers, > Jonathan > > On Wed, 13 Dec 2017 at 10:34 Julian Maurice > wrote: > > Hi developers, > > I stumbled upon a line of code recently and I can't figure out why it > has be done this way. I hope you can help me :) > > The line in question is in Koha::Objects::find: > > ? ? croak 'Cannot use "->find" in list context' if wantarray; > > I read the two bugs (18539 and 18179) and the link given by Jonathan but > I still don't understand why the call in list context has been > forbidden. Why not simply return undef (an explicit undef) when no > records have be found ? It would work as expected in scalar and list > contexts. > > Here is a possible rewrite of 'find' to better explain what I mean: > > ? ? sub find { > ? ? ? ? my ( $self, @pars ) = @_; > > ? ? ? ? my $object = undef; > > ? ? ? ? @pars = grep { defined } @pars; > ? ? ? ? if (@pars) { > ? ? ? ? ? ? my $result = $self->_resultset()->find(@pars); > ? ? ? ? ? ? if ($result) { > ? ? ? ? ? ? ? ? $object = > $self->object_class()->_new_from_dbic($result); > ? ? ? ? ? ? } > ? ? ? ? } > > ? ? ? ? return $object; > ? ? } > > @a = Koha::Patrons->find('foo'); # would result in @a = (undef) > {a => K::P->find('foo'), b => 'bar'}; # would result in {a => undef, b > => 'bar'} > > Please tell me what you think. > > -- > Julian Maurice > > BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > > http://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/ > -- Julian Maurice BibLibre From julian.maurice at biblibre.com Wed Dec 13 15:56:35 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Wed, 13 Dec 2017 15:56:35 +0100 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context In-Reply-To: References: <57528b81-ae04-0584-7b93-64325f6285fd@biblibre.com> Message-ID: Probably, but that's not my point. I understand why the previous code needed to be fixed, which is to avoid that { a => Koha::Patrons->find("foo"), b => "bar" } would result in { a => "b", "bar" => undef } My question is: why the solution to this problem was to forbid calls in list context while we could simply return an explicit undef? It forces us to write 'scalar' in front of a call that should always return a single value, and in my opinion it's a "code smell" Le 13/12/2017 ? 15:29, Marcel de Rooy a ?crit?: > i forgot to add scalar in the second.. > > probably you should > > if( $a = xxx->find ) > > ?? push @b, $a > > > ------------------------------------------------------------------------ > *Van:* Julian Maurice > *Verzonden:* woensdag 13 december 2017 15:20:34 > *Aan:* Marcel de Rooy > *Onderwerp:* Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find > calls in list context > ? > This particular line will work (only the first, in the second, find is > still called in list context), but @a would contain one element (undef) > and the example code given by Jonathan will also fail, whether we call > find in list context or not. > > Le 13/12/2017 ? 15:12, Marcel de Rooy a ?crit?: >> Are you sure ? >> >> push @a, scalar Koha..->find >> >> or @a = ( ...->find ) >> >> >> should work imo >> >> ------------------------------------------------------------------------ >> *Van:* koha-devel-bounces at lists.koha-community.org >> namens Julian Maurice >> >> *Verzonden:* woensdag 13 december 2017 15:07:11 >> *Aan:* Jonathan Druart >> *CC:* koha-devel at lists.koha-community.org >> *Onderwerp:* Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find >> calls in list context >> ? >> Ok, but the proposed fix doesn't fix this code: >> >> @a = scalar Koha::Patrons->find('foo'); >> if (@a) { # still equals to 1 >> ? say $a[0]->borrowernumber; # still BOOM >> } >> >> And yes, that was the link ;) >> >> Le 13/12/2017 ? 14:58, Jonathan Druart a ?crit?: >>> Hi Julian, >>> >>> >>>> @a = Koha::Patrons->find('foo'); # would result in @a = (undef) >>> >>> And that leads to issues: >>> if ( @a ) { # = 1 >>> ? say $a[0]->borrowernumber; # BOOM >>> } >>> >>> See also https://perlmaven.com/how-to-return-undef-from-a-function (was >>> it the link you were talking about?) >>> >>> Cheers, >>> Jonathan >>> >>> On Wed, 13 Dec 2017 at 10:34 Julian Maurice >> > wrote: >>> >>>???? Hi developers, >>> >>>???? I stumbled upon a line of code recently and I can't figure out why it >>>???? has be done this way. I hope you can help me :) >>> >>>???? The line in question is in Koha::Objects::find: >>> >>>???? ? ? croak 'Cannot use "->find" in list context' if wantarray; >>> >>>???? I read the two bugs (18539 and 18179) and the link given by Jonathan but >>>???? I still don't understand why the call in list context has been >>>???? forbidden. Why not simply return undef (an explicit undef) when no >>>???? records have be found ? It would work as expected in scalar and list >>>???? contexts. >>> >>>???? Here is a possible rewrite of 'find' to better explain what I mean: >>> >>>???? ? ? sub find { >>>???? ? ? ? ? my ( $self, @pars ) = @_; >>> >>>???? ? ? ? ? my $object = undef; >>> >>>???? ? ? ? ? @pars = grep { defined } @pars; >>>???? ? ? ? ? if (@pars) { >>>???? ? ? ? ? ? ? my $result = $self->_resultset()->find(@pars); >>>???? ? ? ? ? ? ? if ($result) { >>>???? ? ? ? ? ? ? ? ? $object = >>>???? $self->object_class()->_new_from_dbic($result); >>>???? ? ? ? ? ? ? } >>>???? ? ? ? ? } >>> >>>???? ? ? ? ? return $object; >>>???? ? ? } >>> >>>???? @a = Koha::Patrons->find('foo'); # would result in @a = (undef) >>>???? {a => K::P->find('foo'), b => 'bar'}; # would result in {a => undef, b >>>???? => 'bar'} >>> >>>???? Please tell me what you think. >>> >>>???? -- >>>???? Julian Maurice >>???? > >>>???? BibLibre >>>???? _______________________________________________ >>>???? Koha-devel mailing list >>>???? Koha-devel at lists.koha-community.org >>>???? >>>???? http://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/ >>> >> >> -- >> Julian Maurice >> BibLibre >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://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/ > > -- > Julian Maurice > BibLibre -- Julian Maurice BibLibre From oha at oha.it Wed Dec 13 16:08:11 2017 From: oha at oha.it (Francesco Rivetti) Date: Wed, 13 Dec 2017 16:08:11 +0100 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context In-Reply-To: References: <57528b81-ae04-0584-7b93-64325f6285fd@biblibre.com> Message-ID: On 13. des. 2017 15:56, Julian Maurice wrote: > My question is: why the solution to this problem was to forbid calls in > list context while we could simply return an explicit undef? > It forces us to write 'scalar' in front of a call that should always > return a single value, and in my opinion it's a "code smell" I completely agree with this. Francesco From oleonard at myacpl.org Wed Dec 13 18:06:03 2017 From: oleonard at myacpl.org (Owen Leonard) Date: Wed, 13 Dec 2017 12:06:03 -0500 Subject: [Koha-devel] Add a digest option for AUTO_RENEWALS Notice Message-ID: Is anyone currently working on, or have plans to work on Bug 19736, "Add a digest option for AUTO_RENEWALS Notice?" https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19736 -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From dcook at prosentient.com.au Thu Dec 14 00:51:30 2017 From: dcook at prosentient.com.au (David Cook) Date: Thu, 14 Dec 2017 10:51:30 +1100 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context In-Reply-To: References: <57528b81-ae04-0584-7b93-64325f6285fd@biblibre.com> Message-ID: <004c01d3746d$4c8eca80$e5ac5f80$@prosentient.com.au> Alternatively, you could write: my $foo = Koha::Patrons->find("foo"); my $hashref = { a => $foo, b => "bar" }; or my $foo = Koha::Patrons->find("foo"); my $hashref = { b => "bar" }; $hashref->{a} = $foo if $foo; Personally, I'm not a fan of putting function calls in data structures. 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-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Julian Maurice Sent: Thursday, 14 December 2017 1:57 AM To: Marcel de Rooy Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context Probably, but that's not my point. I understand why the previous code needed to be fixed, which is to avoid that { a => Koha::Patrons->find("foo"), b => "bar" } would result in { a => "b", "bar" => undef } My question is: why the solution to this problem was to forbid calls in list context while we could simply return an explicit undef? It forces us to write 'scalar' in front of a call that should always return a single value, and in my opinion it's a "code smell" Le 13/12/2017 ? 15:29, Marcel de Rooy a ?crit?: > i forgot to add scalar in the second.. > > probably you should > > if( $a = xxx->find ) > > ?? push @b, $a > > > ---------------------------------------------------------------------- > -- > *Van:* Julian Maurice > *Verzonden:* woensdag 13 december 2017 15:20:34 > *Aan:* Marcel de Rooy > *Onderwerp:* Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find > calls in list context > ? > This particular line will work (only the first, in the second, find is > still called in list context), but @a would contain one element > (undef) and the example code given by Jonathan will also fail, whether > we call find in list context or not. > > Le 13/12/2017 ? 15:12, Marcel de Rooy a ?crit?: >> Are you sure ? >> >> push @a, scalar Koha..->find >> >> or @a = ( ...->find ) >> >> >> should work imo >> >> --------------------------------------------------------------------- >> --- >> *Van:* koha-devel-bounces at lists.koha-community.org >> namens Julian Maurice >> >> *Verzonden:* woensdag 13 december 2017 15:07:11 >> *Aan:* Jonathan Druart >> *CC:* koha-devel at lists.koha-community.org >> *Onderwerp:* Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find >> calls in list context >> ? >> Ok, but the proposed fix doesn't fix this code: >> >> @a = scalar Koha::Patrons->find('foo'); if (@a) { # still equals to 1 >> ? say $a[0]->borrowernumber; # still BOOM } >> >> And yes, that was the link ;) >> >> Le 13/12/2017 ? 14:58, Jonathan Druart a ?crit?: >>> Hi Julian, >>> >>> >>>> @a = Koha::Patrons->find('foo'); # would result in @a = (undef) >>> >>> And that leads to issues: >>> if ( @a ) { # = 1 >>> ? say $a[0]->borrowernumber; # BOOM >>> } >>> >>> See also https://perlmaven.com/how-to-return-undef-from-a-function >>> (was it the link you were talking about?) >>> >>> Cheers, >>> Jonathan >>> >>> On Wed, 13 Dec 2017 at 10:34 Julian Maurice >>> > wrote: >>> >>>???? Hi developers, >>> >>>???? I stumbled upon a line of code recently and I can't figure out >>>why it >>>???? has be done this way. I hope you can help me :) >>> >>>???? The line in question is in Koha::Objects::find: >>> >>>???? ? ? croak 'Cannot use "->find" in list context' if wantarray; >>> >>>???? I read the two bugs (18539 and 18179) and the link given by >>>Jonathan but >>>???? I still don't understand why the call in list context has been >>>???? forbidden. Why not simply return undef (an explicit undef) when >>>no >>>???? records have be found ? It would work as expected in scalar and >>>list >>>???? contexts. >>> >>>???? Here is a possible rewrite of 'find' to better explain what I mean: >>> >>>???? ? ? sub find { >>>???? ? ? ? ? my ( $self, @pars ) = @_; >>> >>>???? ? ? ? ? my $object = undef; >>> >>>???? ? ? ? ? @pars = grep { defined } @pars; >>>???? ? ? ? ? if (@pars) { >>>???? ? ? ? ? ? ? my $result = $self->_resultset()->find(@pars); >>>???? ? ? ? ? ? ? if ($result) { >>>???? ? ? ? ? ? ? ? ? $object = >>>???? $self->object_class()->_new_from_dbic($result); >>>???? ? ? ? ? ? ? } >>>???? ? ? ? ? } >>> >>>???? ? ? ? ? return $object; >>>???? ? ? } >>> >>>???? @a = Koha::Patrons->find('foo'); # would result in @a = (undef) >>>???? {a => K::P->find('foo'), b => 'bar'}; # would result in {a => >>>undef, b >>>???? => 'bar'} >>> >>>???? Please tell me what you think. >>> >>>???? -- >>>???? Julian Maurice >>???? > >>>???? BibLibre >>>???? _______________________________________________ >>>???? Koha-devel mailing list >>>???? Koha-devel at lists.koha-community.org >>>???? >>>???? >>>http://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/ >>> >> >> -- >> Julian Maurice BibLibre >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://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/ > > -- > Julian Maurice BibLibre -- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel at lists.koha-community.org http://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/ From kohanews at gmail.com Thu Dec 14 02:44:29 2017 From: kohanews at gmail.com (kohanews) Date: Wed, 13 Dec 2017 17:44:29 -0800 Subject: [Koha-devel] Call for News: December 2017 Newsletter Message-ID: <2af4f394-920b-fe93-8104-1323b10da7b9@gmail.com> I'm collecting news for the December newsletter. Send anything noteworthy to: k o h a news AT gmail dot com News criteria: --------------------------- ** For events **: ?? - Please include dates for past events. If I can't find dates I may not add it. ?? - Announcements for future events with dates T.B.A. are fine ...Eg., Kohacon ?? - For past events , **** one month back is the cut-off? ****. * News items can be of any length. * Images are fine * Anything and everything Koha. * Submit by the 26th of the month. If you are working on an interesting project or development related to Koha, please let me know and I'll include it in the development section. Thank you! -- Chad Roseburg Editor, Koha Community Newsletter From julian.maurice at biblibre.com Thu Dec 14 09:25:49 2017 From: julian.maurice at biblibre.com (Julian Maurice) Date: Thu, 14 Dec 2017 09:25:49 +0100 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context In-Reply-To: <004c01d3746d$4c8eca80$e5ac5f80$@prosentient.com.au> References: <57528b81-ae04-0584-7b93-64325f6285fd@biblibre.com> <004c01d3746d$4c8eca80$e5ac5f80$@prosentient.com.au> Message-ID: Of course we could, but why fix the calls when we can fix the subroutine itself ? I filed a bug report : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19809 Le 14/12/2017 ? 00:51, David Cook a ?crit?: > Alternatively, you could write: > > my $foo = Koha::Patrons->find("foo"); > my $hashref = { a => $foo, b => "bar" }; > > or > my $foo = Koha::Patrons->find("foo"); > my $hashref = { b => "bar" }; > $hashref->{a} = $foo if $foo; > > Personally, I'm not a fan of putting function calls in data structures. > > 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-bounces at lists.koha-community.org > [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Julian > Maurice > Sent: Thursday, 14 December 2017 1:57 AM > To: Marcel de Rooy > Cc: koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in > list context > > Probably, but that's not my point. > > I understand why the previous code needed to be fixed, which is to avoid > that > > { a => Koha::Patrons->find("foo"), b => "bar" } > > would result in { a => "b", "bar" => undef } > > My question is: why the solution to this problem was to forbid calls in list > context while we could simply return an explicit undef? > It forces us to write 'scalar' in front of a call that should always return > a single value, and in my opinion it's a "code smell" > > Le 13/12/2017 ? 15:29, Marcel de Rooy a ?crit?: >> i forgot to add scalar in the second.. >> >> probably you should >> >> if( $a = xxx->find ) >> >> ?? push @b, $a >> >> >> ---------------------------------------------------------------------- >> -- >> *Van:* Julian Maurice >> *Verzonden:* woensdag 13 december 2017 15:20:34 >> *Aan:* Marcel de Rooy >> *Onderwerp:* Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find >> calls in list context >> ? >> This particular line will work (only the first, in the second, find is >> still called in list context), but @a would contain one element >> (undef) and the example code given by Jonathan will also fail, whether >> we call find in list context or not. >> >> Le 13/12/2017 ? 15:12, Marcel de Rooy a ?crit?: >>> Are you sure ? >>> >>> push @a, scalar Koha..->find >>> >>> or @a = ( ...->find ) >>> >>> >>> should work imo >>> >>> --------------------------------------------------------------------- >>> --- >>> *Van:* koha-devel-bounces at lists.koha-community.org >>> namens Julian Maurice >>> >>> *Verzonden:* woensdag 13 december 2017 15:07:11 >>> *Aan:* Jonathan Druart >>> *CC:* koha-devel at lists.koha-community.org >>> *Onderwerp:* Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find >>> calls in list context >>> ? >>> Ok, but the proposed fix doesn't fix this code: >>> >>> @a = scalar Koha::Patrons->find('foo'); if (@a) { # still equals to 1 >>> ? say $a[0]->borrowernumber; # still BOOM } >>> >>> And yes, that was the link ;) >>> >>> Le 13/12/2017 ? 14:58, Jonathan Druart a ?crit?: >>>> Hi Julian, >>>> >>>> >>>>> @a = Koha::Patrons->find('foo'); # would result in @a = (undef) >>>> >>>> And that leads to issues: >>>> if ( @a ) { # = 1 >>>> ? say $a[0]->borrowernumber; # BOOM >>>> } >>>> >>>> See also https://perlmaven.com/how-to-return-undef-from-a-function >>>> (was it the link you were talking about?) >>>> >>>> Cheers, >>>> Jonathan >>>> >>>> On Wed, 13 Dec 2017 at 10:34 Julian Maurice >>>> > > wrote: >>>> >>>> ???? Hi developers, >>>> >>>> ???? I stumbled upon a line of code recently and I can't figure out >>>> why it >>>> ???? has be done this way. I hope you can help me :) >>>> >>>> ???? The line in question is in Koha::Objects::find: >>>> >>>> ???? ? ? croak 'Cannot use "->find" in list context' if wantarray; >>>> >>>> ???? I read the two bugs (18539 and 18179) and the link given by >>>> Jonathan but >>>> ???? I still don't understand why the call in list context has been >>>> ???? forbidden. Why not simply return undef (an explicit undef) when >>>> no >>>> ???? records have be found ? It would work as expected in scalar and >>>> list >>>> ???? contexts. >>>> >>>> ???? Here is a possible rewrite of 'find' to better explain what I mean: >>>> >>>> ???? ? ? sub find { >>>> ???? ? ? ? ? my ( $self, @pars ) = @_; >>>> >>>> ???? ? ? ? ? my $object = undef; >>>> >>>> ???? ? ? ? ? @pars = grep { defined } @pars; >>>> ???? ? ? ? ? if (@pars) { >>>> ???? ? ? ? ? ? ? my $result = $self->_resultset()->find(@pars); >>>> ???? ? ? ? ? ? ? if ($result) { >>>> ???? ? ? ? ? ? ? ? ? $object = >>>> ???? $self->object_class()->_new_from_dbic($result); >>>> ???? ? ? ? ? ? ? } >>>> ???? ? ? ? ? } >>>> >>>> ???? ? ? ? ? return $object; >>>> ???? ? ? } >>>> >>>> ???? @a = Koha::Patrons->find('foo'); # would result in @a = (undef) >>>> ???? {a => K::P->find('foo'), b => 'bar'}; # would result in {a => >>>> undef, b >>>> ???? => 'bar'} >>>> >>>> ???? Please tell me what you think. >>>> >>>> ???? -- >>>> ???? Julian Maurice >>> ???? > >>>> ???? BibLibre >>>> ???? _______________________________________________ >>>> ???? Koha-devel mailing list >>>> ???? Koha-devel at lists.koha-community.org >>>> ???? >>>> ???? >>>> http://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/ >>>> >>> >>> -- >>> Julian Maurice BibLibre >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> http://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/ >> >> -- >> Julian Maurice BibLibre > > -- > Julian Maurice BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > > -- Julian Maurice BibLibre From nick at bywatersolutions.com Thu Dec 14 15:32:11 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Thu, 14 Dec 2017 14:32:11 +0000 Subject: [Koha-devel] Reminder string freeze for stable December 15th Message-ID: Hi All, I mentioned at the meetings yesterday but just sending a reminder not here. Pushing patches today and catching up now, string freeze tomorrow. -Nick (kidclamp) -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Thu Dec 14 16:28:07 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 14 Dec 2017 15:28:07 +0000 Subject: [Koha-devel] REST api RFCs Message-ID: Hi everyone. Following yesterday's dev meeting (I'm sorry I couldn't attend) it was clear there should be some votes on the changes that we belive need to be made. In order to organize the documentation on this decision making process, and have something more precise to vote on, I've put together a front wiki page: https://wiki.koha-community.org/wiki/REST_api_RFCs in which all endpoint-specific RFCs can be found. I have added the endpoints I've been, am and will be working on. Also endpoints I know Biblibre is working on. As the discussion was about the patrons endpoint specifically, I started by creating an RFC for it: https://wiki.koha-community.org/wiki/Patrons_endpoint_RFC It is organized in two sections: actions and paths, and the object definition. The idea is that you can add your own column (put your name on it) with your personal proposal. Discussions can happen in other places like IRC or koha-devel. Please add your comments on each issue you think it is worth, and please contact me if you have any doubts or want to discuss specific stuffs. I will be spending the next days polishing this RFC and moving into the rest of them in the same way. Before adding new endpoints to that list, I would suggest we have a small conversation here in koha-devel to avoid polluting the front page with several variations of the same endpoints. This is just a suggestion, though. Thanks for your interest and feedback! Cheers -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Thu Dec 14 17:17:37 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 14 Dec 2017 16:17:37 +0000 Subject: [Koha-devel] REST api RFCs In-Reply-To: References: Message-ID: On the dev meeting it was mentioned that version number should be shifted with this changes. I don't think we should do that right now (we only have 3 endpoints!, this is not yet an API) Anyway, looking forward to your comments! El jue., 14 dic. 2017 a las 12:28, Tomas Cohen Arazi () escribi?: > Hi everyone. Following yesterday's dev meeting (I'm sorry I couldn't > attend) it was clear there should be some votes on the changes that we > belive need to be made. > > In order to organize the documentation on this decision making process, > and have something more precise to vote on, I've put together a front wiki > page: > > https://wiki.koha-community.org/wiki/REST_api_RFCs > > in which all endpoint-specific RFCs can be found. I have added the > endpoints I've been, am and will be working on. Also endpoints I know > Biblibre is working on. > > As the discussion was about the patrons endpoint specifically, I started > by creating an RFC for it: > > https://wiki.koha-community.org/wiki/Patrons_endpoint_RFC > > It is organized in two sections: actions and paths, and the object > definition. The idea is that you can add your own column (put your name on > it) with your personal proposal. Discussions can happen in other places > like IRC or koha-devel. > > Please add your comments on each issue you think it is worth, and please > contact me if you have any doubts or want to discuss specific stuffs. > > I will be spending the next days polishing this RFC and moving into the > rest of them in the same way. > > Before adding new endpoints to that list, I would suggest we have a small > conversation here in koha-devel to avoid polluting the front page with > several variations of the same endpoints. This is just a suggestion, though. > > Thanks for your interest and feedback! > Cheers > > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at bywatersolutions.com Thu Dec 14 22:52:45 2017 From: info at bywatersolutions.com (Brendan Gallagher) Date: Thu, 14 Dec 2017 13:52:45 -0800 Subject: [Koha-devel] Koha and Elastic Search used in production ? In-Reply-To: <4737400f-0476-7c76-eca9-b79344abe3f8@biblibre.com> References: <4737400f-0476-7c76-eca9-b79344abe3f8@biblibre.com> Message-ID: Our plan is that Nick is working on getting ES as stable as possible. He has invested many days in the past months and will continue to have different days to work on ES in the coming months. There are a number of ES bugs out there that needs testing and sign off. Our goal is that by 18.05 this will be a viable option for use in production. If you have further questions please don't hesitate to ask Nick. -Brendan On Wed, Dec 13, 2017 at 5:56 AM, Paul Poulain wrote: > Hello all, > > Is there someone using Koha with ES in production ? > > bywater, PTFS-E, Catalyst-NZ, Theke, or any other support company, what's > your plan ? > > BibLibre is planning to invest some effort to work on Koha-ES with UNIMARC > in the next months, if there are things to share, we would be more than > happy ! > > -- > 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 at lists.koha-community.org > http://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/ -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Office: Portland, OR - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info at bywatersolutions.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From dcook at prosentient.com.au Fri Dec 15 00:24:45 2017 From: dcook at prosentient.com.au (David Cook) Date: Fri, 15 Dec 2017 10:24:45 +1100 Subject: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context In-Reply-To: References: <57528b81-ae04-0584-7b93-64325f6285fd@biblibre.com> <004c01d3746d$4c8eca80$e5ac5f80$@prosentient.com.au> Message-ID: <00c101d37532$ba0523f0$2e0f6bd0$@prosentient.com.au> Fixing the calls would make the behaviour of the function more explicit and less prone to human error. But... I think fixing the function itself is fair enough. If we look at DBIx::Class::ResultSet, it looks like it returns a scalar or undef: http://search.cpan.org/dist/DBIx-Class/lib/DBIx/Class/ResultSet.pm#find. Makes sense if Koha::Objects does the same thing. 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: Julian Maurice [mailto:julian.maurice at biblibre.com] Sent: Thursday, 14 December 2017 7:26 PM To: David Cook ; 'Marcel de Rooy' Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls in list context Of course we could, but why fix the calls when we can fix the subroutine itself ? I filed a bug report : https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19809 Le 14/12/2017 ? 00:51, David Cook a ?crit : > Alternatively, you could write: > > my $foo = Koha::Patrons->find("foo"); > my $hashref = { a => $foo, b => "bar" }; > > or > my $foo = Koha::Patrons->find("foo"); > my $hashref = { b => "bar" }; > $hashref->{a} = $foo if $foo; > > Personally, I'm not a fan of putting function calls in data structures. > > 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-bounces at lists.koha-community.org > [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of > Julian Maurice > Sent: Thursday, 14 December 2017 1:57 AM > To: Marcel de Rooy > Cc: koha-devel at lists.koha-community.org > Subject: Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find calls > in list context > > Probably, but that's not my point. > > I understand why the previous code needed to be fixed, which is to > avoid that > > { a => Koha::Patrons->find("foo"), b => "bar" } > > would result in { a => "b", "bar" => undef } > > My question is: why the solution to this problem was to forbid calls > in list context while we could simply return an explicit undef? > It forces us to write 'scalar' in front of a call that should always > return a single value, and in my opinion it's a "code smell" > > Le 13/12/2017 ? 15:29, Marcel de Rooy a ?crit : >> i forgot to add scalar in the second.. >> >> probably you should >> >> if( $a = xxx->find ) >> >> push @b, $a >> >> >> --------------------------------------------------------------------- >> - >> -- >> *Van:* Julian Maurice >> *Verzonden:* woensdag 13 december 2017 15:20:34 >> *Aan:* Marcel de Rooy >> *Onderwerp:* Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find >> calls in list context >> >> This particular line will work (only the first, in the second, find >> is still called in list context), but @a would contain one element >> (undef) and the example code given by Jonathan will also fail, >> whether we call find in list context or not. >> >> Le 13/12/2017 ? 15:12, Marcel de Rooy a ?crit : >>> Are you sure ? >>> >>> push @a, scalar Koha..->find >>> >>> or @a = ( ...->find ) >>> >>> >>> should work imo >>> >>> -------------------------------------------------------------------- >>> - >>> --- >>> *Van:* koha-devel-bounces at lists.koha-community.org >>> namens Julian Maurice >>> >>> *Verzonden:* woensdag 13 december 2017 15:07:11 >>> *Aan:* Jonathan Druart >>> *CC:* koha-devel at lists.koha-community.org >>> *Onderwerp:* Re: [Koha-devel] Bug 18539 - Forbid Koha::Objects->find >>> calls in list context >>> >>> Ok, but the proposed fix doesn't fix this code: >>> >>> @a = scalar Koha::Patrons->find('foo'); if (@a) { # still equals to >>> 1 >>> say $a[0]->borrowernumber; # still BOOM } >>> >>> And yes, that was the link ;) >>> >>> Le 13/12/2017 ? 14:58, Jonathan Druart a ?crit : >>>> Hi Julian, >>>> >>>> >>>>> @a = Koha::Patrons->find('foo'); # would result in @a = (undef) >>>> >>>> And that leads to issues: >>>> if ( @a ) { # = 1 >>>> say $a[0]->borrowernumber; # BOOM } >>>> >>>> See also https://perlmaven.com/how-to-return-undef-from-a-function >>>> (was it the link you were talking about?) >>>> >>>> Cheers, >>>> Jonathan >>>> >>>> On Wed, 13 Dec 2017 at 10:34 Julian Maurice >>>> > > wrote: >>>> >>>> Hi developers, >>>> >>>> I stumbled upon a line of code recently and I can't figure out >>>> why it >>>> has be done this way. I hope you can help me :) >>>> >>>> The line in question is in Koha::Objects::find: >>>> >>>> croak 'Cannot use "->find" in list context' if wantarray; >>>> >>>> I read the two bugs (18539 and 18179) and the link given by >>>> Jonathan but >>>> I still don't understand why the call in list context has been >>>> forbidden. Why not simply return undef (an explicit undef) >>>> when no >>>> records have be found ? It would work as expected in scalar >>>> and list >>>> contexts. >>>> >>>> Here is a possible rewrite of 'find' to better explain what I mean: >>>> >>>> sub find { >>>> my ( $self, @pars ) = @_; >>>> >>>> my $object = undef; >>>> >>>> @pars = grep { defined } @pars; >>>> if (@pars) { >>>> my $result = $self->_resultset()->find(@pars); >>>> if ($result) { >>>> $object = >>>> $self->object_class()->_new_from_dbic($result); >>>> } >>>> } >>>> >>>> return $object; >>>> } >>>> >>>> @a = Koha::Patrons->find('foo'); # would result in @a = >>>> (undef) >>>> {a => K::P->find('foo'), b => 'bar'}; # would result in {a => >>>> undef, b >>>> => 'bar'} >>>> >>>> Please tell me what you think. >>>> >>>> -- >>>> Julian Maurice >>> > >>>> BibLibre >>>> _______________________________________________ >>>> Koha-devel mailing list >>>> Koha-devel at lists.koha-community.org >>>> >>>> >>>> http://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/ >>>> >>> >>> -- >>> Julian Maurice BibLibre >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> http://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/ >> >> -- >> Julian Maurice BibLibre > > -- > Julian Maurice BibLibre > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > > -- Julian Maurice BibLibre From andreas.hedstrom.mace at su.se Fri Dec 15 09:44:25 2017 From: andreas.hedstrom.mace at su.se (=?utf-8?B?QW5kcmVhcyBIZWRzdHLDtm0gTWFjZQ==?=) Date: Fri, 15 Dec 2017 08:44:25 +0000 Subject: [Koha-devel] REST api RFCs In-Reply-To: References: Message-ID: Hi! This sounds like a really good initiative Tom?s, getting the major endpoints listed and structured so that the REST API work can proceed! However, I?m surprised that the endpoint for accountlines is not listed in the RFC. Some reasons why I think that this should be included: We at Stockholm University Library is already using (a previous) version of this endpoint in production You mentioned that you included other endpoints BibLibre is working on: we sponsored BibLibre to build this endpoint a while back But above all I believe other libraries will also be interested in using this endpoint! (At the hackfest in Lund recently, there was interest in using this endpoint from Oslo Public Library etc.) Best regards, Andreas Hedstr?m Mace Fr?n: p? uppdrag av Tomas Cohen Arazi Datum: torsdag 14 december 2017 16:28 Till: koha-devel ?mne: [Koha-devel] REST api RFCs Hi everyone. Following yesterday's dev meeting (I'm sorry I couldn't attend) it was clear there should be some votes on the changes that we belive need to be made. In order to organize the documentation on this decision making process, and have something more precise to vote on, I've put together a front wiki page: https://wiki.koha-community.org/wiki/REST_api_RFCs in which all endpoint-specific RFCs can be found. I have added the endpoints I've been, am and will be working on. Also endpoints I know Biblibre is working on. As the discussion was about the patrons endpoint specifically, I started by creating an RFC for it: https://wiki.koha-community.org/wiki/Patrons_endpoint_RFC It is organized in two sections: actions and paths, and the object definition. The idea is that you can add your own column (put your name on it) with your personal proposal. Discussions can happen in other places like IRC or koha-devel. Please add your comments on each issue you think it is worth, and please contact me if you have any doubts or want to discuss specific stuffs. I will be spending the next days polishing this RFC and moving into the rest of them in the same way. Before adding new endpoints to that list, I would suggest we have a small conversation here in koha-devel to avoid polluting the front page with several variations of the same endpoints. This is just a suggestion, though. Thanks for your interest and feedback! Cheers -- Tom?s Cohen Arazi Theke Solutions (https://theke.io) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Fri Dec 15 11:15:10 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Fri, 15 Dec 2017 10:15:10 +0000 Subject: [Koha-devel] REST api RFCs In-Reply-To: References: Message-ID: Andreas, it will be included! That list is only what I managed to write after the dev meeting, and is certainly incomplete. El vie., 15 de dic. de 2017 5:44 a. m., Andreas Hedstr?m Mace < andreas.hedstrom.mace at su.se> escribi?: > Hi! > > > > This sounds like a really good initiative Tom?s, getting the major > endpoints listed and structured so that the REST API work can proceed! > > > > However, I?m surprised that the endpoint for accountlines is not listed in > the RFC. Some reasons why I think that this should be included: > > > > We at Stockholm University Library is already using (a previous) version > of this endpoint in production > > You mentioned that you included other endpoints BibLibre is working on: we > sponsored BibLibre to build this endpoint a while back > > But above all I believe other libraries will also be interested in using > this endpoint! (At the hackfest in Lund recently, there was interest in > using this endpoint from Oslo Public Library etc.) > > > > Best regards, > > Andreas Hedstr?m Mace > > > > > > *Fr?n: * p? uppdrag av Tomas > Cohen Arazi > *Datum: *torsdag 14 december 2017 16:28 > *Till: *koha-devel > *?mne: *[Koha-devel] REST api RFCs > > > > Hi everyone. Following yesterday's dev meeting (I'm sorry I couldn't > attend) it was clear there should be some votes on the changes that we > belive need to be made. > > > > In order to organize the documentation on this decision making process, > and have something more precise to vote on, I've put together a front wiki > page: > > > > https://wiki.koha-community.org/wiki/REST_api_RFCs > > > > in which all endpoint-specific RFCs can be found. I have added the > endpoints I've been, am and will be working on. Also endpoints I know > Biblibre is working on. > > > > As the discussion was about the patrons endpoint specifically, I started > by creating an RFC for it: > > > > https://wiki.koha-community.org/wiki/Patrons_endpoint_RFC > > > > It is organized in two sections: actions and paths, and the object > definition. The idea is that you can add your own column (put your name on > it) with your personal proposal. Discussions can happen in other places > like IRC or koha-devel. > > > > Please add your comments on each issue you think it is worth, and please > contact me if you have any doubts or want to discuss specific stuffs. > > > > I will be spending the next days polishing this RFC and moving into the > rest of them in the same way. > > > > Before adding new endpoints to that list, I would suggest we have a small > conversation here in koha-devel to avoid polluting the front page with > several variations of the same endpoints. This is just a suggestion, though. > > > > Thanks for your interest and feedback! > > Cheers > > > > -- > > Tom?s Cohen Arazi > > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 > GPG: B2F3C15F > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolin.somers at biblibre.com Fri Dec 15 12:32:07 2017 From: fridolin.somers at biblibre.com (Fridolin SOMERS) Date: Fri, 15 Dec 2017 12:32:07 +0100 Subject: [Koha-devel] Starman workers reload via signal Message-ID: <822a02f4-eb2b-5a07-6bc6-cfd40874f711@biblibre.com> Hi, We recently found some interesting Starman feature. Since it is a master/workers software there is, like in Apache, a way to "gracefully" rebuild the workers without stopping master : kill -HUP 123 (123 being the master PID). Unlike stop/start of starman, the used workers will not be stopped until there task is done. During that idle workers will indeed be killed and rebuild. This is useful when one wants to refresh Plack persistence on a production running server. See : https://metacpan.org/pod/distribution/Starman/script/starman#SIGNALS We used this in our systemd service for starman : ExecReload=/bin/kill -HUP ${MAINPID} This may be usefull in koha-plack. Regards, -- Fridolin SOMERS BibLibre - software and system maintainer From nick at bywatersolutions.com Fri Dec 15 15:16:07 2017 From: nick at bywatersolutions.com (Nick Clemens) Date: Fri, 15 Dec 2017 14:16:07 +0000 Subject: [Koha-devel] MySQL 5.7 issues and Database Config Message-ID: HI All, At the last meeting it came up that the latest versions of MariaDB are enforcing sql strict mode: https://mariadb.com/kb/en/library/sql-mode/ This page on the wiki will need to be updated with the configuration tweaks needed for allowing koha to work: https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Ubuntu_16.04_and_MySQL_5.7 We should also focus on solving the issues here: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17258 If someone with the correct knowledge can update the wiki it would be appreciated. At the meeting folks were interested in helping anyone who can provide patches to work towards compatibility. Let us know if you can, what help you need, and let get this moving :-) -Nick (kidclamp) -------------- next part -------------- An HTML attachment was scrubbed... URL: From victor.grousset at biblibre.com Fri Dec 15 17:08:14 2017 From: victor.grousset at biblibre.com (Victor Grousset) Date: Fri, 15 Dec 2017 17:08:14 +0100 Subject: [Koha-devel] Recent TLS vulnerability (AKA ROBOT) Message-ID: <09d5e606-5ffe-dabe-76c0-9194a4a1ee2d@biblibre.com> Hi, Here is a quick and dirty summary of what I have found: https://framagit.org/snippets/1131 Has anyone found something contradictory or complementary? Cheers, -- Victor Grousset, dev support/maintenance BibLibre, Services en logiciels libres pour les biblioth?ques BibLibre, Libre/Open Source software and services for libraries From barton at bywatersolutions.com Fri Dec 15 20:49:25 2017 From: barton at bywatersolutions.com (Barton Chittenden) Date: Fri, 15 Dec 2017 14:49:25 -0500 Subject: [Koha-devel] REST api RFCs In-Reply-To: References: Message-ID: Tomas, Thank you for putting the REST api RFCs page together; having a series of pages that document the routes was sorely needed. One question -- the RFCs lists the route for borrowers as '/patrons'. However https://wiki.koha-community.org/wiki/Coding_ Guidelines_-_API#SWAGGER1.2:_Resource_names suggests that we should use /users instead of /borrowers, /patrons, or /members. Should we change the RFC to follow the Coding Guidelines, or change the guidelines? On Fri, Dec 15, 2017 at 5:15 AM, Tomas Cohen Arazi wrote: > Andreas, it will be included! That list is only what I managed to write > after the dev meeting, and is certainly incomplete. > > El vie., 15 de dic. de 2017 5:44 a. m., Andreas Hedstr?m Mace < > andreas.hedstrom.mace at su.se> escribi?: > >> Hi! >> >> >> >> This sounds like a really good initiative Tom?s, getting the major >> endpoints listed and structured so that the REST API work can proceed! >> >> >> >> However, I?m surprised that the endpoint for accountlines is not listed >> in the RFC. Some reasons why I think that this should be included: >> >> >> >> We at Stockholm University Library is already using (a previous) version >> of this endpoint in production >> >> You mentioned that you included other endpoints BibLibre is working on: >> we sponsored BibLibre to build this endpoint a while back >> >> But above all I believe other libraries will also be interested in using >> this endpoint! (At the hackfest in Lund recently, there was interest in >> using this endpoint from Oslo Public Library etc.) >> >> >> >> Best regards, >> >> Andreas Hedstr?m Mace >> >> >> >> >> >> *Fr?n: * p? uppdrag av >> Tomas Cohen Arazi >> *Datum: *torsdag 14 december 2017 16:28 >> *Till: *koha-devel >> *?mne: *[Koha-devel] REST api RFCs >> >> >> >> Hi everyone. Following yesterday's dev meeting (I'm sorry I couldn't >> attend) it was clear there should be some votes on the changes that we >> belive need to be made. >> >> >> >> In order to organize the documentation on this decision making process, >> and have something more precise to vote on, I've put together a front wiki >> page: >> >> >> >> https://wiki.koha-community.org/wiki/REST_api_RFCs >> >> >> >> in which all endpoint-specific RFCs can be found. I have added the >> endpoints I've been, am and will be working on. Also endpoints I know >> Biblibre is working on. >> >> >> >> As the discussion was about the patrons endpoint specifically, I started >> by creating an RFC for it: >> >> >> >> https://wiki.koha-community.org/wiki/Patrons_endpoint_RFC >> >> >> >> It is organized in two sections: actions and paths, and the object >> definition. The idea is that you can add your own column (put your name on >> it) with your personal proposal. Discussions can happen in other places >> like IRC or koha-devel. >> >> >> >> Please add your comments on each issue you think it is worth, and please >> contact me if you have any doubts or want to discuss specific stuffs. >> >> >> >> I will be spending the next days polishing this RFC and moving into the >> rest of them in the same way. >> >> >> >> Before adding new endpoints to that list, I would suggest we have a small >> conversation here in koha-devel to avoid polluting the front page with >> several variations of the same endpoints. This is just a suggestion, though. >> >> >> >> Thanks for your interest and feedback! >> >> Cheers >> >> >> >> -- >> >> Tom?s Cohen Arazi >> >> Theke Solutions (https://theke.io ) >> ? +54 9351 3513384 <+54%209%20351%20351-3384> >> GPG: B2F3C15F >> > -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Tue Dec 19 21:27:51 2017 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Tue, 19 Dec 2017 21:27:51 +0100 Subject: [Koha-devel] QA Sprint - Get your bugs ready! Message-ID: Hi all, just a quick note: the QA team will have a QA sprint on 21 December. https://wiki.koha-community.org/wiki/2017-12-21_QA_Sprint_Day You might want to make sure your patches apply, polish your commit messages and update your test plans! :) Katrin From tomascohen at gmail.com Thu Dec 21 18:15:32 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 21 Dec 2017 17:15:32 +0000 Subject: [Koha-devel] REST api RFCs In-Reply-To: References: Message-ID: I've written the RFC's for: /cities [1] /libraries [2] so we can vote on them on the next dev meeting (Dec 27th). PLEASE add your column with your discrepancies so it is easier to discuss/vote. Comments outside the table are welcome, with explanations, etc. THANKS! [1] https://wiki.koha-community.org/wiki/Cities_endpoint_RFC [2] https://wiki.koha-community.org/wiki/Libraries_endpoint_RFC El vie., 15 dic. 2017 a las 16:49, Barton Chittenden (< barton at bywatersolutions.com>) escribi?: > Tomas, > > Thank you for putting the REST api RFCs page together; having a series of > pages that document the routes was sorely needed. > > One question -- the RFCs lists the route for borrowers as '/patrons'. > However > https://wiki.koha-community.org/wiki/Coding_Guidelines_-_API#SWAGGER1.2:_Resource_names > suggests that we should use /users instead of /borrowers, /patrons, or > /members. > > Should we change the RFC to follow the Coding Guidelines, or change the > guidelines? > > > On Fri, Dec 15, 2017 at 5:15 AM, Tomas Cohen Arazi > wrote: > >> Andreas, it will be included! That list is only what I managed to write >> after the dev meeting, and is certainly incomplete. >> >> El vie., 15 de dic. de 2017 5:44 a. m., Andreas Hedstr?m Mace < >> andreas.hedstrom.mace at su.se> escribi?: >> >>> Hi! >>> >>> >>> >>> This sounds like a really good initiative Tom?s, getting the major >>> endpoints listed and structured so that the REST API work can proceed! >>> >>> >>> >>> However, I?m surprised that the endpoint for accountlines is not listed >>> in the RFC. Some reasons why I think that this should be included: >>> >>> >>> >>> We at Stockholm University Library is already using (a previous) version >>> of this endpoint in production >>> >>> You mentioned that you included other endpoints BibLibre is working on: >>> we sponsored BibLibre to build this endpoint a while back >>> >>> But above all I believe other libraries will also be interested in using >>> this endpoint! (At the hackfest in Lund recently, there was interest in >>> using this endpoint from Oslo Public Library etc.) >>> >>> >>> >>> Best regards, >>> >>> Andreas Hedstr?m Mace >>> >>> >>> >>> >>> >>> *Fr?n: * p? uppdrag av >>> Tomas Cohen Arazi >>> *Datum: *torsdag 14 december 2017 16:28 >>> *Till: *koha-devel >>> *?mne: *[Koha-devel] REST api RFCs >>> >>> >>> >>> Hi everyone. Following yesterday's dev meeting (I'm sorry I couldn't >>> attend) it was clear there should be some votes on the changes that we >>> belive need to be made. >>> >>> >>> >>> In order to organize the documentation on this decision making process, >>> and have something more precise to vote on, I've put together a front wiki >>> page: >>> >>> >>> >>> https://wiki.koha-community.org/wiki/REST_api_RFCs >>> >>> >>> >>> in which all endpoint-specific RFCs can be found. I have added the >>> endpoints I've been, am and will be working on. Also endpoints I know >>> Biblibre is working on. >>> >>> >>> >>> As the discussion was about the patrons endpoint specifically, I started >>> by creating an RFC for it: >>> >>> >>> >>> https://wiki.koha-community.org/wiki/Patrons_endpoint_RFC >>> >>> >>> >>> It is organized in two sections: actions and paths, and the object >>> definition. The idea is that you can add your own column (put your name on >>> it) with your personal proposal. Discussions can happen in other places >>> like IRC or koha-devel. >>> >>> >>> >>> Please add your comments on each issue you think it is worth, and please >>> contact me if you have any doubts or want to discuss specific stuffs. >>> >>> >>> >>> I will be spending the next days polishing this RFC and moving into the >>> rest of them in the same way. >>> >>> >>> >>> Before adding new endpoints to that list, I would suggest we have a >>> small conversation here in koha-devel to avoid polluting the front page >>> with several variations of the same endpoints. This is just a suggestion, >>> though. >>> >>> >>> >>> Thanks for your interest and feedback! >>> >>> Cheers >>> >>> >>> >>> -- >>> >>> Tom?s Cohen Arazi >>> >>> Theke Solutions (https://theke.io ) >>> ? +54 9351 3513384 <+54%209%20351%20351-3384> >>> GPG: B2F3C15F >>> >> -- >> Tom?s Cohen Arazi >> Theke Solutions (https://theke.io ) >> ? +54 9351 3513384 <+54%209%20351%20351-3384> >> GPG: B2F3C15F >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at lists.koha-community.org >> http://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/ >> > > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Thu Dec 21 18:44:23 2017 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Thu, 21 Dec 2017 17:44:23 +0000 Subject: [Koha-devel] REST api RFCs In-Reply-To: References: Message-ID: /holds done too. Please review and add your opinion! Remember the landing page for the RFCs is here: https://wiki.koha-community.org/wiki/REST_api_RFCs Thanks! El jue., 21 dic. 2017 a las 14:15, Tomas Cohen Arazi () escribi?: > I've written the RFC's for: > > /cities [1] > /libraries [2] > > so we can vote on them on the next dev meeting (Dec 27th). > > PLEASE add your column with your discrepancies so it is easier to > discuss/vote. > Comments outside the table are welcome, with explanations, etc. > > THANKS! > > [1] https://wiki.koha-community.org/wiki/Cities_endpoint_RFC > [2] https://wiki.koha-community.org/wiki/Libraries_endpoint_RFC > > > El vie., 15 dic. 2017 a las 16:49, Barton Chittenden (< > barton at bywatersolutions.com>) escribi?: > >> Tomas, >> >> Thank you for putting the REST api RFCs page together; having a series of >> pages that document the routes was sorely needed. >> >> One question -- the RFCs lists the route for borrowers as '/patrons'. >> However >> https://wiki.koha-community.org/wiki/Coding_Guidelines_-_API#SWAGGER1.2:_Resource_names >> suggests that we should use /users instead of /borrowers, /patrons, or >> /members. >> >> Should we change the RFC to follow the Coding Guidelines, or change the >> guidelines? >> >> >> On Fri, Dec 15, 2017 at 5:15 AM, Tomas Cohen Arazi >> wrote: >> >>> Andreas, it will be included! That list is only what I managed to write >>> after the dev meeting, and is certainly incomplete. >>> >>> El vie., 15 de dic. de 2017 5:44 a. m., Andreas Hedstr?m Mace < >>> andreas.hedstrom.mace at su.se> escribi?: >>> >>>> Hi! >>>> >>>> >>>> >>>> This sounds like a really good initiative Tom?s, getting the major >>>> endpoints listed and structured so that the REST API work can proceed! >>>> >>>> >>>> >>>> However, I?m surprised that the endpoint for accountlines is not listed >>>> in the RFC. Some reasons why I think that this should be included: >>>> >>>> >>>> >>>> We at Stockholm University Library is already using (a previous) >>>> version of this endpoint in production >>>> >>>> You mentioned that you included other endpoints BibLibre is working on: >>>> we sponsored BibLibre to build this endpoint a while back >>>> >>>> But above all I believe other libraries will also be interested in >>>> using this endpoint! (At the hackfest in Lund recently, there was interest >>>> in using this endpoint from Oslo Public Library etc.) >>>> >>>> >>>> >>>> Best regards, >>>> >>>> Andreas Hedstr?m Mace >>>> >>>> >>>> >>>> >>>> >>>> *Fr?n: * p? uppdrag av >>>> Tomas Cohen Arazi >>>> *Datum: *torsdag 14 december 2017 16:28 >>>> *Till: *koha-devel >>>> *?mne: *[Koha-devel] REST api RFCs >>>> >>>> >>>> >>>> Hi everyone. Following yesterday's dev meeting (I'm sorry I couldn't >>>> attend) it was clear there should be some votes on the changes that we >>>> belive need to be made. >>>> >>>> >>>> >>>> In order to organize the documentation on this decision making process, >>>> and have something more precise to vote on, I've put together a front wiki >>>> page: >>>> >>>> >>>> >>>> https://wiki.koha-community.org/wiki/REST_api_RFCs >>>> >>>> >>>> >>>> in which all endpoint-specific RFCs can be found. I have added the >>>> endpoints I've been, am and will be working on. Also endpoints I know >>>> Biblibre is working on. >>>> >>>> >>>> >>>> As the discussion was about the patrons endpoint specifically, I >>>> started by creating an RFC for it: >>>> >>>> >>>> >>>> https://wiki.koha-community.org/wiki/Patrons_endpoint_RFC >>>> >>>> >>>> >>>> It is organized in two sections: actions and paths, and the object >>>> definition. The idea is that you can add your own column (put your name on >>>> it) with your personal proposal. Discussions can happen in other places >>>> like IRC or koha-devel. >>>> >>>> >>>> >>>> Please add your comments on each issue you think it is worth, and >>>> please contact me if you have any doubts or want to discuss specific stuffs. >>>> >>>> >>>> >>>> I will be spending the next days polishing this RFC and moving into the >>>> rest of them in the same way. >>>> >>>> >>>> >>>> Before adding new endpoints to that list, I would suggest we have a >>>> small conversation here in koha-devel to avoid polluting the front page >>>> with several variations of the same endpoints. This is just a suggestion, >>>> though. >>>> >>>> >>>> >>>> Thanks for your interest and feedback! >>>> >>>> Cheers >>>> >>>> >>>> >>>> -- >>>> >>>> Tom?s Cohen Arazi >>>> >>>> Theke Solutions (https://theke.io ) >>>> ? +54 9351 3513384 <+54%209%20351%20351-3384> >>>> GPG: B2F3C15F >>>> >>> -- >>> Tom?s Cohen Arazi >>> Theke Solutions (https://theke.io ) >>> ? +54 9351 3513384 <+54%209%20351%20351-3384> >>> GPG: B2F3C15F >>> >>> _______________________________________________ >>> Koha-devel mailing list >>> Koha-devel at lists.koha-community.org >>> http://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/ >>> >> >> -- > Tom?s Cohen Arazi > Theke Solutions (https://theke.io ) > ? +54 9351 3513384 <+54%209%20351%20351-3384> > GPG: B2F3C15F > -- Tom?s Cohen Arazi Theke Solutions (https://theke.io ) ? +54 9351 3513384 GPG: B2F3C15F -------------- next part -------------- An HTML attachment was scrubbed... URL: From katrin.fischer.83 at web.de Wed Dec 27 08:13:56 2017 From: katrin.fischer.83 at web.de (Katrin Fischer) Date: Wed, 27 Dec 2017 08:13:56 +0100 Subject: [Koha-devel] MySQL 5.7 issues and Database Config In-Reply-To: References: Message-ID: <247df3c0-f18f-6ccd-db32-125d83707a53@web.de> Hi, since this has been sitting unanswered for a while, I have added some notes to the wiki: https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Ubuntu_16.04_and_MySQL_5.7 We should also change the requirements listed on the website: https://koha-community.org/download-koha/ Katrin On 15.12.2017 15:16, Nick Clemens wrote: > HI All, > > At the last meeting it came up that the latest versions of MariaDB are > enforcing sql strict mode: https://mariadb.com/kb/en/library/sql-mode/ > > This page on the wiki will need to be updated with the configuration > tweaks needed for allowing koha to work: > https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Ubuntu_16.04_and_MySQL_5.7 > > We should also focus on solving the issues here: > https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17258 > > If someone with the correct knowledge can update the wiki it would be > appreciated. > > At the meeting folks were interested in helping anyone who can provide > patches to work towards compatibility. Let us know if you can, what > help you need, and let get this moving :-) > > -Nick (kidclamp) > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at lists.koha-community.org > http://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/ -------------- next part -------------- An HTML attachment was scrubbed... URL: