Time  Nick            Message
22:29 cait            good night all
22:14 cait            wizzyrea++
22:14 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9375 major, P5 - low, ---, gmcharlt, NEW , Logging in with LDAP creates duplicate users
22:14 wizzyrea        all right, bug 9375
22:05 cait            hehe
22:05 jcamins         Call it crostini and suddenly it's interesting. :)
22:05 jcamins         Crostini!
22:05 cait            boring :)
22:05 cait            well and some toast with things
22:04 cait            plum pie (in the cafe where I tried to learn until they kicked me out)
22:04 cait            hm
22:04 jcamins         cait: what did you eat for dinner?
22:03 cait            jcamins: don't make me hungry :)
21:56 jcamins         "Balsamic, bisque & biscuit"?
21:56 druthb          Dyrcona: to the crickets?   EW.
21:53 jcamins         We're also having leftover balsamic caramelized onion and mushroom and herb crostini.
21:53 jcamins         One of the nice things about working from home.
21:53 Dyrcona         jcamins: You're making me hungry, and it's an hour until I can get home to the crickets......
21:52 wizzyrea        hehe
21:52 jcamins         Or "iPhone Anniversary Bisque & Biscuit," but I think the first is better.
21:52 Dyrcona         :)
21:51 jcamins         I can call dinner the "First Agonalia Bisque & Biscuit."
21:51 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8148 critical, P5 - low, ---, gmcharlt, NEW , ldap authentication should FAIL if ldap contains NEW password, and user types the PREVIOUS password
21:51 wizzyrea        bug 8148 is kind of related
21:50 wizzyrea        well look for an existing one that needs to be bumped.
21:50 jcamins         I'm thinking I might also make some sweet potato biscuits.
21:50 wizzyrea        ok well, I'm going to file this bug then.
21:50 wizzyrea        noice
21:50 jcamins         The rutabaga bisque is cooking now.
21:48 * jcamins       is thinking big huge bad awful bug.
21:45 * wizzyrea      wonders why ldap doesn't look to see if there is already one, and insert it's data into the existing user.
21:45 wizzyrea        that erm... seems not good.
21:45 wizzyrea        but the db doesn't
21:45 wizzyrea        so the interface would enforce unique usernames
21:44 wizzyrea        ha and you can't edit that dupe patron because the interface claims it's username is already used.
21:43 wizzyrea        let's just go with that.
21:43 wizzyrea        very super bad.
21:43 cait            I get you :)
21:43 cait            yeah
21:43 wizzyrea        no that's a double negative.
21:43 cait            heh
21:43 wizzyrea        er
21:43 wizzyrea        that is very not super ungood
21:42 wizzyrea        ew
21:42 cait            the field in the database is not unique
21:42 cait            patron import does do that too :(
21:42 cait            no
21:42 wizzyrea        like ldap or CAS
21:42 wizzyrea        were they using external authentication?
21:42 cait            I ended up in the wrong patron account
21:42 cait            I have seen some weird thing once with doubled up user names
21:42 cait            wizzyrea: there is a bug for username no being forced to be unique
21:41 wizzyrea        but the same login credentials
21:41 wizzyrea        so we had borrowers existing, then when they logged in, they were getting dupes with higher borrowernumbers
21:40 wizzyrea        for example, we migrated a library from sirsi
21:40 wizzyrea        3.8.7
21:39 wizzyrea        one sec for revision
21:39 wizzyrea        this is gonna be.... 3.8
21:39 jcamins         What version are you seeing it in?
21:39 jcamins         That's a bug.
21:39 wizzyrea        yea, that's what I thought
21:39 cait            especially the doubled up user name in the database
21:38 cait            that sounds evil
21:38 wizzyrea        or, this isn't behaviour that we should be expecting.
21:37 wizzyrea        this is a bug, right?
21:37 wizzyrea        does it seem odd that if a native koha user exists with a username and password, if using LDAP, a second, duplicate user will be created with the same username and password when that user logs in (for the first time, it doesn't keep creating duplicates)
20:25 khall           fixed, i also removed the dead deps and I think all the new ones have been added
20:19 khall           and new deps need added
20:19 khall           actually, that's a dead dependency. It needs removed
20:19 jcamins         Why did you use Config::General instead of Config::Simple? I have no preference, just wondering.
20:18 khall           There still a long todo list, I'll fix the merge marker right now
20:18 jcamins         Thanks.
20:18 jcamins         Oh, look, there's a new patch addressing those things.
20:17 jcamins         khall: bad news... I have spotted a few issues: 1) merge marker in sysprefs.sql (easy to fix, for when you upload the next iteration), 2) there doesn't seem to be a way to disable plugins by editing the koha-conf.xml file, 3) there don't appear to be any links to the plugin pages, 4) there should be a detailed test plan.
19:59 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7804 enhancement, P5 - low, ---, kyle.m.hall, In Discussion , Add Koha Plugin System
19:59 * jcamins       awaits the hordes of testers descending on bug 7804...
19:59 jcamins         Karma for anyone tests bug 7804!
19:58 jcamins         Then test it!
19:57 maximep         I can't wait for this plugin system!
19:54 wizzyrea        average is 57km/h
19:54 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7804 enhancement, P5 - low, ---, kyle.m.hall, In Discussion , Add Koha Plugin System
19:54 khall           jcamins and anybody else interested, new Plugin system code is posted on bug 7804 . Be warned, it is not completed, but is completely usable!
19:54 wizzyrea        ooh gust of 87km/h
19:53 wizzyrea        temp is nice tho
19:53 wizzyrea        again, they don't mention the rather forceful winds.
19:53 wizzyrea        hm really
19:52 huginn          wizzyrea: The current temperature in Wellington, New Zealand is 20.0°C (8:00 AM NZDT on January 10, 2013). Conditions: Scattered Clouds. Humidity: 73%. Dew Point: 15.0°C. Pressure: 29.74 in 1007 hPa (Steady).
19:52 wizzyrea        @wunder wellington, nz
19:52 huginn          wizzyrea: Error: No such location could be found.
19:52 wizzyrea        @wunder wgtn
19:51 wizzyrea        is there anyone around who can release it?
19:51 wizzyrea        because I so daftly attached screenshots my message is in moderation
19:51 wizzyrea        oh fooey
19:50 * wizzyrea      does a righteous copy/paste to answer that question
19:45 cait            yours are weirder :)
19:45 jcamins         cait: you do.
19:45 cait            jcamins: and you say I have weird libraries? :)
19:45 wizzyrea        ha that is hilariously the exact same question I got just 3 days ago
19:44 cait            oh
19:44 huginn          cait: The coded form of the mathematical data contained in field 255 (Mathematical Data Area) of the bibliographic record. (Repeatable) [a,b,c,d,e,f,g,h,j,k,m,n,p,r,s,t,x,y,z,2,6,8]
19:44 cait            @marc 034
19:43 wizzyrea        I haven't gotten there yet
19:43 wizzyrea        ha no
19:41 jcamins         But the prescriptive instructions which are actually just descriptive are not very helpful.
19:41 cait            wizzyrea: did you see the email on the list asking about the routing list mails?
19:41 * chris_n       contributes a few mealworm patties to the bug conversation
19:40 jcamins         I figured out what I needed eventually.
19:40 wizzyrea        hm
19:39 jcamins         Wow, I have to say that the specification for field 034 $d-$g is remarkably unhelpful.
19:38 cait            :P
19:38 cait            of the old ones
19:38 cait            oleonard: cleaning out 50 bugs I think
19:38 cait            hi #koha
19:38 jcamins         oleonard: fixing ALL THE THINGS!
19:37 oleonard        I can't remember, what did we volunteer wizzyrea for during the meeting?
19:35 jcamins         wizzyrea: me too, and I've been around for 6 hours. :(
19:34 Dyrcona         Locusts...bet I could farm them without much real work.... ;)
19:34 wizzyrea        hey I just started my day ;)
19:34 tweetbot`       [off] twitter: @kohails: "#kohails  Introduction to the Koha 3.10 Public Catalog http://t.co/4P9WmKJC"
19:34 jcamins         Meanwhile #evergreen is actually doing serious work.
19:34 wizzyrea        ...they don't have cloven hooves, I guess that's cool
19:33 jcamins         Crickets are not due to the height of their legs compared to their wingspan or something like that.
19:33 druthb          grossgrossgross...
19:33 jcamins         Better to farm locusts... they're kosher.
19:33 druthb          eeeewwwww
19:32 Dyrcona         That's it! I'll have a cricket farm.... Cricket! It's the new chicken!
19:32 jcamins         Still, despite having resigned twice since I started lurking on #evergreen.
19:32 * Dyrcona       is the "Chief Bug Wrangler" for Evergreen, btw.
19:32 Dyrcona         Weta bugs....
19:31 oleonard        Presumably sometimes both
19:31 jcamins         You can alternate your time between crushing grapes and crushing bugs.
19:30 Dyrcona         ^might^mighty
19:29 jcamins         lol
19:29 Dyrcona         jcamins: That little vineyard in Marlborough is looking might attractive right now.
19:26 tweetbot`       [off] twitter: @ByWaterSolution: "Introduction to the Koha 3.10 Public Catalog http://t.co/vIcNBoya #kohails"
18:56 Shane-S         removed that item and it worked
18:56 Shane-S         chris_n: found it the webinterface have diamond with a question mark
18:51 chris_n         iirc you can export each item in a batch by itself; time-consuming if you have large batches though
18:50 Shane-S         okay, well it was a batch so I will have to see what is in it
18:49 chris_n         in which case the pdf based tools are probably useless for you
18:49 chris_n         unless you have lots of diacriticals and non-latin chars
18:48 chris_n         in either case, if you can locate and isolate the offending record, you should be able to print
18:48 chris_n         it may also be a bad marc record
18:48 chris_n         it looks like you are running afoul of the unicode problem in the pdf stuff
18:47 Shane-S         sorry ti took me so long got interrupted
18:47 Shane-S         chris_n: Wide character in compress at /usr/share/perl5/PDF/Reuse.pm line 819
18:42 jcamins         And I was wrong, because there are five entries for 10135, and only one of them is missing a barcode.
18:42 jcamins         Agreed, but I have no idea why there's an error message at all.
18:41 rambutan        but in any event that error message should be more informative
18:41 jcamins         That looks really weird.
18:41 jcamins         Maybe those are items you have deaccessioned?
18:41 rambutan        http://imageshack.us/photo/my-images/829/circ2.png/
18:40 rambutan        https://imageshack.us/photo/my-images/213/circ1.png/
18:36 rambutan        ah, correct
18:34 jcamins         Those should be item/biblio numbers.
18:34 jcamins         rambutan: I don't recall hearing a bug like that.
18:34 rambutan        selecting an item with a transaction number (is that what it is?) does work as expected
18:33 rambutan        I don't see this listed as a known bug, am I missing it?
18:33 rambutan        I get "Software error: Can't call method "field" on an undefined value at /home/koha/kohaclone/C4/Items.pm line 1396."
18:33 rambutan        Koha In the log viewer, when I click on an Item under the info column which has no associated transaction number...
18:29 chris_n         Shane-S: open the corrupt pdf in a text editor and paste the error
18:23 Shane-S         Anything I can try or check, it generates the PDF but adobe and Sumatra PDF readers error on the file. I can upload the file somewhere if need be
18:22 Shane-S         I am having issue with the label maker for barcodes, the PDFs are coming up invalid. Just started happening today, I restarted the server and still have this issue Koha Version:
18:02 * oleonard      reminds sekjal too late to B his OB
18:00 sekjal          gtg; NISO webinar
17:42 jatara          Yep...enhancement request. Will send to our support company.
17:37 * oleonard      has no problem with enhancement requests
17:37 oleonard        It certainly could be.
17:36 * slef          runs
17:36 slef            oleonard: so it would be an enhancement request?
17:20 jatara          Thanks so much.
17:19 reiveune        bye
17:15 oleonard        sorry, I don't think it's possible without changing the way Koha works.
17:12 jatara          I can understand that. I just want to be able to retrieve a result set of no more than 50-60 and have them display on the same page.
17:09 oleonard        The reports system is designed to prevent the possibility of returning a result set so large that it would crash your browser
17:08 jatara          It works fine, but our librarians prefer to be able to print the whole thing out without having to go through that extra step.
17:07 oleonard        jatara: The CSV download option won't work for you?
17:05 jatara          don't want to page through the rows..just have them all on one screen
17:05 jatara          Yes, for printing
17:05 oleonard        jatara: For printing?
17:04 oleonard        jatara: I don't think so
17:01 jatara          Is there a way I can increase the number of results (rows) from a report on my screen?
17:01 sekjal          write a mobile app that can listen to pings coming from the Arduino, so you can guide a person to a book...
16:59 sekjal          I'm sure there could be something neat done with Arduinos in the stacks... perhaps emitting some kind of homing signal?
16:58 rambutan        that might look cool?
16:57 slef            a koru-shaped Pi case?
16:57 sekjal          rambutan:  yes!
16:57 sekjal          though given the amount of work my friend has to do to get his Replicator 2 to run, we may need a dedicated staff member
16:57 rambutan        you could print a Pi case, and run Koha on it
16:56 jcamins         sekjal: ... something that runs Koha? :)
16:56 rambutan        we're trying to get into the biz
16:56 sekjal          my library may also be considering one
16:56 sekjal          rambutan:  a friend has purchased one, so I'm pondering what to commission
16:56 rambutan        sekjal: doing anything with 3D printers (open hardware)?
16:55 rambutan        Happy Birthday to the Three!
16:53 jcamins         lol
16:52 Dyrcona         sekjal: Just tell them jcamins story, but say Ruby on Rails caused it.
16:51 libsysguy       damn
16:51 jcamins         Yeah, but the bathtub problems predated our insurance policy.
16:50 jcamins         Stupid laminate that traps moisture underneath it.
16:50 jcamins         The insurance adjuster came, looked around and said "right, the entire floor has got to go."
16:50 * sekjal        is not a fan
16:50 sekjal          slef: if only I could scare folks away from Ruby on Rails entirely....
16:50 libsysguy       and didn't the bathtub get ruined too ;)
16:50 jcamins         Our upstairs neighbor flooded our kitchen Thursday night.
16:50 libsysguy       what are you putting in?
16:50 jcamins         Yeah.
16:50 libsysguy       really?
16:49 jcamins         Looks like I may be getting a new kitchen floor soon.
16:49 jcamins         lol
16:49 libsysguy       I'll take it over any wrinkle cream
16:49 paul_p          sophie (our support team manager) told me this morning "it's a prevention measure Paul, don't worry" :D
16:49 libsysguy       Anna got me a new kitchen sink
16:49 gmcharlt        paul_p_wife++ ;)
16:49 slef            sekjal has been scaring rails users ;)
16:49 libsysguy       HA
16:49 bag             HA
16:48 paul_p          a (real life joke) = yesterday, my wife bought for me a ... anti-aging cream. Nice birthday gift :\ (I'm 45 today)
16:48 nengard         hehe
16:48 jcamins         Yes, I suggest that it be International QAing Day!
16:48 libsysguy       I think on you're cake day all your patches pass!!
16:48 paul_p          happy birthday libsysguy
16:47 bag             heh
16:47 sekjal          I propose we make today some kind of official Koha-liday
16:47 paul_p          libsysguy = it's your birthday to ? wow, should we ask this requirement to be a QA team member ? :D
16:47 libsysguy       happy bday paul_p and bag
16:47 bag             hey there is paul_p - happy birthday to you!
16:47 paul_p          bag = happy birthday !
16:47 * libsysguy     doesn't like this cake sharing idea oleonard
16:47 bag             thanks oleonard and gmcharlt
16:47 gmcharlt        (while the cats the away, the mice will play - I've fixed the needs signoff link on the dashboard)
16:46 paul_p          sekjal  thanks
16:46 sekjal          bag:  doing alright. starting to get into some open hardware projects
16:46 gmcharlt        happy birthday!
16:46 gmcharlt        wow
16:46 bag             how you been sekjal ?
16:46 oleonard        Happy birthday to the three of you. We got you each one third of a cake!
16:45 bag             THANKS!
16:45 bag             hey sekjal
16:45 libsysguy       and thank you
16:45 libsysguy       indeed
16:45 sekjal          quite the auspicious day:  happy birthday paul_p, bag and libsysguy!
16:42 vfernandes      I can't see no more CSS :D
16:42 jatara          When I create a new report, is there a way to increase the number of rows displayed on the screen. I want to be able to see all my results on one page
16:42 gmcharlt        vfernandes:  looks very nice indeed
16:42 kf              yes, looks nice .)
16:42 sekjal          hi, jcamins
16:42 jcamins         Hi, sekjal.
16:42 jcamins         vfernandes: nice!
16:42 oleonard        Looks great vfernandes
16:41 vfernandes      people what you think about this new OPAC design? http://keep.dyndns.biz:8054
16:30 gmcharlt        kitten kebabs?  scrollback must be *very* interesting
16:11 slef            chris_n: kitten kebabs are irregular words
15:51 kf              but it might not be the website itself, but something with networks
15:51 kf              nengard: a bit
15:51 kf              nengard: I will try :)
15:50 nengard         :)
15:50 nengard         Loving it
15:50 nengard         yeah it does to me too!
15:50 oleonard        Seems speedy to me nengard, FWIW
15:48 nengard         kf you said bywater site was slow for you before - is it better now that we upgraded?
15:42 oleonard        You're welcome
15:42 jatara          Thank you!
15:41 jatara          That worked! I cut and pasted the full URL, not realizing that the software was going to truncate my entry. The truncating process went a little too far, but everything works now.
15:39 oleonard        (click the "html" button)
15:38 oleonard        Are you looking at the rich text version? Perhaps check the source in the news editor?
15:38 jcamins         Sounds like a relative rather than absolute URL.
15:38 jatara          and if i go to the news interface, it works fine (link #1)
15:38 jatara          how is that possible? I used the news interface to add this link.
15:37 jatara          what i see on the news item: http://koha-staff.pisd.edu:8080/cgi-bin/reports/guided_reports.pl?reports=1690&phase=Run%20this%20report
15:37 jatara          what it SHOULD be: http://koha-staff.pisd.edu:8080/cgi-bin/koha/reports/guided_reports.pl?reports=1690&phase=Run%20this%20report
15:36 jatara          ohhh...that's interesting
15:33 oleonard        How do the links differ in each place? You can try copying the link and pasting them to compare (since the 404 error rewrites the location)
15:32 jatara          fully qualified
15:32 oleonard        jatara: Is it a root-relative or fully-qualified URL?
15:32 oleonard        jatara: Sounds like a problem with the path in the link
15:31 jatara          I'm trying to add links to reports to our news section. Problem is, the links work fine when I'm viewing the table of news items in the tools section, but they return 404 errors when you click on the links directly from the news item.
15:30 chris_n         I hate irregular words
15:30 jcamins         jatara: go ahead and ask your question. If someone can help, they will.
15:30 jcamins         "whose"
15:29 * chris_n       wonders briefly about the plural possessive of who
15:29 jatara          Hi, all. Have a question if you have a minute.
15:29 chris_n         since the catalogers within who's reach I dwell seem relatively content atm, it just remained at the bottom of my filo todo buffer
15:25 kf              I wasn't talking about labels
15:25 chris_n         particularly title fields
15:25 kf              oh
15:25 chris_n         labels text
15:25 chris_n         at this point it will take time+money to fix (with emphasis on time)
15:25 kf              text wrapping of what?
15:24 chris_n         but it works in "most" cases, as I said
15:24 chris_n         text wrapping depends on lots of parameters which the current code does not account for
15:24 kf              not sure where to sort in text wrapping
15:23 chris_n         in any case, that's the long and short of it
15:23 kf              maybe
15:23 chris_n         or did I splice together two unrelated threads of conversation? :-P
15:23 oleonard        chris_n: That was in regards to custom translations
15:23 chris_n         <kf> oleonard: and especially in that place, every library wants their own text
15:23 chris_n         <kf> oleonard: it's doable, but you will have to think about the change every time you update koha
15:23 chris_n         <oleonard> chris_n doesn't seem to be interested in working on that anymore
15:22 kf              huh?
15:20 chris_n         what I wrote works in "most" cases, but can get messy
15:19 chris_n         oleonard: kf is correct, text wrapping is a moving target
15:05 jcamins         This is why newer patches are required to have detailed commit messages.
15:04 nengard         okay
15:04 nengard         oh ?. well that's confusing
15:04 jcamins         No it doesn't. That's the name of the routine that retrieves MARC notes.
15:04 nengard         in the commit body it does
15:03 jcamins         It doesn't list the preference name.
15:03 nengard         just fyi for the release notes
15:03 nengard         jcamins the commit message on the bug has the wrong preference name
15:03 nengard         oh okay
15:02 jcamins         I should remove it from the list.
15:02 jcamins         File::Find::Rule isn't actually required anymore.
15:02 nengard         NotesBlacklist
15:02 nengard         oh look the pref name is wrong
15:01 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9162 enhancement, P1 - high, ---, vfernandes, Pushed to Master , Add a system preference to set which notes fields appears on title notes/description separator
15:01 nengard         bug 9162
15:01 nengard         hi all, i'm trying to find the new GetMarcNotes preference but I don't see it ? I didn't have the new File::Find::Rule Perl module (I must have installed it on my other computer not this one) until now ? was that needed to get Koha to prompt me for a db upgrade?
14:42 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8977 normal, P5 - low, ---, gmcharlt, Pushed to Master , printoverdues.sh call an uninitialized variable
14:42 jenkins_koha    stephane.delaune: Bug 8977:replace unitialized directory var in printoverdues
14:42 jenkins_koha    Project Koha_master build #1005: SUCCESS in 1 hr 4 min: http://jenkins.koha-community.org/job/Koha_master/1005/
14:39 kf              forget it, I am tired today
14:39 oleonard        kf: holds expirations?
14:39 kf              oleonard: hm not sure, but hasn't that seen some changes since?
14:38 slef            updating the bug
14:38 slef            so the new label creator was summer 2009
14:38 slef            9755514
14:37 slef            e751044 f4d4622 6860310
14:36 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3474 enhancement, P5 - low, ---, gmcharlt, NEW , Handling of and report for expired or cancelled holds, display expiration dates
14:36 oleonard        Maybe jwagner can provide a rebased patch for Bug 3474
14:34 kf              oleonard: and especially in that place, every library wants their own text
14:34 kf              oleonard: it's doable, but you will have to think about the change every time you update koha
14:34 oleonard        chris_n doesn't seem to be interested in working on that anymore
14:34 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2499 enhancement, P5 - low, ---, cnighswonger, NEW , Improvement on text wrapping algorithm needed
14:34 slef            (I'm looking at bug 2499)
14:34 slef            has the label printer been changed since 2008-08-09?
14:33 slef            ...that we WONTFIX...
14:33 slef            would I be right to say that the WONTFIX that by adding a system preference?
14:32 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3707 enhancement, P5 - low, ---, chris, NEW , Add system preference for customization of the OPAC login page
14:32 slef            kf: purely to fix what they perceive as bug 3707
14:32 * oleonard      has never tried it
14:32 oleonard        kf: Not if you're just changing certain sections of an existing translation, no?
14:31 kf              why would youwant a custom po? it's nightmarish :)
14:30 slef            it would be better to not mess with the templates and still create a custom po file, no?
14:30 kf              but if you mess with the templates, you would have to
14:30 kf              we don't use custom po files
14:29 slef            kf: if they want to use odd language, define their own po file containing the odd language.
14:29 kf              ?
14:29 slef            kf: oh actually they'd be better off doing that as a en-XX language and merging in updates from en-GB or whatever.
14:29 kf              and all our customers are at least using German and English
14:28 H               ok i keep searching maybe i find a sollution
14:28 kf              yeah, but it's even more horrible if you have more than one language to maintain
14:28 kf              for translations and for updates - because you will need to maintain your own po files too
14:28 slef            kf: but still possible. We should support child themes if we don't already but I'm not even going to suggest that one.
14:27 kf              the typo was mine
14:27 kf              slef: that's a really bad idea you know
14:27 oleonard        slef: It is not in the OPAC
14:27 slef            kf: should have been customising
14:27 H               yes
14:27 kf              customuzing templates?
14:27 jcamins         In that case, I think perhaps your records are corrupted.
14:27 slef            oleonard: any idea on the OPAC?
14:26 H               it always dissapear afther indexing
14:26 H               i tried a few times
14:26 jcamins         I thought this was a new problem?
14:26 huginn          04Bug 2647: enhancement, P3, ---, gmcharlt, NEW , Make Patron Reading History be Paginated
14:26 slef            updating http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2647
14:26 H               but i had the problem before
14:26 H               reimport and try again ?
14:25 jcamins         I can't figure out why it would have suddenly just stopped working.
14:25 oleonard        In the staff client it is paginated via JS plugin slef
14:25 jcamins         It shouldn't.
14:25 jcamins         Hm.
14:25 H               does the fact that i dont use the default framework for import has some influence ?
14:25 wahanui         i heard nothing was a requirement, we have guidelines though
14:25 H               still nothing
14:24 slef            is the Patron Reading History Paginated these days?
14:23 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3707 enhancement, P5 - low, ---, chris, NEW , Add system preference for customization of the OPAC login page
14:23 slef            old bug 3707 updated
14:23 kf              slef++ for the mail
14:23 oleonard        slef: oleonard@myacpl.org
14:23 jcamins         You shouldn't need to reindex again. Do another search.
14:22 slef            found it nm
14:22 H               reindexing again ?
14:22 H               sudo /usr/share/koha/bin/koha-zebra-ctl.sh restart Restarting the Zebra Server
14:21 H               ok he did restart
14:21 slef            oleonard: what's your bugzilla email address?
14:19 jcamins         Yeah, I'm not sure where it is.
14:19 H               probably need a path
14:19 H               not found
14:18 jcamins         In that case, you can restart Zebra with koha-zebra-ctl.sh.
14:18 H               on that server manualy i had some help in the chat here (not with packages)
14:17 slef            drojf: costs of downloading by all users, plus a couple of ambiguities in the licence - that's what the co-operative exceptions are intended to mitigate.
14:17 jcamins         H: how did you install Koha?
14:17 jcamins         H: that looks right to me, but you might try restarting Zebra.
14:16 slef            drojf: the licensor's freedom to swing their arms stops at the licensee's noses.
14:16 slef            drojf: no, licensors cannot force publication and only disclosure to themselves if they are also a licensee of the modified version.
14:16 H               http://mibpaste.com/vve5zx
14:15 drojf           complications even
14:15 drojf           slef: what do you mean by complication AGPL brings?
14:15 slef            found bug, fixed bug, resent old bug report
14:15 H               ok did not wanna spawn
14:14 slef            pgrep zebrasrv
14:13 jcamins         To check, run `ps aux | grep zebrasrv`
14:12 drojf           sorry, slow brain
14:10 drojf           kf: ah, now i understand. they say it is cloudbased and people do not install it themselves
14:09 drojf           kf: oh, just stops? that's odd
14:09 H               was testing sorry
14:09 kf              so I miss there is more to read
14:09 kf              drojf: it stops autoscrolling
14:09 H               yes
14:08 kf              drojf: wasn't the difference that they don't give the code to anyone but do only host? (no external servers?)
14:07 drojf           or, how does scrolling break??
14:07 jcamins         H: could you please confirm that zebrasrv is running?
14:07 drojf           scrolling does not "break"
14:07 jcamins         Actually, I was about to ask that.
14:06 kf              never mind...broken scrolling again
14:06 kf              H: is your zebrasrv running?
14:05 drojf           [off] LibLime Academic Koha code version:; Koha schema version:
14:04 drojf           (or even "put that source code on your website for everyone to see")
14:03 drojf           as a creator of free software you cannot yourself request the license being respected (as in "show me the source code you used it in")?
14:02 slef            drojf: but hey, this is a market for lemons :(
14:02 slef            drojf: s/free//
14:01 slef            drojf: as we are the ones who can hold them to the licence or seek damages for infringement of our copyright, but we still need some licensee to try and fail to obtain source from their upstream ll
14:01 drojf           i don't think anyone who knows the slightest about free software would purchase ll academic
14:00 slef            drojf: that too
14:00 drojf           slef: i assumed you would need a koha developer that knows his source code is used
13:59 slef            drojf: AGPL debatably helps slightly with such cases, as it allows any user (and not only the server buyer) to request it, but it brings too many other complications for my taste.
13:58 libsysguy       my cat was late to wake me up
13:58 slef            drojf: yes but you'd need a ll academic koha purchaser to request the source code. Compare with GPL-Violations handling of routers.
13:58 libsysguy       I feel well rested
13:57 oleonard        Hi libsysguy, you're looking well-rested ;)
13:56 drojf           understanding that koha is licensed under gpl and ll academic koha is licensed under ihavenoidea but uses gpl code i was wondering if that isn't exactly the kind of dispute the SFLC was created for
13:53 slef            drojf: like, if you pay your chief exec a million euros a year but don't distribute any dividend to shareholders, you can claim to be "not for profit".
13:52 slef            drojf: and yes, "not for profit" is an ambiguity people can (and do) drive trucks through.
13:51 slef            drojf: so what did you mean "what is between us and the [SFLC]"?
13:50 H               http://mibpaste.com/c2ITOB
13:49 H               yes was ok
13:48 jcamins         Oh, so there was no output from running rebuild_zebra?
13:47 H               result empty screen
13:47 H               then to make sure it was indexed i did do the re indexing
13:46 H               i did add a bulk off data first
13:46 drojf           or people that develop (and get paid) and put out the software for free
13:46 drojf           people that work for free?
13:46 drojf           what are "not for profit" developers?
13:45 jcamins         H: did anything change between the last time it worked and now?
13:45 drojf           The Software Freedom Law Center (SFLC) is an organization that provides pro bono legal representation and related services to not-for-profit developers of free software/open source software
13:45 H               oeps dropped out of chat
13:44 drojf           oleonard: ah, that problem again ;)
13:44 oleonard        drojf: Now try thinking like Smeagol.
13:44 drojf           slef: SFLC provided lawyers for some cases
13:44 oleonard        drojf: That is the result of thinking like a sane and rational person.
13:44 jcamins         Myshking is walking back and forth on my desk hitting my chin with his forehead every time he passes.
13:43 drojf           oleonard: i doubt there is only liblime code in it so that does not make sense to me. re-use gpl code, be gpl, put source code on website for download. or use crazy own licence, don't use gpl code of others
13:43 H               http://mibpaste.com/T5inJQ
13:42 slef            let me know what you think
13:42 slef            ok, first attempt at old bugs report emailed
13:41 jcamins         Whatever.
13:40 slef            s/is for/is claimed to be for/
13:40 wahanui         koha user is probably who should own the files after install (or some user that does most definitely not have root privileges)
13:40 H               koha user
13:39 jcamins         oleonard: that's what AGPL is for.
13:39 jcamins         H: sounds like you might have run rebuild_zebra as the wrong user... what user did you use?
13:39 oleonard        And the notion that if they're "sharing" the code with the sponsoring library that counts?
13:39 slef            drojf: SFLC is an advice centre. I think thd-away asked them for advice in the past.
13:38 H               Problem ---- all my search result dissapeared afther reindexing ? anny tips what that could be the indexing did not give an error before i could search my data aftherwards it was gone (koha 3.8.7)
13:38 jcamins         Agreement from more developers, I think.
13:37 jenkins_koha    Starting build #1005 for job Koha_master (previous build: SUCCESS)
13:37 drojf           interesting. so what is between us and the software freedom law center?
13:36 oleonard        drojf: That right, the "academic" version has never been open
13:35 jcamins         Apparently not.
13:34 slef            not built on rubber blocks then? :-/
13:34 jcamins         Jo's new library.
13:34 slef            jcamins: which is Te Tekare?
13:34 slef            [off] the name restriction suggests not... purpose or field of endeavour restriction, depending if you're FS or OS...
13:34 jcamins         Oh dear. Sounds like the flooring in Te Tekare buckled.
13:33 drojf           [off] ok so the academic thing is not "open" at all?
13:33 slef            [off] the fork continues the old LL tradition of screwing all incoming links to their website... at least now it is only their site and not ours!
13:33 drojf           [off] i don't mean harley if that is what you are referring to.
13:33 jcamins         [off] https://github.com/liblime/LibLime-Koha/ https://github.com/ptfs/Koha-PTFS and I want to say there were a few tarballs
13:32 slef            [off] not sure if it was on their website. There was some thrown over the wall once.
13:31 drojf           [off] that is probably a stupid question, but didn't the fork use to have some kind of (outdated) source code to download on their website? i don't find anything at all
13:31 slef            is it possible to make them public?
13:31 slef            still doesn't work from scripts :-/
13:31 slef            ah Preferences: Saved Searches
13:30 slef            that doesn't work if I'm not logged in
13:29 slef            how do I share it?
13:29 slef            http://bugs.koha-community.org/bugzilla3/buglist.cgi?cmdtype=runnamed&namedcmd=old%20bugs
13:29 oleonard        ...inside Bugzilla
13:29 * slef          tries
13:29 oleonard        Not much shorter, but you can share it with others
13:29 slef            if I save it, can I access it with a shorter URL?
13:28 slef            not saved yet tbh
13:28 slef            oleonard: http://bugs.koha-community.org/bugzilla3/buglist.cgi?bug_status=NEW&bug_status=REOPENED&bug_status=ASSIGNED&f1=days_elapsed&o1=greaterthan&query_format=advanced&v1=700 might be it
13:28 slef            oleonard: yes
13:28 slef            oh sure I know it's all about reducing the load
13:28 jcamins         My time is much better spent actually testing things.
13:27 oleonard        Has anyone put together or found a saved Bugzilla search showing what bugs might be covered in a proposed mass closing?
13:27 slef            yay autocomplete
13:27 jcamins         However, as long as no one is paying me one red cent, I am not spending hours trying to figure out what the patches are _for_ or how to test them.
13:27 jcamins         *read through
13:27 slef            jcamins: remove bugzilla?
13:26 jcamins         slef: I read through the patches, and I remove bugzilla.
13:26 wahanui              16.8
13:26 slef            wahanui: 2.8*6
13:26 oleonard        drojf++ # because we don't downvote people for their opinions around here
13:26 slef            jcamins: but the commit message could be for a patch that misunderstands the bug report and so on. I feel QA should look at bz and RMs should read through patches, which is probably why I've not stood for those roles.
13:26 drojf           oh, it says kohacon. i'm excited
13:25 drojf           oleonard++
13:24 oleonard        http://wiki.koha-community.org/wiki/General_IRC_meeting,_7_February_2013
13:24 oleonard        I created a basic wiki page for the next meeting with stock agenda items. Please feel free to edit, everyone.
13:24 huginn          New commit(s) kohagit: Merge branch 'bug_8977' into 3.12-master <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=e901ae15de6717f8594bd80ecfb0c5e8a23b8af5>
13:24 jcamins         slef: see the above explanation.
13:24 slef            jcamins: it was why test plans should be repeated in the commit message rather than left on bz.
13:23 slef            jcamins: that wasn't the debate AIUI.
13:23 * jwagner       goes to look
13:23 jcamins         jwagner: yeah, oleonard sent a message to the mailing list yesterday.
13:22 jcamins         And, thd, the reason test plans are absolutely mandatory is that the RM is not going to read through a patch to see what it does, whether or not it would be trivial.
13:21 jwagner         There was a meeting?
13:21 jcamins         Sounds good.
13:20 drojf           i like it
13:19 slef            how about this lead-in text: "Would you check some of these rather old bugs to suggest what to do, please? Ideally, tell irc.oftc.net #koha know that you're looking at a bug."
13:17 jcamins         Good, nothing of import.
13:17 oleonard        That's the one.
13:17 jcamins         Heh.
13:17 drojf           wasn't that long
13:17 drojf           "do all the things"
13:16 oleonard        It's around here somewhere. Really long and complicated.
13:16 jcamins         oleonard: I'm looking for the minutes now.
13:16 oleonard        jcamins: Did you get the list of things we volunteered you to do during the meeting?
13:15 oleonard        Hi again #koha
13:12 slef            irc or etherpad should suffice
13:06 drojf           or we spend 3 months writing a ticket system to hand out old bugs one by one ;)
13:02 drojf           or some etherpad thingy like we had at gbsd sometimes
13:02 drojf           maybe a "i'll take a look at old_bug_number" on irc is enough?
13:01 drojf           how many people do we realistically think will work on that? and how many of those do not hang around here?
13:01 kf              not ideal.
13:01 kf              encourage people to reply to the mail with a new list minus worked on bugs?
13:00 slef            drojf: yeah but how do we stop it?
12:59 drojf           [off] kf: see, they promise stuff too :D
12:58 kf              drops off
12:58 kf              slef: hm yeah, that's why a searched list would have been nice, can see what drops of by modification date
12:57 kf              [off] http://www.librarytechnology.org/ltg-displaytext.pl?RC=17550
12:57 drojf           -1 for multiple people checking single ancient bugs
12:57 slef            and do we think multiple people will check each one?
12:56 kf              drojf: lol
12:56 drojf           you could vary the subject too. promise people stuff. free ipad, viagra...
12:56 kf              :)
12:56 slef            if the batches get too big, will they all get checked?
12:56 kf              oh
12:56 slef            and I'll probably vary the sending time too
12:56 slef            I'd also go for something other than 7 so that it changes day each time
12:55 wahanui              19.6
12:55 kf              wahanui: 2.8*7
12:55 kf              2.8*7
12:55 kf              I was hoping to get it done faster :)
12:55 slef            2.8 * 7 = 19.6
12:55 kf              25?
12:55 kf              and like...hm. 30?
12:55 kf              but opinions might differe here :)
12:54 kf              slef: I think something like weekly maybe
12:53 slef            so if we'd need to check about 2.8 old bugs per day to get through them in 3 months, how many would you like me to email out how often?
12:49 vfernandes      works fine :)
12:28 kf              here is a full example: http://wiki.koha-community.org/wiki/SQL_Reports_Library#Links
12:27 vfernandes      hummm thanks a lot kf
12:25 kf              it's very handy
12:25 kf              concat('<a href....',biblionumber,'...)
12:25 kf              you use concat + html
12:25 wahanui         reports library is probably found at http://wiki.koha-community.org/wiki/SQL_Reports_Library
12:25 kf              reports library?
12:25 kf              there is an example on the reports page I think
12:24 kf              vfernandes: yes
12:21 vfernandes      one question: it's possible to have links in SQL reports
12:19 kf              there are minutes on the wiki
12:18 kf              vfernandes: yes
12:14 vfernandes      meeting is over?
12:01 kf              you should ask gerundio maybe
12:00 kf              don't know
11:57 slef            kf: oh right. Do you think they'll implement strict consent?
11:56 kf              slef: seems it's a topic for spain/portugal now
11:53 slef            kf: UK ICO backed down on implementing the cookie consent directive, so we stopped working on it.
11:38 kf              I think it will be done on release probably
11:36 slef            the licence change
11:35 kf              slef: ?
11:32 slef            mmmm so is it left for jcamins_away to drive?
11:30 Brooke          that ended up being removed from the wiki agenda, also
11:29 slef            kf: oic. context fail.
11:29 Brooke          yep
11:29 slef            Brooke: ha'penny = halfpenny, FWIW
11:29 kf              that very meeting
11:29 kf              it wasn't done becuse we already voted
11:29 slef            kf: sorry you don't escape that easy ;)
11:29 Brooke          heh, if you had a haypenny for each instance that happened, you'd be rich :P
11:29 kf              ah
11:29 slef            18:44:51 <cait> i think if we advertise this [GPLv3 change], anyone intersted can show up next meeting
11:29 kf              well not fair, I didn't chair because Iforgot.. and would probably have forgot that too
11:29 kf              I didn't chair that :P
11:29 kf              oh
11:28 slef            I just spotted another action not noted as an #action in the minutes of December's meeting.
11:28 kf              team?
11:28 slef            Toll! Ein Anderes Macht's!
11:27 Brooke          nicht so gut aber
11:27 kf              und dir?
11:27 kf              gut
11:26 Brooke          Wie geht's?
11:26 kf              hi Brooke
11:25 Brooke          o/
11:22 wahanui         i think RM is jcamins
11:22 kf              RM?
11:22 kf              RM is jcamins
11:22 wahanui         kf: I forgot rm
11:22 kf              forget RM
11:22 kf              this was a horrible time for US - maybe not fair
11:18 wahanui         RM is busy :) or paul_p
11:18 slef            wahanui: RM?
11:18 slef            3.12 RM?
11:16 slef            so, where do I report bugs in the k-c git-bz?
11:15 oleonard        See you all in a couple of hours
11:15 slef            Would someone else create the next meeting page, please?
11:15 slef            updated http://wiki.koha-community.org/wiki/General_IRC_meeting,_9_January_2013
11:14 drojf           maybe we should have a deadline for news about kohacon or else give it to the second location? :P
11:14 kathryn         nightie night!
11:14 kf              sleep well nzers :)
11:14 davidnind       thanks kf for chairing, off to bed (midnight here in NZ)
11:13 JDatTeTakere    zzzzz...bed it is...work in 8 hours.
11:13 kathryn         thanks kf, bye all
11:13 * oleonard      returns to his breakfast
11:13 drojf           kf++
11:13 paul_p          bye all
11:13 kf              thx all for being here - now back to work/bed! :)
11:12 huginn          Log:            http://meetings.koha-community.org/2013/koha_irc_meeting.2013-01-09-10.01.log.html
11:12 huginn          Minutes (text): http://meetings.koha-community.org/2013/koha_irc_meeting.2013-01-09-10.01.txt
11:12 huginn          Minutes:        http://meetings.koha-community.org/2013/koha_irc_meeting.2013-01-09-10.01.html
11:12 huginn          Meeting ended Wed Jan  9 11:11:16 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
11:12 kf              #endmeeting
11:12 davidnind       kf++
11:12 kf              :)
11:12 kf              hope that was right
11:12 kathryn         (13th is fine too)
11:12 kf              #info Next meeting is 7 February 2:00 UTC
11:12 wahanui         gerundio's stomach is complaining too much
11:12 slef            wahanui: gerundio's stomach?
11:12 kf              ok, 7th
11:12 thd`            7th is better for being well after ALA midwinter.
11:12 JDatTeTakere    7th is good
11:11 kf              I never got to be friends with the new meeting times
11:11 davidnind       happy with day either side
11:11 slef            thanks wahanui
11:11 drojf           oleonard: only bad for everyone else that likes today's time ;)
11:11 wahanui         7th is worth a try
11:11 slef            7th?
11:11 kathryn         day either side is no worries for the Catalyst lot so far as I know :)
11:11 slef            or you can go for 13th if you don't mind me missing
11:11 oleonard        That time is okay for me, but if it's bad for everyone else let's not do it then
11:10 kf              I think having another meeting sooner is better, not postpone it too long
11:10 slef            kathryn: move by a day or two weeks?
11:10 kf              kathryn: would 7th be ok?
11:10 drojf           oh. maybe better take a week later then
11:10 kathryn         oh! 6 feb is public holiday in NZ so not ideal
11:09 slef            6 Feb looks ok to me at the mo
11:09 kf              iirc
11:09 kf              I think something like 3/4 pm for you
11:09 kf              and noone who will be awake then is here?
11:09 kathryn         evil must mean happy for me :)
11:09 slef            slackers ;)
11:09 kf              davidnind++
11:09 kf              davidnind: thx for looking upt eh times .)
11:08 kf              same here
11:08 drojf           ah, the evil time. go nuts with the date, will be in bed :)
11:08 kf              #topic Time/date for next meeting
11:08 davidnind       6 February 2:00? (previous meetings: 7 Nov - 2:00, 5 Dec - 18:00, 9 Jan - 10:00)
11:07 kf              we have reached an hour now - i would like to sset the date/time for next meeting
11:07 slef            argh, and it hardcodes koha-patches@...
11:07 * drojf         giggles
11:07 drojf           "Teach git-bz to optionally sign off when applying patches ... DO NOT USE THIS OPTION AS AN ALTERNATIVE TO ACTUALLY TESTING CODE."
11:06 kf              and a central place
11:06 kf              maybe just set one pu because it's flexible
11:06 slef            ?
11:05 slef            people set up a repo on k-c because I wasn't including koha-specific changes (as I actually use git-bz for other things)
11:05 kf              #link http://git.koha-community.org/gitweb/?p=git-bz.git;a=summary
11:05 * thd           about to be involuntarily disconnected
11:05 slef            ohhhh I see
11:05 drojf           but that does not mean anything
11:05 drojf           i didn't know
11:05 kf              slef: I am not sure
11:04 slef            kf: was that announced and I just missed it?
11:03 thd             paul_p: I think that your proposal to change bug status without necessarily changing resolution is much better than some hybrid non-standard resolution.
11:03 kf              ok, anything that should be added to the minutes? #info etc?
11:02 drojf           forkers :P
11:02 kf              slef: there is a git-bz repo on kc-org now
11:02 kf              you can't see relations betwee bugs (yet)
11:02 slef            oleonard: has someone extended it to edit the bugzilla fields and not bothered to send a pull request?
11:01 kf              ColinC: that's true
11:01 ColinC          and it may not mention the other two bugs it inadvertantly fixed or the three it introduced
11:01 kf              git-bz++
11:01 oleonard        slef: git-bz!
11:01 kf              I have to read a gazillion of mails lately and more than happy to get a complete picture
11:01 slef            s/fibbing/misunderstanding the bug report
11:01 slef            and anyway, you still have to look at Bugzilla to mark it "Signed Off"
11:01 kf              oh yes
11:01 oleonard        slef: RM or QA looking at Bugzilla emails for instance?
11:01 slef            the commit message could be fibbing
11:00 kf              ideally
11:00 kf              message
11:00 kf              it's all in the commit
11:00 * slef          boggles
11:00 slef            oleonard: if they're not looking at Bugzilla, how do they know if the patch fixes the bug?
11:00 drojf           +1 for repaste. more load on bugzilla but the latest infos in the latest entry
11:00 kf              you never know what happens on bugzilla between you putting the patch there and me or somene else looking at it
10:59 oleonard        slef: Because someone may not be looking at Bugzilla, just applying patches using git-bz
10:59 kf              repaste
10:59 slef            ok, final query from me on this: in the most common case (test plan from bugzilla still applies), should I repaste the test plan from the bugzilla, or write "see bugzilla"?
10:58 kf              as well as functional description?
10:58 kf              so maybe we could amend that it should also contain developer like descriptions of changes?
10:58 kf              I am all for documentation
10:57 slef            hehe
10:57 drojf           again? :P
10:57 kf              slef: thought you already did recently :)
10:57 slef            Can I also grumble about blank wiki commit messages here? ;-)
10:57 slef            kf: I think that's what ColinC was driving at, but he'd have to confirm.
10:55 slef            #info that's not perfect for us, as it doesn't include the bug/feature summary, which is one thing we do better, but it does show how to describe the change fully
10:55 kf              so more from the code side of things?
10:55 oleonard        You're right slef, and it should
10:55 slef            #link http://www.gnu.org/prep/standards/html_node/Style-of-Change-Logs.html#Style-of-Change-Logs
10:54 kf              bug/feature description
10:54 kf              A description of what problem the bug addresses, or what feature it adds.
10:54 kf              but I think haveing soe guidelines is good and makes you think about what you do even
10:54 slef            kf: and http://wiki.koha-community.org/wiki/Commit_messages doesn't tell people to say what changes they introduce.
10:54 kf              yes, bug reporting is for everyone, we can help people there, also new developers
10:53 oleonard        Bug reporting is separate from commit messages I think
10:53 kf              ColinC: and it's taking too much time to find out
10:53 slef            oleonard: not conflict exactly, but seems to duplicate
10:53 * kf            nods
10:53 slef            oleonard: http://wiki.koha-community.org/wiki/Bug_Reporting_Guidelines#Description
10:52 ColinC          Danger is lots of commit messages currently do not tell you what change they introduce
10:52 oleonard        The commit messages page should be considered the official version at this time. I don't know what other pages conflict with that advice
10:51 kf              a series of steps and tests to do
10:51 kf              I think test plan describes more than one test
10:51 slef            oleonard: so one of the workflow and the commit messages wiki page is probably wrong, or do we want N(patches)+1 test plans for each bug?
10:50 kf              and jcamins++ for good instructions :)
10:50 slef            oleonard: ok.
10:50 kf              oleonard++
10:50 kf              and some patches for one feature also endanger other parts, so test plans need to be a bit bigger
10:50 oleonard        Please keep in mind that the guidelines have already been set by the RM, so this discussion shouldn't be about whether to change it
10:50 thd             slef: Test plans should relate to both a bug and a patch.
10:50 kf              slef: often you find more problems ... than you initially thought there were
10:50 paul_p          slef yep ;-)
10:50 slef            paul_p: last test plan wins?
10:49 oleonard        The test plan tells QA how to test the patch slef
10:49 kf              and paul_p: agreed
10:49 kf              drojf: yep, that's what I think too
10:49 slef            Shouldn't a test plan should pertain to a bug, not to a patch?
10:49 drojf           if it is huge, have an rfc or something?
10:49 paul_p          slef = hélas, as long as it's impossible to update description, we can't rely on the bug description, because the test plan changes between initial submission of the bug & the patch !
10:49 kf              I think if you have something really big, you could put a link to a wiki page
10:48 kf              thd: I haven't heard someone reached a limit yet :) and I write pretty long commit messages when testing sometimes
10:48 slef            thd: yes
10:48 kf              and I like to see in git how things work, test plans help with that there too
10:48 thd             Can the commit message be arbitrarily long?
10:48 kf              slef: the problem is, they get rewritten, amended, etc. a lot, so it's quite hard to findon bugzilla
10:48 oleonard        If you use git-bz to attach patches your test plan will appear in Bugzilla automatically with the commit message
10:48 drojf           i think jcamins_away would like to see them in the commit message
10:48 kf              see the example for a good commit message there
10:48 slef            I feel like I'd expect it in the bug description, not the commit messages.
10:47 kf              #link http://wiki.koha-community.org/wiki/Commit_messages
10:47 slef            bug description/comments or commit messages?
10:47 kf              into the commit message
10:47 drojf           kf: yes i actually mean the missing icu option in the packages
10:47 thd             Where do test plans go?
10:47 kf              slef, thd?
10:47 kf              #topic Test plans
10:47 kf              drojf: I think we can't activate that by default as long as pakages don't support it as option
10:46 kf              # Test plans
10:46 * drojf         hides even more
10:46 drojf           icu
10:46 drojf           ice
10:46 kf              test plans?
10:46 kf              ok
10:45 kf              oleonard: agreed, but we should have the beamer/transporter activated
10:45 slef            #action people keep thinking about if we have disabled any features by default that shouldn't be
10:45 oleonard        I still think the time travel feature is too dangerous to enable by default
10:45 kf              I woudl like to see that as another reminder and encourage to file bugs if you have an idea :)
10:45 slef            anyone been thinking deeply about Koha over the holidays? ;-)
10:45 kf              so, have people thought about it? ;)
10:44 slef            Action Items ------------ * people start thinking about if we have disabled any features by default that shouldn't be
10:44 kf              people start thinking about if we have disabled any features by   default that shouldn't be
10:44 kf              ok, the only action items I can see are:
10:44 * drojf         hides
10:44 * slef          scrabbles
10:44 drojf           but... that was last year!
10:44 kf              not sure what goes here, someone?
10:44 kf              #topic Actions from General IRC meeting, 5 December 2012
10:44 drojf           :)
10:43 kf              ah, ok
10:43 kf              drojf: are you ok witht hat, as it was your proposal?
10:43 drojf           kf: sounds ok for me
10:43 slef            kf: yes, sorry boss.
10:43 kf              just trying to make this not go forever :)
10:43 slef            kf: yes, sorry boss.
10:43 slef            </rant>
10:43 kf              ok, I think we put down some ideas and have a plan to try out - could we agree on moving to the next topic?
10:43 slef            this should be publicised more
10:42 slef            probably most users will want to do ALL searches, so they can see it was fixed in version 3.X.Y and know what they want to upgrade to
10:42 paul_p          but with ALL you'll also get RESO-FIXED & CLOSED, right ?
10:42 slef            I did not know that.
10:42 huginn          slef: 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1634 normal, P3, ---, gmcharlt, RESOLVED REMIND, Incorrect encoding convertion in MARC record form
10:42 slef            @query ALL Incorrect encoding convertion in MARC record form
10:41 kf              or add ALL at the begining of your query
10:41 kf              only if you specify your search to make then
10:41 kf              if you search for keywords, the bug does not show up if it's marked resolved
10:41 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1634 normal, P3, ---, gmcharlt, RESOLVED REMIND, Incorrect encoding convertion in MARC record form
10:41 slef            that was bug 1634
10:41 thd             kf: What do you mean by does not show up?
10:41 paul_p          s/(but//
10:41 slef            oleonard: you're correct
10:41 kf              thd: it gets painful
10:41 paul_p          (but oleonard = would adding a status (something like "old bug to verify if it's still valid") please you to avoid "RESO - REMIND" ?
10:41 huginn          slef: No results for "Incorrect encoding convertion in MARC record form."
10:41 kf              thd: I think we shouldn't invent so many new things in bugzilla
10:41 slef            @query Incorrect encoding convertion in MARC record form
10:40 kf              resolved doesn't show up - I just tested
10:40 thd             slef: What about POSSIBLY RESOLVED REMIND or some variant which is not certainly resolved.
10:40 * slef          tests
10:40 oleonard        slef: No, I assume.
10:40 slef            oleonard: are you sure?
10:39 slef            thd: I look for improvements even in the possibilities I don't prefer.
10:39 oleonard        But resolved remind wouldn't show up in searches, so how is it found by others?
10:39 thd             The presumption of RESOLVED seems mistaken to me.  It should be unambiguously qualified.
10:39 oleonard        I think all resolved remind does it possibly remind the original submitter since they should get an email notification of the change
10:39 kf              hm good description, we should put that on the wiki somewhere maybe
10:39 davidnind       slef: thanks
10:38 slef            davidnind: it's not actually defined in the bugzilla help... but I see it as "ask us about this again later if you care about it"
10:38 kf              slef: sounds perfect :)
10:38 kf              #idea prefer RESOLVED REMIND to RESOLVED WONTFIX
10:38 slef            I already have a script that does email and bugzilla.
10:38 davidnind       What does RESOLVE REMIND mean? Doesn't make any sense to me me (but I'm not a developer...)
10:38 kf              #action slef volunteers to mail the mailing list with old bugs to review
10:37 kf              slef: thank you!
10:37 slef            kf: I volunteer.
10:37 slef            thd: it's still not great, so I'd still prefer to try the mailing old bugs to -devel idea first, but it's better than WONTFIX.
10:37 paul_p          +1 for only bugs in the dashboard
10:37 davidnind       I don't thing automatic closing is a good idea - people have put effort and time into creating. The minimum that should be done is reviewing it. I guess the issue is how this is done...
10:36 kf              and yes,only bugs, not enhancements I would think
10:36 thd             slef: Do you not think that RESOLVED REMIND is as misleading as WONTFIX?
10:36 kf              woudl someone volunteer to create a report/mail the mailing list?
10:36 oleonard        oldest open bugs with enhancements filtered out please!
10:36 kf              ok
10:36 kf              it's late for you!
10:36 kf              #idea add oldest open bugs to koha's dashboard
10:35 drojf           slef: :)
10:35 kf              kathryn: ah, oly for needs sign-off!
10:35 thd             POSSIBLY RESOLVED REMIN would be better
10:35 slef            drojf: hey don't blame me, you put it in your proposal
10:35 kathryn         I was just looking for it...but my eyes are tired!
10:35 kf              let's check :)
10:35 kf              kathryn: I think rangi already did something similar to that
10:35 drojf           wontfix sounds cruel
10:35 paul_p          +1 for RESO REMIND
10:35 kathryn         it might be poss to have the oldest bugs visible on the dashboard, if there's no objection to making old bugs more visible
10:35 drojf           slef: definitely
10:34 slef            drojf: would you be OK with RESOLVED REMIND instead of WONTFIX?
10:34 drojf           and see they are active
10:34 slef            oleonard: from the documentation, "WONTFIX: The problem described is a bug which will never be fixed." which isn't really true if we're auto-closing with "please reopen if this is still a problem"
10:34 drojf           thd: but then you have discussions there on the bug
10:34 oleonard        paul_p: Going through old bugs would be a nice way to get folks involved who wouldn't submit patches for GBSD
10:34 kf              drojf: I would say plus :)
10:33 paul_p          so I won't focus on those very old bugs (except for those affected to me, I already cleaned them a few weeks/months ago iirc)
10:33 thd             The worst bugs as in most annoying but not blockers may be the oldest valid bugs but especially difficult to fix.
10:33 drojf           if we source this out to only bug squashing days i assume that is not going anywhere far. or is that supposed to be a plus to a regular checking of old bugs?
10:33 slef            oleonard: oh sure, but it's a nicer automatic closure reason than WONTFIX
10:33 kf              #idea have a regular mail to the mailing list and a searched report with oldest n bugs for review
10:33 slef            thd: yes, we have REMIND
10:33 paul_p          oleonard = for me, there are enough valid & known things to do to NOT focusing on old things that I don't know if they're still relevant
10:33 oleonard        slef: Setting "remind" didn't accomplish anything in the past when it was done
10:33 kf              #idea next few bug squashing days could focus on reviewing the oldest bugs first
10:32 slef            thd: I think we might have REMIND... checking
10:32 kf              davidnind++ I like that idea
10:32 oleonard        davidnind++
10:32 davidnind       Maybe the next few bug squashing days could focus on reviewing the oldest ones first?
10:32 slef            Irma: congratulations and bye
10:32 thd             We need some name better than won't fix for a designation for any prospective date based closing.
10:32 drojf           slef: that sounds very do-able, if people really do it :)
10:32 kf              congratulations!
10:32 Irma            sorry all, I have to leave, one of my children just got engaged! Bye!!!
10:31 kf              you might miss good hints otherwise and on top the original reporter gets feedback about the progress
10:31 slef            = about 2.8 bugs per day to get through them in 3 months
10:31 kf              then you can work from that
10:31 kf              if a customer reports a bug, you should try seraching first, see if there is more information about the problemon bugzilla
10:31 slef            252 bugs are > 700 days since bug changed.
10:31 kf              paul_p: nto sure that's true
10:30 paul_p          oleonard I think that is because, if I want to fix a bug, I don't know which one to start with. And i'll choose a recent one, for sure. Thus old bugs will never be updated probably
10:30 thd             That is my understanding of the issue please correct me if I am mistaken.
10:29 drojf           oleonard: and they are not all valid. there is stuff "one person" reported, that person is not on bugzilla. we will never find out. there is stuff that is already fixed by other patches. i would not want to close it all if i knew it is all valid
10:29 slef            we do some form of kf's "N bugs a week" idea, get through all "old" bugs in 3(?) months, then reconsider bulk closures?
10:29 kf              so maybe until then we could try and do some review process and see if that works
10:29 oleonard        thd: Is that really the issue?
10:29 thd             oleonard: The issue is that many bugs are listed but no longer valid.
10:29 oleonard        paul_p: I think closing fixed bugs will help better than closing unfixed ones
10:29 kf              next meeting with a mail to the mailing list would be ok for me tho
10:29 slef            can I suggest
10:29 kf              because I woudl not feel comfortable deciding that right now
10:29 paul_p          oleonard = the concern of drojf is that there are so much bugs open, that finding the ones that should really have our attention is impossible
10:28 kf              bulk closing needs a bigger group/some discussion on the mailing list before we do it
10:28 kf              ok, what I think
10:28 oleonard        I'm not sure what the benefit is of closing bugs which are still valid
10:28 paul_p          kf = of course, I would do that for batch closing ;-)
10:28 slef            paul_p: I hate it when debian does that. Results in lots of false closures.
10:28 kf              oleonard++
10:28 drojf           i think i spent a few hours looking at 2008 bugs and checking if valid or not. that were... maybe 30? dont remember
10:28 oleonard        I think we might be better served marking bugs as resolved which are really fixed
10:28 kf              yeah,b ut turning off mail for those might be pointless if you want a comment :)
10:28 thd             paul_p++
10:27 paul_p          what about adding 1st a comment like "is this bug still valid with 3.10 ? in case of no feedback, this bug will be closed in X days"
10:27 * slef          tries to construct a report
10:27 kf              paul_p: thx for the info :)
10:27 slef            how long is reasonable for us to take to review the old bugs?
10:27 thd             s/Bugs/Open bugs/
10:27 paul_p          kf & drojf = I also can suspend mails when bulkmodifying bugs
10:26 drojf           slef: i had numbers, but not at home/not my computer. don't remember, but a few hundreds i think
10:26 thd             Bugs are sorted by date effectively.  Is date sorting not sufficient?
10:26 drojf           (and no, i am not a fan of blindly closing. if we can magane to look at a handful of old things every week, i would prefer that)
10:26 slef            drojf: did your research find out how many are "old"?
10:26 kf              not saying one alone has to do it
10:25 kf              20 every week? :)
10:25 slef            kf: I'd actually go for 12 bugs every 6 days orsomething like that.
10:25 kf              I am torn between drojf and slef actually, I can se both points, but I think blindly closing feels wrong
10:25 drojf           unless a fairy drops a lot of time or money on us
10:25 oleonard        thd: There is no reason to take karma from drojf
10:25 slef            drojf: I sympathise with the problem that they often get in the way.
10:25 drojf           slef: we will never get around to it
10:24 slef            drojf: no, we're just waiting until we get around to it.
10:24 thd             drojf--
10:24 drojf           i don't see how that is better
10:24 drojf           but we dont tell
10:24 thd             slef++
10:24 drojf           slef: that is what we do now
10:24 kf              once the list is done, pull up the next
10:24 kf              could be a saved search
10:24 slef            drojf: I think it would be pretty harmful to let people point at Koha and say "they say they won't fix $BUG, which is a horrible bug they've known about for years"
10:24 thd             kf++
10:24 drojf           oleonard: i would close some things that are "old". maybe "all added/edited last 2009" for starters. a klot of that is imported from an old tracker, reported by people that do not work with us anymore
10:24 kf              and ask people to take a look and close or comment
10:23 kf              like create a mail to the list ever 2 weeks or so with the oldest 50 bugs still open
10:23 thd             oleonard: The proposal is bugs over some given age which concerns me unless they can be easily found.
10:23 kf              maybe we could do it on a month to month basis in a joint effort?
10:23 slef            mib_vwq7dj: sorry, wrong link: http://wiki.koha-community.org/wiki/Koha_on_Ubuntu
10:23 kf              and rangi can turn off mailing for this if you want that
10:22 oleonard        What kind of bug would be a candidate for automatic closing?
10:22 kf              you can do bulk edits
10:22 drojf           i dont know much about bugzilla, maybe we can add a reason? closed-automatically or something?
10:22 slef            mib_vwq7dj: look at INSTALL.ubuntu* in the downloads, or http://wiki.koha-community.org/wiki/Koha_on_Lucid_using_Koha_packages
10:22 kf              I agree with slef too, but I think discussing this is good
10:22 thd             drojf: Is there a way of distinguishing what was closed without full assessment?
10:22 kf              mib_vwq7dj: we are currently holding a community meeting, please come back a bit later
10:22 drojf           we would not lose the old entries, just mark them resolved/wontfix or something, with the option to reopen
10:22 oleonard        I agree with slef
10:21 slef            I'm really hesitent about marking them WONTFIX as there are probably a few lurking there which we should still fix. The problem is finding the wood among the trees.
10:21 mib_vwq7dj      please ask my question
10:21 drojf           my proposal would be to close something like "all from 2009+2010" or something so we return to a useful bugtracker one day
10:21 kf              drojf++ for that
10:21 drojf           there is not much to say i think. we have a long backlog on bugzilla with stuff dating to 2009 (i closed all 2008)
10:20 kf              drojf: do you want tos a few words about your proposal?
10:20 kf              #topic Cleaning bugzilla
10:20 kf              ok, next topic... giving you a second to stop me
10:20 slef            (I think I'm allowed to use #action but only chair can use #agreed and #startvote)
10:19 drojf           at tleast that is the last thing i remember about kohacon
10:19 kf              thx slef
10:19 slef            #action kf to email the organisers and ask how it's going
10:19 thd             mib_vwg7di: someone will direct you to an appropriate resource after the meeting.
10:19 drojf           the last few meetings it was "we are almost done with the hotel stuff"?
10:19 kf              I can do that
10:19 kf              oleonard: ooh, do we get to wear costumes? ;)
10:19 slef            would someone like to email the organisers and ask how it's going?
10:18 drojf           lol
10:18 oleonard        Also known as the Magical Mystery Con
10:18 kf              I am not aware of any news here, is someone present who knows more?
10:18 mib_vwq7dj      hi, I'm new in koha and ubuntu but.  i want to install koha on ubuntu server 12.04.01. Can you give me a step by step tutorial about how to install it
10:18 kf              #topic KohaCon2013
10:18 kf              #agreed votes are pro creating a 'developer's handbook' on the wiki :)
10:17 thd             OK
10:17 kf              but let's put it at the end, ok?
10:17 davidnind       +1
10:17 thd             Yes, I think I am confused about where test plans should go.
10:17 kf              slef: if there is need to discuss, we can create a topic for that
10:17 paul_p          +1 (who could vote -1 ?)
10:17 kathryn         +1 from me too
10:17 jdattetakere    +1
10:17 kf              oleonard: moving on ok for you?
10:16 slef            let me know if/when I can return to test plans
10:16 kf              I was not trying to manipulate the vote.. I think :)
10:16 drojf           +1
10:16 drojf           yeah for documentation
10:16 thd             +1 What could possibly be wrong with more documentation.
10:16 drojf           thd: i can test the functionality of a patch without reading the whole source code. five steps of "do 1, then 2, ... does x work?" are much faster to get thorugh than reading a lot of perl and comments. also non-developers might be testing things (like in a sandbox) and they will probably not touch the patch file at all
10:16 kf              oleonard: I think he just wanted to bring all the links/pages together
10:15 oleonard        Fleshing out the coding guidelines section, or incorporating it?
10:15 kf              +1 from me too
10:15 kf              who is against more documentation - not me :)
10:15 kf              #info proposal in the agenda: http://wiki.koha-community.org/wiki/General_IRC_meeting,_9_January_2013
10:15 slef            ;)
10:15 slef            #vote Yes
10:14 kf              #topic A "Developer's handbook" on the wiki?
10:14 slef            kf: yeah I think we're proving magnus's motivation ;)
10:14 kf              as it seems a good fit right now
10:14 kf              I think I woudl like to moove on to magnus's suggestion at this point
10:14 paul_p          the 7167 has a short follow-up, that should be not so hard to test, and it's a VERY handy improvement!
10:13 slef            which reminds me... editing out "The application crashed."
10:13 kf              #link http://wiki.koha-community.org/wiki/Commit_messages
10:13 kf              ah, i was thinking about
10:13 slef            perhaps
10:13 slef            #link http://wiki.koha-community.org/wiki/Bug_Reporting_Guidelines#Description
10:13 thd             drojf: Would a test plan not be self evident as part of the comments in well written tests?
10:13 kf              #info current discussion about the database update changes can be found in bugzilla - start with bug 7167
10:12 huginn          04Bug 7167: new feature, P1 - high, ---, jonathan.druart, Signed Off , updatedatabase improvements
10:12 huginn          04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167 new feature, P1 - high, ---, jonathan.druart, Signed Off , updatedatabase improvements
10:12 kf              #link http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7167
10:12 wahanui         bug 7167 is commented out of control
10:12 slef            bug 7167
10:12 kf              oleonard: could you find it maybe for me? looking for the bug number
10:12 kf              ther is doc on the wiki
10:12 slef            by test plan you mean the comment with 1.2.3. and description of success/failure?
10:11 kf              and time is really precious when it comes to shorten the list of things waiting for attention :)
10:11 kf              yes, and also you save a lot of time for testers and qa team
10:11 kf              there are a lot linked to the main bug I think, look for database improvements
10:11 drojf           as someone who might be testing your patch, chances are higher with a test plan. and by higher i mean i might actually consider doing it
10:11 slef            yeah pretty much. Anyone got the bug number?
10:10 kf              does that answer your question?
10:10 kf              slef: the new system has been reverted, so for the time being, you just submit your patches with the updatedatabase bit
10:10 paul_p          (sorry for being a little bit late !
10:10 paul_p          #info paul Poulain, BibLibre, France
10:10 * oleonard      didn't mean to be away
10:09 kf              the follow-ups still need sign-off I think
10:09 kf              slef: afaik you can see it in bugzilla
10:09 * oleonard-away asks that everyone listen to kf and really do add test plans and good descriptions to patches!
10:09 kf              I think so far 3.12 is moving along as planned, some bigger features have gone in too
10:09 slef            what's the situation with database updates?
10:09 kf              and please keep signing off and testing
10:09 slef            WaqarAzeem: no problems, but we want to concentrate on news for a few minutes, so ICU help a bit later probably.
10:08 kf              just the usual reminder to add test plans and good descriptions to your patches
10:08 kf              Hm, maybe I could try and say a few things
10:08 WaqarAzeem      I am really sorry for this ...
10:08 kf              #topic Update on 3.12
10:08 WaqarAzeem      i followed and artical and got this error without any trance ... [warn] previous transaction didn't reach commit
10:07 kf              WaqarAzeem: we are in a meeting right now - it shouldn't take long - maybe ask in a few minutes?
10:07 kf              slef: agreed :)
10:07 slef            magnus++ for that reason
10:07 WaqarAzeem      Hi, Is there any problem with 'debean' and ICU feature for multilanguage search indexing.
10:07 kf              #topic Update 3.10
10:07 slef            it would be nice if short updates were left in the agenda if they can't make it
10:06 kf              I think neither our RMaint nor our RM are here today, so I am moving forward if noone speaks up
10:06 kf              you are too late, the topic has moved on
10:06 drojf           i anounce i'm going to get tea water
10:06 kf              #topic Update on 3.8
10:05 kf              ok, moving on to next topic then
10:05 kf              does someone have an announcemnt to make?
10:05 kf              #topic Announcements
10:04 Irma            #info Irma Birchall CALYX Sydney, Australia
10:04 kf              hm forgot the topic...
10:04 raj4perl        that seem to have fixed the rediection issue
10:04 thd             #info Thomas Dukleth, Agogme, New York City
10:04 davidnind       #info David Nind, Wellington, NZ
10:04 ColinC          #info Colin Campbell ptfs-europe ltd.
10:04 kathryn         #info Kathryn Tyree, Catalyst IT, NZ
10:04 raj4perl        just if some one else stumblled upon this issue - The 'Version' parameter was missing in database
10:04 jdattetakere    #info Joanne Dillon (JD) at Te Takere/Horowhenua District Libraries
10:03 kf              thx slef and drojf for the link
10:03 slef            #info MJ Ray, software.coop member, England
10:03 drojf           #info Mirko Tietgen, Berlin
10:03 oleonard-away   #info Owen Leonard, Athens County Public Libraries
10:03 kf              #info Katrin Fischer, BSZ
10:03 drojf           http://wiki.koha-community.org/wiki/General_IRC_meeting,_9_January_2013#Agenda
10:03 kf              please introduce yourself with #info
10:03 raj4perl        Guys
10:03 vfernandes      hello :)
10:03 kf              welcome all to the koha irc meeting
10:03 davidnind       http://wiki.koha-community.org/wiki/General_IRC_meeting,_9_January_2013
10:03 slef            #link http://wiki.koha-community.org/wiki/General_IRC_meeting,_9_January_2013
10:03 huginn          The meeting name has been set to 'koha_irc_meeting'
10:03 huginn          Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
10:03 huginn          Meeting started Wed Jan  9 10:01:27 2013 UTC.  The chair is kf. Information about MeetBot at http://wiki.debian.org/MeetBot.
10:03 kf              #startmeeting Koha IRC Meeting
10:02 wahanui         i already had it that way, huginn.
10:02 huginn          kf: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'
10:02 wahanui         if there is a meeting then Brooke must want me
10:02 kf              #startmeeting
10:02 kf              can you look for the link tot he agenda please?
10:02 kf              give me a second please
10:02 kf              yes I can do that
10:01 drojf           kf: are you chairing?
10:00 drojf           meaning you should try localhost:5001
09:58 drojf           5000 is opac. 5001 would be staff
09:58 raj4perl        and every time it redirects to mantenance.pl
09:58 raj4perl        yes
09:58 kf              did you try accessing localhost:5000?
09:58 drojf           raj4perl: the opac maintenance thingy usually comes when you have not fnished the web installer
09:57 kf              you didn't run the web installer yet, right?
09:57 raj4perl        Okay, will do that. Thanks
09:56 wahanui         mailing lists are at http://koha-community.org/support/koha-mailing-lists/
09:56 kf              mailing lists?
09:56 kf              raj4perl: you can also ask on the mailing list
09:56 kf              raj4perl: sorry, i have never installed koha with plack, maybe if you try a bit later someone with experience will be around
09:53 raj4perl        Here is the log - "OPAC Install required, redirecting to maintenance"
09:50 raj4perl        What am i missing? Please help.
09:50 raj4perl        and when i go to http://localhost:5000/cgi-bin/koha/installer/install.pl, it return 'not found'
09:50 raj4perl        even when i got to http://localhost:5000/cgi-bin/koha/opac-user.pl it redirects back to mantenance.pl
09:50 raj4perl        i've done installation but plack always redirects to http://localhost:5000/cgi-bin/koha/maintenance.pl
09:49 raj4perl        I'm new to koha and plack
09:49 raj4perl        I need your help with installation
09:49 raj4perl        #Koha
09:46 kf              it's so quiet here today, drojf. we shoudl find some nice things to vote on while it's only the two of us ;)
09:43 drojf           yup
09:42 kf              20 mins?
09:21 drojf           hi kf
09:04 kf              good morning drojf
09:03 drojf           good morning #koha
08:45 kf              good morning #koha
08:18 Oak             kia ora #koha
08:06 francharb       good morning #koha
08:02 wahanui         salut, gaetan_B
08:02 gaetan_B        hello
07:56 raj4perl        any ideas what i might be missing please?
07:52 raj4perl        i'm new to plack and koha and would appreciate any help/pointers
07:51 raj4perl        and when i go to http://localhost:5000/cgi-bin/koha/installer/install.pl, it return 'not found'
07:50 raj4perl        even when i got to http://localhost:5000/cgi-bin/koha/opac-user.pl it redirects back to mantenance.pl
07:50 raj4perl        now when i run 'plackup --reload etc/app.psgi' and load localhost:5000 ... it always redirects to http://localhost:5000/cgi-bin/koha/maintenance.pl
07:49 raj4perl        I've clone koha repo from github and installed it as per INSTALL
07:48 raj4perl        Hello all
07:43 reiveune        hello
07:27 wahanui         que tal, alex_a
07:27 alex_a          bonjour
06:57 cait            morning #koha
06:52 cait            hi bag
06:38 bag             heya cait
06:33 bag             YAY
06:33 huginn          bag: Sent just now: <bag> Happy Birthday!
06:33 bag             @notes paul_p
06:33 huginn          bag: The operation succeeded.
06:33 bag             @later tell paul_p  Happy Birthday!
06:33 bag             ok then
06:33 bag             no paul_p yet to wish him happy birthday!
03:42 * wizzyrea      giggles
03:42 eythian         bittorrent or freenet based?
03:42 wizzyrea        hm
03:40 jcamins         Sort of.
03:40 jcamins         wizzyrea: I'm writing a peer-to-peer ILL module.
03:38 wahanui         "What are you trying to do?" or "What is the goal?"
03:38 wizzyrea        the first question?
03:32 jcamins         I can use the opac-suggestions page for ILL requests!
03:21 wahanui         wizzyrea: I forgot translate.koha-community.org
03:21 wizzyrea        forget translate.koha-community.org
03:21 jcamins         translation is translate.koha-community.org
03:21 wahanui         jcamins: I forgot translation
03:21 jcamins         forget translation
03:21 wahanui         hmmm... translate.koha-community.org is back...
03:21 wizzyrea        translate.koha-community.org
03:21 wahanui         i think translation is done through the pref files
03:21 jcamins         translation?
03:21 jcamins         translate?
03:20 _et             where do i get the .po files?
03:20 _et             hi. i'd like to begin translating Koha into Tamil
03:17 huginn          bag: paul_p was last seen in #koha 4 days, 18 hours, 42 minutes, and 42 seconds ago: <paul_p> good morning #koha !
03:17 bag             @seen paul_p
02:04 jcamins         Hello.
02:04 Oak             *sigh*
02:04 Oak             hellol jcamins
02:04 Oak             jcamins++
02:04 Oak             magnuse++
02:04 * Oak           waves
02:03 jcamins         gmcharlt++
02:01 jcamins         Back to Chrome I go.
02:01 jcamins         It works in Chrome.
02:00 wizzyrea        spectacularly fail-y
02:00 wizzyrea        wow that's spectacular
01:58 jcamins         And I can't get this page to reload.
01:55 wizzyrea        O.o I've not ever seen it act that way
01:53 eythian         that's odd, I note the opposite to both those cases.
01:52 jcamins         It doesn't report javascript errors, and whenever it is open I can't switch tabs.
01:51 jcamins         Definitely not.
01:49 wizzyrea        lulz.
01:48 wahanui         http://i.imgur.com/hVVuP.jpg
01:48 wizzyrea        no?
01:47 jcamins         I do not like firebug.