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

Re: [Koha-devel] 3.8.4 interim [was: koha-zebra-daemon not starting]
by Paul 15 Sep '12

15 Sep '12

At 04:41 PM 8/22/2012 -0300, Tomas Cohen Arazi wrote: [snip] > > The tarball has always worked extremely well on i386 machines -- I just > get the impression (not proven) that Ubuntu 12.04 gets its knickers in a > twist on AMD64. Â But with a little time and effort workarounds can be > found. Â Probably nothing wrong, just new quirks, with either Ubuntu or > Koha, but I do not need to be under pressure for the production upgrade. > >is not a 12.04 problem, is a problem with the specific file you're using >with dpkg, which lists some files not available anymore on 12.04. >As Mark said that file has already been patched and its waiting for >inclusion on next release. Thanks for the reply. But, as you say, "its waiting for inclusion on next release" so it's broken in this release. >That said, you can do a clean install using the instructions and ommiting >that --set-selections step. And installing the dependencies by hand. As >Mark also said. More or less what I've done -- but it would not be rocket science to edit install_misc/ubuntu.packages to avoid a certain amount of grief (and before anyone asks "well why don't you do it?" I will as soon as I'm certain that my experience is reproducible and bullet-proof. It may involve looking at the upstream .pl file to see how the list is invoked.) >I also use the tarball in our deployment (38 instances on a single BIG >server) without issues. I'm only trying a test install on relatively BIG server (64-bit, 6 core Intel i7-980X, solid state raided drives, 16Gb ram), mileage varies... > Besides that i386 packages pull which I reported and has been solved. When, where, how? I had to 'sudo apt-get purge .*:i386' for about 50 dependencies in the pull in koha-3.08.04.tar.gz >Anyway, I think we should go back to what your original problem was.Â Is >your incremental indexing working? That was 3.8.3, now trashed, but it never worked -- I'll try it on a 3.8.4 install as soon as I'm away from this machine. >Have you properly set your sax parser? [snip] Yes. Best - P. --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

13 42

String freeze for 3.8.5
by Chris Cormack 14 Sep '12

14 Sep '12

Hi All I will not be pushing any more patches that involve string changes from now on, until 3.8.5 is released on the 22nd of September. Frederic when time permits can you update the 3.8.x po files in pootle please. Thank you Chris

3 3

Overdue Notices
by glaws 14 Sep '12

14 Sep '12

I have a question about overdue notices in Koha 3.8.3. Not sure if this is a bug or not... When a patron has overdue items, the "First Overdue Notice" will generate a list of those items. Perfect. When other overdue items subsequently become overdue within an undetermined but limited amount of time, a "First Overdue Notice" is generated for those items, but if the first set of items have not been resolved (by returning them), they are repeated in the second "First Overdue Notice". See attached .pdf. Desired/correct functionality? -- Greg Lawson Network Administrator Rolling Hills Consolidated Library 1912 N. Belt Highway St. Joseph, MO 64506

3 3

Please include a test plan for your patches!
by Owen Leonard 14 Sep '12

14 Sep '12

With Global Bug-Squashing Day in full swing, I want to test some patches and sign off what I can. The list of bugs needing signoff (http://bugs.koha-community.org/bugzilla3/buglist.cgi?cmdtype=dorem&remactio…) has no low-hanging fruit, so that makes it really important that every bug report include a good test plan. Here are the basics for what I should know after reading the bug report: 1. What the problem is. 2. How to reproduce the problem. 3. What the patch does to solve the problem. 4. What (if any) configuration steps need to be taken after the patch is applied. 5. What steps to take to test that the patch is working correctly. A lot of patches seem to be added with only #3, which in some ways is the least important step from the point of view of people testing. If you have bug on Paul's list of patches which won't be pushed after the feature freeze (in the RM newsletter: http://koha-community.org/koha-release-manager-newsletter-10-2012-08/) and you want to make sure it can be tested, please add a thorough test plan! -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 1

(ver.3.6.2) Staff / Tools: News / Formatting news
by Kari Blomster 14 Sep '12

14 Sep '12

Hello! I have hard times finding the way to format my news tool editor input text in HTML, running ver3.6.2. I have at Staff interface [Home -> Tools (Additional tools) -> News + New Entry) ] now only txt alternative, though manual(en) shows HTML-editor: http://manual.koha-community.org/3.6/en/tools.html#newstool Is there an option to set for HTML in news and/or comments? I searched Koha Administration text search and net freewordsearch for featurelist or casual mentions, but none suitable. Then I gave up and turned here. Object: Help me! Gary Blomster ----- (Mr.) Kari Blomster, librarian Hailuoto Public Library, Finland | http://www.hailuoto.fi/sivu/fi/kuntapalvelut/perus/Sivistyspalvelut/kirjast… Profiles | http://www.hailuoto.fi/sivu/fi/kuntapalvelut/perus/Sivistyspalvelut/kirjast… -- View this message in context: http://koha.1045719.n5.nabble.com/ver-3-6-2-Staff-Tools-News-Formatting-new… Sent from the Koha-devel mailing list archive at Nabble.com.

1 0

Bug 8524 Add barcode plugin that does not autofill
by Chris Cormack 13 Sep '12

13 Sep '12

Hi All I am tempted to push bug 8524 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8524 to 3.8.x to be included in 3.8.5 It is a new plugin that doesn't touch existing code so is safe, and actually fixes a 'bug' in certain use cases. Namely if a library autobarcodes, but don't barcode their ebooks. (quote 123) :) Any objections? Chris

3 2

Call for News for the September Newsletter
by Daniel Grobani 11 Sep '12

