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

More qa test tool patches
by Mark Tompsett 08 Mar '16

08 Mar '16

Greetings, Seems like bug 15870 has motivated me to work on patches for Koha’s QA test tool. I just wrote a nicer counter/complimentary patch for 16003 (either or both, I don’t care), and now that “fatal” warning will clear up nicely with bug 16008. GPML, Mark Tompsett

1 0

Fwd: Packing needs - status to add to bugzilla and the dashboard?
by Brendan Gallagher 08 Mar '16

08 Mar '16

Thanks Liz. ---------- Forwarded message ---------- From: Liz Rea <liz(a)catalyst.net.nz> Date: Tue, Mar 8, 2016 at 12:37 PM Subject: Re: [Koha-devel] Packing needs - status to add to bugzilla and the dashboard? To: Brendan Gallagher <info(a)bywatersolutions.com> Robin wrote a couple of quite good wiki pages on this subject: https://wiki.koha-community.org/wiki/Building_Debian_Dependencies https://wiki.koha-community.org/wiki/Building_Debian_Dependencies/Dependenc… On 09/03/16 06:50, Brendan Gallagher wrote: Yup all good points. Not to put it all on the PM - but I think a way to track this in BZ is needed. A better workflow - perhaps based on Chris's point - a "failed QA - needs package" status (or some worded status)? Do we have a defined role description of responsibility of the Packaging Manager? (I've only read Robin's posts to the mailing list before - is that it?) On Tue, Mar 8, 2016 at 9:37 AM, Galen Charlton <gmc(a)esilibrary.com> <gmc(a)esilibrary.com> wrote: Hi, On Tue, Mar 8, 2016 at 12:30 PM, Chris Cormack <chrisc(a)catalyst.net.nz> <chrisc(a)catalyst.net.nz> wrote: I don't think it's fair to push this all on the package manager. If a dev introduces new dependencies that need packaging, it should be their responsibility to make sure this is done. Indeed. I am willing to build *some* packages (and submit them to Debian), but that willingness is decidedly not infinite. The first question that somebody who proposes to add a new dependency should ask themselves is this: is there a way to accomplish the task at hand without adding a new dependency? If not, can the task at hand be accomplished using packages that are already in Debian stable? If not, does the dependency at least have an active third-party ITP (intent to package) in the Debian bug tracker? Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Software, Inc. / Open Your Library email: gmc(a)esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org &http://evergreen-ils.org _______________________________________________ Koha-devel mailing listKoha-devel@lists.koha-community.orghttp://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/ -- -- Liz Rea Catalyst.Net Limited Level 6, Catalyst House, 150 Willis Street, Wellington. P.O Box 11053, Manners Street, Wellington 6142 GPG: B149 A443 6B01 7386 C2C7 F481 B6c2 A49D 3726 38B7 -- --------------------------------------------------------------------------------------------------------------- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Headquarters: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info(a)bywatersolutions.com

2 1

ARG! It really is isnt. It is not a typo.
by Mark Tompsett 08 Mar '16

08 Mar '16

Greetings, $ koha-qa.pl –v 2 –c 4 ... FAIL t/db_dependent/Filter_MARC_ViewPolicy.t OK critic OK forbidden patterns OK pod FAIL spelling isnt ==> isn't OK valid ... $ grep isnt t/db_dependent/Filter_MARC_ViewPolicy.t isnt( $unfiltered_record->field('020'), undef, isnt( $unfiltered_record->field('008'), undef, isnt( $filtered_record->field('020'), undef, isnt( $unfiltered_record->field('020'), undef, isnt( $filtered_record->field('008'), undef, isnt( $unfiltered_record->field('008'), undef, Spelling checks should exclude “isnt(“, right? GPML, Mark Tompsett

3 3

Accidental ban from bugzilla
by Remi MP 08 Mar '16

08 Mar '16

Hi, Here at inLibro we are developping a perl script that will allow us to automatically test bugs for conflicts when their statuses are "New", "Needs Signoff","Signed Off" and also "In Discussion". The script will change the bugs' statuses to "patch doesn't apply" and notify the people involved. My issue right now is that when I started testing my put requests on a bug I created on my own, my account got banned until 15:30 this afternoon because of too many login attempts : Your IP (127.0.0.1) has been locked out of this account until 2016-03-04 15:28 UTC, as you have exceeded the maximum number of login attempts. Is there a way I could get unbanned? I will install bugzilla locally to continue testing, but still I need to be able to access bugzilla today. Thank you!

9 11

Working on Koha interface guidelines
by Owen Leonard 08 Mar '16

08 Mar '16

A while ago I started a page on the wiki for describing common interface patterns in Koha. I've made some additions to it over the last couple of weeks, and I hope to continue to expand it. https://wiki.koha-community.org/wiki/Interface_patterns As you can see it has been long enough since I started that the first screenshots look out of date. Updating them is on my to-do list. However I think the guidelines are still accurate. To a certain extent, this document is both a catalog of how we generally do things in the staff client template and an explanation of my understanding of /why/ we do some things the way we do. If anyone has any questions or suggestions I would love to hear them. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 2

New "renew" shortcut conflicts with previous use of the accesskey attribute
by Owen Leonard 06 Mar '16

