August 2017 - Koha-bugs - lists.koha-community.org

[Bug 17608] New: Fix behaviour of bulkmarcimport.pl -insert
by bugzilla-daemon＠bugs.koha-community.org 26 Feb '18

26 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17608 Bug ID: 17608 Summary: Fix behaviour of bulkmarcimport.pl -insert Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz According to the POD in bulkmarcimport.pl: -insert if set, only insert when possible This works as expected for bibliographic records, if -insert is specified and a records already exists (based on the criteria specified by the -match option), the record is skipped and no record is inserted. But I do find the behaviour related to items a bit surprising. Even if the record is skipped and not inserted, any items attached to the record in the file that is being imported is attached to the matching record. I would expect items to be ignored if the record exists and is skipped. So the question is: is this behaviour a bug or a feature? Even if it is a bug, I guess we must assume that some libraries out there are relying on the current behaviour of bulkmarcimport.pl, so that the best way to get the behaviour I expect is to add another command line switch, to ignore items for matching records. This way existing users will not get nasty surprises and I will get the behaviour I expect. Opinions? -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 17383] New: Build debian package failed
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '18

23 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17383 Bug ID: 17383 Summary: Build debian package failed Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.stastny(a)teamlibrary.cz QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net When trying to build a Debian package from git with build-git-snapshot, dependencies fail. Unable to resolve dependencies! Giving up... The following NEW packages will be installed: ca-certificates{a} libalgorithm-checkdigits-perl{a} libanyevent-http-perl{a} libanyevent-perl{a} libarchive-zip-perl{a} libauthen-cas-client-perl{a} libbiblio-endnotestyle-perl{a} libbusiness-isbn-data-perl{a} libbusiness-isbn-perl{a} libcache-fastmmap-perl{a} libcache-memcached-fast-perl{a} libcache-perl{a} libcgi-session-driver-memcached-perl{a} libcgi-session-perl{a} libcgi-session-serialize-yaml-perl{a} libclass-accessor-perl{a} libclass-factory-util-perl{a} libcommon-sense-perl{a} libencode-locale-perl{a} libfile-listing-perl{a} libfile-nfslock-perl{a} libheap-perl{a} libhtml-parser-perl{a} libhtml-tagset-perl{a} libhtml-tree-perl{a} libhttp-cookies-perl{a} libhttp-date-perl{a} libhttp-message-perl{a} libhttp-negotiate-perl{a} libio-socket-ssl-perl{a} libio-string-perl{a} liblwp-mediatypes-perl{a} liblwp-protocol-https-perl{a} libnet-http-perl{a} libnet-ssleay-perl{a} libssl1.0.0{a} libsub-name-perl{a} liburi-perl{a} libwww-perl{a} libwww-robotrules-perl{a} libxml-libxml-perl{a} libxml-namespacesupport-perl{a} libxml-sax-base-perl{a} libxml-sax-perl{a} libxml2{a} libyaml-syck-perl{a} netbase{a} openssl{a} ucf{a} 0 packages upgraded, 49 newly installed, 0 to remove and 0 not upgraded. Need to get 6299 kB of archives. After unpacking 16.0 MB will be used. Abort. E: pbuilder-satisfydepends failed. I: Copying back the cached apt archive contents I: unmounting dev/pts filesystem I: unmounting run/shm filesystem I: unmounting proc filesystem I: cleaning the build env I: removing directory /var/cache/pbuilder/build//24915 and its subdirectories Command 'pdebuild --buildresult /root/debian' returns an error (256) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 17250] New: Koha::AuthorisedValues - Remove GetAuthValCode
by bugzilla-daemon＠bugs.koha-community.org 23 Feb '18

23 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17250 Bug ID: 17250 Summary: Koha::AuthorisedValues - Remove GetAuthValCode Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 15879] New: Allow multiple plugin directories to be defined in koha-conf.xml
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '18

22 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15879 Bug ID: 15879 Summary: Allow multiple plugin directories to be defined in koha-conf.xml Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be very useful to be able to define multiple plugin directories in the Koha conf file. This would allow for ease of plugin development so that each plugin installed can live in its own git repository. For compatibility, the first plugindir instance defined should be the one used for uploading plugins via the web interface. -- You are receiving this mail because: You are watching all bug changes.

1 21

[Bug 19018] New: Can we make XSLT_Handler a little bit less verbose ?
by bugzilla-daemon＠bugs.koha-community.org 22 Feb '18

22 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19018 Bug ID: 19018 Summary: Can we make XSLT_Handler a little bit less verbose ? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org As reported on bug 17807, XSLT_Handler reports that a XSLT file is not found for each record it wants to process (running oai.pl). Additionally, we also have: Can't locate object method "nodeType" via package "<?xml version="1.0" encoding="UTF-8"?> [ And a complete MARC record dump. ] " (perhaps you forgot to load "<?xml version="1.0" encoding="UTF-8"?> [ Same MARC record dump again ] "?) at /usr/share/perl5/HTTP/OAI/Encapsulation.pm line 68. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 18198] New: MARC21: Further improve handling of 5XX$u in GetMarcNotes
by bugzilla-daemon＠bugs.koha-community.org 16 Feb '18

