Time  Nick          Message
01:44 florent       rangi: What could be the value of reporting 2 identical errors for the same bad import entry?
01:46 rangi         none really, sounds like just a mistake
01:48 florent       Thank you. I will  fix that.
01:57 jcamins       Double certainty that it's wrong?
02:07 florent       Double the trouble
02:10 * wizzyrea    feels a little ragey about this bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15840
02:10 huginn        04Bug 15840: major, P3, ---, jonathan.druart, Pushed to Stable , Import borrowers tool explodes if userid already exists
02:15 * Francesca   waves
02:15 wizzyrea      mostly because I have an import file that wasn't generating userid's, and even though it took literally 5 minutes to add that, 1. it's not documented as a requirement and 2. I had to make a change on a thing that's going live right now and that is uncomfortablemaking.
02:16 * wizzyrea    has an unhappy.
03:04 rangi         @wunder nzwn
03:04 huginn        rangi: The current temperature in Wellington, New Zealand is 16.0°C (2:30 PM NZST on April 19, 2016). Conditions: Mostly Cloudy. Humidity: 72%. Dew Point: 11.0°C. Pressure: 30.27 in 1025 hPa (Steady).
06:27 * magnuse     waves
06:35 * cait        waves back and runs off to work
06:47 reiveune      hello
06:47 wahanui       salut, reiveune
06:59 alex_a        bonjour
07:22 gaetan_B      hello
07:24 drojf         morning
07:32 magnuse       @wunder boo
07:32 huginn        magnuse: The current temperature in Bodo, Norway is 5.0°C (9:20 AM CEST on April 19, 2016). Conditions: Partly Cloudy. Humidity: 65%. Dew Point: -1.0°C. Windchill: 0.0°C. Pressure: 29.62 in 1003 hPa (Steady).
07:32 magnuse       @wunder marseille
07:32 huginn        magnuse: The current temperature in Marseille, France is 11.0°C (9:00 AM CEST on April 19, 2016). Conditions: Clear. Humidity: 58%. Dew Point: 3.0°C. Pressure: 30.09 in 1019 hPa (Steady).
07:33 drojf         @wunder berlin, germany
07:33 huginn        drojf: The current temperature in Berlin Tegel, Germany is 10.0°C (9:20 AM CEST on April 19, 2016). Conditions: Mostly Cloudy. Humidity: 58%. Dew Point: 2.0°C. Pressure: 30.09 in 1019 hPa (Steady).
07:33 drojf         @wunder thessaloniki
07:33 huginn        drojf: The current temperature in Thessaloniki, Greece is 21.0°C (10:20 AM EEST on April 19, 2016). Conditions: Mostly Cloudy. Humidity: 60%. Dew Point: 13.0°C. Pressure: 29.98 in 1015 hPa (Steady).
07:35 cait          morning all
07:35 cait          Joubu: good poitn about the password - thx for sending the e-mail anyway!
07:38 magnuse       done translating nb-NO for 3.22.6 \o/
07:39 cait          german seems to be done - it feels a bit suspicious
07:43 * drojf       is very trusty
07:43 LibraryClaire morning
07:43 drojf         hi LibraryClaire
07:43 LibraryClaire hi drojf :)
07:48 cait          drojf: heh
07:48 cait          hi LibraryClaire :)
07:56 magnuse       cait: why suspicious?
08:04 eythian       German always sounds suspicious.
08:05 eythian       Like they've left towels on a beach chair or something.
08:06 liw           eine kleine Tasse Schokoladenschnitzel mit Bananenkartoffeln und Kabelsalat auf def Hauptbahnhof, bitte
08:20 cait          lol
08:26 drojf         later #koha
08:33 LibraryClaire hi cait :)
08:33 LibraryClaire sorry - impromptu meeting occured
08:34 cait          @later tell drojf hm thinking - should we add something about technical requirements? (bring your own laptop, need admin perm to install kohadevbox?)
08:34 huginn        cait: The operation succeeded.
08:34 cait          could have written that in german *confusedbrain*
08:44 LibraryClaire hehe
09:47 ashimema      that sounds tasty
09:51 LibraryClaire tasty?
09:53 magnuse       "eine kleine Tasse Schokoladenschnitzel mit Bananenkartoffeln und Kabelsalat" from liw, i presume
09:54 LibraryClaire aah yes :)
09:56 ashimema      :)
09:56 * liw         hides in shame
09:56 ashimema      hehe
10:00 LibraryClaire I'll stay clear of the Kabelsalat I reckon ;)
11:11 cait          khall: around?
11:11 khall         yo
11:11 cait          bug 9393
11:11 huginn        04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9393 minor, P5 - low, ---, kyle, Failed QA , Add note to circulation.pl if borrower has pending modifications
11:11 cait          more concerned about the second point - first is not a blocker (as I wrote ;) )
11:12 cait          But something else: You might also not be able to see the entry for the patron because of IndependentBranchesPatronModifications - not sure how to handle this. Maybe we should only show the link of logged in branch and staff branch match?
11:12 khall         ok, I think I can do something about the second part.
11:12 cait          i thought maybe it's easy, maybe not, so i noted it
11:12 cait          perhaps owen has an idea at some point (for the accordeon) but we can leave it for sure
11:13 cait          mostly was interested in you looking into the 2 questions and see what could be done
11:13 cait          or not
11:13 cait          because it hink it will be the first 2 things people might notice
11:13 cait          hope that makes sense
11:15 cait          early mornign qa might not be my best :)
11:16 khall         heh ; )
11:46 oleonard      Hi #koha
11:51 druthb        oleonard!  :D
11:53 oleonard      It's nice to have you around druthb. I feel like even though you don't work on Koha, if there were some kind of Koha-related Kaiju attacking the city you would spring into action to help us form a giant robot.
11:56 oleonard      https://www.youtube.com/watch?v=EMgsAD3D948
11:57 druthb        :)
11:57 druthb        I would, yes.
11:59 cait          lol
11:59 cait          oleonard++ :)
12:28 tcohen        morning
12:31 cait          oleonard, khall: could you take a look at bug 11317 and blou's question there?
12:31 huginn        04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11317 enhancement, P5 - low, ---, philippe.blouin, Patch doesn't apply , Add a way to access files from the intranet.
12:31 khall         k
12:32 cait          i think it would be a cool feature
12:32 cait          to have a safe access to the print notice files on the server
12:33 oleonard      Seems more like a tool to me, since the log viewer is considered a tool. But I have just now looked at this bug for the first time so I may not fully understand.
12:34 cait          i think tool too :)
12:34 cait          but i don't want them to have to change things once again... if you all disagree
12:34 cait          oleonard: probably best to not start reading at the top
12:39 khall         cait: didn't notice your convo, but I had the oposite thought
12:41 oleonard      khall: Why?
12:42 khall         I think from a usability/permissions/technical standpoint this should probably be considered a report. This script does not alter data, but only makes it accessible. This makes it technically a "report" to me.
12:42 khall         Furthermore, it seems likely that the librarians needing to access this data are the same ones who would run other reports, and not necessarily be the same ones running tools. This to me is another reason to move it back to the reports page.
12:42 khall         That's just my opinion of course
12:43 khall         if it gets it's own permission, it's really a coin toss
12:43 khall         but I think the latter argument would still apply
12:43 tcohen        hi cait khall
12:43 khall         mornin nengard!
12:43 khall         mornin tcohen!
12:43 oleonard      What are the kinds of logs which might be viewed by this tool?
12:44 nengard       khall!!!!!!!
12:44 wahanui       khall is volunteering to come over and fix it for you, it seems. ;)
12:44 nengard       :)
12:44 khall         lol
12:44 khall         oleonard: what came to my mind were the "print" files for overdues, etc
12:44 khall         basically cli report output
12:44 khall         but I can't claim to know that was the intention
12:45 oleonard      Overdues aren't considered a report. Notices are under tools. Is there output from reports which would also be covered?
12:46 blou          oleonard: it gives access to files.  Any files you want to give access to.
12:46 drojf1        after having read the bug report for ~30 seconds, what makes it a report? does it technically go through the creation process of a report? (i assume not, if it is log files? or its another kind of logfiles)? if not it sounds closer to the downmload database tool to me than to a report
12:46 blou          our users use it for access to the print notices (hold, overdues...)
12:47 drojf1        ok that sounds reportdish. i thought of stuff like apache log
12:47 drojf1        *reportish
12:47 cait          khall: now we disagree :)
12:47 cait          oleonard: files generated on the server
12:47 blou          I could give access to apache logs.
12:47 blou          I -> It
12:47 drojf1        give it an extra permission and flip a coin
12:48 cait          hi blou
12:48 drojf1        or does it really matter?
12:48 cait          :)
12:48 blou          hello Cait!
12:48 oleonard      Are there any kinds of files which might be created by existing reports which would be accessed by this feature?
12:48 blou          Action_logs are through Tools
12:48 blou          although they sound reportish
12:48 blou          :)
12:48 nengard       i think it's the 'log viewer' that's the tool
12:49 nengard       the fact that you can 'view' the logs is toolish :) hehe
12:49 blou          This feature can give access to any directory specified in koha-conf
12:49 drojf1        lol
12:49 cait          i like the idea of having a separate perm
12:49 cait          it will require stup on the server for the directory i think
12:49 drojf1        that sounds not reportish but dangerous :)
12:50 drojf1        it definitely needs a separate permission
12:50 drojf1        regardless what it is labelled
12:50 blou          i need the separate perm for my client.  Specific requirement...
12:50 oleonard      I'm firmly in the "Tools" camp.
12:50 cait          technically you could add a suppermission to reports - the structure is there with run/execute below reports...
12:50 cait          but i am still a tools person
12:50 blou          dangerous: with great power....
12:50 drojf1        make a whole new module out of it, called reportish tools!1
12:50 drojf1        sorry
12:51 cait          drojf1: go and stand in the corner heh
12:51 khall         I'd say maybe tools is better for simplicity at this point
12:51 blou          dish, tools... gets me to erfworld
12:51 drojf1        team tools
12:52 cait          #startvote should the access file feature be under tools or reports? (tools,reports)
12:52 blou          I'm team QA.  Whatever gets it signed :-)
12:52 cait          oooh
12:52 cait          only works in a meeting
12:52 drojf1        lol
12:52 drojf1        lets have a short meeting about it
12:52 drojf1        :P
12:52 cait          well
12:52 cait          thre is a dev meeting this wednesay
12:52 cait          but i was hoping to we could agree on something :)
12:53 cait          khall: are yo strictly opposed to tools?
12:53 drojf         do we really want to vote there if that is a tool or report? we don't have real things to do? :P
12:53 cait          that was just my way of reminding of the meeting
12:53 cait          because i got that on my todo list today :)
12:53 khall         cait: no I am not, either way is really fine with me
12:53 drojf         oh. that worked very well!
12:53 drojf         cait++
12:53 khall         bikeshedding--
12:54 drojf         but i want green :(
12:54 cait          drojf: i lost track of your opinion
12:54 drojf         green is tools. and heads if we flip a coin
12:54 kidclamp      there should be a new category, reools
12:54 blou          drools
12:54 drojf         i like drools
12:55 drojf         excellent!
12:55 cait          kidclamp: you can stand in the corner with drojf for making up new modules :P
12:55 kidclamp      drolls++
12:55 liw           drojf, biff
12:55 oleonard      You guys are the worst :P
12:55 * kidclamp    hangs head in shame
12:55 cait          you missed us, right?
12:55 * kidclamp    scuttles off to create new bugs
12:56 cait          blou: do you think you got an answer?
12:56 blou          cait: yeah, drools
12:56 drojf         brb
12:57 blou          cait: question: a new patch, or this change invalidate a lot of thing which will need retesting, thus a squash is ok ?
12:57 cait          hm let's do soemthing in the middle
12:57 cait          a follow-up?
12:57 wahanui       a follow-up is much easier to test than the first patch.
12:57 tcohen        ah c'mon
12:58 blou          ?!
12:58 tcohen        we still don't have master packages!
12:58 cait          tcohen: ?
12:58 tcohen        sorry, private rant
12:58 cait          blou: a new patch with the last changes for easy review
12:58 cait          5 patches then on the bug
12:58 cait          4 now
12:58 cait          not sure how to explain :)
12:59 blou          ok, just a patch.  No squash.  Ok.
12:59 cait          makes it easier to review i think
12:59 blou          Although someone a Sha1.  So that won't fix it
12:59 cait          if it moves around... we can still squash
13:00 cait          yeah, rebae what#s there i'd say
13:00 cait          and then change on top
13:00 blou          cait: thanks.  Will do today
13:04 drojf         cait: yes there will be some info about tech requirements for the newbies, but i think that still has time
13:04 drojf         but i wanted to send it to the list finally :)
13:05 drojf         (about your @later)
13:08 drojf         did you choose a colour why i was gone? it's so quiet suddenly
13:09 oleonard      Yes drojf we chose "bleen"
13:24 drojf         oleonard: i think we have to bring that up at the dev meeting
13:25 oleonard      In all seriousness we should have a style guide that includes guidelines for use of color.
13:25 oleonard      Then we have a framework for discussions of changes, like the use of bleen.
13:35 francharb     bleen? blue green?
13:36 francharb     is it like greige?
13:36 francharb     grey beige
13:36 francharb     hi oleonard, hi all ;)
13:36 oleonard      francharb: The definition of bleen is slated for a discussion at the color meeting. We've blocked out 90 minutes for that issue.
13:37 francharb     ahah
13:37 francharb     it's definitively an important one
14:10 oleonard      I don't understand what problem Bug 14695 solves.
14:10 huginn        04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14695 enhancement, P5 - low, ---, kyle.m.hall, Needs Signoff , Add ability to place multiple item holds on a given record per patron
14:11 oleonard      Why would I want to say, "For this item type I want to allow 3 holds per title?"
14:11 oleonard      What I want to say is "For this item type I want to allow multiple holds, period." And inherit the hold limit.
14:12 oleonard      Not that what I want is what everyone wants.
14:12 oleonard      Which is why I ask: What problem does it solve?
14:12 oleonard      khall?
14:12 wahanui       khall is volunteering to come over and fix it for you, it seems. ;)
14:12 khall         sup?
14:12 wahanui       everything.
14:12 oleonard      I have questions ^^
14:14 khall         oleonard: I don't have the best knowledge, but it's a huge request from lots of libraries. I think maybe for teachers needing many copies, or being able to specify multiple volumes where something like an encylopedia is cataloged with all volumes on one record
14:15 khall         probably the latter is the more common reason
14:15 oleonard      That's the kind of need I see too, but I don't understand how defining a specific multi-hold count is helpful.
14:15 oleonard      How many volumes does any particular multi-volume set have?
14:16 khall         it's just to avoid general hold spamming, generally the same reason we have hold limits in general. it's just hold limits for a specific record
14:24 cait          kidclamp++ nice blog post
14:24 oleonard      cait: ?
14:25 cait          http://bywatersolutions.com/2016/04/19/koha-3-22-custom-sound-alerts/
14:28 kidclamp      thanks cait
14:49 oleonard      Bug 15456 makes me want to re-indent all the things.
14:49 huginn        04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15456 enhancement, P5 - low, ---, jweaver, Signed Off , Fix tabs and inconsistent indentation in smart-rules.tt
14:56 pianohacker   oleonard: it was oddly cathartic
14:56 oleonard      pianohacker: That's how I felt when making the Bootstrap templates for the OPAC
14:57 pianohacker   I definitely believe that
14:57 pianohacker   how is the staff client work going?
14:58 oleonard      Slowly :)
14:59 oleonard      Unfortunately I ran into an issue where you can't exclude Bootstrap's forms CSS when doing a custom build, so I'm trying to figure out if I should try for a workaround or just do a bunch of overrides to keep things looking correct.
15:02 blou          Got a question about koha-qa
15:03 blou          FAIL	  valid		Name "Cache::RemovalStrategy::LRU::FIELDS" used only once: possible typo
15:03 tcohen        blou: I recall Joubu filled a bug for that
15:03 blou          Anyone could cue me onto what is causing that (and its friends) ?
15:03 blou          ok
15:04 blou          so it IS unrelated to my patch, then ?
15:06 cait          there is a bug in PQA for that
15:06 cait          or  more a patch
15:06 cait          you can ignore it for now i think
15:07 cait          blou: don't forget the atomicupdate for the perm :)
15:08 blou          already in
15:08 cait          hm not seeing it
15:08 cait          was sneaking a look at your new patch
15:11 cait          blou: it's missing the atomicupdate - the new patch
15:11 cait          blou: for existng installations
15:15 blou          arrrrgh.  I forgot the git add !!
15:15 cait          heh
15:15 cait          you are not the first
15:15 blou          I even TESTED the atomic update throught the webinstaller.  I was so sure all was ok.  Sigh....
15:21 pianohacker   also, hi all
15:22 blou          cait: Ok, NOW i sent all the files.  Only took my 4 tries...  I hope it's the right versions of the files... (blou /crying)
15:22 * cait        sends cookies
15:23 * oleonard    sends cookies to everyone whose patches he has failed today... Feeling like an ogre.
15:23 cait          you are doing great work, have some cookies
15:27 cait          the qa queue is exploding
15:27 * cait        is scared
15:27 drojf         later #koha
16:12 reiveune      bye
16:16 oleonard      khall: What is the "Holds to place (count)" field for in the staff client? (Bug 14695)
16:16 huginn        04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14695 enhancement, P5 - low, ---, kyle.m.hall, Needs Signoff , Add ability to place multiple item holds on a given record per patron
16:17 khall         oleonard: in the circ rules, I should have specified that ; )
16:17 gaetan_B      bye
16:17 oleonard      I don't understand. Does setting that value when placing a hold in the staff client do something?
16:18 khall         it limits the number of holds a given patron can place on a single record. The default is 1 to replicate existing behavior
16:19 oleonard      So when placing a hold you can redefine the limit that patron can placed, overriding the setting for that patron category/item type defined in circ rules?
16:20 bag           morning
16:21 khall         no, that's still in effect as well. You could have the hold limit be 5, and the hold per record limit be 3
16:21 khall         so the patron can place 5 total holds, and only 3 on any given record
16:22 oleonard      But why is there a drop-down on the 'place hold' screen where I can choose a number for "Holds to place (count)?"
16:23 khall         for convenience when placing multiple record level holds, that was a request by Chris iirc
16:23 oleonard      what does it do?
16:23 khall         it places the number of record level holds you specifiy in the pulldown
16:24 khall         nick and the qa team hashed out a list of change requests a while back and I implemented them
16:24 khall         that was one
16:24 khall         @kidclamp++ for that
16:24 huginn        khall: I've exhausted my database of quotes
16:25 oleonard      Oh I see it's for getting multiple copies of something, unconnected to item-level holds.
16:26 khall         yep!
16:26 oleonard      There's more going on here than is described in the test plan.
16:26 khall         my bad, I missed that bit
17:49 huginn        New commit(s) kohagit: [SIGNED-OFF] Bug 15113: koha-rebuild-zebra should check USE_INDEXER_DAEMON and skip... <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=997ad166c6ea53d47e3e15e7720d63da9f3b0a80>
17:49 oleonard      It's fascinating to me that browser technology has advanced to the point where Bug 6815 could be a workable feature now.
17:49 huginn        04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6815 enhancement, P5 - low, ---, mtompset, In Discussion , Capture member photo via webcam
17:50 tcohen        oleonard: hehe
17:50 tcohen        sure!
17:50 tcohen        bag: thanks
17:50 oleonard      Maybe nengard should resurrect Bug 1937
17:50 huginn        04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1937 enhancement, P3, ---, gmcharlt, CLOSED WONTFIX, Scan barcode with webcam
17:51 nengard       hmm
17:52 nengard       anyone can resurect that if they want :)
17:52 tcohen        :)
18:19 huginn        New commit(s) kohagit: [SIGNED-OFF] Bug 16190: Enable the indexer daemon by default <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=98f551faec2627742b0b1d5b72e1791b4451b401>
18:20 oleonard      Interesting that submitting a blank form for a circulation rule gives you unlimited checkouts allowed but zero for a loan period.
18:21 oleonard      Zero checkouts allowed for an infinite time would be great.
18:37 tcohen        users++
18:59 oleonard      Bye #koha
19:18 tcohen        bye #koha
19:54 rangi         morning
20:03 cait          morning rangi
20:23 rangi         hmm is master currently broken for others?
20:23 rangi         DBIx::Class::ResultSet::next(): Unknown column 'me.archived' in 'field list' at /home/vagrant/kohaclone/Koha/Objects.pm line 150
20:23 rangi         im getting that at
20:23 rangi         http://localhost:8081/cgi-bin/koha/admin/preferences.pl
20:24 rangi         I think it might be just my db
20:24 rangi         out of sync with the schema
20:27 cait          hm me?
20:27 wahanui       go to bed
20:27 cait          archived.
20:27 cait          no idea where this could be
20:27 rangi         super useful error message!
20:27 rangi         yeah exactly
20:28 cait          rangi: currency
20:28 cait          or currencies
20:28 cait          http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=installer/data/mysql/kohastructure.sql;hb=98f551faec2627742b0b1d5b72e1791b4451b401#l774
20:28 rangi         hmm
20:29 rangi         so there must be a patch that removes that
20:30 cait          hm or adds?
20:30 rangi         or adds it but not properly
20:30 rangi         because i just ran the update
20:31 rangi         lemme check the updatedatabase
20:31 rangi
20:33 cait          hm can help search in a bit - brb
20:34 rangi         fixed
20:47 cait          ah cool
20:47 cait          what was it?
20:48 rangi         probably another patch had moved the version number higher than that
21:11 rangi         hmm
21:12 rangi         i think Dianna might have misunderstood
21:12 cait          hm?
21:12 rangi         the pin thing
21:12 rangi         reply to you and jonathan
21:12 cait          oh?
21:13 cait          hm email program is unwilling to open.
21:13 rangi         its on the list
21:13 rangi         she says they use it, but I dont think any code is there to use it
21:13 cait          depends on how they use it - i tried today
21:13 rangi         also, she has misunderstood the storing in clear text bit too
21:13 cait          it stores fine
21:13 cait          i don't have her email yet it seems
21:14 rangi         https://lists.katipo.co.nz/pipermail/koha/2016-April/045242.html
21:14 wizzyrea      I think she's confused by the password
21:15 wizzyrea      they may label the regular password "pin" in their installation
21:15 cait          can someone else try and clear things up?
21:15 eythian       there's something we have that causes all errors and warnings to include a stack trace. That would make tracking down those issues a lot easier, I'm sure it's something that could be hooked into debug mode. (I don't know how it's actually done, but it's a lifesaver.)
21:15 rangi         yeah, i dont think she is talking about teh same thing, the password option in extended attributes is totally stored in plain text and it's a really bad idea and should be removed
21:15 eythian       (by "those" I mean that error from scrollback :)
21:15 cait          i tested it today - i can confirm
21:15 wizzyrea      I don't understand the purpose
21:16 wizzyrea      of the passwords there
21:16 wizzyrea      why were they added originally?
21:16 rangi         eythian: yeah debug level i think
21:16 cait          someone said as an additional login on the bug report
21:16 cait          but never fully implemented
21:16 cait          i kind of thought it was for another application maybe - or a pin... but apart from storing and editing it doesn't seem to do anything
21:18 rangi         yeah
21:18 rangi         i dont have the brainspace to explain that
21:19 wizzyrea      I've got it
21:23 cait          thx!
21:23 wizzyrea      oh jeez she's from Salina. That's 30k from my home town.
21:23 wizzyrea      how funny
21:23 wizzyrea      we are talking about the tickbox in borrower attributes for "password" right?
21:26 rangi         yeah i think so
21:26 wizzyrea      done
21:28 cait          wizzyrea++
21:38 wizzyrea      She says "You are right I was thinking of the PIN in Registration. Thanks"
21:41 cait          cool