06 Mar '16

The staff client uses (albeit inconsistently) the "accesskey" attribute in some dialogs where a Yes/No choice is offered: Yes, delete (Y) / No, don't delete (N) I've just seen that the addition of the renew tab in the header search form assigned "Alt-y" to the renew form. These two shortcuts can't coexist. I personally use the accesskey option when it is available (and when it works), but I imagine not many people do. Is it not worth keeping? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org

2 1

Wiki - Delete/disable user Xdbmsx
by David Nind 04 Mar '16

04 Mar '16

Hi. I accidentally approved a new wiki user last night (I thought I had rejected it, but must have approved it :-( ). Could someone who has permission disable/block the user Xdbmsx as I don't have permissions to do this. The user has also created several pages that need to be deleted. Apologies for this.... David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 m. +64 21 0537 847 | w. +64 4 8906 098

3 3

Patron searching change 'start_wtih' / 'contain' Bug 15252 / 15930
by Nick Clemens 04 Mar '16

04 Mar '16

Hello all, In bug 15252 a change was introduced to fix the problem of too many / irrelevant results when searching for patrons with multi-part names e.g. 'jean paul' 'mac beth' 'le guelec' This change now defaults many searches to 'start_with' and does not split terms for a 'start_with' search. This does not affect members-home.pl, but many other patrons searches request.pl, common/patron_search.tt ... A side effect of this change is that searching for a patrons full name i.e. 'Henry Acevedo' or 'Edna Acosta' returns no results as it is searching for [firstname like 'edna acosta%'] it also prevents searches like 'Ed aco' from finding results. The searches above returned results through 3.18, but 15252 is in 3.20.8 and 3.22.2 and master As we are seeing libraries upgrade to the newer versions we are hearing complaints as this is a big behaviour change from their viewpoint. Jonathan and I have been discussing on Bug 15930 and the options we have so far are: 1/ add a special case to search on firstname and surname (if start_with) 2/ add a pref to default on contains or start_with 3/ let the libraries who want a different behavior modify the default with some JS code 4/ add phrase searching with quotes and split terms otherwise Ideally we want to allow for ease in finding multi part names, but not introduce a change for single part names Thoughts?

2 1

Jenkins status
by Tomas Cohen Arazi 03 Mar '16

03 Mar '16

Hi everyone, on a recent plugin upgrade it seems jenkins configuration lost track of the git repositories each task must follow. I'm fixing it. Sorry for the inconvenience, and thanks Jonathan for reporting it. -- Tomás Cohen Arazi Theke Solutions (http://theke.io) ✆ +54 9351 3513384 GPG: B2F3C15F

1 0

RM update - May 2nd
by Brendan Gallagher 03 Mar '16

03 Mar '16

Hi All - It's been a little bit of time since I've posted. Sorry it's ended up being a long email. ( Easier to say most of this here instead of posting all this into an IRC meeting) ;) Currently the PQA is very low. I encourage all of you to review the needs sign-off page and test some of the wonderful code that many of us have written. Just to remind - the dashboard is a great place to start (everyone should have that one bookmarked - I hope I didn't date myself with that term). http://dashboard.koha-community.org/ - Also here is a link to the Bugzilla page that has the Needs Signoff queue - http://tinyurl.com/h3zdxec . Remember that Bugzilla is only the name of the tracker that we are using - it's not only bugs but also features and other coding needs for Koha. ;) Also a reminder for those that are newer to testing - try out the sandboxes - https://wiki.koha-community.org/wiki/Sandboxes (please remember that you can also ask any of us for help). I know that there are a few things that I need to follow up on for some recent patches that have been pushed. I'm on them and tracking them. Thankfully no one is using Master in production :) As always if I have missed something or I have made a mistake - please let me know and I thank you all for the times you have pointed out a spot I missed (those curly brackets if you know what I mean) Somethings I'd like to concentrate on going forward. 1. Speed. two bugs in general - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15350 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15341 Any and all help is welcome here. Jonathan has been presenting thoughts and comments about this for awhile now - let's all help there. There are some others too and we should all think about this. I feel like we are loading too much with each page. Also dbix::class should be examined. 2. Elastic Search - https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12478 Is the main bug where there are comments, code and thoughts. I think we need a sign-off on this and get this into QA with larger discussions happening. The Main goal for now is that it doesn't break anything with Zebra and we can push this in experimental. There are some good comments and questions on the bug. 3. Staying on top of PQA queue so our developers do not have to spend time rebasing code. I will hopefully maintain that. (sorry for those that have had to rebase so far) 4. Continue to encourage new signoff champions! This is on all of us to encourage and help those that want to do this and have time to do it. We can do it. 5. EDIfact code - needs a signoff. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7736 and https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15630 great work by PTFS-europe and nice job by Kyle Hall on making it plugable so that it works around the standards. (Also I encourage PTFS-europe on submitting more of their code - they are sitting on a few gems right now that will be great for Koha - so if you see their code come it - let's test it). 6. Jenkins - I would like to see Jenkins pass as stable for Master in the near future. I will be spending sometime working on that. I know this turned into a long email. But let's do it! Cheers, 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: Santa Barbara, CA - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com info(a)bywatersolutions.com

1 0