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

Re: [Koha] Changed IP - Can't connect to mysql server
by Mason James 13 May '08

13 May '08

On 2008/05/13, at 1:13 AM, Robert Linebaugh wrote: > Koha version 2.2.5 (Internal IP 10.0.254.3) > Mysql version 4.1 (Internal IP 10.0.254.4) > > I did not use the GRANT ALL ON command on the mysql server. I > assume this command has to be performed on the mysql server and the > @server should be the Koha server? (ex. GRANT ALL ON koha.* to > kohaadmin(a)10.0.254.3 ) I probably need to know the mysql root > password that I’ve been reading about? > > I’m not sure how to connect to the mysql server with the > commandline mysql client from the koha server. > > C:\Documents and Settings\rlinebaugh>telnet 10.0.250.4 3306 > Connecting To 10.0.250.4...Could not open connection to the host, > on port 3306: > Connect failed > > Rob Hi Rob, your mysql server isnt configured to allow remote connections. these are *nix examples, but you get the gist... You can google for more info. 1) edit your mysql conf file , change your bind-address value from 127.0.0.1 to your server's IP server$ vi /etc/mysql/my.cnf # bind-address = 127.0.0.1 bind-address = 10.0.254.4 ------------ 2) restart your mysqld server$ /etc/init.d/mysql restart ------------ 3) connect to server from the client.... client $ mysql -u kohaadmin -h 10.0.254.4 -p koha Your MySQL connection id is 8 Server version: 5.0.32-Debian_7etch5 Debian etch distribution Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> Mason. > From: Mason James [mailto:mason.loves.sushi@gmail.com] > Sent: Friday, May 09, 2008 7:53 PM > To: Ryan Higgins > Cc: Robert Linebaugh; koha > Subject: Re: [Koha] Changed IP - Can't connect to mysql server > > > On 2008/05/10, at 10:02 AM, Ryan Higgins wrote: > > > > Did you > > GRANT ALL ON mykoha_db_name.* to kohaadmin(a)72.227.31.7 > > on the mysql server ? > > Can you connect to the mysql server with the commandline mysql > client on the koha server ? > > > I had to change the IP scheme of my network. I have changed the > > interfaces, hosts and koha.conf files to reflect the new IP. > When I try > > to access Koha by typing http://koha.domain.com:8050 I get a 500 > > internal server error. My opac-error_log file says: > > > > > > > > Thu May 08 21:24:58 2008] [error] [client 72.227.31.7] DBI > > connect('Koha:10.0.250.4','kohaadmin',...) failed: Can't connect to > > MySQL server on '10.0.250.4' (111) at > > /usr/local/koha/intranet/modules/C4/Context.pm line 411 > > Hi Robert, > > Try these tests too... > > To test your networking, try a telnet to the remote mysql box... > $ telnet 10.0.250.4 3306 > > If that works, hit it with the mysql client... > $ mysql -u kohaadmin –h 10.0.250.4 –p'mypassword' koha > > Cheers, Mason. _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

2 2

Problems with Fixes to 1782
by Joshua Ferraro 12 May '08

12 May '08

I've just applied and pushed Henri-Damien's recent patch to fix bug 1782. The patch adds a new syspref called AddPatronLists that allows the administrator to specify how patron types and categories should be displayed in the patron add screen. Specifically, it seems to determin whether the categories should be organized by the top-level hard-coded type codes (Adult, Child, Staff, etc.), or whether the user-specified categories are the only ones that should be displayed. NOTE: This only patches the drop-down list when adding a patron, the memberentry.pl screen still groups the list of categories by the type selected, regardless of the syspref's value. I'd consider this a bug. However, this patch causes complete failure of memberentry.pl. When adding new patrons, the following error results, regardless of the value of the PatronLists syspref: Bad index while coercing array into hash at /home/jmf/repos/koha-rm-test.git/members/memberentry.pl line 151. The relevant lines in memberentry.pl are: 150 my $tmpborrowercategory=GetBorrowercategory($check_category); 151 $check_categorytype=$tmpborrowercategory->{'category_type'}; The problem is that it assumes that GetBorrowercategory always returns a hash, which it does not. This is a problem in and of itself, but futher digging reveals that a sub called 'checkuniquemember' is completely bogus, and may be the real cause of the problem (it attempts to prevent creation of patrons with the same name!!!) WARNING: These bugs are outstanding, and it's very likely that adding and editing patrons WILL FAIL after you apply these patches until the problems are resolved. Normally, I wouldn't push up a patch that had such catastrophic consequences, but I feel the best approach in this case is to push up a fix to the problem asap. So ... any volunteers to repair the damage and clean up this problematic area? Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE CEO migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf(a)liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS

