IRC log for #koha, 2012-07-09

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

All times shown according to UTC.

Time Nick Message
00:10 dcook joined #koha
00:10 dcook Allo allo
00:11 Is anyone else getting the error "Can't locate C4/Heading/MARC21.pm in @INC" when they try to change MARC 245 $a?
00:11 To elaborate further, is anyone else missing the folder C4/Heading ?
00:12 (for 3.8)
00:13 jcamins dcook: never seen anything like that.
00:14 dcook Hmm, I thought not. It seems to me that I've changed the 245 $a before as well, so I'm wondering if someone accidentally deleted that folder from our install
00:14 It's in our git, so either that or maybe it didn't install, like  bug 8135
00:14 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8135 critical, P1 - high, ---, chris, Pushed to Stable , Services Directory and itemrecorddisplay.pl File Missing After Install
00:15 jcamins dcook: the files are included in 3.8.x (in fact, we've had that file since 3.2 at least), so you probably need to reinstall from scratch.
00:16 dcook Or copy the folders across
00:16 jcamins No, don't.
00:16 You're missing unknown numbers of files.
00:16 Reinstall.
00:16 Copying folders can only lead to pain, suffering, and misery.
00:17 dcook I'm inclined to agree, although I'm not sure how what that will be received around here
00:17 jcamins Put it this way:
00:17 If you don't reinstall, the system is likely to go down hard *after* corrupting all the customers' data.
00:17 If you do, you have a bit of scheduled downtime.
00:18 And while you're at it, change the passwords.
00:18 dcook Oh?
00:18 jcamins dcook: think about it. Someone deleted core files from a production server.
00:19 There is no valid reason to be deleting any Koha file from that server, so chances are they got more files in the process of doing something dangerous.
00:20 Data corruption is almost inevitable.
00:20 Not from that file, but _I_ would never bet my customers' data on the assumption that "surely no one would have deleted anything else."
00:21 Or "surely no one would have *edited* any files while they were doing things they shouldn't to a production server running a gazillion catalogs."
00:22 dcook While I see your point, I'm not sure what I've done to provoke such hostility, jcamins
00:23 jcamins dcook: that wasn't intended as hostile.
00:23 dcook: if it came off as hostile, I apologize.
00:23 My point was, you're *right*, and here are a bunch of reasons to back that up if your employers don't like your opinion.
00:24 dcook I appreciate the apology. At first, that's how I was interpreting it.
00:25 jcamins No, not at all intended as hostile. However, sometimes it helps to say "this guy on #koha said X."
00:25 (especially when you said X first)
00:26 dcook Very true. I imagine that phrase will come up in conversation. Thank you for the list of reasons that you have provided.
00:28 jcamins Hopefully it'll help and you'll be able to rescue the server with only a bit of inconvenience when editing records for a little while.
00:32 dcook Well, there will be no inconvenience to anyone but me, since it's just a test instance
00:32 jcamins Oh, good.
00:32 * jcamins breathes a sigh of relief.
00:32 dcook I appreciate the concern :)
00:33 jcamins In that case, it's nice and easy. Just rerun the installer reinstall the files.
00:33 dcook The downside is that I will lose all the customizations that I've been working on
00:34 jcamins Aren't you using git for customizations?
00:34 I saw a couple of patches from you.
00:34 dcook At this stage, we're using git for customizations that we're putting back into the community
00:35 Some are changes that are very client specific, so they shouldn't/wouldn't be approved
00:35 jcamins Ah.
00:35 dcook We've also been quite eager to get a "working" version up
00:35 jcamins I recommend using git for everything, even if you're not actually going to be submitting it.
00:36 That way if you have a problem like this, you can just do "git reset --hard" and rescue the situation.
00:36 dcook Someone else suggested that to me too, and I quite like the idea
00:36 How do you test your patches though?
00:36 jcamins Usually directly on my git install.
00:37 dcook How do you mean?
00:38 jcamins Rather than using a standard install, I do a dev install, and just check out the branch I'm interested in testing.
00:39 dcook Ahh, that's what I thought you were meaning
00:39 I suggested that in the beginning, but it fell by the wayside
00:39 jcamins Much easier than modifying files in a standard install, then trying to keep track of the changes mentally.
00:39 dcook No doubt
00:39 jcamins I strongly recommend *against* that for production, but for development, that's the only way to go.
00:40 dcook Makes sense
00:40 So you commit your changes to your local master branch
00:41 * dcook ponders for a minute
00:41 jcamins Actually, I don't use a branch called "master" at all because it'd be too easy to get confused.
00:41 I have a branch called "cpspecial" which is the branch with all C & P's customizations.
00:42 dcook Do you put each customization in a different branch adjacent or beneath that one?
00:43 jcamins For customizations that are not suitable to submit to the community, I develop directly on that branch.
00:43 For everything that is being submitted, I actually develop against master first, _then_ backport to cpspecial (which is based on 3.6.x).
00:45 * dcook nods
00:46 dcook As I mentioned to you a while ago, I'm still quite new to git. With "git reset --hard", that takes you back to the beginning where you first cloned the git?
00:47 jcamins No, that takes you back to the state of the repository prior to whatever changes were last made and not checked in.
00:47 dcook Mmm, right
00:47 So then you don't lose commits when you reset
00:47 jcamins Exactly.
00:47 With a standard install, you would.
00:48 dcook Although you can peel back commits using "git reset ^Head" or some such, yes?
00:48 jcamins Exactly.
00:48 dcook I'm thinking that my new course of action is materializing before me :P
00:48 jcamins Or, if you just want to look and see what things were like two commits ago you could do "git checkout HEAD^^"
00:49 dcook Mmm, I seem to remember seeing that recently
00:49 jcamins And if you realize that you committed something you didn't want to a while ago, you can either do an interactive rebase ("git rebase -i origin/master" [or some other appropriate branch]) or revert ("git revert gitcommitid")
00:49 dcook So when you bring up a new library, do you just run a standard install from your git?
00:50 jcamins I actually use packages.
00:50 Which I compile off of my git repo.
00:51 Once I think I have everything the way I want it, I push it to my release repository (which is a regular git repo except it only has two remotes: git.k-c.org and my personal github account) and generate the packages/tarball/release stuff using this script: https://github.com/jcamins/rel[…]r/release-tool.pl
00:52 I then have another script which uploads the packages to my apt repository, and I can update my clients by just running `sudo apt-get update && sudo apt-get upgrade`
00:52 When I add a new client, I just run `koha-create --create-db newclient`
00:54 dcook Intriguing
00:55 I've been wondering about tarballs
00:55 Especially in terms of keeping up with new releases
00:55 jcamins I don't use them.
00:55 dcook You use a different type of package?
00:56 jcamins Oh, no one's told you how the Debian packages work?
00:56 My friend, you are in for a real treat. :D
00:56 * jcamins is overly fond of the Debian packages.
00:57 dcook I'm all ears :p
00:57 jcamins Rather than needing to manually download the tarball, and run through the installation process, the Debian packages allow you to just add an apt repository (there's one at debian.koha-community.org) and install Koha using: `apt-get install koha-common` and upgrade Koha using: `apt-get upgrade koha-common`
00:57 That second command also takes care of running updatedatabase.pl on *all* your instances.
00:58 The packages also provide a whole bunch of amazingly useful scripts for managing Koha installations.
01:00 * dcook drools
01:00 dcook Unfortunately, we're not on Debian :/
01:00 jcamins If you look in your git repo in debian/scripts, you'll see them.
01:01 koha-create will spin up a new instance, and allows you to configure pretty much everything that can be configured using one easy-to-automate command.
01:01 This also means you don't have to remember the administrative password.
01:01 (for each Koha instance)
01:01 That may sound insignificant, but that's actually a really big deal.
01:01 It means people are less likely to use the exact same password for lots of clients.
01:01 What are you running? Red Hat/CentOS?
01:01 dcook SuSe
01:01 jcamins Hrm.
01:01 I bet you could package Koha for SuSe.
01:03 dcook I find the prospect immensely desirable, haha
01:04 jcamins Of course, I can't seem to figure out what kind of packates SuSE uses.
01:05 Oh, RPM, maybe?
01:07 * jcamins considers downloading opensuse and trying.
01:07 jcamins Uh, OpenSUSE=free version of SusE, right?
01:08 dcook I do believe so, yes
01:09 jcamins Just 'cause I'm curious, I'm going to turn Koha's .deb into an RPM, and see what happens.
01:10 dcook I'm quite curious as well. I've been thinking for a while that there has got to be a better way of managing everything
01:12 jcamins Wow... opensuse looks a lot like Windows.
01:12 At least the progress bars.
01:14 dcook I've only ever interacted with it remotely, although I'm always interested in linux distros that look like Windows. I want to convert people to Linux, but there is a fair amount of resistance due to the visual dissimilarity
01:15 jcamins I don't actually know what the interface looks like yet, but the installer gave me pause because it looked startlingly like the installer for Windows 2k.
01:15 Now it looks less like the installer for win2k, but at first it did.
01:15 Okay, it's back to looking like a win2k install.
01:16 (with a lizard instead of a flag)
01:16 cjh dcook: one day we will have reactos
01:16 jcamins Hehe.
01:17 cjh we can just swap out windows for reactos and nobody will ever know...
01:17 dcook "The ultimate goal of ReactOS is to allow you to remove Windows® and install ReactOS without the end user noticing the change."
01:17 cjh :)
01:18 dcook Sounds like the start of a bad sci fi movie
01:18 cjh heh
01:18 dcook jcamins: did you use alien to convert from deb to rpm?
01:19 jcamins dcook: that's what I'm trying.
01:20 I like the opensuse installer, anyway.
01:23 dcook I'm not really sure why we use suse. I seem to remember hearing that Debian is the most popular option.
01:24 jcamins Yeah, Debian is the most popular by far.
01:25 dcook With reason, it seems
01:25 jcamins Probably you started with suse back when suse seemed like it would be better supported (?).
01:27 dcook I'll be sure to ask ;)
01:41 jcamins Hm.
01:41 Could someone on master take a moment to run `perl -c misc/cronjobs/thirdparty/Ta​lkingTech_itiva_inbound.pl`
01:46 dcook unable to locate Koha configuration file koha-conf.xml at C4/Context.pm line 360                                       . syntax error at misc/cronjobs/thirdparty/Ta​lkingTech_itiva_inbound.pl line 67, n                                       ear "$IN open"
01:47 Global symbol "$IN" requires explicit package name at misc/cronjobs/thirdparty/T                                       alkingTech_itiva_inbound.pl line 67. misc/cronjobs/thirdparty/Ta​lkingTech_itiva_inbound.pl had compilation errors.
01:47 jcamins Yeah, that's what I got, too.
01:47 Thanks.
01:47 dcook np
01:47 jcamins It seemed so odd that a new file wouldn't compile that I thought I ought to check whether others were seeing that, too.
01:48 dcook Fair enough. I hadn't even heard of this file until you mentioned it
01:51 jcamins It's new, for the Itiva TalkingTech automatic phone call service.
01:51 (and you now know everything about it that I do;)
01:51 dcook Haha
01:51 Yeah, I did a quick google :p
01:51 Sounds like it could be a good addition
01:51 Although I'm not sure how much people want to use phone calls anymore
01:55 Quick question, jcamins: when it comes to adding patches from the community, do you wait for individual releases or do you apply patches piecemeal?
01:55 jcamins That's a complicated question, actually.
01:56 As a general rule, I wait for releases.
01:56 (as RMaint for 3.6.x, I can be pretty confident that the patches that I care about will be getting in... ;)
01:57 However, I also backport features from 3.8.x and master, which obviously will *not* be in any official 3.6.x release.
01:58 dcook Ahhh, makes sense
01:58 jcamins So... both?
01:59 dcook Fair enough
01:59 While I'm definitely thinking of using a dev install and doing my customizations via git, I'm still not sure how I'm going to keep up with the community.
02:00 jcamins Are you tracking master, 3.8.x, or 3.6.x?
02:02 dcook At the moment, I'm tracking master for my testing, but I'm thinking of tracking just 3.8.x, when I actually start getting people up and running
02:03 jcamins Right. For development you should always track master, and rebase early and often.
02:03 If you wait for a release to rebase a development, you'll have to resolve lots of conflicts every time you want to submit a patch.
02:05 For clients, I would track 3.8.x and merge 3.8.x in once per month (or week) or something like that.
02:06 (I merge in 3.6.x one week after release)
02:06 dcook Mmm, and that's why you develop against master and backport
02:06 jcamins Right.
02:07 Also, it means that I get more eyes on the code
02:07 dcook Merge isn't the same as rebase, right?
02:07 jcamins Right.
02:08 rebase rewrites history, and puts all your work at the tip of the branch.
02:08 Merge leaves all your where it is, then just sticks the new commits from master on top.
02:08 dcook So, I would rebase my master branch against 3.8.x, and then merge in my customizations into that?
02:09 Hmm, or maybe not
02:09 jcamins That's a bit trickier, actually.
02:09 Do you have any customizations directly on your master branch?
02:10 dcook No, I always leave that one alone
02:10 jcamins Okay, then you just need to check out a new branch that you will merge all your customizations into.
02:11 For example: git checkout -b prosentient origin/3.8.x
02:11 In order to backport customizations that you developed against git, you will cherrypick them.
02:12 To do that, you figure out the commit id (git log customizationbranch will give it to you) then, while on the prosentient branch run: git cherry-pick commitid
02:15 dcook I think that I get the idea now. I haven't looked into cherry-pick yet though. I imagine that backporting would involve a lot of manual work
02:18 jcamins It depends.
02:18 As a general rule, not too much.
02:18 dcook Just where there are conflicts, so I suppose that would depend
02:18 So you've got your master branch that tracks origin/master
02:19 You've got your customization branch e.g. prosentient
02:19 Instead of rebasing prosentient, I would merge it with origin/3.8.x on a regular basis?
02:20 jcamins Exactly.
02:20 dcook What's the advantage to keeping that "history" that rebase would erase?
02:21 jcamins If you make a mistake, or run into problems down the line, you can figure out exactly where they came from.
02:23 dcook And this history is kept in the log?
02:23 To merge, I would need to first run "git fetch" too, right?
02:23 jcamins Right.
02:23 On both counts.
02:24 rangi rebase is not useful on any repositories you publish
02:24 because if someone clones, then you rebase and push, next time they pull, big ugly mess (youcan fix it, but its harsh)
02:25 rebase is fine for private branches
02:25 thats my rule of thumb anyway
02:25 dcook Mmm, I think I understand. Thanks, rangi.
02:26 And thank you so much, jcamins
02:26 jcamins You're welcome.
02:26 dcook I suppose the only thing missing now is how to add and update clients
02:26 from the git
02:26 rangi build debian packages
02:27 then apt-get upgrade :)
02:27 dcook We're running on SUSE :/
02:27 rangi ahh, sorry :)
02:27 tag
02:27 git tag is your friend then
02:27 tag a commit and thats the point you want to 'release'
02:27 then you can git checkout tagname
02:28 its easy to track exactly what is in production that way, as your branches grow
02:28 dcook I'm not sure that I follow you :/
02:28 rangi in git you can tag a commit
02:28 eg
02:29 in a koha repo
02:29 git checkout v3.08.02
02:29 jcamins Speaking of branches growing, I need to delete some branches.
02:29 rangi will get the exact point that the release was built from
02:29 dcook Ahhh
02:29 rangi even tho 3.8.x is now 67 commits in the future
02:29 so tag it when you want to upgrade your clients, you get a record of exactly where it was
02:30 so if you need to check it out to diagnose a problem
02:30 you havent had to memorise a commit sha :)
02:30 dcook That would be handy
02:31 So, let's say I download 3.8.0...I do some work...the community does some work...
02:31 rangi yup
02:31 dcook I installed from 3.8.0
02:31 Do I tag my git at 3.8.1 (for example), and then make a patch that takes into account all those commits?
02:32 rangi you could do that
02:32 i would however just git checkout yourtag
02:32 you only need to make a patch when you submit back to koha
02:32 jcamins rangi: bug 8383 and 8384 eagerly awaiting your signoff.
02:32 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8383 enhancement, P1 - high, ---, jcamins, Needs Signoff , Need test to check that Perl files will compile
02:33 rangi and that should always be against master
02:33 sweet can do
02:33 * jcamins calls it a night.
02:33 jcamins_away Good night, #koha.
02:33 rangi http://catalyst.net.nz/news/an[…]ibrary-joins-koha
02:33 dcook Thanks again, jcamins_away. You're a life saver!
02:34 But rangini, that would only put my dev install at the right place
02:34 How would I keep my clients (on standard installs?) up to date with my git? :S
02:35 rangi ahh
02:35 you could make new tarballs
02:35 but what you probably want to do is
02:35 move those to dev (git) installs (or make suse packages :))
02:36 * rangi hopes he is helping
02:36 dcook Any and all advice is helpful, rangini :)
02:36 rangi dcook: you should get prosentient to send you to wellington for a couple of days :)
02:36 dcook rangi *
02:37 That's not a bad idea...
02:37 rangi it's totally doable from this end
02:37 dcook I'll ask about it after lunch :)
02:37 rangi :)
02:38 dcook I would love to see your set up and learn more!
02:38 rangi excellent
02:38 dcook As for the dev (git) installs, I've heard that's not very desirable for production environments though
02:41 rangi well it can be dangerous if someone goes git pull
02:41 on a running system
02:41 ie, they are easier to mess up, so you have to build procedures around that
02:42 dcook Mmm
02:42 rangi like using tags, ie, never git pulling or deving or anything like that in your production installs
02:43 get it all tested and sorted
02:43 then tag
02:43 and checkout the tag
02:43 so you are always at a known (hopefully good) state
02:44 dcook Hmm, not sure that I follow now
02:44 I would have one git for development, but each client would need their own git to run a dev install, right?
02:45 So I'm not sure how I would keep them all synced
02:45 rangi yep, but they dont clone from the main koha-comunity one
02:45 they clone from your git
02:45 eg
02:45 http://git.catalyst.net.nz/gw?[…]oha.git;a=summary
02:46 now we dont run git in production, but we have branches for some of our clients who have nonstandard things
02:46 dcook And you keep the Catalyst git up to date through periodic merges?
02:46 rangi http://git.catalyst.net.nz/gw?[…]ads/hlt-packaging
02:46 we merge in releases
02:47 when we upgrade them, we try to keep them on the latest stable
02:47 and try to get everything back in upstream, so we dont have local changes
02:47 or as few as possible
02:47 dcook With the exception of those clients who have the nonstandard things?
02:48 rangi even those, we try to move to standard
02:48 i hate local customisations
02:48 dcook Me too
02:48 rangi its death by a thousand paper cuts
02:48 dcook They've been the bane of my existence lately
02:48 rangi *nod*
02:48 dcook My last estimate was 400-800 ;)
02:48 rangi http://git.catalyst.net.nz/gw?[…]ads/hlt-packaging if you scroll down
02:49 you'll see a yellow v3.06.04
02:49 thats the 3.6.4 release
02:49 (we merge at the tag point)
02:49 eg i could do
02:49 git checkout hlt-packaging
02:49 git fetch kc
02:50 (kc is the naame of the remote pointing at koha community)
02:50 git merge v3.06.06
02:50 and id have brought that branch up to that point
02:51 dcook The releases are tagged in the kc git?
02:51 rangi yep
02:52 http://git.koha-community.org/[…]p=koha.git;a=tags
02:52 dcook Interesting..
02:52 wahanui interesting is sometimes good and sometimes bad
02:53 dcook That's the second time I've fallen for that one :p
02:53 Hmm
02:53 rangi hehe
02:53 rangi?
02:53 wahanui I LIKE ALMONDS! HAVE SOME NUTS!
02:53 rangi it could be worse see :)
02:53 dcook lol
02:54 I'll remember that ;)
02:54 This looks like a good method for keeping my dev install up to date.
02:54 * dcook is immensely pleased about that
02:55 dcook I don't imagine that we'll choose to do dev installs for everyone though..
02:55 You mentioned making suse packages
02:55 I started looking up how to make a rpm package
02:56 Actually, nix the rpm idea for a moment
02:57 The releases are posted as tarballs. Cait mentioned that you can run Makefile to use these to upgrade an install
02:57 rangi thats right
02:57 dcook That seems fairly seamless, until I want to add something local
02:57 rangi yup
02:57 then you have to build your own tarball
02:57 dcook I was thinking that might be the case
02:58 rangi perl Makefile.PL --prev-install-log /path/to/koha-install-log make make test sudo make upgrade
02:58 dcook If I installed 3.8.2 over top of a customized 3.8.0 though..
02:58 rangi hmm those should be on sep lines
02:59 dcook Mmm, right. I remember reading that you needed the log in order to do an upgrade
02:59 What's "make make test"?
02:59 Or rather, what's its purpose?
03:00 rangi shoudl be
03:00 make
03:00 make test
03:00 sudo make upgrade
03:00 make test runs the unit tests, will hopefully catch anything fatal
03:01 before you cant stop :)
03:01 dcook Handy!
03:02 So that starts the upgrade process
03:02 rangi yep
03:02 dcook I assume that one is prompted for the location of the tarball at some point?
03:03 rangi you have to unpack the tarball
03:03 and run those commands in it
03:03 look in the INSTALL file, for the upgrade section
03:03 dcook Looking at it now :)
03:03 Well, maybe not..
03:03 I'm looking at the upgrade section of Makefile.pl :S
03:05 Hmm
03:06 When unpacking a tarball, do the files overwrite the existing ones?
03:07 rangi you unpack them in a dir
03:07 the sudo make upgrade copies them over the other ones
03:07 thats why do the test first
03:07 dcook Mmm
03:08 So if I was controlling everything through my git...
03:08 I wouldn't download the new Koha releases as tarballs
03:09 rangi nope
03:09 dcook I'd merge them into my git
03:09 rangi yup
03:09 dcook Then send out updates as tarballs
03:09 rangi yep
03:10 dcook If I had my dev instance and a prod instance on the same server, I would still probably want to use tarballs?
03:10 * dcook ponders
03:11 rangi hmm yeah 6 of one
03:11 dcook 6 of one?
03:11 wahanui 6
03:11 rangi half a dozen of the other
03:12 dcook If I understand correctly...because they have the same files but different structures?
03:12 rangi yep
03:14 dcook I suppose a person could always make a tarball from the git...apply it to a test standard install and then run a diff and install accordingly from there
03:14 Rather than doing the tarball upgrade to each one
03:14 rangi yeah you could do that
03:15 dcook Hmm, I'll have to ponder that one a bit more. It seems like I've got many of the options in front of me
03:15 Mind you...
03:15 What do you do in that case?
03:15 You have your dev git...
03:15 Run clients on debian
03:16 Try to not make local changes and upgrade only on stable releases?
03:16 Oh right, apt upgrade...
03:17 rangi thats it
03:17 * dcook thinks that getting a Debian server up and running would save a lot of hassle..
03:17 * wajasu there is a lot of good dev info in today's conversation :)
03:18 dcook Agreed. Thanks for all the info, rangi and jcamins_away
03:19 * dcook wanders off to pass on all the good things
03:19 wajasu i've been working on a shell script that builds a vm so i can develop on archlinux.  should work on suse.
03:21 i've never followed the make upgrade process.  i do a fresh install, and load up the database from a mysql backup.
03:47 cait joined #koha
03:52 cait morning #koha
04:07 mtj morning cait , hope your sleep was goood :)
04:12 cait hi mtj - it was :)
04:29 rangi ooohh how cool is this http://self.gutenberg.org/
04:34 cait hmm quite cool? :)
04:35 rangi :)
04:35 dcook Oooh, agreed
04:35 That one's getting re-posted tout de suite
04:35 Btw, morning, cait :)
04:45 cait morning dcook
04:45 :)
04:51 drojf boo for waking up at 4am and not being able to sleep again
04:52 cait it's 3 hours later... have you tried ever since?
04:52 drojf no i got up like 10 times and read stuff
04:52 buti feel not really functional
04:53 hmm. got this funny "all gtk-stuff looks grey and broken"-thing again. i don't like this day so far
04:54 * cait starts reading it law
05:06 druthb joined #koha
05:08 mtj well, i've finished my perl-critic-progressive script, for koha-qa :)
05:08 http://git.kohaaloha.com/?p=ko[…]tools/.git;a=tree
05:08 its actually 2 scripts
05:09 1 calls the other, for every file being checked
05:12 you can pass a 'commit' arg to it, so it will check the last $x commits for errors
05:12 $ cd koha/git
05:12 $ koha-qa-critic.pl -c 5
05:13 ... will check that last 5 commits for new perlcritic errors
05:19 mbalmer joined #koha
05:19 mbalmer m'ning
06:02 alex_a joined #koha
06:02 alex_a bonjour
06:02 wahanui hello, alex_a
06:03 cait hi alex_a and mbalmer
06:06 francharb joined #koha
06:07 francharb good morning #koha
06:12 ropuch Good morning
06:20 cait hi all :)
06:20 * cait loves the new dashboard > http://dashboard.koha-community.org/
06:21 cait it's updating in real time!
06:22 dcook_away I'm hoping to start upload quite a few in the next few days ;)
06:22 * dcook_away pretends to actually be away again
06:23 mtj cait:  fyi: i have some graphs running on koha-bugz too -> http://munin.kohaaloha.com/koh[…]koha_bz_head.html
06:25 tres wiggly
06:25 cait :)
06:44 bbl :)
06:44 cait left #koha
06:53 sophie_m joined #koha
06:55 laurence joined #koha
06:55 sophie_m hi #koha
06:59 rangi back
06:59 dcook Quick question for ppl
06:59 Is the 942 still used in 3.4+?
07:00 * dcook is doing some support for 3.2 and doesn't see the point in filling out the 942 when the cataloguer could just write out the call number in the 952/item record
07:00 rangi if you dont have itemlevel itemtypes switched on then yes
07:00 hmm call number no, but itemtype is still used in 942
07:02 matts hi #koha !
07:02 dcook Mmm
07:03 Thanks, rangi
07:03 reiveune joined #koha
07:03 dcook So cataloguers won't be able to automate call numbers with the except of specifying a default value in the bib framework?
07:03 reiveune hello
07:05 gaetan_B joined #koha
07:06 gaetan_B hello  !
07:07 * dcook mutters about non-standard cataloguing practice.
07:07 asaurat joined #koha
07:08 dcook Salut reiveune and gaetan_B :)
07:08 reiveune salut dcook :)
07:08 gaetan_B bonjour :)
07:09 dcook Ca va?
07:09 papa joined #koha
07:10 gaetan_B bien et toi ?
07:12 kf joined #koha
07:14 dcook Pas mal. Je suis un peu malade, mais il est 17 heures à Sydney, donc je suis assez heureux ;)
07:21 * kf waves
07:22 reiveune1 joined #koha
07:42 laurence joined #koha
07:59 Waylon joined #koha
07:59 Waylon hiya all
07:59 kf hi Waylon
07:59 Waylon Error:  Can't locate loadable object for module Net::Z3950::ZOOM
08:00 for .cpan/build/Net-Z3950-ZOOM-1.28-Xr3qsn/blib/lib# perl ../../t/25-scan.t
08:00 how do i fix?
08:00 kf i am not sure, what are you trying to do?
08:01 mtj simple, dont use cpan -> http://packages.debian.org/squ[…]t-z3950-zoom-perl
08:01 Waylon this is lenny
08:01 kf yes, and that
08:01 wahanui and that is, like, indeed a problem
08:01 kf Waylon: isn't lenny quite old now?
08:01 mtj simple, dont use lenny... ;)
08:01 Waylon yeah, but its what I know koha 3.0 can work with.
08:01 can koha 3.0 run on squeeze?
08:02 kf I see no reason why not - but I am not sure someone tried
08:02 I mean we probably use the same modules still, and some more
08:02 mtj i cant see why it wouldnt
08:04 Waylon what about libxml and perl-libxml versions?
08:04 vs koha 3?
08:05 mtj pass...
08:07 do some testing, sure
08:07 but take this situation as an opportunity to upgrade your OS
08:09 Waylon path to upgrade from lenny to squeeze without OS reinstall, is easy and works?
08:10 apt-get dist-upgrade?
08:14 mtj yep, thats the one
08:15 Waylon k. don't want to get hostgator's 'management' to do yet another reload.
08:15 damn idiots.
08:15 * Waylon is so fustrated, not having console access.
08:15 mtj yow, i didnt knwo it was possible to run a koha on hostgator
08:15 curious, how did you install zebra?
08:16 Waylon hostgator dedicated server
08:17 mtj yeah, no console is a great reason to stay away
08:17 Waylon 'managed' server
08:17 mtj ok, gotcha
08:17 Waylon screw up the os, and you just have to trust they can fix it.
08:18 * Waylon made one mistake with interfaces, told them about it.. they just backed up the useless OS and reinstalled lenny
08:18 Waylon wtf?
08:18 mtj yeah, i highly recommend linode , as a better option
08:19 Waylon we are moving to softlayer, hostgator's superior officer.
08:19 ... too much startrek.
08:19 softlayer is hostgator's datacenter.
08:19 it goes hostgator management -> old theplanet hardware -> softlayer datacenters
08:19 mtj (get a console, this time)
08:20 Waylon got one.. but yea... need to get this off of hostgator server #1 onto #2, because server #1's harddrive is on the way out.
08:21 then i can work on softlayer #1 and #2 koha 3.8 servers.
08:21 rangi http://dashboard.koha-community.org/ <-- pulling in the jenkins statuses now too
08:26 mtj rangi++  very nice , very nice :)
08:28 Waylon:  how were they cherry-picking without git?
08:29 Waylon probably were watching koha patches and just willynilly intergrating them.
08:29 some were used.. some were not.
08:30 so impossible to just rebase.
08:33 kf rangi++ jenkins++ :)
08:34 slef messy... if you want to try to figure it out, find yourself a good merge tool that can do "merge two directories with ancestor directories", but it's probably a lot of work
08:35 Waylon yea
08:35 just going to install koha 3.8 on a seperate server, and reimplement the code thats not part of default koha 3.0
08:36 mtj ... using git ;)
08:36 Waylon yes. each file, each change, gitted.
08:37 paul_p joined #koha
08:40 mtj Waylon:  what i would do , if i where you is - commit you current koha codebase against a 3.0 codebase
08:40 you would get 1 big commit, but it will show you everything thats changed
08:41 * Waylon nods.
08:41 kf mtj: I think the problem is that lots of things changed - so even if he gets it running, he will have to look through all and everything when moving to 3.8 :(
08:41 Waylon or just diff the two directories
08:41 kf ah right
08:41 for seeing the changes
08:41 Waylon yea.. i will have to get to know koha 3.8 quite intimately.
08:41 I guess ill become someone well versed in koha 3.8 by the end of all this.
08:42 mtj yep, git would give just a 'prettier' diff
08:42 slef Anyone seen this problem?  If I get "Please confirm checkout  Item Conversion technology: a complement to plastic recycling / (1) is checked out to Test (2). Check in and check out?" and click "Yes, Check Out (Y)", the same screen redisplays. Anyone seen this?
08:42
08:42 mtj hmm, no :/
08:44 * slef goes to test it on a master
08:45 slef by the way, some of the demos listed as running master are not: ByWater reports itself as 3.8.0, ESI as 3.2.5
08:45 * slef sees if he can edit the demo list but suspects he should not be allowed to
08:47 slef I can. Updating entries
08:48 what's head's dbrev?
08:50 3.09.00.024
08:50 so libriotech's is current
08:51 that's the only one
08:57 not a problem - just nice to be accurately documented
08:57 Waylon well. just did full upgrade to squeeze..
08:57 and rebooted
08:57 hope it comes back.
08:58 connnection timing out.
08:58 still timing out.
08:59 its back!
08:59 it worked!
08:59 kf yay!
09:02 paul_p good morning #koha
09:02 Waylon morning
09:02 evening
09:03 paul_p Maybe I should say "good time where you're #koha" ;-)
09:04 kf hi paul_p
09:04 drojf good morning paul_p
09:05 kf can you please revert bug 5981? :(
09:05 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=5981 normal, P5 - low, ---, alex.arnaud, ASSIGNED , OPAC: Add limits to search history
09:05 kf paul_p: I had massive problems with search until I deactivated opac search history, but no clue why. The problem is different than in 3.8 and 3.6 - but there is something seriously wrong with it.
09:07 Waylon whats that hidden dependancy that isn't listed, for koha 3.0?
09:07 kf hm no eythian today?
09:08 paul_p: and sorry to start your day with this - I am sure there are lots of nice things to push too :)
09:08 Waylon: why shoudl there be one? do you have a specific error?
09:08 * Waylon remembers there was one.
09:08 Waylon or was that for koha 3.2 upgrade? can't remember.
09:10 kf Waylon: and I don'tk now what you are talking about :)
09:10 there is a script to be run between 3.2 and 3.4 - do you mean that?
09:10 chris_n` joined #koha
09:10 Waylon hmm. n
09:10 no
09:11 nevermind, ill probably find out later.
09:13 gaetan_B the "place hold" button is missing from the MARC view in the staff interface in some of my installs but not all of them... Has anyone seen this before ?
09:13 kf hm all the same version?
09:14 gaetan_B kf: not all off them, but i saw this on two masters
09:14 kf hmmm
09:14 gaetan_B one has the button, the other hasn't !
09:15 kf maybe some difference in configuration?
09:15 * gaetan_B is looking in this direction...
09:25 paul_p_ joined #koha
09:26 reiveune joined #koha
09:26 asaurat1 joined #koha
09:29 slef gaetan_B: check tt files to see what might hide that, trace back to pl files that display the tt files, see if there's a syspref or incorrect logic.
09:33 drojf left #koha
09:37 drojf joined #koha
09:43 drojf joined #koha
09:49 drojf1 joined #koha
09:55 rangi !jenkins build koha_master now
09:55 jenkins_koha rangi: job koha_master build scheduled now
09:55 Starting build #778 for job Koha_master (previous build: STILL FAILING -- last SUCCESS #773 4 days 18 hr ago)
09:55 Project Koha_master build #778: STILL FAILING in 22 sec: http://jenkins.koha-community.[…]/Koha_master/778/
09:59 rangi !jenkins build koha_master now
09:59 jenkins_koha rangi: job koha_master build scheduled now
09:59 Starting build #779 for job Koha_master (previous build: STILL FAILING -- last SUCCESS #773 4 days 18 hr ago)
10:05 asaurat joined #koha
10:13 dpavlin joined #koha
10:14 clrh_ rangi: thanks for the dashboard, if I have ideas to enhence it, I will forward to you
10:15 rangi cool, or you can send a merge request too :)
10:16 https://gitorious.org/koha-dashboard/
10:16 im hoping someone will clone it and fix all my css/html :-)
10:19 papa joined #koha
10:51 jenkins_koha Project Koha_master build #779: NOW UNSTABLE in 51 min: http://jenkins.koha-community.[…]/Koha_master/779/
10:51 kf NOW UNSTABLE?
10:51 why now?
10:53 rangi before it couldnt build
10:53 now its finding the actual errors
10:53 http://jenkins.koha-community.[…]Build/testReport/
10:53 i think mtj spotted the broken template already, i saw a bug for that
11:06 slef rangi: the wine was lovely, thank you :)
11:12 rangi excellent :)
11:20 nengard joined #koha
11:25 jwagner joined #koha
11:35 jcamins_away rangi: any idea how I can make the syntax check not run BEGIN blocks?
12:25 jcamins If one more person agrees with Katrin and I, I will joyfully move the links outside the search table.
12:25 (referring to bug 8208)
12:25 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8208 enhancement, P5 - low, ---, jcamins, Signed Off , Add "create authority" button to auth_finder plugin
12:28 kf wizzyrea? ole... oh still on vacation...
12:31 mib_wuon95 joined #koha
12:32 mib_wuon95 good day
12:32 i have a question
12:32 jcamins Go ahead and ask it, and if anyone can help, they will. :)
12:35 Hm. A pity oleonard isn't here... I don't know how to turn a link into a button.
12:35 gaetan_B kf: i think i bothered you last week with my missing "place hold" button on the marc view : reiveune helped me find an explanation for that : bug 8390 (and you should be affected as well if we are not mistaken...)
12:35 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8390 normal, P5 - low, ---, koha-bugs, NEW , Place hold button is missing from the MARC view page
12:36 kf gaetan_B: I think probably noone notices because not all opacs have the marc view activated even .hm.
12:37 gaetan_B kf: that's a good point, i think most librarians would rather spare themselves the marc view !
12:37 NateC joined #koha
12:37 kf gaetan_B: but consistency is still good :)
12:39 mib_wuon95 i installed kyle hall's virtual machine koha 3.8. i imported a marc record with an item (with 952 marc field). the problem is that when i rebuild the zebra there is no item. am i missing something?
12:40 jcamins mib_wuon95: I've never used the virtual machine, but I'd imagine that it should work...
12:40 You checked the box that said "Import items"?
12:40 mib_wuon95 @jcamins: yap
12:41 huginn mib_wuon95: I'll give you the answer just as soon as RDA is ready
12:41 kf mib_wuon95: did you only stage it or also imported it?
12:41 mib_wuon95: import consists of 2 steps, first you stage the file, then you import it, following the link to "manage" your staged imports
12:41 mib_wuon95 and also I installed koha 3.8, installed available live cd, and installed kyle hall's 3.8 in a virtual machine (virtual box). I'm also having problem with items
12:42 @kf: yes, i did both
12:42 huginn mib_wuon95: I'll give you the answer just as soon as RDA is ready
12:42 khall bug 8391 needs so
12:42 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8391 enhancement, P5 - low, ---, kyle.m.hall, Needs Signoff , Cannot view reading record through staff client
12:42 kf mib_wuon95: don't use the @ :) our bots mean you are talking to them :)
12:43 mib_wuon95 oh i'm sorry kf. the last part is import this batch into the catalog
12:43 so it's a bug?
12:44 jcamins mib_wuon95: that's very unlikely.
12:44 We'd have lots more reports of that if it were a bug.
12:44 What fields did you have in your 952?
12:44 mib_wuon95 here: =952  \\$w2011-10-24$p033073hp$r2011-10-24$40$00$6F__KPM_00041_W55​_W54_2000$915302$bLLS$10$o(F) KPM 41 W55 W54 2000$d2002-12-10$70$cGEN$2l​cc$g695.00$yBK$aLLS$iMR_02 1177; MD_$kR_; PO_; PD 00668
12:45 jcamins Hm.
12:45 mib_wuon95 that data was downloaded from a working 3.6 machine
12:45 jcamins khall: is there anything special about the vm appliance?
12:46 khall jcamins: only the 'koha management console' I wrote. Other than that, it's a basic dev style install
12:47 jcamins Hm.
12:47 mib_wuon95 the first 2 virtual machines of khall were very helpful (2.3 and 3.6) our local install were run through khall's vm :)
12:47 khall :-D
12:47 mib_wuon95 2.3 -> 3.2
12:48 This time i'm having problem with "No physical items for this record"
12:49 drojf joined #koha
12:49 mib_wuon95 Not only with a small import from stage marc record but also from previous data migration
12:49 khall mib_wuon95: if you use koha to create an item on a record, then rebuild zebra, does it show up?
12:50 mib_wuon95 ..of about more than 10000 records.
12:52 jcamins kf: I have decided we are a quorum wrt bug 8208.
12:52 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8208 enhancement, P5 - low, ---, jcamins, Signed Off , Add "create authority" button to auth_finder plugin
12:52 jcamins khall: aren't you usually kyleh?
12:53 khall jcamins: indeed
12:53 samuel joined #koha
12:53 samuel hi everybody
12:54 alex_a joined #koha
12:54 mib_wuon95 khall, there is an item
12:54 jcamins Why the change?
12:56 mib_wuon95 and is there a way that when I import through stage marc record, the biblioitem should be used is the one in 999$c or 999$d?
12:57 edveal joined #koha
12:57 jcamins mib_wuon95: biblionumber is in 999$c, and biblioitemnumbers is in 999$d.
12:58 mib_wuon95 sorry, i mean 952$9 which is the itemnumber right?
12:58 jcamins Ah. No, you can't keep itemnumbers.
12:58 libsysguy joined #koha
12:58 jcamins At least, I don't think you can.
12:59 mib_wuon95 in next koha maybe? :)
12:59 jcamins mib_wuon95: I doubt it.
12:59 I can't see any use for that.
12:59 (and implementing it would be non-trivial)
13:00 mib_wuon95 like if i'm having trouble with mysql import (dump) of records and items, i could have the option of importing instead the marc records of my previous koha machine?
13:00 jcamins Sure, but you don't need to keep itemnumbers to do it.
13:01 That will work fine right now.
13:01 (or should... once I finish what I'm working on, I'm going to try importing some items)
13:02 Actually, if you're migrating from 3.6 to 3.8, why don't you just use mysqldump to export the old database, and reimport the entire database?
13:02 mib_wuon95 i actually did that
13:02 but i instead tried to work with small data, one one record with one item
13:03 but i still had the same problem of not having physical item for my records
13:03 jcamins Oh, so there were no items showing up even when you did a complete database dump?
13:03 mib_wuon95 yap
13:04 after a rebuild
13:04 zebra rebuild
13:04 jcamins Hm.
13:04 mib_wuon95 -b -r -v
13:04 and -x -b
13:04 alex_a1 joined #koha
13:04 jcamins This sounds like a misconfiguration to me.
13:05 I can definitely tell you that upgrading from 3.6.x works.
13:05 mib_wuon95 i tried it actually with kyle hall's koha 3.8 vitual machin]e
13:05 i just imported the mysql
13:06 jcamins Did you edit any files on the virtual machine?
13:06 mib_wuon95 ..rebuild the zebra
13:06 i didn't
13:06 jcamins Okay.
13:06 mib_wuon95 i installed webmin
13:06 to make things easy
13:06 jcamins kyleh: I don't suppose you've seen this behavior on the virtual appliance before?
13:07 kyleh jcamins: no I can't say I have.
13:07 ago43 joined #koha
13:07 mib_wuon95 i'm more of a librarian actually with modest IT skills :)
13:07 jcamins mib_wuon95: did you run the remove_items_from_biblioitems.pl script at some point?
13:07 paul_p_ mib_wuon95 = a limit you can find with trying this is if you've a different MARC flavour or MARC configuration than the one the virtual machine has
13:07 mib_wuon95 i installed phpmyadmin too in the virtual machine
13:08 paul_p_ (morning jcamins & kyleh & mib_wuon95 & all other americaners -south or north-)
13:08 mib_wuon95 but i did this also with 3.2 and 3.6 but has not experience this problem
13:08 paul_p_ mib_wuon95 ah, so that's probably OK, unless kyleh changed his configuration in the meantime ! kyleh did you do something like that ?
13:08 kyleh good afternoon paul_p!
13:09 There are no unusual configuration settings in the virtual appliance
13:10 * kyleh follows the debian.install guide in git to create the koha virtual appliances
13:10 jcamins kf: follow-up to bug 8208.
13:10 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8208 enhancement, P5 - low, ---, jcamins, Signed Off , Add "create authority" button to auth_finder plugin
13:13 kf yep, its on my list no
13:13 w
13:31 ryehex joined #koha
13:35 ryehex I created a new box with debian 6, koha 3.8 (using apt-get) then connected the export of my old koha db (from v3.0) and installed my instance. Then did the update to 3.4 script.
13:36 now if i login to the admin and search ALL i get results. However if I narrow the search to a specific Library I see always get no results. Any Idea of why that would be? Thanks
13:36 Waylon ooo. hows it going ryehex ?
13:37 ryehex good
13:37 Waylon hmm... is library, a function of items or biblioitems?
13:37 jcamins ryehex: do you have items attached to all your records?
13:38 Waylon with items no longer being exported into marc for zebra, how does zebra search?
13:38 or does items create marc xml as the export occurs?
13:39 jcamins Waylon: the latter.
13:40 ryehex for the book i searched it should have had an item for that record. It showed up in the list when I searched all. but when I narrowed the search there was no results
13:40 jcamins How did you narrow the search?
13:41 Waylon you mean, by branch: ?
13:41 ryehex on the advanced search screen I chose a specific library in the Individual libraries: dropdown
13:42 yea branch
13:42 jcamins ryehex: did you check the "Availability" box?
13:43 paul_p_: I don't know if you noticed, but I did a follow-up to address the issues that Frere Marie found with bug 8268.
13:43 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8268 enhancement, P5 - low, ---, jcamins, Passed QA , Koha should offer way to backup entire db
13:47 ryehex hmm. with or without "Availability" checked it gives the same result: No results match your search for 'kw,wrdl: hunger games' with limit(s): 'branch:Kinkora Regional High School' in PEI School Library System Catalog
13:49 maximep joined #koha
13:59 gaetan_B IntranetBiblioDefaultView doesn't seem to have any effect, or am i mistaken ?
14:04 jcamins ryehex: and when you look at a record does it say it's at Kinkora Regional High School?
14:04 joubu++
14:12 ryehex yea, I tried to search by the exact barcode for a book. same..no results. seems like the search only works across 'all branches'. and only when no extra parameters are being set into the search
14:13 paul_p_ jcamins yes, i've seen the follow-up for bug 8268, don't worry
14:13 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8268 enhancement, P5 - low, ---, jcamins, Passed QA , Koha should offer way to backup entire db
14:13 jcamins paul_p_: with the quotes in my comment, it's so long I was concerned you might have gotten bored. ;)
14:13 ryehex: if you search for exact barcode it finds the book, but when you set the branch, it doesn't?
14:18 * wizzyrea waves
14:18 ryehex no sorry. the only time I could get any results was doing a 'keyword search' where  'individual libraries=all libraries'. any other setting changes causes no results to be returned.
14:19 jcamins ryehex: your items are not being indexed, tehn.
14:19 *then
14:20 ... are you using the 3.8 Koha Virtual appliance from Kyle Hall?
14:23 talljoy joined #koha
14:24 jcamins We were just talking about a similar problem.
14:27 ryehex no. I downloaded Debian 6 then used apt-get to create koha on my VM. I Also did the entire process on a different server actually running Debian 6 (no virtual machine) and it had the same results with the search
14:30 jcamins Okaay.
14:31 fredericd With 3.8 and hourly loan, there is something changed on Check Out page. Does anybody else notices this changement (regression)?
14:32 wizzyrea what change
14:32 wahanui hmmm... change is quite new
14:33 wizzyrea the first question?
14:33 wahanui "What are you trying to do?"  "What is the goal?" or "What problem are you experiencing?"
14:33 JesseM joined #koha
14:33 fredericd In 3.6, there is a 'Previous Checkouts' section, and a 'Current sessions' section.
14:33 jcamins ryehex: that was not a dubious "okay." That was a typo. ;)
14:34 ryehex: and you said you ran the remove_items_from_biblioitems.pl script, right?
14:34 fredericd In 3.8, you have a mix of both sections, so you can't see separetly the check outs you've just done
14:34 wizzyrea you mean books you checked out say, yesterday
14:34 separated from the ones you checked out today
14:34 fredericd yes
14:35 wizzyrea 1s
14:35 ryehex yea. well I ran this 'sudo /usr/sbin/koha-upgrade-to-3.4' which calls that script
14:37 jcamins Yeah, that should do it.
14:37 Hm.
14:37 That's really weird.
14:37 mib_wuon95: I'm thinking it might be a bug after all, though it's hard to see how no one has reported it before today.
14:38 Unfortunately, I have to head into the city and can't troubleshoot.
14:38 gaetan_B fredericd: is it bug 8043 ?
14:38 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8043 normal, P3, ---, kyle.m.hall, Pushed to Stable , today's checkouts are in Previous checkouts in circulation.pl
14:39 wizzyrea I don't see previous checkouts at all anymore
14:39 fredericd wizzyrea: That's it
14:40 gaetan_B: It seems it is this bug
14:40 mib_wuon95 jcamins, so we should file a bug on my query?
14:41 wizzyrea and with the patch it's working
14:41 on current master I mean
14:41 of course, because it's been pushed and stuff.
14:42 jcamins_away mib_wuon95: yeah, I think so. If someone is able to determine that it is *not* a bug, it will be marked invalid. But two people have reported this problem today, which makes me think maybe there's something odd about 3.8.2.
14:43 mib_wuon95 okay, haven't filed a bug before, will try today
14:43 drojf kyleh: i cannot reproduce bug 8391. i see "Checked Out" as return date in circulation history, no error
14:43 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8391 normal, P5 - low, ---, kyle.m.hall, Needs Signoff , Cannot view reading record through staff client
14:45 fredericd Thanks wizzyrea and gaetan_B for you quick response... problem solved.
14:45 * wizzyrea points at gaetan_B - he fixed it ;)
14:46 jcamins_away fredericd: before I leave... do you accept pull requests for Koha::Contrib::Tamil?
14:47 fredericd yes, of cours
14:47 course
14:47 jcamins_away :)
14:47 I added a daemon that handles packages.
14:48 fredericd ? Could you say more about that?
14:48 jcamins_away The daemon that you had can only handle one instance.
14:49 So I wrote a daemon that will get a list of all the instances created by the packages, then start an indexer daemon for each one.
14:50 oleonard joined #koha
14:50 jcamins_away I'd like to one day get it so that there's only one event loop, but I haven't figured out how to do that yet.
14:50 fredericd jcamins_away: what will happen if you add or remove an instance?
14:50 jcamins_away fredericd: it doesn't automatically detect it, so you have to restart the daemon.
14:50 I'd like to improve that part of it, too.
14:51 fredericd It doesn't matter that much having multiple indexing daemon running simultanousely
14:51 and that way you can leave to the sysadmin the task of starting/stop daemon
14:51 when enable/disabling instances
14:51 jcamins_away Oh, all the package daemon does is makes sure that they all get started.
14:52 kf bye all :)
14:52 kf left #koha
14:53 jcamins_away I also added initial support for indexing based on update time rather than zebraqueue, but, again, I haven't finished it yet.
14:55 * jcamins_away closes up and heads into the city.
15:17 mib_wuon95 joined #koha
15:22 Waylon oh f...... different perl versions have different undefined value rules?
15:27 gaetan_B bye !
15:28 hdl joined #koha
15:33 talljoy joined #koha
15:39 cait joined #koha
15:39 logbot joined #koha
15:41 oleonard Hi cait, #koha
15:41 cait hi oleonard :)
15:41 how was your vacation?
15:41 oleonard It was a lot of fun!
15:42 * oleonard is buried in email now
15:43 reiveune left #koha
15:45 cait oleonard: normal :)
15:46 after 2 weeks I need a day to read mails, it's insane
15:46 oleonard: photos? :)
15:46 oleonard Approximately 2000 of them :)
15:47 cait ok, maybe I should ask for a best of then :)
15:47 have you found that in your mail already? http://dashboard.koha-community.org/
15:47 oleonard Yes, that's cool
15:49 asaurat left #koha
15:49 cait it totally is :)
15:49 bbl :)
15:52 tweetbot` joined #koha
15:53 Waylon figured out the secret sauce. CGI::Session::Serialize::yaml
15:54 oleonard tweetbot?
15:56 Waylon !tweet hi
15:57 hmm..
15:57 oleonard What was that supposed to do?
15:57 Waylon hoping it would do soemthing
15:59 melia joined #koha
16:00 wizzyrea oleonard, welcome home!
16:00 oleonard Thanks wizzyrea
16:05 paul_p joined #koha
16:09 SJeffery joined #koha
16:18 bshum_ joined #koha
16:22 SJeffery If you add an author that has an authority record it seems to delete all subfields in the record you are working on except $d. Is there any way to get it to leave other fields such as $r and $4?
16:23 jcamins_away SJeffery: not yet.
16:23 nengard joined #koha
16:24 jcamins_away However, that should be possible in the future, once these various authority developments are finished.
16:24 SJeffery Curses!
16:25 So the authority work does not add the feature, but it allows for its future development, correct?
16:41 laurence left #koha
16:54 mveron joined #koha
17:06 oleonard Bug 8374 is one reason why I do not like the JavaScript "print" function.
17:06 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8374 enhancement, P5 - low, ---, oleonard, NEW , Option to print all entries of a list/cart in a user friendly format
17:08 ago43 joined #koha
17:08 mbalmer joined #koha
17:09 mbalmer evenueng
17:10 mveron joined #koha
17:11 mveron Hi #koha
17:11 mbalmer hi hi, mr. holiday ;)
17:11 brylie joined #koha
17:12 mveron :-)
17:22 edveal joined #koha
17:26 cait joined #koha
17:38 ago43 joined #koha
17:38 slef JOOI anyone know of an educational consortium using Koha?
17:42 libsysguy joined #koha
17:43 ago43 joined #koha
18:01 adnc joined #koha
18:02 drojf left #koha
18:27 drojf joined #koha
18:30 brylie joined #koha
18:31 chris_n` joined #koha
18:44 brylie joined #koha
18:49 jenkins_koha Starting build #89 for job Koha_3.8.x (previous build: SUCCESS)
18:49 slef all quiet on the Koha front
18:50 * oleonard is in a post-lunch stupor
18:51 cait :)
18:51 how is the inbox? :)
18:53 rangi new stat on the dashboard, activity of the previous day (utc time)
18:53 oleonard Inbox is improving, thanks
18:53 Hi rangi
18:53 cait nice!
18:54 rangi heya oleonard :)
18:54 cait I like th random bug :)
18:54 well I like everything :)
18:54 * rangi sneaks off to feed the kids
19:21 brylie_ joined #koha
19:30 mbalmer joined #koha
19:31 eythian joined #koha
19:35 trea joined #koha
19:41 jenkins_koha Project Koha_3.8.x build #89: SUCCESS in 52 min: http://jenkins.koha-community.[…]ob/Koha_3.8.x/89/
19:41 * semarie-koha: Bug 3280 : Restrict Send basket feature
19:41 * m.de.rooy: Bug 3280 Followup for privacy issue on X-Orig-IP in mail header
19:41 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=3280 normal, P3, ---, semarie-koha, Pushed to Master , opac/opac-sendbasket.pl security leaky
19:47 nengard left #koha
19:53 cait oleonard++ :)
19:53 already back to writing patches!
19:53 oleonard Can't resist
19:53 cait we are lucky you can't :)
19:54 oleonard I'd been meaning to fix that bug for a while
19:54 mbalmer cait, please fix the remaining problems.  thanks, the management.
19:55 cait all of them?
19:55 mbalmer sure.
19:55 cait ok, i will rewrite in java then
19:55 :P
19:55 * cait doens't even like java much
19:55 cait mbalmer: I got a program for the bis conference today :)
19:55 mbalmer doh…..
19:56 rangi he said fix the problems, not spend 7 years writing specs and libraries and then making the problems worse cait!
19:56 cait hehe
19:56 hey, I am a librarian!
19:56 * cait hides
19:57 mbalmer I am book!
20:01 slef I'm a bookend.
20:02 cait slef: red or green?
20:03 oh
20:03 I filed bug 8400
20:03 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8400 enhancement, P5 - low, ---, gmcharlt, NEW , Placing holds in staff creates lots of warnings in the logs
20:03 cait where are the fireworks?
20:04 oleonard You only get those for the thousands
20:04 cait ah... well, i can continue testing
20:04 no problem :P
20:06 kathryn joined #koha
20:07 trea-phone left #koha
20:10 * cait puts some too soft baileys fudge in the middle of Koha
20:10 cait eat at your own risk
20:10 brylie joined #koha
20:12 kathryn good morning all, ugh cait too early for baileys fudge even for me :)
20:12 cait hm.... take some for lunch?
20:12 and it's cooked
20:12 i don't think much alcohol is left
20:14 libsysguy joined #koha
20:18 cait ... it's really not that bad
20:18 only a bit soft
20:21 mtj hmm, how do i add a new dependancy to Koha?
20:21 ago43 joined #koha
20:21 chris_n` joined #koha
20:21 mtj ie: which files has i gotsta edit?
20:22 slef mtj: yes, probably.
20:22 * slef looks
20:23 mtj koha_perl_deps.pl calls -> C4::Installer::PerlModules...
20:23 slef that's the thingy
20:23 PerlDependencies.pm isn't it?
20:23 mtj ah, got it
20:23 yeah ;)
20:24 ta
20:24 slef I think you may also want to update debian/control*
20:24 rangi yes you do
20:25 and then the INSTALL files too
20:25 or whatever they point at like misc/something something
20:25 slef rangi: we should write this shit down
20:25 rangi either that or update the INSTALL files to stop telling people to refer to that file
20:25 slef misc/something something uses PerlDependencies.pm I think
20:26 rangi i dont think so, there are static files in there
20:26 lists of packages
20:26 should go away
20:26 slef oh you mean install_misc/debian.packages as mentioned in INSTALL.debian?
20:26 chris_n` joined #koha
20:26 rangi and tell people to just run koha_perl_deps.pl
20:26 yeah
20:26 either that needs to be brought up to date, or go away
20:26 slef koha_perl_deps.pl doesn't tell you which debs to install
20:26 rangi it could
20:27 slef yeah
20:27 rangi another key in the hash maybe?
20:27 cait o
20:27 h
20:27 right, I have to do a follow up for the package I added
20:27 slef or just read debian/control*
20:27 cait there was something... on a bug somewhere
20:27 rangi that too
20:30 oleonard Bye #koha
20:30 rangi cya oleonard
20:32 wizzyrea left #koha
20:32 wizzyrea joined #koha
20:48 mtj !twadd #kohails kohails
20:48 tweetbot` OK, now watching for '#kohails kohails'
20:48 chris_n` joined #koha
20:49 cait mtj: is the tweetbot yours? :)
20:49 mtj++
20:49 what does it do?
20:50 drojf cait: tweet something and try?
20:50 :)
20:50 cait my account is not public, doubt it would work
20:50 mtj yes, it watches twitter for keywords...
20:50 drojf ah. no probabyl not
20:51 cait mtj: cool :)
20:51 drojf probably even
20:51 cait I am still looking for the one who owns the bot that posts the git commit messages to twitter...
20:51 because the links in those tweets don't work
20:51 chris_n` joined #koha
20:52 mtj cait,  thats rangi
20:53 rangi and it cant be fixed
20:53 cait oh
20:53 rangi its twitter double encoding
20:53 cait meh.
20:53 ok
20:53 mtj aah, i'd like to prove you wrong there chris :)
20:53 rangi weve tried dlvr.it and googles feed2tweet thing, both dont work
20:53 you tried
20:53 cait mtj: do it! heh
20:54 rangi and it didnt work, its using the method you told me to
20:54 and they still dont work
20:54 mtj meh, i dont think i *personally* tried the method i suggested to you
20:54 (so, was still kinda hoping it might work :) )
20:55 cait maybe remove the links then?
20:55 rangi Bug 8233 follow-up fixin DBRev goo.gl/fb/WHGLC
20:55 huginn 04Bug http://bugs.koha-community.org[…]w_bug.cgi?id=8233 enhancement, P5 - low, ---, jonathan.druart, ASSIGNED , New search engine layer - introduce solr without breaking anything else
20:55 rangi is what it says
20:56 and it still munges the url
20:56 im just killing the whole thing
20:56 cait bad twitter, no cookie for you!
20:57 mtj yeah, bad birdy
20:59 !twadd kohails
20:59 tweetbot` OK, now watching for 'kohails'
21:00 drojf hm. somebody tweet already :D
21:00 cait drojf: retweet rangi#s new blog post? :)
21:00 mtj /me just did...
21:00 cait or a note about the vote or the awesome dashboard!
21:01 drojf i dont tweet
21:01 cait btw
21:01 drojf maybe i should start
21:01 cait drojf++ # for the voting reminder :)
21:01 @karma drojf
21:01 huginn cait: Karma for "drojf" has been increased 17 times and decreased 1 time for a total karma of 16.
21:01 tweetbot` Twitter: @KohaBugs: "test-tweet for #kohails hashtag"
21:02 drojf yeah works
21:03 rangi drojf: you can use identi.ca and get it to tweet for you, thats what i try to do
21:04 drojf i had an identi.ca account once. very long ago. never used it. remembered that a while ago but either they deleted it or it was not the username i thought :)
21:04 * cait hunts blood sucking little monsters
21:04 drojf vampire dwarfs? cool
21:06 cait I wish
21:06 I can hear it, but not see it
21:06 but can't sleep while I hear it...
21:07 edveal left #koha
21:10 liw I use both identi.ca and twitter, but haven't linked them (and I'm unsure about keeping twitter)
21:11 drojf woohoo. we will have kohacon in Not completed or Not displayed
21:12 rangi lol
21:12 liw: yeah im conflicted about twitter, it does work well in promoting koha though
21:13 cait drojf: lol
21:13 is that some white spot on the map?
21:15 alex_a joined #koha
21:59 tweetbot` Twitter: @kohails: "#kohails  Choosing something to sign off http://t.co/At0QZJdS"
22:06 maximep left #koha
22:24 tweetbot` Twitter: @ByWaterSolution: "Koha, LDAP, And You! http://t.co/XiA81yWf #kohails"
22:24 ago43 joined #koha
22:27 NateC joined #koha
22:38 libsysguy ahh how did my post end up on the tweetbot!?!
22:38 lol
23:23 jcamins Wow... EBSCO took over Book Review Digest Plus.
23:24 * jcamins officially dislikes EBSCO's new unified look.
23:30 Irma1 joined #koha
23:47 BobB joined #koha
23:48 hankbank joined #koha
23:52 papa joined #koha

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

koha1