July 2022 - Koha-bugs - lists.koha-community.org

[Bug 28364] New: koha-z3950-responder breaks because of log4perl.conf permissions
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28364 Bug ID: 28364 Summary: koha-z3950-responder breaks because of log4perl.conf permissions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com To reproduce: 1. Create a Koha instance: $ koha-create --create-db test 2. Initiate all the things 3. Enable and start the z3950 responder $ koha-z3950-responder --enable test $ koha-z3950-responder --start test 4. Try doing some search: $ yaz-client localhost:2100 => FAIL: you get: Connecting...OK. Sent initrequest. Target closed connection Z> quit See you later, alligator. => FAIL: No warning or anything on the logs 5. Stop the daemon $ koha-z3950-responder --stop test 6. Run it manually: $ PERL5LIB=/usr/share/koha/lib KOHA_CONF=/etc/koha/sites/test/koha-conf.xml /usr/bin/perl /usr/share/koha/bin/z3950_responder.pl -c /etc/koha/sites/test/z3950 -u test-koha -p /var/run/koha/test/z3950-responder.pid -d test-koha-z3950 7. Repeat the 4, on a separate terminal (no daemon mode this time) => FAIL: You get: Cannot open /etc/koha/sites/test/log4perl.conf (Permission denied) at /usr/share/perl5/Log/Log4perl/Config/BaseConfigurator.pm line 51. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 21375] New: NCIP service for Koha
by bugzilla-daemon＠bugs.koha-community.org 23 Sep '22

23 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21375 Bug ID: 21375 Summary: NCIP service for Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: amitddng135(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org NCIP service for Koha -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 30497] New: Constraint old_reserves_ibfk_4 should be SET NULL instead of CASCADE
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30497 Bug ID: 30497 Summary: Constraint old_reserves_ibfk_4 should be SET NULL instead of CASCADE Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org kohastructure defines it as SET NULL but this upgrade 'decided' differently: $DBversion = "3.23.00.055"; ALTER TABLE old_reserves ADD CONSTRAINT `old_reserves_ibfk_4` FOREIGN KEY (`itemtype`) REFERENCES `itemtypes` (`itemtype`) ON DELETE CASCADE ON UPDATE CASCADE; I think we should go for SET NULL here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 30490] New: Should deleting a parent itemtype be CASCADING?
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30490 Bug ID: 30490 Summary: Should deleting a parent itemtype be CASCADING? Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Database Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org This is a sync issue between schema and upgrades. MASTER structure: CONSTRAINT `itemtypes_ibfk_1` FOREIGN KEY (`parent_type`) REFERENCES `itemtypes` (`itemtype`) ON DELETE CASCADE ON UPDATE CASCADE $DBversion = '20.06.00.022'; ALTER TABLE itemtypes ADD CONSTRAINT itemtypes_ibfk_1 FOREIGN KEY (parent_type) REFERENCES itemtypes (itemtype) NOTE: When you do not add CASCADE, you fallback to RESTRICT ! Main question is now: Which is right? Should the delete be cascading or not? I would opt for RESTRICT here. A pragmatical choice too; deleting item types will normally not be done so much :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 31055] New: Move koha-functions to /usr/sbin instead of koha/bin
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31055 Bug ID: 31055 Summary: Move koha-functions to /usr/sbin instead of koha/bin Change sponsored?: --- Product: Koha Version: unspecified 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 For a long time I am copying koha-functions.sh to /usr/share/koha/bin, since that is the location that the koha-* scripts expect it to be. It would be easier to put it in sbin too. Please tell me if there are valid legitimate reasons to do not so. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 28666] New: Locale::XGettext::TT2 shows as missing in about.pl page
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28666 Bug ID: 28666 Summary: Locale::XGettext::TT2 shows as missing in about.pl page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com Created attachment 122597 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=122597&action=e… pic the Locale::XGettext::TT2 perl module is installed via the debian libtemplate-plugin-gettext-perl package, but still shows as uninstalled in about.pl # dpkg -L libtemplate-plugin-gettext-perl | grep -i tt2 /usr/bin/xgettext-tt2 /usr/share/man/man1/xgettext-tt2.1p.gz /usr/share/man/man3/Locale::XGettext::TT2.3pm.gz /usr/share/perl5/Locale/XGettext/TT2.pm /usr/share/perl5/Locale/XGettext/TT2.pod -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 24189] New: Can't login to SIP2
by bugzilla-daemon＠bugs.koha-community.org 22 Sep '22

