- Koha-devel - lists.koha-community.org

Perl 7
by dcook＠prosentient.com.au 26 Jun '20

26 Jun '20

For those who don't know, Perl 7 was just announced yesterday: https://www.perl.com/article/announcing-perl-7/ I've talked about this in the "Perl version requirement" thread but basically it boils down to "Perl 7 is v5.32 with different settings. Your code should work if it's not a mess. Expect a user release within a year." The article is worth a read though. It points out a number of language aspects that have changed (e.g. bareword file handles, indirect object notation, etc), and we could actually work on eliminating those in our current code to bring Koha more in line with modern Perl. While we're still years away from moving Koha over to this hypothetical Perl 7, it's something to look forward to. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

4 5

Call for testing: Merge deleted biblio, biblioitems, biblio_metadata, and items tables (bug 20271)
by Katrin Fischer 23 Jun '20

23 Jun '20

Hi all, early on in a release cycle is the best moment to discuss, test and progress on big changes proposed for Koha. These can have adverse effects, so we want as many people as possible involved in testing. The first of these bugs we want to ask for help with is: Bug 20271- Merge deleted biblio, biblioitems, biblio_metadata, and items tables https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20271 The proposed patches merge the tables for active bibliograhic and item data. Testing can be done on a development environment using the remote branch listed in the URL field on Bugzilla: https://gitlab.com/joubu/Koha/commits/bug_20271 Any findings can be added to Bugzilla, be discussed on the mailing list or IRC. We've also set up a FramaCalc file that you can add notes to get some ideas from for testing: https://lite.framacalc.org/9hdw-bug_20271 We are looking for as much feedback as possible until the end of next week. The more buzz, the happier we will be! Best wishes, Katrin

1 0

Koha 19.11.07 released
by Aleisha Amohia 23 Jun '20

23 Jun '20

Hello! The Koha community is proud to announce the release of Koha 19.11.07. Koha 19.11.07 is a bugfix/maintenance release that includes 2 enhancements and 48 bugfixes. Full release notes can be found here: https://koha-community.org/koha-19-11-07-released/ This is my first release! :D -- *Aleisha Amohia* Koha Developer Catalyst IT - Expert Open Source Solutions She/her | Mob: +64 21 024 04004 | Tel: +64 4 499 2267 | www.catalyst.net.nz <http://www.catalyst.net.nz> Catalyst Logo CONFIDENTIALITY NOTICE: This email is intended for the named recipients only. It may contain privileged, confidential or copyright information. If you are not the named recipient, any use, reliance upon, disclosure or copying of this email or its attachments is unauthorised. If you have received this email in error, please reply via email or call +64 4 499 2267.

1 0

Translate Koha Plugins?
by dcook＠prosentient.com.au 22 Jun '20

22 Jun '20

Hi all, Is there an existing mechanism for translating Koha Plugins? I'm (slowly) working on some plugins, and there are folk in the Czech Republic who would like to use them but not in English. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

6 7

Re: [Koha-devel] Koha Installation on Ubuntu 20.04
by Mason James 22 Jun '20

22 Jun '20

hi Sandeep, the output looks ok, so you can ignore that message but, it seems you need to run... sudo a2enmod headers proxy_http On 22/06/20 3:09 am, Dr. Sandeep Bhavsar wrote: > Hi Mason James > > I have attached the results of both the commands. > > On Sun, Jun 21, 2020 at 4:27 AM Mason James <mtj(a)kohaaloha.com <mailto:mtj@kohaaloha.com>> wrote: > > hi Sandeep > can you run these 2 command, and show the results... > > # dpkg -l koha-common | grep koha > ii koha-common 20.05.00-1 all integrated (physical) library management system > > # systemctl restart koha-common.service ; systemctl status koha-common.service > koha-common.service - LSB: Start required services for each Koha instance > Loaded: loaded (/etc/init.d/koha-common; generated; vendor preset: enabled) > Active: active (exited) since Sun 2020-06-21 10:50:29 NZST; 5min ago > Docs: man:systemd-sysv-generator(8) > Process: 30687 ExecStop=/etc/init.d/koha-common stop (code=exited, status=0/SUCCESS) > Process: 30812 ExecStart=/etc/init.d/koha-common start (code=exited, status=0/SUCCESS) > CPU: 92ms > > > On 20/06/20 8:40 pm, Dr. Sandeep Bhavsar wrote: > > > > Dear All > > > > I am installing Koha on Ubuntu 20.04 and facing the below error , please guide > > > > Setting up koha-common (20.05.00-1) ... > > Failed to enable unit: Unit /run/systemd/generator.late/koha-common.service is transient or generated. > > > > > > -- > > Warm Regards > > > > Dr. Sandeep Bhavsar > > Librarian > > *Prin. L. N. Welingkar Institute of Management Development & Research(AUTONOMOUS)* > > L Napoo Road | Matunga (CR) | Mumbai- 400 019. > > Tel: 022-2419 8377 | Mob: 9870 18 9999 > > Library Portal/: http://elearn.welingkar.org/infowe/ > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel(a)lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> > > https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel > > website : http://www.koha-community.org/ > > git : http://git.koha-community.org/ > > bugs : http://bugs.koha-community.org/ > > > > -- > Warm Regards > > Dr. Sandeep Bhavsar > Librarian > *Prin. L. N. Welingkar Institute of Management Development & Research(AUTONOMOUS)* > L Napoo Road | Matunga (CR) | Mumbai- 400 019. > Tel: 022-2419 8377 | Mob: 9870 18 9999 > Library Portal/: http://elearn.welingkar.org/infowe/ >

