IRC log for #koha, 2014-05-12

← Previous day | Today | Next day → | Search | Index

All times shown according to UTC.

Time Nick Message
00:53 mtj hi #koha
00:54 ooh, this looks interesting -> https://www.youtube.com/watch?v=w5Jc8-6UU4Q
00:56 amazing that i have never spotted this till now...
00:58 wow, i gotta save this for later today :0)
01:07 .
01:07 peeps, does anyone have a handy alias to delete a commit, in git?
01:08 …where the commit is quite deep, and the commit SHA is known
01:09 the best i have got via google is..
01:09 $ git rebase -p --onto SHA^ SHA
01:10 its been running for about 5 minutes, still going...
01:13 hmm, i think my git has a library thats missing
01:16 actually... i think my server needs a reboot :)
01:35 eythian mtj: there's no such thing as "delete a commit"
01:36 except for rebasing, which then rewrites all the history following
01:36 the closest safe thing is to revert it.
01:41 dcook Not sure why you'd want to delete a commit anyway O_o
01:45 I wouldn't mind renaming some commits so that they're easier to find later, but the whole history thing has become more obvious recently as I've been collaborating more on local projects
01:45 mtj i have a commit where i delete a directory… now i want that directory back
01:45 eythian mtj: revert it
01:46 dcook ^
01:46 mtj ok, will do :)
01:46 dcook Then if you decide that you actually did want to delete it, revert the revert
01:46 rangi you only need to delete if you accidentally put data that should never be public
01:46 theres a lot on github that should be deleted :)
01:47 dcook Didn't eythian post a link a while ago that shows the number of swears on github?
01:47 mtj yeah, this is a def. a private repo
01:47 dcook mtj: Revert will only undo the original commit. The info will still exist in the history of course
02:06 rangi yeah you only need delete when you accidentally push your passwords or something, a revert doesnt help you then :)
03:01 mtj what do peeps think about a script to update/freshen koha conf files, when upgrading?
03:01 afaik, its currently a manual task?
03:02 eythian mtj: now try it with zero risk of breakage.
03:04 mtj heh, yeah… :)
03:04 atm, i'm just thinking of a quick/dirty script to use myself
03:05 and manually fixing the breakage
03:06 dcook Sounds nice :)
03:09 mtj how do other people in #koha handle this problem?
03:10 dcook We use a script that updates based on a model, but I'm not responsible for that script, so not 100% on the deets
03:12 mtj hmm, now i think of it… my solution is not that bad
03:13 eythian we don't. if something actually needs it, we do it manually.
03:13 There was talk of making something that extracted all the user-configurable parts of the koha-conf and re-wrote it from template.
03:14 mtj yeah, thats basically what i'm thinking too
03:14 its not perfect, but its a start
03:17 and track/restore your site-specific mods using git
03:23 anyhoo… thanks for the guys. -  i'll have a bit more of a think about it, over the week
03:23 eythian joined #koha
03:25 mtj dcook, any poss. of your script being submitted to koha?
03:31 jeff joined #koha
03:39 dcook mtj: I sincerely doubt it. I've never even seen the thing.
03:53 mtj all good
04:04 i thought i would be a fool to not ask you :p
04:04 dcook Hehe. Fair enough ;)
04:21 cait joined #koha
04:26 BobB joined #koha
04:27 paxed ffs. whoever thought it would be good to order the categories-table by the categorycode? ugh.
04:27 (and Yet Another table with no id numbering? *rolleye*)
04:28 rangi i reckon you'd be better off just writing your own ils paxed
04:33 paxed yes, ils with blackjack and hookers.
04:35 eythian ID numbering is only needed when it's needed. If something naturally has a key, you don't need artificial ones. Also, tables aren't ordered.
04:35 Results are ordered, but there's no sensible way to think of a table as ordered.
04:36 paxed eythian: in other words, no way to reorder the table without changing the categorycode.
04:37 eythian paxed: Short of imposing your own ordering on the results, "reorder the table" isn't a meaningful sentence.
04:37 Besides, I'd be inclined to sort the results by description.
04:38 paxed even that would be better than sorting by categorycode.
04:39 eythian it'd be an easy change.
04:59 paxed bug 12228
04:59 huginn 04Bug http://bugs.koha-community.org[…]_bug.cgi?id=12228 enhancement, P5 - low, ---, koha-bugs, NEW , Sort patron category by description not by code
05:09 BobB joined #koha
05:14 BobB joined #koha
05:51 * magnuse waves
05:51 dcook Yo magnuse
05:53 magnuse yo yo yo dcook
05:53 wassup?
05:54 time to leave work? :-)
05:55 dcook Not for another hour :)
05:59 BobB_ joined #koha
05:59 magnuse yeah, guess i'm a bit early today
05:59 * magnuse waves to BobB and BobB_
06:00 BobB_ only bobb_waves back  :)
06:06 BobB joined #koha
06:28 * cait waves too
06:31 cait left #koha
06:33 petter joined #koha
06:39 reiveune joined #koha
06:39 reiveune hello
06:39 wahanui hey, reiveune
06:39 laurence joined #koha
06:44 alex_a joined #koha
06:52 magnuse @wunder boo
06:52 huginn magnuse: The current temperature in Bodo, Norway is 6.0°C (8:20 AM CEST on May 12, 2014). Conditions: Mostly Cloudy. Humidity: 87%. Dew Point: 4.0°C. Windchill: 4.0°C. Pressure: 29.59 in 1002 hPa (Steady).
06:54 paul_p joined #koha
06:58 gaetan_B joined #koha
06:59 gaetan_B hello !
06:59 rangi hi gaetan_B
07:02 * magnuse waves again
07:03 rangi hiya magnuse
07:03 magnuse hiya rangi
07:03 long time no see, it feels like
07:07 rangi yeah, both been busy I think
07:08 magnuse yup
07:20 how can we get bug 11944 in? if it makes sense to the elders, it seems like the kind of thing that just needs to be pushed, and then have the kinks ironed out over time
07:20 huginn 04Bug http://bugs.koha-community.org[…]_bug.cgi?id=11944 major, P5 - low, ---, gmcharlt, Needs Signoff , Cleanup Koha UTF-8
07:20 magnuse first patch for 3.17 perhaps?
07:28 rangi sounds like a plan
07:28 magnuse yay!
07:29 it's the kind of bug where you sort of have to test *everything*, and that will never happen, of course
07:29 rangi yep
07:30 magnuse hm, i guess it might be possible to have some kind of bot/spider that clicks on every link and looks for double encoded chars?
07:31 rangi its hard to spot those, but possible to catch a lot
07:35 jeff_ joined #koha
07:42 ashimema Hmm, still on my first foray into hosting a repository for our local deb packages.. any pro's here I could quiz?
07:44 rangi you are using reprepro
07:44 ?
07:44 ashimema I am..
07:44 and the repository.. sort of works.
07:44 rangi right
07:44 ashimema but, when trying to install koha-common from it i get a whole host of 'Depends: *** but is not going to be installed' errors.
07:45 At that point, i'm stretching my understanings ;)
07:45 rangi ah ha
07:45 thats not your fault
07:46 you still have the main debian repos eh?
07:46 wheezy doesnt have some of the modules we need
07:47 ashimema aha.. I need to add the community repo along side my own repo don't I..
07:47 rangi exactly
07:47 and as long as your package is numbered higher
07:47 ashimema currently, just got wheezy, indexdata and our own.. but not community..
07:47 awesome.. thanks rangi.. something so simple!
07:47 rangi it will use your koha-common, not the one in the community repo
07:48 ashimema I was starting to feel rather stupid
07:48 magnuse rangi++
07:49 rangi congrats on the belfast uni btw
07:49 ashimema Cheers, I've still got some mopping up to do, but their pretty much live now...
07:50 paul_p joined #koha
07:50 ashimema they're a strange customer though.. normally we do loads of customisation of the opac for them to make it 'fit' their organisation.. they've stuck with bootstrap out of the box.. not even put anything in the css,js prefs yet..
07:50 looks odd to me ;)
07:51 rangi yeah, thats kinda weird
07:52 ashimema I'm sure they'll get to it.
07:52 rangi do you know what ils they had before?
07:52 ashimema one of the sirsidynix systems.. horizon I think..
07:53 rangi ahh that explains it
07:53 you could throw mud at a monitor and it would be prettier than that
07:53 ashimema one we do a huge number of migrations from ;).. having said that, on this occasion our partners in ireland did the migration part (InterLeaf Technologies).. we're just hosting, and adding shibboleth support (which I hoep to get bmcc to sign off son ;) )
07:53 rangi sweet
07:53 ashimema hehe.. indeed.
07:54 shib still could do with a few more eyes to look over it.. but it's getting closer with every install I do of it.
07:54 I know bywater have been testing is too
07:55 hows the elastic stuff coming along.. I get excited eery time I hear one of you guys is working on it ;)
07:56 rangi its ticking along nicely eythian has been doing most of it lately in between his plack work
07:56 magnuse eythian++
07:56 ashimema excellent.. too mighty important project.. plack and elastic.. that's great to hear
07:57 magnuse OPL will be indexing their rdf in elasticsearch - i wonder if koha will be able to talk to that
07:57 or if it will mean a ton of config changes
07:57 * magnuse knows next to nothing about ES, yet...
07:58 rangi magnuse: yep it will
07:59 its schema less, you can index rdf and marc in it .. also unimarc and marc21 etc
07:59 and some dc
07:59 and whatever else you want
08:00 magnuse but there will probably be different index names and so on?
08:00 rangi there can be
08:00 its pretty much up to you
08:02 the nice thing is catmandu makes it easy
08:02 ashimema next random packages question... how does apt count (in terms of version.. I've been following various instructions and have a package names '3.14.06~ptfs1'.. is that gonna be taken as above '3.14.06'..?
08:02 rangi yep
08:02 ashimema rangi++ for finding catmandu++
08:03 :)
08:03 rangi i think magnuse found it first
08:04 ashimema :)
08:04 magnuse w00t :-)
08:05 it would be super awesome if koha could just use the rdf-indexed-in-es that opl will create
08:06 ashimema that'd be awesome.
08:06 rangi i think its a possibility yeah
08:07 maybe a little work
08:07 but the thing with es
08:07 it hands out json results
08:07 so its easy to build a frontend
08:08 magnuse it might be worth thinking about when opl does their development
08:08 if the two projects use the same kinds of names for things, it might be easier to interoperate
08:09 ashimema bloody tube strike a week back meant I missed a really interesting sounding meetup with some of the elastic search guru's over here..
08:09 rangi yep
08:09 ahh bummer ashimema
08:09 ashimema opl (oslo public library?)
08:09 indeed.. still, reading your code is interesting enough to start with..
08:13 atheia joined #koha
08:14 atheia Hello all
08:14 ashimema morning atheia
08:14 rangi hi atheia
08:15 atheia Morning ashimema, rangi
08:15 magnuse opl is Oslo Public Library a.k.a. "Deichman" - see http://www.deichman.no/ for their website and http://digital.deichman.no/ for their tech blog
08:15 opl?
08:15 wahanui hmmm... opl is Oslo Public Library a.k.a. "Deichman" - see http://www.deichman.no/ for their website and http://digital.deichman.no/ for their tech blog
08:15 magnuse hiya atheia
08:16 ashimema :)
08:18 yeay, repo working perfectly now :).. that should make my testing of packages easier :)
08:19 sophie_m joined #koha
08:19 atheia hi magnuse!
08:19 ashimema or rather.. helping others to test packages easier :)
08:24 rangi sweet
08:28 magnuse yay
08:34 * mtj_ waves to #koha
08:34 mtj_ hey rangi, did you end up buying a lappy in the US?
08:35 rangi yep, got a system76
08:36 mtj_ just having a looky now... :)
08:39 * magnuse waves to mtj_
08:39 rangi mtj_: got the galago
08:51 mtj_ all the system76 models look awesome
08:59 ...world-wide shipping too :)
09:00 rangi yep
09:14 magnuse ooh, they ship to norway :-)
09:14 then the one remaining problem is the keyboard...
09:55 hm, i do wonder why i am not seeing any bibliographic info in results lists on current master? details looks normal. i have done a full reindex...
10:08 ashimema are you using the remote xslt settings at all..
10:10 On second thoughts.. ignore that, bug 11826 hasn't been pushed yet.
10:11 huginn 04Bug http://bugs.koha-community.org[…]_bug.cgi?id=11826 enhancement, P5 - low, ---, m.de.rooy, Passed QA , Improving code for XSLT handling
10:11 ashimema thought you may have foud a bug in it.. after all my testing ;)
10:11 somthing else must be the culprit
10:18 magnuse nope, no remote xslt :-)
10:20 havn't looked at the log yet, though
10:21 "GetCOinSBiblio called with undefined record at ..." - looks like it is not getting the record from zebra the way it should?
10:24 and one warning about "when" and "Smartmatch" per record
10:47 * magnuse waves to khall
10:47 khall good day magnuse!
10:48 ashimema hi khall
10:48 khall hi ashimema!
10:50 * magnuse tries a reboot
10:52 magnuse joined #koha
10:54 magnuse wow, when i connect with yaz-client and do "f something" i get "Memory segmentation fault (core dumped)"
11:02 oh well, lunchtime
11:02 wahanui i guess lunchtime is a terrible time for a meeting
11:02 magnuse so it is!
11:04 NateC joined #koha
11:11 marcelr joined #koha
11:11 marcelr hi #koha
11:12 magnuse: please have a look at bug 9612 followup
11:12 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=9612 minor, P5 - low, ---, m.de.rooy, Signed Off , SRU Response is different when DOM indexing is enabled
11:12 marcelr may explain your search results
11:32 markvandenborre I am thinking about cover images
11:33 I have a consistent directory structure with one pdf per book, and I can reliably run a script to pull the cover page from those pdfs
11:34 I guess there must be a way to import those cover images into the repo
11:34 in one batch
11:34 any suggestions on how to tackle that one?
11:34 paxed if i'm adding a new slip for printing, should the db entry go into updatedatabase.pl?
11:34 markvandenborre I hope a more elegant answer is possible than sql
11:35 paxed (in the patch, that is)
11:35 why would you add the book covers into the repo?
11:36 if the cover images are in a predictable URL, you could just add the image url in the xslt
11:37 marcelr paxed: your db entry should go to updatedatabase for upgrades and into installer/../.sql for new installs
11:37 paxed marcelr: so, both.
11:37 marcelr yeah
11:37 markvandenborre paxed: I'm trying to keep a koha install as standard as possible
11:38 marcelr paxed: you will be happy to see that a new notice must be copied to 10 language folders..
11:38 markvandenborre maybe that is indeed the way to go...
11:38 paxed marcelr: i know. which is stupid.
11:38 marcelr true
11:38 i once tried something to remove that barrier, but alas
11:38 paxed markvandenborre: just copy the stock xslt, and set the syspref to use your own version of it.
11:39 markvandenborre thx for the hint!
11:40 been 10 years since I touched any xslt, but should be possible
11:41 jcamins That's way more complicated than just using the built-in cover image feature.
11:41 There's an option to upload a zip file with all your cover images and an index.
11:41 You'll have to do it in several batches because the maximum upload size is probably 5mb, but that shouldn't be too bad.
11:42 I don't remember the exact format for the cover image index.
11:42 It should be in the manual.
11:47 fridolin joined #koha
11:48 markvandenborre jcamins: found it, sorry, should have looked at that more carefully first
11:48 and thanks
11:48 fridolin hie all
11:51 marcelr hi fridolin
11:51 fridolin hi marcelr
11:53 meliss joined #koha
12:07 collum joined #koha
12:09 tcohen joined #koha
12:10 tcohen morning
12:12 marcelr hi tcohen
12:18 ashimema hey tcohen.. I've updated your repo guide on the wiki a tiny bit, just to get version numbering a bit more standard to debian... hope that not treading on toes.
12:18 oleonard joined #koha
12:20 oleonard Hi #koha
12:20 ashimema hi oleonard
12:23 francharb joined #koha
12:24 tcohen ashimema: np
12:24 looks good
12:24 francharb good morning #koha
12:30 ashimema has anyone else ever noticed that during the installer login page, there's a 'Koha' link randomly positioned on the left side of the screen?
12:30 it's been there for ages.. I've never though to mention it before
12:31 oleonard CSS text offset from image replacement? Is your browser maximized?
12:34 ashimema yup..
12:34 and yup..
12:35 I have a widescreen monitor, so it's probably more prominent for me too ;)
12:36 hmm.. test-indent: -1000px;.. why is it like that?
12:37 paxed i think that's a pretty common way of moving stuff "away" via css.
12:37 ashimema why not just not have the text in the html in the first place?
12:40 oleonard ashimema: It's a way to replace text with an image via CSS.
12:40 ashimema: It's intended to be more customizable and more accessible
12:41 talljoy joined #koha
12:41 talljoy left #koha
12:41 talljoy joined #koha
12:42 oleonard ashimema: On the other hand, the "-1000px" was implemented at a time when 1000px seemed like a reasonable number of pixels to push something offscreen.
12:42 ashimema I see..
12:42 oleonard Progress.
12:42 wahanui progress is probably good
12:43 ashimema I've seen it an offset like that before.. never really like it.. seems cludgy.. but I've also never looked into the alternatives.
12:44 I don't really understand how it's more customizable really either..
12:44 oh well, I'll bow to the styling pro ;)
12:44 magnuse "visibility: hidden" or something like that wouldn't work?
12:45 oleonard ashimema: Theoretically you could add something like #login h1 {  background: url("my-custom-logo.gif") }
12:47 magnuse: I tried to pick a widely-accepted image-replacement method that had been well-tested.
12:49 magnuse oleonard: i trust you a 110% when it comes to css. just wondering... ;-)
12:51 oleonard It's not unreasonable to think that there is a better method now. And if not, then "-5000" could always work for a couple more years ;)
12:51 * oleonard demands that someone get him an Oculus Rift for Koha testing
12:56 ashimema hehe..
12:58 nengard joined #koha
12:58 ashimema lost by the finickyness of css then.. as I thought you could do that anyway without the anchor 'Koha' text..
12:58 eitherway.. it's not an especially important bug.. but a bug none the less in my eyes ;)
13:02 * ashimema wonders how caits course is going
13:03 fridolin joined #koha
13:03 * druthb has no doubt.  Cait is awesome.
13:05 petter joined #koha
13:07 petter joined #koha
13:10 Dyrcona joined #koha
13:26 jl- joined #koha
13:27 tcohen ashimema: would you take a look at the patches for bug 11404?
13:27 huginn 04Bug http://bugs.koha-community.org[…]_bug.cgi?id=11404 major, P5 - low, ---, tomascohen, Needs Signoff , add out-of-the-box support for Apache 2.4
13:28 ashimema will do tcohen.
13:30 nengard hi all, is there a bug somewhere about not for loan items (aka on order items) showing in the holds queue?
13:33 ashimema I've not come across one yet negard..
13:33 but I'm 'no cait' when it comes to bugzilla ;)
13:34 nlegrand joined #koha
13:34 nlegrand hey koha o/
13:34 ashimema I've not come across one yet nengard..
13:35 nengard okey dokey
13:41 rambutan joined #koha
13:43 nlegrand I'm having a weird trouble with zebra biblios full reindexion, Zebra merge stop silently at =~ 20 %, It seems I have all items in the intranet, but nothing in the opac
13:43 does someone have an idea about it?
13:50 ashimema does it actually stop.. or is it still running.. I sometimes find the merge/commit actions of zebra take a very very long time.. but do eventually complete
13:53 nlegrand ashimema: it looks like this: http://pastebin.com/Kjv6g5Xz
13:54 ashimema ah, that really is a silent failure.
13:54 'fraid I know no better then.
13:54 nlegrand :) thanks anyway
13:54 ashimema try running it in verbose.. you may get a bit more info
13:54 sorry.. double verbose..
13:54 -v -v
13:54 nlegrand ashimema: it is verbose :(
13:54 ashimema or even -v -v -v
13:54 nlegrand ho !
13:54 nice
13:54 ashimema ;)
13:55 nlegrand I'm doing it right now :)
13:55 ashimema it'll spit a hell of a lot onto screen... but with any luck the actualy error will appear for you :)
14:19 phasefx joined #koha
14:24 ashimema tcohen, those patches 'look' good to me, but I'm still no package expert.  I'm building a set from them now to test they work as expected, but I'm not expecting any failures.
14:25 tcohen ashimema: due to a bug in apache2-mpm-itk you need to first install it, and then koha-common
14:26 and to install it do: a2dismoe mpm-event ; a2enmod mpm-prefork ; apt-get install apache2-mpm-itk
14:27 ashimema had a feeling that would be the case..
14:27 tcohen there's nothing we can do about it
14:27 barton joined #koha
14:27 ashimema I'm not really sure what make koha require the specific apache stuff
14:27 tcohen (koha-common depends on mpm-itk, which would fail to install unless you do those steps
14:27 ashimema yeah, I've got into problems with that before.
14:28 tcohen we need mpm-itk to implement the user-per-instance schema
14:28 ashimema ah, I see.
14:28 tcohen which we dont seem to be abandoning in a near future :-P
14:28 ashimema :)
14:28 which, i think, makes sense for security?
14:29 tcohen exactly, other option would be to use setuid for the apache process
14:29 which I wouldn't
14:30 ashimema coolios.. I'll report back anything if I run into issue.. otherwise I'll go ahead and sign it off..
14:31 nengard I'm documenting the code in bug 9016 can someone tell me how 'feed' works?
14:31 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=9016 enhancement, P5 - low, ---, jonathan.druart, Pushed to Master , Multi transport types for notices
14:33 kmlussier joined #koha
14:36 huginn New commit(s) kohagit: Bug 9724: ensure hourly loans show time due in SCO <http://git.koha-community.org/[…]989f3fbe542c47aaa>
14:46 jenkins_koha Starting build #1752 for job Koha_master (previous build: SUCCESS)
14:55 tgoat joined #koha
15:10 fridolin left #koha
15:23 reiveune bye
15:23 reiveune left #koha
15:24 rocio joined #koha
15:38 cait joined #koha
15:40 pianohacker joined #koha
15:50 gaetan_B bye!
15:50 * cait waves
15:53 druthb Hi, cait!  *hugs*
15:54 cait hi ruth :)
15:55 alex_a joined #koha
16:04 talljoy hi druthb  great pic on the FB today!
16:04 windblown and sassy
16:04 loved it
16:04 jcamins in?
16:15 ashimema cait... your alive..
16:15 how'd it go today?
16:15 * ashimema sends hugs to cait
16:16 cait barelyy
16:16 ooh
16:16 the server is still alive too
16:16 that makes me happy
16:16 ashimema :)
16:20 pianohacker hi ashimema°
16:20 !
16:21 ashimema hi pianohacker.. lnog time no see.
16:21 hows uni?
16:21 pianohacker good, just walked! Doing summer session now
16:22 ashimema 'just walked'.. is than another americanism?
16:22 pianohacker (walked meaning graduated)
16:22 ashimema oh.. awesome.. congrats.
16:22 Oak joined #koha
16:22 pianohacker probably an americanism. Hell if I know
16:22 ashimema does that mean we sohuld expect more of you here again now :)
16:23 druthb thanks, talljoy—Sam caught me mugging for the camera, and it just Worked.
16:23 talljoy it was. AWESOME.
16:23 pianohacker ashimema: yup, should be in at least a bit more
16:24 ashimema good news.
16:24 wahanui hmmm... good news is it looks like it's running properly.
16:35 tcohen joined #koha
16:43 laurence left #koha
17:01 jenkins_koha Project Koha_master build #1752: SUCCESS in 2 hr 16 min: http://jenkins.koha-community.[…]Koha_master/1752/
17:01 Owen Leonard: Bug 9724: ensure hourly loans show time due in SCO
17:01 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=9724 minor, P5 - low, ---, oleonard, Pushed to Master , Hourly loans don't show time due in SCO
17:04 oleonard tcohen++ # nice response in the prog/CCSR removal thread
17:06 Dyrcona Well, this is intriguing: http://aims.fao.org/community/[…]ry-system-ils-ove
17:07 Oh, then I see the co-sponsors.....
17:21 mveron joined #koha
17:40 ashimema that's interesting indeed.. as I thought they were one of our customers.. and running community
17:43 That really is interesting.. they've got links to koha-community.org all over the place.. but it's being presented by liblime... I'll go digging
17:55 oleonard-away Shouting "KOHA" is typical Liblime
18:02 mveron joined #koha
18:18 HdezCortes joined #koha
18:19 HdezCortes Hola, necesito ayuda quisiera saber si alquien habla español ??
18:23 markvandenborre HdezCortes: sorry, can't help you, but I see that some people seem to be translating the manual to Spanish
18:24 maybe they can?
18:24 HdezCortes ok
18:25 when I enter my koha server freezes well http://200.88.48.100:8080/
18:25 do not know why he got so
18:33 mtompset joined #koha
18:33 mtompset Greetings, #koha.
18:36 HdezCortes I have problem with my server got so koha and not for what reason if someone could help me?? http://200.88.48.100:8080/
18:40 mtompset HdezCortes: Which instructions did you follow?
18:40 (to install it)
18:42 HdezCortes KohaInstallGuide
18:42 mtompset My guess is that you did a name-based installation which only listened to port 80, and that there is no mention of the IP address in your apache configuration files, so it just passes you back the OPAC all the time.
18:43 So why aren't you using http://whatever-the-name-is:8080/?
18:43 where you change whatever-the-name-is to the correct name?
18:43 HdezCortes mtomset : pero koha esta funcionan bien y de repente se puso asi
18:44 mtomset but koha is working well and suddenly became so
18:44 mtompset Are you using a different machine?
18:44 HdezCortes no
18:45 mtompset If it is a corporate machine, do they reset the computers every month to a default installation to avoid viruses?
18:46 Oh... have you always used the IP address to access it?
18:47 chris_n joined #koha
19:05 nengard oleonard got a question about your ebook styling code
19:05 oleonard Sure
19:05 nengard it doesn't work with track clicks turned on - is it as simple as escaping the ? with a /
19:05 in the URL check
19:06 and if i make no sense i blame cold meds
19:07 the URL is: http://MYLIBRARY/cgi-bin/koha/[…]blionumber=129144
19:08 I had var ohdbks_link = td.find("a[href^='http://www.gutenberg.org/etext']");
19:08 but that didn't work cause that's not how it starts
19:08 and then   var ohdbks_link = td.find("a[href^='http://MYLIBRARY/cgi-bin/koha/[…]enberg.org/etext']");
19:08 didn't work either
19:10 oleonard nengard: I don't know offhand, you'll have to do some tests and/or read the docs on how jQuery's find work
19:10 cait joined #koha
19:12 NateC joined #koha
19:13 nengard :( that means thinking ... no thinking for this brain today :)
19:18 oleonard - fyi:
19:18 var pgbks_link = td.find("a[href*='http://www.gutenberg.org/etext/']");
19:18 *= instead of ^=
19:23 sophie_m joined #koha
19:34 mtompset Greetings, sophie_m.
19:35 HdezCortes Someone is in line
19:39 cait joined #koha
19:49 taylorSchmidt joined #koha
19:50 pianohacker hi taylorSchmidt!
19:50 all: taylorSchmidt is one of my group members on the field session project we're doing for Koha
19:50 cait hi pianohacker
19:50 is there a test installation with rancor maybe?
19:51 pianohacker cait: I can update my test server to the latest set of patches
19:51 cait i was asked about a new better cataloguing module...
19:51 HdezCortes Good I have problem with my server Koha Someone can help me??
19:52 cait pianohacker: ah, i thought maybe there was already something somewhere - worth asking :)
19:53 Dawa joined #koha
19:53 pianohacker And Dawa is the other
19:54 cait hi Dawa and taylorSchmidt
19:54 what is the project about?
19:54 pianohacker khall: don't know where bag went but we have Dawa and taylorSchmidt here
19:54 cait: AngularJS-based AJAX circulation client
19:54 cait oh
19:54 interesting
19:54 wahanui interesting is sometimes good and sometimes bad
19:55 taylorSchmidt Hey guys, happy to be here!
19:55 khall bag had to run to the airport, he should be back soon I hope
19:55 pianohacker rangi: ping :)
19:55 rangi hey
19:56 pianohacker we want to meet in #koha or break off into another channel?
19:56 rangi might be easier in another
19:56 bag I’m back
19:56 pianohacker makes sense
19:56 khall agreed
19:56 pianohacker #fs ?
19:56 bag #csmkoha
19:56 pianohacker oh nvm
19:56 bag nevermind :P
19:56 rangi too late i already made one :)
19:56 bag is right
19:57 Sean joined #koha
19:57 pianohacker /join #kohaproject
19:58 Sean In the borrower info on the left side (in checkout or when viewing a patron) is it possible to add expiration date (in the block of data beneath the phone, where name, address, home library, email, etc currently are)?
19:58 HdezCortes Good I have problem with my server Koha Someone can help me??
20:06 rangi HdezCortes: we wont know if we can help or not, until you ask your question
20:10 nengard left #koha
20:11 bag bug 11703
20:11 wahanui bug 11703 is waiting for an answer, I started QA on it :)
20:11 huginn 04Bug http://bugs.koha-community.org[…]_bug.cgi?id=11703 enhancement, P5 - low, ---, kyle, Passed QA , Convert checkouts table to ajax datatable
20:23 HdezCortes my koha server displaying a page that is not you have to show it can account at the following address 200.88.48.100:8080
20:24 rambutan left #koha
20:25 kmlussier left #koha
20:30 fredericd joined #koha
20:31 rangi HdezCortes: im not sure i understand you sorry
20:39 jce joined #koha
20:44 jce Hey there.  Anybody on?
20:48 cait1 joined #koha
20:49 cait1 @wunder Konstanz
20:49 huginn cait1: The current temperature in Taegerwilen, Taegerwilen, Germany is 8.7°C (10:45 PM CEST on May 12, 2014). Conditions: Clear. Humidity: 72%. Dew Point: 4.0°C. Windchill: 9.0°C. Pressure: 30.01 in 1016 hPa (Rising).
20:55 pianohacker leaving now, will check in later
20:55 cait1: I'll get rancor on my test server and let you know when it's up later tonight
20:55 cait1 ah
20:56 now he is gone...
20:56 hm
20:58 jce So, anyone on here know anything about Koha?
20:59 mtompset Greetings, cait1. How goes the QA processing? :)
20:59 cait1 too busy for qa right now, maybe some later this week
21:00 mtompset jce, people usually just ask the question, and if someone knows how to help, they'll say. Everyone here generally knows something about Koha.
21:01 magnuse bag: HI
21:01 bag magnuse: HI
21:01 magnuse :-)
21:01 mtompset Also, jce, sometimes you're more likely to get an answer by asking the mailing lists.
21:02 magnuse, bag: Greetings!
21:02 bag :)
21:02 magnuse hiya mtompset
21:04 jce I'm working on a problematic Koha upgrade.  Ubuntu 12.04, Koha 3.14.  Created a new instance, trying to import old database.  Tried 'sudo koha-mysql <instance> < Koha_Backup_localhost.sql'.  Got "Access denied for user ... to database '<Name of old database instance>
21:04 rangi edit the .sql
21:04 near the top it will have a line use old database
21:04 take that out
21:05 then it will stop trying to restore to the old database
21:06 jce rangi:  (assuming you're talking to me, as that seems relevant)  Thanks, I'll check that out.
21:09 Ok, it has a command to CREATE DATABASE <Old_Database> and a USE command.  Should I get rid of them both?  is '--' a comment in an SQL file?
21:12 Assumed Yes and Yes, and it seems to be populating the database.  Thanks for the help, rangi.
21:17 BigRig joined #koha
21:19 jce Upgraded the database schema successfully.  Now I'm going to try rebuilding the zebra index with 'sudo koha-rebuild-zebra -f -v <instance>'.  This is installed from Debian packages.  Is it correct to sudo this from my regular user account, or am I supposed to log in (or su) as another user?
21:20 rangi no, doing it from your account is ok, as long as you use sudo
21:25 jce rangi:  Thanks.  Rebuilding now.
21:25 rangi cool
21:36 jce Next problem:  The old username and password doesn't work for the intranet.  This is an IP-based installation, it is not accessed over the Internet.  I get the logon screen at localhost:8080, but the old username/password doesn't work.
21:37 rangi login in with the one in the koha-conf.xml
21:37 mtompset sudo xmlstarlet sel -t -v 'yazgfs/config/pass' /etc/koha/sites/{the instance name}/koha-conf.xml
21:37 rangi and make a user, and give it superlibrarian permissions, then logout and login with that user instead
21:37 never use the password in koha-conf again after that (except if you delete your real user or something)
21:38 mtompset the system user name is koha_{instance name}
21:38 And follow rangi's advice. :)
21:46 jce Have to create a Patron Category.  Do I make up an arbitrary category code?  I assume Category type should be 'staff'.
21:49 rangi doesnt actually matter at all
21:49 the permissions are what matter
21:50 categorycodes dont really do anything, except give you more information
21:55 jce Ok, thanks rangi and mtompset.  Created a user.  Still getting no results from a search in OPAC on an author I know is in the holdings.
21:55 mtompset Did you do a full reindex?
21:55 Always a good idea to do a full reindex after getting your data into an instance.
21:57 jce I did this:  sudo koha-rebuild-zebra -f -v bcmc   Does the instance include koha_  i.e. koha_bcmc?
22:00 It said:  "Records exported: 3295" which is a plausible number.
22:01 mtompset If the instance didn't exist, you would know. :)
22:03 jce That's what I thought.
22:03 bag @wunder 93109
22:03 huginn bag: The current temperature in Westside, Santa Barbara, California is 32.4°C (3:03 PM PDT on May 12, 2014). Conditions: Clear. Humidity: 11%. Dew Point: -2.0°C. Pressure: 30.01 in 1016 hPa (Falling).
22:03 bag I’m melting
22:04 jce I have this in /var/log/koha/bcmc/opac-error.log:  [Mon May 12 16:55:39 2014] [error] [client 127.0.0.1] File does not exist: /usr/share/koha/opac/htdocs/opac-tmpl/css, referer: http://localhost/cgi-bin/koha/[…].pl?idx=au&q=borg
22:04 [Mon May 12 16:55:40 2014] [error] [client 127.0.0.1] [Mon May 12 16:55:40 2014] 404.pl: Use of uninitialized value in concatenation (.) or string at /usr/share/koha/lib/C4/Auth.pm line 391., referer: http://localhost/cgi-bin/koha/[…].pl?idx=au&q=borg
22:06 cait1 left #koha
22:11 jce FWIW, /usr/share/koha/lib/C4/Auth.pm line 391 reads as follows:  opaccolorstylesheet       => C4::Context->preference("opaccolorstylesheet"),
22:12 It looks as if some CSS stuff is missing from my installation, but that doesn't seem relevant to the problem of no results coming up in OPAC searches.
22:18 eythian hi
22:18 wahanui privet, eythian
22:21 mtompset Got to run. Bye.
22:21 Have a great day, #koha.
22:24 bag heya eythian
22:24 wahanui go back to bed, eythian
22:30 eythian I wish
22:33 irma joined #koha
22:35 eythian rangi or others: should a script in misc/load_testing be a dependency in C4::Installer::PerlDependencies?
22:36 I suppose it's an optional dependency
22:38 rangi yeah only optional
22:38 personally i think that that the load testing stuff should probably be its on repo
22:38 eythian Something has been added that isn't in debian, and I'm trying to avoid having to make a package for it :)
22:38 I think this'll be safe enough to blacklist.
22:40 papa joined #koha
22:49 bag man it’s so hot here - I’m having a beer early today
22:53 eythian @wunder nzwn
22:53 huginn eythian: The current temperature in Wellington, New Zealand is 16.0°C (10:30 AM NZST on May 13, 2014). Conditions: Mostly Cloudy. Humidity: 77%. Dew Point: 12.0°C. Pressure: 30.09 in 1019 hPa (Steady).
22:53 bag eythian: say you are in santa barbara and you could have a beer early with me :)
22:53 @wunder SBA
22:53 huginn bag: The current temperature in Santa Barbara, California is 31.0°C (2:53 PM PDT on May 12, 2014). Conditions: Clear. Humidity: 9%. Dew Point: -6.0°C. Pressure: 30.01 in 1016 hPa (Falling).
22:53 eythian sounds like a plan :D
22:55 OK, fingers crossed I have master building again and I can test the thing I was actually planning to test.
23:02 JesseM_away joined #koha
23:05 jce The Wiki page 'Koha_on_ubuntu_-_packages_long' says that "Koha 3.4.x or later no longer stores items in biblio records." and then shows how to rebuild the zebra index.  So I assume that the index is stored in another table in the same database.  What table is that?  I'm still unable to get any search results, and I'd like to look in phpmyadmin and see if the new index is really there.
23:06 eythian jce: "items"
23:06 it was always there, it's more that it's used a little differently post 3.4
23:07 jce Thanks eythian.  I'm now seeing a step I may have missed.  I hadn't run koha-upgrade-to-3.4
23:08 eythian ah yep, that's reasonably important.
23:08 jce :)
23:08 eythian although, you should still get search results without having run it
23:08 just you're likely to get twice as many items
23:09 jce Hmm.  I was getting nothing at all.  Well, I'm running it now, so we'll see what happens.
23:10 eythian it'll do a full zebra reindex when it's done, that may help things too.
23:12 dcook bag: Jealous
23:14 jce: I haven't read too much scrollback, but... the item data and MARCXML bib record are stored in MySQL tables, while the Zebra indexes are stored in a Zebra db (which you can query using yaz-client)
23:15 jce dcook:  Thanks.
23:16 koha-upgrade-to-3.4 completed, but still no joy.
23:16 Thought for sure that would fix it.
23:16 eythian jce: try sudo service koha-common restart
23:16 make sure everything is running
23:19 jce Looks as everything is running (except SIP server, but I don't think we're using that.)
23:19 eythian hmm
23:19 errors in /var/log/koha/whatever?
23:19 especially the zebra files
23:19 * dcook is curious what was printed out while re-indexing Zebra
23:20 eythian hmm yeah, any warnings there?
23:21 jce Farther up the irc log I posted about some errors in /var/log/koha/bcmc/opac-error.log, but they seemed to pertain to CSS.  I'll check the other stuff.
23:21 dcook jce: Yeah, no worries about opaccolorstylesheet. It's an optional stylesheet.
23:22 jce Records exported: 3295
23:22 ====================
23:22 REINDEXING zebra
23:22 ====================
23:22 17:53:43-12/05 zebraidx(15082) [warn] Record didn't contain match fields in (bib1,Local-number)
23:22 ====================
23:22 CLEANING
23:22 ====================
23:22 Zebra configuration information
23:22 ================================
23:22 Zebra biblio directory      = /var/lib/koha/bcmc/biblios
23:22 Zebra authorities directory = /var/lib/koha/bcmc/authorities
23:22 Koha directory              = /usr/share/koha/intranet/cgi-bin
23:22 BIBLIONUMBER in :     090$c
23:22 BIBLIOITEMNUMBER in : 090$d
23:22 dcook Useful link for pastes: paste.koha-community.org
23:22 jce: Are you using UNIMARC or MARC21?
23:23 rangi yeah that looks like unimarc
23:23 in marc21 its 999c and d
23:24 jce Hmm.  I thought we were using MARC21, but it's been long enough since I last worked on this, I may be wrong.
23:26 rangi you could look in the db, check the marcxml field in the biblioitems table for a record
23:26 jce So I may have a mismatch of my MARC record types between the database and the new server instance?
23:26 rangi could be, the record didnt contain match fields is suspicious
23:27 jcamins Looks like MARC21 from Koha 2.2.
23:27 Hi.
23:27 rangi hi jcamins
23:28 jcamins git?
23:28 wahanui git is, like, http://wiki.koha-community.org[…]Control_Using_Git
23:29 jce Does this tell us what we need to know?  "xmlns="http://www.loc.gov/MARC21/slim">"
23:29 This system was first installed in 2008, so it could be that we still have junk left over from Koha 2.2.
23:30 Though it has been upgraded a couple times since then.
23:30 eythian beware that many upgrades from 2.2 have had issues pop up further down the track
23:30 jcamins Like this one!
23:31 But, also, problems with database structure.
23:33 rangi that person who was the release manager for 3.0 has a lot to answer for
23:33 jcamins Including our Zebra configuration.
23:34 rangi yep
23:35 jce Looking back at my notes, the first install was in 8/07 on Ubuntu 7.04.
23:35 So, what would be my next troubleshooting step?
23:36 jcamins Unfortunately I'm not sure. I usually just export the MARC records, move the biblionumber and biblioitemnumber into the correct fields, and treat it like a migration.
23:37 eythian OK, _this_ time maybe I'll have master building again.
23:38 jce I've thought about installing Ubuntu 10.04 in a VM, reinstalling Koha 3.8 (which appears to be the previous version in use) and seeing if I can get it running that way again.
23:38 tcohen joined #koha
23:39 jce Would it be possible to do a migration with the database in the state it's in?
23:40 eythian tcohen: oh, I just emailed you
23:41 rangi jce: your idea of getting a 3.8 up is not a bad one
23:41 id do that, see if it is working there
23:41 then you have time to do an export and migration into a 3.14 (or 3.16 when its released)
23:42 you have the original backup still eh?
23:42 jce I was sort of hoping to avoid that, but I'll give it a try.
23:42 I do.
23:42 rangi if we we sure that the zebra/biblionumber mismatch is the only problem, you could try to fix that in place
23:43 but it might not be, .. for future, dont turn the old one off until the new one is tested and working :-)
23:43 jce Is there some documentation I should look at for migration?
23:45 Well, I hadn't planned on doing an upgrade at this time.  I ran some Ubuntu updates and things didn't go well, so I decided it was time to upgrade the OS.  This is a small library and they have only 1 machine for the server.  But it's a point well taken.
23:45 rangi *nod* we run into that a bit too
23:45 3.8.x will work fine with 14.04
23:45 you dont have to go back to 10.04
23:46 eythian 14.04 on packages is currently problematic
23:46 jce I'm using 12.04 ATM because of the package problem with 14.04.
23:46 rangi well the cavaet with 14.04 is they changed apache versions and apache broke backwards compatibility
23:46 in its config files
23:46 * eythian is going to be testing fixes for this today, assuming master finally builds.
23:46 rangi but yeah 12.04 would work fine
23:46 with 3.8.x, if thats easier
23:47 jce I'm actually setting Koha up for a second library as well, and was hoping to go straight to 14.04.
23:47 dcook jce: As for migration, it depends on what you want to migrate over.
23:47 eythian jce: well, all going well, we'll backport the fixes into 3.14.
23:48 jce All they're using this for is a card catalog.  They don't have any patrons defined, and they don't use it for check-outs.
23:48 eythian unfortunately it's not going to be perfect, the debian apache packages have introduced some bugs. They can be worked around though.
23:48 jce dcook:  so we really just need to migrate the holdings.
23:48 dcook jce: Sounds dead easy then. Dump the records out of it, run up a 3.8, import the records into that :).
23:49 Well, fix the records, I guess ;)
23:49 Should be as easy as moving those 090$c and 090$d fields to 999$c and 999$d.
23:49 Actually, you might not need to bother...
23:50 eythian this assumes your records are actually MARC21
23:50 dcook Yeah, there is that
23:50 jce I'm pretty sure they're MARC21.
23:50 rangi dcook: i wouldnt do it like that
23:50 id run up a 3.8
23:51 import the old backup
23:51 check it works there
23:51 then export the records from it, and load them into your new 3.14
23:52 ie, first id get it working with 3.8.x again so the library can work, then do the migration and test its all working ok, and then cut over
23:52 dcook Mmm, that's a good point.
23:52 Could run into problems if the item types, branches, and locations aren't the same...
23:53 Those'll need to be re-created in the 3.14 as well
23:54 jce rangi:  I think that's what I'll try.  Would I be exporting the records from Koha or is that something I should do in phpmyadmin?
23:54 rangi id export from your 3.8
23:56 jce So, should I change my package repositories, or just download a bunch of .deb files.  The latter sounds like dependency hell to me.
23:57 Or should I use a tar ball?

← Previous day | Today | Next day → | Search | Index

koha1