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

Ubuntu12.04+MariaDB Jenkins node removed
by Tomas Cohen Arazi 16 Sep '15

16 Sep '15

Hi, as current master is not supposed to support Ubuntu 12.04, I've just removed the tests on that node. We should set a Debian 8 + MariaDB node. If anyone has a spare VM that could be contributed for that purpose, just let me know. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F

1 0

Install master on debian jessie
by Tajoli Zeno 16 Sep '15

16 Sep '15

Hi to all, i'm try to install git master version on debian jessie. I installed modules using repo deb http://debian.koha-community.org/koha stable main [unstable doesn't work now] using the commands: sudo apt-get install koha-deps sudo apt-get install koha-perldeps sudo apt-get install liblog-log4perl-perl sudo apt-get install libplack-middleware-reverseproxy-perl sudo apt-get install memcached then I do git clone, checked and installed perl dependecies. For apache I installed sudo a2enmod rewrite deflate sudo a2enmod cgi sudo a2dissite 000-default sudo a2ensite koha Now there problem on apache. The intranet log says: [Tue Sep 15 17:25:04.573995 2015] [authz_core:error] [pid 7132] [client 10.0.2.2:54862] AH01630: client denied by server configuration It seems connect with this change from 2.2 to 2.4: http://httpd.apache.org/docs/2.4/upgrading.html -> Authorization I try to do the change from 2.2 configuration: Order deny,allow Deny from all to 2.4 configuration: Require all denied But it does't work. Do you have any more idea on the topic ? Bye Zeno Tajoli -- Zeno Tajoli /Dipartimento Sviluppi Innovativi/ - Automazione Biblioteche Email: z.tajoli(a)cineca.it Fax: 051/6132198 *CINECA* Consorzio Interuniversitario - Sede operativa di Segrate (MI)

3 2

Call for development news: September Newsletter
by kohanews 15 Sep '15

15 Sep '15

Let the community hear what cool things you're working on! Bugs that need testing, sign-offs and user feedback? k o h a news AT gmail dot com Thank you! -- Chad Roseburg Editor, Koha Newsletter

1 0

Thoughts about timing and Koha schedules
by Brendan Gallagher 14 Sep '15

14 Sep '15

Hi All - ByWater is on its 7th year, so we have a solid set of data for analyzing, and recently I've noticed a few things. Let me try and paint the picture. Major Koha releases are every six months and usually the 22nd day of the month, with the target being November and May. (Please correct me if I am wrong) Library funding cycles in the US run either fiscal year (July to June), Calendar year (January to December), or some odd fiscal year close to the July~June year. Ok that being said from the time management situation with ByWater that introduces a few complexities. (Let me describe the workflow and maybe you'll see what I am talking about) Most of the time a library will sign a migration contract with us that dictates we must have them "go-live" before a certain fiscal date OR the library isn't really able to "sign" a contract for services until a certain fiscally motivated date (which places us into a similar roll-out). That being said we find that May and November (plus and minus a month) are our busiest times of the year. I've got 3 people on the road for education/training, 3 people heavily in the fields of migrations scripts, and 3 developers that are heavily in the field of meeting development expectations for lots and lots of go-lives (*note - plus additional staff to support an influx in tickets or other support needs during a go-live period). So if we slide the releases to say February and August - I would be able to dedicate more man power (9+ people from the above paragraph) around the heavy testing/ debugging / bug writing/squashing periods for a release. I know I know - there isn't really a time that Koha doesn't need more testing, but I've noticed that the volunteer effort is usually much greater/demanding the closer we are to major release date. I am wondering if others are finding the same with their work schedules (other support providers, academic institutions, public institutions, and my favorite volunteers). Are there certain times of the years where your day job is predictably busy that you aren't able to dedicate the resources that you want towards the greatest project in the world Koha. With the data set that we're sitting on here, we are constantly seeking ways that we can contribute more. Just a thought and was curious if others analyzed a similar aspect with their environment and perhaps maybe we should bring such a discussion into the open or a general IRC meeting. Especially any of us that are support providers we should be always be thinking about how we can do more for Koha. Thanks and Cheers (another sleepless night thinking about my favorite subject - Koha), Brendan -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Portland, OR - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info(a)bywatersolutions.com

11 19

Re: [Koha-devel] koha use percona xtradb cluster
by Kivilahti Olli-Antti 11 Sep '15

11 Sep '15

Thanks for the links! Olli-Antti Kivilahti Järjestelmäkeittäjä vaarakirjastot.fi +358 50 449 7763 --Powered by Kubuntu Linux! On 10.09.2015 12:30, long_sam.tw wrote: Hi, Kivilahti attached files DB cluster plus haproxy some info Installing Percona XtraDB Cluster on Ubuntu https://www.percona.com/doc/percona-xtradb-cluster/5.5/howtos/ubuntu_howto.… Load balancing with HAProxy https://www.percona.com/doc/percona-xtradb-cluster/5.5/howtos/haproxy.html keepalived https://www.howtoforge.com/setting-up-a-high-availability-load-balancer-wit… sysbench test tool https://www.percona.com/doc/percona-xtradb-cluster/5.5/howtos/virt_sandbox.… BR, longshan Kivilahti Olli-Antti <olli-antti.kivilahti(a)jns.fi><mailto:olli-antti.kivilahti@jns.fi> 於 2015/9/10 (週四) 4:45 PM 寫道﹕ Wow! I am really happy that it works with Koha. How does it perform for you? How big is your library/consortium? Olli-Antti Kivilahti Järjestelmäkeittäjä vaarakirjastot.fi +358 50 449 7763 --Powered by Kubuntu Linux! On 10.09.2015 10:01, long_sam.tw wrote: Dear koha folks , Recently , I use percona xtradb cluster plus haproxy. + keepalived It provides ha & load balancing, some ref : https://www.percona.com/doc/percona-xtradb-cluster/5.6/installation/apt_rep… It support debian & ubuntu BR, longshan _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org<mailto:Koha-devel@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(a)lists.koha-community.org<mailto:Koha-devel@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/

