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

Weired OPAC
by Vimal Kumar V. 27 Nov '12

27 Nov '12

Dear Friends, I upgraded Koha 3.8.6 to 3.10. I got the OPAC page seems weired. see the screenshot, https://picasaweb.google.com/lh/photo/EYE-GwXzFzJU4rxKxqOOpNMTjNZETYmyPJy0l… I installed Koha from Ubuntu packages. I installed all dependencies. -- Vimal Kumar V. Mahatma Gandhi University Library Kottayam, Kerala- 686 560 Web: http://www.vimalkumar.org Blog: http://linuxhalwa.blogspot.com http://kohageek.blogspot.in --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

4 3

test
by laurent ducos 27 Nov '12

27 Nov '12

1 0

last test
by laurent ducos 27 Nov '12

27 Nov '12

sorry

1 0

test
by laurent ducos 27 Nov '12

27 Nov '12

test

1 0

test
by laurent ducos 27 Nov '12

27 Nov '12

Just a test, sorry for the noise

1 0

Bugzilla Change Recommendation
by Nicole Engard 26 Nov '12

26 Nov '12

Right now when you comment on a bug in Bugzilla it saves your change and shows the next bug in the search on the screen. Often I need to make a couple edits and this makes me change the wrong bug report (an error I've seen others make as well). We have bugzilla set up at work to redirect you back to the bug you just edited/commented on when you submit - is there a reason why we don't do that with Koha's bugzilla? Nicole

3 3

Re: [Koha-devel] FW: Changes in Bugzilla
by Marcel de Rooy 26 Nov '12

26 Nov '12

I added a patch manually. And cannot set the status to Needs signoff. That should really be made possible! -----Oorspronkelijk bericht----- Van: Paul Poulain [mailto:paul.poulain@biblibre.com] Verzonden: maandag 26 november 2012 10:59 Aan: Marcel de Rooy Onderwerp: Re: FW: [Koha-devel] Changes in Bugzilla Le 26/11/2012 10:49, Marcel de Rooy a écrit : > Example 7143 is on Assigned, the field is not shown. I wrote that on my initial mail: That's why I've added a custom field "patch complexity", with jared suggested values, that appears only when you submit a patch (ie: when bug status reaches "need signoff" or any 'later' value) => the field does not appear when the bug is "assigned", only when the bug reaches "need signoff" or later -- Paul POULAIN - Associé-gérant Tel : (33) 4 91 81 35 08 http://www.biblibre.com Logiciels Libres pour les bibliothèques et les centres de documentation

2 2

Changes in Bugzilla
by Paul Poulain 26 Nov '12

26 Nov '12

Hello, As I've suggested in previous mails, I made some changes in bugzilla: * new severity "new feature". This is/will be for real new features. The "enhancement" being for an existing feature. That will be useful for generating Release Notes of 3.12 (I'll take care later of updating the script) * New custom field for patch complexity: I suggested to change "priority" to put "patch complexity" instead. - Jared suggested to use the following terms: 1-string patch 2-trivial patch 3-small patch 4-medium patch 5-large patch - Marcel suggested to use a specific custom field. After thinking of it again, I think Marcel was right: the "patch complexity" will be something irrelevant for librarians and/or when submitting a bug (and not a patch !). One can know the complexity of a patch only ... when the patch is submitted. That's why I've added a custom field "patch complexity", with jared suggested values, that appears only when you submit a patch (ie: when bug status reaches "need signoff" or any 'later' value) I made this field mandatory, to be sure it's filled. For QA team (or anyone else), I suggest to add this column to results lists: * do your query * "Change columns" * add "Complexity of the patch" Have a good day. -- Paul POULAIN - BibLibre http://www.biblibre.com Free & Open Source Softwares for libraries Koha, Drupal, Piwik, Jasper

2 3

New Koha Packages released
by Robin Sheat 26 Nov '12

26 Nov '12

Packages for Koha 3.8.7 and 3.10.0 are now available in the usual place. As there's a new major version, this requires some changes. Previously, in the 'squeeze' repository, there was 3.8, and in oldstable, 3.6. Now 3.10 is going in to squeeze, 3.8 moves into oldstable, and 3.6 falls out. For now, anyway. There are plans to set up a repo for even older, maintained versions too. This will require a dist-upgrade, as there will be new dependencies. A note: right now, the squeeze repo may not install on 64-bit machines. This is something that will be fixed soon (like, tomorrow.) Let me know if there are any issues. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D

1 0

Test failure in 3.10.0
by Robin Sheat 26 Nov '12

26 Nov '12

There is a syntax error in the test cases. I don't really know how to fix it or I would. This is (not surprisingly) breaking the package build for 3.10.0, so could someone who knows what's going on here please take a look ASAP. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9142 $ KOHA_CONF=~/koha-dev/etc/koha-conf.xml t/Calendar.t 1..22 ok 1 - use Koha::Calendar; ok 2 - use C4::Calendar; String found where operator expected at t/Calendar.t line 130, near "subtest '\'Datedue\' tests'" (Do you need to predeclare subtest?) "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 131. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 134. "my" variable $dt masks earlier declaration in same scope at t/Calendar.t line 135. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 137. "my" variable $dt masks earlier declaration in same scope at t/Calendar.t line 137. "my" variable $one_day_dur masks earlier declaration in same scope at t/Calendar.t line 137. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 141. "my" variable $dt masks earlier declaration in same scope at t/Calendar.t line 141. "my" variable $two_day_dur masks earlier declaration in same scope at t/Calendar.t line 141. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 145. "my" variable $test_dt masks earlier declaration in same scope at t/Calendar.t line 145. "my" variable $seven_day_dur masks earlier declaration in same scope at t/Calendar.t line 145. String found where operator expected at t/Calendar.t line 151, near "subtest '\'Calendar\' tests'" (Do you need to predeclare subtest?) "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 152. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 155. "my" variable $dt masks earlier declaration in same scope at t/Calendar.t line 156. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 158. "my" variable $dt masks earlier declaration in same scope at t/Calendar.t line 158. "my" variable $one_day_dur masks earlier declaration in same scope at t/Calendar.t line 158. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 162. "my" variable $test_dt masks earlier declaration in same scope at t/Calendar.t line 162. "my" variable $seven_day_dur masks earlier declaration in same scope at t/Calendar.t line 162. String found where operator expected at t/Calendar.t line 168, near "subtest '\'Days\' tests'" (Do you need to predeclare subtest?) "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 169. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 172. "my" variable $dt masks earlier declaration in same scope at t/Calendar.t line 173. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 175. "my" variable $dt masks earlier declaration in same scope at t/Calendar.t line 175. "my" variable $one_day_dur masks earlier declaration in same scope at t/Calendar.t line 175. "my" variable $cal masks earlier declaration in same scope at t/Calendar.t line 179. "my" variable $test_dt masks earlier declaration in same scope at t/Calendar.t line 179. "my" variable $seven_day_dur masks earlier declaration in same scope at t/Calendar.t line 179. syntax error at t/Calendar.t line 130, near "subtest '\'Datedue\' tests'" syntax error at t/Calendar.t line 148, near "}" syntax error at t/Calendar.t line 165, near "}" syntax error at t/Calendar.t line 182, near "}" Execution of t/Calendar.t aborted due to compilation errors. # Looks like you planned 22 tests but ran 2. # Looks like your test exited with 255 just after 2. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D

1 1