1 1

[marc.chantreux@biblibre.com: Re: XML::LIBXSLT error on Debian etch]
by Marc Chantreux 09 May '08

09 May '08

----- Forwarded message from Marc Chantreux <marc.chantreux(a)biblibre.com> ----- From: Marc Chantreux <marc.chantreux(a)biblibre.com> To: koha-devel(a)lists.koha.org Subject: Re: [Koha-devel] XML::LIBXSLT error on Debian etch On Wed, May 07, 2008 at 08:48:34AM -0600, Chadwick, John, DCA wrote: > Okay, I got the DBD::mysql issue resolved yesterday. I am down to one stubborn package, XML::LIBXSLT won't install. as this module is debian packaged, why don't you install it by this way ? koha:/# apt-cache policy libxml-libxslt-perl libxml-libxslt-perl: Installé : 1.59-1 Candidat : 1.59-1 Table de version : 1.62-1.1 0 500 http://ftp.fr.debian.org testing/main Packages *** 1.59-1 0 990 http://ftp.u-strasbg.fr etch/main Packages 100 /var/lib/dpkg/status hth -- Marc Chantreux BibLibre, expert en logiciels libres pour l'info-doc http://biblibre.com ----- End forwarded message ----- -- Marc Chantreux BibLibre, expert en logiciels libres pour l'info-doc http://biblibre.com

1 0

IndependantBranches features...
by Paul POULAIN 09 May '08

09 May '08

Hello, For libraries with IndependantBranches=ON, 1 question : Only the home library can edit an item. I think the holding library should be able to edit it as well. The use case : an item is returned after an issue, and the holding library sees that there is something bad on the item (page removed, DVD scratched... atm, the library can't update the item. I'll submit a patch for that, unless someone object. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

4 6

[Koha] Koha 3.0 beta on Kubuntu gutsy - "production mode - trapped fatal error"
by Mason James 08 May '08

08 May '08

> > Hi Robert, > > On a debian box, try installing the package 'libmysqlclient15-dev' > to resolve your missing 'mysql_config' file issue. > > $ which mysql_config > /usr/bin/mysql_config > > $ dpkg -S /usr/bin/mysql_config > libmysqlclient15-dev: /usr/bin/mysql_config > > Cheers, Mason. > Just a little update (on a debian box) The previous 'dpkg -S' example only works on packages that you *already* have installed Try apt-file to find out which package a file belongs to - that you *dont* have installed. $ sudo apt-get install apt-file $ apt-get update $ apt-file search 'mysql_config' libmysqlclient15-dev: usr/bin/mysql_config Mason. _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

1 0

Re: [Koha-devel] QA process (was: "freezing" koha 3.0)
by Andrew Moore 07 May '08

07 May '08

On Wed, May 7, 2008 at 11:10 AM, Paul POULAIN <paul.poulain(a)free.fr> wrote: <snip> > For instance, the role of QA > manager means almost nothing in real life. I'm sorry about that, we > should speak of how to introduce the QA role in the git process. I'm interested in opening up this topic a little bit more. Specifically, I'd like to know what I can do as a developer to make the QA process more efficient and effective. Some of the things I can think of that I can do that may help us are: * ensure that I create test cases for new code that I add * try to create test cases for other code that I touch * Document and describe the recent changes to the test suite to make it easier for others to use and extend it * document my changes and the anticipated side effects more thoroughly in my git commit messages and on bugs.koha.org * triage my bugs and others so that bugs.koha.org is more accurate * set up a smoke bot to run the automated test suite after each commit and report the results What things do the rest of you see as being high-value contributions to the QA process? -Andy

3 2

RFC: alternate borrower IDs
by Galen Charlton 07 May '08

07 May '08

Hi, Various LibLime customers have requested the ability to have the borrower record store additional IDs beyond the barcode and OPAC user ID. To meet this requirement, we propose the following development, which barring a general escape of zombies from the sewers of Chicago, I could implement by the middle of next week. The concept of alternate (or additional) IDs would support the following use cases: [1] A (academic) library loads patron records for their students from CSV file extracted from a database run by the campus registrar. However, the registrar does not know or care about barcodes and userids assigned by the library; all they supply is a unique campus ID number that the library is expected to match against during patron imports. [2] A library has more than two identifiers for their patrons. Two types of identifiers can take passwords or PINs. [3] More broadly, and this is something that falls out of the specific implementation I'm about to propose, the library wants to add free-text attributes to the patron record that are not covered by the existing columns of the borrowers table. To implement this, two new database tables would be added: borrower_attribute_types (ID or attribute_types) * ID type code (e.g., INSTID) * ID type description (e.g., 'Campus student ID') * repeatable (whether or not a borrower record can have more than one ID of that type) * unique (whether or not the ID should be enforced as a unique identifier) * opac_display (whether or not the ID should display in the patron's account page) * password_allowed (whether or not a password can be associated with the ID and used for patron authentication) * staff_searchable (whether or not the ID can be searched in the staff interface) borrower_attributes * borrowernumber (foreign key) * ID type (foreign key) * attribute (text string containing the ID or attribute) * password (optional password associated with the ID) The primary functional changes would be 1. new Administration page to define borrower ID types 2. new patron editing page to add, delete, or edit borrower ID types 3. additional pane or box in patron account tab in OPAC to display additional IDs 4. in staff client, ability to include one or more ID types in search box 5. ability to load alternate IDs via the patron import tool. This would be done by adding an optional column in the CSV file that would contain ID types and IDs. Any unique ID would act as a matchpoint. For example, the column might contain: "INSTID:12345, MAJOR:Physics, ADDLOGIN:abcdef/passwd" The new feature would be guarded by a syspref - if the preference is off, no sign of the additional IDs would display in the Administration menu, the patron editor, or the OPAC. I would appreciate comments on this proposed functionality, the proposed implementation, and whether or not this would be of use to others. Regards, Galen -- Galen Charlton Koha Application Developer LibLime galen.charlton(a)liblime.com p: 1-888-564-2457 x709 _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