22 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24189 Bug ID: 24189 Summary: Can't login to SIP2 Change sponsored?: --- Product: Koha Version: 18.11 Hardware: HP OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: hamsiah(a)interxs.com.my QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Created attachment 96081 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=96081&action=ed… Sip testing tool return value '0' which indicate as login failure This problem occurred when we trying to shut down the server. But then after we start up the server, the SIP2 connection was failed. This is the log from the selfcheck machine after start the server. It's showing that the connection is connected but the login seems failed because of the status indicate as '0'. Please refer attachment for clearer view. 21/11/2019 05:00:05 ILSport Error - The attempt to connect timed out 21/11/2019 05:00:26 ILSport Error - The attempt to connect timed out 21/11/2019 05:00:47 ILSport Error - The attempt to connect timed out 21/11/2019 05:01:08 ILSport Error - The attempt to connect timed out 21/11/2019 05:01:44 ILSport Connected 21/11/2019 05:01:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5 21/11/2019 05:01:45 From <---- ILS 940AY0AZFDFE 21/11/2019 05:01:45 To-->ILS 9901002.00AY1AZFCA7 21/11/2019 05:01:46 ILSport Disconnected by remote host 21/11/2019 05:03:44 ILSport Connected 21/11/2019 05:03:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0 21/11/2019 05:03:45 From <---- ILS 940AY5AZFDF 21/11/2019 05:03:45 To-->ILS 9901002.00AY6AZFCA2 21/11/2019 05:03:46 ILSport Disconnected by remote host 21/11/2019 05:05:44 ILSport Connected 21/11/2019 05:05:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5 21/11/2019 05:05:45 From <---- ILS 940AY0AZFDFE 21/11/2019 05:05:45 To-->ILS 9901002.00AY1AZFCA7 21/11/2019 05:05:46 ILSport Disconnected by remote host 21/11/2019 05:08:05 ILSport Error - The attempt to connect timed out 21/11/2019 05:08:26 ILSport Error - The attempt to connect timed out 21/11/2019 05:08:35 ILSport Error - Connection is forcefully rejected 21/11/2019 05:08:36 ILSport Connected 21/11/2019 05:08:36 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0 21/11/2019 05:08:38 From <---- ILS 940AY5AZFDF9 21/11/2019 05:08:38 To-->ILS 9901002.00AY6AZFCA2 21/11/2019 05:08:38 ILSport Disconnected by remote host 21/11/2019 05:09:44 ILSport Connected 21/11/2019 05:09:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5 21/11/2019 05:09:45 From <---- ILS 940AY0AZFDFE 21/11/2019 05:09:45 To-->ILS 9901002.00AY1AZFCA7 21/11/2019 05:09:46 ILSport Disconnected by remote host 21/11/2019 05:11:44 ILSport Connected 21/11/2019 05:11:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0 21/11/2019 05:11:45 From <---- ILS 940AY5AZFDF9 21/11/2019 05:11:45 To-->ILS 9901002.00AY6AZFCA2 21/11/2019 05:11:46 ILSport Disconnected by remote host 21/11/2019 05:13:44 ILSport Connected 21/11/2019 05:13:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5 21/11/2019 05:13:45 From <---- ILS 940AY0AZFDFE 21/11/2019 05:13:45 To-->ILS 9901002.00AY1AZFCA7 21/11/2019 05:13:46 ILSport Disconnected by remote host 21/11/2019 05:15:44 ILSport Connected 21/11/2019 05:15:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0 21/11/2019 05:15:45 From <---- ILS 940AY5AZFDF9 21/11/2019 05:15:45 To-->ILS 9901002.00AY6AZFCA2 21/11/2019 05:15:46 ILSport Disconnected by remote host 21/11/2019 05:17:44 ILSport Connected 21/11/2019 05:17:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY0AZF1A5 21/11/2019 05:17:45 From <---- ILS 940AY0AZFDFE 21/11/2019 05:17:45 To-->ILS 9901002.00AY1AZFCA7 21/11/2019 05:17:46 ILSport Disconnected by remote host 21/11/2019 05:19:44 ILSport Connected 21/11/2019 05:19:44 To-->ILS 9300CNselfcheckp1|COS3lfch3ckp1|CP20000|AY5AZF1A0 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 28665] New: perl Text::CSV::Unicode module is required, but missing
by bugzilla-daemon＠bugs.koha-community.org 21 Sep '22

21 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28665 Bug ID: 28665 Summary: perl Text::CSV::Unicode module is required, but missing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org CC: mtj(a)kohaaloha.com Created attachment 122596 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=122596&action=e… pic the perl Text::CSV::Unicode module is required, but missing we should install it during Koha installation -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 21458] New: Messaging preferences extension: Hold filled digest
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '22

20 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21458 Bug ID: 21458 Summary: Messaging preferences extension: Hold filled digest Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: black23(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Hi, if borrowers use "Holds to pull" usualy librarians prepare more than one document. Now Koha sends x notices for every hold. It would be better to send digest with all holds together in one e-mail or SMS. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 31120] New: Items will renew for zero ( 0 ) days if renewalperiod is blank/empty value
by bugzilla-daemon＠bugs.koha-community.org 20 Sep '22

20 Sep '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31120 Bug ID: 31120 Summary: Items will renew for zero ( 0 ) days if renewalperiod is blank/empty value Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com If the rule renewalperiod is the blank empty string instead of being null/undefined or non-existant, Koha will interpret the renewal period as being zero days instead of falling back to the issuelength rule. It makes sense to me that a literal 0 here should make it renew for zero days even though that is nonsensical. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21