From mtj at kohaaloha.com Sun Oct 2 05:06:59 2011 From: mtj at kohaaloha.com (Mason James) Date: Sun, 2 Oct 2011 16:06:59 +1300 Subject: [Koha-devel] tt style point In-Reply-To: <4E82E863.5090204@biblibre.com> References: <4E733D85.9020300@ptfs-europe.com> <4E736576.9020306@gmail.com> <4E7372F4.4090109@ptfs-europe.com> <4E76F8A5.40509@gmail.com> <44EE2F7E-6B48-4969-A60C-7212DF55B18C@kohaaloha.com> <4E784C0D.2090308@gmail.com> <4E82E863.5090204@biblibre.com> Message-ID: <522DD2AF-2AD2-45CA-A1A4-581940DF75CB@kohaaloha.com> On 2011-09-28, at 10:26 PM, Paul Poulain wrote: > Le 20/09/2011 13:40, Mason James a ?crit : >>>> it is always the same question : who will decide >> we can decide now the koha-devel mailing-list, or as a topic for the next Koha IRC meeting >> >> > i've added the topic for the next IRC meeting > http://wiki.koha-community.org/wiki/General_IRC_Meeting,_5_October_2011#Agenda thanks Paul, thats great! fyi: i've updated the 5th-Oct irc-meeting wiki entry with some examples for the suggested perltidy styles... http://git.kohaaloha.com/?p=koha-perltidy/.git;a=commit;h=HEAD i'm really hoping for vote on this issue, see you all at the irc-meeting on the 5th-Oct ;) cheers, Mason -- KohaAloha, NZ From David.W.Hartman at disney.com Tue Oct 4 15:09:22 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Tue, 4 Oct 2011 09:09:22 -0400 Subject: [Koha-devel] Koha 3.4.5 -- does it fix the "detect duplicates" when importing records? Message-ID: <3E19441498923443B9DBE2FE1C0E70B60447DD09E8@SM-FLOR-VXMB04B.wdw.disney.com> Does anyone know if this upgrade 3.4.5 will fix the "detect duplicates" feature when importing records? When I import records, Koha cannot identify the duplicate records (even though the ISBNs are identical). I have reported the problem to the bug fixers but was wondering if the upgrade fixes it. -----Original Message----- From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Chris Nighswonger Sent: Tuesday, September 27, 2011 7:44 AM To: koha at lists.katipo.co.nz; koha-devel at lists.koha-community.org; koha-translate at lists.koha-community.org Subject: [Koha-devel] Koha 3.4.5 is now available It is with pleasure that I announce the release of Koha 3.4.5. The package can be retrieved from: http://download.koha-community.org/koha-3.04.05.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.04.05.tar.gz.MD5 http://download.koha-community.org/koha-3.04.05.tar.gz.MD5.asc http://download.koha-community.org/koha-3.04.05.tar.gz.sig Release notes for 3.4.5 are below. Come and get it! RELEASE NOTES FOR KOHA 3.4.5 - 26 September 2011 ======================================================================== Koha is the first free and open source software library automation package (ILS). Development is sponsored by libraries of varying types and sizes, volunteers, and support companies from around the world. The website for the Koha project is ? ?http://koha-community.org/ Koha 3.4.5 can be downloaded from: ? ?http://download.koha-community.org/koha-3.04.05.tar.gz Installation instructions can be found at: ? ?http://wiki.koha-community.org/wiki/Installation_Documentation ? ?OR in the INSTALL files that come in the tarball Koha 3.4.5 is a bugfix/maintenance release. Highlights of 3.4.5 ====================== 4122 ? ?blocker ? ? WebBasedSelfCheck doesn't control anything 6704 ? ?critical ? ?merging records cuts off fields at quotation marks 6727 ? ?critical ? ?can't import frameworks 6750 ? ?critical ? ?Guarantor search broken on translated templates 4419 ? ?major ? ? ? Cannot change module for notice templates 4966 ? ?major ? ? ? no way to finish receiving 6318 ? ?major ? ? ? fields missing when editing a layout 6351 ? ?major ? ? ? Cannot delete library-specific circulation rules 6620 ? ?major ? ? ? Sip Server Output may be buffered 6651 ? ?major ? ? ? koha-upgrade-to-3.4 fails when multiple instances are present 6665 ? ?major ? ? ? advancedMARCeditor preference not functioning 6765 ? ?major ? ? ? Enable correct checksums for UTF-8 encoded data 6834 ? ?major ? ? ? $template->{param_map} is deprecated with the introduction of Template::Toolkit 6841 ? ?major ? ? ? A member with cataloging permissions cannot change branches (when independent branches is set on) Bugs fixed in 3.4.5 ====================== 520 ? ? Displaying ALL records 1016 ? ?Crashed mySql tables 1220 ? ?validation problems and usability in lynx 1664 ? ?Installer not picking up missing perl modules 2539 ? ?kohaspsuggest is deprecated, notes outmoded 2775 ? ?Test suite failing after change to cache sysprefs 2891 ? ?Cannot manually enter dates in some report forms 4866 ? ?Optionally enable Change event for item plugins 4868 ? ?Improve controls for cloning and deleting MARC subfields 4877 ? ?Create and update the manual pages for the koha-* scripts. 5028 ? ?Remove references to catmaintain.pl 5252 ? ?Emails & Phones On Patron Add/Edit form 5498 ? ?Standardize markup and style of pagination menus 5524 ? ?Can't delete list from second page of results 5602 ? ?Improve configurability of package building scripts 5866 ? ?At larger hold volume, waitingreserves.pl for all libraries times out, can cause generalized slowness 6121 ? ?waitingreserves: branchname instead of branch code 6129 ? ?ISSN url param for serialssolutions.com 6256 ? ?Many bib1 attributes missing 6275 ? ?Automated backups of data and config 6368 ? ?unimarc_field_4XX plugin does not work with new templates 6431 ? ?New Circulation modules for Hourly Circulation 6458 ? ?incorrect parsing result in translation processing 6479 ? ?Encoding problem in "recievedlist" when the numbering formula contains utf-8 characters 6516 ? ?koha-create makes assumptions about borrowernumber of staff user 6517 ? ?koha-create wants "use database" in DEFAULTSQL 6528 ? ?Cataloging search issues - Holdings not displayed in location column 6538 ? ?help on letter.pl is incorrect 6540 ? ?Add more options to koha-create 6555 ? ?only 10 lists in pull down when adding from a bib record 6562 ? ?Reserve request generates unnecessary runtime errors 6595 ? ?Add German translation for purchase suggestion mails 6602 ? ?Reports dictionary doesn't properly recognize text columns 6640 ? ?Template errors in defining default variable values causes information not to be displayed 6652 ? ?Zip showing in funny place on libraries admin 6656 ? ?Default sort preferences ignored on advanced search 6662 ? ?sort options in opac are dewey specific 6677 ? ?patron stats still refers to debarred 6695 ? ?Layout of patron category add/edit form slightly broken 6696 ? ?New category button broken when no categories defined 6712 ? ?Remove memberofinstitution markup from templates until it can be completed 6715 ? ?xmlControlField.js always fetches the value_builder xml files in the "en" directory. 6723 ? ?allow framework import with CRLF 6724 ? ?Holds Ratio does not allow decimals 6726 ? ?When SMS is enabled the messaging table is misaligned 6728 ? ?Table sorter for receiving acquisitions 6732 ? ?Missing Title for Manual Invoice 6733 ? ?printing routing list sends you to main serials page 6744 ? ?Acknowledge the actual es-ES translators 6747 ? ?Additional check in opac-export 6753 ? ?Markup corrections and improvements for label export window 6754 ? ?Improve breadcrumbs on lists pages 6768 ? ?Two unused include files can be removed: error-top.inc and error-bottom.inc 6791 ? ?editing list with apostrophe loses text 6794 ? ?Broken toggle in member-flags in ie 6822 ? ?RIS export problem in opac-export.pl with parsing the MARC 6829 ? ?Remove two warnings for opac-MARCdetail 6860 ? ?syndetics covers not showing on search results or shelf browse 6863 ? ?covers missing from shelf browse for various services System requirements ====================== ? ?Changes since 3.2: ? ?* Template::Toolkit Documentation ====================== As of Koha 3.2, the Koha manual is now maintained in DocBook. ?The home page for Koha documentation is ? ?http://koha-community.org/documentation/ As of the date of these release notes, only the english version of the Koha manual is available: ? ?http://koha-community.org/documentation/3-4-manual/ The Git repository for the Koha manual can be found at ? ?http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary Translations ====================== Complete or near-complete translations of the OPAC and staff interface are available in this release for the following languages: ?* Chinese ?* Danish ?* English (New Zealand) ?* English (USA) ?* French (France) ?* French (Canada) ?* German ?* Greek ?* Hindi ?* Italian ?* Norwegian ?* Portuguese ?* Spanish ?* Turkish Partial translations are available for various other languages. The Koha team welcomes additional translations; please see ? ?http://wiki.koha-community.org/wiki/Translating_Koha for information about translating Koha, and join the koha-translate list to volunteer: ? ?http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate The most up-to-date translations can be found at: ? ?http://translate.koha-community.org/ Release Team ====================== The release team for Koha 3.4 is Release Manager: ? ? ? ?Chris Cormack Documentation Manager: ?Nicole C Engard Translation Manager: ? ?Fr??d??ric Demians Release Maintainer (3.2.x): ? ? ? ? ? ? ? ? ? ? ? ?Chris Nighswonger Release Maintainer (3.4.x): ? ? ? ? ? ? ? ? ? ? ? ?Chris Nighswonger QA Manager: ? ? ? ? ? ? Colin Campbell Credits ====================== We thank the following individuals who contributed patches to Koha 3.4.5 Tomas Cohen Arazi Alex Arnaud Steven Callender Colin Campbell Fr??d??rick Capovilla Chris Cormack Christophe Croullebois Fr??d??ric Demians Nicole C. Engard Magnus Enger Katrin Fischer Srdjan Jankovic Janusz Kaczmarek Ulrich Kleiber Henri-Damien LAURENT Owen Leonard Chris Nighswonger Maxime Pelletier Paul Poulain Liz Rea Marcel de Rooy Salvador Zaragoza Rubio Robin Sheat Ian Walls Ward van Wanrooij Brett Wilkins We regret any omissions. ?If a contributor has been inadvertantly missed, please send a patch against these release notes to koha-patches at lists.koha-community.org. Revision control notes ====================== The Koha project uses Git for version control. ?The current development version of Koha can be retrieved by checking out the master branch of ? ?git://git.koha-community.org/koha.git The branch for Koha 3.4.x (i.e., this version of Koha and future bugfix releases) is 3.4.x. The next major feature release of Koha will be Koha 3.6.0. Bugs and feature requests ====================== Bug reports and feature requests can be filed at the Koha bug tracker at ? ?http://bugs.koha-community.org/ Ehara taku toa i te toa takitahi, engari he toa takitini _______________________________________________ Koha-devel mailing list Koha-devel at 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/ From mtj at kohaaloha.com Tue Oct 4 15:53:00 2011 From: mtj at kohaaloha.com (Mason James) Date: Wed, 5 Oct 2011 02:53:00 +1300 Subject: [Koha-devel] Koha 3.4.5 -- does it fix the "detect duplicates" when importing records? In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60447DD09E8@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD09E8@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: <5AB5FE58-7ABF-40C0-BD67-2F8252B9EAFD@kohaaloha.com> On 2011-10-5, at 2:09 AM, Hartman, David W. - GBTS Library wrote: > Does anyone know if this upgrade 3.4.5 will fix the "detect duplicates" feature when importing records? When I import records, Koha cannot identify the duplicate records (even though the ISBNs are identical). > > I have reported the problem to the bug fixers but was wondering if the upgrade fixes it. whats the bug number? -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 535 bytes Desc: This is a digitally signed message part URL: From David.W.Hartman at disney.com Tue Oct 4 16:02:00 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Tue, 4 Oct 2011 10:02:00 -0400 Subject: [Koha-devel] Koha 3.4.5 -- does it fix the "detect duplicates" when importing records? In-Reply-To: <5AB5FE58-7ABF-40C0-BD67-2F8252B9EAFD@kohaaloha.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD09E8@SM-FLOR-VXMB04B.wdw.disney.com> <5AB5FE58-7ABF-40C0-BD67-2F8252B9EAFD@kohaaloha.com> Message-ID: <3E19441498923443B9DBE2FE1C0E70B60447DD09F4@SM-FLOR-VXMB04B.wdw.disney.com> Bug 6909 - -----Original Message----- From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Mason James Sent: Tuesday, October 04, 2011 9:53 AM To: Hartman, David W. - GBTS Library Cc: koha-devel Subject: Re: [Koha-devel] Koha 3.4.5 -- does it fix the "detect duplicates" when importing records? On 2011-10-5, at 2:09 AM, Hartman, David W. - GBTS Library wrote: > Does anyone know if this upgrade 3.4.5 will fix the "detect duplicates" feature when importing records? When I import records, Koha cannot identify the duplicate records (even though the ISBNs are identical). > > I have reported the problem to the bug fixers but was wondering if the upgrade fixes it. whats the bug number? From ian.walls at bywatersolutions.com Tue Oct 4 16:03:49 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Tue, 4 Oct 2011 10:03:49 -0400 Subject: [Koha-devel] Koha 3.4.5 -- does it fix the "detect duplicates" when importing records? In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60447DD09F4@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD09E8@SM-FLOR-VXMB04B.wdw.disney.com> <5AB5FE58-7ABF-40C0-BD67-2F8252B9EAFD@kohaaloha.com> <3E19441498923443B9DBE2FE1C0E70B60447DD09F4@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: I believe 6909 is a duplicate of 6713, which is patched: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6713 -Ian On Tue, Oct 4, 2011 at 10:02 AM, Hartman, David W. - GBTS Library < David.W.Hartman at disney.com> wrote: > Bug 6909 - > > -----Original Message----- > From: koha-devel-bounces at lists.koha-community.org [mailto: > koha-devel-bounces at lists.koha-community.org] On Behalf Of Mason James > Sent: Tuesday, October 04, 2011 9:53 AM > To: Hartman, David W. - GBTS Library > Cc: koha-devel > Subject: Re: [Koha-devel] Koha 3.4.5 -- does it fix the "detect duplicates" > when importing records? > > > On 2011-10-5, at 2:09 AM, Hartman, David W. - GBTS Library wrote: > > > Does anyone know if this upgrade 3.4.5 will fix the "detect duplicates" > feature when importing records? When I import records, Koha cannot identify > the duplicate records (even though the ISBNs are identical). > > > > I have reported the problem to the bug fixers but was wondering if the > upgrade fixes it. > > > whats the bug number? > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Wed Oct 5 09:55:56 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Wed, 05 Oct 2011 09:55:56 +0200 Subject: [Koha-devel] Commentary on Paul's Koha 3.8 Release Manager proposal In-Reply-To: <20110914225143.5442B9F0E8@nail.towers.org.uk> References: <20110914225143.5442B9F0E8@nail.towers.org.uk> Message-ID: <4E8C0D8C.7090001@biblibre.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 15/09/2011 00:51, MJ Ray a ?crit : > A minor disagreement is with the platform. Paul's proposal seems to > be for 3.8 and 4.0 RM, yet there's very little detail on 4.0 because > the community discussion hasn't really started: lots of great features > suggested, some scary changes, but not much agreed. Let's agree the > RM for 3.8 and then when the next release rolls around, then let's see > what we want to do then? > In general, I'm fine with folding into 3.x progressively. Seems > like a good idea. (Now find me more libraries so I can spend > more time on it... ;-) ) Answering your mail just before the IRC meeting, sorry for not taking time before. I've already expressed that changing RM every 6 months is too much. In my idea, the RM should promise to stay RM for 2 releases. That's with this idea that I?ve submitted my application. I agree that there are little details for 4.0, but the most important thing is that I want to discuss how to do things early (starting "immediately", organize, ... HTE (Hope This Explain ;-) ) - -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOjA2MAAoJEK81SonuhyGo21cH/1wYFS/lqRZMe9Zi69DTVInk f7deqSvyimsGLfpXKxJ8DPq2hLsVqTA8o5aCg8sENFMboNYgxqoYaaAjLaKCc5tY PPhMLN2mXhHVQ1aOUpucqkpFX6NIA+gsVOjGJW+EYZ3ika+czVnzlMR/TfzDP/vH mpxZnZEVylgDcprHdG0Ty15Rgnx3u8ZnTRoYJe2jLZORs1oijUJYZGpUnSKFSjKO pus/JFrBiTr1OUwsXRRQHlw/S2YefV2B+NreIiZlY51TP+TstNtbfx36qM4O2JMw ZHEQLDrgKzKj7Zg6shhT+69+lDmF1QP2eD/v6Fjmfq+ejqiwq7c7BdHSk/iJNgE= =5gaP -----END PGP SIGNATURE----- From paul.poulain at biblibre.com Wed Oct 5 10:07:19 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Wed, 05 Oct 2011 10:07:19 +0200 Subject: [Koha-devel] Commentary on Paul's Koha 3.8 Release Manager proposal In-Reply-To: References: <4E6DD1DD.6090302@biblibre.com> Message-ID: <4E8C1037.5020704@biblibre.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 12/09/2011 15:37, Ian Walls a ?crit : > Yes, the main difference in our proposals is primarily one of timing. > You're proposing that we have Koha 4.0 ready in about 1 year, and will > include Solr integration and updated Perl coding practices. Those are > certainly good things, yes, and they may well be possible in 1 year. Or > they may not. well, considering Solr is in production at 3 of our libraries, that some ppl are already involved in reintroducing zebra over the updated API we've developped for Solr, I think it's possible in 1 year. And BibLibre is willing to dedicate the needed ressources to achieve this goal ! > I agree that we should continue to do time-based releases; every 6 months > seems to be working well for us. The difficulty here, though, is that with > time-based releases, you cannot guarantee that any given feature will be > ready in time. Sure, any one development team can promise they'll have it > coded up to their clients standards and rebased for inclusion, but how will > that interact with other code written by other teams? Who, outside the > original development team, can be committed to test and sign-off on the > work? I don't say it will be easy. But not harder than what had been done before. (Note for newbies : i'm an always optimistic man ;-) ) I add that more coordination will result in less conflicts. And my application is coordination-centric. > So, when working on time-based releases, you cannot promise features. agreed > This > is why I propose we continue with time-based releases on the 3.X line until > such time as all the agreed-upon features for Koha 4.0 are ready. If we're > quick, sure, we can jump straight from 3.8 to 4.0. I think it's much more > likely we'll have a 3.10 in there, but maybe that's just me. isn't it just a numbering difference ? I feel it is. I've nothing about updating the 1st digit on each major structural change. So, i've nothing against saying something like : "the final goal : solr/persistency/DB abstraction/supporting more than MARC oct 12, Solr & DB abstraction ready = Koha 4.0 april 13, persistency ready = Koha 5.0 oct 13, supporting more than MARC = Koha 6.0 It's just a numbering question, very minor difference ;-) > I think it's more important to define our goals in > those terms, rather than in how we're going to accomplish them. Agreed > HDL pointed out early in the thread that some of the features I was floating > as possible for Koha 4.0 were librarian-centric, and some were > developer-centric. He's right, I wasn't really clearly differentiating in > that list. It was mostly meant as an example of what else would could > reasonably accomplish for the next major release of the software. Agreed, and coordination (Hackfest in 4 weeks++ on this matter !) > I don't think there will be nearly as many merge conflicts and rebase issues > as you fear, Paul. Once we decide on our feature set, any interested > developers would meet to figure out the coding requirements. This may take > several meetings, but in the end, we'll have a roadmap of what features > depend on what. Agreed. > I really like the idea of having multiple sandboxes set up so that folks can > test the different features more easily. We should definitely do this. > Having more people doing testing and Quality Assurance is always a good > thing. Providing test plans, test results and reasons for passing/failing > QA on the bug report will make it much easier to keep track of the history > of any particular fix or feature. BibLibre has now a "private cloud", with 4 servers, virtualization, template VMs. We can easily add physical servers, have a centralised authentification,... Still to be discussed with all of us, but we could add a (physical) server (16GB, quadri code) dedicated to sandboxes (or add VMs the physical server we already use for testing). We will discuss details later. > Our end goal is the same: make Koha the best it can be. We're mostly > disagreeing over small details. Whatever the outcome of this discussion, I > know we will all continue to work hard together to improve Koha. Agreed ;-) - -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOjBA3AAoJEK81SonuhyGofA4IALE+fszcuU4fqkJWh6pFoBIi zowZwPnElz68LXyAfMLzS2USkvD2sYJ4CYSw3QjgLE0oLMMyvVAobi7wvPLo/u7y S8IL8E/c7ZYeSzoQDI600MzNWt+FrpCQlcuwryxNjCPy8MyNuV/Q4aeei+/Qyj7S TVusfwKf8zaaNeoDMZC8xFj00Ij240pCCoIk0dadVtmINTtGOkmuTYpHOd+Fz4Pb GFDGfss8M70gZwEr8f/bo7kj4b0r+LHxv6xvtz+LR1iPd+f7OL7iikhnnRgSerPI vniy6oImc3sMR6oQGBcOaOhkWVochJMUs4iXRWkwCM3tSyjIWxvSYGFOoxquLiM= =9GlW -----END PGP SIGNATURE----- From kmkale at anantcorp.com Wed Oct 5 12:34:37 2011 From: kmkale at anantcorp.com (Koustubha Kale) Date: Wed, 5 Oct 2011 16:04:37 +0530 Subject: [Koha-devel] Interested to speak at KohaCon 2011 In-Reply-To: References: Message-ID: Hi this sounds like an excellent idea. unfortunately the program is full atm. but i am sure we can accommodate you in place of some one canceling at the last moment. or for this kind of topic, we can even have a parallel session.. if you want to interact with the developers we are going to have a hackfest from 4th nov to 6th nov. since there is no fixed program for that, you can achieve your objective there too.. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2 On Wed, Oct 5, 2011 at 3:52 PM, Anand Chitipothu wrote: > Hi, > > My name is Anand Chitipothu and I work for the Internet Archive. My > colleague Noufal Ibrahim and I would like to submit a presentation proposal > for KohaCon-2011. We work for the Open Library project, which is a publicly > editable library catalog. The director of the Open Library project, George > Oates, presented at KohaCon 2010. > > We would like to talk about how Open Library and Koha can work together and > see if we can work with the Koha developers at the conference to come up > with a prototype, if possible. > > Please let us know how can we submit a proposal and what else we need to > do. > > Thanks, > Anand > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjr at phonecoop.coop Wed Oct 5 13:36:44 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Wed, 5 Oct 2011 12:36:44 +0100 (BST) Subject: [Koha-devel] Commentary on Paul's Koha 3.8 Release Manager proposal In-Reply-To: <4E8C0D8C.7090001@biblibre.com> Message-ID: <20111005113644.6D51A9F0E8@nail.towers.org.uk> Paul Poulain > I've already expressed that changing RM every 6 months is too much. In > my idea, the RM should promise to stay RM for 2 releases. > That's with this idea that I?ve submitted my application. Offer if you want, but that's not how it was worded. Anyway, it seems this is moot for now. Meeting minutes to follow. Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From cnighswonger at foundations.edu Wed Oct 5 22:02:44 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Wed, 5 Oct 2011 16:02:44 -0400 Subject: [Koha-devel] freenode #koha and #koha-news Message-ID: By way of announcement, the Koha Community has secured control of the #koha namespace on freenode. #koha will serve as a backup for our main #koha channel on OFTC. Folks coming in channel there will receive a message pointing them to the main channel. #koha-news is simply that, a channel for posting Koha related news. huginn will automatically post any items on the blog feed of www.k-c.org. Feel free to post any other Koha related news there as well. This replaces the historic #kohanews channel which will go away at some unknown point when freenode begins enforcing their new namespace policy. Basically we have control of any channel beginning with '#koha-' Enjoy! Kind Regards, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin at catalyst.net.nz Wed Oct 5 23:25:23 2011 From: robin at catalyst.net.nz (Robin Sheat) Date: Thu, 06 Oct 2011 10:25:23 +1300 Subject: [Koha-devel] Interested to speak at KohaCon 2011 In-Reply-To: References: Message-ID: <1317849923.11495.31.camel@zarathud> Op woensdag 05-10-2011 om 16:04 uur [tijdzone +0530], schreef Koustubha Kale: > this sounds like an excellent idea. unfortunately the program is full > atm. but i am sure we can accommodate you in place of some one > canceling at the last moment. or for this kind of topic, we can even > have a parallel session.. I hope you [Anand] do come, I think that a talk on that would be fascinating. Even if only at the hackfest, I'm sure people would be willing to set aside a bit of time to talk about it. -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From noufal at archive.org Thu Oct 6 08:16:57 2011 From: noufal at archive.org (Noufal Ibrahim) Date: Thu, 06 Oct 2011 11:46:57 +0530 Subject: [Koha-devel] Interested to speak at KohaCon 2011 In-Reply-To: <1317849923.11495.31.camel@zarathud> (Robin Sheat's message of "Thu, 06 Oct 2011 10:25:23 +1300") References: <1317849923.11495.31.camel@zarathud> Message-ID: <87zkhe63vq.fsf@sanitarium.localdomain> Robin Sheat writes: > Op woensdag 05-10-2011 om 16:04 uur [tijdzone +0530], schreef Koustubha > Kale: >> this sounds like an excellent idea. unfortunately the program is full >> atm. but i am sure we can accommodate you in place of some one >> canceling at the last moment. or for this kind of topic, we can even >> have a parallel session.. > > I hope you [Anand] do come, I think that a talk on that would be > fascinating. Even if only at the hackfest, I'm sure people would be > willing to set aside a bit of time to talk about it. Both of us will surely be there. -- ~noufal http://nibrahim.net.in Everyone writes on the walls except me. -Said to be graffiti seen in Pompeii From M.de.Rooy at rijksmuseum.nl Thu Oct 6 13:29:00 2011 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Thu, 6 Oct 2011 11:29:00 +0000 Subject: [Koha-devel] Git whitespace warnings on DOS files Message-ID: <809BE39CD64BFD4EB9036172EBCCFA313408DB@S-MAIL-1B.rijksmuseum.intra> Hi all, Does anyone of you know how to get rid of whitespace warnings in git in the following scenario. (See also bugzilla patch 6803). (Note that I am using git version 1.6.0.6.) If you have a higher version and do not have the warnings, please let me know. Applying patch /usr/share/koha/rma/patches/6803-mods-xsl-v35.patch /usr/share/koha/rma/patches/6803-mods-xsl-v35.patch:27: trailing whitespace. /usr/share/koha/rma/patches/6803-mods-xsl-v35.patch:37: trailing whitespace. --> warning: 2 lines add whitespace errors. The whitespace warnings are related to the CRs (carriage return) on those lines, since the file is still in DOS format (koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2MODS3-1.xsl). Thanks, Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: From colin.campbell at ptfs-europe.com Thu Oct 6 15:05:59 2011 From: colin.campbell at ptfs-europe.com (Colin Campbell) Date: Thu, 06 Oct 2011 14:05:59 +0100 Subject: [Koha-devel] Git whitespace warnings on DOS files In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA313408DB@S-MAIL-1B.rijksmuseum.intra> References: <809BE39CD64BFD4EB9036172EBCCFA313408DB@S-MAIL-1B.rijksmuseum.intra> Message-ID: <4E8DA7B7.7020600@ptfs-europe.com> On 06/10/11 12:29, Marcel de Rooy wrote: > Hi all, > > Does anyone of you know how to get rid of whitespace warnings in git in the following scenario. (See also bugzilla patch 6803). > (Note that I am using git version 1.6.0.6.) If you have a higher version and do not have the warnings, please let me know. > I think if you set git config apply.whitespace=strip it will show the error but strip the whitespace errors in applying the patch. C. -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 845 557 5634 (phone) +44 (0) 7759 633626 (mobile) colin.campbell at ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com From David.W.Hartman at disney.com Thu Oct 6 15:20:34 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Thu, 6 Oct 2011 09:20:34 -0400 Subject: [Koha-devel] Koha 3.05 Message-ID: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> I would like to upgrade from Koha 3.05 to the latest version .. I want to tell my technical person the install path... Do I need to do each install to upgrade. 3.4.x series Current Stable Release Latest milestones: 3.04.03 Latest releases: 3.04.05, 3.04.04, 3.04.03, 3.04.02, 3.04.01, 3.04.00 Bugs targeted: None Blueprints targeted: None This is the stable branch of the 3.4.x release series 3.2.x series Supported Latest releases: 3.02.10, 3.02.09, 3.02.08, 3.02.8, 3.02.07, 3.02.06, 3.02.05, 3.02.04, 3.02.03, 3.02.02, 3.02.01, 3.02.00 Bugs targeted: None Blueprints targeted: None The stable branch for 3.2.x releases 3.0.x series Obsolete Latest releases: 3.0.6 Blueprints targeted: None The 3.0.x stable branch David W. Hartman Global Business Technology Strategy Library Team Disney 336N 407 828 4250 (8-222) FAX 407 828 4868 FOLLOW MY RESEARCH on Backlot & Yammer! Learn about our research partners in the 2011 IT Research Competency Center GBTS CAST can click to request AV Equipment, Books, & Research WATCH the GBTS Library (Video) Update ! CLICK for the GBTS VIRTUAL LIBRARYportal site!! "This communication is confidential, intended only for the named recipients above and may contain trade secrets or other information that is exempt from disclosure under applicable law. Any use, dissemination, distribution or copying of this communication by anyone other than the named recipients is strictly prohibited. If you have received this communication in error, please immediately notify us by calling (407) 828-4250. Thank you." [cid:image001.gif at 01CC8407.AB68A060]Please consider your environmental responsibility before printing this e-mail [cid:image001.gif at 01CC8407.AB68A060] Think Environmentality! Reduce! Reuse! Recycle! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 2028 bytes Desc: image001.gif URL: From ian.walls at bywatersolutions.com Thu Oct 6 17:56:12 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Thu, 6 Oct 2011 11:56:12 -0400 Subject: [Koha-devel] Koha 3.05 In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: David, What type of installation do you have? Tarball or Git? This will inform the best upgrade method for you. When you say you're on Koha 3.05, do you mean 3.00.05, or 3.05.00? The former is the now obsolete Koha 3.0 line, while the latter is the dev version for Koha 3.6 (which would indicate to me you have a Git install) Whatever your installation type and path, you won't need to install each intermediate version; you can jump straight from Koha 3.0.5 to Koha 3.4.5 if you wish, though it will take a fair amount of time to process all the updates. Cheers, -Ian 2011/10/6 Hartman, David W. - GBTS Library > I would like to upgrade from Koha 3.05 to the latest version ..**** > > ** ** > > I want to tell my technical person the install path? Do I need to do each > install to upgrade. **** > > ** ** > > *3.4.x series **Current Stable Release* > **** > > Latest milestones: 3.04.03 Latest releases: > 3.04.05 , 3.04.04, > 3.04.03 , 3.04.02, > 3.04.01 , 3.04.00 > **** > > Bugs targeted: None > Blueprints targeted: None **** > > This is the stable branch of the 3.4.x release series**** > > *3.2.x series **Supported* **** > > Latest releases: 3.02.10 , > 3.02.09 , 3.02.08, > 3.02.8 , 3.02.07, > 3.02.06 , 3.02.05, > 3.02.04 , 3.02.03, > 3.02.02 , 3.02.01, > 3.02.00 **** > > Bugs targeted: None > Blueprints targeted: None **** > > The stable branch for 3.2.x releases**** > > *3.0.x series **Obsolete* **** > > Latest releases: 3.0.6 **** > > Blueprints targeted: None **** > > The 3.0.x stable branch**** > > ** ** > > *David W. Hartman* > Global Business Technology Strategy Library > Team Disney 336N > 407 828 4250 (8-222) > FAX 407 828 4868 > > FOLLOW MY RESEARCH on Backlot & Yammer > ! > Learn about our research partners in the 2011 IT Research Competency > Center > GBTS CAST can click to request AV Equipment, > Books , & Research > WATCH the GBTS Library (Video) Update ! > CLICK for the GBTS VIRTUAL LIBRARY portal > site!!**** > > "This communication is confidential, intended only for the named recipients > above and may contain trade secrets or other information that is exempt from > disclosure under applicable law. Any use, dissemination, distribution or > copying of this communication by anyone other than the named recipients is > strictly prohibited. If you have received this communication in error, > please immediately notify us by calling (407) 828-4250. Thank you."**** > > [image: cid:075452218 at 28012009-07E4]*Please consider your environmental > responsibility before printing this e-mail* *[image: > cid:075452218 at 28012009-07EB]***** > > *Think Environmentality! Reduce! Reuse! Recycle!***** > > **** > > ** ** > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2028 bytes Desc: not available URL: From David.W.Hartman at disney.com Thu Oct 6 19:18:03 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Thu, 6 Oct 2011 13:18:03 -0400 Subject: [Koha-devel] Koha 3.05 In-Reply-To: References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> I think we can use Git. And our current version is 3.05.00.011 We?d love to jump straight to 3.4.5 (the system can be offline for hours ? we could run it overnight, etc.) From: Ian Walls [mailto:ian.walls at bywatersolutions.com] Sent: Thursday, October 06, 2011 11:56 AM To: Hartman, David W. - GBTS Library Cc: koha-devel Subject: Re: [Koha-devel] Koha 3.05 David, What type of installation do you have? Tarball or Git? This will inform the best upgrade method for you. When you say you're on Koha 3.05, do you mean 3.00.05, or 3.05.00? The former is the now obsolete Koha 3.0 line, while the latter is the dev version for Koha 3.6 (which would indicate to me you have a Git install) Whatever your installation type and path, you won't need to install each intermediate version; you can jump straight from Koha 3.0.5 to Koha 3.4.5 if you wish, though it will take a fair amount of time to process all the updates. Cheers, -Ian 2011/10/6 Hartman, David W. - GBTS Library > I would like to upgrade from Koha 3.05 to the latest version .. I want to tell my technical person the install path? Do I need to do each install to upgrade. 3.4.x series Current Stable Release Latest milestones: 3.04.03 Latest releases: 3.04.05, 3.04.04, 3.04.03, 3.04.02, 3.04.01, 3.04.00 Bugs targeted: None Blueprints targeted: None This is the stable branch of the 3.4.x release series 3.2.x series Supported Latest releases: 3.02.10, 3.02.09, 3.02.08, 3.02.8, 3.02.07, 3.02.06, 3.02.05, 3.02.04, 3.02.03, 3.02.02, 3.02.01, 3.02.00 Bugs targeted: None Blueprints targeted: None The stable branch for 3.2.x releases 3.0.x series Obsolete Latest releases: 3.0.6 Blueprints targeted: None The 3.0.x stable branch David W. Hartman Global Business Technology Strategy Library Team Disney 336N 407 828 4250 (8-222) FAX 407 828 4868 FOLLOW MY RESEARCH on Backlot & Yammer! Learn about our research partners in the 2011 IT Research Competency Center GBTS CAST can click to request AV Equipment, Books, & Research WATCH the GBTS Library (Video) Update ! CLICK for the GBTS VIRTUAL LIBRARYportal site!! "This communication is confidential, intended only for the named recipients above and may contain trade secrets or other information that is exempt from disclosure under applicable law. Any use, dissemination, distribution or copying of this communication by anyone other than the named recipients is strictly prohibited. If you have received this communication in error, please immediately notify us by calling (407) 828-4250. Thank you." [cid:image001.gif at 01CC842A.60F7D7D0]Please consider your environmental responsibility before printing this e-mail [cid:image001.gif at 01CC842A.60F7D7D0] Think Environmentality! Reduce! Reuse! Recycle! _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 2028 bytes Desc: image001.gif URL: From ian.walls at bywatersolutions.com Thu Oct 6 20:38:25 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Thu, 6 Oct 2011 14:38:25 -0400 Subject: [Koha-devel] Koha 3.05 In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: David, You're already a little beyond 3.4.5! Version 3.05.00.011 is the most current database version, so it looks like you're running a Git install on master, with a very recent pull. You could always stand to do another git pull... there have been new bug fixes and features since this thread started, even! Cheers, -Ian On Thu, Oct 6, 2011 at 1:18 PM, Hartman, David W. - GBTS Library < David.W.Hartman at disney.com> wrote: > I think we can use Git. And our current version is 3.05.00.011**** > > ** ** > > We?d love to jump straight to 3.4.5 (the system can be offline for hours > ? we could run it overnight, etc.)**** > > ** ** > > *From:* Ian Walls [mailto:ian.walls at bywatersolutions.com] > *Sent:* Thursday, October 06, 2011 11:56 AM > *To:* Hartman, David W. - GBTS Library > *Cc:* koha-devel > *Subject:* Re: [Koha-devel] Koha 3.05**** > > ** ** > > David, > > > What type of installation do you have? Tarball or Git? This will inform > the best upgrade method for you. > > When you say you're on Koha 3.05, do you mean 3.00.05, or 3.05.00? The > former is the now obsolete Koha 3.0 line, while the latter is the dev > version for Koha 3.6 (which would indicate to me you have a Git install) > > Whatever your installation type and path, you won't need to install each > intermediate version; you can jump straight from Koha 3.0.5 to Koha 3.4.5 if > you wish, though it will take a fair amount of time to process all the > updates. > > Cheers, > > > -Ian**** > > 2011/10/6 Hartman, David W. - GBTS Library *** > * > > I would like to upgrade from Koha 3.05 to the latest version ..**** > > **** > > I want to tell my technical person the install path? Do I need to do each > install to upgrade. **** > > **** > > *3.4.x series **Current Stable Release* > **** > > Latest milestones: 3.04.03 Latest releases: > 3.04.05 , 3.04.04, > 3.04.03 , 3.04.02, > 3.04.01 , 3.04.00 > **** > > Bugs targeted: None > Blueprints targeted: None **** > > This is the stable branch of the 3.4.x release series**** > > *3.2.x series **Supported* **** > > Latest releases: 3.02.10 , > 3.02.09 , 3.02.08, > 3.02.8 , 3.02.07, > 3.02.06 , 3.02.05, > 3.02.04 , 3.02.03, > 3.02.02 , 3.02.01, > 3.02.00 **** > > Bugs targeted: None > Blueprints targeted: None **** > > The stable branch for 3.2.x releases**** > > *3.0.x series **Obsolete* **** > > Latest releases: 3.0.6 **** > > Blueprints targeted: None **** > > The 3.0.x stable branch**** > > **** > > *David W. Hartman* > Global Business Technology Strategy Library > Team Disney 336N > 407 828 4250 (8-222) > FAX 407 828 4868 > > FOLLOW MY RESEARCH on Backlot & Yammer > ! > Learn about our research partners in the 2011 IT Research Competency > Center > GBTS CAST can click to request AV Equipment, > Books , & Research > WATCH the GBTS Library (Video) Update ! > CLICK for the GBTS VIRTUAL LIBRARY portal > site!!**** > > "This communication is confidential, intended only for the named recipients > above and may contain trade secrets or other information that is exempt from > disclosure under applicable law. Any use, dissemination, distribution or > copying of this communication by anyone other than the named recipients is > strictly prohibited. If you have received this communication in error, > please immediately notify us by calling (407) 828-4250. Thank you."**** > > [image: cid:075452218 at 28012009-07E4]*Please consider your environmental > responsibility before printing this e-mail* *[image: > cid:075452218 at 28012009-07EB]***** > > *Think Environmentality! Reduce! Reuse! Recycle!***** > > **** > > **** > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/**** > > > > > -- > Ian Walls > Lead Development Specialist > ByWater Solutions > Phone # (888) 900-8944 > http://bywatersolutions.com > ian.walls at bywatersolutions.com > Twitter: @sekjal**** > -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2028 bytes Desc: not available URL: From bob at calyx.net.au Fri Oct 7 00:56:29 2011 From: bob at calyx.net.au (Bob Birchall) Date: Fri, 07 Oct 2011 09:56:29 +1100 Subject: [Koha-devel] Koha 3.05 In-Reply-To: References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: <4E8E321D.7000105@calyx.net.au> On 07/10/11 05:38, Ian Walls wrote: > David, > > > You're already a little beyond 3.4.5! Version 3.05.00.011 is the most > current database version, so it looks like you're running a Git > install on master, with a very recent pull. You could always stand to > do another git pull... there have been new bug fixes and features > since this thread started, even! > > Cheers, > > > -Ian To explain further, if Ian will forgive me, 3.4.5 is shorthand for 3.04.05 - hence its previous to 3.05.00. Bob Calyx > > On Thu, Oct 6, 2011 at 1:18 PM, Hartman, David W. - GBTS Library > > wrote: > > I think we can use Git. And our current version is 3.05.00.011 > > We?d love to jump straight to 3.4.5 (the system can be offline > for hours ? we could run it overnight, etc.) > > *From:*Ian Walls [mailto:ian.walls at bywatersolutions.com > ] > *Sent:* Thursday, October 06, 2011 11:56 AM > *To:* Hartman, David W. - GBTS Library > *Cc:* koha-devel > *Subject:* Re: [Koha-devel] Koha 3.05 > > David, > > > What type of installation do you have? Tarball or Git? This will > inform the best upgrade method for you. > > When you say you're on Koha 3.05, do you mean 3.00.05, or > 3.05.00? The former is the now obsolete Koha 3.0 line, while the > latter is the dev version for Koha 3.6 (which would indicate to me > you have a Git install) > > Whatever your installation type and path, you won't need to > install each intermediate version; you can jump straight from Koha > 3.0.5 to Koha 3.4.5 if you wish, though it will take a fair amount > of time to process all the updates. > > Cheers, > > > -Ian > > 2011/10/6 Hartman, David W. - GBTS Library > > > > I would like to upgrade from Koha 3.05 to the latest version .. > > I want to tell my technical person the install path? Do I need to > do each install to upgrade. > > *3.4.x series */Current Stable > Release/ > > Latest milestones: 3.04.03 > Latest > releases: 3.04.05 , > 3.04.04 , 3.04.03 > , 3.04.02 > , 3.04.01 > , 3.04.00 > > > Bugs targeted: None > Blueprints targeted: None > > This is the stable branch of the 3.4.x release series > > *3.2.x series */Supported/ > > Latest releases: 3.02.10 > , 3.02.09 > , 3.02.08 > , 3.02.8 > , 3.02.07 > , 3.02.06 > , 3.02.05 > , 3.02.04 > , 3.02.03 > , 3.02.02 > , 3.02.01 > , 3.02.00 > > > Bugs targeted: None > Blueprints targeted: None > > The stable branch for 3.2.x releases > > *3.0.x series */Obsolete/ > > Latest releases: 3.0.6 > > Blueprints targeted: None > > The 3.0.x stable branch > > */David W. Hartman/* > Global Business Technology Strategy Library > Team Disney 336N > 407 828 4250 (8-222) > FAX 407 828 4868 > > FOLLOW MY RESEARCH on Backlot & > Yammer ! > Learn about our research partners in the2011 IT Research > Competency Center > GBTS CAST can click to requestAV Equipment > , Books > , & Research > > WATCH the GBTS Library (Video) Update > ! > CLICK for the GBTS VIRTUAL LIBRARY > portal site!! > > "This communication is confidential, intended only for the named > recipients above and may contain trade secrets or other > information that is exempt from disclosure under applicable law. > Any use, dissemination, distribution or copying of this > communication by anyone other than the named recipients is > strictly prohibited. If you have received this communication in > error, please immediately notify us by calling (407) 828-4250 > . Thank you." > > cid:075452218 at 28012009-07E4*Please consider your environmental > responsibility before printing this e-mail* > *cid:075452218 at 28012009-07EB* > > *Think Environmentality! Reduce! Reuse! Recycle!* > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > > > > > -- > Ian Walls > Lead Development Specialist > ByWater Solutions > Phone # (888) 900-8944 > http://bywatersolutions.com > ian.walls at bywatersolutions.com > Twitter: @sekjal > > > > > -- > Ian Walls > Lead Development Specialist > ByWater Solutions > Phone # (888) 900-8944 > http://bywatersolutions.com > ian.walls at bywatersolutions.com > Twitter: @sekjal > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Bob Birchall Director Calyx Group Pty Limited Mob: 0414 796 988 Email: bob at calyx.net.au Web: www.calyx.net.au Participating in the Koha Open ILS project: http://koha-community.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 2028 bytes Desc: not available URL: From David.W.Hartman at disney.com Fri Oct 7 01:31:53 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Thu, 6 Oct 2011 19:31:53 -0400 Subject: [Koha-devel] Koha 3.05 In-Reply-To: <4E8E321D.7000105@calyx.net.au> References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> <4E8E321D.7000105@calyx.net.au> Message-ID: <3E19441498923443B9DBE2FE1C0E70B60447DD0AE2@SM-FLOR-VXMB04B.wdw.disney.com> Thanks Bob! So ? to get the patches that fixed the ?detect duplicates? error I was having ?. I need to do another git pull for the same version I have, right? From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Bob Birchall Sent: Thursday, October 06, 2011 6:56 PM To: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Koha 3.05 On 07/10/11 05:38, Ian Walls wrote: David, You're already a little beyond 3.4.5! Version 3.05.00.011 is the most current database version, so it looks like you're running a Git install on master, with a very recent pull. You could always stand to do another git pull... there have been new bug fixes and features since this thread started, even! Cheers, -Ian To explain further, if Ian will forgive me, 3.4.5 is shorthand for 3.04.05 - hence its previous to 3.05.00. Bob Calyx On Thu, Oct 6, 2011 at 1:18 PM, Hartman, David W. - GBTS Library > wrote: I think we can use Git. And our current version is 3.05.00.011 We?d love to jump straight to 3.4.5 (the system can be offline for hours ? we could run it overnight, etc.) From: Ian Walls [mailto:ian.walls at bywatersolutions.com] Sent: Thursday, October 06, 2011 11:56 AM To: Hartman, David W. - GBTS Library Cc: koha-devel Subject: Re: [Koha-devel] Koha 3.05 David, What type of installation do you have? Tarball or Git? This will inform the best upgrade method for you. When you say you're on Koha 3.05, do you mean 3.00.05, or 3.05.00? The former is the now obsolete Koha 3.0 line, while the latter is the dev version for Koha 3.6 (which would indicate to me you have a Git install) Whatever your installation type and path, you won't need to install each intermediate version; you can jump straight from Koha 3.0.5 to Koha 3.4.5 if you wish, though it will take a fair amount of time to process all the updates. Cheers, -Ian 2011/10/6 Hartman, David W. - GBTS Library > I would like to upgrade from Koha 3.05 to the latest version .. I want to tell my technical person the install path? Do I need to do each install to upgrade. 3.4.x series Current Stable Release Latest milestones: 3.04.03 Latest releases: 3.04.05, 3.04.04, 3.04.03, 3.04.02, 3.04.01, 3.04.00 Bugs targeted: None Blueprints targeted: None This is the stable branch of the 3.4.x release series 3.2.x series Supported Latest releases: 3.02.10, 3.02.09, 3.02.08, 3.02.8, 3.02.07, 3.02.06, 3.02.05, 3.02.04, 3.02.03, 3.02.02, 3.02.01, 3.02.00 Bugs targeted: None Blueprints targeted: None The stable branch for 3.2.x releases 3.0.x series Obsolete Latest releases: 3.0.6 Blueprints targeted: None The 3.0.x stable branch David W. Hartman Global Business Technology Strategy Library Team Disney 336N 407 828 4250 (8-222) FAX 407 828 4868 FOLLOW MY RESEARCH on Backlot & Yammer! Learn about our research partners in the 2011 IT Research Competency Center GBTS CAST can click to request AV Equipment, Books, & Research WATCH the GBTS Library (Video) Update ! CLICK for the GBTS VIRTUAL LIBRARYportal site!! "This communication is confidential, intended only for the named recipients above and may contain trade secrets or other information that is exempt from disclosure under applicable law. Any use, dissemination, distribution or copying of this communication by anyone other than the named recipients is strictly prohibited. If you have received this communication in error, please immediately notify us by calling (407) 828-4250. Thank you." [cid:image001.gif at 01CC845E.9A6C41C0]Please consider your environmental responsibility before printing this e-mail [cid:image001.gif at 01CC845E.9A6C41C0] Think Environmentality! Reduce! Reuse! Recycle! _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -- Bob Birchall Director Calyx Group Pty Limited Mob: 0414 796 988 Email: bob at calyx.net.au Web: www.calyx.net.au Participating in the Koha Open ILS project: http://koha-community.org -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 2028 bytes Desc: image001.gif URL: From mtj at kohaaloha.com Fri Oct 7 02:48:04 2011 From: mtj at kohaaloha.com (Mason James) Date: Fri, 7 Oct 2011 13:48:04 +1300 Subject: [Koha-devel] Koha 3.05 In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60447DD0AE2@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> <4E8E321D.7000105@calyx.net.au> <3E19441498923443B9DBE2FE1C0E70B60447DD0AE2@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: On 2011-10-7, at 12:31 PM, Hartman, David W. - GBTS Library wrote: > Thanks Bob! > > So ? to get the patches that fixed the ?detect duplicates? error I was having ?. I need to do another git pull for the same version I have, right? if you ?are? running 3.5.0 - then you already have that patch, for that bug so there's no need for you to do anything... -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 535 bytes Desc: This is a digitally signed message part URL: From mtj at kohaaloha.com Fri Oct 7 03:30:02 2011 From: mtj at kohaaloha.com (Mason James) Date: Fri, 7 Oct 2011 14:30:02 +1300 Subject: [Koha-devel] Koha 3.05 In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B604484C3134@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> <4E8E321D.7000105@calyx.net.au> <3E19441498923443B9DBE2FE1C0E70B60447DD0AE2@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B604484C3134@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: On 2011-10-7, at 2:01 PM, Hartman, David W. - GBTS Library wrote: > Hello James, > > Yes, but I cannot get the "detect duplicates" to work when importing records. This error was reported and patched after I installed. How do I get the patch update? nope, this error was patched *before* you installed here's your bug.... http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6713 and here's the Koha release with the patch for your bug http://koha-community.org/koha-3-4-4/ 6713 critical marc import not matching <<<<<<<<<<<<<<<<<<<<<<<<<< so... your Koha already has that patch... -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 535 bytes Desc: This is a digitally signed message part URL: From David.W.Hartman at disney.com Fri Oct 7 03:47:16 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Thu, 6 Oct 2011 21:47:16 -0400 Subject: [Koha-devel] Koha 3.05 In-Reply-To: References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> <4E8E321D.7000105@calyx.net.au> <3E19441498923443B9DBE2FE1C0E70B60447DD0AE2@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B604484C3134@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: <3E19441498923443B9DBE2FE1C0E70B60447DD0AED@SM-FLOR-VXMB04B.wdw.disney.com> Thanks for your patience James, I just tried to import 510 records, all of which have identical ISBNS (020 field) to the 3000 records in my Koha database and I am still getting the "0 records with at least one match in catalog per matching rule "ISBN". Let me recap because I need your help and there has to be an answer to this. I installed version 3.05.00.011 over a month ago, before I reported the bug - I just heard about the patch recently so I am eager to continue importing records (and items). I am not technical at all but don't I need to do something to "get" the patch installed? Or, if I have this patch, how do I "apply" it to my computer? Bottom line is I still do not have the duplicate detection working. All 510 new imports have identical ISBNs to existing records -- I imported only the first copy of book records, now I am adding the 510 "second copies" records. All should match. -----Original Message----- From: Mason James [mailto:mtj at kohaaloha.com] Sent: Thursday, October 06, 2011 9:30 PM To: Hartman, David W. - GBTS Library Cc: koha-devel Subject: Re: [Koha-devel] Koha 3.05 On 2011-10-7, at 2:01 PM, Hartman, David W. - GBTS Library wrote: > Hello James, > > Yes, but I cannot get the "detect duplicates" to work when importing records. This error was reported and patched after I installed. How do I get the patch update? nope, this error was patched *before* you installed here's your bug.... http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6713 and here's the Koha release with the patch for your bug http://koha-community.org/koha-3-4-4/ 6713 critical marc import not matching <<<<<<<<<<<<<<<<<<<<<<<<<< so... your Koha already has that patch... From mtj at kohaaloha.com Fri Oct 7 09:56:26 2011 From: mtj at kohaaloha.com (Mason James) Date: Fri, 7 Oct 2011 20:56:26 +1300 Subject: [Koha-devel] Koha 3.05 In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60447DD0AED@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> <4E8E321D.7000105@calyx.net.au> <3E19441498923443B9DBE2FE1C0E70B60447DD0AE2@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B604484C3134@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0AED@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: On 2011-10-7, at 2:47 PM, Hartman, David W. - GBTS Library wrote: > Thanks for your patience James, > > I am not technical at all but don't I need to do something to "get" the patch installed? Or, if I have this patch, how do I "apply" it to my computer? your release of Koha already has this patch, you don't need to apply anything > > Bottom line is I still do not have the duplicate detection working. All 510 new imports have identical ISBNs to existing records -- I imported only the first copy of book records, now I am adding the 510 "second copies" records. All should match. i recommend you update the bug report, with your problem http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6713 describe the steps you took (screenshots are good here) and please attach a problematic MARC record(s) to the bug, so others can test your problem -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 535 bytes Desc: This is a digitally signed message part URL: From ian.walls at bywatersolutions.com Fri Oct 7 13:37:34 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Fri, 7 Oct 2011 07:37:34 -0400 Subject: [Koha-devel] Koha 3.05 In-Reply-To: References: <3E19441498923443B9DBE2FE1C0E70B60447DD0A95@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0ABA@SM-FLOR-VXMB04B.wdw.disney.com> <4E8E321D.7000105@calyx.net.au> <3E19441498923443B9DBE2FE1C0E70B60447DD0AE2@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B604484C3134@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0AED@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: David, Try editing your ISBN matching rule; there may be some data corruption resulting from the bug, and doing a quick tidy in the Admin area would resave that data correctly. -Ian 2011/10/7 Mason James > > On 2011-10-7, at 2:47 PM, Hartman, David W. - GBTS Library wrote: > > > Thanks for your patience James, > > > > > I am not technical at all but don't I need to do something to "get" the > patch installed? Or, if I have this patch, how do I "apply" it to my > computer? > > your release of Koha already has this patch, you don't need to apply > anything > > > > > Bottom line is I still do not have the duplicate detection working. All > 510 new imports have identical ISBNs to existing records -- I imported only > the first copy of book records, now I am adding the 510 "second copies" > records. All should match. > > > i recommend you update the bug report, with your problem > http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6713 > > describe the steps you took (screenshots are good here) > and please attach a problematic MARC record(s) to the bug, so others can > test your problem > > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Fri Oct 7 18:09:23 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Fri, 07 Oct 2011 18:09:23 +0200 Subject: [Koha-devel] sending patches to koha-patches mailing list ? Message-ID: <4E8F2433.9030302@biblibre.com> Hello everybody, The workflow we have atm is to send all patches to the koha-patches mailing-list. New ones, as well as signed-off. I think it's a good idea for new patches, that's a good source to see what has been submitted, even if we also have other sources. But for signed-off patches, I think it's useless time-consuming: - the signoff is also in the bug itself, having it in the mailing list add nothing. (we also have KohaGBSD that automatically tweets all status changes, plus "signed-off" query on bugzilla) - with git bz, we have a very fast and handy way to retrieve & send patches to the bug, so who still uses patches from the mailing list ? (note: if you don't use git bz, you should ! see http://wiki.koha-community.org/wiki/Git_bz_configuration) So I suggest to update our rule to request sending only new patches to the mailing list. Your opinion ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From mjr at phonecoop.coop Fri Oct 7 20:17:30 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Fri, 7 Oct 2011 19:17:30 +0100 (BST) Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <4E8F2433.9030302@biblibre.com> Message-ID: <20111007181730.967C19F0E8@nail.towers.org.uk> Paul Poulain [...] > So I suggest to update our rule to request sending only new patches to > the mailing list. > Your opinion ? Unless anyone's actually using the signed-off patches on the list, I think that's a fine update, until we get a smarter list archiver. I admit, I don't use the patches list much any more apart from posting links into bugs.k-c each month. Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From paul.a at aandc.org Sat Oct 8 17:48:50 2011 From: paul.a at aandc.org (Paul) Date: Sat, 08 Oct 2011 11:48:50 -0400 Subject: [Koha-devel] memcached and repcached Message-ID: <5.2.1.1.2.20111008114001.05b89b08@stormy.ca> In an effort to get maximum performance (read speed) out of the latest Koha (3.04.05 -- hope to have it in production next week), I looked at memcached, then found repcached which might or might not help -- it might even be DOA, but then again it might help using two IPs for koha and koha-admin Has anyone else looked into or fiddled with this? tnx Paul Tired old sys-admin From cnighswonger at foundations.edu Sun Oct 9 04:26:56 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Sat, 8 Oct 2011 22:26:56 -0400 Subject: [Koha-devel] Koha Master Running on Win32 Platform Message-ID: For anyone who may be interested, I've the master branch of Koha running on Windows XP. I have documented steps which should be reproducible on the wiki [1] for anyone wanting to have a go at it. I'd love to see someone else be able to have a try. There are a few changes which must be made in to code. I will push my work up to my public git repo sometime this week so you can grab them there until I have time to submit them for inclusion in master branch. This is somewhat of a winding, long-term, no-definite-end sort of project for me, so if you want more, you're welcome to jump in and help. I'm not sending this to the user's list because it is by no means intended for general consumption and is still very pre-alpha. Many thanks to Curtis Jewell and the folks who maintain Strawberry Perl [2] for adding a number of key modules to help get Koha running under Strawberry. Kind Regards, Chris [1] http://wiki.koha-community.org/wiki/Koha_3.4 [2] http://www.nntp.perl.org/group/perl.win32.vanilla/2010/01/msg196.html -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisc at catalyst.net.nz Sun Oct 9 23:22:02 2011 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Mon, 10 Oct 2011 10:22:02 +1300 Subject: [Koha-devel] String freeze for 3.6.0 Message-ID: <20111009212202.GY28240@rorohiko.wgtn.cat-it.co.nz> Ok whanau We have hit string freeze, what this means is now any patches that change strings have to be considered quite heavily, because it will make it harder for the translators. Fr?d?ric if you could make the .po files for 3.6 that would be execllent. Now, what is my plan from here, patches that are in signed off state, that don't touch templates, can still go in provided the pass QA. Ones that do change templates, if they are criticals or blockers, they will still go in. Features: My inclination is push any features that are signed off now, or were submitted for sign off before the feature freeze, and that pass qa. My theory for this is, if they miss translation, that can be fixed by 3.6.1 which is only a month later. If they miss going into 3.6.0 they need to wait for 3.8.0 which is 6 months. If this sounds bad to anyone, please object, but that is the current system I am working to Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From robin at catalyst.net.nz Mon Oct 10 00:48:01 2011 From: robin at catalyst.net.nz (Robin Sheat) Date: Mon, 10 Oct 2011 11:48:01 +1300 Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <20111007181730.967C19F0E8@nail.towers.org.uk> References: <20111007181730.967C19F0E8@nail.towers.org.uk> Message-ID: <1318200481.6421.4.camel@zarathud> Op vrijdag 07-10-2011 om 19:17 uur [tijdzone +0100], schreef MJ Ray: > > Unless anyone's actually using the signed-off patches on the list, > I think that's a fine update, until we get a smarter list archiver. I tend to agree. > I admit, I don't use the patches list much any more apart from posting > links into bugs.k-c each month. I use it to see what's going by that's of interest, that's about it. But I'm no release manager, so maybe it's of more use to them. (also: seconding Paul's mention of git bz, it's a huge time-and-hassle-saver.) -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From Katrin.Fischer at bsz-bw.de Mon Oct 10 09:38:06 2011 From: Katrin.Fischer at bsz-bw.de (Fischer, Katrin) Date: Mon, 10 Oct 2011 09:38:06 +0200 Subject: [Koha-devel] String freeze for 3.6.0 In-Reply-To: <20111009212202.GY28240@rorohiko.wgtn.cat-it.co.nz> References: <20111009212202.GY28240@rorohiko.wgtn.cat-it.co.nz> Message-ID: <028B1A54D03E7B4482CDCA4EC8F06BFD01805AF2@Bodensee.bsz-bw.de> +1 for including some features after string freeze. Perhaps we can have another update to the po files on Pootle shortly before or after release. So people can finish translation and use the files directly from Pootle for generating their translated templates. Katrin > -----Original Message----- > From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel- > bounces at lists.koha-community.org] On Behalf Of Chris Cormack > Sent: Sunday, October 09, 2011 11:22 PM > To: koha-devel at lists.koha-community.org > Cc: koha-translate at lists.koha-community.org > Subject: [Koha-devel] String freeze for 3.6.0 > > Ok whanau > > We have hit string freeze, what this means is now any patches that change > strings have to be considered quite heavily, because it will make it harder > for the translators. > > Fr?d?ric if you could make the .po files for 3.6 that would be execllent. > > Now, what is my plan from here, patches that are in signed off state, that > don't touch templates, can still go in provided the pass QA. > > Ones that do change templates, if they are criticals or blockers, they will > still go in. > > Features: My inclination is push any features that are signed off now, or > were submitted for sign off before the feature freeze, and that pass qa. > My theory for this is, if they miss translation, that can be fixed by > 3.6.1 which is only a month later. If they miss going into 3.6.0 they need > to wait for 3.8.0 which is 6 months. > > If this sounds bad to anyone, please object, but that is the current system > I am working to > > Chris > -- > Chris Cormack > Catalyst IT Ltd. > +64 4 803 2238 > PO Box 11-053, Manners St, Wellington 6142, New Zealand From paul.poulain at biblibre.com Mon Oct 10 09:50:27 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Mon, 10 Oct 2011 09:50:27 +0200 Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <1318200481.6421.4.camel@zarathud> References: <20111007181730.967C19F0E8@nail.towers.org.uk> <1318200481.6421.4.camel@zarathud> Message-ID: <4E92A3C3.1010309@biblibre.com> Le 10/10/2011 00:48, Robin Sheat a ?crit : > (also: seconding Paul's mention of git bz, it's a huge > time-and-hassle-saver.) What would be absolutly WONDERFUL would be to add a parameter to update the patch status. Something like : "git bz attach -status signed-off 4321 HEAD " Plus fixing the bug that makes attaching more than one patch at a time impossible. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From chrisc at catalyst.net.nz Mon Oct 10 09:58:33 2011 From: chrisc at catalyst.net.nz (Chris Cormack) Date: Mon, 10 Oct 2011 20:58:33 +1300 Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <4E92A3C3.1010309@biblibre.com> References: <20111007181730.967C19F0E8@nail.towers.org.uk> <1318200481.6421.4.camel@zarathud> <4E92A3C3.1010309@biblibre.com> Message-ID: <20111010075832.GC28240@rorohiko.wgtn.cat-it.co.nz> * Paul Poulain (paul.poulain at biblibre.com) wrote: > Le 10/10/2011 00:48, Robin Sheat a ?crit : > > (also: seconding Paul's mention of git bz, it's a huge > > time-and-hassle-saver.) > > What would be absolutly WONDERFUL would be to add a parameter to update > the patch status. > Something like : > "git bz attach -status signed-off 4321 HEAD " > Plus fixing the bug that makes attaching more than one patch at a time > impossible. First i'd like to add a -3 switch so that the apply will use a 3way merge. At the moment if it fails you have to try that manually. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From M.de.Rooy at rijksmuseum.nl Mon Oct 10 10:19:46 2011 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Mon, 10 Oct 2011 08:19:46 +0000 Subject: [Koha-devel] Git whitespace warnings on DOS files In-Reply-To: <4E8DA7B7.7020600@ptfs-europe.com> References: <809BE39CD64BFD4EB9036172EBCCFA313408DB@S-MAIL-1B.rijksmuseum.intra> <4E8DA7B7.7020600@ptfs-europe.com> Message-ID: <809BE39CD64BFD4EB9036172EBCCFA31341CB0@S-MAIL-1B.rijksmuseum.intra> Thanks for replying, Colin. Applying with --whitespace=strip (or fix) does not make a difference. In both cases the errors are shown, but the changes are applied. I would just like to get rid of the warnings, because they are not valid in this case. In a DOS file (such as this file still is), all lines have CR before LF. When a patch generates warnings, it is likely to be ignored. Apparently, the git developers did not yet tackle this line endings issue. -----Oorspronkelijk bericht----- Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Colin Campbell Verzonden: donderdag 6 oktober 2011 15:06 Aan: koha-devel at lists.koha-community.org Onderwerp: Re: [Koha-devel] Git whitespace warnings on DOS files On 06/10/11 12:29, Marcel de Rooy wrote: > Hi all, > > Does anyone of you know how to get rid of whitespace warnings in git in the following scenario. (See also bugzilla patch 6803). > (Note that I am using git version 1.6.0.6.) If you have a higher version and do not have the warnings, please let me know. > I think if you set git config apply.whitespace=strip it will show the error but strip the whitespace errors in applying the patch. C. -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 845 557 5634 (phone) +44 (0) 7759 633626 (mobile) colin.campbell at ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com _______________________________________________ Koha-devel mailing list Koha-devel at 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/ From M.de.Rooy at rijksmuseum.nl Mon Oct 10 10:29:06 2011 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Mon, 10 Oct 2011 08:29:06 +0000 Subject: [Koha-devel] FW: Git whitespace warnings on DOS files Message-ID: <809BE39CD64BFD4EB9036172EBCCFA31341CD0@S-MAIL-1B.rijksmuseum.intra> Chris, Would you mind running dos2unix on the following three xsl files in koha master: [marcel at RKM004 testclone]$ grep -Ulr --include=*.xsl "^M" * koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2MODS3-1.xsl koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2MODS.xsl koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2RDFDC.xsl These three files are the only xsl files in dos format. I could generate a patch for it, but again this will result in lots of whitespace warnings. If you have another idea, please let me know. Marcel -----Oorspronkelijk bericht----- Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Marcel de Rooy Verzonden: maandag 10 oktober 2011 10:20 Aan: koha-devel at lists.koha-community.org Onderwerp: Re: [Koha-devel] Git whitespace warnings on DOS files Thanks for replying, Colin. Applying with --whitespace=strip (or fix) does not make a difference. In both cases the errors are shown, but the changes are applied. I would just like to get rid of the warnings, because they are not valid in this case. In a DOS file (such as this file still is), all lines have CR before LF. When a patch generates warnings, it is likely to be ignored. Apparently, the git developers did not yet tackle this line endings issue. -----Oorspronkelijk bericht----- Van: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] Namens Colin Campbell Verzonden: donderdag 6 oktober 2011 15:06 Aan: koha-devel at lists.koha-community.org Onderwerp: Re: [Koha-devel] Git whitespace warnings on DOS files On 06/10/11 12:29, Marcel de Rooy wrote: > Hi all, > > Does anyone of you know how to get rid of whitespace warnings in git in the following scenario. (See also bugzilla patch 6803). > (Note that I am using git version 1.6.0.6.) If you have a higher version and do not have the warnings, please let me know. > I think if you set git config apply.whitespace=strip it will show the error but strip the whitespace errors in applying the patch. C. -- Colin Campbell Chief Software Engineer, PTFS Europe Limited Content Management and Library Solutions +44 (0) 845 557 5634 (phone) +44 (0) 7759 633626 (mobile) colin.campbell at ptfs-europe.com skype: colin_campbell2 http://www.ptfs-europe.com _______________________________________________ Koha-devel mailing list Koha-devel at 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/ _______________________________________________ Koha-devel mailing list Koha-devel at 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/ From chris at bigballofwax.co.nz Mon Oct 10 11:13:43 2011 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Mon, 10 Oct 2011 22:13:43 +1300 Subject: [Koha-devel] FW: Git whitespace warnings on DOS files In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA31341CD0@S-MAIL-1B.rijksmuseum.intra> References: <809BE39CD64BFD4EB9036172EBCCFA31341CD0@S-MAIL-1B.rijksmuseum.intra> Message-ID: On 10 October 2011 21:29, Marcel de Rooy wrote: > Chris, > Would you mind running dos2unix on the following three xsl files in koha master: > > [marcel at RKM004 testclone]$ grep -Ulr --include=*.xsl ?"^M" * > koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2MODS3-1.xsl > koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2MODS.xsl > koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2RDFDC.xsl > > These three files are the only xsl files in dos format. > I could generate a patch for it, but again this will result in lots of whitespace warnings. Interestingly I get a different result chrisc at rorohiko:~/git/koha$ grep -Ulr --include=*.xsl "^M" * koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2MODS.xsl koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2RDFDC.xsl koha-tmpl/intranet-tmpl/prog/en/xslt/MARC21slim2MODS3-1.xsl (perhaps you didnt do a ctrl-v ctrl-m to create the ^M) I have fixed the line endings on those ones Chris From cnighswonger at foundations.edu Mon Oct 10 15:05:26 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Mon, 10 Oct 2011 09:05:26 -0400 Subject: [Koha-devel] String freeze for 3.6.0 In-Reply-To: <20111009212202.GY28240@rorohiko.wgtn.cat-it.co.nz> References: <20111009212202.GY28240@rorohiko.wgtn.cat-it.co.nz> Message-ID: +1 from me too. Kind Regards, Chris 2011/10/9 Chris Cormack > Ok whanau > > We have hit string freeze, what this means is now any patches that > change strings have to be considered quite heavily, because it will > make it harder for the translators. > > Fr?d?ric if you could make the .po files for 3.6 that would be > execllent. > > Now, what is my plan from here, patches that are in signed off state, > that don't touch templates, can still go in provided the pass QA. > > Ones that do change templates, if they are criticals or blockers, they > will still go in. > > Features: My inclination is push any features that are signed off now, > or were submitted for sign off before the feature freeze, and that > pass qa. > My theory for this is, if they miss translation, that can be fixed by > 3.6.1 which is only a month later. If they miss going into 3.6.0 they > need to wait for 3.8.0 which is 6 months. > > If this sounds bad to anyone, please object, but that is the current > system I am working to > > Chris > -- > Chris Cormack > Catalyst IT Ltd. > +64 4 803 2238 > PO Box 11-053, Manners St, Wellington 6142, New Zealand > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjr at phonecoop.coop Mon Oct 10 17:05:50 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Mon, 10 Oct 2011 16:05:50 +0100 (BST) Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <20111010075832.GC28240@rorohiko.wgtn.cat-it.co.nz> Message-ID: <20111010150550.B4BCF9F0E8@nail.towers.org.uk> > * Paul Poulain (paul.poulain at biblibre.com) wrote: > > What would be absolutly WONDERFUL would be to add a parameter to update > > the patch status. > > Something like : > > "git bz attach -status signed-off 4321 HEAD " > > Plus fixing the bug that makes attaching more than one patch at a time > > impossible. The right way to do that is probably to let git bz attach take arbitrary form input names and values from the bugzilla update form, so the above example would be: git bz attach -cf_patch_status 'Signed Off' 4321 HEAD Chris Cormack > First i'd like to add a -3 switch so that the apply will use a 3way > merge. At the moment if it fails you have to try that manually. That sounds like a good but simple improvement, if only we had more time! Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Webmaster, Debian Developer, Past Koha RM, statistician, former lecturer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for various work through http://www.software.coop/ From f.demians at tamil.fr Mon Oct 10 18:51:40 2011 From: f.demians at tamil.fr (=?UTF-8?B?RnLDqWTDqXJpYyBEZW1pYW5z?=) Date: Mon, 10 Oct 2011 18:51:40 +0200 Subject: [Koha-devel] [Koha-translate] String freeze for 3.6.0 In-Reply-To: References: <20111009212202.GY28240@rorohiko.wgtn.cat-it.co.nz> Message-ID: <4E93229C.3040906@tamil.fr> Translation files for Koha 3.6 are now all available on: http://translate.koha-community.org Dear translators, you're invited to start your (hard) work. Thanks. -- Fr?d?ric DEMIANS http://www.tamil.fr/u/fdemians.html From danielg.koha at gmail.com Mon Oct 10 20:31:25 2011 From: danielg.koha at gmail.com (Daniel Grobani) Date: Mon, 10 Oct 2011 11:31:25 -0700 Subject: [Koha-devel] freenode #koha and #koha-news In-Reply-To: References: Message-ID: Hi Chris, Thanks for the info. How does the role of the news channel differ from that of the newsletter? Cheers, Daniel On Wed, Oct 5, 2011 at 1:02 PM, Chris Nighswonger < cnighswonger at foundations.edu> wrote: > By way of announcement, the Koha Community has secured control of the #koha > namespace on freenode. > > #koha will serve as a backup for our main #koha channel on OFTC. Folks > coming in channel there will receive a message pointing them to the main > channel. > > #koha-news is simply that, a channel for posting Koha related news. huginn > will automatically post any items on the blog feed of www.k-c.org. Feel > free to post any other Koha related news there as well. This replaces the > historic #kohanews channel which will go away at some unknown point when > freenode begins enforcing their new namespace policy. > > Basically we have control of any channel beginning with '#koha-' > > Enjoy! > > Kind Regards, > Chris > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cnighswonger at foundations.edu Tue Oct 11 02:17:40 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Mon, 10 Oct 2011 20:17:40 -0400 Subject: [Koha-devel] freenode #koha and #koha-news In-Reply-To: References: Message-ID: Hey Daniel, At present the news channel picks up notices real-time from the rss feed on the website. Any other news is appropriate there as well, afaik. Kind Regards, Chris On Mon, Oct 10, 2011 at 2:31 PM, Daniel Grobani wrote: > Hi Chris, > > Thanks for the info. How does the role of the news channel differ from that > of the newsletter? > > Cheers, > Daniel > > > On Wed, Oct 5, 2011 at 1:02 PM, Chris Nighswonger < > cnighswonger at foundations.edu> wrote: > >> By way of announcement, the Koha Community has secured control of the >> #koha namespace on freenode. >> >> #koha will serve as a backup for our main #koha channel on OFTC. Folks >> coming in channel there will receive a message pointing them to the main >> channel. >> >> #koha-news is simply that, a channel for posting Koha related news. huginn >> will automatically post any items on the blog feed of www.k-c.org. Feel >> free to post any other Koha related news there as well. This replaces the >> historic #kohanews channel which will go away at some unknown point when >> freenode begins enforcing their new namespace policy. >> >> Basically we have control of any channel beginning with '#koha-' >> >> Enjoy! >> >> Kind Regards, >> Chris >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Tue Oct 11 14:05:55 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 11 Oct 2011 14:05:55 +0200 Subject: [Koha-devel] KohaCon / Hackfest Message-ID: <4E943123.3010104@biblibre.com> Hello koha-devel, I've not a clear view of who comes & stay for the hackfest, and the traveling dates. Could you say please ? 3 of BibLibre are coming. Me, Julian Maurice (developer) and Francois Charbonnier (librarian, project manager), we arrive on friday 28th, 11:55PM we leave on Nov, 8th 3AM (ouch !) We will stay at Vihanginn hotel. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From ian.walls at bywatersolutions.com Tue Oct 11 15:54:12 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Tue, 11 Oct 2011 09:54:12 -0400 Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <20111010150550.B4BCF9F0E8@nail.towers.org.uk> References: <20111010075832.GC28240@rorohiko.wgtn.cat-it.co.nz> <20111010150550.B4BCF9F0E8@nail.towers.org.uk> Message-ID: I find that my workflow for pretty much all development and QA work centers around Bugzilla now. Even when git-bz fails to work as intended, I can still wget the patches and test them. What about looking into a means of auto-generating patches to the patches list when new "Patch" type attachments are added to Bugzilla? This would save everyone a step, and keep the incoming patches synced with the patches on bugs.koha-community.org. For course, as MJ points out, we'd need time to implement such a thing. -Ian On Mon, Oct 10, 2011 at 11:05 AM, MJ Ray wrote: > > * Paul Poulain (paul.poulain at biblibre.com) wrote: > > > What would be absolutly WONDERFUL would be to add a parameter to update > > > the patch status. > > > Something like : > > > "git bz attach -status signed-off 4321 HEAD " > > > Plus fixing the bug that makes attaching more than one patch at a time > > > impossible. > > The right way to do that is probably to let git bz attach take > arbitrary form input names and values from the bugzilla update form, > so the above example would be: > git bz attach -cf_patch_status 'Signed Off' 4321 HEAD > > Chris Cormack > > First i'd like to add a -3 switch so that the apply will use a 3way > > merge. At the moment if it fails you have to try that manually. > > That sounds like a good but simple improvement, if only we had more > time! > > Regards, > -- > MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. > Webmaster, Debian Developer, Past Koha RM, statistician, former lecturer. > In My Opinion Only: see http://mjr.towers.org.uk/email.html > Available for hire for various work through http://www.software.coop/ > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Tue Oct 11 15:58:45 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 11 Oct 2011 15:58:45 +0200 Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: References: <20111010075832.GC28240@rorohiko.wgtn.cat-it.co.nz> <20111010150550.B4BCF9F0E8@nail.towers.org.uk> Message-ID: <4E944B95.7020505@biblibre.com> Le 11/10/2011 15:54, Ian Walls a ?crit : > I find that my workflow for pretty much all development and QA work centers > around Bugzilla now. Even when git-bz fails to work as intended, I can > still wget the patches and test them. > > What about looking into a means of auto-generating patches to the patches > list when new "Patch" type attachments are added to Bugzilla? This would > save everyone a step, and keep the incoming patches synced with the patches > on bugs.koha-community.org. +1 (I'm so happy with those tools that I could volunteer to do it, but I don't have the skills, sorry...) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From mglavica at ffzg.hr Tue Oct 11 19:32:30 2011 From: mglavica at ffzg.hr (Marijana Glavica) Date: Tue, 11 Oct 2011 19:32:30 +0200 Subject: [Koha-devel] KohaCon / Hackfest In-Reply-To: <4E943123.3010104@biblibre.com> References: <4E943123.3010104@biblibre.com> Message-ID: On Tue, Oct 11, 2011 at 2:05 PM, Paul Poulain wrote: > Hello koha-devel, > > I've not a clear view of who comes & stay for the hackfest, and the > traveling dates. Could you say please ? > > 3 of BibLibre are coming. Me, Julian Maurice (developer) and Francois > Charbonnier (librarian, project manager), we arrive on friday 28th, > 11:55PM we leave on Nov, 8th 3AM (ouch !) > We will stay at Vihanginn hotel. > > Dobrica Pavlinusic (systems librarian) and me (librarian and systems librarian) from Croatia are coming on Oct 30 early in the morning and will leave on Nov 7 We will stay at Royal In hotel. -- Marijana Glavica Psychology Librarian and Systems Librarian Faculty of Humanities and Social Sciences Library University of Zagreb, Croatia http://knjiznica.ffzg.unizg.hr/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin at catalyst.net.nz Tue Oct 11 23:58:07 2011 From: robin at catalyst.net.nz (Robin Sheat) Date: Wed, 12 Oct 2011 10:58:07 +1300 Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: References: <20111010075832.GC28240@rorohiko.wgtn.cat-it.co.nz> <20111010150550.B4BCF9F0E8@nail.towers.org.uk> Message-ID: <1318370287.6421.49.camel@zarathud> Op dinsdag 11-10-2011 om 09:54 uur [tijdzone -0400], schreef Ian Walls: > What about looking into a means of auto-generating patches to the > patches list when new "Patch" type attachments are added to Bugzilla? > This would save everyone a step, and keep the incoming patches synced > with the patches on bugs.koha-community.org. Keep in mind that sending to the list is very easy, maybe people are doing it the hard way. What I do is: git bz attach HEAD git send-email --to=kpatches HEAD^ press enter and 'y' a few times, and it's done. You could probably wrap this up in a script if you wanted. (note the slightly different commit reference, and 'kpatches' is an alias I set up for the patches list.) This said, auto-sending from bugzilla would be great, I'm just hoping to make it easier until someone finds the time to do that :) -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From robin at catalyst.net.nz Wed Oct 12 00:02:55 2011 From: robin at catalyst.net.nz (Robin Sheat) Date: Wed, 12 Oct 2011 11:02:55 +1300 Subject: [Koha-devel] KohaCon / Hackfest In-Reply-To: References: <4E943123.3010104@biblibre.com> Message-ID: <1318370575.6421.52.camel@zarathud> Op dinsdag 11-10-2011 om 19:32 uur [tijdzone +0200], schreef Marijana Glavica: > Dobrica Pavlinusic (systems librarian) and me (librarian and systems > librarian) from Croatia are coming on Oct 30 early in the morning and > will leave on Nov 7 > We will stay at Royal In hotel. I'm going to be there, arriving late on the 29th, leaving early on the 7th. Staying at Vihang's Inn. At least, provided my visa arrives. Should probably chase that up. -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From ian.walls at bywatersolutions.com Wed Oct 12 00:39:26 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Tue, 11 Oct 2011 18:39:26 -0400 Subject: [Koha-devel] KohaCon / Hackfest In-Reply-To: <1318370575.6421.52.camel@zarathud> References: <4E943123.3010104@biblibre.com> <1318370575.6421.52.camel@zarathud> Message-ID: The ByWater team will be there sometime on the 28th and taking off late on the 8th, also staying at Vihang's Inn. -Ian 2011/10/11 Robin Sheat > Op dinsdag 11-10-2011 om 19:32 uur [tijdzone +0200], schreef Marijana > Glavica: > > Dobrica Pavlinusic (systems librarian) and me (librarian and systems > > librarian) from Croatia are coming on Oct 30 early in the morning and > > will leave on Nov 7 > > We will stay at Royal In hotel. > > I'm going to be there, arriving late on the 29th, leaving early on the > 7th. Staying at Vihang's Inn. At least, provided my visa arrives. Should > probably chase that up. > > -- > Robin Sheat > Catalyst IT Ltd. > ? +64 4 803 2204 > GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From savitra.sirohi at osslabs.biz Wed Oct 12 05:46:13 2011 From: savitra.sirohi at osslabs.biz (savitra sirohi) Date: Wed, 12 Oct 2011 09:16:13 +0530 Subject: [Koha-devel] KohaCon / Hackfest In-Reply-To: References: <4E943123.3010104@biblibre.com> <1318370575.6421.52.camel@zarathud> Message-ID: Amit and myself will be there from OSS Labs. We have not been to a Koha hackfest before, is it time to starting developing an agenda? Some of the things we would be interested in are: Solr Integration Acquisitions including EDI Serials budgeting and payment Reporting, charting and analysis Thanks, Savitra 2011/10/12 Ian Walls : > The ByWater team will be there sometime on the 28th and taking off late on > the 8th, also staying at Vihang's Inn. > > > -Ian > > 2011/10/11 Robin Sheat >> >> Op dinsdag 11-10-2011 om 19:32 uur [tijdzone +0200], schreef Marijana >> Glavica: >> > Dobrica Pavlinusic (systems librarian) and me (librarian and systems >> > librarian) from Croatia are coming on Oct 30 early in the morning and >> > will leave on Nov 7 >> > We will stay at Royal In hotel. >> >> I'm going to be there, arriving late on the 29th, leaving early on the >> 7th. Staying at Vihang's Inn. At least, provided my visa arrives. Should >> probably chase that up. >> >> -- >> Robin Sheat >> Catalyst IT Ltd. >> ? +64 4 803 2204 >> GPG: 5957 6D23 8B16 EFAB FEF8 ?7175 14D3 6485 A99C EB6D >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ > > > > -- > Ian Walls > Lead Development Specialist > ByWater Solutions > Phone # (888) 900-8944 > http://bywatersolutions.com > ian.walls at bywatersolutions.com > Twitter: @sekjal > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > From bob at calyx.net.au Wed Oct 12 07:59:51 2011 From: bob at calyx.net.au (Bob Birchall) Date: Wed, 12 Oct 2011 16:59:51 +1100 Subject: [Koha-devel] KohaCon / Hackfest In-Reply-To: <4E943123.3010104@biblibre.com> References: <4E943123.3010104@biblibre.com> Message-ID: <4E952CD7.8090608@calyx.net.au> On 11/10/11 23:05, Paul Poulain wrote: > Hello koha-devel, > > I've not a clear view of who comes& stay for the hackfest, and the > traveling dates. Could you say please ? > > 3 of BibLibre are coming. Me, Julian Maurice (developer) and Francois > Charbonnier (librarian, project manager), we arrive on friday 28th, > 11:55PM we leave on Nov, 8th 3AM (ouch !) > We will stay at Vihanginn hotel. Though not much help with the hacking, Irma and I will arrive in Thane on Sunday 30 and will be around until Sunday 6. We'll be in Mumbai on Saturday and Sunday before the conference, so call us if you are about. Bob Birchall Calyx +61 414 796 988 From kmkale at anantcorp.com Wed Oct 12 11:00:13 2011 From: kmkale at anantcorp.com (Koustubha Kale) Date: Wed, 12 Oct 2011 14:30:13 +0530 Subject: [Koha-devel] Kohacon11 participant information Message-ID: Hi All, We need some information about participants. This information will help us estimate numbers of participants, organize local assistance if required and in case of foreign nationals, we are required to submit this to our local police station. Request you to kindly fill the google form here https://docs.google.com/spreadsheet/viewform?hl=en_US&formkey=dEE2LUVkRDVOSlluMnRmaFMtbHkzLWc6MQ#gid=0if you are planning to attend the Kohacon11. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Wed Oct 12 14:06:00 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Wed, 12 Oct 2011 14:06:00 +0200 Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <20111010075832.GC28240@rorohiko.wgtn.cat-it.co.nz> References: <20111007181730.967C19F0E8@nail.towers.org.uk> <1318200481.6421.4.camel@zarathud> <4E92A3C3.1010309@biblibre.com> <20111010075832.GC28240@rorohiko.wgtn.cat-it.co.nz> Message-ID: <4E9582A8.3060901@biblibre.com> Le 10/10/2011 09:58, Chris Cormack a ?crit : > * Paul Poulain (paul.poulain at biblibre.com) wrote: >> Le 10/10/2011 00:48, Robin Sheat a ?crit : >>> (also: seconding Paul's mention of git bz, it's a huge >>> time-and-hassle-saver.) >> >> What would be absolutly WONDERFUL would be to add a parameter to update >> the patch status. >> Something like : >> "git bz attach -status signed-off 4321 HEAD " >> Plus fixing the bug that makes attaching more than one patch at a time >> impossible. > > > First i'd like to add a -3 switch so that the apply will use a 3way > merge. At the moment if it fails you have to try that manually. If someone has the Python skill: edit git-bz, at line 1497, you'll see : process = git.am(filename, _interactive=True ) Changing it to : process = git.am(filename, _interactive=True, 3=True ) should do the trick (i've tested with i=true, and you get the git am -i (interactive) as expected) EXCEPT that python don't like the 3 (or any arg starting with a number), returning a nasty > File "/home/paul/bin/git-bz", line 1497 > process = git.am(filename, _interactive=True, 3=True ) > SyntaxError: keyword can't be an expression I've tried with "3", no success: > File "/home/paul/bin/git-bz", line 1497 > process = git.am(filename, _interactive=True, "3"=True ) > SyntaxError: keyword can't be an expression I've tried with _3, no success either, no python error but git says error: unknown option `-3' I've tried with 3way, "3way", _3way, with 2 starting __ (__3way...) couldn't find the correct syntax. If someone has a suggestion... -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From kmkale at anantcorp.com Wed Oct 12 11:40:58 2011 From: kmkale at anantcorp.com (Koustubha Kale) Date: Wed, 12 Oct 2011 15:10:58 +0530 Subject: [Koha-devel] About Conference & the ggdocs In-Reply-To: <4E955B21.80503@biblibre.com> References: <4E955B21.80503@biblibre.com> Message-ID: Thanks Paul, actually there is no hassle / interaction with the police for you at all. Just something we have to do as organizers. To everybody else, if you are on a tourist visa ( or if you are Indian), its all right not to fill the form as we don't need to send your information to anyone in that case. But we would still like to know your dates of arrival & departure, the hotel you will be staying in, whether you will attend the hackfest, whether you would like to take the day trip etc. This will help us in organizing and in providing you with any assistance if required. So please mail me this information. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2 On Wed, Oct 12, 2011 at 2:47 PM, Paul Poulain wrote: > Hi Kousthuba, > (cc-ed all foreigners I know will participate) > > I'm quite annoyed by the gg docs you just opened. > ( > https://docs.google.com/a/biblibre.com/spreadsheet/viewform?hl=en_US&formkey=dEE2LUVkRDVOSlluMnRmaFMtbHkzLWc6MQ#gid=0if > ) > > It start by: > "Also in case of foreign nationals, we are required to submit this > information to the local police. " > > As you probably know, most of us (all ?) come to india with a "tourist" > passport. So we're not supposed to be here for a conference ! I don't > want to have any problem with your local police, so I won't fill this > document unless you convince me I should ! > > But of course, i'll be at the hackfest (& ready to teach, hack, do many > Koha-related things), and I'm interested by the Mumbai trip, so you can > count on us 3 > > Feel free to catch me on IRC if you want. > -- > Paul POULAIN > http://www.biblibre.com > Expert en Logiciels Libres pour l'info-doc > Tel : (33) 4 91 81 35 08 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From David.W.Hartman at disney.com Thu Oct 13 02:14:18 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Wed, 12 Oct 2011 20:14:18 -0400 Subject: [Koha-devel] Unable to get patches .. "detect duplicates not working" Message-ID: <3E19441498923443B9DBE2FE1C0E70B60447DD0C51@SM-FLOR-VXMB04B.wdw.disney.com> Can any techies help? I know that the detect duplicates was patched (thank you for patching it) .. Here is the bug record bug 6713: 4975 | 5791 To "get" the patch, I just learned that I am not on git after all. We used apt-get. However, I did update the packages last week and we are as current as can be. Here is the installed version: KOHA_INSTALLED_VERSION=3.05.00.011 I just tried to do the following: sudo apt-get upgrade yaz sudo apt-get upgrade zebra sudo apt-get upgrade koha sudo apt-get upgrade I get the same result each time: koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: idzebra-2.0 idzebra-2.0-utils libidzebra-2.0-dev libidzebra-2.0-mod-alvis libidzebra-2.0-mod-dom libidzebra-2.0-mod-grs-marc libidzebra-2.0-mod-grs-regx libidzebra-2.0-mod-grs-xml libidzebra-2.0-mod-text libyaz4 yaz 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded. How can we get the patch? If I have it, then I am stuck cuz Koha is not detecting duplicates when I import the "copy 2" items. My library catalog is full of original "copy 1" records. Now I am adding 500 second copies (my collection was divided into copies when I started the conversion to move to Koha). Sorry to keep posting this .. :( David -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Thu Oct 13 14:36:25 2011 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Thu, 13 Oct 2011 12:36:25 +0000 Subject: [Koha-devel] Sorting >1000 records Message-ID: <809BE39CD64BFD4EB9036172EBCCFA31342FEE@S-MAIL-1B.rijksmuseum.intra> Hi all, Does anyone of you know why search results of >1000 records are not sorted well? Is this a zebra limitation? Should I update zebra for that? I am running idzebra 2.0.43 and yaz 3.0.49 with Koha 3.3. Thanks, Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: From frederic at tamil.fr Thu Oct 13 15:04:34 2011 From: frederic at tamil.fr (=?ISO-8859-1?Q?Fr=E9d=E9ric_Demians?=) Date: Thu, 13 Oct 2011 15:04:34 +0200 Subject: [Koha-devel] Sorting >1000 records In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA31342FEE@S-MAIL-1B.rijksmuseum.intra> References: <809BE39CD64BFD4EB9036172EBCCFA31342FEE@S-MAIL-1B.rijksmuseum.intra> Message-ID: <4E96E1E2.1080601@tamil.fr> > Does anyone of you know why search results of >1000 records are not > sorted well? Is this a zebra limitation? Should I update zebra for > that? Modify your zebra-biblios.cfg file. For example, to increase the max records from a resultset to be used for sorting up to 5000, add this line: sortmax: 5000 Default value is 1000. -- Fr?d?ric DEMIANS http://www.tamil.fr/u/fdemians.html From fridolyn.somers at gmail.com Thu Oct 13 15:27:01 2011 From: fridolyn.somers at gmail.com (Fridolyn SOMERS) Date: Thu, 13 Oct 2011 15:27:01 +0200 Subject: [Koha-devel] Unable to get patches .. "detect duplicates not working" In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60447DD0C61@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD0C51@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0C61@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: I think stable repository will have revisions 3.4.0, 3.4.1, 3.4.2 ... dev repository will have last build package (containing nearly last source revision). But I see that bug 6713 is not yet integrated. Patch is just send. It will need testing and integration before it is integrated in GIT then debian package. You will have to integrate manually this patch. It is not so difficult. Read it to apply it on source. Remove lines begining with - and add lines begining with +. For more, Google is your friend.
On Thu, Oct 13, 2011 at 2:59 PM, Hartman, David W. - GBTS Library < David.W.Hartman at disney.com> wrote: > Fridolyn,**** > > ** ** > > We are using the stable .. should we use the dev? I am > copying in Brian Weissman who has been my savior on this project! J **** > > ** ** > > *From:* Fridolyn SOMERS [mailto:fridolyn.somers at gmail.com] > *Sent:* Thursday, October 13, 2011 8:01 AM > *To:* Hartman, David W. - GBTS Library > *Subject:* Re: [Koha-devel] Unable to get patches .. "detect duplicates > not working"**** > > ** ** > > Hie, > > > Do you use the stable or the dev package repository ? > See > http://wiki.koha-community.org/wiki/Koha_3.2_on_Debian_Squeeze#Development_Version > >
**** > > 2011/10/13 Hartman, David W. - GBTS Library ** > ** > > Can any techies help? **** > > **** > > I know that the detect duplicates was patched (thank you for patching it) > .. Here is the bug record bug 6713: > 4975| 5791 > **** > > **** > > To ?get? the patch, I just learned that I am not on git after all. We used > apt-get. However, I did update the packages last week and we are as current > as can be. Here is the installed version:**** > > **** > > KOHA_INSTALLED_VERSION=3.05.00.011**** > > **** > > I just tried to do the following:**** > > **** > > sudo apt-get upgrade yaz**** > > sudo apt-get upgrade zebra**** > > sudo apt-get upgrade koha**** > > sudo apt-get upgrade**** > > **** > > I get the same result each time:**** > > **** > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get upgrade**** > > Reading package lists... Done**** > > Building dependency tree**** > > Reading state information... Done**** > > The following packages have been kept back:**** > > idzebra-2.0 idzebra-2.0-utils libidzebra-2.0-dev libidzebra-2.0-mod-alvis > **** > > libidzebra-2.0-mod-dom libidzebra-2.0-mod-grs-marc**** > > libidzebra-2.0-mod-grs-regx libidzebra-2.0-mod-grs-xml**** > > libidzebra-2.0-mod-text libyaz4 yaz**** > > 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.**** > > **** > > How can we get the patch? If I have it, then I am stuck cuz Koha is not > detecting duplicates when I import the ?copy 2? items. My library catalog > is full of original ?copy 1? records. Now I am adding 500 second copies (my > collection was divided into copies when I started the conversion to move to > Koha). **** > > **** > > Sorry to keep posting this .. L**** > > * ***** > > *David***** > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/**** > > > > > -- > Fridolyn SOMERS > ICT engineer > PROGILONE - Lyon - France > fridolyn.somers at gmail.com**** > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers at gmail.com -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From ian.walls at bywatersolutions.com Thu Oct 13 15:40:03 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Thu, 13 Oct 2011 09:40:03 -0400 Subject: [Koha-devel] Sorting >1000 records In-Reply-To: <4E96E1E2.1080601@tamil.fr> References: <809BE39CD64BFD4EB9036172EBCCFA31342FEE@S-MAIL-1B.rijksmuseum.intra> <4E96E1E2.1080601@tamil.fr> Message-ID: This reminds me of the maximumRecordSize problem (default 1MB). Would anyone like to volunteer to make these kinds of configurations controllable in koha-conf.xml? :) -Ian 2011/10/13 Fr?d?ric Demians > > Does anyone of you know why search results of >1000 records are not > > sorted well? Is this a zebra limitation? Should I update zebra for > > that? > > Modify your zebra-biblios.cfg file. For example, to increase the max > records from a resultset to be used for sorting up to 5000, add this line: > > sortmax: 5000 > > Default value is 1000. > > -- > Fr?d?ric DEMIANS > http://www.tamil.fr/u/**fdemians.html > > ______________________________**_________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolyn.somers at gmail.com Thu Oct 13 16:24:06 2011 From: fridolyn.somers at gmail.com (Fridolyn SOMERS) Date: Thu, 13 Oct 2011 16:24:06 +0200 Subject: [Koha-devel] Unable to get patches .. "detect duplicates not working" In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60447DD0C6A@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD0C51@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0C61@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0C6A@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: Sorry, I missed it, it has been send to GIT : http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=9b38eccf73b199bf450915ba01236ddf76658a5a On Thu, Oct 13, 2011 at 3:32 PM, Hartman, David W. - GBTS Library < David.W.Hartman at disney.com> wrote: > Ahhh ? so we do not have the patch. I need to tell the list that .. they > kept saying over and over that we had the patch ..**** > > ** ** > > Brian, is this good enough info to try?**** > > ** ** > > *From:* Fridolyn SOMERS [mailto:fridolyn.somers at gmail.com] > *Sent:* Thursday, October 13, 2011 9:27 AM > *To:* koha-devel > *Cc:* Weissman, Brian S.; Hartman, David W. - GBTS Library > > *Subject:* Re: [Koha-devel] Unable to get patches .. "detect duplicates > not working"**** > > ** ** > > I think > stable repository will have revisions 3.4.0, 3.4.1, 3.4.2 ... > dev repository will have last build package (containing nearly last source > revision). > > But I see that bug 6713 is > not yet integrated. Patch is just send. > It will need testing and integration before it is integrated in GIT then > debian package. > > You will have to integrate manually this patch. > It is not so difficult. > Read it to apply it on source. > Remove lines begining with - and add lines begining with +. > > For more, Google is your friend. > >
**** > > On Thu, Oct 13, 2011 at 2:59 PM, Hartman, David W. - GBTS Library < > David.W.Hartman at disney.com> wrote:**** > > Fridolyn,**** > > **** > > We are using the stable .. should we use the dev? I am > copying in Brian Weissman who has been my savior on this project! J **** > > **** > > *From:* Fridolyn SOMERS [mailto:fridolyn.somers at gmail.com] > *Sent:* Thursday, October 13, 2011 8:01 AM > *To:* Hartman, David W. - GBTS Library > *Subject:* Re: [Koha-devel] Unable to get patches .. "detect duplicates > not working"**** > > **** > > Hie,**** > > > > Do you use the stable or the dev package repository ? > See > http://wiki.koha-community.org/wiki/Koha_3.2_on_Debian_Squeeze#Development_Version > >
**** > > 2011/10/13 Hartman, David W. - GBTS Library ** > ** > > Can any techies help? **** > > **** > > I know that the detect duplicates was patched (thank you for patching it) > .. Here is the bug record bug 6713: > 4975| 5791 > **** > > **** > > To ?get? the patch, I just learned that I am not on git after all. We used > apt-get. However, I did update the packages last week and we are as current > as can be. Here is the installed version:**** > > **** > > KOHA_INSTALLED_VERSION=3.05.00.011**** > > **** > > I just tried to do the following:**** > > **** > > sudo apt-get upgrade yaz**** > > sudo apt-get upgrade zebra**** > > sudo apt-get upgrade koha**** > > sudo apt-get upgrade**** > > **** > > I get the same result each time:**** > > **** > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get upgrade**** > > Reading package lists... Done**** > > Building dependency tree**** > > Reading state information... Done**** > > The following packages have been kept back:**** > > idzebra-2.0 idzebra-2.0-utils libidzebra-2.0-dev libidzebra-2.0-mod-alvis > **** > > libidzebra-2.0-mod-dom libidzebra-2.0-mod-grs-marc**** > > libidzebra-2.0-mod-grs-regx libidzebra-2.0-mod-grs-xml**** > > libidzebra-2.0-mod-text libyaz4 yaz**** > > 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.**** > > **** > > How can we get the patch? If I have it, then I am stuck cuz Koha is not > detecting duplicates when I import the ?copy 2? items. My library catalog > is full of original ?copy 1? records. Now I am adding 500 second copies (my > collection was divided into copies when I started the conversion to move to > Koha). **** > > **** > > Sorry to keep posting this .. L**** > > * ***** > > *David***** > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/**** > > > > > -- > Fridolyn SOMERS > ICT engineer > PROGILONE - Lyon - France > fridolyn.somers at gmail.com**** > > > > > -- > Fridolyn SOMERS > ICT engineer > PROGILONE - Lyon - France > fridolyn.somers at gmail.com**** > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers at gmail.com -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From fridolyn.somers at gmail.com Thu Oct 13 16:38:10 2011 From: fridolyn.somers at gmail.com (Fridolyn SOMERS) Date: Thu, 13 Oct 2011 16:38:10 +0200 Subject: [Koha-devel] Unable to get patches .. "detect duplicates not working" In-Reply-To: References: <3E19441498923443B9DBE2FE1C0E70B60447DD0C51@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0C61@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0C6A@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: You can see in release note of Koha 3.4.4 it has been integrated : http://koha-community.org/koha-3-4-4/ I've looked at debian stable repository, its revision is 3.4.5. You should have it by updating. You may have a problem with updating. What is your Debian version ? You may use "Synaptic" program to manage packages and repositories.
On Thu, Oct 13, 2011 at 4:24 PM, Fridolyn SOMERS wrote: > Sorry, > > I missed it, it has been send to GIT : > http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=9b38eccf73b199bf450915ba01236ddf76658a5a > > > On Thu, Oct 13, 2011 at 3:32 PM, Hartman, David W. - GBTS Library < > David.W.Hartman at disney.com> wrote: > >> Ahhh ? so we do not have the patch. I need to tell the list that .. they >> kept saying over and over that we had the patch ..**** >> >> ** ** >> >> Brian, is this good enough info to try?**** >> >> ** ** >> >> *From:* Fridolyn SOMERS [mailto:fridolyn.somers at gmail.com] >> *Sent:* Thursday, October 13, 2011 9:27 AM >> *To:* koha-devel >> *Cc:* Weissman, Brian S.; Hartman, David W. - GBTS Library >> >> *Subject:* Re: [Koha-devel] Unable to get patches .. "detect duplicates >> not working"**** >> >> ** ** >> >> I think >> stable repository will have revisions 3.4.0, 3.4.1, 3.4.2 ... >> dev repository will have last build package (containing nearly last source >> revision). >> >> But I see that bug 6713 is >> not yet integrated. Patch is just send. >> It will need testing and integration before it is integrated in GIT then >> debian package. >> >> You will have to integrate manually this patch. >> It is not so difficult. >> Read it to apply it on source. >> Remove lines begining with - and add lines begining with +. >> >> For more, Google is your friend. >> >>
**** >> >> On Thu, Oct 13, 2011 at 2:59 PM, Hartman, David W. - GBTS Library < >> David.W.Hartman at disney.com> wrote:**** >> >> Fridolyn,**** >> >> **** >> >> We are using the stable .. should we use the dev? I am >> copying in Brian Weissman who has been my savior on this project! J **** >> >> **** >> >> *From:* Fridolyn SOMERS [mailto:fridolyn.somers at gmail.com] >> *Sent:* Thursday, October 13, 2011 8:01 AM >> *To:* Hartman, David W. - GBTS Library >> *Subject:* Re: [Koha-devel] Unable to get patches .. "detect duplicates >> not working"**** >> >> **** >> >> Hie,**** >> >> >> >> Do you use the stable or the dev package repository ? >> See >> http://wiki.koha-community.org/wiki/Koha_3.2_on_Debian_Squeeze#Development_Version >> >>
**** >> >> 2011/10/13 Hartman, David W. - GBTS Library * >> *** >> >> Can any techies help? **** >> >> **** >> >> I know that the detect duplicates was patched (thank you for patching it) >> .. Here is the bug record bug 6713: >> 4975| 5791 >> **** >> >> **** >> >> To ?get? the patch, I just learned that I am not on git after all. We used >> apt-get. However, I did update the packages last week and we are as current >> as can be. Here is the installed version:**** >> >> **** >> >> KOHA_INSTALLED_VERSION=3.05.00.011**** >> >> **** >> >> I just tried to do the following:**** >> >> **** >> >> sudo apt-get upgrade yaz**** >> >> sudo apt-get upgrade zebra**** >> >> sudo apt-get upgrade koha**** >> >> sudo apt-get upgrade**** >> >> **** >> >> I get the same result each time:**** >> >> **** >> >> koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get upgrade**** >> >> Reading package lists... Done**** >> >> Building dependency tree**** >> >> Reading state information... Done**** >> >> The following packages have been kept back:**** >> >> idzebra-2.0 idzebra-2.0-utils libidzebra-2.0-dev >> libidzebra-2.0-mod-alvis**** >> >> libidzebra-2.0-mod-dom libidzebra-2.0-mod-grs-marc**** >> >> libidzebra-2.0-mod-grs-regx libidzebra-2.0-mod-grs-xml**** >> >> libidzebra-2.0-mod-text libyaz4 yaz**** >> >> 0 upgraded, 0 newly installed, 0 to remove and 11 not upgraded.**** >> >> **** >> >> How can we get the patch? If I have it, then I am stuck cuz Koha is not >> detecting duplicates when I import the ?copy 2? items. My library catalog >> is full of original ?copy 1? records. Now I am adding 500 second copies (my >> collection was divided into copies when I started the conversion to move to >> Koha). **** >> >> **** >> >> Sorry to keep posting this .. L**** >> >> * ***** >> >> *David***** >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/**** >> >> >> >> >> -- >> Fridolyn SOMERS >> ICT engineer >> PROGILONE - Lyon - France >> fridolyn.somers at gmail.com**** >> >> >> >> >> -- >> Fridolyn SOMERS >> ICT engineer >> PROGILONE - Lyon - France >> fridolyn.somers at gmail.com**** >> > > > > -- > Fridolyn SOMERS > ICT engineer > PROGILONE - Lyon - France > fridolyn.somers at gmail.com > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers at gmail.com -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From arosello at uci.cu Thu Oct 13 22:01:01 2011 From: arosello at uci.cu (Adnier Rosello Carrazana) Date: Thu, 13 Oct 2011 16:01:01 -0400 (CDT) Subject: [Koha-devel] Problem with Koha to MARC correspondence In-Reply-To: Message-ID: <211ed25e-8dcf-4e17-b5e5-3a43e4fcb904@ucimail4.uci.cu> my greetings, I have defined a correspondence between a new field (userid) in biblioitems table and the MARC Bibliographic records(tag 001 N?mero de control), but, when I insert a new record, the field "userid" is not corresponding with tag 001 value's, it have 0. Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU! http://www.antiterroristas.cu http://justiciaparaloscinco.wordpress.com From mtj at kohaaloha.com Fri Oct 14 13:24:39 2011 From: mtj at kohaaloha.com (Mason James) Date: Sat, 15 Oct 2011 00:24:39 +1300 Subject: [Koha-devel] Unable to get patches .. "detect duplicates not working" In-Reply-To: References: <3E19441498923443B9DBE2FE1C0E70B60447DD0C51@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0C61@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0C6A@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: <4C74034A-731A-49A0-BFD5-53F5FAA713AD@kohaaloha.com> > > On Thu, Oct 13, 2011 at 4:24 PM, Fridolyn SOMERS wrote: > Sorry, > > I missed it, it has been send to GIT : http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=9b38eccf73b199bf450915ba01236ddf76658a5a > > > On Thu, Oct 13, 2011 at 3:32 PM, Hartman, David W. - GBTS Library wrote: > Ahhh ? so we do not have the patch. I need to tell the list that .. they kept saying over and over that we had the patch .. > > > KOHA_INSTALLED_VERSION=3.05.00.011 David the patch for bug 6713 was added in version 3.05.00.008 if you are running 3.05.00.011 - you *have* that patch, (as i keep saying over and over) > > On Thu, Oct 13, 2011 at 2:59 PM, Hartman, David W. - GBTS Library wrote: > > Fridolyn, > > > We are using the stable nope, if you are running 3.05.xxxxx you are running a DEV Koha release > .. should we use the dev? you already are.. i hope this makes some sense cheers, Mason -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 535 bytes Desc: This is a digitally signed message part URL: From Brian.S.Weissman at disney.com Fri Oct 14 14:32:01 2011 From: Brian.S.Weissman at disney.com (Weissman, Brian S.) Date: Fri, 14 Oct 2011 08:32:01 -0400 Subject: [Koha-devel] Unable to get patches .. "detect duplicates not working" In-Reply-To: <4C74034A-731A-49A0-BFD5-53F5FAA713AD@kohaaloha.com> References: <3E19441498923443B9DBE2FE1C0E70B60447DD0C51@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0C61@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60447DD0C6A@SM-FLOR-VXMB04B.wdw.disney.com> <4C74034A-731A-49A0-BFD5-53F5FAA713AD@kohaaloha.com> Message-ID: <1B81ADAC73500E47B91DF0E0E556C7891EC1532A27@SM-FLOR-VXMB06A.wdw.disney.com> Mason, You are correct. We are using DEV. But you knew that already. :) Most of my apt.sources was pointing to the stable packages. The last line, the koha line, was pointing to dev. I missed that. However, we are still not able to import duplicates. I'm working around it manually in SQL and it seems to be doing the trick. I don't know enough about the MARC side to know if there are errors in our records, but from the little I know, it certainly looks like they are ok. Clearly there is a dependent field somewhere we are not looking. For now, I'm just doing an insert into the items table with a copy of the record with the same biblio number as the copy 1. I just replace the copy number and the barcode number. That seems to have worked for us with the exception that the number of copies in the master record does not seem to be updating on its own. It looks like it updates after some interaction. I couldn't find which table "copies available" was in. But that is a minor point. We are in business and that is the main thing. Thanks, Bri Brian Weissman WDW BT, Technical Specialist Team Disney North - 303B Office: 407.828.4751 Brian.S.Weissman at Disney.com -----Original Message----- From: Mason James [mailto:mtj at kohaaloha.com] Sent: Friday, October 14, 2011 7:25 AM To: Fridolyn SOMERS Cc: koha-devel; Weissman, Brian S.; Hartman, David W. - GBTS Library Subject: Re: [Koha-devel] Unable to get patches .. "detect duplicates not working" > > On Thu, Oct 13, 2011 at 4:24 PM, Fridolyn SOMERS wrote: > Sorry, > > I missed it, it has been send to GIT : http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=9b38eccf73b199bf450915ba01236ddf76658a5a > > > On Thu, Oct 13, 2011 at 3:32 PM, Hartman, David W. - GBTS Library wrote: > Ahhh ... so we do not have the patch. I need to tell the list that .. they kept saying over and over that we had the patch .. > > > KOHA_INSTALLED_VERSION=3.05.00.011 David the patch for bug 6713 was added in version 3.05.00.008 if you are running 3.05.00.011 - you *have* that patch, (as i keep saying over and over) > > On Thu, Oct 13, 2011 at 2:59 PM, Hartman, David W. - GBTS Library wrote: > > Fridolyn, > > > We are using the stable nope, if you are running 3.05.xxxxx you are running a DEV Koha release > .. should we use the dev? you already are.. i hope this makes some sense cheers, Mason -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting annoying in email? From kmkale at anantcorp.com Fri Oct 14 17:30:37 2011 From: kmkale at anantcorp.com (Koustubha Kale) Date: Fri, 14 Oct 2011 21:00:37 +0530 Subject: [Koha-devel] Fwd: Interested to speak at KohaCon 2011 In-Reply-To: <4E980177.50903@biblibre.com> References: <4E980177.50903@biblibre.com> Message-ID: Hi Anand / Noufal, Please see the mail from Paul below. It frees up a 1 hour slot for you on 01/11/2011 between 4.00 pm to 5.00 pm. Hope this is suitable and that you will take it up. If yes, please confirm back to me with an email. Please include title and an abstract of your talk. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2 ---------- Forwarded message ---------- From: Paul Poulain Date: 2011/10/14 Subject: Re: [Koha-devel] Interested to speak at KohaCon 2011 To: Koustubha Kale Cc: Fran?ois Charbonnier , Robin Sheat < robin at catalyst.net.nz> Le 05/10/2011 12:34, Koustubha Kale a ?crit : > Hi > this sounds like an excellent idea. unfortunately the program is full > atm. but i am sure we can accommodate you in place of some one canceling > at the last moment. or for this kind of topic, we can even have a > parallel session.. > if you want to interact with the developers we are going to have a > hackfest from 4th nov to 6th nov. since there is no fixed program for > that, you can achieve your objective there too.. Hi Kousthuba, I spoke with my colleage Francois, that will do the talk(s) about "serials & acquisitions, what is pending", and he agrees to merge both talks in to one, freeing a slot. I let you confirm you're OK and email Anand Chitipothu to tell him he can speak. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 -------------- next part -------------- An HTML attachment was scrubbed... URL: From abesottedphoenix at yahoo.com Fri Oct 14 17:42:40 2011 From: abesottedphoenix at yahoo.com (BWS Johnson) Date: Fri, 14 Oct 2011 08:42:40 -0700 (PDT) Subject: [Koha-devel] Fwd: Interested to speak at KohaCon 2011 In-Reply-To: References: <4E980177.50903@biblibre.com> Message-ID: <1318606960.7023.YahooMailNeo@web114711.mail.gq1.yahoo.com> Kia ora! ??????? That's great news! Thanks for this, Paul, I'm sure that everyone will be excited to hear what our friends at Open Library have to say. :D Cheers, Brooke From mjr at phonecoop.coop Fri Oct 14 21:30:24 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Fri, 14 Oct 2011 20:30:24 +0100 (BST) Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <1318370287.6421.49.camel@zarathud> Message-ID: <20111014193024.0D5769F0E8@nail.towers.org.uk> Robin Sheat > Keep in mind that sending to the list is very easy, maybe people are > doing it the hard way. > > What I do is: > > git bz attach HEAD > git send-email --to=kpatches HEAD^ # [...] That's doesn't work for me. For various reasons, I want my email sent from one of three email hosts, not from git on a development server. So I need to format-patch on the server, then copy it across and send it from elsewhere. Not as easy as git bz. I'm guessing that people who use SPF or DKIM might have similar needs, but I don't often use them. > This said, auto-sending from bugzilla would be great, I'm just hoping to > make it easier until someone finds the time to do that :) Sounds good. I don't see a problem with it. Anyone? Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From ali_madad04 at yahoo.com Sat Oct 15 11:51:12 2011 From: ali_madad04 at yahoo.com (ali madad) Date: Sat, 15 Oct 2011 02:51:12 -0700 (PDT) Subject: [Koha-devel] Project of Database development for a Digital Library Message-ID: <1318672272.16481.YahooMailClassic@web45105.mail.sp1.yahoo.com> Dear All KOHA experts, ? We are a Digital Library in Kabul Afghanistan (www.acku.edu.af), currently we are using ?Greenstone Database for our online library management system (http://www.nzdl.org/gsdlmod/cgi-bin/library?a=p&p=about&c=acku&l=en&nl=1%3E) ?but it cannot support ?many features and enhancements required! Therefore, it has been a high concern for our management to sort this issue out by any possible, professional and very standard solution, ?please find the attached for our new database specifications and wish list. Below are few points for which we need your kind recommendations and suggestions! 1)????? Depending on our wish list, maybe it is recommended to use an Integrated system (Greenstone and KOHA) ?so that to get best features out of both systems. 2)????? Upgrade of Greenstone?s current version (http://www.nzdl.org/gsdlmod/cgi-bin/library?a=p&p=about&c=acku&l=en&nl=1%3E) ?into new version so that to support our attached requirements. 3)????? Migration into KOHA. ? Our main concern: As we have already discussed with some database professionals, one of the main issue is to run KOHA or may be integrated system on Dari and Pastho two Afghan languages, some of them were not ready to do the translation! Kindly enlighten us by your kind suggestions and recommendations on any system you prefer so that to help us running the project independently or if you can help us on Translation of database into to Dari and Pashto languages!? ? Ali Basharyar IT Department Afghanistan Centre at Kabul University Kabul-Afghanistan +93 (0)799 707 667 ali.basharyar at acku.edu.af ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ali_madad04 at yahoo.com Sat Oct 15 11:56:06 2011 From: ali_madad04 at yahoo.com (ali madad) Date: Sat, 15 Oct 2011 02:56:06 -0700 (PDT) Subject: [Koha-devel] Project of KOHA Database Development for a Digital Library Message-ID: <1318672566.73578.YahooMailClassic@web45115.mail.sp1.yahoo.com> Dear All KOHA experts, ? We are a Digital Library in Kabul Afghanistan (www.acku.edu.af), currently we are using ?Greenstone Database for our online library management system (http://www.nzdl.org/gsdlmod/cgi-bin/library?a=p&p=about&c=acku&l=en&nl=1%3E) ?but it cannot support ?many features and enhancements required! Therefore, it has been a high concern for our management to sort this issue out by any possible, professional and very standard solution, ?please find the attached for our new database specifications and wish list. Below are few points for which we need your kind recommendations and suggestions! ? 1)????? Depending on our wish list, maybe it is recommended to use an Integrated system (Greenstone and KOHA) ?so that to get best features out of both systems. 2)????? Upgrade of Greenstone?s current version (http://www.nzdl.org/gsdlmod/cgi-bin/library?a=p&p=about&c=acku&l=en&nl=1%3E) ?into new version so that to support our attached requirements. 3)????? Migration into KOHA. ? Our main concern: ? As we have already discussed with some database professionals, one of the main issue is to run KOHA or may be integrated system on Dari and Pastho two Afghan languages, some of them were not ready to do the translation! Kindly enlighten us by your kind suggestions and recommendations on any system you prefer so that to help us running the project independently or if you can help us on Translation of database into to Dari and Pashto languages!? ? Ali Basharyar IT Department Afghanistan Centre at Kabul University Kabul-Afghanistan +93 (0)799 707 667 ali.basharyar at acku.edu.af ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From M.de.Rooy at rijksmuseum.nl Mon Oct 17 12:17:24 2011 From: M.de.Rooy at rijksmuseum.nl (Marcel de Rooy) Date: Mon, 17 Oct 2011 10:17:24 +0000 Subject: [Koha-devel] Cleaning up import tables and action log Message-ID: <809BE39CD64BFD4EB9036172EBCCFA3134DA7B@S-MAIL-1B.rijksmuseum.intra> Hi, Is anyone of you using code to periodically purge records from import_records, import_biblios, import_batches and/or action_logs ? If so, would it be an idea to include such code into cleanup_database.pl in misc/cronjobs ? Thanks for sharing, Marcel -------------- next part -------------- An HTML attachment was scrubbed... URL: From noufal at archive.org Mon Oct 17 13:55:50 2011 From: noufal at archive.org (Noufal Ibrahim) Date: Mon, 17 Oct 2011 17:25:50 +0530 Subject: [Koha-devel] Fwd: Interested to speak at KohaCon 2011 In-Reply-To: (Koustubha Kale's message of "Fri, 14 Oct 2011 21:00:37 +0530") References: <4E980177.50903@biblibre.com> Message-ID: <87obxf4yt5.fsf@sanitarium.localdomain> Hello Koustubha, I have included our talk title and abstract below. Thanks! --------------------------------------------------- Title: Open Library and Koha Abstract: Open Library is a project of the Internet Archive to create a catalogue of every book ever published. It is like a Wikipedia of books. Anyone can edit it to add new books or update existing ones to make it better. All the data in Open Library is freely available through APIs and regular dumps. This talk discusses the Open Library APIs and how to use them with Koha. Open Library website: http://openlibrary.org/ Internet Archive website: http://www.archive.org/ Authors: Anand Chitipothu & Noufal Ibrahim --------------------------------------------------- Koustubha Kale writes: > Hi Anand / Noufal, > Please see the mail from Paul below. It frees up a 1 hour slot for you on > 01/11/2011 between 4.00 pm to 5.00 pm. > Hope this is suitable and that you will take it up. > If yes, please confirm back to me with an email. Please include title and an > abstract of your talk. [...] -- ~noufal http://nibrahim.net.in The best cure for insomnia is to get a lot of sleep. -W. C. Fields From cnighswonger at foundations.edu Mon Oct 17 20:06:08 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Mon, 17 Oct 2011 14:06:08 -0400 Subject: [Koha-devel] Koha Master Running on Win32 Platform In-Reply-To: References: Message-ID: Update: I've pushed a copy of my MSWin32 branch [1] and updated the wiki page [2]. I'd be interested in seeing someone attempt to duplicate my work. It is not for the faint of heart, it will take you quite a bit of time, and it is a thankless task... you've been warned. ;-) [1] http://git.koha-community.org/gitweb/?p=wip/koha-chris_n.git;a=shortlog;h=refs/heads/MSWin32 [2] http://wiki.koha-community.org/wiki/Koha_3.4 On Sat, Oct 8, 2011 at 10:26 PM, Chris Nighswonger wrote: > For anyone who may be interested, I've the master branch of Koha running on > Windows XP. I have documented steps which should be reproducible on the wiki > [1] for anyone wanting to have a go at it. I'd love to see someone else be > able to have a try. There are a few changes which must be made in to code. I > will push my work up to my public git repo sometime this week so you can > grab them there until I have time to submit them for inclusion in master > branch. This is somewhat of a winding, long-term, no-definite-end sort of > project for me, so if you want more, you're welcome to jump in and help. I'm > not sending this to the user's list because it is by no means intended for > general consumption and is still very pre-alpha. > > Many thanks to Curtis Jewell and the folks who maintain Strawberry Perl [2] > for adding a number of key modules to help get Koha running under > Strawberry. > > Kind Regards, > Chris > > [1] http://wiki.koha-community.org/wiki/Koha_3.4 > [2] http://www.nntp.perl.org/group/perl.win32.vanilla/2010/01/msg196.html > From danielg.koha at gmail.com Mon Oct 17 21:38:41 2011 From: danielg.koha at gmail.com (Daniel Grobani) Date: Mon, 17 Oct 2011 12:38:41 -0700 Subject: [Koha-devel] Call for News for the October Newsletter Message-ID: Hi, I'm gathering news for the October newsletter. Please send me by the 24th anything you think the community might like to know about. "News" can be as short as a sentence or as long as a paper. I especially encourage you to send me a line or two about what you're currently working on for publication in the gossip/society column. And if you know of a go-live not announced on the list, please be sure to let me know about it. Many thanks, Daniel Grobani -------------- next part -------------- An HTML attachment was scrubbed... URL: From dabenavidesd at yahoo.es Tue Oct 18 00:50:11 2011 From: dabenavidesd at yahoo.es (Daniel Alejandro Benavides D.) Date: Mon, 17 Oct 2011 23:50:11 +0100 (BST) Subject: [Koha-devel] Koha Master Running on Win32 Platform In-Reply-To: Message-ID: <1318891811.90210.YahooMailClassic@web29708.mail.ird.yahoo.com> Hi: I would ARGUE the way of Embedded for Win32, is kind a VM on top of your system of choice, thus you can get the hardware support and the availability of such in a ROM or something like that, for instance, a Virtual box or so. Then I would pursue the cloud, with the same platform but be based on the network services available, like Google, etc. for high-profile and added value of koha. I think is worth to try to run koha but for the sake of comparison and proof of the concept good to see how this goes. Thanks in advance PS I don't know how perl goes with handy platform development, but C isn't still that portability true that you could port same basic core support onto any system, and MS porting is something hard, which I still can't see it isn't that hard as an Unix box, it could be worse. Anyway, if so, what is the next step for koha support perl6 and to the electric cloud, perhaps even rewriting while migrating? That's the way of easy of portability if I may say so. --- El lun, 17/10/11, Chris Nighswonger escribi?: > De: Chris Nighswonger > Asunto: Re: [Koha-devel] Koha Master Running on Win32 Platform > Para: koha-devel at lists.koha-community.org > Fecha: lunes, 17 de octubre, 2011 13:06 > Update: > > I've pushed a copy of my MSWin32 branch [1] and updated the > wiki page > [2]. I'd be interested in seeing someone attempt to > duplicate my work. > It is not for the faint of heart, it will take you quite a > bit of > time, and it is a thankless task... you've been warned. > ;-) > > [1] http://git.koha-community.org/gitweb/?p=wip/koha-chris_n.git;a=shortlog;h=refs/heads/MSWin32 > [2] http://wiki.koha-community.org/wiki/Koha_3.4 > > > On Sat, Oct 8, 2011 at 10:26 PM, Chris Nighswonger > > wrote: > > For anyone who may be interested, I've the master > branch of Koha running on > > Windows XP. I have documented steps which should be > reproducible on the wiki > > [1] for anyone wanting to have a go at it. I'd love to > see someone else be > > able to have a try. There are a few changes which must > be made in to code. I > > will push my work up to my public git repo sometime > this week so you can > > grab them there until I have time to submit them for > inclusion in master > > branch. This is somewhat of a winding, long-term, > no-definite-end sort of > > project for me, so if you want more, you're welcome to > jump in and help. I'm > > not sending this to the user's list because it is by > no means intended for > > general consumption and is still very pre-alpha. > > > > Many thanks to Curtis Jewell and the folks who > maintain Strawberry Perl [2] > > for adding a number of key modules to help get Koha > running under > > Strawberry. > > > > Kind Regards, > > Chris > > > > [1] http://wiki.koha-community.org/wiki/Koha_3.4 > > [2] http://www.nntp.perl.org/group/perl.win32.vanilla/2010/01/msg196.html > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > From cnighswonger at foundations.edu Tue Oct 18 01:59:26 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Mon, 17 Oct 2011 19:59:26 -0400 Subject: [Koha-devel] Call for News for the October Newsletter In-Reply-To: References: Message-ID: Feel free to include my blurb about my Win32 work if you like. Chris 2011/10/17 Daniel Grobani : > Hi, > > I'm gathering news for the October newsletter. Please send me by the 24th > anything you think the community might like to know about. > > "News" can be as short as a sentence or as long as a paper. I especially > encourage you to send me a line or two about what you're currently working > on for publication in the gossip/society column. And if you know of a > go-live not announced on the list, please be sure to let me know about it. > > Many thanks, > Daniel Grobani > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > From kmkale at anantcorp.com Tue Oct 18 08:44:03 2011 From: kmkale at anantcorp.com (Koustubha Kale) Date: Tue, 18 Oct 2011 12:14:03 +0530 Subject: [Koha-devel] Kohacon11 program : make sure you are there!! Message-ID: Hi All, Here is the program for kohacon11 http://kohacon11.vpmthane.org/ocs/index.php/k/k11/schedConf/program It looks great with lots of interesting topics and great presenters. So make sure that you all are there on 31st October 2011 at VPM, Thane, Maharashtra, India.. Looking forward to meeting you all there :) Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From arosello at uci.cu Tue Oct 18 17:12:06 2011 From: arosello at uci.cu (Adnier Rosello Carrazana) Date: Tue, 18 Oct 2011 11:12:06 -0400 (CDT) Subject: [Koha-devel] Don't insert wthdrawn field!! In-Reply-To: Message-ID: <10b8b4a2-7d52-4f20-a126-aabc1df92c66@ucimail4.uci.cu> Hello, when I insert a new item, the field 952-0 (wthdrawn), not in the MARC record object, any idea?, greetings. Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU! http://www.antiterroristas.cu http://justiciaparaloscinco.wordpress.com From fridolyn.somers at gmail.com Tue Oct 18 17:31:26 2011 From: fridolyn.somers at gmail.com (Fridolyn SOMERS) Date: Tue, 18 Oct 2011 17:31:26 +0200 Subject: [Koha-devel] Don't insert wthdrawn field!! In-Reply-To: <10b8b4a2-7d52-4f20-a126-aabc1df92c66@ucimail4.uci.cu> References: <10b8b4a2-7d52-4f20-a126-aabc1df92c66@ucimail4.uci.cu> Message-ID: Hie, Since 3.4 (i don't remember the exact revision), items in MARC format are no longer stored in biblioitems.marcxml, they are in items table. See here : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5579 Regards, On Tue, Oct 18, 2011 at 5:12 PM, Adnier Rosello Carrazana wrote: > Hello, > > when I insert a new item, the field 952-0 (wthdrawn), not in the MARC > record object, any idea?, > > greetings. > Fin a la injusticia, LIBERTAD AHORA A NUESTROS CINCO COMPATRIOTAS QUE SE > ENCUENTRAN INJUSTAMENTE EN PRISIONES DE LOS EEUU! > http://www.antiterroristas.cu > http://justiciaparaloscinco.wordpress.com > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers at gmail.com -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From mjr at phonecoop.coop Tue Oct 18 18:18:16 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Tue, 18 Oct 2011 17:18:16 +0100 (BST) Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <4E9582A8.3060901@biblibre.com> Message-ID: <20111018161816.4E3EB9F0E8@nail.towers.org.uk> Paul Poulain > Le 10/10/2011 09:58, Chris Cormack a ?crit : > > First i'd like to add a -3 switch so that the apply will use a 3way > > merge. At the moment if it fails you have to try that manually. > If someone has the Python skill: > edit git-bz, at line 1497, you'll see : > process = git.am(filename, _interactive=True ) > Changing it to : > process = git.am(filename, _interactive=True, 3=True ) > should do the trick (i've tested with i=true, and you get the git am -i > (interactive) as expected) Well, that will always run with -3, which isn't optional like I think Chris was suggesting. Is there a drawback with it? Or it would, except for what you found: > EXCEPT that python don't like the 3 (or any arg starting with a number), > returning a nasty > > File "/home/paul/bin/git-bz", line 1497 > > process = git.am(filename, _interactive=True, 3=True ) > > SyntaxError: keyword can't be an expression [...] > couldn't find the correct syntax. If someone has a suggestion... If I've understood it right, the co-op's python guru suggests it might be process = git.am(filename, kwargs=**{'_interactive': True, '3': True}) but we suspect we should hack git_run to handle leading-number args nicer. Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From paul.poulain at biblibre.com Tue Oct 18 18:32:33 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 18 Oct 2011 18:32:33 +0200 Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <20111018161816.4E3EB9F0E8@nail.towers.org.uk> References: <20111018161816.4E3EB9F0E8@nail.towers.org.uk> Message-ID: <4E9DAA21.3030503@biblibre.com> Le 18/10/2011 18:18, MJ Ray a ?crit : > Paul Poulain >> process = git.am(filename, _interactive=True, 3=True ) >> should do the trick (i've tested with i=true, and you get the git am -i >> (interactive) as expected) > > Well, that will always run with -3, which isn't optional like > I think Chris was suggesting. Is there a drawback with it? yes, that would. But anyway, git tries to apply the patch without 3way before testing 3way. At least that's how I understand git. > If I've understood it right, the co-op's python guru suggests it might be > process = git.am(filename, kwargs=**{'_interactive': True, '3': True}) will try and let you know ! > but we suspect we should hack git_run to handle leading-number args nicer. thanks though -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From christianjcj at gmail.com Tue Oct 18 22:02:59 2011 From: christianjcj at gmail.com (Christian Calle Jahuira) Date: Tue, 18 Oct 2011 16:02:59 -0400 Subject: [Koha-devel] Problems of translation into my language Message-ID: Dear It is a pleasure to participate in this community. I need help please. I'm translating into Spanish Koha Koha version 3.4.5 on Debian Lenny and I have the following error. root at christianjcj:/usr/share/koha/misc/translator# ./tmpl_process3.plinstall -i /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/ -o /usr/share/koha//intranet/htdocs/intranet-tmpl/prog/en -s ./es-ES-i-staff-t-prog-v-3002000.po Can't locate C4/TmplTokenType.pm in @INC (@INC contains: /etc/perl /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 /usr/local/lib/site_perl .) at TmplTokenizer.pm line 5. BEGIN failed--compilation aborted at TmplTokenizer.pm line 5. Compilation failed in require at ./tmpl_process3.pl line 19. BEGIN failed--compilation aborted at ./tmpl_process3.pl line 19. root at christianjcj:/usr/share/koha/misc/translator# Thanks for the help. -- Christian Jhonny Calle Jahuira TUTOR ELEARNING - UMSA Consultor Sistemas de Informacion de Bibliotecas de la UMSA Email: christianjcj at gmail.com Cel: 73017301 - 65151595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dubyk at ukr.net Tue Oct 18 22:13:43 2011 From: dubyk at ukr.net (Serhij Dubyk) Date: Tue, 18 Oct 2011 13:13:43 -0700 (PDT) Subject: [Koha-devel] Problems of translation into my language In-Reply-To: References: Message-ID: <1318968823581-4915252.post@n5.nabble.com> Try: env KOHA_CONF=/etc/koha/koha-conf.xml PERL5LIB=/usr/share/koha3/lib perl -I /usr/share/koha3/lib "./translate" install es-ES (with own paths) ----- TNTU & ServanTek, Ternopil', Ukraine -- View this message in context: http://koha.1045719.n5.nabble.com/Problems-of-translation-into-my-language-tp4915216p4915252.html Sent from the Koha-devel mailing list archive at Nabble.com. From gonzalez at famaf.unc.edu.ar Tue Oct 18 22:14:54 2011 From: gonzalez at famaf.unc.edu.ar (Bernardo Gonzalez Kriegel) Date: Tue, 18 Oct 2011 17:14:54 -0300 Subject: [Koha-devel] Problems of translation into my language In-Reply-To: References: Message-ID: You must set the variables KOHA_CONF and PERL5LIB before you run the translate script. -- Bernardo Gonzalez Kriegel gonzalez at famaf.unc.edu.ar 2011/10/18 Christian Calle Jahuira > Dear > > It is a pleasure to participate in this community. > > I need help please. > > I'm translating into Spanish Koha Koha version 3.4.5 on Debian Lenny and I > have the following error. > > > root at christianjcj:/usr/share/koha/misc/translator# ./tmpl_process3.plinstall -i /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/ -o > /usr/share/koha//intranet/htdocs/intranet-tmpl/prog/en -s > ./es-ES-i-staff-t-prog-v-3002000.po > Can't locate C4/TmplTokenType.pm in @INC (@INC contains: /etc/perl > /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 > /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 > /usr/local/lib/site_perl .) at TmplTokenizer.pm line 5. > BEGIN failed--compilation aborted at TmplTokenizer.pm line 5. > Compilation failed in require at ./tmpl_process3.pl line 19. > BEGIN failed--compilation aborted at ./tmpl_process3.pl line 19. > root at christianjcj:/usr/share/koha/misc/translator# > > > > Thanks for the help. > > -- > Christian Jhonny Calle Jahuira > TUTOR ELEARNING - UMSA > Consultor Sistemas de Informacion de Bibliotecas de la UMSA > Email: christianjcj at gmail.com > Cel: 73017301 - 65151595 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ian.walls at bywatersolutions.com Tue Oct 18 23:03:19 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Tue, 18 Oct 2011 17:03:19 -0400 Subject: [Koha-devel] Koha 3.6 approaches! Get your patches signed off today! Message-ID: Everyone, Koha 3.6 is only days away from release, and lots of good stuff has been tested and integrated! However, there are still lots of fixes and enhancements left to test. If you check the following link, you can see about 94 patches that folks have written that need someone to give them a signoff before they can be integrated into Koha. http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&field0-0-0=cf_patch_status&query_format=advanced&type0-0-0=equals&value0-0-0=Needs%20Signoff&title=Bug%20List%3A%20Needs%20Signoff&list_id=13603 If you've got a bug in there that is bothering you, give it a test. If you've got a patch you've written that needs a signoff, bribe a friend to test it (I think a "you test my patch, I'll test yours" arrangement could be quite productive). I've got a few that need signoff, myself, and would happily make such a deal, if anyone's willing :) I'll be trying to get as many of these checked as I can before the deadline set by our Release Manager, but I know I won't be able to cover them all. Any and all help you can lend would be greatly appreciated, as we gear up to make Koha 3.6 the best release yet. Thank you all, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From tomascohen at gmail.com Wed Oct 19 16:45:12 2011 From: tomascohen at gmail.com (Tomas Cohen Arazi) Date: Wed, 19 Oct 2011 11:45:12 -0300 Subject: [Koha-devel] Problems of translation into my language In-Reply-To: References: Message-ID: You need to re-check the instructions you're following (and perhaps change them) for the install process, as for 3.4.5 version you shouldn't be running tmpl_process3.pl as it is for the previous template system. You should be running perl translate install es-ES for instance. Take a look at http://wiki.koha-community.org/wiki/Installation_of_additional_languages_for_OPAC_and_INTRANET_staff_client regards To+ 2011/10/18 Christian Calle Jahuira : > Dear > > It is a pleasure to participate in this community. > > I need help please. > > I'm translating into Spanish Koha Koha version 3.4.5 on Debian Lenny and I > have the following error. > > > root at christianjcj:/usr/share/koha/misc/translator# ./tmpl_process3.pl > install -i /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/ -o > /usr/share/koha//intranet/htdocs/intranet-tmpl/prog/en -s > ./es-ES-i-staff-t-prog-v-3002000.po > Can't locate C4/TmplTokenType.pm in @INC (@INC contains: /etc/perl > /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 > /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 > /usr/local/lib/site_perl .) at TmplTokenizer.pm line 5. > BEGIN failed--compilation aborted at TmplTokenizer.pm line 5. > Compilation failed in require at ./tmpl_process3.pl line 19. > BEGIN failed--compilation aborted at ./tmpl_process3.pl line 19. > root at christianjcj:/usr/share/koha/misc/translator# > > > > Thanks for the help. > > -- > Christian Jhonny Calle Jahuira > TUTOR ELEARNING? - UMSA > Consultor Sistemas de Informacion de Bibliotecas de la UMSA > Email: christianjcj at gmail.com > Cel: 73017301 - 65151595 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > From fridolyn.somers at gmail.com Thu Oct 20 09:13:04 2011 From: fridolyn.somers at gmail.com (Fridolyn SOMERS) Date: Thu, 20 Oct 2011 09:13:04 +0200 Subject: [Koha-devel] Problems of translation into my language In-Reply-To: References: Message-ID: Hie, In my last use, there it was impossible to translate a "standard" installation of Koha (in /usr/share/koha). It was only possible in a "dev" install. To cheat it, you can create a symbolic link : ln -s /usr/share/koha/misc /usr/share/koha/intranet/cgi-bin So misc is like in the "dev" install, with intranet perl scripts. Regards, On Wed, Oct 19, 2011 at 4:45 PM, Tomas Cohen Arazi wrote: > You need to re-check the instructions you're following (and perhaps > change them) for the install process, as for 3.4.5 version you > shouldn't be running tmpl_process3.pl as it is for the previous > template system. You should be running > > perl translate install es-ES > > for instance. > > Take a look at > > > http://wiki.koha-community.org/wiki/Installation_of_additional_languages_for_OPAC_and_INTRANET_staff_client > > regards > To+ > > 2011/10/18 Christian Calle Jahuira : > > Dear > > > > It is a pleasure to participate in this community. > > > > I need help please. > > > > I'm translating into Spanish Koha Koha version 3.4.5 on Debian Lenny and > I > > have the following error. > > > > > > root at christianjcj:/usr/share/koha/misc/translator# ./tmpl_process3.pl > > install -i /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/ -o > > /usr/share/koha//intranet/htdocs/intranet-tmpl/prog/en -s > > ./es-ES-i-staff-t-prog-v-3002000.po > > Can't locate C4/TmplTokenType.pm in @INC (@INC contains: /etc/perl > > /usr/local/lib/perl/5.10.1 /usr/local/share/perl/5.10.1 /usr/lib/perl5 > > /usr/share/perl5 /usr/lib/perl/5.10 /usr/share/perl/5.10 > > /usr/local/lib/site_perl .) at TmplTokenizer.pm line 5. > > BEGIN failed--compilation aborted at TmplTokenizer.pm line 5. > > Compilation failed in require at ./tmpl_process3.pl line 19. > > BEGIN failed--compilation aborted at ./tmpl_process3.pl line 19. > > root at christianjcj:/usr/share/koha/misc/translator# > > > > > > > > Thanks for the help. > > > > -- > > Christian Jhonny Calle Jahuira > > TUTOR ELEARNING - UMSA > > Consultor Sistemas de Informacion de Bibliotecas de la UMSA > > Email: christianjcj at gmail.com > > Cel: 73017301 - 65151595 > > > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers at gmail.com -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From psm_vu at india.com Thu Oct 20 16:30:01 2011 From: psm_vu at india.com (Partha Mukhopadhyay) Date: Thu, 20 Oct 2011 16:30:01 +0200 (CEST) Subject: [Koha-devel] Authority data import fail (UTF-8) Message-ID: <20111020143001.87BD51215BD3@smtp03.zmail.com> An HTML attachment was scrubbed... URL: From christianjcj at gmail.com Thu Oct 20 16:39:25 2011 From: christianjcj at gmail.com (Christian Calle Jahuira) Date: Thu, 20 Oct 2011 10:39:25 -0400 Subject: [Koha-devel] Error in the cataloging module Message-ID: Dear. When you start cataloging in Koha-3.04.05.000 version of a book store I get the following error can anyone help please. Can't call method "fields" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2103. thanks -- Christian Jhonny Calle Jahuira TUTOR ELEARNING - UMSA Consultor Sistemas de Informacion de Bibliotecas de la UMSA Email: christianjcj at gmail.com Cel: 73017301 - 65151595 Cochabamba-La Paz / Bolivia -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolyn.somers at gmail.com Thu Oct 20 17:07:56 2011 From: fridolyn.somers at gmail.com (Fridolyn SOMERS) Date: Thu, 20 Oct 2011 17:07:56 +0200 Subject: [Koha-devel] Error in the cataloging module In-Reply-To: References: Message-ID: It usuallly means that the biblio with specified number (in URL : biblionumber=...) does not exist in database. 2011/10/20 Christian Calle Jahuira > Dear. > > When you start cataloging in Koha-3.04.05.000 version of a book store I get the following error can anyone help please. > > > > Can't call method "fields" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2103. > > thanks > > > -- > Christian Jhonny Calle Jahuira > TUTOR ELEARNING - UMSA > Consultor Sistemas de Informacion de Bibliotecas de la UMSA > Email: christianjcj at gmail.com > Cel: 73017301 - 65151595 > Cochabamba-La Paz / Bolivia > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers at gmail.com -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From David.W.Hartman at disney.com Thu Oct 20 17:44:15 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Thu, 20 Oct 2011 11:44:15 -0400 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: References: Message-ID: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> Just a heads up that a recent "update" by Debian Linux removed the application Koha - my apache and data files apparently are fine. How do I reinstall Koha without damaging or overwriting my data? If anyone has any experience with this, please let me know. If you see the red "burst" in the upper right hand corner, only do the safe install .. or else... -------------- next part -------------- An HTML attachment was scrubbed... URL: From robin at catalyst.net.nz Fri Oct 21 00:11:51 2011 From: robin at catalyst.net.nz (Robin Sheat) Date: Fri, 21 Oct 2011 11:11:51 +1300 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: <1319148711.18770.3.camel@zarathud> Hartman, David W. - GBTS Library schreef op do 20-10-2011 om 11:44 [-0400]: > Just a heads up that a recent ?update? by Debian Linux removed the > application Koha ? my apache and data files apparently are fine. > > How do I reinstall Koha without damaging or overwriting my data? If > anyone has any experience with this, please let me know. > Just reinstall the koha-common package. Grab a backup if you want to be safe, but I'd expect it would be fine. If everything in /etc/ is untouched (which I'd expect) then it should just magically work again. > If you see the red ?burst? in the upper right hand corner, only do the > safe install .. or else? Are you able to provide me with more information? Perhaps the logs in /var/log/apt or so. I'd like to see what was going on there. Robin. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From David.W.Hartman at disney.com Thu Oct 20 17:02:59 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Thu, 20 Oct 2011 11:02:59 -0400 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" Message-ID: <3E19441498923443B9DBE2FE1C0E70B60448A87E98@SM-FLOR-VXMB04B.wdw.disney.com> Just a heads up that a recent "update" by Debian Linux removed the application Koha - my apache and data files apparently are fine. If anyone has any experience with this, please let me know. If you see the red "burst" in the upper right hand corner, only do the safe install .. or else... David W. Hartman Global Business Technology Strategy Library Team Disney 336N 407 828 4250 (8-222) FAX 407 828 4868 FOLLOW MY RESEARCH on Backlot & Yammer! Learn about our research partners in the 2011 IT Research Competency Center GBTS CAST can click to request AV Equipment, Books, & Research WATCH the GBTS Library (Video) Update ! CLICK for the GBTS VIRTUAL LIBRARYportal site!! "This communication is confidential, intended only for the named recipients above and may contain trade secrets or other information that is exempt from disclosure under applicable law. Any use, dissemination, distribution or copying of this communication by anyone other than the named recipients is strictly prohibited. If you have received this communication in error, please immediately notify us by calling (407) 828-4250. Thank you." [cid:image001.gif at 01CC8F17.D435D7E0]Please consider your environmental responsibility before printing this e-mail [cid:image001.gif at 01CC8F17.D435D7E0] Think Environmentality! Reduce! Reuse! Recycle! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 2028 bytes Desc: image001.gif URL: From David.W.Hartman at disney.com Thu Oct 20 17:39:21 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Thu, 20 Oct 2011 11:39:21 -0400 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" Message-ID: <3E19441498923443B9DBE2FE1C0E70B60448A87F46@SM-FLOR-VXMB04B.wdw.disney.com> Hello, Just a heads up that a recent ?update? by Debian Linux removed the application Koha ? my apache and data files apparently are fine. Does anyone know how to reinstall Koha without damaging the data files ? If anyone has any experience with this, please let me know. If you see the red ?burst? in the upper right hand corner, only do the safe install .. or else? -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolyn.somers at gmail.com Fri Oct 21 15:19:22 2011 From: fridolyn.somers at gmail.com (Fridolyn SOMERS) Date: Fri, 21 Oct 2011 15:19:22 +0200 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60448A87F46@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60448A87F46@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: I bet it comes from the dependency of koha with "apache2-mpm-itk". The common apache MPM is "apache2-mpm-worker". So you may have installed a package that depends on it ; the conflic has been resolved by unistalling apache2-mpm-itk and koha. 2011/10/20 Hartman, David W. - GBTS Library > Hello,**** > > Just a heads up that a recent ?update? by Debian Linux removed the > application Koha ? my apache and data files apparently are fine. **** > > Does anyone know how to reinstall Koha without damaging the data files ? If > anyone has any experience with this, please let me know. If you see the red > ?burst? in the upper right hand corner, only do the safe install .. or else? > **** > > **** > > ** ** > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers at gmail.com -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From David.W.Hartman at disney.com Fri Oct 21 15:26:26 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Fri, 21 Oct 2011 09:26:26 -0400 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: References: <3E19441498923443B9DBE2FE1C0E70B60448A87F46@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: <3E19441498923443B9DBE2FE1C0E70B60448A8882F@SM-FLOR-VXMB04B.wdw.disney.com> How do we reinstall Koha? We are having some difficulty adding it back. We have backed up the hard drive just in case so we do not lose the data... From: koha-devel-bounces at lists.koha-community.org [mailto:koha-devel-bounces at lists.koha-community.org] On Behalf Of Fridolyn SOMERS Sent: Friday, October 21, 2011 9:19 AM To: koha-devel Subject: Re: [Koha-devel] Koha uninstalled by Debian Linux "update" I bet it comes from the dependency of koha with "apache2-mpm-itk". The common apache MPM is "apache2-mpm-worker". So you may have installed a package that depends on it ; the conflic has been resolved by unistalling apache2-mpm-itk and koha. 2011/10/20 Hartman, David W. - GBTS Library > Hello, Just a heads up that a recent "update" by Debian Linux removed the application Koha - my apache and data files apparently are fine. Does anyone know how to reinstall Koha without damaging the data files ... If anyone has any experience with this, please let me know. If you see the red "burst" in the upper right hand corner, only do the safe install .. or else... _______________________________________________ Koha-devel mailing list Koha-devel at 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/ -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers at gmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcamins at cpbibliography.com Fri Oct 21 15:54:13 2011 From: jcamins at cpbibliography.com (Jared Camins-Esakov) Date: Fri, 21 Oct 2011 09:54:13 -0400 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60448A8882F@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60448A87F46@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60448A8882F@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: David, The same way you installed it in the first place. Make sure you have the debian.koha-community.org apt repository listed in /etc/apt/sources.list, then run: > sudo apt-get update > sudo apt-get install koha-common Alternatively, you can do what I do, which is push your preferred koha-common*.deb package out to your server, and then run: > dpkg -i ${PKG_NAME} (if you get an error from that, follow the instructions) N.B.: using the k-c.org repo is to be VASTLY preferred if you aren't sure why you'd use the alternative I pointed out (i.e. I offer the alternative for completeness, not because you should follow those instructions). Regards, Jared 2011/10/21 Hartman, David W. - GBTS Library > How do we reinstall Koha? We are having some difficulty adding it back. We > have backed up the hard drive just in case so we do not lose the data? *** > * > > ** ** > > *From:* koha-devel-bounces at lists.koha-community.org [mailto: > koha-devel-bounces at lists.koha-community.org] *On Behalf Of *Fridolyn > SOMERS > *Sent:* Friday, October 21, 2011 9:19 AM > *To:* koha-devel > *Subject:* Re: [Koha-devel] Koha uninstalled by Debian Linux "update"**** > > ** ** > > I bet it comes from the dependency of koha with "apache2-mpm-itk". > The common apache MPM is "apache2-mpm-worker". > So you may have installed a package that depends on it ; the conflic has > been resolved by unistalling apache2-mpm-itk and koha.**** > > 2011/10/20 Hartman, David W. - GBTS Library ** > ** > > Hello,**** > > Just a heads up that a recent ?update? by Debian Linux removed the > application Koha ? my apache and data files apparently are fine. **** > > Does anyone know how to reinstall Koha without damaging the data files ? If > anyone has any experience with this, please let me know. If you see the red > ?burst? in the upper right hand corner, only do the safe install .. or else? > **** > > **** > > **** > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/**** > > > > > -- > Fridolyn SOMERS > ICT engineer > PROGILONE - Lyon - France > fridolyn.somers at gmail.com**** > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins at cpbibliography.com (web) http://www.cpbibliography.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From jcamins at cpbibliography.com Fri Oct 21 16:10:25 2011 From: jcamins at cpbibliography.com (Jared Camins-Esakov) Date: Fri, 21 Oct 2011 10:10:25 -0400 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE79@SM-FLOR-VXMB06A.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> <1319148711.18770.3.camel@zarathud> <667301C2-C408-4C23-A579-0CD2C571BBDE@disney.com> <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE79@SM-FLOR-VXMB06A.wdw.disney.com> Message-ID: Brian and David, Please keep these discussions on the list, so that anyone else encountering these issues in the future will be able to find the fix. It looks to me like your problem is the GPG key for the indexdata repository. The good news is, you don't need the indexdata repository anymore, I don't think. Try removing that line from /etc/apt/sources.list, rerunning apt-get update, and reinstalling koha-common. Regards, Jared On Fri, Oct 21, 2011 at 10:05 AM, Weissman, Brian S. < Brian.S.Weissman at disney.com> wrote: > Here is what I have found so far. It looks like something in the automatic > updates told the system to remove koha. This excerpt seems to be the > relevant bit from history.log: > > Start-Date: 2011-10-20 10:28:54 > Install: libidzebra-2.0:i386 (2.0.49-1indexdata, automatic) > Upgrade: libidzebra-2.0-mod-grs-regx:i386 (2.0.44-2, 2.0.49-1indexdata), > libidzebra-2.0-dev:i386 (2.0.44-2, 2.0.49-1indexdata), > libidzebra-2.0-mod-grs-xml:i386 (2.0.44-2, 2.0.49-1indexdata) > Remove: koha-common:i386 (3.5-1~git+20111017180723.41928b08), > libidzebra-2.0-mod-dom:i386 (2.0.44-2), libidzebra-2.0-0:i386 (2.0.44-2), > libidzebra-2.0-modules:i386 (2.0.49-1indexdata), > libidzebra-2.0-mod-grs-marc:i386 (2.0.44-2), idzebra-2.0:i386 (2.0.44-2), > libidzebra-2.0-mod-alvis:i386 (2.0.44-2), idzebra-2.0-utils:i386 (2.0.44-2), > libidzebra-2.0-mod-text:i386 (2.0.44-2) > End-Date: 2011-10-20 10:29:03 > > Start-Date: 2011-10-20 10:29:28 > Install: libreadline5:i386 (5.2-7, automatic) > Upgrade: tzdata:i386 (2011k-0squeeze1, 2011l-0squeeze1) > End-Date: 2011-10-20 10:29:32 > > And this is from the term.log: > > Log started: 2011-10-20 10:28:54 > Removing koha-common ... > Stopping Zebra server for koha > Removing idzebra-2.0 ... > Removing idzebra-2.0-utils ... > Removing libidzebra-2.0-modules ... > Removing libidzebra-2.0-mod-text ... > Processing triggers for man-db ... > Preparing to replace libidzebra-2.0-mod-grs-xml 2.0.44-2 (using ... > Unpacking replacement libidzebra-2.0-mod-grs-xml ... > Preparing to replace libidzebra-2.0-mod-grs-regx 2.0.44-2 (using ... > Unpacking replacement libidzebra-2.0-mod-grs-regx ... > Removing libidzebra-2.0-mod-grs-marc ... > Removing libidzebra-2.0-mod-dom ... > Removing libidzebra-2.0-mod-alvis ... > Preparing to replace libidzebra-2.0-dev 2.0.44-2 (using ... > Unpacking replacement libidzebra-2.0-dev ... > Processing triggers for man-db ... > Removing libidzebra-2.0-0 ... > Selecting previously deselected package libidzebra-2.0. > Unpacking libidzebra-2.0 (from ... > Setting up libidzebra-2.0 (2.0.49-1indexdata) ... > Setting up libidzebra-2.0-mod-grs-xml (2.0.49-1indexdata) ... > Setting up libidzebra-2.0-mod-grs-regx (2.0.49-1indexdata) ... > Setting up libidzebra-2.0-dev (2.0.49-1indexdata) ... > Log ended: 2011-10-20 10:29:03 > > Log started: 2011-10-20 10:29:28 > Preparing to replace tzdata 2011k-0squeeze1 (using ... > Unpacking replacement tzdata ... > Setting up tzdata (2011l-0squeeze1) ... > > Current default time zone: 'America/New_York' > Local time is now: Thu Oct 20 10:29:30 EDT 2011. > Universal Time is now: Thu Oct 20 14:29:30 UTC 2011. > Run 'dpkg-reconfigure tzdata' if you wish to change it. > > Selecting previously deselected package libreadline5. > Unpacking libreadline5 (from ... > Setting up libreadline5 (5.2-7) ... > Log ended: 2011-10-20 10:29:32 > > I have since tried to reinstall koha and followed a string of dependencies > and had no success. Here is the chain with the errors. Let me know if you > want more details. > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get update > (list of gets deleted for space) > Fetched 11.6 MB in 10s (1,091 kB/s) > Reading package lists... Done > W: GPG error: http://ftp.indexdata.dk wheezy Release: The following > signatures w ere invalid: KEYEXPIRED 1319102732 KEYEXPIRED 1319102732 > KEYEXPIRED 1319102732 > > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install koha > > The following packages have unmet dependencies: > koha : Depends: koha-common but it is not going to be installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install koha-common > > The following packages have unmet dependencies: > koha-common : Depends: idzebra-2.0 but it is not going to be installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install idzebra-2.0 > > The following packages have unmet dependencies: > idzebra-2.0 : Depends: idzebra-2.0-utils (= 2.0.49-1indexdata) but it is > not going to be installed > Depends: libidzebra-2.0-modules but it is not going to be > installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install idzebra-2.0-utils > > The following packages have unmet dependencies: > idzebra-2.0-utils : Depends: libyaz4 (>= 4.2.10) but 4.0.11-1 is to be > installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libidzebra-2.0-modules > > The following packages have unmet dependencies: > libidzebra-2.0-modules : Depends: libidzebra-2.0-mod-alvis but it is not > going to be installed > Depends: libidzebra-2.0-mod-dom but it is not > going to be installed > Depends: libidzebra-2.0-mod-grs-marc but it is not > going to be installed > Depends: libidzebra-2.0-mod-text but it is not > going to be installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libyaz4 > > The following packages have unmet dependencies: > libyaz4 : Depends: libgnutls26 (>= 2.12.6.1-0) but 2.8.6-1 is to be > installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libgnutls26 > > libgnutls26 is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get upgrade libgnutls26 > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following packages have been kept back: > libyaz4 yaz > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. > > That is where I dead end. > > > Brian Weissman > WDW BT, Technical Specialist > Team Disney North - 303B > Office: 407.828.4751 > Brian.S.Weissman at Disney.com > > > > -----Original Message----- > From: Hartman, David W. - GBTS Library > Sent: Thursday, October 20, 2011 6:18 PM > To: Robin Sheat > Cc: Weissman, Brian S. > Subject: Re: [Koha-devel] Koha uninstalled by Debian Linux "update" > > Yes, we'll report what we can and thanks for your help! > > Sent from my iPhone! Pardon typos, etc. > > > On Oct 20, 2011, at 6:12 PM, "Robin Sheat" wrote: > > > Hartman, David W. - GBTS Library schreef op do 20-10-2011 om 11:44 > > [-0400]: > >> Just a heads up that a recent ?update? by Debian Linux removed the > >> application Koha ? my apache and data files apparently are fine. > >> > >> How do I reinstall Koha without damaging or overwriting my data? If > >> anyone has any experience with this, please let me know. > >> > > Just reinstall the koha-common package. Grab a backup if you want to be > > safe, but I'd expect it would be fine. If everything in /etc/ is > > untouched (which I'd expect) then it should just magically work again. > > > >> If you see the red ?burst? in the upper right hand corner, only do the > >> safe install .. or else? > > > > Are you able to provide me with more information? Perhaps the logs > > in /var/log/apt or so. I'd like to see what was going on there. > > > > Robin. > > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/ > -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins at cpbibliography.com (web) http://www.cpbibliography.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.a at aandc.org Fri Oct 21 16:17:42 2011 From: paul.a at aandc.org (Paul) Date: Fri, 21 Oct 2011 10:17:42 -0400 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: <1319148711.18770.3.camel@zarathud> References: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: <5.2.1.1.2.20111021094409.02ca1b70@localhost> At 11:11 AM 10/21/2011 +1300, Robin Sheat wrote: >Hartman, David W. - GBTS Library schreef op do 20-10-2011 om 11:44 >[-0400]: > > Just a heads up that a recent ???update??? by Debian Linux removed the > > application Koha ? my apache and data files apparently are fine. > > > > How do I reinstall Koha without damaging or overwriting my data? If > > anyone has any experience with this, please let me know. > > >Just reinstall the koha-common package. Grab a backup if you want to be >safe, but I'd expect it would be fine. If everything in /etc/ is >untouched (which I'd expect) then it should just magically work again. > > > If you see the red ???burst??? in the upper right hand corner, only do the > > safe install .. or else >Are you able to provide me with more information? Perhaps the logs >in /var/log/apt or so. I'd like to see what was going on there. So would I. Was this an update, upgrade or [safe?] install? I'm not sure how Debian could have "removed the application Koha" - maybe backing up some .conf files under an "old" name? My own recent but limited experience is that the perl/CPAN involvement is the most time-consuming aspect of upgrading to the latest Koha release, but this could potentially be complicated if an OS upgrade (presumably Linux core) added further factors requiring intervention. Best - Paul Paul Tired old sys-admin From David.W.Hartman at disney.com Fri Oct 21 16:21:41 2011 From: David.W.Hartman at disney.com (Hartman, David W. - GBTS Library) Date: Fri, 21 Oct 2011 10:21:41 -0400 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE97@SM-FLOR-VXMB06A.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> <1319148711.18770.3.camel@zarathud> <667301C2-C408-4C23-A579-0CD2C571BBDE@disney.com> <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE79@SM-FLOR-VXMB06A.wdw.disney.com> <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE97@SM-FLOR-VXMB06A.wdw.disney.com> Message-ID: <3E19441498923443B9DBE2FE1C0E70B60448A88968@SM-FLOR-VXMB04B.wdw.disney.com> Jared, Thanks for the info, but the results appear to be the same without the index line, minus the GPG error. From tracing the dependencies, it looks to me like a bogus requirement somewhere along the way. koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libyaz4 The following packages have unmet dependencies: libyaz4 : Depends: libgnutls26 (>= 2.12.6.1-0) but 2.8.6-1 is to be installed E: Broken packages I looked in /var/lib/dpkg/status and found that libgnutls26 is version 2.8.6-1. Upgrading that tells me that the latest version is installed. This makes me think there is a bad dependency with libyaz4. However, this is the info in the status file for that package: Package: libyaz4 Status: install ok installed Priority: extra Section: libs Installed-Size: 1768 Maintainer: Vincent Danjean Architecture: i386 Source: yaz Version: 4.0.11-1 Replaces: libyaz Depends: libc6 (>= 2.7), libgnutls26 (>= 2.7.14-0), libicu44 (>= 4.4.1-1), libwrap0 (>= 7.6-4~), libxml2 (>= 2.7.4), libxslt1.1 (>= 1.1.25) Breaks: idzebra (<= 1.3.4-2), libyaz, php4-yaz (<= 4.1.2-5) Description: The YAZ Z39.50 toolkit (runtime files) YAZ is a toolkit that allows you to develop software using the ANSI Z39.50/ISO23950 standard for information retrieval. . This package includes runtime files. Homepage: http://www.indexdata.dk/yaz/ I am not sure where to go from here. David Hartman From: Jared Camins-Esakov [mailto:jcamins at cpbibliography.com] Sent: Friday, October 21, 2011 10:10 AM To: Weissman, Brian S. Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Koha uninstalled by Debian Linux "update" Brian and David, Please keep these discussions on the list, so that anyone else encountering these issues in the future will be able to find the fix. It looks to me like your problem is the GPG key for the indexdata repository. The good news is, you don't need the indexdata repository anymore, I don't think. Try removing that line from /etc/apt/sources.list, rerunning apt-get update, and reinstalling koha-common. Regards, Jared On Fri, Oct 21, 2011 at 10:05 AM, Weissman, Brian S. > wrote: Here is what I have found so far. It looks like something in the automatic updates told the system to remove koha. This excerpt seems to be the relevant bit from history.log: Start-Date: 2011-10-20 10:28:54 Install: libidzebra-2.0:i386 (2.0.49-1indexdata, automatic) Upgrade: libidzebra-2.0-mod-grs-regx:i386 (2.0.44-2, 2.0.49-1indexdata), libidzebra-2.0-dev:i386 (2.0.44-2, 2.0.49-1indexdata), libidzebra-2.0-mod-grs-xml:i386 (2.0.44-2, 2.0.49-1indexdata) Remove: koha-common:i386 (3.5-1~git+20111017180723.41928b08), libidzebra-2.0-mod-dom:i386 (2.0.44-2), libidzebra-2.0-0:i386 (2.0.44-2), libidzebra-2.0-modules:i386 (2.0.49-1indexdata), libidzebra-2.0-mod-grs-marc:i386 (2.0.44-2), idzebra-2.0:i386 (2.0.44-2), libidzebra-2.0-mod-alvis:i386 (2.0.44-2), idzebra-2.0-utils:i386 (2.0.44-2), libidzebra-2.0-mod-text:i386 (2.0.44-2) End-Date: 2011-10-20 10:29:03 Start-Date: 2011-10-20 10:29:28 Install: libreadline5:i386 (5.2-7, automatic) Upgrade: tzdata:i386 (2011k-0squeeze1, 2011l-0squeeze1) End-Date: 2011-10-20 10:29:32 And this is from the term.log: Log started: 2011-10-20 10:28:54 Removing koha-common ... Stopping Zebra server for koha Removing idzebra-2.0 ... Removing idzebra-2.0-utils ... Removing libidzebra-2.0-modules ... Removing libidzebra-2.0-mod-text ... Processing triggers for man-db ... Preparing to replace libidzebra-2.0-mod-grs-xml 2.0.44-2 (using ... Unpacking replacement libidzebra-2.0-mod-grs-xml ... Preparing to replace libidzebra-2.0-mod-grs-regx 2.0.44-2 (using ... Unpacking replacement libidzebra-2.0-mod-grs-regx ... Removing libidzebra-2.0-mod-grs-marc ... Removing libidzebra-2.0-mod-dom ... Removing libidzebra-2.0-mod-alvis ... Preparing to replace libidzebra-2.0-dev 2.0.44-2 (using ... Unpacking replacement libidzebra-2.0-dev ... Processing triggers for man-db ... Removing libidzebra-2.0-0 ... Selecting previously deselected package libidzebra-2.0. Unpacking libidzebra-2.0 (from ... Setting up libidzebra-2.0 (2.0.49-1indexdata) ... Setting up libidzebra-2.0-mod-grs-xml (2.0.49-1indexdata) ... Setting up libidzebra-2.0-mod-grs-regx (2.0.49-1indexdata) ... Setting up libidzebra-2.0-dev (2.0.49-1indexdata) ... Log ended: 2011-10-20 10:29:03 Log started: 2011-10-20 10:29:28 Preparing to replace tzdata 2011k-0squeeze1 (using ... Unpacking replacement tzdata ... Setting up tzdata (2011l-0squeeze1) ... Current default time zone: 'America/New_York' Local time is now: Thu Oct 20 10:29:30 EDT 2011. Universal Time is now: Thu Oct 20 14:29:30 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. Selecting previously deselected package libreadline5. Unpacking libreadline5 (from ... Setting up libreadline5 (5.2-7) ... Log ended: 2011-10-20 10:29:32 I have since tried to reinstall koha and followed a string of dependencies and had no success. Here is the chain with the errors. Let me know if you want more details. koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get update (list of gets deleted for space) Fetched 11.6 MB in 10s (1,091 kB/s) Reading package lists... Done W: GPG error: http://ftp.indexdata.dk wheezy Release: The following signatures w ere invalid: KEYEXPIRED 1319102732 KEYEXPIRED 1319102732 KEYEXPIRED 1319102732 koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install koha The following packages have unmet dependencies: koha : Depends: koha-common but it is not going to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install koha-common The following packages have unmet dependencies: koha-common : Depends: idzebra-2.0 but it is not going to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install idzebra-2.0 The following packages have unmet dependencies: idzebra-2.0 : Depends: idzebra-2.0-utils (= 2.0.49-1indexdata) but it is not going to be installed Depends: libidzebra-2.0-modules but it is not going to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install idzebra-2.0-utils The following packages have unmet dependencies: idzebra-2.0-utils : Depends: libyaz4 (>= 4.2.10) but 4.0.11-1 is to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libidzebra-2.0-modules The following packages have unmet dependencies: libidzebra-2.0-modules : Depends: libidzebra-2.0-mod-alvis but it is not going to be installed Depends: libidzebra-2.0-mod-dom but it is not going to be installed Depends: libidzebra-2.0-mod-grs-marc but it is not going to be installed Depends: libidzebra-2.0-mod-text but it is not going to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libyaz4 The following packages have unmet dependencies: libyaz4 : Depends: libgnutls26 (>= 2.12.6.1-0) but 2.8.6-1 is to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libgnutls26 libgnutls26 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get upgrade libgnutls26 Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: libyaz4 yaz 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. That is where I dead end. Brian Weissman WDW BT, Technical Specialist Team Disney North - 303B Office: 407.828.4751 Brian.S.Weissman at Disney.com -----Original Message----- From: Hartman, David W. - GBTS Library Sent: Thursday, October 20, 2011 6:18 PM To: Robin Sheat Cc: Weissman, Brian S. Subject: Re: [Koha-devel] Koha uninstalled by Debian Linux "update" Yes, we'll report what we can and thanks for your help! Sent from my iPhone! Pardon typos, etc. On Oct 20, 2011, at 6:12 PM, "Robin Sheat" > wrote: > Hartman, David W. - GBTS Library schreef op do 20-10-2011 om 11:44 > [-0400]: >> Just a heads up that a recent ?update? by Debian Linux removed the >> application Koha ? my apache and data files apparently are fine. >> >> How do I reinstall Koha without damaging or overwriting my data? If >> anyone has any experience with this, please let me know. >> > Just reinstall the koha-common package. Grab a backup if you want to be > safe, but I'd expect it would be fine. If everything in /etc/ is > untouched (which I'd expect) then it should just magically work again. > >> If you see the red ?burst? in the upper right hand corner, only do the >> safe install .. or else? > > Are you able to provide me with more information? Perhaps the logs > in /var/log/apt or so. I'd like to see what was going on there. > > Robin. > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins at cpbibliography.com (web) http://www.cpbibliography.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From fridolyn.somers at gmail.com Fri Oct 21 16:33:11 2011 From: fridolyn.somers at gmail.com (Fridolyn SOMERS) Date: Fri, 21 Oct 2011 16:33:11 +0200 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: <3E19441498923443B9DBE2FE1C0E70B60448A88968@SM-FLOR-VXMB04B.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> <1319148711.18770.3.camel@zarathud> <667301C2-C408-4C23-A579-0CD2C571BBDE@disney.com> <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE79@SM-FLOR-VXMB06A.wdw.disney.com> <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE97@SM-FLOR-VXMB06A.wdw.disney.com> <3E19441498923443B9DBE2FE1C0E70B60448A88968@SM-FLOR-VXMB04B.wdw.disney.com> Message-ID: Hie, Now that you removed indexdata repository, update and retry to install koha. You should not use "apt-get" but "aptitude", it can solve such problems and warns on pachage removal : > sudo aptitude install koha 2011/10/21 Hartman, David W. - GBTS Library > Jared,**** > > ** ** > > Thanks for the info, but the results appear to be the same without the > index line, minus the GPG error. From tracing the dependencies, it looks to > me like a bogus requirement somewhere along the way. **** > > ** ** > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libyaz4 > > The following packages have unmet dependencies: > libyaz4 : Depends: libgnutls26 (>= 2.12.6.1-0) but 2.8.6-1 is to be > installed > E: Broken packages**** > > ** ** > > I looked in /var/lib/dpkg/status and found that libgnutls26 is version > 2.8.6-1. Upgrading that tells me that the latest version is installed. This > makes me think there is a bad dependency with libyaz4. However, this is the > info in the status file for that package:**** > > ** ** > > Package: libyaz4**** > > Status: install ok installed**** > > Priority: extra**** > > Section: libs**** > > Installed-Size: 1768**** > > Maintainer: Vincent Danjean **** > > Architecture: i386**** > > Source: yaz**** > > Version: 4.0.11-1**** > > Replaces: libyaz**** > > Depends: libc6 (>= 2.7), libgnutls26 (>= 2.7.14-0), libicu44 (>= 4.4.1-1), > libwrap0 (>= 7.6-4~), libxml2 (>= 2.7.4), libxslt1.1 (>= 1.1.25)**** > > Breaks: idzebra (<= 1.3.4-2), libyaz, php4-yaz (<= 4.1.2-5)**** > > Description: The YAZ Z39.50 toolkit (runtime files)**** > > YAZ is a toolkit that allows you to develop software using the**** > > ANSI Z39.50/ISO23950 standard for information retrieval.**** > > .**** > > This package includes runtime files.**** > > Homepage: http://www.indexdata.dk/yaz/**** > > ** ** > > I am not sure where to go from here. **** > > ** ** > > David Hartman**** > > ** ** > > ** ** > > ** ** > > *From:* Jared Camins-Esakov [mailto:jcamins at cpbibliography.com] > *Sent:* Friday, October 21, 2011 10:10 AM > *To:* Weissman, Brian S. > *Cc:* koha-devel at lists.koha-community.org > > *Subject:* Re: [Koha-devel] Koha uninstalled by Debian Linux "update"**** > > ** ** > > Brian and David, > > Please keep these discussions on the list, so that anyone else encountering > these issues in the future will be able to find the fix. > > It looks to me like your problem is the GPG key for the indexdata > repository. The good news is, you don't need the indexdata repository > anymore, I don't think. Try removing that line from /etc/apt/sources.list, > rerunning apt-get update, and reinstalling koha-common. > > Regards, > Jared**** > > On Fri, Oct 21, 2011 at 10:05 AM, Weissman, Brian S. < > Brian.S.Weissman at disney.com> wrote:**** > > Here is what I have found so far. It looks like something in the automatic > updates told the system to remove koha. This excerpt seems to be the > relevant bit from history.log: > > Start-Date: 2011-10-20 10:28:54 > Install: libidzebra-2.0:i386 (2.0.49-1indexdata, automatic) > Upgrade: libidzebra-2.0-mod-grs-regx:i386 (2.0.44-2, 2.0.49-1indexdata), > libidzebra-2.0-dev:i386 (2.0.44-2, 2.0.49-1indexdata), > libidzebra-2.0-mod-grs-xml:i386 (2.0.44-2, 2.0.49-1indexdata) > Remove: koha-common:i386 (3.5-1~git+20111017180723.41928b08), > libidzebra-2.0-mod-dom:i386 (2.0.44-2), libidzebra-2.0-0:i386 (2.0.44-2), > libidzebra-2.0-modules:i386 (2.0.49-1indexdata), > libidzebra-2.0-mod-grs-marc:i386 (2.0.44-2), idzebra-2.0:i386 (2.0.44-2), > libidzebra-2.0-mod-alvis:i386 (2.0.44-2), idzebra-2.0-utils:i386 (2.0.44-2), > libidzebra-2.0-mod-text:i386 (2.0.44-2) > End-Date: 2011-10-20 10:29:03 > > Start-Date: 2011-10-20 10:29:28 > Install: libreadline5:i386 (5.2-7, automatic) > Upgrade: tzdata:i386 (2011k-0squeeze1, 2011l-0squeeze1) > End-Date: 2011-10-20 10:29:32 > > And this is from the term.log: > > Log started: 2011-10-20 10:28:54 > Removing koha-common ... > Stopping Zebra server for koha > Removing idzebra-2.0 ... > Removing idzebra-2.0-utils ... > Removing libidzebra-2.0-modules ... > Removing libidzebra-2.0-mod-text ... > Processing triggers for man-db ... > Preparing to replace libidzebra-2.0-mod-grs-xml 2.0.44-2 (using ... > Unpacking replacement libidzebra-2.0-mod-grs-xml ... > Preparing to replace libidzebra-2.0-mod-grs-regx 2.0.44-2 (using ... > Unpacking replacement libidzebra-2.0-mod-grs-regx ... > Removing libidzebra-2.0-mod-grs-marc ... > Removing libidzebra-2.0-mod-dom ... > Removing libidzebra-2.0-mod-alvis ... > Preparing to replace libidzebra-2.0-dev 2.0.44-2 (using ... > Unpacking replacement libidzebra-2.0-dev ... > Processing triggers for man-db ... > Removing libidzebra-2.0-0 ... > Selecting previously deselected package libidzebra-2.0. > Unpacking libidzebra-2.0 (from ... > Setting up libidzebra-2.0 (2.0.49-1indexdata) ... > Setting up libidzebra-2.0-mod-grs-xml (2.0.49-1indexdata) ... > Setting up libidzebra-2.0-mod-grs-regx (2.0.49-1indexdata) ... > Setting up libidzebra-2.0-dev (2.0.49-1indexdata) ... > Log ended: 2011-10-20 10:29:03 > > Log started: 2011-10-20 10:29:28 > Preparing to replace tzdata 2011k-0squeeze1 (using ... > Unpacking replacement tzdata ... > Setting up tzdata (2011l-0squeeze1) ... > > Current default time zone: 'America/New_York' > Local time is now: Thu Oct 20 10:29:30 EDT 2011. > Universal Time is now: Thu Oct 20 14:29:30 UTC 2011. > Run 'dpkg-reconfigure tzdata' if you wish to change it. > > Selecting previously deselected package libreadline5. > Unpacking libreadline5 (from ... > Setting up libreadline5 (5.2-7) ... > Log ended: 2011-10-20 10:29:32 > > I have since tried to reinstall koha and followed a string of dependencies > and had no success. Here is the chain with the errors. Let me know if you > want more details. > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get update > (list of gets deleted for space) > Fetched 11.6 MB in 10s (1,091 kB/s) > Reading package lists... Done > W: GPG error: http://ftp.indexdata.dk wheezy Release: The following > signatures w ere invalid: KEYEXPIRED 1319102732 KEYEXPIRED 1319102732 > KEYEXPIRED 1319102732 > > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install koha > > The following packages have unmet dependencies: > koha : Depends: koha-common but it is not going to be installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install koha-common > > The following packages have unmet dependencies: > koha-common : Depends: idzebra-2.0 but it is not going to be installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install idzebra-2.0 > > The following packages have unmet dependencies: > idzebra-2.0 : Depends: idzebra-2.0-utils (= 2.0.49-1indexdata) but it is > not going to be installed > Depends: libidzebra-2.0-modules but it is not going to be > installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install idzebra-2.0-utils > > The following packages have unmet dependencies: > idzebra-2.0-utils : Depends: libyaz4 (>= 4.2.10) but 4.0.11-1 is to be > installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libidzebra-2.0-modules > > The following packages have unmet dependencies: > libidzebra-2.0-modules : Depends: libidzebra-2.0-mod-alvis but it is not > going to be installed > Depends: libidzebra-2.0-mod-dom but it is not > going to be installed > Depends: libidzebra-2.0-mod-grs-marc but it is not > going to be installed > Depends: libidzebra-2.0-mod-text but it is not > going to be installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libyaz4 > > The following packages have unmet dependencies: > libyaz4 : Depends: libgnutls26 (>= 2.12.6.1-0) but 2.8.6-1 is to be > installed > E: Broken packages > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libgnutls26 > > libgnutls26 is already the newest version. > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. > > koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get upgrade libgnutls26 > Reading package lists... Done > Building dependency tree > Reading state information... Done > The following packages have been kept back: > libyaz4 yaz > 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. > > That is where I dead end. > > > Brian Weissman > WDW BT, Technical Specialist > Team Disney North - 303B > Office: 407.828.4751 > Brian.S.Weissman at Disney.com**** > > > > > -----Original Message----- > From: Hartman, David W. - GBTS Library > Sent: Thursday, October 20, 2011 6:18 PM > To: Robin Sheat > Cc: Weissman, Brian S. > Subject: Re: [Koha-devel] Koha uninstalled by Debian Linux "update"**** > > Yes, we'll report what we can and thanks for your help! > > Sent from my iPhone! Pardon typos, etc.**** > > > > On Oct 20, 2011, at 6:12 PM, "Robin Sheat" wrote: > > > Hartman, David W. - GBTS Library schreef op do 20-10-2011 om 11:44 > > [-0400]: > >> Just a heads up that a recent ?update? by Debian Linux removed the > >> application Koha ? my apache and data files apparently are fine. > >> > >> How do I reinstall Koha without damaging or overwriting my data? If > >> anyone has any experience with this, please let me know. > >> > > Just reinstall the koha-common package. Grab a backup if you want to be > > safe, but I'd expect it would be fine. If everything in /etc/ is > > untouched (which I'd expect) then it should just magically work again. > > > >> If you see the red ?burst? in the upper right hand corner, only do the > >> safe install .. or else? > > > > Are you able to provide me with more information? Perhaps the logs > > in /var/log/apt or so. I'd like to see what was going on there. > > > > Robin.**** > > > **** > > > _______________________________________________ > > Koha-devel mailing list > > Koha-devel at 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/**** > > > > > -- > Jared Camins-Esakov**** > > Bibliographer, C & P Bibliography Services, LLC**** > > (phone) +1 (917) 727-3445**** > > (e-mail) jcamins at cpbibliography.com**** > > (web) http://www.cpbibliography.com/**** > > ** ** > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Fridolyn SOMERS ICT engineer PROGILONE - Lyon - France fridolyn.somers at gmail.com -------------- section suivante -------------- Une pi?ce jointe HTML a ?t? nettoy?e... URL: From robin at catalyst.net.nz Fri Oct 21 21:01:33 2011 From: robin at catalyst.net.nz (Robin Sheat) Date: Sat, 22 Oct 2011 08:01:33 +1300 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: References: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> <1319148711.18770.3.camel@zarathud> <667301C2-C408-4C23-A579-0CD2C571BBDE@disney.com> <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE79@SM-FLOR-VXMB06A.wdw.disney.com> Message-ID: <4EA1C18D.40109@catalyst.net.nz> On 22-10-11 03:10, Jared Camins-Esakov wrote: > It looks to me like your problem is the GPG key for the indexdata > repository. The good news is, you don't need the indexdata repository > anymore, I don't think. Try removing that line from > /etc/apt/sources.list, rerunning apt-get update, and reinstalling > koha-common. It looks to me like indexdata has updated their repo, and it causes something to be removed (in particular, libyaz4) that koha-common depends on, rather than the GPG key. However, the solution above is exactly what you want: remove the line from sources.list, sudo aptitude update, sudo aptitude install koha-common At the moment I recommend against a) running the indexdata repository, the versions in debian work well, and b) the 'koha' package. As Jared says, use koha-common. Robin. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 262 bytes Desc: OpenPGP digital signature URL: From kmkale at anantcorp.com Sat Oct 22 08:49:25 2011 From: kmkale at anantcorp.com (Koustubha Kale) Date: Sat, 22 Oct 2011 12:19:25 +0530 Subject: [Koha-devel] Kohacon11 Mumbai day trip on 3rd November details Message-ID: Hi All, Here is tentative itinerary and cost of the planned Mumbai day trip on 3rd November. Itinerary : 1. 8am : Leave from Thane by bus 2. 9.30am : arrive at Gateway of India and leave by ferry for Elephanta caves ( designated a UNESCO World Heritage Site) 3. 10.30am to 12.30 : arrive at Elephanta Caves, site seeing with a guide, lunch either at the MTDC hotel on the island or back on mainland near Gateway of India. 4. 12.30pm to 1.30pm : ferry back to Gateway of India. ( if lunch on mainland , then lunch 1.30pm to 2.30pm near Gateway of India ) Else 1.30pm to 2.30 pm lunch in MTDC hotel on Elephanta caves and 1.30pm to 2.30 pm ferry back to Gateway of India 5. 2.30pm onwards local shopping, drive back while seeing local sites such as Mumbai University building, Marine Drive, Girgaon Chaupaty ( beach ) etc. 6. Around 6 to 7pm arrive back in Thane Approximate cost per person : INR 2000 Includes all costs such as travel, entry tickets, guide fees, lunch and afternoon tea/coffee. Please let me know urgently if you would llike to join the trip so that we can do the bookings.. Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at bigballofwax.co.nz Sat Oct 22 18:33:01 2011 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Sun, 23 Oct 2011 05:33:01 +1300 Subject: [Koha-devel] Koha 3.6.0 released Message-ID: It is with great plesure that I announce the release of Koha 3.6.0. This is major feature release, containing 85 enhancements and 356 bugfixes. A total of 728 patches have been included from 60 developers in this release. A big thanks goes out to all of them, plus all the other people involved in this release. You can download this release at http://download.koha-community.org/koha-3.06.00.000.tar.gz or you can wait a couple of days for the packages to appear at http://debian.koha-community.org. Release notes are available below. RELEASE NOTES FOR KOHA 3.6.0 - 22 October 2011 ======================================================================== Koha is the first free and open source software library automation package (ILS). Development is sponsored by libraries of varying types and sizes, volunteers, and support companies from around the world. The website for the Koha project is http://koha-community.org/ Koha 3.6.0 can be downloaded from: http://download.koha-community.org/koha-3.06.00.tar.gz Installation instructions can be found at: http://wiki.koha-community.org/wiki/Installation_Documentation OR in the INSTALL files that come in the tarball Koha 3.6.0 is a major feature release. New features in 3.6.0 ====================== ACQUISITIONS * When deleting an order, items are deleted and if applicable the biblio also (if no holds, subscriptions etc are attached) * Add Basket number and Invoice number search * Control view of baskets for vendor with a sys pref (own/branch/all) * Control confirmation when closing a basket with a sys pref ADMINISTRATION * New permission for overdues report CATALOGING * Z3950 results highlighting * Easy Analytics support * Improve controls for cloning and deleting MARC subfields * Capability to blank subfields in Batch Modification * UNIMARC field 225 plugin: allow $a value data entry * Adjust default values for MARC21 authority Fixed-Length Data Elements * Update UNIMARC plugins * Adding option to "attach another item" when finished attaching items CIRCULATION * Added a checkin tab to the patron search screen * Added enumchron field to the place holds screen * Better hold information on the staff biblio detail screen * Added a checked out from colum to list of checked out items (syspref controlled) * Add link to fast add framework while circulating, if a barcode is not found * Automatically check out fast add item after cataloging it * Add shelving location to checkin results screen OPAC * Paging on the opac detail page, allowing the user to move through search results * Recent comments view * Added a powered by Koha footer * Show a warning if placing a hold incurs a charge * Added user customisable html block under the facets in search results * Added customisable html block under OpacNav and patron account links * Profile pictures in the OPAC next to review authors * Show number of comments on the "Comments" tab in OPAC PATRONS * Log membership renewal * Allow patron update script (on OPAC) to send email using the from address of the patron * Extended attributes display much improved * Partial fine payments * If a patron search returns one result, redirect to patron details page MESSAGING * Improved the email checking when sending "Hold filled" notices. * Add today's date on checkin/checkout notices REPORTS * Added links to the schema and reports library * Record localuse statistics, when returning items not on issue * Control for which branch renewals are recorded with a sys pref SEARCHING * Added ISBN filter to advanced * Analytic links search on full phrase title * Control order in which facet categories display SIP * Add Support for the Fee Paid Message ENHANCED CONTENT * Add integration for EBSCO's Novelist Select service * Enable Koha to fetch book covers from Open Library STAFF INTERFACE * Improved styling of the table pager * Add autocomplete="off" to borrowernumbers and barcode forms * Improved the tinymce editor on the Koha news page INTERFACE * Added crystal icon set * Nicer style for "clear screen" button * Added capability to limit the RSS results INTERNATIONALIZATION * Tons of fixes to the translation tools * Add German translation for purchase suggestion mails * Spanish translation for SQL files INTERNALS, PACKAGING AND PERFORMANCE * Simplified system preferences for the web installer * Create and update the manual pages for the koha-* scripts. * Automated backups of data and config * Improve configurability of package building scripts COMMAND LINE UTILITIES * cron script to allow easy anonymisation of patron circulation data BUGFIXES * Longer userid fields * Clean up guided reports dictionary entry process * Circulation restrictions working when other withdrawn reasons are used * Fixed LDAP username case issues Plus 356 more bugfixes System Preferences ====================== The following system preferences are new in 3.6.0: * numSearchRSSResults * OpacRenewalBranch * ShowReviewerPhoto * BasketConfirmations * MARCAuthorityControlField008 * OpenLibraryCovers * OPACResultsSidebar * RecordLocalUseOnReturn * OpacKohaUrl * NovelistSelectEnabled * NovelistSelectProfile * NovelistSelectPassword * NovelistSelectView * EasyAnalyticalRecords * OpacNavBottom * AcqViewBaskets * OpacShowRecentComments System requirements ====================== Changes since 3.4: * Perl 5.10 is required Documentation ====================== As of Koha 3.2, the Koha manual is now maintained in DocBook. The home page for Koha documentation is http://koha-community.org/documentation/ As of the date of these release notes, only the English version of the Koha manual is available: http://manual.koha-community.org/3.6/en/ The Git repository for the Koha manual can be found at http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary Translations ====================== Complete or near-complete translations of the OPAC and staff interface are available in this release for the following languages: * Chinese (Taiwan) * Danish * English (USA) * English (UK) * French (France) * German * Italian * Portuguese (Brazil) * Spanish Partial translations are available for various other languages. The Koha team welcomes additional translations; please see http://wiki.koha-community.org/wiki/Translating_Koha for information about translating Koha, and join the koha-translate list to volunteer: http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate The most up-to-date translations can be found at: http://translate.koha-community.org/ Release Team ====================== The release team for Koha 3.6 is Release Manager: Chris Cormack Documentation Manager: Nicole C Engard Translation Manager: Fr?d?ric Demians QA Manager: Ian Walls Bug Wranglers: MJ Ray, Marcel Roy, Paul Poulain, Mason James Release Maintainer (3.4.x): Chris Nighswonger Release Maintainer (3.6.x): Chris Nighswonger Credits ====================== We thank the following libraries who are known to have sponsored new features in Koha 3.6: * Los Gatos Public Library * NEKLS * East Brunswick Public Library * Athens County Public Libraries * Horowhenua Library Trust * Halton Borough Council * South Taranaki District Council We thank the following individuals who contributed patches to Koha 3.6.0. Nu?o L?pez Ans?tegui Alex Arnaud Larry Baerveldt Greg Barniskis D Ruth Bavousett Steven Callender Jared Camins-Esakov Colin Campbell Fernando L. Canizo Fr?d?rick Capovilla Galen Charlton Tomas Cohen Arazi Chris Cormack Jeremy Crabtree Christophe Croullebois Elliott Davis Fr?d?ric Demians St?phane Delaune Ricardo Dias Marques Jonathan Druart Nicole C. Engard Magnus Enger Katrin Fischer Amit Gupta Mason James Srdjan Jankovic Janusz Kaczmarek Ulrich Kleiber Henri-Damien LAURENT Owen Leonard Fr?re S?bastien Marie Francois Marier Julian Maurice Meenakshi.R Matthias Meusburger Sophie Meynieux Joy Nelson Chris Nighswonger Maxime Pelletier Paul Poulain Dobrica Pavlinusic MJ Ray Liz Rea Thatcher Rea Marcel de Rooy Juan Romay Sieira Brice Sanchez Jean-Andr? Santoni John Seymour Robin Sheat Fridolyn SOMERS Zeno Tajoli Jane Wagner Ian Walls Ward van Wanrooij Jesse Weaver Brett Wilkins Salvador Zaragoza Rubio We regret any omissions. If a contributor has been inadvertantly missed, please send a patch against these release notes to koha-patches at lists.koha-community.org. Revision control notes ====================== The Koha project uses Git for version control. The current development version of Koha can be retrieved by checking out the master branch of git://git.koha-community.org/koha.git The branch for Koha 3.6.x (i.e., this version of Koha and future bugfix releases) is 3.6.x. The next major feature release of Koha will be Koha 3.8.0. Bugs and feature requests ====================== Bug reports and feature requests can be filed at the Koha bug tracker at http://bugs.koha-community.org/ Ehara taku toa i te toa takitahi, engari he toa takitini From mjr at phonecoop.coop Sat Oct 22 18:57:43 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Sat, 22 Oct 2011 17:57:43 +0100 (BST) Subject: [Koha-devel] Cleaning up import tables and action log In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA3134DA7B@S-MAIL-1B.rijksmuseum.intra> Message-ID: <20111022165743.2F56C9F0E8@nail.towers.org.uk> Marcel de Rooy > Is anyone of you using code to periodically purge records from import_records, import_biblios, import_batches and/or action_logs ? > If so, would it be an idea to include such code into cleanup_database.pl in misc/cronjobs ? I'm pretty sure we do at one of our more resource-starved servers (library-owned and upgrade will happen when budget permits). It seems like a good idea to add them to cleanup_database. I think action_logs help for monitoring sometimes, so it would be nice to have that be optional. Apart from debugging, is there much help in keeping import_* around for longer? Thanks, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From mjr at phonecoop.coop Sat Oct 22 19:01:26 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Sat, 22 Oct 2011 18:01:26 +0100 (BST) Subject: [Koha-devel] Authority data import fail (UTF-8) In-Reply-To: <20111020143001.87BD51215BD3@smtp03.zmail.com> Message-ID: <20111022170126.E56939F0E8@nail.towers.org.uk> Partha Mukhopadhyay > ./bulkauthimport.pl -file /home/psm/Desktop/auth/auth_all_bn.mrc utf8 "\xE0" does not map to Unicode at /usr/lib/perl/5.10/Encode.pm line 174, <GEN12> line 1. > What is happening? Something is not working ;-) Is it possible for you to reply to the list with the output of the command "locale" and if that says UTF-8 a lot, can you prepare a sample authority file containing one record that shows the problem and put it somewhere for download, please? Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From mjr at phonecoop.coop Sat Oct 22 19:09:45 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Sat, 22 Oct 2011 18:09:45 +0100 (BST) Subject: [Koha-devel] Perl style point, was: tt style point In-Reply-To: <20110922174251.2DDC99F0E8@nail.towers.org.uk> Message-ID: <20111022170945.F16239F0E8@nail.towers.org.uk> I'm not sure this ever came back to this list, but the meeting http://librarypolice.com/koha-meetings/2011/koha.2011-10-05-10.00.log.html#l-862 agreed to use perlstyle as the recommended perltidy config from now on. I've updated http://wiki.koha-community.org/wiki/Coding_Guidelines#Perl but, returning to the original topic of this thread, http://wiki.koha-community.org/wiki/Coding_Guidelines#HTML_Templates could still do with a bit of expansion and linking to some tt resources. Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From cnighswonger at foundations.edu Sat Oct 22 19:55:25 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Sat, 22 Oct 2011 13:55:25 -0400 Subject: [Koha-devel] Koha 3.6.0 released In-Reply-To: References: Message-ID: Congrats to everyone! Great work. Kind Regards, Chris On Sat, Oct 22, 2011 at 12:33 PM, Chris Cormack wrote: > It is with great plesure that I announce the release of Koha 3.6.0. > > This is major feature release, containing 85 enhancements and 356 > bugfixes. A total of 728 patches have been included from 60 developers > in this release. A big thanks goes out to all of them, plus all the > other people involved in this release. > > You can download this release at > http://download.koha-community.org/koha-3.06.00.000.tar.gz or you can > wait a couple of days for the packages to appear at > http://debian.koha-community.org. > > Release notes are available below. > > > > RELEASE NOTES FOR KOHA 3.6.0 - 22 October 2011 > ======================================================================== > > Koha is the first free and open source software library automation package > (ILS). Development is sponsored by libraries of varying types and sizes, > volunteers, and support companies from around the world. > The website for the Koha project is > > ? ?http://koha-community.org/ > > Koha 3.6.0 can be downloaded from: > > ? ?http://download.koha-community.org/koha-3.06.00.tar.gz > > Installation instructions can be found at: > > ? ?http://wiki.koha-community.org/wiki/Installation_Documentation > > ? ?OR in the INSTALL files that come in the tarball > > Koha 3.6.0 is a major feature release. > > New features in 3.6.0 > ====================== > > ?ACQUISITIONS > ? ?* When deleting an order, items are deleted and if applicable the > ? ? ?biblio also (if no holds, subscriptions etc are attached) > ? ?* Add Basket number and Invoice number search > ? ?* Control view of baskets for vendor with a sys pref (own/branch/all) > ? ?* Control confirmation when closing a basket with a sys pref > > ?ADMINISTRATION > ? ?* New permission for overdues report > > ?CATALOGING > ? ?* Z3950 results highlighting > ? ?* Easy Analytics support > ? ?* Improve controls for cloning and deleting MARC subfields > ? ?* Capability to blank subfields in Batch Modification > ? ?* UNIMARC field 225 plugin: allow $a value data entry > ? ?* Adjust default values for MARC21 authority Fixed-Length Data Elements > ? ?* Update UNIMARC plugins > ? ?* Adding option to "attach another item" when finished attaching items > > ?CIRCULATION > ? ?* Added a checkin tab to the patron search screen > ? ?* Added enumchron field to the place holds screen > ? ?* Better hold information on the staff biblio detail screen > ? ?* Added a checked out from colum to list of checked out items > ? ? ?(syspref controlled) > ? ?* Add link to fast add framework while circulating, if a barcode > is not found > ? ?* Automatically check out fast add item after cataloging it > ? ?* Add shelving location to checkin results screen > > ?OPAC > ? ?* Paging on the opac detail page, allowing the user to move > through search results > ? ?* Recent comments view > ? ?* Added a powered by Koha footer > ? ?* Show a warning if placing a hold incurs a charge > ? ?* Added user customisable html block under the facets in search results > ? ?* Added customisable html block under OpacNav and patron account links > ? ?* Profile pictures in the OPAC next to review authors > ? ?* Show number of comments on the "Comments" tab in OPAC > > ?PATRONS > ? ?* Log membership renewal > ? ?* Allow patron update script (on OPAC) to send email using the > ? ? ?from address of the patron > ? ?* Extended attributes display much improved > ? ?* Partial fine payments > ? ?* If a patron search returns one result, redirect to patron details page > > ?MESSAGING > ? ?* Improved the email checking when sending "Hold filled" notices. > ? ?* Add today's date on checkin/checkout notices > > ?REPORTS > ? ?* Added links to the schema and reports library > ? ?* Record localuse statistics, when returning items not on issue > ? ?* Control for which branch renewals are recorded with a sys pref > > ?SEARCHING > ? ?* Added ISBN filter to advanced > ? ?* Analytic links search on full phrase title > ? ?* Control order in which facet categories display > > ?SIP > ? ?* Add Support for the Fee Paid Message > > ?ENHANCED CONTENT > ? ?* Add integration for EBSCO's Novelist Select service > ? ?* Enable Koha to fetch book covers from Open Library > > ?STAFF INTERFACE > ? ?* Improved styling of the table pager > ? ?* Add autocomplete="off" to borrowernumbers and barcode forms > ? ?* Improved the tinymce editor on the Koha news page > > ?INTERFACE > ? ?* Added crystal icon set > ? ?* Nicer style for "clear screen" button > ? ?* Added capability to limit the RSS results > > ?INTERNATIONALIZATION > ? ?* Tons of fixes to the translation tools > ? ?* Add German translation for purchase suggestion mails > ? ?* Spanish translation for SQL files > > ?INTERNALS, PACKAGING AND PERFORMANCE > ? ?* Simplified system preferences for the web installer > ? ?* Create and update the manual pages for the koha-* scripts. > ? ?* Automated backups of data and config > ? ?* Improve configurability of package building scripts > > ?COMMAND LINE UTILITIES > ? ?* cron script to allow easy anonymisation of patron circulation data > > ?BUGFIXES > ? ?* Longer userid fields > ? ?* Clean up guided reports dictionary entry process > ? ?* Circulation restrictions working when other withdrawn reasons are used > ? ?* Fixed LDAP username case issues > > ? ?Plus 356 more bugfixes > > System Preferences > ====================== > > The following system preferences are new in 3.6.0: > ?* numSearchRSSResults > ?* OpacRenewalBranch > ?* ShowReviewerPhoto > ?* BasketConfirmations > ?* MARCAuthorityControlField008 > ?* OpenLibraryCovers > ?* OPACResultsSidebar > ?* RecordLocalUseOnReturn > ?* OpacKohaUrl > ?* NovelistSelectEnabled > ?* NovelistSelectProfile > ?* NovelistSelectPassword > ?* NovelistSelectView > ?* EasyAnalyticalRecords > ?* OpacNavBottom > ?* AcqViewBaskets > ?* OpacShowRecentComments > > System requirements > ====================== > > ? ?Changes since 3.4: > > ? ?* Perl 5.10 is required > > Documentation > ====================== > > As of Koha 3.2, the Koha manual is now maintained in DocBook. ?The > home page for Koha documentation is > > ? ?http://koha-community.org/documentation/ > > As of the date of these release notes, only the English version of the > Koha manual is available: > > ? ?http://manual.koha-community.org/3.6/en/ > > The Git repository for the Koha manual can be found at > > ? ?http://git.koha-community.org/gitweb/?p=kohadocs.git;a=summary > > Translations > ====================== > > Complete or near-complete translations of the OPAC and staff > interface are available in this release for the following languages: > > ?* Chinese (Taiwan) > ?* Danish > ?* English (USA) > ?* English (UK) > ?* French (France) > ?* German > ?* Italian > ?* Portuguese (Brazil) > ?* Spanish > > Partial translations are available for various other languages. > > The Koha team welcomes additional translations; please see > > ? ?http://wiki.koha-community.org/wiki/Translating_Koha > > for information about translating Koha, and join the koha-translate > list to volunteer: > > ? ?http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-translate > > The most up-to-date translations can be found at: > > ? ?http://translate.koha-community.org/ > > Release Team > ====================== > > The release team for Koha 3.6 is > > Release Manager: ? ? ? ?Chris Cormack > Documentation Manager: ?Nicole C Engard > Translation Manager: ? ?Fr?d?ric Demians > QA Manager: ? ? ? ? ? ? Ian Walls > Bug Wranglers: ? ? ? ? ?MJ Ray, Marcel Roy, Paul Poulain, Mason James > > Release Maintainer (3.4.x): > ? ? ? ? ? ? ? ? ? ? ? ?Chris Nighswonger > Release Maintainer (3.6.x): > ? ? ? ? ? ? ? ? ? ? ? ?Chris Nighswonger > > Credits > ====================== > > We thank the following libraries who are known to have sponsored > new features in Koha 3.6: > ?* Los Gatos Public Library > ?* NEKLS > ?* East Brunswick Public Library > ?* Athens County Public Libraries > ?* Horowhenua Library Trust > ?* Halton Borough Council > ?* South Taranaki District Council > > We thank the following individuals who contributed patches to > Koha 3.6.0. > > Nu?o L?pez Ans?tegui > Alex Arnaud > Larry Baerveldt > Greg Barniskis > D Ruth Bavousett > Steven Callender > Jared Camins-Esakov > Colin Campbell > Fernando L. Canizo > Fr?d?rick Capovilla > Galen Charlton > Tomas Cohen Arazi > Chris Cormack > Jeremy Crabtree > Christophe Croullebois > Elliott Davis > Fr?d?ric Demians > St?phane Delaune > Ricardo Dias Marques > Jonathan Druart > Nicole C. Engard > Magnus Enger > Katrin Fischer > Amit Gupta > Mason James > Srdjan Jankovic > Janusz Kaczmarek > Ulrich Kleiber > Henri-Damien LAURENT > Owen Leonard > Fr?re S?bastien Marie > Francois Marier > Julian Maurice > Meenakshi.R > Matthias Meusburger > Sophie Meynieux > Joy Nelson > Chris Nighswonger > Maxime Pelletier > Paul Poulain > Dobrica Pavlinusic > MJ Ray > Liz Rea > Thatcher Rea > Marcel de Rooy > Juan Romay Sieira > Brice Sanchez > Jean-Andr? Santoni > John Seymour > Robin Sheat > Fridolyn SOMERS > Zeno Tajoli > Jane Wagner > Ian Walls > Ward van Wanrooij > Jesse Weaver > Brett Wilkins > Salvador Zaragoza Rubio > > We regret any omissions. ?If a contributor has been inadvertantly missed, > please send a patch against these release notes to > koha-patches at lists.koha-community.org. > > Revision control notes > ====================== > > The Koha project uses Git for version control. ?The current development > version of Koha can be retrieved by checking out the master branch of > > ? ?git://git.koha-community.org/koha.git > > The branch for Koha 3.6.x (i.e., this version of Koha and future bugfix > releases) is 3.6.x. > > The next major feature release of Koha will be Koha 3.8.0. > > Bugs and feature requests > ====================== > > Bug reports and feature requests can be filed at the Koha bug > tracker at > > ? ?http://bugs.koha-community.org/ > > Ehara taku toa i te toa takitahi, engari he toa takitini > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ From paul.poulain at biblibre.com Mon Oct 24 09:25:07 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Mon, 24 Oct 2011 09:25:07 +0200 Subject: [Koha-devel] Kohacon11 Mumbai day trip on 3rd November details In-Reply-To: References: Message-ID: <4EA512D3.8000001@biblibre.com> Le 22/10/2011 08:49, Koustubha Kale a ?crit : > Please let me know urgently if you would llike to join the trip so that > we can do the bookings.. Hi Koustubha, You can count/include the 3 from BibLibre -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Mon Oct 24 14:41:30 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Mon, 24 Oct 2011 14:41:30 +0200 Subject: [Koha-devel] Koha 3.6 is out, starting Koha 3.8 ! Message-ID: <4EA55CFA.2050805@biblibre.com> Hello happy hackers, As Koha 3.6 has been released on saturday, it's time to start officially Koha 3.8 I don't have all doors opened yet, but chris is in a plane back to NZ and will grant all access I need and explain some things he did as RM once he has recovered from his trip. === Bugzilla === In the meantime, I've started some work on bugzilla : * all ENH that are "needs signoff" and/or "signed off" have been switched to Rel_3_8 version. * I've added a "Koha 3.8 patches" shared query that you can add to your footers if you want. * i'll also investigate ENH that are "failed QA" and either bump them to 3.8 or close the bug as "abandonned" if it seems it's abandonned. Of course, the author will always be welcomed to reopen it and submit an acceptable patch. I'll decide looking at the age of the patch, how far is it to be acceptable, how active is the patch original author, how interesting is it to have this ENH. * looking at all ENH, I see there are 920 that are open. A large part of them have had no activity for more than 1 year. A few of them maybe good ideas, but they are not sponsored. I do the following proposition : "i'll close all ENH bugs that are not sponsored and have had no activity for more than nine months. For sponsored entries that have more than 9 months, i'll add a comment to ask wether we should wait for a patch or close the bug". If you disagree, please argue. If it's OK, I'll add this rule to the wiki. === Koha roadmap === I plan to start a wiki page with the roadmap. I'll store on this page : * what *will* be in Koha 3.8 = features/patches that have been validated and are already merged into master * what *should* be in Koha 3.8 = features/patches that have been submitted * what *could* be in Koha 3.8 = features/patches that have been announced, should be submitted in time, but you know, sometimes you don't do what you would like to do... I'll mark "could/should" only important things. I'll add in "will" everything (like what chris did with http://koha-releasemanagement.branchable.com/ ). I'll add in "could/should" only "important" things (ie : not a minor improvement to display a missing field, or add a link/control/...) I also plan to split the roadmap in 2 parts : * functionnal => for patches that are interesting for librarians. * technical => for patches that are interesting for developers I'll submit in the next days a first draft of all changes we could do in the next months (year(s) ?). That will be ambitious, of course that will be a 1st draft to discuss from what you want , my main goal being to have a clear visibility of where we would like to go and who want to endorse what. You won't probably be surprised by what will be in this list, as it's things we already have speaking of. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From henridamien.laurent at biblibre.com Mon Oct 24 15:54:11 2011 From: henridamien.laurent at biblibre.com (Henri-Damien LAURENT) Date: Mon, 24 Oct 2011 15:54:11 +0200 Subject: [Koha-devel] Perl style point, was: tt style point In-Reply-To: <20111022170945.F16239F0E8@nail.towers.org.uk> References: <20111022170945.F16239F0E8@nail.towers.org.uk> Message-ID: <1319464451.6466.7.camel@hdlaurent-laptop> Le samedi 22 octobre 2011 ? 18:09 +0100, MJ Ray a ?crit : > I'm not sure this ever came back to this list, but the meeting > http://librarypolice.com/koha-meetings/2011/koha.2011-10-05-10.00.log.html#l-862 > agreed to use perlstyle as the recommended perltidy config from now > on. > ok.... But is there a perltidy option to be sure to abide by this "perlstyle" Is "perl-style" the same as pbp ? Is that the perltidyrc in our xt in src ? > I've updated http://wiki.koha-community.org/wiki/Coding_Guidelines#Perl > but, returning to the original topic of this thread, > http://wiki.koha-community.org/wiki/Coding_Guidelines#HTML_Templates > could still do with a bit of expansion and linking to some tt resources. > > Hope that helps, -- Henri-Damien LAURENT BibLibre From psm_vu at india.com Mon Oct 24 16:15:47 2011 From: psm_vu at india.com (Partha Mukhopadhyay) Date: Mon, 24 Oct 2011 14:15:47 +0000 (UTC) Subject: [Koha-devel] Authority data import fail (UTF-8) In-Reply-To: <20111022170126.E56939F0E8@nail.towers.org.uk> References: <20111022170126.E56939F0E8@nail.towers.org.uk> Message-ID: <20111024141547.AB86C11C1@smtp02.zmail.com> An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Mon Oct 24 17:52:49 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Mon, 24 Oct 2011 17:52:49 +0200 Subject: [Koha-devel] Bugzilla changes/improvements Message-ID: <4EA589D1.9050209@biblibre.com> Hello koha-devel, I'm doing a checking of our bugzilla usage. I've added some pages on the wiki about submitting a patch, and have some questions/propositions. Please give me your opinion about them. The propositions that won't be agreed by all (unanimity) will be discussed in a later IRC meeting. Here they are, in random order. ? what's the difference between master and Rel_3_8 versions ? I feel "master" should not be used for bugs, only for ENH, and, when a patch is submitted for an ENH, it should be attached to "next planned version" (ie : Rel_3_8 those days) ? The priority is used to set "patch sent". This is a problem as we completly loose Priority field usage. A solution would be to have a patch status "patch sent" added, have the patch status always visible, and keep priority for what it's supposed to be, the priority. Patch status could then be "--" (patch not sent), "needs signoff", "does not apply"... as we have today. ? QA contact : could we do a better use of this field ? I know Ian & QA team are working/thinking to this question, so it's here just for reminder. ? Signed-off & passed QA = The signature and the QA process could be in any order: if a patch does not meet our QA rules, there's no need to test it if the QA team sees it. So maybe we have a field for "QA status" (-- / passed QA / failed) and the patch status for sign-off (-- / signed off / does not apply) ? For instance, I don't know how we could keep track of the "patch submitter" ? do we want/need ? I throw an open question here. ? bug status : it's NEW/ASSIGNED/RESOLVED and it's not really correctly used. Many bugs stay "new" = as of today, 12 bugs have a patch for version Rel_3_8 and are still marked "new". They should be "assigned". I propose to enforce the use of the "ASSIGNED". This question is connected to the question of the use of the default assignee i've asked a few weeks ago. ? Components : I proposed to clean them a while ago. Now I have concrete & detailled propositions. http://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap I've checked all entries with less than 30 bugs open, and propose something for each of them. The global idea is to have component entries close from modules we have in Koha. ? About, importedbugs, = no bugs, drop those entries. ? Authentication = 19 bugs, move them to "architecture, Internals and plumbing" ? Browser compatibility = 10 bugs, move them to "Architecture internals and plumbing" or "templates" ? bugs.koha-community.org = 2 bugs, move them to "websites, mailing lists,..." ? contribs.koha-community.org = 1 bug, move it to "websites, mailing lists,..." ? Developer documentation = 5 bugs, move them to "Architecture, internals and plumbing" ? Documentation = 11 bugs, keep them here, interesting for Nicole & doc writers ? Holidays = 2 bugs, move them to "Tools" ? Installation and upgrade = merge "command line" and "web-based" (20 and 24 repectively) ? Label printing = 27 bugs, move them to "Tools" ? MARC authority and MARC bibliographic (26 and 27 repectively) = we could merge them, not sure, i'm not proposing that, your opinion/thoughts about that ? ? MARC bibliographic staging/import = 14 bugs, move them to tools ? Self-checkout = 4, move them to "circulation" ? SIP2 = 18, move them to "circulation" or "Architecture, plumbing" ? Test suite = only 3, but keep them as we want to improve test coverage, it's to encourage ppl ! ? Transaction logs = 5, move them to "Tools" ? translate.koha-community.org = 2, move them to "Websites, Mailing lists,..." ? Z39.50, SRU, OpenSearch = 14, move them to searching ? The "hardware" field is useless. http://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=&y_axis_field=rep_platform&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap 12 are reported "MacIntosh", and not related to Mac specifically, others are PC/All/Other. I propose we remove it completly from the forms (Can we ? Use it for something else & what ?) ? The 'OS' field is useless. http://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=&y_axis_field=op_sys&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap ? 5 bugs are "windows", and 3 are "others", it does not seem they are relevant. I propose we remove it completly from the forms (Can we ? Use it for something else & what ?) ? Version field : there are many, only a few are used : http://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=&y_axis_field=version&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap Could we hide all versions that are unsupported and have no bug opened now ? (all 1.x & 2.x versions, many 3.0.x and 3.2.x versions) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From oleonard at myacpl.org Mon Oct 24 18:12:07 2011 From: oleonard at myacpl.org (Owen Leonard) Date: Mon, 24 Oct 2011 12:12:07 -0400 Subject: [Koha-devel] Bugzilla changes/improvements In-Reply-To: <4EA589D1.9050209@biblibre.com> References: <4EA589D1.9050209@biblibre.com> Message-ID: > ? The priority is used to set "patch sent". This is a problem as we > completly lose Priority field usage. I don't mind that we lose Priority. Priority is completely arbitrary: a bug which is high priority for me might not be high priority for the release manager. I ignore this setting altogether. > I propose > to enforce the use of the "ASSIGNED". What do you mean by "enforce?" I reset the status to "ASSIGNED" whenever I see a bug which seems to be so. There's not much we can do besides point out the error. This question is connected to the > question of the use of the default assignee i've asked a few weeks ago. > ? Components : I proposed to clean them a while ago. Now I have concrete > & detailled propositions. I really don't see any problem with having lots of components. In fact I'd vote for more rather than fewer. > ? The "hardware" field is useless. It isn't if you have a bug which is tied to your particular hardware. If it's useless it's probably because people don't remember to set it. Can we force it to default to "Any" since most bugs are not hardware-dependent? > ? The 'OS' field is useless. Same as hardware: seldom-used, but maybe not useless. Can they be hidden when "advanced fields" are hidden? > Could we hide all versions that are unsupported and have no bug opened > now ? (all 1.x & 2.x versions, many 3.0.x and 3.2.x versions) Can Bugzilla be configured to show only a selection of versions for which there are bugs? I'm in favor of this change if so. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From oleonard at myacpl.org Mon Oct 24 18:20:09 2011 From: oleonard at myacpl.org (Owen Leonard) Date: Mon, 24 Oct 2011 12:20:09 -0400 Subject: [Koha-devel] Bugzilla changes/improvements In-Reply-To: References: <4EA589D1.9050209@biblibre.com> Message-ID: Oh, and my vote for the most urgently-needed change to Bugzilla? Please change "Rel_3_8" to "rel_3_8" like all the other "rel_*_*" entries, it's driving me crazy!! -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org From paul.poulain at biblibre.com Mon Oct 24 18:29:44 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Mon, 24 Oct 2011 18:29:44 +0200 Subject: [Koha-devel] Bugzilla changes/improvements In-Reply-To: References: <4EA589D1.9050209@biblibre.com> Message-ID: <4EA59278.1090708@biblibre.com> Le 24/10/2011 18:20, Owen Leonard a ?crit : > Oh, and my vote for the most urgently-needed change to Bugzilla? > > Please change "Rel_3_8" to "rel_3_8" like all the other "rel_*_*" > entries, it's driving me crazy!! Agreed, I saw this small-but-very-annoying detail today, but can't change it yet (no access) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Mon Oct 24 18:38:55 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Mon, 24 Oct 2011 18:38:55 +0200 Subject: [Koha-devel] Bugzilla changes/improvements In-Reply-To: References: <4EA589D1.9050209@biblibre.com> Message-ID: <4EA5949F.6030605@biblibre.com> Le 24/10/2011 18:12, Owen Leonard a ?crit : >> ? The priority is used to set "patch sent". This is a problem as we >> completly lose Priority field usage. > > I don't mind that we lose Priority. Priority is completely arbitrary: > a bug which is high priority for me might not be high priority for the > release manager. I ignore this setting altogether. My arguments: * having "patch sent" in priority is not really intuitive * having it in the "patch status" is logic * we could completly discard priority if no-one want to use it. But I feel we could use it to set a priority as a supplementary information (with the severity) : a bug can be critical, but happening only in a very rare situation (low priority), or not very important, but annoying everyday ! So I think both fields can be usefull. >> I propose >> to enforce the use of the "ASSIGNED". > > What do you mean by "enforce?" I reset the status to "ASSIGNED" > whenever I see a bug which seems to be so. There's not much we can do > besides point out the error. yep, and by "enforcing" I was implying "adding this into submitting a patch guidelines on the wiki" >> ? Components : I proposed to clean them a while ago. Now I have concrete >> & detailled propositions. > > I really don't see any problem with having lots of components. In fact > I'd vote for more rather than fewer. really ? I always need many seconds when I file a bug to say "is component XXX the right one" ? Other's opinion ? At least, please check my detailled proposition, some could really be merged/removed. >> ? The "hardware" field is useless. > It isn't if you have a bug which is tied to your particular hardware. > If it's useless it's probably because people don't remember to set it. > Can we force it to default to "Any" since most bugs are not > hardware-dependent? >> ? The 'OS' field is useless. > > Same as hardware: seldom-used, but maybe not useless. Can they be > hidden when "advanced fields" are hidden? By "useless" I was meaning "unused". I couldn't find a bug where the "hardware" info was relevant. Same for OS field. That's why I suggest to drop those fields. But having them being hidden would be OK for me. As you rise this point : can we put what we want on "No advanced fields" ? If yes, I would add Status/sponsored/priority/patch status to "no advanced fields" and remove OS and hardware from there, you're right. >> Could we hide all versions that are unsupported and have no bug opened >> now ? (all 1.x & 2.x versions, many 3.0.x and 3.2.x versions) > > Can Bugzilla be configured to show only a selection of versions for > which there are bugs? I'm in favor of this change if so. I don't know, and that was my proposition & hope... -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From ian.walls at bywatersolutions.com Mon Oct 24 18:46:29 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Mon, 24 Oct 2011 12:46:29 -0400 Subject: [Koha-devel] Bugzilla changes/improvements In-Reply-To: <4EA589D1.9050209@biblibre.com> References: <4EA589D1.9050209@biblibre.com> Message-ID: Everyone, First off, Paul, thanks for getting this rolling. I've been thinking a lot about optimizing our Bugzilla set up to match today's current practices. ByWater Solutions uses Bugzilla internally for partners support needs, so I'm pretty well-versed in some of the configuration changes that we can make. Here's my take on Paul's comments: *Versions: * I think the versions in this list should correspond to the main branches on the Koha Git repo. So, we'd have 3.2.x, 3.4.x, 3.6.x and master. A bug report should be connected to the most current version (if it's a problem in 3.6.x and master, report is as master). For enhancements, I say we report them against master. Then, when the feature freeze rolls around, we take everything that has submitted code so far, and move it 3.8.x. If it makes it, great, if it doesn't, after release it gets moved back to master. We can delete old version values in BZ, but there isn't a way to obsolete them like there are with other field statuses. I think if we find anything on a version older than 3.0.x, we should probably: a) verify it's still relevant b) remove or re-report it in the current context *Component*: I'm with Owen that more is better than less, here. Each component controls the default Assignee, and having a more finely-grained default assignee's list will keep folks from getting overloaded with bug assignments (in theory). The universal problem here being, of course, that while folks can be ASSIGNED a bug, we can never guarantee they'll DO anything about it. We're all free agents, and cannot enforce any sort of assignment or timetable outside on a community-wide scale. Perhaps the issue with "which component to I choose" could be mollified with some kind instructions saying "It doesn't really matter, it'll get to the right place! Just be clear in your report" *Status*: We don't use the regular status field much at all, except to mark the patch as "resolved". Why don't we put the Patch Status into the regular ol' Status field? That would have a couple advantages: - Easier searching, since it's a default value, not a custom value - We can enable Workflows between statuses - We no longer have the dependency on Priority to control the display of this critical value I'll write up more about the potential for the Workflows, and how I hope the QA team can fit into that, in another post. *Priority:* I agree with Owen that this is pretty arbitrary... it may not be useful to us right now. *Severity:* we should keep, since it highlights issues in red and bold if they're critical or blocker *Hardware/OS*: should keep, as well, though they are very seldom useful. A little cluttersome, but a handy categorization for those few times when it's relevant. *QA Contact:* I'd like to move the 'bugs at lists.koha-community.org' from being the Default QA contact to a Global Watcher. This makes more sense to me, since it's always supposed to report on things, and if someone changed the QA contact on a bug report, the list would no longer get notified on update. The QA Contact field can then be used assign the QA portion of the patch submission process to one of the three QA team members (myself, Marcel de Rooy and Jonathan Druart). This'll make it easier for us to divide the work, and make sure that work submitted by one company is cross-checked by another. I think we should also start talking about making BZ a more central component in our Patch Submission Procedures. I know I don't use the patches list-serv now as anymore than a notification means. Everything I write, test and pass QA is done on Bugzilla (either through Git BZ or manually). I think that's the way with most of our other developers, as well More soon.... -Ian On Mon, Oct 24, 2011 at 11:52 AM, Paul Poulain wrote: > Hello koha-devel, > > I'm doing a checking of our bugzilla usage. I've added some pages on the > wiki about submitting a patch, and have some questions/propositions. > Please give me your opinion about them. The propositions that won't be > agreed by all (unanimity) will be discussed in a later IRC meeting. > > Here they are, in random order. > > ? what's the difference between master and Rel_3_8 versions ? I feel > "master" should not be used for bugs, only for ENH, and, when a patch is > submitted for an ENH, it should be attached to "next planned version" > (ie : Rel_3_8 those days) > > ? The priority is used to set "patch sent". This is a problem as we > completly loose Priority field usage. A solution would be to have a > patch status "patch sent" added, have the patch status always visible, > and keep priority for what it's supposed to be, the priority. Patch > status could then be "--" (patch not sent), "needs signoff", "does not > apply"... as we have today. > > ? QA contact : could we do a better use of this field ? I know Ian & QA > team are working/thinking to this question, so it's here just for reminder. > > ? Signed-off & passed QA = The signature and the QA process could be in > any order: if a patch does not meet our QA rules, there's no need to > test it if the QA team sees it. So maybe we have a field for "QA status" > (-- / passed QA / failed) and the patch status for sign-off (-- / signed > off / does not apply) > > ? For instance, I don't know how we could keep track of the "patch > submitter" ? do we want/need ? I throw an open question here. > > ? bug status : it's NEW/ASSIGNED/RESOLVED and it's not really correctly > used. > Many bugs stay "new" = as of today, 12 bugs have a patch for version > Rel_3_8 and are still marked "new". They should be "assigned". I propose > to enforce the use of the "ASSIGNED". This question is connected to the > question of the use of the default assignee i've asked a few weeks ago. > > ? Components : I proposed to clean them a while ago. Now I have concrete > & detailled propositions. > > http://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap > I've checked all entries with less than 30 bugs open, and propose > something for each of them. The global idea is to have component entries > close from modules we have in Koha. > ? About, importedbugs, = no bugs, drop those entries. > ? Authentication = 19 bugs, move them to "architecture, Internals and > plumbing" > ? Browser compatibility = 10 bugs, move them to "Architecture internals > and plumbing" or "templates" > ? bugs.koha-community.org = 2 bugs, move them to "websites, mailing > lists,..." > ? contribs.koha-community.org = 1 bug, move it to "websites, mailing > lists,..." > ? Developer documentation = 5 bugs, move them to "Architecture, > internals and plumbing" > ? Documentation = 11 bugs, keep them here, interesting for Nicole & doc > writers > ? Holidays = 2 bugs, move them to "Tools" > ? Installation and upgrade = merge "command line" and "web-based" (20 > and 24 repectively) > ? Label printing = 27 bugs, move them to "Tools" > ? MARC authority and MARC bibliographic (26 and 27 repectively) = we > could merge them, not sure, i'm not proposing that, your > opinion/thoughts about that ? > ? MARC bibliographic staging/import = 14 bugs, move them to tools > ? Self-checkout = 4, move them to "circulation" > ? SIP2 = 18, move them to "circulation" or "Architecture, plumbing" > ? Test suite = only 3, but keep them as we want to improve test > coverage, it's to encourage ppl ! > ? Transaction logs = 5, move them to "Tools" > ? translate.koha-community.org = 2, move them to "Websites, Mailing > lists,..." > ? Z39.50, SRU, OpenSearch = 14, move them to searching > > ? The "hardware" field is useless. > > http://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=&y_axis_field=rep_platform&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap > 12 are reported "MacIntosh", and not related to Mac specifically, others > are PC/All/Other. > I propose we remove it completly from the forms (Can we ? Use it for > something else & what ?) > > ? The 'OS' field is useless. > > http://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=&y_axis_field=op_sys&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap > ? 5 bugs are "windows", and 3 are "others", it does not seem they are > relevant. > I propose we remove it completly from the forms (Can we ? Use it for > something else & what ?) > > ? Version field : there are many, only a few are used : > > http://bugs.koha-community.org/bugzilla3/report.cgi?x_axis_field=&y_axis_field=version&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&deadlinefrom=&deadlineto=&bug_id=&bug_id_type=anyexact&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=&chfieldto=Now&field0-0-0=noop&type0-0-0=noop&value0-0-0=&format=table&action=wrap > Could we hide all versions that are unsupported and have no bug opened > now ? (all 1.x & 2.x versions, many 3.0.x and 3.2.x versions) > > > -- > Paul POULAIN > http://www.biblibre.com > Expert en Logiciels Libres pour l'info-doc > Tel : (33) 4 91 81 35 08 > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjr at phonecoop.coop Mon Oct 24 18:46:51 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Mon, 24 Oct 2011 17:46:51 +0100 (BST) Subject: [Koha-devel] Koha 3.6 is out, starting Koha 3.8 ! In-Reply-To: <4EA55CFA.2050805@biblibre.com> Message-ID: <20111024164651.633D09F0E8@nail.towers.org.uk> Paul Poulain wrote: [...] > * i'll also investigate ENH that are "failed QA" and either bump them to > 3.8 or close the bug as "abandonned" if it seems it's abandonned. Of > course, the author will always be welcomed to reopen it and submit an > acceptable patch. I'll decide looking at the age of the patch, how far > is it to be acceptable, how active is the patch original author, how > interesting is it to have this ENH. I feel that just closing the bug as abandoned without further action is almost always going to be the wrong thing to do, no matter what the severity. For example, just this weekend, I came across bug 6142 that appeared to have been abandoned by biblibre workers, but was a simple task to clean up and sign off. I think the above policy will result in losing a lot of viable code. What do other wranglers think? Also, does QAM like this idea? > * looking at all ENH, I see there are 920 that are open. A large part of > them have had no activity for more than 1 year. A few of them maybe good > ideas, but they are not sponsored. I do the following proposition : > "i'll close all ENH bugs that are not sponsored and have had no activity > for more than nine months. For sponsored entries that have more than 9 > months, i'll add a comment to ask wether we should wait for a patch or > close the bug". If you disagree, please argue. If it's OK, I'll add this > rule to the wiki. ENH bugs in the needs-sponsor state probably have willing developers attached. I think it would be good to first post a list to koha at lists whether any libraries are interested in sponsoring and give them some time to respond. I'll do that in a moment. Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From mjr at phonecoop.coop Mon Oct 24 19:06:38 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Mon, 24 Oct 2011 18:06:38 +0100 (BST) Subject: [Koha-devel] Koha 3.6 is out, starting Koha 3.8 ! In-Reply-To: <4EA55CFA.2050805@biblibre.com> Message-ID: <20111024170638.A79E09F0E8@nail.towers.org.uk> Paul Poulain wrote: [...] > * looking at all ENH, I see there are 920 that are open. A large part of > them have had no activity for more than 1 year. A few of them maybe good > ideas, but they are not sponsored. I do the following proposition : > "i'll close all ENH bugs that are not sponsored and have had no activity > for more than nine months. For sponsored entries that have more than 9 > months, i'll add a comment to ask wether we should wait for a patch or > close the bug". [...] Actually, I'm not posting to koha at lists because I can't replicate the above results. I've saved "ENH bugs that are not sponsored and have had no activity for more than nine months" as a shared search called "stalled-enh" and it has only 5 entries at present: 3296 enh replace sessionlog with Perl4Log implementation Authenti 5387 enh Support for NISO CORE: Cost of Resource Exchange Protocol Acquisit 5388 enh Circulation of related/requiring items (like Book and CD sets) Circulat 3230 enh Automatic Credit when Lost item is returned Circulat 3732 enh field lengths and multi-line boxes Catalogi I also searched for sponsored ENHs which are 270+ days unchanged and found 41. Of those, only one had failed QA, which was bug 4241 (Add lost/claims returned displays to patron record). There's a big difference between 46 and "a large part of" 920. Are you sure your search parameters were correct? There were also two that were seeking developer: 3237 enh OpenID patron authentication Patrons 5395 enh C4::Acquisition::SearchOrder POD inconsistent with function Develope I've asked 3237 if they are still seeking a developer and I'll do 5395 as soon as I get a few minutes (next Saturday maybe). Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From ian.walls at bywatersolutions.com Mon Oct 24 19:13:12 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Mon, 24 Oct 2011 13:13:12 -0400 Subject: [Koha-devel] Koha 3.6 is out, starting Koha 3.8 ! In-Reply-To: <20111024164651.633D09F0E8@nail.towers.org.uk> References: <4EA55CFA.2050805@biblibre.com> <20111024164651.633D09F0E8@nail.towers.org.uk> Message-ID: Anything that's Failed QA may still be in the process of being developed. I'd recommend trying to reinvigorate the conversation in the comments before marking such as abandoned. I see no problem with leaving enhancement requests open, so long as they still apply. There are enhancements I was looking at years ago that are still not available, and would still be applicable. For my part, the list I'm concerned with is the "Signed Off" list. For those doing the signing off, the "Needs Signoff" makes a good starting place. And for everyone else writing patches, usually we're doing them to fix a specific issue in front of us (if you're scanning through the bugs list to find issues to squash, I commend you!). Being able to try a bit of work to an existing bug report may be easier than filing a new one, provided you can find it. That's made easier by leaving old reports open, even if there hasn't been active on them recently. -Ian On Mon, Oct 24, 2011 at 12:46 PM, MJ Ray wrote: > Paul Poulain wrote: [...] > > * i'll also investigate ENH that are "failed QA" and either bump them to > > 3.8 or close the bug as "abandonned" if it seems it's abandonned. Of > > course, the author will always be welcomed to reopen it and submit an > > acceptable patch. I'll decide looking at the age of the patch, how far > > is it to be acceptable, how active is the patch original author, how > > interesting is it to have this ENH. > > I feel that just closing the bug as abandoned without further action > is almost always going to be the wrong thing to do, no matter what the > severity. For example, just this weekend, I came across bug 6142 that > appeared to have been abandoned by biblibre workers, but was a simple > task to clean up and sign off. I think the above policy will result > in losing a lot of viable code. What do other wranglers think? > > Also, does QAM like this idea? > > > * looking at all ENH, I see there are 920 that are open. A large part of > > them have had no activity for more than 1 year. A few of them maybe good > > ideas, but they are not sponsored. I do the following proposition : > > "i'll close all ENH bugs that are not sponsored and have had no activity > > for more than nine months. For sponsored entries that have more than 9 > > months, i'll add a comment to ask wether we should wait for a patch or > > close the bug". If you disagree, please argue. If it's OK, I'll add this > > rule to the wiki. > > ENH bugs in the needs-sponsor state probably have willing developers > attached. I think it would be good to first post a list to koha at lists > whether any libraries are interested in sponsoring and give them some > time to respond. I'll do that in a moment. > > Hope that helps, > -- > MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. > http://koha-community.org supporter, web and LMS developer, statistician. > In My Opinion Only: see http://mjr.towers.org.uk/email.html > Available for hire for Koha work http://www.software.coop/products/koha > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjr at phonecoop.coop Mon Oct 24 19:18:38 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Mon, 24 Oct 2011 18:18:38 +0100 (BST) Subject: [Koha-devel] Perl style point, was: tt style point In-Reply-To: <1319464451.6466.7.camel@hdlaurent-laptop> Message-ID: <20111024171838.500209F0E8@nail.towers.org.uk> Henri-Damien LAURENT > Le samedi 22 octobre 2011 ? 18:09 +0100, MJ Ray a ?crit : > > I'm not sure this ever came back to this list, but the meeting > > http://librarypolice.com/koha-meetings/2011/koha.2011-10-05-10.00.log.html#l-862 > > agreed to use perlstyle as the recommended perltidy config from now > > on. > > > ok.... But is there a perltidy option to be sure to abide by this > "perlstyle" As I understand it, perltidy defaults to perlstyle, so just run it with no options or rc file. > Is "perl-style" the same as pbp ? No. > Is that the perltidyrc in our xt in src ? No. Hope that informs, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From ian.walls at bywatersolutions.com Mon Oct 24 20:30:57 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Mon, 24 Oct 2011 14:30:57 -0400 Subject: [Koha-devel] Proposed changes to our Patch Submission and QA workflows Message-ID: Everyone, In an effort to make patch submission and quality assurance easier on everyone for this next release cycle, I've got some proposals to run by you all. 1. In Bugzilla, move the Koha Bugs List from being the Default QA Contact to a Global Watcher. This has two advantages: 1. It frees up the QA Contact field for use by the QA Team 2. It guarantees that the Bugs List always gets included on the changes; with the current set up, someone could in theory remove the Bugs List as QA contact, preventing the list from getting updates. 2. To reduce email traffic, I propose we stop sending SIGNED OFF patches to the patches list. We've got Bugzilla lists (which can be connected to RSS and daily croned emails) which will inform the QA team on what patches are ready for QA. I did not use the patches list much this last release cycle to direct my QA work; it was all based of the Bugzilla statuses 2a. Ideally, I'd like to set up Bugzilla to automatically send the patches to the listserv for us, or to be able to accept patches sent to the listserv as attachments. This is going to take some custom coding, so it's probably not practical for right now. 3. Now that I'm not the only QA person for the release cycle, I'd like to formalize our rules about making sure that any submitted patch doesn't get processed solely by one company. I felt uncomfortable every time I passed a patch both written and signed off by ByWater teammates, because while I was sure it was good code, I knew I had a bias (often times, the code was fixing an issue one of our partners had reported). My strategy for 3.6 was to acknowledge the bias, and ask if anyone had any objections. With 3.8, I can pass anything that I write, or that is written/signed-off by ByWater alone, to Marcel or Jonathan for QA testing. Here're the rules I'd like to see in place: 1. A patch may not be written and signed off by the same person (existing rule) 2. The QA team consists of the Release Manager, the Quality Assurance Manager, and the Quality Assurance Assistants. This team has the right to move a patch through QA. 3. The QAM delegates the QA work between himself and the QAAs, in accordance with the rules. 4. A patch may not be written and QA'ed by the same person 5. A patch may not be written, signed off and QA'ed by any group of people in the same institution 6. A patch MAY be signed off and QA'ed by the same member of the QA team, but the RM may challenge this if he feels the patch needs more testing. Rule 5 still applies in this case. Comments? Ideas? Counter-proposals? -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From dpavlin at rot13.org Mon Oct 24 21:37:42 2011 From: dpavlin at rot13.org (Dobrica Pavlinusic) Date: Mon, 24 Oct 2011 21:37:42 +0200 Subject: [Koha-devel] utf-8 handling in Koha Message-ID: <20111024193742.GA31433@rot13.org> In our migration to new koha, we hit bug 6554. We are having similar problem, but in our case we don't use localized templates but have utf-8 characters inside MySQL which get double utf-8 encoded before they are sent to browser. 1: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6554 Below is short summary of changes from patch: This patch tries to clean up utf-8 handling in Koha. In current implementation (mostly commented out in this patch) uses heuristic to guess which strings need decoding from utf-8 to binary representation and doesn't support utf-8 characters in templates and has problems with utf-8 data from database. With this changes, Koha perl code always uses utf-8 encoding correctly. All incomming data from database is allready correctly marked as utf-8, and decoding of utf8 is required only from Zebra and XSLT transfers which don't set utf-8 flag correctly. For output, standard perl :utf8 handler is used removing various "wide character" warnings as side-effect. I would love to hear your thoughts on this approach. So far, I know that it breaks CGI::Session (which is documented as known bug in it's documentation) so after first reload library names, shelfs and other data returned from session isn't encoded correctly. I would also need to check if this change affect LDAP, Z39.50 encoding and SIP server, but before I start down this road do you see any reasons not to persueue it? Compatibility with older perl versions might be one reason. I'm running perl v5.10.1 from Debian squeeze. -- Dobrica Pavlinusic 2share!2flame dpavlin at rot13.org Unix addict. Internet consultant. http://www.rot13.org/~dpavlin From chris at bigballofwax.co.nz Tue Oct 25 04:19:47 2011 From: chris at bigballofwax.co.nz (Chris Cormack) Date: Tue, 25 Oct 2011 15:19:47 +1300 Subject: [Koha-devel] Koha 3.6 is out, starting Koha 3.8 ! In-Reply-To: <4EA55CFA.2050805@biblibre.com> References: <4EA55CFA.2050805@biblibre.com> Message-ID: On 25 October 2011 01:41, Paul Poulain wrote: > Hello happy hackers, > > As Koha 3.6 has been released on saturday, it's time to start officially > Koha 3.8 > I don't have all doors opened yet, but chris is in a plane back to NZ > and will grant all access I need and explain some things he did as RM > once he has recovered from his trip. > You have access to bugzilla and to the master branch in git now. Chris From Brian.S.Weissman at disney.com Fri Oct 21 16:18:50 2011 From: Brian.S.Weissman at disney.com (Weissman, Brian S.) Date: Fri, 21 Oct 2011 10:18:50 -0400 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: References: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> <1319148711.18770.3.camel@zarathud> <667301C2-C408-4C23-A579-0CD2C571BBDE@disney.com> <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE79@SM-FLOR-VXMB06A.wdw.disney.com> Message-ID: <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE97@SM-FLOR-VXMB06A.wdw.disney.com> Jared, Thanks for the info, but the results appear to be the same without the index line, minus the GPG error. From tracing the dependencies, it looks to me like a bogus requirement somewhere along the way. koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libyaz4 The following packages have unmet dependencies: libyaz4 : Depends: libgnutls26 (>= 2.12.6.1-0) but 2.8.6-1 is to be installed E: Broken packages I looked in /var/lib/dpkg/status and found that libgnutls26 is version 2.8.6-1. Upgrading that tells me that the latest version is installed. This makes me think there is a bad dependency with libyaz4. However, this is the info in the status file for that package: Package: libyaz4 Status: install ok installed Priority: extra Section: libs Installed-Size: 1768 Maintainer: Vincent Danjean Architecture: i386 Source: yaz Version: 4.0.11-1 Replaces: libyaz Depends: libc6 (>= 2.7), libgnutls26 (>= 2.7.14-0), libicu44 (>= 4.4.1-1), libwrap0 (>= 7.6-4~), libxml2 (>= 2.7.4), libxslt1.1 (>= 1.1.25) Breaks: idzebra (<= 1.3.4-2), libyaz, php4-yaz (<= 4.1.2-5) Description: The YAZ Z39.50 toolkit (runtime files) YAZ is a toolkit that allows you to develop software using the ANSI Z39.50/ISO23950 standard for information retrieval. . This package includes runtime files. Homepage: http://www.indexdata.dk/yaz/ I am not sure where to go from here. Thanks, Bri Brian Weissman WDW BT, Technical Specialist Team Disney North - 303B Office: 407.828.4751 Brian.S.Weissman at Disney.com [cid:image001.png at 01CC8FDA.AE3B8300] From: Jared Camins-Esakov [mailto:jcamins at cpbibliography.com] Sent: Friday, October 21, 2011 10:10 AM To: Weissman, Brian S. Cc: koha-devel at lists.koha-community.org Subject: Re: [Koha-devel] Koha uninstalled by Debian Linux "update" Brian and David, Please keep these discussions on the list, so that anyone else encountering these issues in the future will be able to find the fix. It looks to me like your problem is the GPG key for the indexdata repository. The good news is, you don't need the indexdata repository anymore, I don't think. Try removing that line from /etc/apt/sources.list, rerunning apt-get update, and reinstalling koha-common. Regards, Jared On Fri, Oct 21, 2011 at 10:05 AM, Weissman, Brian S. > wrote: Here is what I have found so far. It looks like something in the automatic updates told the system to remove koha. This excerpt seems to be the relevant bit from history.log: Start-Date: 2011-10-20 10:28:54 Install: libidzebra-2.0:i386 (2.0.49-1indexdata, automatic) Upgrade: libidzebra-2.0-mod-grs-regx:i386 (2.0.44-2, 2.0.49-1indexdata), libidzebra-2.0-dev:i386 (2.0.44-2, 2.0.49-1indexdata), libidzebra-2.0-mod-grs-xml:i386 (2.0.44-2, 2.0.49-1indexdata) Remove: koha-common:i386 (3.5-1~git+20111017180723.41928b08), libidzebra-2.0-mod-dom:i386 (2.0.44-2), libidzebra-2.0-0:i386 (2.0.44-2), libidzebra-2.0-modules:i386 (2.0.49-1indexdata), libidzebra-2.0-mod-grs-marc:i386 (2.0.44-2), idzebra-2.0:i386 (2.0.44-2), libidzebra-2.0-mod-alvis:i386 (2.0.44-2), idzebra-2.0-utils:i386 (2.0.44-2), libidzebra-2.0-mod-text:i386 (2.0.44-2) End-Date: 2011-10-20 10:29:03 Start-Date: 2011-10-20 10:29:28 Install: libreadline5:i386 (5.2-7, automatic) Upgrade: tzdata:i386 (2011k-0squeeze1, 2011l-0squeeze1) End-Date: 2011-10-20 10:29:32 And this is from the term.log: Log started: 2011-10-20 10:28:54 Removing koha-common ... Stopping Zebra server for koha Removing idzebra-2.0 ... Removing idzebra-2.0-utils ... Removing libidzebra-2.0-modules ... Removing libidzebra-2.0-mod-text ... Processing triggers for man-db ... Preparing to replace libidzebra-2.0-mod-grs-xml 2.0.44-2 (using ... Unpacking replacement libidzebra-2.0-mod-grs-xml ... Preparing to replace libidzebra-2.0-mod-grs-regx 2.0.44-2 (using ... Unpacking replacement libidzebra-2.0-mod-grs-regx ... Removing libidzebra-2.0-mod-grs-marc ... Removing libidzebra-2.0-mod-dom ... Removing libidzebra-2.0-mod-alvis ... Preparing to replace libidzebra-2.0-dev 2.0.44-2 (using ... Unpacking replacement libidzebra-2.0-dev ... Processing triggers for man-db ... Removing libidzebra-2.0-0 ... Selecting previously deselected package libidzebra-2.0. Unpacking libidzebra-2.0 (from ... Setting up libidzebra-2.0 (2.0.49-1indexdata) ... Setting up libidzebra-2.0-mod-grs-xml (2.0.49-1indexdata) ... Setting up libidzebra-2.0-mod-grs-regx (2.0.49-1indexdata) ... Setting up libidzebra-2.0-dev (2.0.49-1indexdata) ... Log ended: 2011-10-20 10:29:03 Log started: 2011-10-20 10:29:28 Preparing to replace tzdata 2011k-0squeeze1 (using ... Unpacking replacement tzdata ... Setting up tzdata (2011l-0squeeze1) ... Current default time zone: 'America/New_York' Local time is now: Thu Oct 20 10:29:30 EDT 2011. Universal Time is now: Thu Oct 20 14:29:30 UTC 2011. Run 'dpkg-reconfigure tzdata' if you wish to change it. Selecting previously deselected package libreadline5. Unpacking libreadline5 (from ... Setting up libreadline5 (5.2-7) ... Log ended: 2011-10-20 10:29:32 I have since tried to reinstall koha and followed a string of dependencies and had no success. Here is the chain with the errors. Let me know if you want more details. koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get update (list of gets deleted for space) Fetched 11.6 MB in 10s (1,091 kB/s) Reading package lists... Done W: GPG error: http://ftp.indexdata.dk wheezy Release: The following signatures w ere invalid: KEYEXPIRED 1319102732 KEYEXPIRED 1319102732 KEYEXPIRED 1319102732 koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install koha The following packages have unmet dependencies: koha : Depends: koha-common but it is not going to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install koha-common The following packages have unmet dependencies: koha-common : Depends: idzebra-2.0 but it is not going to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install idzebra-2.0 The following packages have unmet dependencies: idzebra-2.0 : Depends: idzebra-2.0-utils (= 2.0.49-1indexdata) but it is not going to be installed Depends: libidzebra-2.0-modules but it is not going to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install idzebra-2.0-utils The following packages have unmet dependencies: idzebra-2.0-utils : Depends: libyaz4 (>= 4.2.10) but 4.0.11-1 is to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libidzebra-2.0-modules The following packages have unmet dependencies: libidzebra-2.0-modules : Depends: libidzebra-2.0-mod-alvis but it is not going to be installed Depends: libidzebra-2.0-mod-dom but it is not going to be installed Depends: libidzebra-2.0-mod-grs-marc but it is not going to be installed Depends: libidzebra-2.0-mod-text but it is not going to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libyaz4 The following packages have unmet dependencies: libyaz4 : Depends: libgnutls26 (>= 2.12.6.1-0) but 2.8.6-1 is to be installed E: Broken packages koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get install libgnutls26 libgnutls26 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. koha-koha at WW-R-ITLWDW1K5M:~$ sudo apt-get upgrade libgnutls26 Reading package lists... Done Building dependency tree Reading state information... Done The following packages have been kept back: libyaz4 yaz 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. That is where I dead end. Brian Weissman WDW BT, Technical Specialist Team Disney North - 303B Office: 407.828.4751 Brian.S.Weissman at Disney.com -----Original Message----- From: Hartman, David W. - GBTS Library Sent: Thursday, October 20, 2011 6:18 PM To: Robin Sheat Cc: Weissman, Brian S. Subject: Re: [Koha-devel] Koha uninstalled by Debian Linux "update" Yes, we'll report what we can and thanks for your help! Sent from my iPhone! Pardon typos, etc. On Oct 20, 2011, at 6:12 PM, "Robin Sheat" > wrote: > Hartman, David W. - GBTS Library schreef op do 20-10-2011 om 11:44 > [-0400]: >> Just a heads up that a recent ?update? by Debian Linux removed the >> application Koha ? my apache and data files apparently are fine. >> >> How do I reinstall Koha without damaging or overwriting my data? If >> anyone has any experience with this, please let me know. >> > Just reinstall the koha-common package. Grab a backup if you want to be > safe, but I'd expect it would be fine. If everything in /etc/ is > untouched (which I'd expect) then it should just magically work again. > >> If you see the red ?burst? in the upper right hand corner, only do the >> safe install .. or else? > > Are you able to provide me with more information? Perhaps the logs > in /var/log/apt or so. I'd like to see what was going on there. > > Robin. > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ -- Jared Camins-Esakov Bibliographer, C & P Bibliography Services, LLC (phone) +1 (917) 727-3445 (e-mail) jcamins at cpbibliography.com (web) http://www.cpbibliography.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 10025 bytes Desc: image001.png URL: From ali.basharyar at acku.edu.af Sun Oct 23 11:42:39 2011 From: ali.basharyar at acku.edu.af (Ali Basharyar) Date: Sun, 23 Oct 2011 14:12:39 +0430 Subject: [Koha-devel] Database Developmnet Project -ACKU Message-ID: <002001cc9168$338544e0$9a8fcea0$@basharyar@acku.edu.af> Dear Sir /Madam, We are a Digital Library in Kabul Afghanistan, currently we are using Greenstone Database for our online library management system. ( http://www.nzdl.org/gsdlmod/cgi-bin/library?a=p&p=about&c=acku&l=en&nl=1%3E) , our current database cannot support many features that can play very vital role in our activities like: Serial Control and Copy cataloging, Therefore, it has been a high concern for our management to sort this issue out by a professional and very standard solution. Please find the attached for our new database wish list. we are looking for a company that can help us develop a new database (KOHA) which should properly run on English and two Afghan languages (Dari and Pashto), therefore, we have already shared our wish list with some developers. some were ready to help us on English part but did not seem to be interested in two of our local languages, Dari and Pashto. however, according to our basic research there are some instances of KOHA running on Farsi (Dari) which shall be helpful. Depending on our wish list, Kindly enlighten us by your kind suggestions and recommendations and your interest if you would like to do this project. Please do not hesitate to contact me for any query! Kind Regards Ali Basharyar IT-ACKU ali.basharyar at acku.edu.af +93 (0) 799 707 667 www.acku.edu.af -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ACKU database system wish list database (4).doc Type: application/msword Size: 59392 bytes Desc: not available URL: From paul.poulain at biblibre.com Tue Oct 25 10:37:59 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 10:37:59 +0200 Subject: [Koha-devel] Perl style point, was: tt style point In-Reply-To: <20111024171838.500209F0E8@nail.towers.org.uk> References: <20111024171838.500209F0E8@nail.towers.org.uk> Message-ID: <4EA67567.9030803@biblibre.com> Le 24/10/2011 19:18, MJ Ray a ?crit : >> ok.... But is there a perltidy option to be sure to abide by this >> "perlstyle" > > As I understand it, perltidy defaults to perlstyle, so just run it > with no options or rc file. Reminder: we've said during the last IRC monthly meeting that: * new code should be perlstyled * perltidying must not be done in a file mixed with other things * we don't perltidy everything for now, as it would result in git blame returning the perltidy submitter as author of everything. Side question : if someone has an idea to perltidy everything and not loose the blame, he's welcomed. I've checked git blame --help, and it seems we have a friend here : -w Ignore whitespace when comparing the parent?s version and the child?s to find where the lines came from. except it's just for whitespace, and perltidy often update more than space... QUESTION/DISCUSSION = I feel that just tidying new code will result in a mixing of style that will be uncomfortable. OTOH, tidying everything would resuld in git blame being unsusable. It mean both situations are unsatisfying. Does anyone have an idea to improve the situation ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Tue Oct 25 11:10:15 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 11:10:15 +0200 Subject: [Koha-devel] sending patches to koha-patches mailing list ? In-Reply-To: <1318200481.6421.4.camel@zarathud> References: <20111007181730.967C19F0E8@nail.towers.org.uk> <1318200481.6421.4.camel@zarathud> Message-ID: <4EA67CF7.9030600@biblibre.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 10/10/2011 00:48, Robin Sheat a ?crit : > Op vrijdag 07-10-2011 om 19:17 uur [tijdzone +0100], schreef MJ > Ray: >> >> Unless anyone's actually using the signed-off patches on the >> list, I think that's a fine update, until we get a smarter list >> archiver. > > I tend to agree. As no-one has objected and 3 are explicitly for (including me), I've updated the wiki : http://wiki.koha-community.org/w/index.php?title=Sign_off_on_patches&diff=prev&oldid=6223 - -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOpnzyAAoJEK81SonuhyGovg0IAIhWIjV+VsFfzlJ/VPYxJRlX YcDSdIJcWu26NKoRAoQdNx9DK2QC6BVdahg9OuS7oXmrdsd7GzxXKQBh/h6Bm0Br /7/O5aPECabOk8MQICOBaeGhy3zBs5yuIIwf936fwZsQD3+d77Nxvfkou/Xa7zGJ kH2byd0tC8EfZmLUWXDDwSQsv6Fo8eK1w9N/BKaTIXU94zWoy4/XOatRxMYXSsA7 Ideyj8iIvfpZRzqIy3bS7FnsVpyMBASm9k4VDaLrNUse+REWg4A4ITgwv1eHrxcn pMgxHB58FaTZQnmMv3ieqWZRylQT8BOroD+5usjv5xfh/k0ukKmJZkoGxrQ8VfA= =GnYK -----END PGP SIGNATURE----- From paul.poulain at biblibre.com Tue Oct 25 11:17:22 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 11:17:22 +0200 Subject: [Koha-devel] Cleaning up import tables and action log In-Reply-To: <809BE39CD64BFD4EB9036172EBCCFA3134DA7B@S-MAIL-1B.rijksmuseum.intra> References: <809BE39CD64BFD4EB9036172EBCCFA3134DA7B@S-MAIL-1B.rijksmuseum.intra> Message-ID: <4EA67EA2.6000606@biblibre.com> Le 17/10/2011 12:17, Marcel de Rooy a ?crit : > Hi, > > Is anyone of you using code to periodically purge records from > import_records, import_biblios, import_batches and/or action_logs ? > > If so, would it be an idea to include such code into cleanup_database.pl > in misc/cronjobs ? +1 Sounds a very good idea. We have already made a dirty mysql < "truncate xxx" on some setups IIRC. Would be better to have it in cleanup_database. I also agree it should be driven by a parameter, like the number in days to keep/clean. Something like cleanup_database --import 90 --action_logs 180 (90 days for import_* tables and 180 for action logs in this example) And if no parameter are given, either do nothing or remove after a default duration (30 for import ? 90 for action_logs ?) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Tue Oct 25 12:08:24 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 12:08:24 +0200 Subject: [Koha-devel] Bugzilla changes/improvements In-Reply-To: References: <4EA589D1.9050209@biblibre.com> Message-ID: <4EA68A98.5070707@biblibre.com> Le 24/10/2011 18:46, Ian Walls a ?crit : > *Versions: * I think the versions in this list should correspond to the > main branches on the Koha Git repo. So, we'd have 3.2.x, 3.4.x, 3.6.x > and master. A bug report should be connected to the most current > version (if it's a problem in 3.6.x and master, report is as master). It's already the case (see the link i've provided in my initial mail) Report of bugs NEW or ASSIGNED : Rel_3_8 68 master 1031 rel_3_0 97 rel_3_2 132 rel_3_4 327 rel_3_6 129 unspecified 150 Total 1934 => we can discard all "old" versions. > For enhancements, I say we report them against master. Then, when the > feature freeze rolls around, we take everything that has submitted code > so far, and move it 3.8.x. If it makes it, great, if it doesn't, after > release it gets moved back to master. that makes sense. does anyone disagree ? * if you report a bug => report it with the version you're encountering the problem * if you report an enhancement => report it against master, the RM will move to rel_x_x when the patch is pushed. > We can delete old version values in BZ, but there isn't a way to > obsolete them like there are with other field statuses. I think if we > find anything on a version older than 3.0.x, we should probably: > a) verify it's still relevant > b) remove or re-report it in the current context There were only 2, i took care of them. > *Component*: I'm with Owen that more is better than less, here. Each > component controls the default Assignee, and having a more > finely-grained default assignee's list will keep folks from getting > overloaded with bug assignments (in theory). OK, i'm convinced. But we still could discard a few (about & importedbugs that have no entries, and bugs.koha-community.org & translate/koha-community.org. > The universal problem here being, of course, that while folks can be > ASSIGNED a bug, we can never guarantee they'll DO anything about it. > We're all free agents, and cannot enforce any sort of assignment or > timetable outside on a community-wide scale. My proposition is : * keep "NEW" by default * when someone want to endorse a bug (ie: and say "i'll do something"), set ASSIGNED. So by looking at "NEW" bugs, we will know what is orphan and waiting for a volunteer, and looking at old ASSIGNED, we could send a reminder to assignees to ask for confirmation they plan to do something (and if they say "no", we switch back to "NEW") > *Status*: We don't use the regular status field much at all, except to > mark the patch as "resolved". Why don't we put the Patch Status into > the regular ol' Status field? That would have a couple advantages: > > * Easier searching, since it's a default value, not a custom value > * We can enable Workflows between statuses > * We no longer have the dependency on Priority to control the display > of this critical value > > I'll write up more about the potential for the Workflows, and how I hope > the QA team can fit into that, in another post. I'm not sure I understand. > *Priority:* I agree with Owen that this is pretty arbitrary... it may > not be useful to us right now. OK. But the "patch sent" has nothing to do in "priority". The good solution would be to have "patch status" always displayed, with value "--" to say no patch. It's so true that, if you remove the "patch sent" and keep the failed QA (for example), the patch will still appear in the "failed QA" report ! > *Severity:* we should keep, since it highlights issues in red and bold > if they're critical or blocker Agreed. > *Hardware/OS*: should keep, as well, though they are very seldom > useful. A little cluttersome, but a handy categorization for those few > times when it's relevant. If you look at my initial mail and the link with report, you'll see it's never useful ! The more I think of it, the more I feel we need a "browser" field (IE / Firefox / Chrome / Opera / ... / Other), don't care of Hardware. OS maybe relevant for some very specific cases where the server is something strange (like HP-UX or Unix). But we don't have any bug where this information is usefull, so it's only theoric. > *QA Contact:* I'd like to move the 'bugs at lists.koha-community.org > ' from being the Default QA > contact to a Global Watcher. This makes more sense to me, since it's > always supposed to report on things, and if someone changed the QA > contact on a bug report, the list would no longer get notified on update. +1 > I think we should also start talking about making BZ a more central > component in our Patch Submission Procedures. I know I don't use the > patches list-serv now as anymore than a notification means. Everything > I write, test and pass QA is done on Bugzilla (either through Git BZ or > manually). I think that's the way with most of our other developers, as > well +1 (and i've updated the wiki that way a few hours ago) thread to be continued... -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Tue Oct 25 12:36:00 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 12:36:00 +0200 Subject: [Koha-devel] Proposed changes to our Patch Submission and QA workflows In-Reply-To: References: Message-ID: <4EA69110.6010101@biblibre.com> Le 24/10/2011 20:30, Ian Walls a ?crit : > Everyone, Everyalone, (french joke suspected ;-) ) > In an effort to make patch submission and quality assurance easier on > everyone for this next release cycle, I've got some proposals to run by > you all. > > 1. In Bugzilla, move the Koha Bugs List from being the Default QA > Contact to a Global Watcher. This has two advantages: > 1. It frees up the QA Contact field for use by the QA Team > 2. It guarantees that the Bugs List always gets included on the > changes; with the current set up, someone could in theory remove the > Bugs List as QA contact, preventing the list from getting updates. +1 > 2. To reduce email traffic, I propose we stop sending SIGNED OFF > patches to the patches list. We've got Bugzilla lists (which can be > connected to RSS and daily croned emails) which will inform the QA team > on what patches are ready for QA. I did not use the patches list much > this last release cycle to direct my QA work; it was all based of the > Bugzilla statuses +1 (and already decided I think. At least i've updated the wiki that way 2 hours ago !) > 2a. Ideally, I'd like to set up Bugzilla to automatically send the > patches to the listserv for us, or to be able to accept patches sent to > the listserv as attachments. This is going to take some custom coding, > so it's probably not practical for right now. +1 (and same comment : it would be great, but I don't know how to do it for instance) > 3. Now that I'm not the only QA person for the release cycle, I'd like > to formalize our rules about making sure that any submitted patch > doesn't get processed solely by one company. I felt uncomfortable every > time I passed a patch both written and signed off by ByWater teammates, > because while I was sure it was good code, I knew I had a bias (often > times, the code was fixing an issue one of our partners had reported). > My strategy for 3.6 was to acknowledge the bias, and ask if anyone had > any objections. With 3.8, I can pass anything that I write, or that is > written/signed-off by ByWater alone, to Marcel or Jonathan for QA testing. > > Here're the rules I'd like to see in place: > > 1. A patch may not be written and signed off by the same person > (existing rule) OK > 2. The QA team consists of the Release Manager, the Quality Assurance > Manager, and the Quality Assurance Assistants. This team has the > right to move a patch through QA. OK > 3. The QAM delegates the QA work between himself and the QAAs, in > accordance with the rules. OK, but how will you 3 decide who-QA-what ? module by module ? 1st who shoot ? regular meeting to assign QA ? other ? > 4. A patch may not be written and QA'ed by the same person +1, no doubt > 5. A patch may not be written, signed off and QA'ed by any group of > people in the same institution You mean the 3 (writter-signoffer-QAer) can't be from the same institution ? So 2 can be OK ? I agree then. > 6. A patch MAY be signed off and QA'ed by the same member of the QA > team, but the RM may challenge this if he feels the patch needs more > testing. Rule 5 still applies in this case. +1 And it's not only a matter of "sign-off & QA by the same member". for major patches, I may/will request more testing than just 1 sign-off. in a few cases, Chris asked for more testing (when it was MARC sensible, for example), I'll continue that way (and maybe be harder than him) it may be worth adding a line about that. > Comments? Ideas? Counter-proposals? A few comments: * for trivial patches (like template changes, comment/doc), I wouldn't object to have a short circuit (just 1 of QA/sign-off for example) * I'm OK to be a member of the QA team (as RM, see #2). And I'll introduce a little change in RM stuff: I may/could push a patch without testing it myself. I'm not sure yet, but I feel that if a patch has been written by Nicole, signed-off by Katrin, QAed by Marcel, in some situations, i will trust them. For now I don't know if this possibility will arise, but it could. My idea here is to have more time to communicate/organize/improve team working/... I'll see and let you know if it happens. * can we say "RM has the final cut" about accepting a patch ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Tue Oct 25 12:40:55 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 12:40:55 +0200 Subject: [Koha-devel] Proposed changes to our Patch Submission and QA workflows In-Reply-To: References: Message-ID: <4EA69237.2000708@biblibre.com> Le 24/10/2011 20:30, Ian Walls a ?crit : > Comments? Ideas? Counter-proposals? ("send" button hit too quickly...) * For developers who have their own publit git server, we could also let them publish their bug in a branch of their repo (and not attach the patch to the bug). Is it compatible with the signoff procedure (not sure). Is it accessible to ppls knowing git only a little (not sure) so it's just an idea I throw. -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From magnus at enger.priv.no Tue Oct 25 14:12:42 2011 From: magnus at enger.priv.no (Magnus Enger) Date: Tue, 25 Oct 2011 14:12:42 +0200 Subject: [Koha-devel] Proposal for Global Bug Squashing Day: 2011-11-04 Message-ID: Dear Community! After colluding with my fellow bug wrangler Katrin I'd like to propose a date for the next GBSD: http://wiki.koha-community.org/wiki/2011-11-04_Global_bug_squashing_day This coincides with the first day of the hackfest at KohaCon11. Maybe we could get a bit of a Google Hangout going, or something? We'll see... Anyway: Be there or be [_]! Best regards, Magnus From christianjcj at gmail.com Tue Oct 25 15:58:02 2011 From: christianjcj at gmail.com (Christian Calle Jahuira) Date: Tue, 25 Oct 2011 09:58:02 -0400 Subject: [Koha-devel] problem in cataloging Message-ID: Hello Friends I write from La Paz Bolivia, install Koha version v3.06 and I have the following problem in cataloging in MARC21: Can't call method "fields" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2261. Can you help please. Thank you. -- Christian Jhonny Calle Jahuira TUTOR ELEARNING - UMSA Consultor Sistemas de Informacion de Bibliotecas de la UMSA Email: christianjcj at gmail.com Cel: 73017301 - 65151595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ian.walls at bywatersolutions.com Tue Oct 25 16:05:17 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Tue, 25 Oct 2011 10:05:17 -0400 Subject: [Koha-devel] problem in cataloging In-Reply-To: References: Message-ID: Christian, This is a problem in your TransformMarcToKoha subroutine; the record you're passing is corrupted or invalid somehow. How are you coming to this error? What page is coming up on? This will help us narrow down which script is calling the subroutine, and with what parameters. -Ian 2011/10/25 Christian Calle Jahuira > Hello Friends > > I write from La Paz Bolivia, install Koha version v3.06 and I have the > following problem in cataloging in MARC21: > > > Can't call method "fields" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2261. > > > > Can you help please. > > Thank you. > > -- > Christian Jhonny Calle Jahuira > TUTOR ELEARNING - UMSA > Consultor Sistemas de Informacion de Bibliotecas de la UMSA > Email: christianjcj at gmail.com > Cel: 73017301 - 65151595 > > > _______________________________________________ > Koha-devel mailing list > Koha-devel at 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/ > -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From christianjcj at gmail.com Tue Oct 25 16:16:49 2011 From: christianjcj at gmail.com (Christian Calle Jahuira) Date: Tue, 25 Oct 2011 10:16:49 -0400 Subject: [Koha-devel] problem in cataloging In-Reply-To: References: Message-ID: Thanks for the help Install for cataloging in MARC21 format and I'm using cataloging sheet that comes by default (Default) in KOHA 3.06. thanks 2011/10/25 Ian Walls > Christian, > > > This is a problem in your TransformMarcToKoha subroutine; the record you're > passing is corrupted or invalid somehow. How are you coming to this error? > What page is coming up on? This will help us narrow down which script is > calling the subroutine, and with what parameters. > > > -Ian > > 2011/10/25 Christian Calle Jahuira > >> Hello Friends >> >> I write from La Paz Bolivia, install Koha version v3.06 and I have the >> following problem in cataloging in MARC21: >> >> >> Can't call method "fields" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2261. >> >> >> >> Can you help please. >> >> Thank you. >> >> -- >> Christian Jhonny Calle Jahuira >> TUTOR ELEARNING - UMSA >> Consultor Sistemas de Informacion de Bibliotecas de la UMSA >> Email: christianjcj at gmail.com >> Cel: 73017301 - 65151595 >> >> >> _______________________________________________ >> Koha-devel mailing list >> Koha-devel at 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/ >> > > > > -- > Ian Walls > Lead Development Specialist > ByWater Solutions > Phone # (888) 900-8944 > http://bywatersolutions.com > ian.walls at bywatersolutions.com > Twitter: @sekjal > -- Christian Jhonny Calle Jahuira TUTOR ELEARNING - UMSA Consultor Sistemas de Informacion de Bibliotecas de la UMSA Email: christianjcj at gmail.com Cel: 73017301 - 65151595 -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Tue Oct 25 16:31:44 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 16:31:44 +0200 Subject: [Koha-devel] another suggestion for bugzilla Message-ID: <4EA6C850.30106@biblibre.com> Hello, I have an idea I submit here, let's see if it's a good one. What about ordering patch status by adding a number in front of each : 1- needs signoff 2- signed-off 2b- does not apply 3- passed QA 3b- failed QA 4- patch pushed I'm always searching "where is the value I want to set" ... -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Tue Oct 25 16:38:17 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 16:38:17 +0200 Subject: [Koha-devel] another suggestion for bugzilla In-Reply-To: <4EA6C850.30106@biblibre.com> References: <4EA6C850.30106@biblibre.com> Message-ID: <4EA6C9D9.5010303@biblibre.com> Le 25/10/2011 16:31, Paul Poulain a ?crit : > Hello, > > I have an idea I submit here, let's see if it's a good one. > > What about ordering patch status by adding a number in front of each : > 1- needs signoff > 2- signed-off > 2b- does not apply > 3- passed QA > 3b- failed QA > 4- patch pushed Hey... there's better than this (bugzilla is great...) the "sortkey" column let us define the order without changing the name. So I propose : Needs signoff Signed-off Does not apply Passed QA Failed QA Patch pushed Agreed ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From tajoli at cilea.it Tue Oct 25 16:45:55 2011 From: tajoli at cilea.it (Zeno Tajoli) Date: Tue, 25 Oct 2011 16:45:55 +0200 Subject: [Koha-devel] another suggestion for bugzilla In-Reply-To: <4EA6C9D9.5010303@biblibre.com> References: <4EA6C850.30106@biblibre.com> <4EA6C9D9.5010303@biblibre.com> Message-ID: <4EA6CBA3.8010306@cilea.it> Hi, Il 25/10/2011 16:38, Paul Poulain ha scritto: > Hey... there's better than this (bugzilla is great...) the "sortkey" > column let us define the order without changing the name. > So I propose : > Needs signoff > Signed-off > Does not apply > Passed QA > Failed QA > Patch pushed > > Agreed ? > for me +1 -- Dott. Zeno Tajoli tajoliAT_SPAM_no_prendiATcilea.it fax +39 02 2135520 CILEA - Consorzio Interuniversitario http://www.cilea.it/disclaimer From mjr at phonecoop.coop Tue Oct 25 16:49:11 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Tue, 25 Oct 2011 15:49:11 +0100 (BST) Subject: [Koha-devel] Proposal for Global Bug Squashing Day: 2011-11-04 In-Reply-To: Message-ID: <20111025144911.50D529F0E8@nail.towers.org.uk> Magnus Enger > After colluding with my fellow bug wrangler Katrin I'd like to propose > a date for the next GBSD: > http://wiki.koha-community.org/wiki/2011-11-04_Global_bug_squashing_day I'll probably only be available early and late that day - I think the early overlaps with the hackfest, but maybe everyone will be gone by late? > This coincides with the first day of the hackfest at KohaCon11. Maybe > we could get a bit of a Google Hangout going, or something? We'll > see... Please please please could we use something more open than Google? Has the IRC been working well so far? Are you after other features which the current tools don't have? > Anyway: Be there or be [_]! [_] is another mailing list I'm on! Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. Webmaster, Debian Developer, Past Koha RM, statistician, former lecturer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for various work through http://www.software.coop/ From paul.poulain at biblibre.com Tue Oct 25 17:09:40 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 17:09:40 +0200 Subject: [Koha-devel] Bugzilla changes/improvements In-Reply-To: References: <4EA589D1.9050209@biblibre.com> Message-ID: <4EA6D134.5040108@biblibre.com> Le 24/10/2011 18:20, Owen Leonard a ?crit : > Oh, and my vote for the most urgently-needed change to Bugzilla? > > Please change "Rel_3_8" to "rel_3_8" like all the other "rel_*_*" > entries, it's driving me crazy!! (Thanks to chris that gave me access) It's done. I also have moved all rel_3_8 bugs : * to master, for ENH * to rel_3_6 for the 4 bugs that have been reported against rel_3_8 HTH -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From ian.walls at bywatersolutions.com Tue Oct 25 17:17:42 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Tue, 25 Oct 2011 11:17:42 -0400 Subject: [Koha-devel] Patch status workflow (for Bugzilla) Message-ID: Community, As I'd mentioned in a previous thread, I think we should consider removing the custom attribute "patch status" from Bugzilla, and keeping track of this information in the regular Status attribute. This has several advantages: - Easier searching, since it's a default value, not a custom value - We can enable Workflows between Statuses - We no longer have the dependency on Priority to control the display of this critical value The Workflows allow us to specify how tickets are allowed to change status, from which to which. Here's an example workflow: - NEW (default for all incoming tickets) - ASSIGNED (to the developer working on it) - NEEDS_SIGNOFF (once a patch has been submitted) - SIGNED_OFF (after signoff) - PASSED_QA (once QA'ed successfully) - PATCH_PUSHED - RESOLVED For a patch that fails testing, it would look more like this: - NEW - ASSIGNED - NEEDS_SIGNOFF - FAILED QA (some obvious problem found by tester) - NEEDS_SIGNOFF (again, now that the problem is fixed - SIGNED OFF - FAILED QA (less obvious problem) - NEEDS_SIGNOFF - SIGNED OFF - PASSED QA - PATCH_PUSHED - RESOLVED Workflows could prevent jumping a status straight from ASSIGNED to PASSED QA, for example; that status could only be reached from SIGNED OFF. All the changes to these statuses are recorded in the bug reports history, so we have a record of the life cycle. I think this is what Status was initially designed to do, so we just need to leverage it. -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjr at phonecoop.coop Tue Oct 25 17:21:57 2011 From: mjr at phonecoop.coop (MJ Ray) Date: Tue, 25 Oct 2011 16:21:57 +0100 (BST) Subject: [Koha-devel] another suggestion for bugzilla In-Reply-To: <4EA6C9D9.5010303@biblibre.com> Message-ID: <20111025152157.D7CC69F0E8@nail.towers.org.uk> Paul Poulain wrote: [...] > Signed-off I think that one should not have a hyphen, but I can't really explain it. Just a small note: whatever values are picked may need to be typed in a future enhanced git bz. Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha From paul.poulain at biblibre.com Tue Oct 25 17:33:57 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 17:33:57 +0200 Subject: [Koha-devel] Patch status workflow (for Bugzilla) In-Reply-To: References: Message-ID: <4EA6D6E5.4010900@biblibre.com> Le 25/10/2011 17:17, Ian Walls a ?crit : > Community, > Workflows could prevent jumping a status straight from ASSIGNED to > PASSED QA, for example; that status could only be reached from SIGNED > OFF. All the changes to these statuses are recorded in the bug reports > history, so we have a record of the life cycle. > > I think this is what Status was initially designed to do, so we just > need to leverage it. +1 ! Note we must be able to reach RESOLVED from anywhere (in case it's wontfix / duplicate / ... ) In my previous mail, I suggested to have a short circuit for trivial patches. Is it incompatible with preventing jumping from assigned to passed QA ? in your idea would you prevent anyone oustide from QA team to move to "passed QA" or "failed QA" ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Tue Oct 25 17:35:02 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 17:35:02 +0200 Subject: [Koha-devel] another suggestion for bugzilla In-Reply-To: <20111025152157.D7CC69F0E8@nail.towers.org.uk> References: <20111025152157.D7CC69F0E8@nail.towers.org.uk> Message-ID: <4EA6D726.1030907@biblibre.com> Le 25/10/2011 17:21, MJ Ray a ?crit : > Paul Poulain wrote: [...] >> Signed-off > > I think that one should not have a hyphen, but I can't really explain it. > > Just a small note: whatever values are picked may need to be typed in > a future enhanced git bz. I don't want to change values, i just want to change the order they appear ! and as Ian is doing another proposal that sounds fine to me, it may be useless quickly ;-) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Tue Oct 25 17:36:58 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 17:36:58 +0200 Subject: [Koha-devel] Patch status workflow (for Bugzilla) In-Reply-To: References: Message-ID: <4EA6D79A.7040206@biblibre.com> Le 25/10/2011 17:17, Ian Walls a ?crit : > Community, > > > As I'd mentioned in a previous thread, I think we should consider > removing the custom attribute "patch status" from Bugzilla, and keeping > track of this information in the regular Status attribute. This has > several advantages: > > * Easier searching, since it's a default value, not a custom value > * We can enable Workflows between Statuses > * We no longer have the dependency on Priority to control the display > of this critical value > > The Workflows allow us to specify how tickets are allowed to change > status, from which to which. Here's an example workflow: > > * NEW (default for all incoming tickets) > * ASSIGNED (to the developer working on it) > * NEEDS_SIGNOFF (once a patch has been submitted) > * SIGNED_OFF (after signoff) > * PASSED_QA (once QA'ed successfully) > * PATCH_PUSHED > * RESOLVED other potential problem : when moving all existing bugs/patches to those new status, we will set the "last modification date" to "today" right ? can't it be the source of some glitch/pain/problem/surprise/misunderstanding ? (just asking) -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From paul.poulain at biblibre.com Tue Oct 25 17:44:54 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Tue, 25 Oct 2011 17:44:54 +0200 Subject: [Koha-devel] Bugzilla changes/improvements In-Reply-To: References: <4EA589D1.9050209@biblibre.com> Message-ID: <4EA6D976.6030506@biblibre.com> Le 24/10/2011 18:46, Ian Walls a ?crit : > Everyone, > *Versions: * I think the versions in this list should correspond to the > main branches on the Koha Git repo. So, we'd have 3.2.x, 3.4.x, 3.6.x > and master. A bug report should be connected to the most current > version (if it's a problem in 3.6.x and master, report is as master). I've checked for old versions = as there are bugs attached to most of them (sometimes just 1), we can't drop the version. So, I propose = * create rel_1_2 and rel_2_0 versions * move all 1.2.x and 2.0.x bugs to those "generic versions" * move all 2.2.x bugs to rel_2_2 (rel_2_2 already exist) * move all dev_week bugs to rel_3_0 (dev_week had been created during the 1st ever hackfest, in Marseille, Kohacon06, it was before 3.0, the work to add zebra to koha) * drop all 1.2, 2.0, 2.x, and dev_week versions 2nd suggestion : have the old versions named xrel_1_2 (same for 2_0, 2_2, 3_0) to have them at the end of all lists -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From robin at catalyst.net.nz Wed Oct 26 00:31:58 2011 From: robin at catalyst.net.nz (Robin Sheat) Date: Wed, 26 Oct 2011 11:31:58 +1300 Subject: [Koha-devel] Koha uninstalled by Debian Linux "update" In-Reply-To: <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE97@SM-FLOR-VXMB06A.wdw.disney.com> References: <3E19441498923443B9DBE2FE1C0E70B60448A87F61@SM-FLOR-VXMB04B.wdw.disney.com> <1319148711.18770.3.camel@zarathud> <667301C2-C408-4C23-A579-0CD2C571BBDE@disney.com> <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE79@SM-FLOR-VXMB06A.wdw.disney.com> <1B81ADAC73500E47B91DF0E0E556C7891EC16AEE97@SM-FLOR-VXMB06A.wdw.disney.com> Message-ID: <1319581918.26925.30.camel@zarathud> Weissman, Brian S. schreef op vr 21-10-2011 om 10:18 [-0400]: > Thanks for the info, but the results appear to be the same without the > index line, minus the GPG error. From tracing the dependencies, it > looks to me like a bogus requirement somewhere along the way. You should see something like this to these commands: $ apt-cache policy libyaz4 libyaz4: Installed: 4.0.11-1 Candidate: 4.0.11-1 Version table: *** 4.0.11-1 0 500 http://debian.catalyst.net.nz/debian/ squeeze/main amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy libgnutls26 libgnutls26: Installed: 2.8.6-1 Candidate: 2.8.6-1 Version table: *** 2.8.6-1 0 500 http://debian.catalyst.net.nz/debian/ squeeze/main amd64 Packages 100 /var/lib/dpkg/status This is from a completely up-to-date debian install, running Koha from packages. -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From robin at catalyst.net.nz Wed Oct 26 00:36:26 2011 From: robin at catalyst.net.nz (Robin Sheat) Date: Wed, 26 Oct 2011 11:36:26 +1300 Subject: [Koha-devel] Perl style point, was: tt style point In-Reply-To: <4EA67567.9030803@biblibre.com> References: <20111024171838.500209F0E8@nail.towers.org.uk> <4EA67567.9030803@biblibre.com> Message-ID: <1319582186.26925.32.camel@zarathud> Paul Poulain schreef op di 25-10-2011 om 10:37 [+0200]: > * perltidying must not be done in a file mixed with other things What does that mean? > I feel that just tidying new code will result in a mixing of style > that > will be uncomfortable. I don't think that's a big deal. As sections get worked on, they'll get tidier. The sections that don't get tidier are the ones that don't get worked on and hence seen so often :) -- Robin Sheat Catalyst IT Ltd. ? +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From cnighswonger at foundations.edu Wed Oct 26 02:26:27 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Tue, 25 Oct 2011 20:26:27 -0400 Subject: [Koha-devel] 3.4.x String Freeze and Road Map Update Message-ID: As of 0016 UTC, the 3.4.x branch is in string freeze. Only patches not affecting strings and critical and blocker bugfixes will be pushed. My plans are to release 3.4.6 on 1 November 2011, and to move all subsequent 3.4.x releases to the first of the month. 3.4.7 will release 1 December 2011, and then I plan to move to a bi-monthly release schedule for the 3.4.x branch as long as there are applicable commits. After the release of 3.4.12 (or if several months pass with no applicable commits submitted) I will enter a motion to EOL the 3.4.x branch at the next nearest monthly IRC meeting. If you have any comments/suggestions/critiques of this road map, feel free to respond to this thread with them. Also, if you see something in master which I have missed or know of a 3.4.x patch in bugzilla missed, please feel free to point it out. I'll be glad to catch it in the next release. Kind Regards, Chris Nighswonger Koha 3.4/3.6 Release Maintainer -------------- next part -------------- An HTML attachment was scrubbed... URL: From magnus at enger.priv.no Wed Oct 26 09:48:26 2011 From: magnus at enger.priv.no (Magnus Enger) Date: Wed, 26 Oct 2011 09:48:26 +0200 Subject: [Koha-devel] Proposal for Global Bug Squashing Day: 2011-11-04 In-Reply-To: <20111025144911.50D529F0E8@nail.towers.org.uk> References: <20111025144911.50D529F0E8@nail.towers.org.uk> Message-ID: On 25 October 2011 16:49, MJ Ray wrote: > Please please please could we use something more open than Google? > Has the IRC been working well so far? ?Are you after other features > which the current tools don't have? Sorry for being unclear about this. Google Hangout is a video-conference-thingamajig, so what I had in mind was establishing an audio-visual link to the lucky people in Thane, just for the fun of it. I don't believe IRC works very well with audio and visuals, yet... ;-) And yes, Google Hangout is a Google service, yes it does require download and installation of a closed plugin-thingy. But on the plus-side, I know several potential GBSD'ers use and it works quite well (even with video from several participants, as opposed to Skype). It was always meant as a fun add-on to the main event and participating is in no way required to be part of the fun that is GBSD. More details here: http://www.google.com/support/plus/bin/topic.py?hl=en-GB&topic=1257349&parent=1698315 I'm very interested in learning about FLOSS alternatives for videoconferencing, though! Best regards, Magnus Enger From paul.poulain at biblibre.com Wed Oct 26 11:31:27 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Wed, 26 Oct 2011 11:31:27 +0200 Subject: [Koha-devel] Perl style point, was: tt style point In-Reply-To: <1319582186.26925.32.camel@zarathud> References: <20111024171838.500209F0E8@nail.towers.org.uk> <4EA67567.9030803@biblibre.com> <1319582186.26925.32.camel@zarathud> Message-ID: <4EA7D36F.10504@biblibre.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Le 26/10/2011 00:36, Robin Sheat a ?crit : > Paul Poulain schreef op di 25-10-2011 om 10:37 [+0200]: >> * perltidying must not be done in a file mixed with other things > > What does that mean? It means the new code must be perltidyied, but old code must not be perltidyed at the same time. ie: your patches must do one thing only This question is worrying me a little (just a little, really) I must say. we will speak of during HackFest I think. - -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOp9NvAAoJEK81SonuhyGoqaYIAKoM+mFRJqAG4Yv2c5UlXoLe GGPZyAaIdYhUkjtm14Af/saJ9sZq8daJNoG3Gbi3umdIEULcZfIUKVRBfjlE5NN3 DEfuqn8pQqhHczE34ClsxSikZlVy7/KaeiJDQsLXd12lpezD5xGCZXya0k8LIpIj Vuh769NQTrv3MOFtsCj6NUpxDC5pdGP7rPayU529Fo4+k6NxyY4CoSxpjDTATBOO x3HXuA65ddpIYS8HxxGai4sNmsQfAlY3CHT0FHdGCmhYSXG0FidumN3dhn1MJs54 0DCJlPHr4reNmN/GtAKPsNnEoRp5lTK0TrvURI6VRjnek3RWzTeVilpTrjrCL1A= =acr2 -----END PGP SIGNATURE----- From mtj at kohaaloha.com Wed Oct 26 15:21:43 2011 From: mtj at kohaaloha.com (Mason James) Date: Wed, 26 Oct 2011 18:51:43 +0530 Subject: [Koha-devel] Kohacon11 Mumbai day trip on 3rd November details In-Reply-To: <4EA512D3.8000001@biblibre.com> References: <4EA512D3.8000001@biblibre.com> Message-ID: <169D04FC-380C-4AA1-9C2B-00A908720274@kohaaloha.com> On 2011-10-24, at 12:55 PM, Paul Poulain wrote: > Le 22/10/2011 08:49, Koustubha Kale a ?crit : >> Please let me know urgently if you would llike to join the trip so that >> we can do the bookings.. > Hi Koustubha, > > You can count/include the 3 from BibLibre sorry about the late reply (have been since traveling since the 22nd) i have two people keen for the trip, from NZ -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 535 bytes Desc: This is a digitally signed message part URL: From cnighswonger at foundations.edu Wed Oct 26 18:54:32 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Wed, 26 Oct 2011 12:54:32 -0400 Subject: [Koha-devel] Patch status workflow (for Bugzilla) In-Reply-To: <4EA6D79A.7040206@biblibre.com> References: <4EA6D79A.7040206@biblibre.com> Message-ID: On Tue, Oct 25, 2011 at 11:36 AM, Paul Poulain wrote: > > The Workflows allow us to specify how tickets are allowed to change > > status, from which to which. Here's an example workflow: > > > > * NEW (default for all incoming tickets) > > * ASSIGNED (to the developer working on it) > > * NEEDS_SIGNOFF (once a patch has been submitted) > > * SIGNED_OFF (after signoff) > > * PASSED_QA (once QA'ed successfully) > > * PATCH_PUSHED > > * RESOLVED > Speaking as a third-term release maintainer (fwiw), I would like to see an additional patch status added to be known as NEEDS BACKPORTING. This will allow for a quick search by the release maintainer to see what people expect to be backported. The simple distinction between enhancement and bug disappears once an enhancement has made its way into master and/or the current stable release and bugs are filed against it, thus making it hard to know just by looking at the git bug-branch or bugzilla nomenclature. Setting the patch status to NEEDS BACKPORTING would greatly ease this job. Kind Regards, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Wed Oct 26 19:01:38 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Wed, 26 Oct 2011 19:01:38 +0200 Subject: [Koha-devel] Patch status workflow (for Bugzilla) In-Reply-To: References: <4EA6D79A.7040206@biblibre.com> Message-ID: <4EA83CF2.8080101@biblibre.com> Le 26/10/2011 18:54, Chris Nighswonger a ?crit : > On Tue, Oct 25, 2011 at 11:36 AM, Paul Poulain > > wrote: > > > The Workflows allow us to specify how tickets are allowed to change > > status, from which to which. Here's an example workflow: > > > > * NEW (default for all incoming tickets) > > * ASSIGNED (to the developer working on it) > > * NEEDS_SIGNOFF (once a patch has been submitted) > > * SIGNED_OFF (after signoff) > > * PASSED_QA (once QA'ed successfully) > > * PATCH_PUSHED > > * RESOLVED > Speaking as a third-term release maintainer (fwiw), I would like to see > an additional patch status added to be known as NEEDS BACKPORTING. I feel it should not be a status but another field. When should we set "backporting" ? after patch pushed ? in which case ? aren't all bugfixes supposed to be backported to stable ? > This > will allow for a quick search by the release maintainer to see what > people expect to be backported. The simple distinction between > enhancement and bug disappears once an enhancement has made its way into > master and/or the current stable release and bugs are filed against it, > thus making it hard to know just by looking at the git bug-branch or > bugzilla nomenclature. Setting the patch status to NEEDS BACKPORTING > would greatly ease this job. ...OK, got it (the answer to my question just below) So I've a proposition : all bugs should be version rel_3_6, all ENH and bugs attached to ENH should be version rel_3_8 version "master" being dedicated to ENH that still haven't made their way to rel_3_8. So you could find all bugs that needs backporting : all patches attached to rel_3_6 ! makes sense ? -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From cnighswonger at foundations.edu Wed Oct 26 20:02:57 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Wed, 26 Oct 2011 14:02:57 -0400 Subject: [Koha-devel] Patch status workflow (for Bugzilla) In-Reply-To: <4EA83CF2.8080101@biblibre.com> References: <4EA6D79A.7040206@biblibre.com> <4EA83CF2.8080101@biblibre.com> Message-ID: On Wed, Oct 26, 2011 at 1:01 PM, Paul Poulain wrote: > ...OK, got it (the answer to my question just below) > So I've a proposition : all bugs should be version rel_3_6, all ENH and > bugs attached to ENH should be version rel_3_8 > version "master" being dedicated to ENH that still haven't made their > way to rel_3_8. > So you could find all bugs that needs backporting : all patches attached > to rel_3_6 ! > So let us say I create an ENH request for an enhancement 'foo.' 1. I open an ENH bug against 'master' for 'foo.' 2. I do development work and attach a patch to the ENH bug. 3. The patch passes through all QA hoops (English-ism suspected). 4. The RM pushes the ENH and moves it to 'rel_3_8'. 5. A bug is discovered and a bug report opened against 'rel_3_8.' 6. Now, let us say I discover bug 'bar' in rel_3_8 and in rel_3_6. 1. I open a bug report against 'rel_3_8' for bug 'bar.' 2. I fix 'bar' and attach a patch to the bug. 3. The fix passes QA. 4. The RM pushes the patch and moves it to 'rel_3_6' if applicable. (But he has to have this knowledge somehow.) That is ok as long as it works out in practice. It would probably be better to have a way for the bug reporter to indicate *all* branches to which the bug applies, but I don't know if this is possible. Perhaps Ian can comment on that. Kind Regards, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From paul.poulain at biblibre.com Thu Oct 27 09:19:37 2011 From: paul.poulain at biblibre.com (Paul Poulain) Date: Thu, 27 Oct 2011 09:19:37 +0200 Subject: [Koha-devel] Patch status workflow (for Bugzilla) In-Reply-To: References: <4EA6D79A.7040206@biblibre.com> <4EA83CF2.8080101@biblibre.com> Message-ID: <4EA90609.7070401@biblibre.com> Le 26/10/2011 20:02, Chris Nighswonger a ?crit : > Now, let us say I discover bug 'bar' in rel_3_8 and in rel_3_6. > > 1. I open a bug report against 'rel_3_8' for bug 'bar.' mmm... I think there are 2 sub-cases here: - library A, that uses Koha 3.6, find the bug and open it in rel_3_6 - hacker B, that uses master, find the bug and open it in master (or in rel_3_8 ? that's where there can be a confusion between master and rel_3_8) > 2. I fix 'bar' and attach a patch to the bug. > 3. The fix passes QA. > 4. The RM pushes the patch and moves it to 'rel_3_6' if applicable. (But > he has to have this knowledge somehow.) right, this point is the problem. And I feel it's not solved by this proposed workflow (not by the "need backporting as well") > That is ok as long as it works out in practice. not sure it will work well then... I think we haven't completly found the "perfect" workflow > It would probably be better to have a way for the bug reporter to > indicate *all* branches to which the bug applies, but I don't know if > this is possible. Perhaps Ian can comment on that. I've investigated bugzilla, and can't find a way to have a multiple version selection. OTH, it's easy to have another field "backport needed", that could be used for that. I don't know if it's a good idea, I just throw it... -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08 From cnighswonger at foundations.edu Thu Oct 27 13:52:22 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Thu, 27 Oct 2011 07:52:22 -0400 Subject: [Koha-devel] Patch status workflow (for Bugzilla) In-Reply-To: <4EA90609.7070401@biblibre.com> References: <4EA6D79A.7040206@biblibre.com> <4EA83CF2.8080101@biblibre.com> <4EA90609.7070401@biblibre.com> Message-ID: On Thu, Oct 27, 2011 at 3:19 AM, Paul Poulain wrote: > Le 26/10/2011 20:02, Chris Nighswonger a ?crit : > That is ok as long as it works out in practice. > not sure it will work well then... I think we haven't completly found > the "perfect" workflow > > > It would probably be better to have a way for the bug reporter to > > indicate *all* branches to which the bug applies, but I don't know if > > this is possible. Perhaps Ian can comment on that. > I've investigated bugzilla, and can't find a way to have a multiple > version selection. > OTH, it's easy to have another field "backport needed", that could be > used for that. I don't know if it's a good idea, I just throw it... > > Actually, I don't have a strong personal preference for the technique of flagging a bug as needing to be backported. I am strongly desirous to see it implemented in some fashion, however. It will reduce the chances of a patch being dropped which should have been backported by simplifying the creation of reports to that effect. If an additional field raises no objections, then I say let us go ahead and implement it. Kind Regards, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From ian.walls at bywatersolutions.com Thu Oct 27 15:39:41 2011 From: ian.walls at bywatersolutions.com (Ian Walls) Date: Thu, 27 Oct 2011 09:39:41 -0400 Subject: [Koha-devel] Patch status workflow (for Bugzilla) In-Reply-To: References: <4EA6D79A.7040206@biblibre.com> <4EA83CF2.8080101@biblibre.com> <4EA90609.7070401@biblibre.com> Message-ID: Chris, So, to summarize, you're looking for a status that can be set to you know which of the Patches Pushed need to be applied to the previous release? There is currently no facility for specifying multiple releases that a bug applies to. We'd have to create a custom field. The difficulty would come with making use of it. For my part, I only test bugs on master, because I only work on master. Verifying the bug in previous releases doubles or triples the work (depending on how many previous releases I'm supporting). That makes filing the bug report much less sustainable a practice, from a workflow point of view. I would think that anything that gets applied to master would be a candidate for inclusion in the stable release branch. It would be the job of the RM to determine a) if the bug applies, b) if the patch applies and c) if it's too big a new feature to include in stable. Given the quantity of code produced in a release cycle, I can see this being a massive job. Would it help to have additional Koha officer(s) responsible for verifying each Patch Pushed bug report is applicable to the stable release, and then flag it one way or the other? This would reduce the Release Maintainer's tasks to just c) above: determining if this is something that should be backported because it's a bug fix (not a new feature). Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls at bywatersolutions.com Twitter: @sekjal -------------- next part -------------- An HTML attachment was scrubbed... URL: From cnighswonger at foundations.edu Thu Oct 27 16:48:34 2011 From: cnighswonger at foundations.edu (Chris Nighswonger) Date: Thu, 27 Oct 2011 10:48:34 -0400 Subject: [Koha-devel] Patch status workflow (for Bugzilla) In-Reply-To: References: <4EA6D79A.7040206@biblibre.com> <4EA83CF2.8080101@biblibre.com> <4EA90609.7070401@biblibre.com> Message-ID: Hi Ian, On Thu, Oct 27, 2011 at 9:39 AM, Ian Walls wrote: > So, to summarize, you're looking for a status that can be set to you know > which of the Patches Pushed need to be applied to the previous release? > > Correct. > There is currently no facility for specifying multiple releases that a bug > applies to. We'd have to create a custom field. The difficulty would come > with making use of it. For my part, I only test bugs on master, because I > only work on master. Verifying the bug in previous releases doubles or > triples the work (depending on how many previous releases I'm supporting). > That makes filing the bug report much less sustainable a practice, from a > workflow point of view. > > The fundamental problem is differentiation between bug fixes for existing features versus bug fixes for enhancements applied either to the current dev cycle or master (they seem the same from my POV). During the 3.6.0 release cycle, we attempted to maintain the distinction between bug fixes and enhancements by this topic branch nominclature: 'new/bug_X' for bug fixes meant to apply to the current dev branch/master and to the current stable branch 'new/enh/bug_Y' for enhancements meant to apply only to the current dev branch/master. As we moved forward and the 'new/enh/bug_Y' branch was merged with the current dev branch/master, folks begin filing bug reports for bugs in 'new/enh/bug_Y.' These patches were, in turn, pushed out as 'new/bug_Z' topic branches. Given that these "new" bugs related to 'new/enh/bug_Y' were practically disassociated with 'new/enh/bug_Y' both by a different topic branch designation and a different, unassociated bug number, it became quite difficult to decide what should or should not be backported. (Other problems were caused by this as well, but those will be resolved if we can arrive at a solution for this one.) > I would think that anything that gets applied to master would be a > candidate for inclusion in the stable release branch. It would be the job > of the RM to determine a) if the bug applies, b) if the patch applies and c) > if it's too big a new feature to include in stable. Given the quantity of > code produced in a release cycle, I can see this being a massive job. > > Perhaps we have not clearly established the job of the RMaint then. You may recall that when I took up the 3.2.x RMaint job, I specified that the burden of ensuring clean application of a given patch to the current stable branch is the job of the submitter rather than the RMaint. This was agreed to by silent consent. [1] I have followed this policy throughout the 3.4.x RMaint cycle as well. Typically if a commit a) is designated as a 'new/bug_X' topic branch *and* b) does not apply cleanly to the current stable branch, I post a request to the submitter to rebase and reformat the patch to apply over the current stable branch *if it should.* This places the burden of determining if the patch should, indeed, be backported on the author. (Which is where it should be IMHO. ie. When I mark a bug as assigned to me, I accept the responsibility of ensuring I fix it in all currently supported releases as well as master. Otherwise, I have not truly fixed the bug.) If this is not what works the best for the majority if the development community, then we need to come up with a work flow which best fits and implement it. Any significant work flow alterations will require more bodies to help with the RMaint process. Based on the response to the call for RMaint volunteers for the 3.6.x branch, I'm guessing we'll have a pretty hard time coming up with the more bodies. ;-) That said, It seems much simpler to me to just add/modify a field in BZ to allow the author of a given bugfix to indicate which branches the fix should apply to. If the fix needs to be reformatted to apply over multiple branches, the author can attach multiple patches to the bug report, indicating which patch applies to which branch. Give the capabilities of GIT, this should not greatly disrupt the developer's work flow. (While I'm wishing... it would really be cool to have a hook which updated the bug with the commit id when it was pushed to whichever branch...) Maybe the entire problem is overblown from my prospective, so I'm certainly open to correction. But with two RMaint cycles under the belt and a staring a third down the throat (Englishism here), I'd love to get this whittled down to size. [1] http://tinyurl.com/3facmhg Kind Regards, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From danielg.koha at gmail.com Fri Oct 28 21:08:45 2011 From: danielg.koha at gmail.com (Daniel Grobani) Date: Fri, 28 Oct 2011 12:08:45 -0700 Subject: [Koha-devel] October newsletter publication delayed Message-ID: Hi, I missed the customary newsletter publication date of the 25th this month due to a bad cold. Although I haven't been able to marshal the energy and attention needed to publish it, I hope to be able to do so before October becomes November. Cheers, Daniel P.S. Happy conferring, you lucky KohaConners! -------------- next part -------------- An HTML attachment was scrubbed... URL: From kmkale at anantcorp.com Sat Oct 29 10:12:16 2011 From: kmkale at anantcorp.com (Koustubha Kale) Date: Sat, 29 Oct 2011 13:42:16 +0530 Subject: [Koha-devel] Kohacon11 : Getting there Message-ID: Hi All, Kohacon11 is here. The venue is at : Vidya Prasarak Mandal's Thane College Campus, Thorle Bajirao Peshwe Sabhagriha, Near CIDCO Bus Stop, Chendani, Thane (west ) Maharashtra, India. Google Maps link : < http://maps.google.com/maps/place?ftid=0x3be7b927cd6912b9:0xcd4b44329d5ed6bb&q=vpm+thane&hl=en&ie=UTF8&ll=19.189836,72.980786&spn=0.000041,0.000043&t=h&z=15&vpsrc=0 > The college campus is 5 minutes walking distance from Thane railway station. Once you are in Thane, you can take an auto-rikshaw to the campus. Just tell the driver you want to go to Thane College near CIDCO. The program start at 9.00am on 31st October 2011. Please find the program and a formal invitation attached. I have included my mobile number in the contact details below. Do not hesitate to call me if you need any assistance. Looking forward to meeting you all there :) Regards, Koustubha Kale Anant Corporation Contact Details : Address : 103, Armaan Residency, R. W Sawant Road, Nr. Golden Dyes Naka, Thane (w), Maharashtra, India, Pin : 400601. TeleFax : +91-22-21720108, +91-22-21720109 Mobile : +919820715876 Website : http://www.anantcorp.com Blog : http://www.anantcorp.com/blog/?author=2 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Koha Invitation.pdf Type: application/pdf Size: 850783 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Koha Programme.pdf Type: application/pdf Size: 1508895 bytes Desc: not available URL: From danielg.koha at gmail.com Mon Oct 31 23:55:14 2011 From: danielg.koha at gmail.com (Daniel Grobani) Date: Mon, 31 Oct 2011 15:55:14 -0700 Subject: [Koha-devel] Official Koha Newsletter : Volume 2, Issue 10: October 2011 Message-ID: [Below is the text of the newsletter. For active links and a more readable format, please visit http://koha-community.org/koha-newsletter-volume-2issue-10-october-2011] Official Koha Newsletter (ISSN 2153-8328) Volume 2, Issue 10: October 2011 Edited by Daniel Grobani, Koha Community Newsletter Editor. Please submit news items to danielg.koha at gmail.com. Table of Contents Koha Developments Koha 3.4.5 Released Koha 3.6.0 Released Enhanced Koha 3.6.x Release Notes Ding Dong The Witch Is Dead, Which Witch? Koha 3.8.0 Release Team Elected A Message from the Koha 3.8.0 Release Manager Koha Community New Koha Libraries Community Gossip Koha in a Norwegian Library School Koha OPAC Web App Past Koha Events Koha 3.6.0 Released During Access2011 Conference October General IRC Meeting Upcoming Koha Events KohaCon11 Global Bug Squashing Day Proposed November General IRC Meeting KohaCon12: Welcome to Edinburgh! Koha Developments Koha 3.4.5 Released by Chris Nighswonger It is with pleasure that I announce the release of Koha 3.4.5. The package can be retrieved from: http://download.koha-community.org/koha-3.04.05.tar.gz You can use the following checksum and signature files to verify the download: http://download.koha-community.org/koha-3.04.05.tar.gz.MD5 http://download.koha-community.org/koha-3.04.05.tar.gz.MD5.asc http://download.koha-community.org/koha-3.04.05.tar.gz.sig Release notes for 3.4.5 are below the fold. Come and get it! Continue reading ?Koha 3.4.5 Available? ? Koha 3.6.0 Released by Chris Cormack It is with great pleasure that I announce the release of Koha 3.6.0. This is major feature release, containing 85 enhancements and 356 bugfixes. A total of 728 patches have been included from 60 developers in this release. A big thanks goes out to all of them, plus all the other people involved in this release. You can download this release at http://download.koha-community.org/koha-3.06.00.000.tar.gz or you can wait a couple of days for the packages to appear at http://debian.koha-community.org. Release notes are available below the fold. Continue reading ?Koha 3.6.0 Released? ? Enhanced Koha 3.6.x Release Notes by Nicole Engard Just like with the release of 3.4, I have edited the release notes for Koha 3.6 to include links to related manual pages and tutorial videos. I hope this helps you find the new features in your Koha installation. For more info, see http://bywatersolutions.com/2011/10/28/koha-3-6-x-release-notes Ding Dong The Witch Is Dead, Which Witch? by Chris Cormack This guy! With the release of Koha 3.6.0 my tenure as Release Manager is over. I?d like to thank everyone who has helped my the last 2 releases happen. I am of course not leaving the community, but I am now freed up to do more coding again. Also, as I am no longer RM I can speak a little more freely about things which is nice also. I am sure Koha 3.8.0 will be a great release, and I hope to get a bunch of my code into it also. The RM is dead! Long live the RM! Koha 3.8.0 Release Team Elected by Chris Cormack During the October General IRC meeting, amongst a lot of other discussion and agenda items, the positions for the 3.8 release of Koha were filled. Congratulations to all those appointed: Release Manager: Paul Poulain, BibLibre, France Release Maintainer: Chris Nighswonger, FBC, USA (Unless someone volunteers before the 3.6.0 release) QA Manager: Ian Walls, ByWater Solutions, USA Assistant QA Managers: Marcel de Rooy, Rijksmuseum, Netherlands; Jonathan Druart, BibLibre, France Translation Manager: Fr?d?ric Demians, Tamil, France Assistant Translation Manager: Katrin Fischer, BSZ, Germany Documentation Manager: Nicole Engard, ByWater Solutions, USA Bug Wranglers: Katrin Fischer, BSZ, Germany; Magnus Enger, Libriotech, Norway; Owen Leonard, ACPL, USA Packaging Manager: Robin Sheat, Catalyst IT, New Zealand Assistant Packaging Manager: Mason James, KohaAloha, New Zealand Bus Driver (AKA meeting chair): Brooke Johnson, USA We are still looking for people to be Module Champions, what this role entails is advocating for a module of Koha. Do you think circulation is important? You could be the Circulation Champion, how about serials? You know you have secretly always wanted to take ownership of a section of Koha you care about, now is your chance! A Message from the Koha 3.8.0 Release Manager by Paul Poulain Koha 3.6.0 has been released, so it?s time to start working on Koha 3.8.0. I?ve been chosen as Release Manager, which is a big responsibility. I?ll continue the good work Chris has done and promote some new ideas or ways of doing things. In the next weeks, I plan to submit a global roadmap that will include short-term as well as long-term goals for Koha, on both functional and technical areas. Stay tuned on the koha-devel mailing list if you?re interested. And don?t hesitate to join us and participate! Koha Community New Koha Libraries Cornish College of the Arts (via ByWater Solutions) Corpus Christi Public Libraries (via ByWater Solutions) Fox Chase Cancer Centers?s Talbot Research Library (via ByWater Solutions) Green Mountain College?s Griswold Library (via ByWater Solutions) Kenya Human Rights Commission Resource Center (via Busara Core Solutions) Service Commun de la Documentation de l?Universit? de Limoges (via BibLibre) Community Gossip Chris Nighswonger has been working on getting the master branch of Koha running on Windows XP. He?s posted his progress to the wiki at http://wiki.koha-community.org/wiki/Koha_3.4. Adrien Saurat has joined BibLibre as Support/Maintenance Manager. Gaetan Boisson has joined BibLibre as Project Lead. Nicole Engard has made her fast add framework even faster. Details are at http://bywatersolutions.com/2011/10/17/faster-fast-add-framework-redux. Kathryn Tyree has joined Catalyst as Koha project manager. Robin Sheat of Catalyst will be giving a talk titled ?Koha: Bringing libraries into the present day? at the OSDC conference in Canberra, Australia, on 16 November. For more info, see http://osdc.com.au/schedule/#kohabringinglibra. And lots of people are doing lots of fun things at KohaCon11! Koha in a Norwegian Library School by Magnus Enger The library program at the Oslo and Akershus University College of Applied Sciences (http://www.hioa.no/eng/) is now offering personal Koha installations to all first and second year students ? a total of about 225 students. Installations will be used during the whole of the education, including for mandatory assignments in cataloging. The installations utilize the Debian packages, and the university college is handling all hosting and installation in-house. Koha OPAC Web App by Stefano Bargioni I?ve created a Koha OPAC for smartphones and tablets. It is located at http://catalogo.pusc.it/mobile/ and can be accessed not only from smartphones but also from desktop PCs using any modern browser. It is a very simple OPAC interface, up to now. Based on jQuery Mobile, it accesses Koha using its SRU server. So it is not an app, nor a set of CSS that adapt Koha web pages to little screens. It is a web app, if I may say so. For more info, contact bargioni at pusc.it. Past Koha Events Koha 3.6.0 Released During Access2011 Conference by Chris Cormack Last Thursday 20th October I gave a talk at Access2011: The Library is Open in Vancouver titled T?tou t?tou: Caring and sharing in a Free and Open source Project. The talk focused on lessons learned by the Koha community that would be of interest to other emerging open source software communities. It was particularly appropriate to the international nature of the Koha community that a kiwi guy could write the release notes, push patches and release Koha 3.6.0 while away in Vancouver. As many of you know Koha 3.6.0 was a major and very satisfying release to be part of. With 85 enhancements and 356 bugfixes Koha 3.6.0 included 728 patches from 60 developers. You can find out who those developers were and what they contributed here. The release notes are published here. One last huge thanks to everyone that contributed to to 3.6.0 and all the best to the release team for 3.8.0! October General IRC Meeting The October general IRC meeting was held on 5 October 2011. For more info, including the agenda and links to the minutes, see http://wiki.koha-community.org/wiki/General_IRC_Meeting,_5_October_2011. Upcoming Koha Events KohaCon11 KohaCon11 is being held 31 October 2011 to 6 November 2011 in Thane, India. The program for KohaCon11 is at http://kohacon11.vpmthane.org/ocs/index.php/k/k11/schedConf/program. For more info, see http://kohacon11.vpmthane.org/ocs/index.php/k/k11. Global Bug Squashing Day Proposed by Magnus Enger Dear Community! After colluding with my fellow bug wrangler Katrin I?d like to propose 04 November as the date of the next GBSD: http://wiki.koha-community.org/wiki/2011-11-04_Global_bug_squashing_day. This coincides with the first day of the hackfest at KohaCon11. Maybe we could get a bit of a Google Hangout going, or something? We?ll see? Anyway: Be there or be [_]! November General IRC Meeting The November general IRC meeting will be held on 16 November 2011. For more info, see http://wiki.koha-community.org/wiki/General_IRC_Meeting,_16_November_2011. KohaCon12: Welcome to Edinburgh! by MJ Ray I?d like to send thanks from software.coop to everyone who voted for Edinburgh in the recent vote. I look forward to welcoming you next summer and we?ll release more details as soon as they are confirmed, as well as asking for feedback on a couple of social event ideas. 2012 is software.coop?s tenth anniversary and also the United Nations International Year of Co-operatives, so it?s a great time for a celebration and collaboration. On that note, I?d also like to thank the people who have sent expressions of interest in helping out with running the event. We?ll ask other co-ops to assist too, but we may well take up some of these offers. Finally, all the best to the KohaCon11 team for the conference that?s about to start. I?m sorry I?m not there, but we?ve already started work on KohaCon12. Have a great time for us and I look forward to hearing much news from India! -------------- next part -------------- An HTML attachment was scrubbed... URL: