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

KohaCon11, a visa for India, but which one
by Paul Poulain 08 Aug '11

08 Aug '11

Hi Kousthuba & al, I think many countries are like France and need a visa to come to the KohaCon. What kind of visa should we request ? A tourist visa, and we don't say we're coming to a conference ? A conference visa (can you provide the requested invitation to the conference ?) ? a business visa (I don't think so: it's not related to any topic for the business visa) Thanks for your feedback. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

2 1

Re: [Koha-devel] Patch format
by Chris Cormack 07 Aug '11

07 Aug '11

On 1 August 2011 10:17, Edgar Fuß <ef(a)math.uni-bonn.de> wrote: >> If you use git format-patch and then git send-email to send it to the >> koha-patches mailing list. > Oh well, I'll try this tomorrow. It's past midnight in my timezone now. > >> that's not as nessecary the mailing list is the main place > Is that information somehow pushed back to bugzilla? Or how do I know someone already posted a patch to the list for a bug I would start to work on? > >> This is the way the other 147 developers do it > I don't quite think I would regard myself a Koha developer. > I'm sort of hopping from one Open Source project to another. So it's sometimes difficult for me to get accustomed to the project's bug reporting policy. However, Koha seems to be the first project I met preferring git patches git format-patch'ed git send-email'ed to a patches list. I'll try to get accustomed to that. Here are some good resources http://wiki.koha-community.org/wiki/Version_Control_Using_Git http://wiki.koha-community.org/wiki/Set_an_email_alias_for_Koha_patches http://wiki.koha-community.org/wiki/Sign_off_on_patches http://wiki.koha-community.org/wiki/Bug-enhancement-patch_Workflow Chris

5 11

eval "use Some::Module"
by Edgar Fuß 07 Aug '11

07 Aug '11

There are several places in Koha (I blindly copied one of them myself) that do eval "use Some::Module" without checking $@ afterwards. Not being a Perl expert myself, I thought that was some clever thing I didn't understand. I lately asked my personal Perl guru about it, and he replied is was plain broken. In fact, it leads to strange errors when sending an email to a bookseller fails. The relevant files are acqui/addorderiso2709.pl, acqui/basketgroup.pl and tools/inventory.pl. There is one correct use in t/db_dependent/lib/KohaTest.pm There is also this strange use of ``eval require'': BEGIN { # find Koha's Perl modules # test carefully before changing this use FindBin; eval { require "$FindBin::Bin/kohalib.pl" }; } all over the place. I can't make any sense out of this.

2 1

One final question ... mapping holdings .... 4 holdings??
by Hartman, David W. - GBTS Library 05 Aug '11

05 Aug '11