11 Sep '12

Dear Koha Kommunitarians, I'm harvesting news for this month's newsletter. Please send me by the 20th anything you think your fellow community members might like to know about. "News" can be as short as a sentence or as long as a paper. I especially encourage you to send me a line or two for the gossip/society column about what you're currently working on. And if you know of a go-live not announced on the list, please be sure to let me know about it. Thanks, Daniel Grobani

1 0

Re: [Koha-devel] cron, env, etc
by Paul 07 Sep '12

07 Sep '12

At 11:13 AM 9/6/2012 -0300, Tomas Cohen Arazi wrote: Tomas - I'm taking the liberty of Cc:ing the devel list (you suggested that you had spoken with some of them) but would thank you for the 'off-list' exchange of emails. I have spent quite a bit of time checking various possibilities/combinations to ensure that a user cron, re-indexing zebra, functions as expected on various combinations of Koha 3.6.x and 3.8.4 on Ubuntu 10.04 and 12.04 (the two current Ubuntu LTS servers) on both 32- and 64-bit boxes. I have come to the conclusion that the use of crontab as outlined in RESULT [B] "rewritten" (see below) is fully functional, is a single "edit" at the time of installation, and could be included with total clarity in INSTALL.ubuntu and on the Wiki. The use of cron.d/koha RESULT [C] "second scenario" is also functional, but requires two edits at install time (and I've included a couple of minor caveats.) I have not looked at the "package", only at various tarballs, so do not know under what conditions either crontab or cron.d may be used. ISTR reading that package and tarball directory structure differs, so am not at all certain how close the two "installs" should or could be maintained. HTH - regards - Paul NOTES: [A] From $ man cron : "cron also reads /etc/crontab, which is in a slightly different format (see crontab(5)). Additionally, cron reads the files in /etc/cron.d: it treats the files in /etc/cron.d as in the same way as the /etc/crontab file (they follow the special format of that file, i.e. they include the user field). However, they are independent of /etc/crontab: they do not, for example, inherit environment variable settings from it." [B] From 3.8.4 INSTALL.ubuntu : 5.2.2 Zebra Indexer Add an entry in Koha user crontab to scheduled added/updated/deleted records indexing by Zebra with this command: <path/to/koha>/misc/migration_tools/rebuild_zebra -z -b -a [C] From <http://wiki.koha-community.org/wiki/Koha_on_Ubuntu> [abbreviated] 3 - Setup the environment variables used by Koha scripts $ sudo gedit /etc/cron.d/koha Add KOHA_CONF=/etc/koha/koha-conf.xml KOHAPATH=/usr/share/koha PERL5LIB=$KOHAPATH/lib (Alternatively ... same result.) $ sudo gedit /etc/bash.bashrc.local Add export KOHA_CONF=/etc/koha/koha-conf.xml export PERL5LIB=/usr/share/koha/lib 5b - Reindexing Choices Option #1: See http://wiki.koha-community.org/wiki/Background_indexing_with_Zebra Option #2: Add a cronjob to index your zebra database. $ sudo gedit /etc/cron.d/koha Add # The cronjobs */5 * * * * koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z &> /dev/null RESULTS: [B] above does not funtion. It does function if rewritten as: 5.2.2 Zebra Indexer Add a Koha user cron job to schedule added/updated/deleted record indexing by Zebra with this command: $ sudo vi /etc/crontab Append the following lines: KOHA_CONF=/etc/koha/koha-conf.xml KOHAPATH=/usr/share/koha PERL5LIB=$KOHAPATH/lib */1 * * * * koha $KOHAPATH/bin/migration_tools/rebuild_zebra.pl -a -b -z &> /dev/null :x [C] {5b Option 1 - respectfully for Frédéric - not explored "This solution is completly outside Koha"} First scenario: para 3 "cron.d" plus para 5.b Option 2 does not function (probably due to [A]) Second Scenario: para 3 "Alernatively" plus para 5.b Option 2 does function, with two possible caveats: (a) Comparing my notes from various "new installs" versus "sandbox testing edits", I suggest adding 'export KOHAPATH=/usr/share/koha' to .bashrc between the other two en vars (b) For a [user] cron, I prefer to 'export' from /home/[user]/.bashrc rather than /etc/bash.bashrc.local --- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

1 0

Unit tests and mock module
by Paul Poulain 07 Sep '12

07 Sep '12

Hi Koha-devel, I just pushed t/Members_AttributeTypes.t unit tests that fake the database. The test here could be redundant with t/db_dependent tests I feel we should be aware of that, and : * decide Mock is the way to go, and promote using of Mock, removing db_dependent tests (that fail if you don't have a database) * decide we should prefer db_dependent tests and limit the use of Mock to specific cases I feel that deciding nothing will result in a poor readability of what tests what, and some difficulties to know which test is to update when you update a sub. So, as Mock is introduced, we must speak of it. Your opinion ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

7 6

RFC on sysprefs deprecation workflow
by Tomas Cohen Arazi 07 Sep '12

07 Sep '12

We have fully documented the process of adding a syspref to Koha[1]. It remains unclear which workflow syspref deprecation should follow. I've been told on IRC that, traditionally, deprecated sysprefs are set to a 'good default' value, and then hidden. If you take a look at bug 8724 [2] you'll notice that i followed that path. But as NoZebra is to be fully removed from Koha tree I ask: what do u think the workflow for syspref removal be? It should be added to the sysprefs wiki too. I can do it if needed. Regards To+ [1] http://wiki.koha-community.org/wiki/System_Preferences [2] http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8724

6 6