Time Nick Message 23:59 dcook I thought that was a uniquely GH thing? 23:59 dcook rangi: how are you sending pull requests? 23:43 mtj_ aah, ok - nice idea 23:43 wahanui module maintainers is still of interest to me.. look like a number of people have now volunteered.. 23:43 rangi module maintainers 23:42 mtj_ hey rangi, what are the MM branches used for, in git? 23:28 mtj_ yes, or that too :0) 22:51 rangi yep 22:47 wizzyrea probably easiest just to ask bywater to give it a bit more RAM 22:45 mtj_ rangi, wizzyrea - that might do the trick... ^^ 22:44 mtj_ hmm.. even a 1gig VM is only $120, at digital-ocean -> https://www.digitalocean.com/pricing/ 22:42 tcohen hi eythian 22:42 mtompset Well, I cloned remotely, and am trying rsync's. ;) 22:42 mtj_ $ git clone https://github.com/Koha-Community/Koha.git 22:41 mtj_ mtompset: perhaps cloing via http might help? 22:40 mtj_ ah, ok... yeah, then your problem might still exist... :/ 22:39 mtompset But I think it is my ISP. 22:39 mtompset Thanks for that idea. 22:39 mtj_ ...if you get stuck, and there's no one about on #irc 22:38 mtj_ https://github.com/Koha-Community 22:38 mtj_ mtompset: you can always use the kc.org/koha repo on github, as a backup... 22:32 huginn eythian: The operation succeeded. 22:32 eythian @later tell magnuse should it? I just noticed it when adding more mappings to the ES stuff. 22:31 eythian hi 21:22 cait :) 21:20 rangi i might get aleisha to fix that on tuesday 21:19 rangi i think the history is maybe a bit out of date 21:19 tcohen \o/ 21:19 cait yay! 21:18 * gmcharlt notes that Viktor is now the newest dev to have a patch accepted 21:17 gmcharlt yeah 21:17 tcohen can we pay for the whole year at once? 21:16 mtompset ah, very comparable to digital ocean. 21:14 wizzyrea that's the smallest they offer now, afaict 21:14 wizzyrea 2048 21:14 mtompset A lot of deltas to resolve, but I think this external git clone worked okay. :) 21:14 tcohen how much RAM wizzyrea ? 21:13 gmcharlt yeah, that's easily within the realm of a quick donation campaign to fund 21:13 wizzyrea which seems not spendy to me. 21:13 rangi right 21:13 wizzyrea it's like $216/yr for kohacommunity 21:12 gmcharlt rangi: thanks 21:12 rangi pushed to master if you push to master 21:12 gmcharlt wizzyrea: yeah, and SSD-backed I/O would be nice 21:12 rangi to a MM owned one 21:12 gmcharlt as in, directly to master, or directly to an MM-owned repo? 21:12 rangi after passed qa 21:12 wizzyrea moving git to linode might actually be cost effective, they're not that expensive 21:12 gmcharlt workflow impliactions? 21:11 tcohen great 21:11 rangi tcohen: there is a new status on bugzilla now "pushed by module maintainer" 21:07 huginn New commit(s) kohagit: Bug 12336 - [SIGNED-OFF] Author of reserved book is not displayed in opac-user.pl <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=5c1599c925da726752a3565b6e11ce72152c1dba> / Bug 12280 - "Others..." reason for suggestions not showing in Bootstrap OPAC <http://git.koha-community.org/gitweb/?p=koha.git;a=commitdiff;h=1346bd250ed70ed429267b4dca2a0c1f90921a60> 21:02 rangi cya Brooke 21:02 Brooke cheers mates! 21:01 mtompset okay... here we go the long way around... git clone on a remote vm, and then rsync. ;) 20:56 rangi that sounds likely then 20:56 mtompset I was having issues with a sudo apt-get update! 20:56 mtompset My cursed ISP? Perhaps. 20:55 rangi i suspect something on your end then, and that might be what is jamming up the server too 20:54 mtompset clone failed for me. 20:54 gmcharlt mtompset: rangi: the clone worked for me 20:54 rangi ill try to do that tonight 20:54 rangi righto 20:53 tcohen i hope i have them next week 20:53 tcohen rangi: could you drop me an email with what is needed to get those virtual servers ready for testing master? 20:48 Brooke 11 mins til COB brah 20:47 rangi any bywaterians about? 20:47 Brooke bye magnus! 20:43 rangi cya magnuse 20:43 tcohen you too magnuse 20:43 * magnuse wishes #koha a good time of the day 20:42 tcohen fetch worked here 20:40 rangi (and didnt before) 20:40 rangi fetch worked fine 20:39 gmcharlt rangi: mtompset: I've bounced git-daemon, and I'm trying a fresh clone 20:39 magnuse :-) 20:39 * Brooke waves back at Magnus! 20:39 * magnuse waves to Brooke 20:38 rangi might be rackspace 20:38 tcohen heh 20:38 rangi dunno if its a linode, its a bywater one 20:38 tcohen the linode server? 20:38 rangi we might want to do an appeal for some dollars to up the vm to the next available size 20:38 mtompset It only has 512MB?! 20:38 rangi it only has 512MB 20:37 rangi out of memory 20:37 mtompset OOM? 20:37 rangi tcohen: ill try again :) 20:37 tcohen I haven't chris 20:37 rangi if i gave it more connections it would OOM 20:37 rangi its not ooming, but its maxed out its available connections 20:36 rangi someone/something is pounding it 20:36 rangi mtompset: its overloaded 20:36 mtompset All I wanted to do was re-test the git install instructions under 14.04 20:36 rangi tcohen: off topic, did you get my pull request (just checking i sent it right) 20:35 mtompset The next 3 are another. 20:35 mtompset The first line is an example of one error. 20:35 mtompset fatal: index-pack failed 20:35 mtompset fatal: pack has bad object at offset 3071120: inflate returned -3 20:35 mtompset error: inflate: data stream error (invalid distance too far back) 20:35 mtompset fatal: protocol error: bad line length character: R▒|▒0 KiB/s 20:33 mtompset after the objects are compressed. 20:33 mtompset during receive. 20:33 mtompset git clone. 20:33 tcohen at which stage mtompset 20:30 mtompset I keep getting protcol error messages. 20:30 mtompset Is anyone else able to git clone koha? 20:29 Brooke muy bueno! 20:29 tcohen yay! people from colombia submited a proposal for presentation 20:29 mtompset Is it meeting time, or can I ask a question? :) 20:28 mtompset Greetings, Brooke. 20:28 tcohen hi Brooke mtompset 20:28 Brooke hi Mtompset and Tcohen 20:28 mtompset Greetings, #koha tcohen 20:24 Brooke oh Waha, why can't you be Zoia? 20:24 wahanui Don't go, Brooke. Stay a while. Stay forever. 20:24 Brooke good night! 20:24 Viktor It's a bit past bedtime here though so I'll say goodbye for now. 20:23 Viktor :) 20:23 gmcharlt you're welcome 20:23 Viktor Thanks for the help. 20:23 Viktor I guess I'll still poke around a bit with it but more to learn than actually hoping to get it solved. 20:22 Viktor Great! 20:21 gmcharlt Viktor: I've updated the bug with a note that hopefully will help whoever tackles writing a patch for it 20:18 Viktor I thought I'd take a look around since it might be small enough a problem for me to grasp but it's a bit over my head anyway. 20:17 Viktor It annoys the librarians I work with quite a bit. 20:16 Viktor Exactly. 20:15 gmcharlt Viktor: indeed, I don't see any particular reason for it to do that at all; it seems like it would be sufficient for it simply to reduce the loan period with each checkout, individually 20:14 Brooke o/ 20:13 gmcharlt Viktor: ick. yeah, munging the duedatespec element like that isn't ideal 20:08 Viktor cait Yep - there is a clear button. But 10067 is about "decreaseLoanHighHolds" sticking a date in the box that stays there until you manually clear it. Which gives all subsequent issues shorter loan period until you remember to clear. 20:05 wahanui gmcharlt: I forgot undo 20:05 gmcharlt wahanui: forget undo 20:05 gmcharlt yeah, there is 20:05 wahanui undo is complete 20:05 cait undo... 20:05 cait but i understand it like gmcharlt as well 20:05 cait Viktor: there hsould be a clear button to undu the specified due date 19:41 Viktor I'll verify it and then look further. 19:41 Viktor Hm. Too bad then. Thanks gmcharlt 19:41 gmcharlt in other words, if you want the specified due date to be sticky for /all/ loans that the workstation makes that day 19:40 gmcharlt Viktor: I beleive that session in this context means "login session" 19:35 Viktor I'm having a look at 10067 that we would like resolved and I'm starting to think that the problem is just that the specified due dates are not cleared as they should. 19:33 Viktor In circ - should "specify due date" clear between every issue (but doesn't)? Otherwise I don't understand what "Remember for session" is for. 19:18 pug I was wondering if there is a obvious answer to - which drupal module provides the best integration with koha - opac module or the eXtensible Catalog module(s) 19:17 pug hi cait 19:09 tcohen bye #koha 18:37 cait :) 18:37 khall I can also agree with your last comment 18:37 khall oohh, I like the way you think! 18:36 gmcharlt khall: done 18:26 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11801 minor, P5 - low, ---, kyle, In Discussion , In transit hold items incorrectly labeled as "Waiting to be pulled" on request.pl 18:26 khall gmcharlt: can you weight in on bug 11801? 18:19 * tcohen is puzzled 18:15 tcohen gmcharlt: i was thinking about that actually 18:13 gmcharlt tcohen: one thought ... adding a test of ::merge() to Search.t, and seeing if it passes on your dev platform 18:06 gmcharlt seems likely 18:05 jcamins (^guess) 18:05 jcamins Predates SimpleSearch? 18:03 tcohen why isn't C4::AuthoritiesMarc::merge using SimpleSearch? 18:03 jcamins Other than that Perl 5.whatever changed all the things. 18:03 jcamins Okay, so, I have no idea what the problem is. 18:02 gmcharlt jcamins: no 18:02 jcamins tcohen: never mind, then. 18:02 tcohen I don't 18:01 jcamins gmcharlt: do you? 18:01 jcamins tcohen: you have DEBUG enabled, don't you? 18:01 jcamins Wait, wait, wait. 18:00 jcamins Well, tell you about. 18:00 jcamins Yeah, I was going to report that too. 17:59 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12151 enhancement, P5 - low, ---, gmcharlt, Needs Signoff , remove remaining uses of the Perl smartmatch operator 17:59 tcohen there's also bug 12151 17:58 tcohen heh, thanks for filling that bug jcamins 17:58 jcamins Except not on bugzilla. 17:57 jcamins Hey, this has already been reported many times. 17:57 jcamins Useless use of '\'; doesn't escape metacharacter '(' at /home/jcamins/kohaclone/C4/AuthoritiesMarc.pm line 856 17:57 jcamins The latest version of Perl changed the way regular expressions work. 17:56 gmcharlt tcohen: yep, I'm running Debian 7 17:56 jcamins Okay, I figured it out. 17:56 tcohen Debian 7? 17:56 gmcharlt tcohen: second test also works for me 17:55 jcamins It lost the connection to MySQL. I got it working again, sort of. 17:54 jcamins tcohen: I'm using Plack. 17:53 tcohen jcamins: maybe you've been hit by apache configuration issues? 17:52 gmcharlt tcohen: now trying with unlinked authorities 17:52 gmcharlt tcohen: works for me (with the 12295 patch) for authorities that are linked to bibs 17:51 jcamins I withdraw my objections to saying that using Ubuntu 14.04 might be premature. 17:50 jcamins tcohen: main page, or anything else. 17:50 tcohen nothing like? 17:49 jcamins Actually, I take that back. Nothing works. 17:47 jcamins I confirm the bug. 17:46 tcohen mine werent 17:46 gmcharlt tcohen: what I'm doing now is specifically testing merging authorities that are linked to bibs 17:45 * tcohen was about to push that one 17:45 * gmcharlt tries again 17:44 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12295 critical, P5 - low, ---, kyle, Passed QA , Javascript error when merging authorities 17:44 gmcharlt was working OK when I tested the patch for bug 12295 17:44 gmcharlt haven't seen that before 17:44 tcohen http://snag.gy/ykity.jpg 17:44 tcohen and boom 17:43 tcohen i created two personal name authorities and tried to merge 17:43 gmcharlt tcohen: yep 17:38 tcohen is anyone available for a quick test on a master setup?¿ 17:32 cait hi tcohen 17:31 tcohen hi cait 17:29 cait hi gmcharlt :) 17:28 gmcharlt hi cait 17:26 cait hi #koha 17:16 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12328 normal, P5 - low, ---, oleonard, NEW , report actions don't work in Chrome 17:16 oleonard Oooh, just ran into Bug 12328. I'll have to eat my words about not being able to reproduce it. 16:57 mjk anyway. i'm shuttng down to start my desktop upgrade. see you guy in about 30 minutes. 16:55 mjk or will config files need tweaking? 16:55 mjk also, will the upgrade be as simple as upgrading the packages then runninh koha-update? 16:55 oleonard That advice is usually given about .0 releases 16:54 mjk so the consensu is wait till version 3.16.1 is out? 16:53 mjk hmm. 16:53 druthb gmcharlt++ # he knows why. 16:50 mjk just about to burn the dvd a reboot for install 16:50 mjk getting ready to upgrade my home linux box to mint 17, though. 16:44 mjk we don't really have a testing server 16:44 mjk for a few weeks 16:44 mjk the new marc frameworks would be nice, but i can live without them 16:44 mjk that's what i was thinking 16:43 gmcharlt though 3.16.0 is certainly good enough to test 16:43 gmcharlt mjk: I'd recommend waiting until 3.16.1 later in June 16:43 gmcharlt it appeared, as if by magic 16:43 mjk would it be too soon to upgrade my club library's production server 16:43 gmcharlt :) 16:42 mjk i just notice there's a new version of koha out 16:42 mjk hey there. 16:34 thd Ok 16:34 jcamins thd: I'm not discussing this. 16:33 thd jcamins: I think that we should be able to hold KohaCon in places where the local laws about even unintended offence can be so severe that you would prefer the home country authorities be contacted and not the local ones. 16:31 thd I think the issue could be fixed with a couple of qualifying words. 16:30 thd jcamins: Refusing would also be wrong. 16:30 jcamins thd: if an organizer *ever* refused to contact the authorities when a participant felt they needed legal redress, I would sincerely hope that every single person at that conference would walk out. 16:29 thd oleonard: The support language is the most troubling in case KohaCon would be held somewhere where an inappropriate remark brought to the intention of authorities could lead to an overzealous prosecution with the death penalty or something otherwise disproportionate for offending the local authorities. 16:27 jcamins oleonard: exactly. 16:26 oleonard And what's all this about somebody suing somebody and everyone's afraid to talk about it? 16:26 thd jcamins: You are exactly right. 16:25 jcamins That makes having the reminder all the more important, not less important. 16:25 thd I recognise the purpose. The fact that some people really need the reminder scares me. 16:25 oleonard ...and help folks realize that if they are the victim of inappropriate conduct that they will be supported by the organizers 16:24 gmcharlt and the existence of it can help folks realize that there are circumstances where their behavior may be unwelcome, and to learn why and how to regulate it 16:23 gmcharlt a code of conduct signals that the community and its events are welcome to all 16:23 thd The bigger problem in the case of Richard Stallman quoting something inappropriate is that he did not realise that even quoting it now would be inappropriate. 16:23 gmcharlt thd: prevent? no. Reduce the chances? yes 16:21 thd No policy will prevent people making mistakes without realising it. Richard Stallman made a much smaller mistake but still a problematic one quoting historical usage at the LibrePlanet conference organised by FSF. 16:18 oleonard /also-remember-that-time-i-compared-open-source-software-to-terrorism/ 16:15 oleonard /2014/06/02/apoligy-i-made-a-mistake-and-i-literally-cant-apologize-to-save-my-life/ 16:14 gmcharlt http://stephenslighthouse.com/2014/06/02/apology-i-made-a-mistake-and-i-cant-fix-it/ 16:14 thd oleonard: Maybe the later. I do not have the correct query term. 16:14 gmcharlt http://www.attemptingelegance.com/?p=2420 16:13 gmcharlt thd: one moment 16:13 gmcharlt that tag didn't really get uptake 16:13 oleonard Censored online, or you didn't find anything with that tag? 16:11 thd slef: Can you explain #slutgate2014 to me? It seems to have been censored online 16:03 * gmcharlt will do so 16:03 slef Can someone add those links to the meeting wiki page, please? 16:03 * gmcharlt engages in violent thumb-wrestling with himself 16:03 wahanui the problem is it's human beings doing it. Rebuild your indexes. 16:03 slef wahanui: what is the problem? 16:02 wahanui Good, I'm glad you figured it out. I didn't understand, and probably never will, being a bot. 16:02 slef never mind 16:02 slef ohhh I wish that had made it into the log 16:02 oleonard No a representative from each meeting must engage in single combat 16:02 huginn Log: http://meetings.koha-community.org/2014/development_irc_meeting.2014-06-04-15.10.log.html 16:02 huginn Minutes (text): http://meetings.koha-community.org/2014/development_irc_meeting.2014-06-04-15.10.txt 16:02 huginn Minutes: http://meetings.koha-community.org/2014/development_irc_meeting.2014-06-04-15.10.html 16:02 huginn Meeting ended Wed Jun 4 16:02:04 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) 16:02 slef #endmeeting 16:02 slef Thank you all for taking part 16:01 slef the earlier meeting can flame us if they want ;-) 16:01 slef #agreed 9th and 10th July same times 22 UTC and 15 UTC 16:01 tcohen +1 16:01 gmcharlt +1 16:00 thd +1 16:00 slef 0 16:00 oleonard +1 16:00 slef how about 9th and 10th July same times 22 UTC and 15 UTC? +1 0 or -1 please 16:00 gmcharlt no objection 16:00 oleonard Fine with me 15:59 thd s/adding a week/a week later/ 15:59 slef Anyone mind adding a week? 15:58 thd I would suggest adding a week. 15:58 slef thd: do you have a suggested alternative? 15:57 slef at least we don't overlap 15:57 thd Some people would be returning from ALA on the 2 and 3 of July. 15:57 slef right - that's probably why it's slid a day then... seems OK to me... not great, but it's difficult to give everything a margin of several days 15:57 gmcharlt FWIW, I have no problem with 2/3 July for the next meeting 15:56 gmcharlt ALA runs from 26 June though 1 July 15:56 slef http://ala14.ala.org/ 15:56 slef hrm, it's not on http://digital-conferences-calendar.info/ 15:55 * slef checks ALA 15:55 thd The occur at the end of ALA and just before the US independence holiday. 15:54 slef thd: howso? 15:54 oleonard Not for me. 15:54 thd Those dates are a problem in the US. 15:54 slef but rangi said we could unagree it if we wannt 15:54 slef yeah 15:54 oleonard Is that what was voted on in the previous session? 15:54 slef is it just me, or is that sliding a day later? 15:53 tcohen +1 15:53 slef how about july 2nd and 3rd same times 22 UTC and 15 UTC? 15:53 slef #topic date and time of next meeting 15:52 slef guessing not 15:51 slef afaik there are none - anyone want to correct me? 15:51 tcohen thanks slef 15:51 slef #topic Actions from the last meeting 15:51 slef #info Can anyone help with the kohacon14 conference website, please? Contact tcohen 15:50 wahanui i guess the website is http://www.koha-community.org 15:50 tcohen the website 15:50 slef Anyone have other comments on kohacon15? 15:50 slef tcohen: the conference website, or the physical site? 15:49 wahanui slef: I forgot #action mtj_ 15:49 slef wahanui: forget #action mtj_ 15:49 wahanui i already had it that way, slef. 15:49 slef #action mtj_ is going to repost the call for conference organisers for kohacon15 15:49 slef There's a proposal from Nigeria and an expression of interest from Zambia. 15:49 tcohen i'm currently struggling to get hands to work on the conference site 15:48 slef #topic kohacon15 15:48 slef please let the community know if there is anything we can do to help 15:48 slef right... I read from last meeting that a few presentations have been submitted 15:48 tcohen that's it 15:47 tcohen exactly 15:47 slef interpreters rather than translators, I assume? 15:46 tcohen as there are some latin-american speakers signed already 15:46 slef ¿Donde estan los elephantes? 15:46 tcohen ^^^^^^ that'd be our main need 15:46 tcohen we need funding for the spanish -> english translators 15:45 tcohen we have most of the stuff covered by UNC 15:45 slef #info call for sponsorship expected next week 15:45 slef heh 15:45 slef tcohen: do you know about this? 15:45 tcohen We'll be calling for sponsorship the next week 15:45 slef #topic Kohacon14 15:44 slef #action gmcharlt will start a thread on the general mailing list 15:44 tcohen gmcharlt++ 15:44 * gmcharlt will start a thread on the general mailing list 15:44 slef but I'd like to check and I apologise for not spotting the paste before now 15:44 thd tcohen: We should discuss the wording on the mailing list. I think a few people including myself have a problem with the language. 15:44 slef they could be wrong or my memory may be wrong ;-) 15:44 slef as in, I'm sure it got ripped to shreds by one community I'm involved with, but I don't have it handy right now 15:43 tcohen ok 15:43 slef tcohen: I'm not comfortable with it. 15:43 tcohen with a timeframe for ammendments? 15:43 tcohen can we say that the current wording is approved 15:43 slef OK to move on? 15:43 slef #agreed we would like this approved before kohacon14 15:42 gmcharlt http://koha-community.org/kohacon/kohacon14/schedule/ 15:42 tcohen that's correct slef 15:42 slef which might be wrong 15:42 slef says my calendar 15:42 slef 6-13 October 15:42 slef gmcharlt: agreed. When is it? ;-) 15:41 tcohen +1 # deadline before conference 15:41 jwagner but open-ended discussions never get finished 15:41 gmcharlt it would be better to have it be approved prior to the conference 15:41 jwagner I don't really care -- whatever gives people time to work on it 15:41 slef jwagner: would kohacon14 be a suitable deadline? 15:41 gmcharlt shall we say by the July meeting for a final draft to vote on? 15:40 jwagner slef, I'd suggest setting a deadline for coming up with wording, or it will drag on forever 15:40 slef OK to move on? 15:40 slef Can those interested take the discussion/development of the wording to the email lists, please? 15:39 slef #agreed the general idea of adopting a code of conduct, not that exact wording 15:39 slef and +1 from me, so... 15:39 thd +1 # Only after some modest additional amendment. 15:39 slef #link https://www.debian.org/vote/2014/vote_002#amendmenttexta includes debian's recent code just below that point 15:39 oleonard +1 15:38 gmcharlt +1 15:38 tcohen +1 # having a code of conduct 15:38 ashimema +1 15:38 jwagner +1 15:38 thd The first use of the word "posting" is part of an overly broad statement which could have unintended consequences. 15:38 slef Please can I have a show of +1 0 or -1 on the general idea of the code of conduct, not that exact wording? 15:37 tcohen could we vote the code of conduct, and in a next meeting vote again on how it would be applied to online ? 15:37 slef I would prefer the wording to be more like Debian's, but I don't think we're debating detailed wording yet. 15:37 ashimema ++ 15:37 thd gmchart: If that is intended, then the word "posting" should be qualified. 15:36 gmcharlt I would be in favor of having Koha's code of conduct extended to online 15:36 jwagner I think it would be useful to find some wording to extend to online presences -- harassment can just as easily occur in virtual as well as physical 15:36 gmcharlt which explicitly includes the IRC channel and mailing list 15:36 gmcharlt similar to (say) the Code4Lib code of conduct 15:36 gmcharlt however, the ultimate goal is to have it apply to online fora 15:36 slef I'd expect it to apply more widely, but I don't know if online already has its own policies. 15:35 gmcharlt jwagner: with respect to the Evergreen policy, the wording is intended to refer to physical events 15:35 tcohen jwagner: i'd agree to make general, but we should find a way to define how can it be enforced 15:35 thd We should be fostering an environment for which no one would ever think of behaving in a manner for which a code of conduct would ever need to be used. 15:34 jwagner With regard to the wording "at any Koha event" -- does that mean it's limited to conferences, etc.? What about online meetings, general IRC or listserv? 15:34 slef thd: it was a twitter hashtag I think 15:34 thd Is that an actual nick? 15:33 slef Do people generally support the idea of adopting a code of conduct? 15:33 slef I think this is overdue and I suspect action has been inspired by #slutgate2014 15:32 slef #link http://paste.koha-community.org/24 15:32 slef #topic Code of Conduct 15:32 slef ok, moving on 15:32 tcohen ok, done 15:31 tcohen awesome 15:31 gmcharlt tcohen: yep 15:31 tcohen who are the jenkins admins to coordinate this? rangi and gmcharlt? 15:30 tcohen they will of course be jenkins nodes 15:30 slef cool 15:30 ashimema UNC++ 15:30 tcohen to have the master branch tested on all of them 15:30 ashimema #info UNC is about to provide 4 virtual machines, running Debian {6|7} and Ubuntu {12.04|14.04} 15:30 tcohen we'll need one more running Debian testing 15:30 gmcharlt UNC++ 15:29 tcohen UNC is about to provide 4 virtual machines, running Debian {6|7} and Ubuntu {12.04|14.04} 15:29 ashimema gmcharlt++ 15:29 slef tcohen: go ahead, please. 15:28 tcohen yes 15:28 slef ok, any more #info we'd like to minute about this? 15:28 ashimema Colin run's koha on his fedora machine.. so tends to pick up new perl issues pretty wuick 15:28 tcohen gmcharlt++ 15:28 gmcharlt and possibly, if tuits permit (but I make no promises) see about factoring QP out into an independent CPAN module that both Koha and Evergreen can use 15:28 slef tcohen++ 15:28 ashimema I am talking like a year or so though.. 15:28 ashimema but i do remember the conversation coming up some time ago.. believe it was highlighted to jcamins.. 15:27 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12343 normal, P5 - low, ---, abl, Needs Signoff , TransformKohaToMarc() is adding MARC subfields in random order 15:27 ashimema pass.. I'll see if I can dig it out.. 15:27 tcohen bug 12343 15:27 gmcharlt tcohen: I intend to tackle both ends 15:27 slef ashimema: any idea where colin highlighted it? I'm not finding it by searching yet. 15:27 tcohen gmcharlt: should we report QueryParser stuff to upstream or just patch our copy? 15:25 tcohen gmcharlt: i agree, what i meant to say is that both PQF queries mean (ultimately) the same 15:25 slef Do we rely on locale to set UTF-8 on filehandles at all? 15:25 gmcharlt IOW, it's pretty clearly an issue if you can't count on a given query being translated into the same base Z39.50 query 15:24 slef Should we be worried about the UTF-8-related changes on there? 15:24 tcohen there is code that relies in things like grabbing the first element of a results hash 15:24 gmcharlt tcohen: I disagree; the tests show that the hash-order randomization somehow leads to a given query being translated into different PQF queries 15:24 thd tcohen: What is the actual issue, multithreaded behaviour or hash keys lack of recognisable orderliness? 15:23 tcohen but i'm glad to hear that you're stepping in 15:23 slef "the ordering has already changed several times during the lifetime of Perl 5" 15:23 tcohen gmcharlt: I've been into QueryParser yesterday and it seems that it is related to the unit tests, and that the effects doesnt affect the semantics/results 15:23 slef #link http://perldoc.perl.org/perl581delta.html#Hash-Randomisation is a more authoritative source 15:22 oleonard Sufficiently inscrutable efficiency is indistinguishable from random? 15:22 tcohen thd: each thread has its own seed 15:22 slef #info tcohen is concerned about Perl 5.18 compatibility and specifically the hash keys randomization 15:22 thd Is it random or merely inscrutable efficiency? 15:22 slef #link http://www.perlmonks.org/?node_id=1005122 is a description from late 2012 15:22 ashimema we agree.. we should be working toward newer perl compatability 15:21 ashimema colin highlighted it some time ago if i remember rightly. 15:21 tcohen and am evaluating discouraging people from using distributions that ship Perl 5.18 for now 15:21 gmcharlt QueryParser has some issues with it; I'm planning to look at it 15:21 tcohen specifically the hash keys randomization 15:20 * tcohen is concerned about Perl 5.18 compatibility 15:20 gmcharlt #info Galen Charlton, ESI 15:20 slef tcohen: go for it 15:20 jwagner #info Jane Wagner LibLime/PTFS 15:20 thd slef: What mini device is that with no arrows? 15:20 tcohen I had an announcement, and a few comments on 3.18 15:20 * gmcharlt is here, but well, nothing more to say about 3.16.1 15:20 slef Or RMaints 15:19 slef Any RMs in? 15:19 slef thd: yeah yeah my keyboard doesn't have arrows on it 15:18 slef #info 3.16.1 will be released in mid-June; there will be some important bugfixes in it (gmcharlt, 22:11:08) 15:18 thd slef: arrow? 15:18 slef ashimema: can you up arrow a few times, Home and add #info to that? ;-) 15:17 slef #topic Update on releases 15:17 slef so let's move to that 15:17 ashimema my bad 15:17 ashimema lol.. yup. 15:17 slef ashimema: we've release updates next 15:17 ashimema that a worthy one? 15:17 ashimema 3.16 released since last meeting wasn't it? 15:17 oleonard jinx 15:16 oleonard #link http://koha-community.org/nz-koha-trademark-update/ 15:16 slef #link http://koha-community.org/nz-koha-trademark-update/ 15:16 slef Any other announcements? 15:16 slef I think I saw a blog post about that earlier if anyone would like more details? 15:16 * oleonard cheers 15:15 slef #info The NZ TM has been registered and is being held in trust by HLT (rangi, 22:08:38) 15:15 ashimema ;) 15:15 slef #topic Announcements 15:15 slef thanks ashimema 15:15 slef other introductions will need to happen as we move on 15:15 ashimema #link http://wiki.koha-community.org/wiki/General_IRC_meeting_3_and_4_June_2014 for agenda 15:14 thd #info Thomas Dukleth, Agogme, New York City 15:13 tcohen thanks thd 15:13 oleonard #info Owen Leonard, Athens County Public Libraries 15:13 thd tcohen: You should set topics in the agenda with #topic Introductions, etc. 15:13 ashimema #info Martin Renvoize, PTFS Europe 15:13 slef #info MJ Ray, software.coop, England 15:13 tcohen #info Tomas Cohen Arazi, UNC 15:13 slef Hello and welcome. Please use "#info" in front of your introduction to have it show up in the automatic minutes 15:13 tcohen :-P 15:13 wahanui #info wahanui, a bot that has become sentient 15:13 slef #topic Introductions 15:13 huginn Current chairs: slef tcohen 15:13 tcohen #chair slef 15:13 ashimema ;) 15:13 ashimema you'll need to add them as a chair with '#chair nick' 15:13 slef tcohen: yes, say #chair NICKNAME 15:12 tcohen can anyone take the role for me? 15:11 oleonard http://wiki.koha-community.org/wiki/General_IRC_meeting_3_and_4_June_2014 15:11 slef thd: got agenda link handy? 15:11 slef tcohen: I think you want #topic Introductions 15:11 thd tcohen: Is this the development meeting or the general meeting? 15:11 tcohen #info Tomas Cohen Arazi, UNC 15:11 ashimema :) 15:11 tcohen slef: thanks 15:10 slef tcohen: I can if you prefer and hope my conn... never mind :) 15:10 ashimema or there's the in depth manual at: http://meetbot.debian.net/Manual.html 15:10 huginn The meeting name has been set to 'development_irc_meeting' 15:10 huginn Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:10 huginn Meeting started Wed Jun 4 15:10:35 2014 UTC. The chair is tcohen. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:10 tcohen #startmeeting Development IRC meeting 15:10 slef yengh 15:09 ashimema give him a couple of mins to read the basics maybe ;) 15:09 ashimema those are the instructions cait pointed me to when I took over for her at a meeting. 15:09 thd tcohen: I think that you only have to issue the command startmeeting. 15:09 ashimema https://wiki.debian.org/MeetBot 15:08 thd tcohen: I think so. 15:08 tcohen can anyone start it and I comment after that? 15:07 tcohen thd: i'd like to but have never done that 15:07 reiveune bye 15:06 thd tcohen: Are you leading the meeting? 15:06 thd Exactly. 15:05 ashimema did someone say meeting.. 15:04 thd Yes. 15:04 oleonard Are we, uh... supposed be having a meeting? 15:04 tcohen Joubu: having the test suit to build its own data 15:01 Joubu tcohen: I am not sure that having a sql file is a good idea. But having a script which generates a dump would be better. 14:59 Joubu tcohen: that could be great to do something with the patch 10337 so 14:59 tcohen i'm pretty sure we can do a mysql koha_3_12 < file.sql before running the unit tests 14:58 tcohen in the logs look for the lines that start with + 14:58 tcohen jenkins just tells the node to run a shell script 14:58 Joubu tcohen: we can define a sql dump in the jenkins configuration ? 14:56 tcohen I hope we can have new nodes for the tests soon 14:56 tcohen Joubu, khall: jenkins nodes might have a db dump to be loaded before running the tests 14:27 Joubu khall: yes, 10337 is there for that. I really would like to see something like that in master 14:26 khall a default ut database would be nice 14:26 khall that's why it's passing for you but not me! 14:26 Joubu khall: and yes, I have S and PT 14:25 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10337 enhancement, P5 - low, ---, jonathan.druart, In Discussion , UT: The unit tests cannot be launched by everyone 14:25 Joubu khall: I created my DB (the one I use for unit tests) with the patch on bug 10337 14:21 khall do you have patron categories S and PT in your database already? 14:21 Joubu khall: against master: prove t/db_dependent/Reserves.t returns "All tests successful." 14:18 Joubu which is really a shame... 14:18 khall that should run Reserves.t 14:18 Joubu and some directories explicitely listed 14:18 Joubu If I remember well, it does something like prove t/* prove t/db_dependent/* 14:17 Joubu for instance, it does not launch files if depth is > 1 14:17 Joubu khall: note that the jenkins config does not include all unit test files 14:17 Joubu khall: There are 3 failures on master 14:16 khall If you don't have the S and PT categories in your database already, Reserves.t will fail 14:16 khall The reason it's not failing on Jenkins is that the data is already in the test database on jenkins, so it doesn't need to be created, so the unit test isn't failing 14:15 khall my unit tests are failing, and it's due to the issue of C4::Context::dbh not being shaired by Koha::Database. 14:15 Joubu see http://jenkins.koha-community.org/ 14:15 Joubu khall: it launched master tests 1 day 15 hr ago 14:14 bag why whats up? 14:14 bag khall: I would assume it’s running 13:58 khall is jenkins no longer running? 13:15 wahanui somebody said confused was "Has anyone really been far even as decided to use even go want to do look more like?" 13:15 ashimema confused 13:04 jcamins oleonard: yeah, in hindsight that would be wise. 13:04 oleonard jcamins: From now on randomly mail out your gitconfig file at regular intervals. 12:57 jcamins Nah, I didn't think so either, but I thought there was a very slight chance you might. 12:57 tcohen i don't think I have your gitconfig 12:53 jcamins (months ago, prior to changing servers) 12:51 jcamins Hey, tcohen, I don't suppose I sent you my gitconfig file? 12:50 tcohen at least it has a patch attached :-D 12:50 tcohen :-( 12:50 tcohen unfortunately 12:50 jcamins Oh, well, that's something else. 12:49 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12343 normal, P5 - low, ---, abl, Needs Signoff , TransformKohaToMarc() is adding MARC subfields in random order 12:49 tcohen bug 12343 12:48 jcamins But only once. 12:47 jcamins Though I had the tests pass on Ubuntu 14.04. 12:47 jcamins tcohen: it's only significant in the unit test, so just tell people not to expect those unit tests to run. 12:47 tcohen I hope we can get that jenkins nodes running soon 12:47 tcohen at least QueryParser code does 12:46 tcohen which has been randomized in Perl 5.18 (which 14.04 ships) 12:46 tcohen there's code (in Koha) that relies on Perl hashes key order 12:45 oleonard What's up with Ubuntu 14.04? 12:43 tcohen heh 12:43 magnuse or it's a new flavour of cookie "mmm... opac!" 12:43 tcohen we should discourage the use of Ubuntu 14.04 immediately 12:43 oleonard Hi tcohen 12:42 tcohen morning oleonard 12:42 tcohen he'll be integrating patch series there for the RM to pull 12:42 oleonard Ah. 12:42 tcohen yeah 12:42 magnuse = rangi 12:41 magnuse module maintainer for the opac 12:40 oleonard branch "MM-OPAC" ? 12:28 tcohen gmcharlt: thanks 12:28 wahanui morning is probably a state of the cait 12:28 tcohen morning! 12:20 oleonard-away Hi #koha 11:32 WaylonR huh.. nevermind... 11:17 WaylonR how do i edit marc framework via mysql? 11:14 WaylonR hiya all. koha 3.0.0pre2 .... I can't seem to be able to modify a marc subfield. 856u, currently linked to biblioitems.url, I would like to set it to repeatable.. but the marc framework editor won't change it. 10:00 alex_a je déco / je reco 09:46 magnuse hm, is it possible to make koha suggest the cardnumber as username, not firstname.surname? 08:34 ashimema at least now I have somewhere to start when working out how the numbers are constructed.. was all black magic before ;) 08:30 rangi :) 08:27 ashimema ack.. sod this.. I'm gonna just use dbic in my hack script 08:25 ashimema nice work on the trademark.. hadn't spoted that yet. 08:24 rangi ashimema: yes it really should be 08:24 magnuse woohoo! 08:24 rangi did everyone see this http://koha-community.org/nz-koha-trademark-update/ 08:23 ashimema I was expecting the db access in a module in C4.. 08:23 ashimema aha.. no wonder I couldn't find it.. 08:22 rangi yep 08:22 Joubu and not sure, we will reach a complex one at the end... 08:21 Joubu rangi: yes, of course. It's useless to have a complex workflow at the beginning 08:21 ashimema just reading it now.. thanks. 08:21 ashimema cheers rangi.. 08:21 rangi ashimema: the member-flags.pl was for you :) 08:21 ashimema good work 08:21 ashimema sounds like the MM's are getting going.. nice to see.. 08:21 rangi until we get to something that works well 08:21 rangi but its a new thing, so i think we will refine as we go 08:20 rangi and complicated ones to our branches 08:20 rangi i was chatting with tcohen, we might push tiny ones direct to master 08:20 Joubu ashimema: o/ 08:20 ashimema hi Joubu 08:20 Joubu rangi: yep, it could be great 08:20 ashimema hi rangi 08:19 rangi that way we could see them on the dashboard too 08:19 * magnuse was thinking that might come in handy too 08:19 rangi or something like that 08:19 rangi pushed to module maintainer 08:19 rangi instead of pushed to master 08:19 rangi yeah i was thinking to make a new status 08:18 rangi ashimema: 08:18 Joubu rangi: don't you think it could be interesting to have this information on the bug report, something like "I pushed this into MM-*" ? 08:18 rangi members/member-flags.pl 08:17 rangi sent him a pull request even 08:17 ashimema I can't the wood for the trees in here this moring 08:17 ashimema ok.. stupid question.. where are patron flags set in the code.. 08:17 rangi i did indeed 08:17 huginn 04Bug http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12336 normal, P5 - low, ---, viktor.sarge, Passed QA , Author of reserved book is not displayed in opac-user.pl 08:17 Joubu rangi: for instance, bug 12336 is passed QA, and pushed to MM-OPAC. Did you communicate with Tomas about this patch ? 08:15 rangi cool 08:14 Joubu thanks rangi. I have nothing to push right now, but I hope to push some stuffs on MM-ACQ soon! 08:13 rangi right, set up, if you push to MM-ACQ it should work (same with MM-Tools) 08:09 rangi will do 08:09 Joubu I think 2 differents is better 08:08 rangi what do you prefer? 08:08 rangi or i could make 2 different ones 08:08 rangi i could make MM-Tools-ACQ 08:08 Joubu rangi: yes 08:08 rangi right, are you doing both? 08:07 Joubu rangi: yes, of course. Not sure it would be interesting for tools. But for Acq, it will be 08:07 rangi so you can make branches under it too if you want 08:07 rangi what i acan do is give you push to MM-Tools and MM-Tools/* 08:06 rangi would you like me to make a MM-Tools one for you, and set it up so you can push to it? 08:06 Joubu rangi: great! Are all MM able to create a branch? 08:05 rangi where i can push stuff for tcohen to merge 08:05 rangi Joubu: i made a branch here http://git.koha-community.org/gitweb/?p=koha.git;a=shortlog;h=refs/heads/MM-OPAC 08:04 rangi :) who knows :) 08:03 Joubu But why would you lie to him? ... 08:02 Joubu rangi: :) 08:01 rangi Joubu: we tried to tell the person that on irc, but they wouldnt believe us, hopefully they believe your email 07:37 wahanui hola, gaetan_B 07:37 gaetan_B hello 07:10 fridolin bonjour magnuse 07:10 magnuse bonjour fridolin 07:09 fridolin hie all 06:53 magnuse :-) 06:53 magnuse hah! 06:53 huginn magnuse: The current temperature in Realtor, CABRIES, France is 18.3°C (8:53 AM CEST on June 04, 2014). Conditions: Clear. Humidity: 35%. Dew Point: 3.0°C. Pressure: 29.86 in 1011 hPa (Steady). 06:53 magnuse @wunder marseille 06:53 magnuse yay! 06:53 huginn magnuse: The current temperature in Bodo, Norway is 19.0°C (8:20 AM CEST on June 04, 2014). Conditions: Clear. Humidity: 37%. Dew Point: 4.0°C. Pressure: 30.01 in 1016 hPa (Steady). 06:53 magnuse @wunder boo 06:53 wahanui niihau, reiveune 06:53 reiveune hello 06:52 alex_a bonjour 06:33 huginn magnuse: The operation succeeded. 06:33 magnuse @later tell eythian i have no idea... :-/ 06:32 * magnuse waves 05:38 * dcook loves using 0123456789 as a test ISBN, especially for Amazon images. Hehe. 05:37 longrider How many indexed documents = 0; 05:37 longrider SolrAPI = http://localhost:8983/solr/koha 05:36 longrider It produce 05:36 longrider But I do not getting record index 05:36 dcook well done, longrider 05:35 longrider I have solved solr down problem 05:26 dcook have a good one 05:26 dcook well done, eythian! 05:25 eythian that'll have to do for the evening unfortunately. 05:24 eythian Good, ES item type limits are now working. 05:20 longrider But I am getting my solr is running 05:20 longrider SolrAPI = http://localhost:8983/solr/koha Solr is Down 05:19 longrider It produce 05:19 longrider now when I run the command ./rebuild_solr.pl -i 05:19 longrider I have solves the non exist issues 05:13 dcook Well, not Solr w/ Koha at least 05:13 dcook But again, I don't do anything with Solr, so no clue 05:12 dcook s/package directores/directories expected by a package install/ 05:12 dcook These paths "/home/koha/solr/etc/searchengine/solr/config.yaml" and "/usr/share/koha/lib/Koha/SearchEngine/Solr/Config.pm" make it look like you're using a non-package install...which is expecting code according to package directories 05:10 longrider Please help me for deploying solr with koha 05:10 longrider Welcome biblibre people 04:51 eythian hmm, I'm not sure then 04:50 longrider file exist 04:50 longrider yes 04:50 longrider The solr config index file (/home/koha/solr/etc/searchengine/solr/config.yaml) for Solr is not exist at /usr/share/koha/lib/Koha/SearchEngine/Solr/Config.pm line 59. 04:50 eythian does the file exist? It's not likely it says that it doesn't exist when it does. 04:49 longrider But I set rightly acccording to the documentation 04:48 longrider The solr config index file (/home/koha/solr/etc/searchengine/solr/config.yaml) for Solr is not exist at /usr/share/koha/lib/Koha/SearchEngine/Solr/Config.pm 04:47 eythian what is the error? 04:47 longrider It also produce error 04:46 longrider and when I run $ ./misc/migration_tools/rebuild_solr.pl -i 04:46 eythian no one can actually visit that, it's not a real URL. 04:45 longrider It do not produce anyting 04:45 longrider on the Validation step 04:44 longrider http://<pro.community.local>/cgi-bin/koha/admin/searchengine/solr/indexes.pl 04:43 eythian longrider: an email that says "it's not working" isn't likely to be acted upon. Better would be to say what part of it isn't working, get help with that, and then update the documentation. 04:32 huginn eythian: The operation succeeded. 04:32 eythian @later tell magnuse how come the nomarc record.abs doesn't have 942$c as itype? 04:31 dcook Makes sense 04:30 eythian and quite different standards/practices. 04:29 eythian it's a moderately different use case. 04:29 eythian very 04:29 eythian err 04:29 eythian vier -ish 04:28 dcook I suppose ICA-AtoM is ILS-like? Pretty sure it does 04:26 eythian I don't know 04:20 mtj_ i wonder if any other ILS' use ES? 04:17 mtj_ oooh, language-detection plugin -> http://gibrown.wordpress.com/2013/05/01/three-principles-for-multilingal-indexing-in-elasticsearch/ 04:16 eythian yeah there'll be some neat stuff we can do like that. 04:14 mtj_ Language Analyzers in ES look impressy -> www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-lang-analyzer.html 04:12 dcook eythian++ 04:12 mtj_ sounds like some awesome progress 04:11 eythian though limiting on adv search needs a bit of work still. 04:11 eythian in other news however, elastic search now has basic and advanced search working. 04:10 mtj_ ... and as eythian said, using custom code not currently in koha stable 04:08 wahanui rumour has it no one else is testing the Ubuntu-specific patches 04:08 mtj_ no one else 04:07 mtj_ longrider: afaik, only the biblibre people have deployed koha with solr 04:05 longrider ys 04:03 eythian But I'd consider your reasons in the first place, it may be a maintenance headache. 04:03 eythian So, you might have some luck. 04:02 eythian ah, a lot of the issues I saw with it are because it requires code that's on github, not on cpan. 03:59 eythian I'm not sure how well though. 03:59 eythian actually, there's a chance it might. 03:54 eythian yes, in France with custom code from biblibre I think. 03:54 longrider some libraries are using solr 03:54 longrider eythian 03:53 wahanui i think Also that is a giant undertaking 03:53 dcook Also that 03:53 eythian longrider: yes, we've been telling you that it probably won't work. 03:53 dcook longrider: As I suggested, maybe in 3-4 hours. 03:53 longrider Anybody here can help me? 03:52 dcook With eythian on this one 03:51 eythian I wouldn't expect it to work. 03:49 longrider http://wiki.koha-community.org/wiki/Solr_deployment 03:49 longrider I got it in the following 03:49 longrider dcook 03:48 longrider I am ok on the above step 03:48 dcook longrider: Where are you reading these instructions? 03:47 dcook eythian: Cool. Always trying to find ways of improving my Perl writing... 03:47 longrider open a browser and go to http://localhost:8983/solr/koha/admin/ you will see the solr administration page you SolrAPI will be http://localhost:8983/solr/koha (nothing to see) 03:47 eythian longrider: as far as I can tell, the SOLR code currently in stock koha simply won't work. 03:47 dcook longrider: The solr folk should be online in about 3-4 hours, I think 03:46 longrider I am trying to deploy solr in my koha 03:46 eythian hmm, I don't think it's the worst thing ever. 03:45 dcook A recursive sub makes it look a bit nicer, but that also seems suboptimal, although perhaps not too bad if you're using references.. 03:45 dcook I didn't need to do it in the end, but it seems suboptimal :/ 03:45 dcook What are your thoughts on declaring a variable before a foreach loop and then populating that variable in the foreach loop so as to get the "previous element"? 03:44 eythian yeah, that's why I like it. 03:44 dcook I like writing 1 line rather than 5 lines in this case... 03:43 dcook Hmm, cool beans 03:41 eythian probably not significant 03:41 eythian I don't know about the relative performance. 03:41 eythian Well, it's different. 03:41 dcook Or is it just sexier? 03:41 dcook eythian: Any ideas about its performance vs foreach and recursive subs? 03:40 dcook eythian for using map which made me think to use map :) 03:40 dcook eythian++ 03:40 dcook map++ 03:23 wizzyrea eythian++ 03:12 eythian now we're getting somewhere 03:12 eythian 'query' => '(_all:book) AND (author:rose)' 02:12 wahanui okay, wizzyrea. 02:12 wizzyrea confetti is also https://31.media.tumblr.com/f53100e15d6190ade350c3d98b0ccd54/tumblr_n5soy8FDMK1tt9lrzo6_250.gif 01:17 wahanui OK, eythian. 01:17 eythian wahanui: kohacon10 is https://archive.org/details/KohaCon10 00:03 pianohacker cool, thanks 00:02 rangi were the other 2 i looked at 00:02 rangi yep that and the t440 00:02 jcamins pianohacker: if you use Linux, a bunch of my friends report the Thinkpad x1 being good. 00:02 rangi constantly 00:00 eythian It cries to the Princess Bride eh? 00:00 rangi https://www.system76.com/laptops/model/galu1 <-- thats what i have 00:00 rangi the trackpad is a bit overly sensitive, but i like everything else