16 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18198 Bug ID: 18198 Summary: MARC21: Further improve handling of 5XX$u in GetMarcNotes Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This actually is a follow-up of bug 14306. That report only touched field 555 in MARC21. But a lot of other 5XX fields have a $u subfield for URIs. This patch generalizes the change made for 555 and extends it to all 5XX $u. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 16365] New: Selectively introduce GetMarcStructure() "unsafe" variant for better performance
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '18

13 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16365 Bug ID: 16365 Summary: Selectively introduce GetMarcStructure() "unsafe" variant for better performance Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org GetMarcStructure() currently uses Koha::Cache in the "safe" mode (returning deep copy of the result data structure by default), which causes numerous performance issues in many Koha scripts. Switching it to the "unsafe" mode globally (2nd patch from Bug 16140) resolves those issues, but ensuring that it is regression-free (and that it will stay that way in the future) is far from easy. This patch proposes a bit more manageable solution, it introduces a possibility to use "unsafe" variant selectively (only in those places in the code where GetMarcStructure() is called repetively). That way, amount of the code that needs to be audited for possible problems gets vastly reduced, without any performance trade-offs. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 18794] New: OAI/Server.t fails on slow servers
by bugzilla-daemon＠bugs.koha-community.org 13 Feb '18

13 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18794 Bug ID: 18794 Summary: OAI/Server.t fails on slow servers Change sponsored?: --- Product: Koha Version: 17.05 Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 14939 https://jenkins.koha-community.org/job/Koha_Master_D8/198/consoleFull # Failed test 'ListMetadataFormats' # at t/db_dependent/OAI/Server.t line 150. # Structures begin differing at: # $got->{responseDate} = '2017-06-12T14:31:51Z' # $expected->{responseDate} = '2017-06-12T14:31:50Z' # PARAM:--- # verb: ListMetadataFormats # EXPECTED:--- # ListMetadataFormats: # metadataFormat: # - metadataNamespace: http://www.openarchives.org/OAI/2.0/oai_dc/ # metadataPrefix: oai_dc # schema: http://www.openarchives.org/OAI/2.0/oai_dc.xsd # - metadataNamespace: http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim # metadataPrefix: marc21 # schema: http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd # - metadataNamespace: http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim # metadataPrefix: marcxml # schema: http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd # request: http://localhost # responseDate: 2017-06-12T14:31:50Z # xmlns: http://www.openarchives.org/OAI/2.0/ # xmlns:xsi: http://www.w3.org/2001/XMLSchema-instance # xsi:schemaLocation: http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd # RESPONSE:--- # ListMetadataFormats: # metadataFormat: # - metadataNamespace: http://www.openarchives.org/OAI/2.0/oai_dc/ # metadataPrefix: oai_dc # schema: http://www.openarchives.org/OAI/2.0/oai_dc.xsd # - metadataNamespace: http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim # metadataPrefix: marc21 # schema: http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd # - metadataNamespace: http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim # metadataPrefix: marcxml # schema: http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd # request: http://localhost # responseDate: 2017-06-12T14:31:51Z # xmlns: http://www.openarchives.org/OAI/2.0/ # xmlns:xsi: http://www.w3.org/2001/XMLSchema-instance # xsi:schemaLocation: http://www.openarchives.org/OAI/2.0/ http://www.openarchives.org/OAI/2.0/OAI-PMH.xsd # Looks like you failed 1 test of 28. [14:32:04] t/db_dependent/OAI/Server.t ............................... Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14939 [Bug 14939] OAI Server classes must be modularized -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 19230] New: Warn when deleting a course in course reserves
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '18

12 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19230 Bug ID: 19230 Summary: Warn when deleting a course in course reserves Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org To reproduce: 1) Ensure UseCourseReserves is enabled 2) Go to Course Reserves, create a course 3) Delete course 4) Notice warn CGI::param called in list context from package CGI::Compile::ROOT::home_vagrant_kohaclone_course_reserves_mod_course_2epl line 43, this can lead to vulnerabilities. See the warning in "Fetching the value or values of a single named parameter" at /usr/share/perl5/CGI.pm line 436. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 18988] New: OPAC password not going by autoemailprimaryaddress preference
by bugzilla-daemon＠bugs.koha-community.org 12 Feb '18

12 Feb '18

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18988 Bug ID: 18988 Summary: OPAC password not going by autoemailprimaryaddress preference Change sponsored?: --- Product: Koha Version: 16.05 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: tejoskumar(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org The way OPAC password recovery is working with koha 16.05 as understood by me is below: 1. We need to enter userid(Loginid) 2. Enter email - any email associated with the patron in the borrower table 3. Verifying email associated with userid(Loginid) in all email fields of that patron 4. The mail is being sent to the particular mailid entered in password recovery form(if it is matching) As per the setting in patron preferences, iam understanding that, if the mailid associated with userid is verified and matching, then the mail trigger should be based on the autoemailprimaryaddress preference and not the mailid entered in the password recovery form. Password recovery form is not going by the patron preference setting though other notices are using that preference. I think this should be rectified. Please correct me if iam understanding this incorrectly. -- You are receiving this mail because: You are watching all bug changes.

1 8