2 1

Koha manual - git setup for local editing
by David Nind 21 Jun '20

21 Jun '20

It's probably just me, but I find setting up or explaining the git setup and editing workflow for the manual to others challenging - particularly those new to git as well: https://wiki.koha-community.org/wiki/Editing_the_Koha_Manual#Editing_the_ma… Also, it may be because I'm just used to working with my own repositories at a basic git level, and not having to worry about forking. Initial setup: - Fork the GitLab repository - Clone your fork - Add a second remote to track the main Koha manual repository (community) - Add a branch to track the remote repository (community_master) Workflow for editing: - Make sure everything is up-to-date: checkout community_master branch, pull, merge with local master - Create a new branch for your changes - Edit and commit - Push branch to GitLab - Create a merge request using GitLab Can anyone suggest any alternative ways to set this up or improve it? Or is that as "easy" as we can make it? (and just say follow the really good instructions and you'll get used to it in time..) Thanks! David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 m. +64 21 0537 847

2 1

Koha Installation on Ubuntu 20.04
by Dr. Sandeep Bhavsar 21 Jun '20

21 Jun '20

Dear All I am installing Koha on Ubuntu 20.04 and facing the below error , please guide Setting up koha-common (20.05.00-1) ... Failed to enable unit: Unit /run/systemd/generator.late/koha-common.service is transient or generated. -- Warm Regards Dr. Sandeep Bhavsar Librarian *Prin. L. N. Welingkar Institute of Management Development & Research (AUTONOMOUS)* L Napoo Road | Matunga (CR) | Mumbai- 400 019. Tel: 022-2419 8377 | Mob: 9870 18 9999 Library Portal*: http://elearn.welingkar.org/infowe <http://elearn.welingkar.org/infowe>*

2 1

Clarifying public routes on REST API
by dcook＠prosentient.com.au 18 Jun '20

18 Jun '20

Hi all, Could I get some clarification on the purpose of the "public" routes for the REST API? In the case of https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24909, it looks like it's a public API that doesn't require authentication/authorization. However other "public" routes like /api/v1/public/* all require authentication and appropriate authorization. Are these denoted as "public" as we're suggesting that only these routes should be used by third-party "public" systems? I don't get it. Hoping someone can offer some clarification. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

2 4

Adopting CPAN and Carton
by dcook＠prosentient.com.au 17 Jun '20

17 Jun '20

Hi all, What are people's thoughts on CPAN and Carton (the Perl version of Bundler, Composer, NPM, etc)? I like the idea as a way of more easily managing Perl dependencies regardless of Linux distribution and version; in other words, we could provide the same dependencies regardless of being on Debian Jessie/Debian Stretch/Debian Buster or Ubuntu or Fedora or RHEL or OpenSUSE. I suppose the difficulty is how we do a community-friendly deployment? I see two main options: 1. Have the Debian package run "carton install" automatically during install/upgrade a. This could be error prone and difficult to support. 2. Have the Koha Debian Package Manager run "carton install" when building the package, and embed the Perl modules in the Koha package a. It's unknown how much this would increase the size of the Koha package It looks like there is some precedence within Debian for embedding modules in a Debian package: https://wiki.debian.org/Javascript/Nodejs/Npm2Deb/Embedding https://wiki.debian.org/Javascript/GroupSourcesTutorial I think Debian and Ubuntu would (and perhaps should) still be first class citizens, but it would mean it would be easier to have RPM packages too - whether they're official, semi-official, or unofficial. I have a lot of experience building RPM packages for CentOS/RHEL and OpenSUSE, so I'd be willing to be involved in some capacity there. I think retaining Debian packages is important, because we have a number of non-Perl dependencies, and the Debian packages provide a lot of very useful automation. Anyway, please share your thoughts. Victor and Martin brought it up on #koha, and I figured I'd continue the conversation here. Personally, I'm moving away from packaging Perl dependencies as Debian packages for non-Koha projects, because it makes porting the projects to a newer version of the same OS much more difficult. I know using Debian's Perl packages have a lot of advantages, as they're tested, reviewed, and patched, but I think it might be time to consider a change. David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Online: 02 8005 0595

9 17

Time to translate! string freeze for 19.05.x has begun
by Victor Grousset/tuxayo 15 Jun '20

15 Jun '20

Hi, saluton, hola, bonjour, String freeze is into effect today Monday 15 June 2020 for the 19.05.x maintenance branch. 19.05.12 release is scheduled for Monday 22 June 2020. Which means it's the right time to head over to the translation platform: https://translate.koha-community.org/projects/ Important reminder: if you add or change a translation in version 19.05, then you must also copy it to 19.11 and 20.05. Otherwise your work will be lost when upgrading to these next versions or the future ones. Happy translating, -- Victor Grousset/tuxayo

1 0