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, master has been updated
       via  3640130d1fbc49ddc2cc4baef53a4c4d7fea76bf (commit)
       via  cb432e7f522f2f052d561dad3b36bc97ca7868a4 (commit)
       via  e98af5828a56b52426ae7aa12d1c85e4f9fb41d2 (commit)
       via  9e1fa801d6f1ff718d8689c855483b8b9c735a9f (commit)
       via  445b0cb8b595136afdebaee2db3bc768b42b445b (commit)
       via  811bee9bce57e67fd22562b3bb62397335b4eeb5 (commit)
      from  49e30bc67d91f300df2efd9b7a2cf0526221fb96 (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 3640130d1fbc49ddc2cc4baef53a4c4d7fea76bf
Author: Marcel de Rooy <m.de.r...@rijksmuseum.nl>
Date:   Fri May 17 07:36:17 2019 +0000

    Bug 22929: Allow SCI/SCO logins independent of GDPR_Policy
    
    This patch makes Auth skip the GDPR policy check when get_template_and_user
    is called for sci/sco (self checkin, checkout).
    I do not really like the change in this form but the nature of self checkin
    and checkout kind of dictate it (double hack).
    I wanted to add a test but since that asks for mocking CGI, checkauth, etc.
    the time needed for that is just too much for this simple change.
    
    Test plan:
    Enable GDPR_Policy and self checkin/checkout.
    Verify that using patrons without consent is not blocking sci/sco.
    
    Signed-off-by: Marcel de Rooy <m.de.r...@rijksmuseum.nl>
    Signed-off-by: Kyle M Hall <k...@bywatersolutions.com>
    Signed-off-by: Tomas Cohen Arazi <tomasco...@theke.io>
    Signed-off-by: Martin Renvoize <martin.renvo...@ptfs-europe.com>

commit cb432e7f522f2f052d561dad3b36bc97ca7868a4
Author: Tomas Cohen Arazi <tomasco...@theke.io>
Date:   Fri Sep 6 15:51:26 2019 -0300

    Bug 23404: (QA follow-up) Minor fix
    
    Signed-off-by: Tomas Cohen Arazi <tomasco...@theke.io>
    Signed-off-by: Martin Renvoize <martin.renvo...@ptfs-europe.com>

commit e98af5828a56b52426ae7aa12d1c85e4f9fb41d2
Author: Fridolin Somers <fridolin.som...@biblibre.com>
Date:   Wed Jul 31 10:59:37 2019 +0200

    Bug 23404: Change UT calls
    
    Run prove t/db_dependent/Circulation/TooMany.t
    Tests are OK
    
    Signed-off-by: Kyle M Hall <k...@bywatersolutions.com>
    Signed-off-by: Tomas Cohen Arazi <tomasco...@theke.io>
    Signed-off-by: Martin Renvoize <martin.renvo...@ptfs-europe.com>

commit 9e1fa801d6f1ff718d8689c855483b8b9c735a9f
Author: Fridolin Somers <fridolin.som...@biblibre.com>
Date:   Wed Jul 31 15:56:22 2019 +0200

    Bug 23404: fix Circulation::TooMany error on itemtype when at biblio level
    
    Circulation::TooMany gets itemtype from $item var beeing a Koha::Item 
unblessed.
    When itemtype is at biblio level, calling $item->{'itemtype'} is wrong.
    
    Test plan :
    1) On a catalog with itemtype at item level : pref item-level_itypes=1
    2) Create a biblio record with itemtype BOOK
    3) Create an item on this biblio record with itemtype BOOK
    4) Delete all issuing rules
    5) Create a issuing rule with itemtype BOOK, any catagorie, any branch
    6) Check-out the item
    7) => Checkout is allowed
    8) Check-in item
    9) Change itemtype at biblio level : pref item-level_itypes=0
    10) Check-out the item
    11) => Checkout is not allowed
        You see message "No circulation rule is defined for this patron and 
itemtype combination"
    
    Signed-off-by: Kyle M Hall <k...@bywatersolutions.com>
    Signed-off-by: Tomas Cohen Arazi <tomasco...@theke.io>
    Signed-off-by: Martin Renvoize <martin.renvo...@ptfs-europe.com>

commit 445b0cb8b595136afdebaee2db3bc768b42b445b
Author: Fridolin Somers <fridolin.som...@biblibre.com>
Date:   Wed Jul 31 11:21:14 2019 +0200

    Bug 23404: add UT to show bug
    
    Run prove t/db_dependent/Circulation/TooMany.t
    It fails on :
        #   Failed test 'We are only allowed one, and we have one (itemtype on 
biblioitem)'
        #   at t/db_dependent/Circulation/TooMany.t line 547.
        #     Structures begin differing at:
        #          $got->{reason} = 'NO_RULE_DEFINED'
        #     $expected->{reason} = 'TOO_MANY_CHECKOUTS'
    
    Signed-off-by: Kyle M Hall <k...@bywatersolutions.com>
    Signed-off-by: Tomas Cohen Arazi <tomasco...@theke.io>
    Signed-off-by: Martin Renvoize <martin.renvo...@ptfs-europe.com>

commit 811bee9bce57e67fd22562b3bb62397335b4eeb5
Author: Caroline Cyr La Rose <carol...@inlibro.com>
Date:   Fri Aug 16 14:28:59 2019 -0400

    Bug 23353: ACQ framework makes fr-CA web installer explode
    
    This patch removes the standalone ACQ framework SQL file in the fr-CA
    directory and adds the ACQ framework creation SQL in the default
    framework file, as it is in other languages.
    
    Signed-off-by: Kyle M Hall <k...@bywatersolutions.com>
    Signed-off-by: Tomas Cohen Arazi <tomasco...@theke.io>
    Signed-off-by: Martin Renvoize <martin.renvo...@ptfs-europe.com>

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

Summary of changes:
 C4/Auth.pm                                         |    3 +-
 C4/Circulation.pm                                  |   13 +--
 .../obligatoire/marc21_framework_DEFAULT.sql       |   56 +++++++++++
 .../obligatoire/marc21_sample_acq_framework.sql    |   56 -----------
 .../obligatoire/marc21_sample_acq_framework.txt    |    1 -
 t/db_dependent/Circulation/TooMany.t               |  106 +++++++++++---------
 6 files changed, 124 insertions(+), 111 deletions(-)
 delete mode 100644 
installer/data/mysql/fr-CA/marcflavour/marc21/obligatoire/marc21_sample_acq_framework.sql
 delete mode 100644 
installer/data/mysql/fr-CA/marcflavour/marc21/obligatoire/marc21_sample_acq_framework.txt


hooks/post-receive
-- 
main Koha release repository
_______________________________________________
koha-commits mailing list
koha-commits@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-commits

Reply via email to