2 1

koha use percona xtradb cluster
by long_sam.tw 10 Sep '15

10 Sep '15

Dear koha folks , Recently , I use percona xtradb cluster plus haproxy. + keepalivedIt provides ha & load balancing, some ref : https://www.percona.com/doc/percona-xtradb-cluster/5.6/installation/apt_rep… It support debian & ubuntu BR, longshan

2 1

Vote for the Kohacon 2016 conference location now!
by Mirko Tietgen 09 Sep '15

09 Sep '15

Dear list, we have opened the vote for the location of the Kohacon 2016 community conference. You can find the proposals in the Koha wiki at http://wiki.koha-community.org/wiki/KohaCon16_Proposals We decided on a simple form over a ranking at the IRC meeting a few minutes ago. The rules are simple: * everybody can vote * one vote per person The voting period is one week. The vote is open until 16 September 2015, 12 UTC. To vote, visit http://abunchofthings.net/limesurvey/index.php/639452?lang=en and follow the instructions. Happy voting, and thanks to both bidders for offering to host Kohacon 2016. Good luck! :) Mirko

1 1

Hi
by Ramesh Parichi 08 Sep '15

08 Sep '15

Hi Friends Can I have the step by step procedure to install KOHA on Ubuntu 14.04 LTS. I have old procedure and i believe there is some change in the procedure in 14.04. please help me out. Regards P. Ramesh Senior Technical Officer Osmania University Hyderabad, India.

2 1

koha for e-resource management
by long_sam.tw 08 Sep '15

08 Sep '15

Dear koha folks. Recently , many ILS provide e-resource management for library. In koha, Are there some plan about e-resource management in the future? BR, longsam

3 5

Atomicupdates for clunky forked Kohas
by Kivilahti Olli-Antti 04 Sep '15

04 Sep '15

Hi there! I heard the community is moving to atomicupdates. We moved to atomicupdates as well! To help us better manage atomicupdates, I devised a installer to keep track of which atomicupdates have already been applied so we don't apply the same updates many times. Also when we deploy/backport more and more feature, it becomes really hard to know which atomicupdates have been installed and which have not. Check this Bug out if you are putting features in production before they get to master. There is also a nice slide show! http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14698 Here is the --help from atomicupdates.pl, it introduces itself quite nicely! <<SNIP atomicupdates.pl Runs all the not-yet-applied atomicupdate-scripts and sql in the atomicupdates-directory, in the order specified by the _updateorder-file. This script uses koha.atomicupdates-table to see if the update has already been applied. Also acts as a gateway to CRUD the koha.atomicupdates-table. -v --verbose Integer, 1 is not so verbose, 3 is maximally verbose. -h --help Flag, This nice help! -a --apply Flag, Apply all the pending atomicupdates from the atomicupdates-directory. -d --directory Path, From which directory to look for atomicupdate-scripts. Defaults to '$KOHA_PATH/installer/data/mysql/atomicupdate/' -r --remove String, Remove the upgrade entry from koha.atomicupdates eg. --remove "Bug71337" -i --insert Path, Add an upgrade log entry for the given atomicupdate-file. Useful to revert an accidental --remove -operation or for testing. eg. -i installer/data/mysql/atomicupdate/Bug5453-Example.pl -l --list Flag, List all entries in the koha.atomicupdates-table. This typically means all applied atomicupdates. -p --pending Flag, List all pending atomicupdates from the atomicupdates-directory. -g --git Path, Build the update order from the Git repository given, or default to the Git repository in $KOHA_PATH. Eg. --git 1, to build with default values, or --git /tmp/kohaclone/ to look for another repository EXAMPLES: atomicupdate.pl -g 1 -a Looks for the Git repository in $KOHA_PATH, parses the issue/commit identifiers from the top 10000 commits and generates the _updateorder-file to tell in which order the atomicupdates-scripts are executed. Then applies all pending atomicupdate-scripts in the order (oldest to newest) presented in the Git repository. atomicupdate --apply -d /home/koha/kohaclone/installer/data/mysql/atomicupdate/ Applies all pending atomicupdate-scripts from the given directory. If the file '_updateorder' is not present, it must be first generated, for example with the --git 1 argument. UPDATEORDER: When deploying more than one atomicupdate, it is imperative to know in which order the updates are applied. Atomicupdates can easily depend on each other and fail in very strange and hard-to-debug -ways if the prerequisite modifications are not in effect. The correct update order is defined in the atomicupdates/_updateorder-file. This is a simple list of issue/commit identifiers, eg. Bug5454 Bug12432 Bug3218 #45 This file is most easily generated directly from the original Git repository, since the order in which the Commits have been introduced most definetely is the order they should be applied. When deploying the atomicupdates to production environments without the Git repository, the _updateorder file must be copied along the atomicupdate-scripts. P.S. Remember to put atomicupdate/_updateorder to your .gitignore SNAP>> -- Olli-Antti Kivilahti Järjestelmäkeittäjä vaarakirjastot.fi +358 50 449 7763 --Powered by Kubuntu Linux!

1 0