3 3

reserves.waitingdate & upgrade 22 => 30
by Paul POULAIN 07 May '08

07 May '08

Hello, in Koha 3.0, the reserves.waitingdate field is used in some places to check that a reserve has been filled & is waiting for pick up. It works fine. Except when migrating from 2.2 : the field is created empty, which a script like circ/waitingdate.pl disklike. That is a problem that can be solved by a single SQL statement : UPDATE `reserves` SET waitingdate=timestamp WHERE found='W' and waitingdate IS NULL Do you think we : - should ignore this transitionnal problem - should updatedatabase with a new DB dump - should do the SQL query when bumping to 062, that has some stuff related to reserves. (my preferred solution) Your opinion ? (feel free to confirm the SQL statement is correct. It was on the DB I just run it on, not 100% sure it's OK for any cases) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : 04 91 31 45 19

1 0

Standardised US English Translation
by russ＠russandsarah.gen.nz 07 May '08

07 May '08

Hi All, After a big fuss, I have gone a bit quiet. Working on Koha is not my day job anymore. Anyway, forgive the cross list posting, but my last email got forwarded to all the lists and I guess this topic is of interest to the devel list as well. I am happy to help out with standardising the language used in the default Koha install to that of the dictionary everyone agreed on. It would be easiest for me to do this using Kartouche at translate.koha.org, because then I can see how many strings still need to be translated and I can do it from anywhere. Any progress with getting a language code setup? Is Joshua the only person that can do this? Cheers, Russel

3 2

install problem postgres
by Roxana Luz Fleipaz 07 May '08

07 May '08

Dear colleagues .. I still long line of development of Koh .. I have a doubt, it is possible to make the installation of beta-koha3 with postgres, debian etch 4.0 at this time? Thank you. Atte. Roxana Luz _______________________________________________ Koha-devel mailing list Koha-devel(a)nongnu.org http://lists.nongnu.org/mailman/listinfo/koha-devel

3 2