[koha-commits] main Koha release repository branch 3.12.x updated. v3.12.08-19-g72fdbbd

Git repo owner gitmaster at git.koha-community.org
Wed Jan 15 18:27:41 CET 2014


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "main Koha release repository".

The branch, 3.12.x has been updated
       via  72fdbbd6633a6b7fd2757b429339bcacc2a43f7a (commit)
       via  d7a7336dff3e33d566b2c85efd689963ef7826de (commit)
       via  ccbaa6f3c42ece752a7c7d6d5c4142ea57d6fd1d (commit)
      from  92d8d9b9c8509828b51c0c7ea8d952e1d065140a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 72fdbbd6633a6b7fd2757b429339bcacc2a43f7a
Author: Robin Sheat <robin at catalyst.net.nz>
Date:   Tue Nov 19 15:26:02 2013 +1300

    Bug 10735: prevent koha-dump from aborting if backupdir undefined
    
    Older versions of Koha didn't have <backupdir>...</backupdir> defined in
    koha-conf.xml. The koha-dump script is aware of this, and checks to see
    if it's there. However, if it's not, xmlstarlet returns a non-0 error
    code which causes the script to abort due to running under set -e.
    
    Test plan:
     * Remove backupdir from koha-conf.xml
     * Run koha-dump, notice that it doesn't do backups
     * Apply patch
     * Run koha-dump again, notice that it does do backups
    
    Signed-off-by: Tomas Cohen Arazi <tomascohen at gmail.com>
    The fallback method works as described. It might be made more robust
    like checking for dir existence (thinking of older instances upgrades).
    But it certainly belongs to another bug report.
    
    Signed-off-by: Jonathan Druart <jonathan.druart at biblibre.com>
    As Tomas said, it would be better to alert the user if the backupdir tag
    does not exist (or contains a nonexistent directory) in the config file.
    
    Signed-off-by: Galen Charlton <gmc at esilibrary.com>
    (cherry picked from commit 266f2a3a9f3d67fed0e0b35d267419a901345b92)
    Signed-off-by: Fridolin SOMERS <fridolin.somers at biblibre.com>
    (cherry picked from commit de1344c2759631e1a8d505151630f160ebdab768)
    Signed-off-by: Tomas Cohen Arazi <tomascohen at gmail.com>

commit d7a7336dff3e33d566b2c85efd689963ef7826de
Author: Kyle M Hall <kyle at bywatersolutions.com>
Date:   Tue Dec 17 16:04:10 2013 -0500

    Bug 11410: ensure cataloging search finds results for searches with ampersands
    
    When QueryParser is off, the cataloging search is passing the incorrect
    variable to SimpleSearch.  I'm sure this is causing other issues, but
    the one I have identified is that any searches with an "&" in them
    return no results.  This patch corrects the bug.
    
    Test Plan:
    1) Catalog a new record titled "Cats & Dogs"
    2) Rebuild your zebra index so this record is indexed
    3) Browse to cataloguing/addbooks.pl
    4) Search for "Cats & Dogs"
    5) Notice you get no results
    6) Apply this patch
    7) Repeat the search
    8) Notice your result now shows up!
    
    Signed-off-by: Heather Braum <hbraum at nekls.org>
    Signed-off-by: Suzanne Fayle <sfayle at roseman.edu>
    Signed-off-by: Katrin Fischer <Katrin.Fischer.83 at web.de>
    This works as described, passes all tests and QA script.
    Note: Because $query = $builtquery when the QueryParser is used,
    this problem is only visible when UseQueryParser is set to "Don't try".
    
    Signed-off-by: Galen Charlton <gmc at esilibrary.com>
    (cherry picked from commit 2a4e193c242372f488892591a72752dfd4ffb138)
    Signed-off-by: Fridolin SOMERS <fridolin.somers at biblibre.com>
    (cherry picked from commit 0c500f463001db06c8c1f72f8b81c8edde6487d7)
    Signed-off-by: Tomas Cohen Arazi <tomascohen at gmail.com>

commit ccbaa6f3c42ece752a7c7d6d5c4142ea57d6fd1d
Author: Fridolyn SOMERS <fridolyn.somers at biblibre.com>
Date:   Wed Oct 30 10:28:49 2013 +0100

    Bug 11166: make library filter in funds administration page more precise
    
    In funds administration, admin/aqbudgets.pl, there is a combobox for
    filtering by library code.
    
    The bug is that the filter uses a pattern match  instead of equals :
      next unless $budget->{budget_branchcode} =~ m/$filter_budgetbranch/;
    
    In this case, if there is a library with code '1' and one with code '12',
    filtering by library '1' will also show funds of library '12'.
    
    Test plan :
    - Create a library with code '1' and one with code '12'
    - Create funds in both libraries
    - Go to admin/aqbudgets.pl
    - Filter by branch '12'
    => You see only funds of this library
    - Filter by branch '1'
    => You see only funds of this library
    
    Signed-off-by: Marcel de Rooy <m.de.rooy at rijksmuseum.nl>
    Signed-off-by: Kyle M Hall <kyle at bywatersolutions.com>
    Passes koha-qa.pl, works as advertised
    
    Signed-off-by: Galen Charlton <gmc at esilibrary.com>
    (cherry picked from commit 484d1490925d736f99a430a6933c96e42ea4e768)
    Signed-off-by: Fridolin SOMERS <fridolin.somers at biblibre.com>
    (cherry picked from commit 64c79561bbabf6476fb72c27435789f4dd19180a)
    Signed-off-by: Tomas Cohen Arazi <tomascohen at gmail.com>

-----------------------------------------------------------------------

Summary of changes:
 admin/aqbudgets.pl       |    2 +-
 cataloguing/addbooks.pl  |    2 +-
 debian/scripts/koha-dump |    2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)


hooks/post-receive
-- 
main Koha release repository


More information about the koha-commits mailing list