I am almost there .. I read online to use these mappings for local holdings (using MARCEDIT) .... when I do I get 4 holdings (see below) Barcode is mapped to 952$p Call number 952$o Item Type Code 952$y Location (branch) code 952$b From: David Hartman [mailto:hartmad@hotmail.com] Sent: Friday, August 05, 2011 5:27 PM To: Hartman, David W. - GBTS Library Subject: 4 holdings?? JUnit in action by Tahchiev, Peter</cgi-bin/koha/opac-search.pl?q=au:Tahchiev,%20Peter%20> Series: . 1Physical details: xxiv, 360 p. : ill. ; 24 cm.Subject(s): 1. JAVA (COMPUTER PROGRAM LANGUAGE)</cgi-bin/koha/opac-search.pl?q=su:1.%20JAVA%20COMPUTER%20PROGRAM%20LANGUAGE> | 2. OBJECT-ORIENTED PROGRAMMING (COMPUTER SCIENCE )</cgi-bin/koha/opac-search.pl?q=su:2.%20OBJECT-ORIENTED%20PROGRAMMING%20COMPUTER%20SCIENCE%20>Year: 2011 Tags from this library: No tags from this library for this title. * Holdings ( 4 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#holdings> * Title Notes</cgi-bin/koha/opac-detail.pl?biblionumber=12601#descriptions> * Comments ( 0 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#comments> Item type Location Call Number Status Date Due BT Library - FL Available 005.7 JAVA H18 (Browse Shelf</cgi-bin/koha/opac-detail.pl?biblionumber=12601&shelfbrowse_itemnumber=37513#shelfbrowser>) Available Available [/opac-tmpl/prog/itemtypeimg/bridge/book.gif] Books Available JUnit in action by Tahchiev, Peter</cgi-bin/koha/opac-search.pl?q=au:Tahchiev,%20Peter%20> Series: . 1Physical details: xxiv, 360 p. : ill. ; 24 cm.Subject(s): 1. JAVA (COMPUTER PROGRAM LANGUAGE)</cgi-bin/koha/opac-search.pl?q=su:1.%20JAVA%20COMPUTER%20PROGRAM%20LANGUAGE> | 2. OBJECT-ORIENTED PROGRAMMING (COMPUTER SCIENCE )</cgi-bin/koha/opac-search.pl?q=su:2.%20OBJECT-ORIENTED%20PROGRAMMING%20COMPUTER%20SCIENCE%20>Year: 2011 Tags from this library: No tags from this library for this title. * Holdings ( 4 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#holdings> * Title Notes</cgi-bin/koha/opac-detail.pl?biblionumber=12601#descriptions> * Comments ( 0 )</cgi-bin/koha/opac-detail.pl?biblionumber=12601#comments> Item type Location Call Number Status Date Due BT Library - FL Available 005.7 JAVA H18 (Browse Shelf</cgi-bin/koha/opac-detail.pl?biblionumber=12601&shelfbrowse_itemnumber=37513#shelfbrowser>) Available Available [/opac-tmpl/prog/itemtypeimg/bridge/book.gif] Books Available

2 4

Is there any way to delete recently added patrons?
by Hartman, David W. - GBTS Library 05 Aug '11

05 Aug '11

I made a mistake on a recent import of patrons that affected hundreds of records .. It looks like recently added patrons cannot be deleted .. So .. Can I delete the entire contents of the data file and start over with csv import. How can this be done? David W. Hartman Global Business Technology Strategy Library Team Disney 336N 407 828 4250 (8-222) FAX 407 828 4868

2 1

Removing sysprefs from language related installer ?
by Paul Poulain 05 Aug '11

05 Aug '11

Hello koha-devel, Since Koha 3.4, the text displayed for the sysprefs is stored in .pref file. It means the sysprefs are no more "language dependant". One of the pain one face when a syspref must be added into Koha is that each language file must be updated, and there are now many (welcome to the new ES one !) It also means that is someone forget to add a syspref into a language, then this language will have incomplete syspref in the DB when installed. Here is what I propose: * remove all syspref SQL files from language (installer/data/mysql/LANGUAGE/mandatory/syspref.sql -or similar name-) * insert them in the kohastructure.sql The syspref is an absolute "must have" to have Koha working, so I think it's correct to have them in the kohastructure.sql If no-one object, i'm willing to write the patch for that. ( Please confirm i'm not forgetting something ! ) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08

1 1

Global Bugs Squashing Day #3
by Magnus Enger 04 Aug '11

04 Aug '11

Dear Community, Just a gentle reminder that in Kiribati it's now August 5th, and time for GBSD#3: http://wiki.koha-community.org/wiki/2011-08-05_Global_bug_squashing_day Not sure what to do? Get on the IRC channel and someone will most likely point you in the right direction! http://koha-community.org/get-involved/irc/ And remember: You don't have to be a programmer to help! Want to add even more fun to the mix? Why not join "The Brave Adventurers of Koha" and earn "Experience Points" for your efforts? http://www.chorewars.com/party.php?name=Koha Again, get on the IRC channel and ask about how to get in there. Happy hunting! Magnus Enger

1 0

Re: [Koha-devel] [Koha-patches] [PATCH] [SIGNED-OFF] Bug 6553 : Follow up adding license statements
by Robin Sheat 04 Aug '11

04 Aug '11

A fairly pedantic note, but to aid in getting things into distros (and just all-round doing it right), licensing headers should have the copyright lines for the people who have contributed to them, as well as the GPL boilerplate. Marcel de Rooy schreef op do 04-08-2011 om 08:10 [+0000]: > From: Chris Cormack <chrisc(a)catalyst.net.nz> > > http://bugs.koha-community.org/show_bug.cgi?id=6653 > > Signed-off-by: Marcel de Rooy <m.de.rooy(a)rijksmuseum.nl> > Patch only adds license text. > --- > rotating_collections/addItems.pl | 17 +++++++++++++++++ > rotating_collections/editCollections.pl | 15 +++++++++++++++ > rotating_collections/rotatingCollections.pl | 17 +++++++++++++++++ > rotating_collections/transferCollection.pl | 17 +++++++++++++++++ > 4 files changed, 66 insertions(+), 0 deletions(-) Robin.

2 1

FW: Patch format
by Marcel de Rooy 04 Aug '11

04 Aug '11

+1 for removing redundancy ;) -----Oorspronkelijk bericht----- Van: koha-devel-bounces(a)lists.koha-community.org [mailto:koha-devel-bounces@lists.koha-community.org] Namens Mason James Verzonden: maandag 1 augustus 2011 02:50 CC: koha-devel(a)lists.koha-community.org Onderwerp: Re: [Koha-devel] Patch format i think an little improvement to our current patch workflow, would be to just attach the patch to a bug, in bugzilla an automated bugzilla script could then send that new patch to the patches list this proposed method removes the double-handling of a patch (sending to patches-list and attaching to bugzilla) and would help encourage people to use bugzilla to track their patches, rather than sending the patch to the list, and the patch getting lost a good idea, or not? Mason _______________________________________________ Koha-devel mailing list Koha-devel(a)lists.koha-community.org http://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/

3 3

Proposal for Assistance with QA Testing for Koha 3.6
by Ian Walls 03 Aug '11

03 Aug '11

Dear Community, As you are likely aware, I am the elected Quality Assurance Manager for the 3.6 release. As you may also be aware, there are currently 96 patches in Bugzilla that are signed off and ready for QA testing (at the time of this writing). My goal for my term as QAM was to keep this list under 10, but as we can see, that's not the current state of things. I do not want to become a bottleneck against good code getting into Koha. Quality Assurance is by it's nature a painstaking process, especially with more complex patches, to ensure that there are no regressions of functionality, or massive, unexpected shifts in default behavior. Often, numerous configurations of data need to checked against, to make sure fixing a bug for one possible setup doesn't cause a new bug in another. So far, we've not had to pull any code from master due to a regression, so it seems this process is working. But, that said, we've still got nearly a hundred patches waiting in the queue. Paul Poulain has offered to assist me with QA for the remainder of the Koha 3.6 release cycle. He's got the hours to dedicate towards this, and can help put some of these patches through their paces. While anyone can test any patch that's been published (and everyone is encouraged to do so), Paul is asking for the additional power to mark the patches he's tested as "Passed QA" if they do indeed pass his tests. Here are the exact terms of the proposal: a) he would not mark any patch he himself has written as Passed QA b) any patch written by BibLibre would need a signoff from another, external person before he'd test it c) he would start with the patches that have been waiting the longest d) the QAM and RM could reject any "Passed QA" patch if they feel it's not sufficient for whatever reason (which would need to be noted in the bug report) I do not feel that I necessarily have the right to transfer the "mark patches as Passed QA" power over to another person without the community's consent. So, I bring this to the group. Is this an acceptable proposal? Does the QAM have the right to "deputize" community members and transfer this particular power, or does the community need to vote on it? Are there any aspects of the issue that I'm missing? Thanks for your consideration and attention on this matter, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

5 5