Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Friday, November 4th, 2011

< Thursday, November 3rd, 2011Raw Log FileSaturday, November 5th, 2011 >
#TimeNickMessage
#01:25:04jamesrf has quit IRC
#01:27:03jamesrf has joined #evergreen
#02:57:33bshum@later tell moodaepo Lost items are weird. Like https://bugs.launchpad.net/evergreen/+bug/851000 happens to us all the time, where we end up telling library staff to manually "fix" things.
#02:57:33pinesol_greenbshum: The operation succeeded.
#02:59:35adrienne has quit IRC
#02:59:40adrienne has joined #evergreen
#03:00:59AaronZ-PLS has joined #evergreen
#03:03:10AaronZ-PLS has quit IRC
#05:42:38_bott_ has quit IRC
#05:43:14_bott_ has joined #evergreen
#06:07:31wlayton has joined #evergreen
#06:22:24darshan has joined #evergreen
#06:24:04darshani am trying to create an action trigger
#06:25:03darshanand To run the action triggers,i need to run the trigger processing script
#06:25:18darshanbut i am running it i am receiving an
#06:25:19darshansession error
#06:25:23darshansuch as
#06:26:32darshanrouter@private.localhost/open-ils.trigger is not connected to the network
#06:26:44darshanne1 wud say on this
#07:12:27wlayton has quit IRC
#07:19:05csharpdarshan: you'll need to go back through these steps: http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors
#07:40:25Dyrcona has joined #evergreen
#07:43:54darshan has quit IRC
#08:31:15fortin has joined #evergreen
#08:31:37AaronZ-PLS has joined #evergreen
#08:39:02dbwells_ is now known as dbwells
#09:10:27darshan has joined #evergreen
#09:12:03Meliss has joined #evergreen
#09:12:17darshanam trying to create an action trigger,and To run the action triggers,i need to run the trigger processing script,,but i am running it i am receiving an,session error,such as,router@private.localhost/open-ils.trigger is not connected to the network,ne1 wud say on this
#09:15:04raynerj has joined #evergreen
#09:15:38csharpdarshan: you missed my reply earlier. You'll need to go back through these steps: http://evergreen-ils.org/dokuwiki/doku.php?id=troubleshooting:checking_for_errors
#09:17:55wlayton has joined #evergreen
#09:19:48akilsdonk has joined #evergreen
#09:25:10dbs has joined #evergreen
#09:25:11dbs has joined #evergreen
#09:38:15wlaytonGoing through the OpenSRF install, I think the instruction to "chown -R opensrf:opensrf <prefixDIR>" is missing from the OpenSRF README file
#09:39:15dbswlayton: ooh, sounds like a good catch
#09:39:45dbsalso, great to see wlayton again!
#09:40:50dbsReally should teach the installer to do the chown'ing, come to think of it; but I'll definitely add that step to the instructions
#09:41:17gmcharltour new ESIer, tfaile is going through our usual trial by fire^W^W^Worientation and installing Evergreen from scratch, and I think he has some notes too
#09:42:26dbswe do say the opensrf user "must own all files contained in the PREFIX directory hierarchy" but it's easy enough to add the command
#09:42:28wlaytondbs: nice to be back!
#09:43:46yboston has joined #evergreen
#09:45:25dbswlayton: pushed fixes to master and rel_2_0
#09:50:10AaronZ-PLS has quit IRC
#09:50:39wlaytondbs: Thanks! I'll try to work on that TODO in the commit message later this weekend.
#09:54:46dbswlayton: right now the install instructions have you create the opensrf user after "make install", so a change to the order of the README would go hand-in-hand with that (can't chown before the user exists!)
#09:56:00dbswlayton: also - as you care about these sorts of things - the long-ago patch that I submitted to ejabberd for ejabberdctl input escape to support passwords containing special characters is being reverted because some other part of the ejabberd toolset gets confused by it
#09:56:56dbshttps://support.process-one.net/browse/EJAB-1399 if you're feeling really frisky and want to delve into the guts of ejabberd and shell scripting :)
#09:57:29dbsWhen I think of strong passwords and special characters, I think of wlayton!
#10:00:24jeffwlayton certainly is a special character.
#10:00:25dbsgmcharlt: cool. I think grace sent me some edits for the 2.1 release notes via email a few days ago, I've been swamped but will try to integrate those today
#10:00:28dbsjeff++
#10:00:32jeffit is a morning of corner cases and outliers.
#10:04:46dbsDoes anyone want to volunteer to put together a developer report for today's community meeting?
#10:05:19dbs probably won't be able to make the meeting, alas - local meeting conflicts
#10:10:39tecoripa has joined #evergreen
#10:11:19tecoripagood morning
#10:11:40tecoripaI have a question about getting permission to create pages on the evergreen wiki...
#10:12:17tecoripaI sent a request to docs@evergreen-ils.org...
#10:12:39tecoripado request take a while to get processed?
#10:12:51dbstecoripa: this is a good place to ask, too. please pm me your email address and name
#10:13:06tecoripaok, thanks...
#10:13:09tecoripajust a second
#10:13:11phasefxtecoripa: and let docs@ know that dbs got you covered
#10:13:25dbs suspects lwhalen@evergreen-dev.catalogue.nrcan.gc.ca isn't really the email address lwhalen wants for git sign-offs
#10:13:49dbs will munge to nrcan-rncan.gc.ca
#10:14:33tecoripathanks, dbs. Just IM'd you my name and email
#10:15:56wlaytondbs: You suspect correctly.
#10:16:47dbstecoripa: you should have mail soon
#10:17:25tecoripaok, thank you. I'll send a note to docs@, letting them know you took care of the request.
#10:17:43dbs can do the can-can(.gc.ca)
#10:22:30csharpso I'm trying to checkout rel_2_0_1 of OpenSRF's git repo, but it looks like that doesn't exist - is that right?
#10:22:58csharp tried 'git checkout tags/rel_2_0_1'
#10:23:21jeffthere is no 2_0_1
#10:23:42tsberecsharp: osrf_rel_2_0_1 ?
#10:23:55tecoripabye
#10:23:56tsbere(probably without a tags/ in front of it)
#10:23:57jeffyou'd want to run "git fetch" (or "git fetch origin", or "git fetch --all"), then "git branch -r" should show you all remote branches.
#10:24:49jeffand there is no OpenSRF branch containing the string "2_0_1"
#10:24:59jeffoh, but there is a tag.
#10:25:08jeffi thought we weren't using tags.
#10:25:16dbsit's documented, I believe
#10:25:22jeffcsharp: "git tag" shows one tag, with the name tsbere mentioned.
#10:25:29csharpah
#10:25:29tsberejeff: evergreen isn't using tags. OpenSRF apparently is using them. :P
#10:25:40dbshttp://evergreen-ils.org/dokuwiki/doku.php?id=dev:release_process:opensrf:2.0
#10:25:46csharpor just one ;-)
#10:25:46jeffaha: "Branches that start with tags/ are legacies of Evergreen's previous Subversion repository"
#10:26:03tecoripa has left #evergreen
#10:26:20jeff(from dev:git)
#10:26:21dbsgmcharlt suggested that we start tagging releases and I embraced his suggestion (and his help)
#10:26:21jeffdbs++
#10:26:34csharpoh - okay - thanks all
#10:26:38jeffalso, awesome that we're gpg signing tags
#10:26:42jeffgmcharlt++
#10:27:06gmcharltwhich reminds me, we should throw a keysigning party at the next EG conference
#10:27:11tsberejeff: On Evergreen we are still making branches with tags/ due to wanting to drop stuff on them afterwards. For OpenSRF apparently there is significantly less "drop stuff on post-tag" so we can use real git tags?
#10:27:21tsbere apparently needs to generate a key
#10:27:35tsbereOr find one of my three old ones. <_<
#10:27:52dbs missed out on the GSoC key-signing party, which would have robustified his completely unsigned key significantly
#10:28:02wlayton 's GPG key used to be ranked 45th most connected in the world...until he lost it.
#10:29:18dbswow
#10:30:05csharpthat's pretty cool ;-)
#10:30:59wlaytonthat was thanks to many years of attending the Ottawa Linux Symposium.
#10:31:25dbs wonders if the BSD folken use GPG keys or avoid them out of principle :)
#10:33:09jenny has joined #evergreen
#10:33:57jeffols++
#10:34:03jeff(i only made the first one)
#10:34:33wlaytonjeff: in 1999?
#10:34:36jeffdbs: pgp and non-mime signatures, last i knew.
#10:34:38jeffwlayton: yes.
#10:35:08jeffdbs: small sample size, though
#10:36:27wlaytonjeff: Cool! Pat Beirn's lunchtime talk there was epic (at least for me)
#10:36:49dbs is randomly reminded that he has some automake changes to support building some utilities that scottmck used for verifying the correctness of fm_IDL.xml (which appears to have problems based on the output of said utility)
#10:36:58dbstime to go open a bug and find / attach that branch
#10:45:06jeffwlayton: was that his talk on memory management? i still think of that every time i come across the concept of Copy-on-Write.
#10:46:49jeffi think i still have the conference audio. "hello, i'm ian goldberg, this is the ottawa linux symposium, and THIS... is a green laser pointer! [audience oos and ahs]"
#10:47:04wlaytonjeff: Yes, but he also continued it outside in the hall afterward. I think I still have the MP3s of a recording someone made of it.
#10:48:00jeffgood memories. i was sad that i never made it back. glad to see that it's still going.
#10:51:35csharp sometimes feels he came to Linux/FLOSS about 10 years too late :-(
#10:56:23bshumHuh
#10:56:42bshumBackdating circulations sometime give people the wrong date and it looks like it's off by one hour, pushing it a day too early.
#10:56:50bshumBug in our staff client or daylight saving's weirdness?
#10:57:04bshumErm a day too late.
#10:57:05jeffbshum: timezone complications.
#10:57:23bshumSo like instead of getting 2011-10-28 11:59:59, they get 2011-10-19 00:59:59
#10:57:33bshumjeff: Timezone complications?
#10:57:42jeffbshum: without looking at the data closely, it is most likely timezone related, based on others experience and discussion here.
#10:57:48bshumHmm
#10:57:59tsberebshum: Was talking to mrpeters-isl about that recently.
#10:58:03bshumI wonder how that would happen if we're all supposed to be in the same timezone?
#10:58:10jeffbshum: circs where a due date and the checkout time are in different UTC offsets
#10:58:21tsberebshum: Backdating uses the due date time and timezone.
#10:58:58bshumjeff: tsbere: Ah okay, thanks.
#10:59:01tsberebshum: I threw some code at mrpeters-isl to deal with that, but he discovered other issues when testing it.
#10:59:04bshumGuess we'll poke at it.
#10:59:43sal_Git question. I know how to git the current master, but if I want to clone the 2.1.0 release (so I can patch it with later bits and pieces) how do I go about that? (One of these days I will understand git. Really.)
#11:00:16tsberesal_: git checkout tags/rel_2_1_0
#11:01:11sal_tsbere: thanks. Of course, now I get to go off to a meeting, so I will try afterwards ;-)
#11:04:07darshan has quit IRC
#11:04:22bshumtsbere: Oh yeah, it looks like the due date was in an 05 timezone, but everything we have is in 04
#11:04:33bshumtsbere: That sounds like it would do it, thanks!
#11:04:49wlayton has quit IRC
#11:04:55tsberebshum: DST differences, I assume ;)
#11:05:06bshumtsbere: That's our assumption as well.
#11:07:20youdonotexist has quit IRC
#11:17:16kmlussier has joined #evergreen
#11:18:22AaronZ-PLS has joined #evergreen
#11:19:18sal_5467
#11:21:11kivilahtiohow can I get money to my fund?
#11:22:24kivilahtiortfm
#11:57:18moodaepokivilahtio++
#11:57:24kivilahtioyeah
#11:57:27kivilahtiobut damn
#12:09:29jenny has left #evergreen
#12:11:34brian_f has joined #evergreen
#12:13:43tsbereberick: For the record, I also have no clue why the OUS is desirable on the indb holdable bug there. <_<
#12:24:25bshummoodaepo++ #reminders
#12:26:01moodaepobshum: Heh I just noticed I didn't send do my action item, probably will get to it later today. Might look suspicious if I send it out an hour before the meeting : )
#12:27:55csharpokay - we're working on setting up our utility server for our 2.1.0 cluster. here is our 1.6.1.8 crontab for opensrf: http://pastebin.com/K6yhnv9k
#12:28:18csharpwhich, if any, of these are deprecated as of 2.1.0?
#12:28:26csharp(if someone has a minute to look)
#12:28:51tsbereRemove the 1 from the fine generator command. Beyond that....not sure.
#12:28:51csharp realizes some may be custom PINES things
#12:29:04jenny has joined #evergreen
#12:29:08bshumI don't recognize gen_blocked_list.sh
#12:29:14bshumIt goes by a different name on our 2.0
#12:29:19csharpah
#12:29:30tsbereLooks like it is a wrapper
#12:29:43csharpyeah - as is circ_notices.sh
#12:29:46bshumThat's what I was just wondering.
#12:30:05rtw has joined #evergreen
#12:30:08bshumSeems pretty normal to me then.
#12:30:12csharpokay - thanks
#12:30:15tsberecsharp: I think the 2.1 fine generator will bail with the 1 passed in on the end, actually, due to the indb grace period work?
#12:30:16bshumCourse I'm not a 2.1.0 site :)
#12:30:29csharptsbere: okay - good to know
#12:30:39tsbere thinks he made it bail with an error in that case
#12:31:02csharpwell, we'll probably test each one manually in any case
#12:31:08csharpthanks for the input
#12:31:19brian_f_ has joined #evergreen
#12:32:55brian_f has quit IRC
#12:33:53sal_ has quit IRC
#12:34:48dbs@later tell community_irc_meeting dbs will be hacking on TPac in Windsor on December 9th, so won't be available if the next Community meeting is scheduled for that date
#12:34:48pinesol_greendbs: The operation succeeded.
#12:35:56dbsof course the "university HR survey results & next actions" meeting that got scheduled for this afternoon blows away my chance of participating in today's community meeting, too
#12:37:49senatordbs: re your high priority lp bug 872651, the problem in OpenLibrary.pm... i set up a straight 2.1.0 test environment...
#12:38:07berick actually sent his passport off for renewal today
#12:38:31berickthough it will probably not be returned in time for tpac hacking :(
#12:38:41dbs curses borders
#12:38:57senatordbs: and i couldn't really duplicate the symptoms. cover art appears fine in the catalog, and i don't get that error message in any logs (unless there's something situational about it i'm missing). however, things still work fine with changes from your branch incorporated
#12:39:07senatorso...
#12:39:31senatorthat's sort of a successful test?
#12:39:32dbssenator: your opensrf.xml is using OpenLibrary added content?
#12:39:45dbsor maybe still using Amazon or something else from previous configs?
#12:40:41dbs is usually happy to hear "hey dbs you _didn't_ break things horribly" but is wary
#12:40:49senatordbs: gah, probably that's it. checking
#12:42:24sal_ has joined #evergreen
#12:43:54bericktsbere: indb hold OUS... aye, glad i'm not the only one
#12:45:36senatordbs: other than changing the content of the opensrf/default/added_content/module node to replace Amazon with OpenLibrary, restarting the settings service, and restarting apache... is there further configuration i should be doing?
#12:46:05dbssenator: can't remember off hand if previously cached artwork would still be cached after restarting apache
#12:46:45dbsso with the possible exception of clearing cached artwork, I think that should clear things up nicely
#12:46:54senatorthat gets cached in memcache right? ok i'll try restarting
#12:48:14berickcache would stick around
#12:48:37senatorok now i have broken cover images. cool
#12:49:10berickhow do you target multiple milestones in LP?
#12:49:11senatorand your patch unbreaks them
#12:49:13berick rubs eyese
#12:49:15senatordbs++
#12:49:17bericki know i've done this before
#12:49:18dbsYAY
#12:49:21senatorwill sign off and merge
#12:49:27dbssenator++
#12:49:33_bott_ has quit IRC
#12:49:39dbsberick: target series
#12:50:13berickdbs: "nominate for series"?
#12:50:16dbsbutton should be just above "Bug description"
#12:50:27dbsah, that's the "release team" vs. "bug wrangler" thing
#12:50:29dbsbah
#12:51:43dbsor "Project Driver" actually
#12:51:44bshum:)
#12:51:53dbs(which is the Release Team at the moment)
#12:52:04bshumdbs: I'll add the tpac dev day to the agenda under the developer report area as an "announcement"
#12:52:11bshumAnd will note that you're anti-Dec9 :)
#12:52:12dbsbshum: sounds good!
#12:53:05bshumSince you won't be around for the meeting, could you put up the agenda link into this channel early? (we can take it down later this weekend or whenever you come back afterwards)
#12:53:19bshumChannel topic I mean
#12:53:36dbs adds berick to the release team for now, need to revisit the driver team membership: "The driver can set goals, approve bug targeting, or set backporting for any major series in the project"
#12:54:03dbsbshum: sure, I can also see about getting chanserv to spread topic permissions around
#12:54:18bshumCool :)
#12:54:20bshumThanks!
#12:54:39dbsthe command for those with topic permissions is: "/MSG chanserv topic #evergreen <fill in topic here>" IIRC
#12:54:40berickspeaking of tpac, kcls is live on tpac in productionn as of last week. not sure if a note went out about that anywhere. so, there's that.
#12:55:53dbs suspected some big site was going live, given the level of recent focus :)
#12:56:09dbskcls++
#12:56:11dbsberick++
#12:56:12jeffcool.
#12:56:13dbssenator++
#12:56:14jeffkcls++
#12:56:16dbset_al++
#12:56:17jefftpac++
#12:56:18jeffesi++
#12:56:22jeff@karma et_al
#12:56:22pinesol_greenjeff: Karma for "et_al" has been increased 2 times and decreased 0 times for a total karma of 2.
#12:56:30jeffet_al++
#12:57:50berick@karma karma-chameleon
#12:57:50pinesol_greenberick: karma-chameleon has neutral karma.
#13:00:45akilsdonk has quit IRC
#13:01:20dbs tries to add TOPIC perms to a bunch of nicks and then wonders why we have the topic locked anyway - as long as we keep "publicly logged" reasonably visible
#13:02:21phasefxsenator++ dbs++ # not waiting for me
#13:04:21ChanServ sets mode: +o dbs
#13:04:35ChanServ sets mode: -o dbs
#13:05:48ChanServ sets mode: +o dbs
#13:05:59ChanServ sets mode: -o dbs
#13:06:23ChanServ sets mode: +o dbs
#13:08:29dbs sets mode: -t
#13:08:30ChanServ sets mode: +t
#13:08:38dbsdamn you chanserv!
#13:09:10WindowsUser has quit IRC
#13:09:17jeffdbs: /msg chanserv set #evergreen mlock +nc-slk
#13:09:19dbsChanServ isn't responding to "SET #evergreen TOPICLOCK OFF"
#13:09:48jeffdbs: the current mlock setting includes +t, which is why ChanServ is undoing your mode changes.
#13:10:03dbsirc is stupid
#13:10:05dbs:)
#13:10:13dbs is much more stupid
#13:10:45dbs sets mode: -t
#13:11:01ChanServ sets mode: -o dbs
#13:11:03dbs changes topic to "Welcome to the #Evergreen library system channel! | We are publicly logged. | Large pastes at http://pastebin.ca or http://paste.lisp.org/new/evergreen or something"
#13:11:07dbsWhee!
#13:12:03dbsSo anybody should be able to change the topic directly now, no chanserv messages required
#13:13:54dbsIf the topic gets abused, we can lock it down again, but let's try a nice open policy :)
#13:16:15berick /topic meet singles in your area
#13:16:57gmcharltberick: c'mon, you know that *single* MARC records are absolutely useless
#13:17:06gmcharltyou need bunches and bunches of them!
#13:18:10tspindler has joined #evergreen
#13:20:12berickbut don't forget... mo' MARC, mo' problems
#13:28:28dbs has quit IRC
#13:28:52Dyrconano MARC, no problems?
#13:28:53dbs has joined #evergreen
#13:28:57Dyrconano MARC, no cry?
#13:32:02sal_ has quit IRC
#13:37:04_bott_ has joined #evergreen
#13:40:23kayals has joined #evergreen
#13:50:14dbs has quit IRC
#13:50:24dbs has joined #evergreen
#13:50:32dbs has joined #evergreen
#13:51:26dbs has quit IRC
#13:51:43denials gets dbs out of channel to stop annoying msgs
#13:54:12LBA has joined #evergreen
#14:00:35moodaepoMeeting time?
#14:00:50jennyI think so!
#14:01:08bshumAww, wasn't able to change the channel topic
#14:01:13bshumOh well.
#14:01:18bshumMeeting agenda: http://ur1.ca/5my0b
#14:01:43rtw has left #evergreen
#14:01:44bshumAs folks introduce themselves for the roll call, let's find some volunteers for minutes / meeting leader
#14:01:50bshum is Ben Shum, Bibliomation
#14:01:51moodaepoI can run the meeting
#14:01:59moodaepo Anoop Atre, PALS
#14:02:00jenny is Jenny Turner, PALS
#14:02:05bshummoodaepo++
#14:02:25phasefx is Jason Etheridge, ESI
#14:02:30tspindlertspindler is Tim Spindler, C/W MARS
#14:03:07denials changes topic to "Meeting agenda: http://ur1.ca/5my0b | Welcome to the #Evergreen library system channel! | We are publicly logged. | Large pastes at http://pastebin.ca or http://paste.lisp.org/new/evergreen"
#14:03:11LBA is Lori Bowen Ayre, The Galecia Group
#14:03:17kmlussier is Kathy Lussier, MassLNC
#14:03:24moodaepodenials++
#14:03:29denials(aside: "/TOPIC <change the topic>" should work for anyone...
#14:03:30yboston is Yamil Suarez - Berklee College of Music
#14:03:39bshumAh, that's why, stupid chanserv :(
#14:03:48bshumI was using the wrong IRC commands
#14:03:59eeevil == Mike Rylander, ESI
#14:05:05jeff is Jeff Godin, TADL
#14:05:08AaronZ-PLS = Aaron Zsembery, PLS
#14:05:20moodaepoAny takers on minutes?
#14:05:34kmlussierI'll take minutes
#14:05:40moodaepokmlussier++
#14:05:42bshumkmlussier++
#14:05:42jennykmlussier++
#14:06:07moodaepoOk moving on then to reviewing last meetings action items.
#14:07:00moodaepo3. I. moodaepo has not emailed the lists with the info about test servers (apologies) plan on taking care of it after this meeting.
#14:08:07moodaepo3. II phasefx did you get an chance to send out the end-of-life for 2.0/1.6 email to the list?
#14:08:24phasefxno, I totally forgot that was on my plate (it is?)
#14:08:40bshumhttp://markmail.org/message/hdofpg56esll2g3q
#14:08:41bshumHe did
#14:08:47phasefx needs to take more vitamin B, doesn't remember it at all :)
#14:09:14phasefxokay, I remember now
#14:09:23phasefxexternal memory
#14:09:28moodaepophasefx++ # getting stuff done and forgetting about have done said stuff.
#14:09:46bshumDoesn't look like much official discussion though; I think dbs had that on his dev meeting discussion topics email too.
#14:10:27phasefxI think we've been going about as if 1.6 was de facto deprecated
#14:11:50moodaepophasefx: Do we need a more official email/discussion on the mailing list and an announcement?
#14:12:46phasefxwell, that's up to us. A blog post might come across as more official, at least as an announcement. Not good for discussion
#14:12:51akilsdonk has joined #evergreen
#14:14:25phasefxanyone want to talk about such things? Now? Later? What do we need to do to go with time-based releases?
#14:15:12eeevilabout version deprecation?
#14:15:18moodaepoeeevil: Yes
#14:15:31eeevilsure ... down with 1.6! :)
#14:15:41bshum+1 (seconded)
#14:16:01eeevilI don't know that the community wants to get into the LTS biz (what if 2.3 is way more stable than 2.2??)
#14:16:05eeevilbut
#14:16:25eeevilI think a minimum time for backporting of noncritical bug fixes is good
#14:16:51AaronZ-PLSeeevil++
#14:16:53eeeviland then, perhaps, a shorter critical (data-loss) bug backporting window
#14:17:19jeff_ has joined #evergreen
#14:17:42bshumBarring any final objections, maybe we should have an action item to announce the end of community support for 1.6 as an official blog post? Then have more time to discuss what'll happen with post-2.x world.
#14:17:45jeff_ is now known as Guest78439
#14:17:50moodaepobshum: +1
#14:17:56eeevilbased on the difference between our (hoped) 4mo plan for release, and the actual 8mos it took, and the hope that we'll get better at it
#14:18:01bshumi.e. action item for dev team to discuss in more details.
#14:18:15Guest78439wow bunch of people on here. Anybody know ncip stuff?
#14:18:26eeevilwould 2 releases for non-crit bugfixes and 3 releases (18mo) for critical ones bee good?
#14:18:45eeeviler ... sec
#14:18:51moodaepoGuest78439: We are in a meeting now could you please try again in about 45 minutes?
#14:19:10eeevilwould 12mo (2 releases, ideally) for non-crit bugfixes and 18mo (3 releases, ideally) for critical ones bee good?
#14:19:11moodaepoOf course hang around and join the meeting in the meanwhile : )
#14:19:45kmlussierFor the minutes: Will dev team also discuss the announcement for end of support for 1.6? Or should somebody volunteer to take up that action item today?
#14:19:54eeevilthat seems in line with what was said up there ^-
#14:21:42eeevilbshum: sorry for just shoving ahead, typing without reading up ;) ... +1 for discussion post-1.6 announcement
#14:21:54Guest78439 has quit IRC
#14:22:19moodaepokmlussier: The action item for today is announcing eol for 1.6, dev team will discuss post 1.6 maintenance.
#14:22:57moodaepoMoving on to 3 III - Don't think Amy sent out the email, bshum?
#14:23:14kmlussiermoodaepo: thanks! But who will be announcing the 1.6 eol?
#14:23:20bshummoodaepo: afterl couldn't make this meeting today, but she told me that there was communication made between groups on that.
#14:23:29moodaepokmlussier: I will volunteer to put that together and post
#14:23:37bshumAnd the different people who needed to know were informed.
#14:23:40moodaepobshum++
#14:23:50kmlussiermoodaepo++
#14:24:04moodaepoNext on LBA - Communications committee & Website Team report
#14:24:22akilsdonk has quit IRC
#14:24:23LBAstand by...paste coming in.
#14:24:40LBAI hope....
#14:24:56bshumhttp://paste.lisp.org/display/125684
#14:25:03bshum rescued it from the lisp
#14:25:22LBAbshum++
#14:25:46bshumThe automatic paste doesn't work, but they are retrievable here: http://paste.lisp.org/list/evergreen
#14:26:07LBAcan I assume you are reading the report? Available for q's...
#14:26:12moodaepoLBA: Anything else to add/discuss?
#14:26:44LBAThe one thing I'd like to mention is that we are pursuing this "idea percolater" to help bring
#14:26:46tspindlerhow does this relate to bug reporting
#14:26:58LBAdifferent ideas together about what people want developed
#14:27:14LBAand to help them find each other to perhaps fund a feature.
#14:27:33LBAwe want to do it in a way that flows nicely into the dev workflow AND is easy for us non-developers
#14:27:35phasefxfund or otherwise collaborate
#14:27:37tspindlerso if implemented, wishlists might be posted here or other development ideas?
#14:27:58LBAtspindler, right.
#14:28:14LBAphasefx, exactly.
#14:28:52moodaepoLBA++ # That includes everyone who has anything to do with the "idea percolator"
#14:29:46LBAAnyone interested, feel free to join us at nov 10 at 11 PST, 2pm EST for our next meeting.
#14:30:10moodaepobshum: You had a last minute addition?
#14:30:18bshumJust a small thing
#14:30:24bshumGeneral committees question: there are contact names for different groups listed on http://evergreen-ils.org/dokuwiki/doku.php?id=faqs:evergreen_committees, but there's no actual contact details (like email, phone, etc.) Would the contact persons for the groups be open to having that information available somewhere? Or that's a task that the Communications Committee could look into for those pondering.
#14:30:27moodaepo(To the communications report from Amy)
#14:30:42moodaeporeport == question
#14:31:09LBAI'm not sure that's a comm decision so much as a person decision...no?
#14:31:45LBAI certainly don't mind being listed. It's not like its hard to get my email address now...
#14:31:47LBAOthers?
#14:32:18moodaepoLBA: So how about we contact those folks and ask them to update the page themselves with contact info they are comfortable posting?
#14:32:22phasefxwe can always come up with proxy email addresses as well, like docs@ for the DIG facilitators
#14:32:56LBA+1 proxy email addresses
#14:33:03phasefxor encourage folks to post publically on the mailing lists
#14:33:47denialsaren't there mailing lists for most committees?
#14:34:06jennysometimes people want A person to ask questions of...so +1 proxy
#14:34:24jennydenials: yes
#14:34:45LBAproxy addresses don't change so even as new leaders step in, its the same contact email that will get you to a live, and relevant person
#14:34:56denialsread the list and pick a person who seems to know something about the area you're interested in? proxy lists (hello feedback) are hard to coordinate responses to, IMO
#14:35:11AaronZ-PLS+1 on proxy. Then the address dont have to change when the when people change
#14:36:18LBAlower threshold to contact one person than a) scour a mailing list archive or b) joining yet another list
#14:36:33phasefxI think proxy addresses have an advantage of being low-barrier, but like dbs said, they're... ha, yall get it
#14:37:47LBAI don't get it.
#14:38:25moodaepoOk so action item setup proxy mail address?
#14:38:30jennyI would assume that the contact people listed for the group would be responsible for the responses to proxy emails...and then ask for help from others if/as needed.
#14:38:49moodaepophasefx: Would we request this from csharp?
#14:39:19kayals has quit IRC
#14:39:37kayals has joined #evergreen
#14:39:55phasefxmoodaepo: depends on what we want to do. feedback is hosted by ESI. docs is a simple postfix alias to multiple addresses
#14:40:37phasefx likes postfix aliases for simplicity, mailing lists for archives
#14:40:42bshumAlternatively we remove contact information to direct people of each group and include an all encompassing "go find the right mailing list and post there"
#14:41:13LBA isn't liking Ben's idear
#14:41:15bshumThough that does seem slightly more intensive.
#14:41:37LBAphasefx +1
#14:41:43kmlussierI like the idea of having a proxy address or just posting the contact person's e-mail address.
#14:42:02phasefxI tell you one thing, with almost every response I give to someone via feedback@, I'm inviting/encouraging them to post to the public mailing list, for their benefit and others
#14:42:35LBAsometimes people just need to get the encouragement/permission
#14:42:37moodaepoOk so action item: Setup proxy (postfix aliases) for primary contacts of each group.
#14:42:53phasefxmore eyeballs, more chance for feedback, spin-off thoughts, more help with responses, etc.
#14:43:11kmlussierWho's action item is that?
#14:43:14moodaepoI will volunteer to do that also (since I'm looking at the file right now : )
#14:43:30kmlussiermoodaepo++
#14:43:30denialsa proxy / autoresponder that provides info on how to subscribe and post to the mailing list?
#14:43:34denials ducks
#14:43:48moodaepoMoving on to Conference committee. Anyone from the group around?
#14:44:18LBAactually, denials, I wouldn't object to that so no throwing from me!
#14:44:19StephenGWills has joined #evergreen
#14:44:55moodaepoLBA: Don't suppose you are on the conference committee? : )
#14:44:57bshumErm, I'm sorta on that.
#14:45:14LBAthankfully, no.
#14:45:21bshumI'm on the programs committee. As far as I know, we're still recruiting program ideas for EG2012
#14:45:46bshummoodaepo++ for putting a link to the conference website on the Evergreen website (in case people have missed the new corner logo switch)
#14:45:57moodaepobshum: Want to update us or should we skip it for this meeting?
#14:46:40bshummoodaepo: I don't have any update on it, other than to say submit programs to Shauna as emails/blogs/etc. have gone around on it.
#14:47:14bshumhttp://evergreen2012.org/?p=85 (for the minutes)
#14:47:51moodaepoWill do. So next up DIG folks! yboston? jenny?
#14:48:02ybostonHere is the DIG update put together by karen Collier: http://evergreen-ils.org/dokuwiki/doku.php?id=community:meetings:2011-11-04:digreport
#14:48:42moodaepoyboston++
#14:48:44denials notes that evergreen201#.org should probably be owned by the Software Freedom Conservancy (or a stable evergreenconference.org or something like that for future)
#14:48:58moodaepodenials++
#14:49:46csharpwe had conference.evergreen-ils.org set up for last years, but because we didn't finish configuring it, it points to the pines site :-/
#14:49:48LBAI propose confeence.evergreen-ils.org for current conf with links to archives from there
#14:49:49csharppines--
#14:50:15LBAthen we don't have to keep creating new subdomains
#14:50:48csharpESI set that up for us - if somebody wants to follow up
#14:51:19enhancin has joined #evergreen
#14:51:22bshumSounds like something that the 2013 crew ought to look into as part of their work.
#14:51:37enhancinI know this is probably a really stupid question but I can't find in the documentation where to create users
#14:51:45eeevilcsharp: the dns for conference.evergreen-ils.org? well, we've transfered it to SFC ... if we can't do it we can find out who can
#14:51:53csharpeeevil: cool
#14:52:09moodaepoenhancin: We are in a meeting now could you please try again in about 20 minutes?
#14:52:12eeevilwho should I point that info at?
#14:52:14enhancinyeah
#14:52:15csharp didn't know where in the process the transfer was
#14:52:31enhancin has quit IRC
#14:52:35csharpeeevil: probably Shauna Borger
#14:52:46gmcharltcsharp: SFC is now the contact for the domains
#14:52:52csharpgmcharlt: excellent
#14:53:07eeevilcsharp: I got the "click here to approve the transfer" emails a couple weeks ago :) ...
#14:53:21gmcharltbut Equinox is still providing name service (via DynDNS) and we can update conference.evergreen-ils.org
#14:53:35eeevilthere we go! :)
#14:53:36gmcharltso we'll just need to know where to point the name
#14:53:37eeevilgmcharlt++
#14:53:51gmcharltjust a CNAME for the main webserver?
#14:54:59moodaepogmcharlt: Sure then we can redirect to where ever from there.
#14:56:08denialsyayz
#14:57:11moodaepoAction item: gmcharlt/esi will update the dns to point to the main web server
#14:57:13moodaepoMoving on folks...reports Taskforce report, jenny?
#14:57:35gmcharltmoodaepo: Action item complete ;) (wait 600 seconds for the TTL to expire)
#14:57:41jennyI've been unable to attend our last 2 meetings (and am still getting caught up!), but Jennifer Bielewski stepped in to convene the group. Sept. was cancelled due to low turnout. The October meeting seems like it was productive...minutes are here: http://open-ils.org/dokuwiki/doku.php?id=evergreen-reports:meetings:2011-10-12
#14:57:43moodaepogmcharlt++
#14:57:59moodaepojenny++
#14:58:20jennyOur next meeting is next Wed, Nov. 9 at 2:30 Eastern on IRC.
#14:58:41jennyand that's all I've got - but bshum may have something additional??
#14:59:22bshumNothing on my end today. Other than jeff saying something about his jasperreports testing, but that'll probably come in more detail at the next reports meeting.
#14:59:33bshumSo come one, come all (who want to know more)
#14:59:37bshum:)
#14:59:37jennyOk then...stay tuned everyone!
#15:00:09moodaepoOk then - Developer report.
#15:00:43bshum2.1.0++
#15:01:23moodaepoeeevil gmcharlt tsbere any one?
#15:01:39denials2.1.0a - heh
#15:01:49bshumDoh... 2.1.0a :)
#15:02:58phasefxwe're chugging :)
#15:03:14moodaepoOk since the devs are busy dev-ing I say we skip their report for this meeting and they can post notes to the minutes when they get a chance
#15:03:18moodaepophasefx++
#15:03:47denialsthat said, our meetings have kind of fallen apart for the last month or so
#15:04:04moodaepoRight bshum just reminded me to point out that "Conifer will be hosting another Tpac development day at University of Windsor on December 9th."
#15:04:24denialsDecember 8th/9th actually :) thanks bshum / moodaepo
#15:04:25phasefxand there are a lot of pull requests to work through, though as mrpeters charitably said, that means there has been a lot of work and bugfixing we've done :)
#15:04:53moodaepodevs++
#15:05:12moodaepoGovernance committee folks updates? LBA?
#15:05:43LBAI think the minutes from the last meeting were posted.
#15:05:47LBAon wiki
#15:05:53LBAshall I paste them too?
#15:06:05moodaepoLBA noe that's good enough
#15:06:19LBALots of sorting out how the whole relationship with SFC works. denials would be better updater.
#15:07:00moodaepoWill do. denials is busy at another meeting so the meeting minutes will suffice
#15:08:22moodaepoRight if there's nothing to add I say we schedule the next meeting for Dec 2nd (suggested by bshum on the agenda page)
#15:08:52kmlussier+1
#15:09:00jenny+1
#15:09:39moodaepoExcellent. Thanks all meeting adjourned.
#15:10:33kmlussierThe agenda suggested an earlier time for the December 2 meeting (9 a.m. PST; 12 p.m. EST). Is that okay with everyone?
#15:11:00moodaepo missed that
#15:11:17moodaepoAny objections folks?
#15:11:28bshumEeps, I think I might have mis-copied that.
#15:11:34bshumFrom a dev meeting agenda
#15:11:40kmlussierOK, so the usual time? Either time works for me.
#15:11:52moodaepoUsual time++
#15:12:07kmlussierok...done
#15:12:19kmlussiermoodaepo++ meeting leader!
#15:12:23StephenGWillsUsual time catches more of the country awake :)
#15:12:37bshumClose, but no gmcharlt and his precise whip of time.
#15:12:40bshummoodaepo++ ;)
#15:13:20denialsStephenGWills: but forces potential IISH / Georgian people to attend during dinner
#15:13:32gmcharltmoodaepo++
#15:14:04denialsmoodaepo++
#15:14:06denialsyall++
#15:17:02StephenGWills updates his locale files
#15:21:08tsbereprinting--
#15:21:09tsbere<_<
#15:23:54tspindlerI posted a question the other day and see if anyone has an answer now, the reshelving script isn't doing anything, i see it runs on the cron job and when issue the command "./reshlving_complete.srfsh" we get the following error "Unable to bootstrap client for requests"
#15:24:07tsbereBad opensrf_core.xml?
#15:24:40tspindlertsbere: i haven't checked that but all I know if there is something wrong its been that way a long time
#15:25:15denialsbad .srfsh.xml ?
#15:25:30tsberethat could be too.
#15:25:35denialsor user that the cron job is running under doesn't have a .srfsh.xml?
#15:26:42tspindlerdenials: i can check that too, the difficulty is we haven't had reshelving for a longtime on this test server and I thought i look at the problem now
#15:27:10tspindlerwe had procrastinated on this since it didn't affect a lot
#15:28:00akilsdonk has joined #evergreen
#15:32:03denialsberick: on the subject of OpenSRF and IPC - we didn't see the problem until approximately 24 hours after restarting our processes. kind of wondering whether there's a counter or timer or something that goes nutty in IPC::SharedState
#15:33:00berickdenials: my thought as well. that's actually part of the reason I lowered the size of the shared mem segment (though it could probably be even smaller)
#15:33:12berickthough.. they should clean up after each request is handed to a child
#15:33:19denials wonders if anyone is going to ake use of the newfound /TOPIC freedom to fix0r the topic :)
#15:34:51akilsdonk has quit IRC
#15:34:51denialsberick: yeah, should. max_requests is at 1000 for max_children 20 in open-ils.storage
#15:36:37bshum changes topic to "Welcome to the #Evergreen library system channel! | We are publicly logged. | Large pastes at http://pastebin.ca or http://paste.lisp.org/new/evergreen or something like that"
#15:36:45bshumWhee!
#15:39:09denialsbshum feels the POWER
#15:40:52gmcharlt changes topic to "Welcome to the #evergreen library system channel! | We are publicly logged. | Large pastes at http://pastebin.ca or http://paste.lisp.org/new/evergreen or something like that"
#15:40:53kayals has quit IRC
#15:41:01gmcharlt;)
#15:42:08denialsberick: count of open-ils.storage requests for a complete day on one of our nodes is 151K, so I would have expected the IPC issue to kick in before that if it was child-recycling related
#15:42:27denials(assuming I counted right, which is by no means assured)
#15:44:19berickyeah
#15:44:57bericki wonder if the problem is not the children, though, but the shares sticking around after all children have died
#15:45:13berickthe -destroy=>1 on the child proc should handle that, but..
#15:45:16berick tries a test
#15:46:27akilsdonk has joined #evergreen
#15:46:52eeevilberick: quoth the docs: you should not use this option in a program that will fork after binding the data
#15:47:12berickyeah, shares are created after forking
#15:47:16kmlussier has quit IRC
#15:47:17eeevilk
#15:48:27berick may just move to flock instead
#15:49:59tspindler has quit IRC
#15:51:56berick confirmed the shares are getting destroyed
#15:54:39berickheh, to quote more perl docs: "Slavish adherence to portability concerns shouldn't get in the way of your getting your job done"
#15:56:35Meliss has quit IRC
#15:58:19denials should also note that Conifer's systems are still on Lenny, with all of their ancientness
#16:00:08denials should also note that the primary symptom for us was that apache processes started locking up at 100% CPU usage like crazy; the IPC lock issue was the only anomaly that I found in the (copious) logs
#16:00:42berickinteresting
#16:00:47denialsit was like an acceleration of the "once in a while, seemingly randomly after a long period of time, an apache process will lock up at 100% CPU usage and have to be killed off"
#16:01:16denialsbut when we killed the apache process this time around, it was just replaced by another 100% CPU apache process
#16:01:25berickdenials: do the apache boxes run the opensrf services too?
#16:01:25denialsand then we had 10 such processes
#16:01:28denialshydras
#16:01:52denialsberick: we have just one apache box that does indeed run opensrf services
#16:01:59eeevilohnoes! the gmail, it does nothing!
#16:02:47berickdenials: by any chance, were the services that logged the IPC errors all running on the apache server?
#16:02:54berick sends denials on crazy goose chase
#16:02:55denials will check
#16:03:15denialsgrep "wild goose" osrfsys*log
#16:03:44berickgrep, the original google
#16:04:46denialsberick: that wild goose sounds pretty tasty
#16:06:13denialsberick: if I'm reading my logs right, yes, they all seem to have died on the apache box; no deaths of the opensrf processes running on the ejabberd box
#16:06:25berickfascinating
#16:06:52denialsyep, confirmed
#16:06:58berickapache and ipc both trying for the same resources?
#16:07:07berickand w/ ipc present, resources are more scarce?
#16:07:18berickso more apache craziness and ipc death
#16:08:55denialsapache's shared memory cache?
#16:12:48fortin has quit IRC
#16:14:06denials finds "protostar osrf_json_gw: [ERR :24499:./osrf_json_gateway.c:220:] Service [(null)] not found or not allowed" - looks anomalous, amongst the scads of File not found noise :)
#16:15:31berickthat happens with bad osrf-gateway-v1 URLs
#16:17:06denialsyeah, we have lots of those from previous days, just never noticed them before
#16:17:18denials boggles at Firefox 3.6.23 UA :)
#16:21:02gmcharlt starts hunting for a copy of NCSA Mosaic just to troll denials
#16:21:29senatorgmcharlt: haha, we're on a wavelength, because i just used wget to do exactly that
#16:21:51senatordoh, wrong window. oh well :-)
#16:23:05denials can take it - *sniff*
#16:28:12raynerj has left #evergreen
#17:00:41akilsdonk has quit IRC
#17:02:34jenny has left #evergreen
#17:19:00enhancin has joined #evergreen
#17:19:47enhancinstupid question, how do I go about creating users?
#17:20:42StephenGWillsnp. the staff client will create patrons for you
#17:21:06enhancinoh, when you try to log in?
#17:21:29StephenGWillsunder circulation, use the register patron function to create patrons (users)
#17:21:50StephenGWillsso... lemme back up.... I assumed that you could log into your staff client?
#17:21:52enhancinI swear I went through all the menus there...thank you
#17:21:58StephenGWillsok
#17:22:01enhancinyeah i have been for a bit
#17:22:05StephenGWillsok
#17:22:17enhancinthanks. later
#17:22:17StephenGWillscirculation -> register patron
#17:22:20StephenGWillsnp
#17:22:26enhancin has quit IRC
#17:23:28StephenGWills has quit IRC
#17:31:57yboston has quit IRC
#17:34:29gdunbar has quit IRC
#17:49:56jamesrfhas anyone had a situation where they needed some org units to have Available = holdable and others not using indb circ?
#18:48:37tsberejamesrf: That sounds wrong.
#18:48:44tsbere(the available holdable or not bit)
#18:49:52tsberejamesrf: If available isn't holdable then you may as well just have holdable set to false for entire OU or similar. All locations for that ou set to false or similar would also work(ish, there are bugs there).
#18:52:41jamesrfbut they need it to be holdable when it's checked out
#18:53:01jamesrfbasically they are a post-secondary library that doesn't allow holds on available items
#18:55:01jamesrfi'm wondering if they really just need the recall feature
#19:05:36tsberejamesrf: There is a "don't allow holds on items on the shelf" feature <_<
#19:05:46jamesrfthere is?!
#19:06:42tsbereTo my knowledge there is
#19:07:08tsberejamesrf: "Has Local Copy Block"
#19:07:12tsbereIn library settings editor
#19:09:15jamesrfahhh thanks
#19:09:16jamesrftsbere++
#19:09:42jamesrflooks like it's just in TTPAC but I could probably stick it into the JSPAC
#19:10:12tsbereI think laurentian (sp?) has been using the feature for a while.
#19:10:18tsbereThus I doubt it is just in TPac
#19:10:53tsbereIn fact, the OU setting exists in 2.0.......
#19:11:08tsbereAs does the "Alert" variant
#19:11:19jamesrfyeah i see it but i'm not seeing any code where it's used
#19:12:06jamesrfah found it
#19:12:46jamesrfer nope
#19:14:32tsbereI have never looked for what triggers it
#19:14:39tsbereAs we don't want it enabled anyway
#19:16:31tsbereMaybe it was only ever rigged up enough for script-based rules
#19:18:05jamesrfnah the script based rules don't even need it and i don't think you can access org unit settings from the scripts very easily
#19:18:15jamesrfit looks like it was added as "seed data" but not used until TTPAC
#19:18:46tsbereWell, the backend method for determining things was added before then
#19:19:36tsbereand if you can call backend functions of any kind getting OU settings is easy ;)
#19:19:41jamesrfthere is a related opensrf call called open-ils.circ.hold.has_copy_at but it doesn't seem to even look at that setting
#19:20:43tsbereBut if you can check the setting with circ scripts, or assume you always want it and just call that either way in your circ scripts............
#19:21:01jamesrfyes well circ scripts must die
#19:21:35tsbereAdding it to JSPac wouldn't be all that hard, but I am not inclined to do so due to having no use for it ;)
#19:22:00jamesrfyeah no i think i can figure out something, just thanks for pointing out that setting i didn't know about it
#19:22:12jamesrfmind you i was looking for "holds on available items" or things like that
#19:23:53tsbereYou could ask dbs how they do it, as to my knowledge they currently do that check.
#19:26:00jamesrfi will peek at Confier.git
#19:59:19brian_f_ has quit IRC
#22:40:53Dyrcona has quit IRC
#22:51:52LBA has quit IRC
#23:15:11tater-laptop has joined #evergreen
#23:31:01tater-home has joined #evergreen
< Thursday, November 3rd, 2011Raw Log FileSaturday, November 5th, 2011 >