Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Tuesday, September 13th, 2011

< Monday, September 12th, 2011Raw Log FileWednesday, September 14th, 2011 >
#TimeNickMessage
#00:10:23dbs has quit IRC
#00:32:52enhancin has joined #evergreen
#01:28:36enhancin has quit IRC
#05:30:55bshum has quit IRC
#05:31:34bshum has joined #evergreen
#05:37:36dkyle has quit IRC
#05:37:38bradl has quit IRC
#05:37:39mtate has quit IRC
#05:37:39sylvar has quit IRC
#05:37:40hughbris has quit IRC
#05:38:59dkyle has joined #evergreen
#05:38:59bradl has joined #evergreen
#05:38:59mtate has joined #evergreen
#05:38:59sylvar has joined #evergreen
#05:38:59hughbris has joined #evergreen
#06:13:34tsbere has quit IRC
#06:14:10tsbere has joined #evergreen
#07:48:08collum has joined #evergreen
#07:53:01kmlussier has joined #evergreen
#08:13:26kmlussier_ has joined #evergreen
#08:13:43kmlussier has quit IRC
#08:13:53kmlussier_ is now known as kmlussier
#08:26:30csharp sighs
#08:27:05csharpnow contacting Linked In to make sure open-ils-dev email list does not receive further emails...
#08:27:17tsbereI attempted to do that. Got an error.
#08:27:31csharp will contact Ephraim directly as well
#08:27:51tsbereMight want to hit open-ils-general while you are at it, though.
#08:27:59csharptsbere: I'm filling out a "Contact Us" web form
#08:31:51tsbere prepares for a week or two of daily "We are giving you preferred access to this domain that is going to expire from us sitting on it for five years soon because you have a similar domain....if you are willing to pay 50x the price you should be willing to!" emails
#08:32:37jefftsbere: hmm?
#08:33:37tsbereOur domain registrar email address got one this morning. They will send another every day for the next week or two, each coming from a different address and referring to different websites to take advantage of the offer.
#08:34:04jefflovely. enjoy!
#08:34:17tsbere"You have the .org version of this site! We want to sell you the .com at 1000% or more markup!"
#08:42:45csharpseems like Mailman should've flagged the LinkedIn email and held it for approval...
#08:42:53csharp looks at the settings
#08:44:11jeffmailman does only basic checks of From: and possibly Sender: -- since the linkedin email had Ephraim's return address, and Ephraim is permitted to post, the linkedin email was sent to the list.
#08:44:32csharpjeff: good to know
#08:44:39jeffI wouldn't worry too much about it, or spend too much time reacting to it. Better things to do, and all that. :-)
#08:44:54tsbereadd a filter for "X-LinkedIn-Class". If that header shows up, hold the message?
#08:45:01csharpjeff: yeah - definitely - just wanted to nip it in the bud ;-)
#08:46:45dbs has joined #evergreen
#09:01:10Dyrcona has joined #evergreen
#09:02:39Meliss has joined #evergreen
#09:03:48shopkins has joined #evergreen
#09:06:55yboston has joined #evergreen
#09:12:02shopkinsHi. I'm having a problem logging into the staff client. Logging in via srfsh works fine - looks like the same issue as enhancin has been posting about. Everything worked on 9-6 then we loaded a large number of patron records, hold and transactions, now nothing
#09:12:30shopkinswe are in a brick environment and I have completely rebooted all servers involved with no luck. Any suggestions?
#09:13:20bshum has quit IRC
#09:13:20bshum has joined #evergreen
#09:14:46dbwellsshopkins, do you also have problems logging in via srfsh when using the public router, as enhancin does?
#09:17:44shopkinsdbwells: yes I get a bootstrapping error
#09:18:26dbwellsshopkins, can you paste that somewhere?
#09:18:57shopkinsdbwells: I did end up getting a "SUCCESS" message after a second try
#09:20:30dbwellsshopkins, well, that seems positive. I am guessing your problem is different than enhancin then, which is good, because nobody has cracked that one.
#09:21:04dbwellsshopkins, what error do you get when logging in via the client?
#09:22:59shopkinsdbwells: Copied "Network or server failure. Please check your Internet connection to 134.241.192.80 and choose Retry Network. If you need to enter Offline Mode, choose Ignore Errors in this and subsequent dialogs. If you believe this error is due to a bug in Evergreen and not network problems, please contact your help desk or friendly Evergreen administrators, and give them this information: method=open-ils.actor.org_unit_settin
#09:24:02dbwellsshopkins: your error got cut off at "method=open-ils.actor.org_unit_settin..."
#09:27:34tsbere looked at the IP address and almost thought shopkins was talking to a MVLC server, before he finished reading the IP address
#09:29:41shopkinsdbwells:http://paste.lisp.org/display/124637
#09:30:07jenny has joined #evergreen
#09:36:15dbwellsshopkins: it seems possible that you have an invalid (i.e. not JSON) org_unit setting. Try this query: select id,evergreen.is_json(value) from actor.org_unit_setting;
#09:36:25dbwellsdo any say 'f'?
#09:37:10tsbereselect * from actor.org_unit_setting where not evergreen.is_json(value)
#09:37:25dbwellsor that :)
#09:38:35tsbere finds that the ou, name, and value are all useful to figure out what broke
#09:39:28shopkinsdbwells: several say false
#09:40:27dbwellsshopkins: okay, if you try tsbere's query you can easily see what is wrong, hopefully.
#09:42:49shopkinsdbwells: I tried tsbere query and get 12 rows returned. Not sure exactly what I am looking for or at
#09:44:08dbwellsshopkins: the 'value' column will have something in it which is not valid JSON. If you have trouble figuring it out, it is likely safe to delete the offending setting rows, then re-create the settings properly in the UI (once you can log in).
#09:49:14shopkinsdbwells: ok I will delete and let you know what happens
#09:50:52dbsdbwells++
#09:50:54dbstsbere++
#09:54:49dbs had no awareness of the evergreen.is_json() function or that non-JSON would break things horribly
#09:55:16phasefx has a pullrequest branch adding that as a check constraint
#09:55:48phasefxI don't think you can break things through the UI
#09:56:03phasefxcould be wrong though :)
#09:56:24berickright, the UI will json-ify everything coming in
#09:56:48berickdbs: about to merge working/user/dbs/tpac-css-buttons (then mtg), then master merge, booyah
#09:57:06dbswow: our JSPAC home page makes 83 requests for 406K of data, the TPAC home page makes 16 requests for 39K of data
#09:57:20dbsberick++
#09:57:31berickdbs++ killin' the images
#09:57:34dbs will pick up phasefx's pullrequest, sounds like an excellent one
#10:00:04dbsshopkins: fwiw, I bet many of your non-JSON issues were something like (((SET value = 'foo'))) instead of (((SET value = '"foo"'))) -- note double-quotes required around string values
#10:00:08jefftpac hacking should be done against collab/berick/template-toolkit-opac-master-merge and best against a fresh install from that branch, or can the tpac bits work against say, 2.1-rcX?
#10:00:17berickfor future reference, a pre-image-cleanup branch is living at esi/template-toolkit-opac-master-image-buttons, since I might need it for my own nefarious purposes
#10:00:24shopkinsdbswells: Ok I deleted those lines and can log in now. As far as breaking things through the UI, we imported these settings from a training machine to our production machine so the import could have gone wrong
#10:00:49shopkinsdbs: thanks for the info and the fix. Will check on the double quotes
#10:00:50dbsberick: cool, preserving history is good
#10:02:11berickjeff: best done w/ fresh install. it moves a lot of stuff around, so 2.1 is pretty much out of the question
#10:02:12dbs hopes that someone with greater Web/CSS skills than his own will tackle the more daunting task of moving to a non-fixed-width layout
#10:02:33jeffberick: thanks
#10:03:59tsbereWait, tpac is fixed width right now?
#10:04:03tsbere might have to tackle that
#10:04:11dbsheh - search results page for a search that results in a single hit is 18 requests on TPac vs. 120 requests on our JSPAC (which is more than default skin, but still)
#10:04:27dbstsbere: yeah, 974px IIRC
#10:04:32jeffhrm. before i try to chase this down, has anyone else noticed the following in an Evergreen Makefile.install output? /bin/bash: line 0: [: too many arguments
#10:04:56dbsjeff: two pg_config files? What version of the Makefile.install?
#10:05:09jeffrel_2_1 branch
#10:05:29dbsand completely up to date?
#10:05:40jeffas of last night
#10:05:48jeffchecking to see what i might be behind on now
#10:06:02dbsand what distro?
#10:06:13jeffsorry, forgot to mention. debian-squeeze
#10:07:09jefffully up to date. oh, maybe the "is old postgres installed" checks, you're thinking?
#10:07:23dbsyep, the checks that I committed yesterday
#10:07:52dbshttp://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=45f2b618fd0485e585b6744a51b9e9719fe1f038 and http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4194c87743f278b7041e938531adacd3caaf50e6
#10:08:39dbsjeff: freshly installed debian-squeeze image?
#10:08:52jeffnot fresh, but close.
#10:08:53dbs wonders if the checks fail in the absence of any packages
#10:09:09dbse.g. if libpq5 is not installed at all, kabooms?
#10:09:21jefflibpq-dev libpq5 were present and were upgraded by Makefile.install
#10:09:41dbshuh. More context, such as a paste, would be useful then
#10:09:51dbsso that we have a clue about what is blowing up where.
#10:10:18dbs was testing on debian-squeeze and did not see said blowups
#10:10:56jeffeverything seemed to work well, i just noticed the error in the output. looking deeper.
#10:13:00jeff$ aptitude versions libpq-dev | grep ^i | sed 's/^i[ \t]*//' | cut -d. -f1
#10:13:00jeffA 9
#10:13:10jeffthat's the extra argument, i think.
#10:13:23jefffull line before sed is:
#10:13:24jeffi A 9.0.4-1~bpo60+1 squeeze-backports 100
#10:14:14jeffof course, that's after it was upgraded by Makefile.install -- presumably before it was something starting with i A 8.4.8-0squeeze2
#10:15:21jeffdbs: is that helpful?
#10:15:54dbsjeff: I would say so.
#10:17:10dbs needs to rebuild vbox drivers before retesting
#10:17:55dbsOf course, if you want to supply a fix that would be even better
#10:20:45jefftwo or three characters, but i'm game to supply the change and have you test :)
#10:20:46tsbereIs there a minimal number of things that need to be restarted if I edit a SELECT query in fm_IDL.xml (instead of restarting everything)?
#10:22:31bericktsbere: I believe restarting services listed in the controller= attribute are all that are needed. in most cases, restart_c
#10:23:12tsbereHmmm. cstore, pcrud, reporter-store. That all covered by restart_c?
#10:23:20berickyep
#10:27:06tsbereThere an easy way to ask the backend "what is the query for this IDL entry?" via, say, srfsh?
#10:29:11berickhm, not that I recall
#10:29:47agJohnAnyone encountered a problem like this (apparently the exception originates in the Perl DateTime module)?
#10:29:49agJohnopen-ils.storage [ERR :16186:action.pm:919:] Error processing overdue circulation [1104732]:
#10:29:50agJohnInvalid local time for date in time zone: America/Chicago
#10:29:51agJohn(Running EV 1.6.1.8 on Ubuntu 10.04 w/ DateTime info as per paste)
#10:31:08agJohnExcept that the paste apparently didn't work....
#10:31:22tsberehttp://paste.lisp.org/display/124640 That paste?
#10:32:05agJohnYeah, that'd be it (how come it didn't pop up in the display here?).
#10:34:23tsbereThe bot isn't in the channel
#10:34:35jefflong story... paste.lisp.org is broken when posting to channel sometimes. you can get the list of pastes for #evergreen here, and pick yours and send the link here manually: http://paste.lisp.org/list/evergreen
#10:34:39tsbereSo the server gives a white screen o death instead of having sane "the bot isn't there, ignore it then" code
#10:36:12agJohnAh so. OK. So, to the error. The only exact reference I've found to this kind of problem is this: http://www.44342.com/perl-f863-t13674-p1.htm (5 years old and no replies in the forum).
#10:38:01agJohnThe dates in the circ in question are not even close to a date related to, say, a transition to daylight time. So, this is all very puzzling.
#10:40:43agJohnReferring to the cpan m info, is this saying there's a 0.70 version and the installed version is 0.52? Is that as it should be?
#10:49:44senatoragJohn: i'm not sure about cpan m, but if you're trying to determine what version of the perl module DateTime you have installed, this is the way to do it from a shell: perl -mDateTime -e 'print $DateTime::VERSION,"\n";'
#10:52:22agJohnYup; that also gives 0.52. So, the question becomes, is there a reason for using the 0.52 version with EV or is that just what happened to land on the server (in /usr/lib/perl5) when it was originally set up and I can go ahead and upgrade and perhaps solve this problem?
#10:53:49mrpeters-islheck FWIW we're on 0.42
#10:53:53senatorno particular version of DateTime is targeted by evergreen as far as i know. i've seen older and newer versions than that work fine.
#10:54:12agJohnGiven the relative silence about the problem itself, I guess I'll try it on a test environment and see if a newer version happens to resolve it.
#10:54:20mrpeters-isl0.66 in some other places
#10:54:40agJohnThanks for the info on the version number, mrpeters-isl & senator.
#10:54:51mrpeters-islno probelm
#10:55:15sal_ has joined #evergreen
#10:59:20dbsagJohn: i was on a call. did you paste the actual data from the offending circ in question?
#11:00:01dbsand/or the date that the server thinks it currently is?
#11:00:02agJohnNope, but I'll add it as an annotation.
#11:01:35dbsalso, if distro updates for time zones have been applied (I'd expect/hope DateTime to rely on the OS for its info, but could be wrong)
#11:05:52bshumDoes anyone know who this sammywilson wiki user is and why they're editing old pages to put links to stuff? Spammer?
#11:07:34gmcharltbshum: based on http://www.evergreen-ils.org/dokuwiki/doku.php?id=advocacy:newsletter&do=diff, spammer
#11:08:02moodaepoWouldn't someone have to have approved the account?
#11:08:39phasefxnot if there's a hole in dokuwiki
#11:08:53moodaepophasefx++
#11:09:06moodaepo goes to check on that...and will delete the user
#11:10:04agJohndbs: I've added the circ data to the paste: http://paste.lisp.org/display/124640
#11:10:05agJohnAlso worth noting that the DB in question was just moved from one server to another (and it used to be physically housed in the Eastern timezone; it appears that the DB was set to just use the local timezone on the server).
#11:10:58phasefxmoodaepo: I reverted that page
#11:12:28kmlussier has quit IRC
#11:12:47dbsagJohn: huh. I would try changing the due date of "2010-09-23 23:59:59" to "2010-09-23 12:59:59" just to see what happens for that one circ
#11:13:10dbsbut I have no experience with migrating databases from one timezone to another
#11:14:18agJohnThis is not an isolated problem; hundreds of errors of this type thrown by the batch processes for dealing with overdues and standing penalties.
#11:15:19kmlussier has joined #evergreen
#11:15:33agJohnSo, it's not going to be easy to see what happens with one particular circ, but I'll give that (or something similar) a shot.
#11:16:13agJohnThe timezone info on the server is surely current enough for US timezones--it was just set up last month....
#11:16:34agJohnI thnk I'll try updating the DateTime module just for the heck of it.
#11:16:55agJohnIt sure seems like it must be a bug in DateTime, ultimately.
#11:18:31mrpeters-islagJohn: I'm not seeing an error in your paste. Perhaps I'm overlooking it?
#11:18:56agJohnSorry, the error (stupidly) was in the main chat text.
#11:19:14agJohn(Was ONLY in the main chat text; I'll add it to the paste.)
#11:19:23mrpeters-islahh now i see
#11:19:55mrpeters-islwasn't going back far enough
#11:20:41mrpeters-islok, so just a hunch, but i wonder if the database is appending "-5" to that
#11:21:01mrpeters-island its saying wait, central time zone can't be 2010-09-09 16:02:03.876097000-5
#11:21:33bericktsbere: am I reading this rigth? [http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/sql/Pg/110.hold_matrix.sql#l146] if circ.holds.usr_not_requestor is set, user and requestor profile groups are swapped?
#11:22:48berickand if so, why do we want the user profile set to the requestor profile?
#11:23:40agJohnmrpeters-isl: meaning it's trying to subtract 5 hours (or 6) but the effect is all wrong because of the textual representation?
#11:24:49mrpeters-islyeah, im thinking its trying to apply the wrong offset
#11:24:54mrpeters-islhave a look at postgresql.conf
#11:24:56mrpeters-isl#timezone = unknown # actually, defaults to TZ environment
#11:25:07mrpeters-islmaybe we can look at your timezone settings in there, if any
#11:25:56mrpeters-islbut im thinking since it's the system time which is America/Chicago you might be trying to insert a timestamp with timezone that doesn't match a possible offset for America/Chicago
#11:27:13mrpeters-islsince chicago is in DST, and your date is within the DST time period i bet it's expecting UTC -6
#11:27:46vagojan has joined #evergreen
#11:27:54mrpeters-isli bet if that date were sometime after November or whenever we switch now (who ever remembers!) it'd accept the -5 that it's probably using from when it was in the Eastern timezone
#11:28:43agJohnYou may be onto something. But I'm not sure why the date/time in question would evaluate to invalid, rather than just being off by one hour (in the case you describe).
#11:29:27mrpeters-isli'm just thinking if you were trying to insert something other than -5 or -6 it would fail because any other offset isn't valid for that TZ
#11:30:10vagojan has left #evergreen
#11:30:12agJohnAh, understoood. So you're thinking it's essentially a configuration problem of some kind.
#11:30:14agJohnI'll sure check the postgresql.conf. The entry in the DB's pg_catalog.pg_settings has timezone = local (use the system date/time).
#11:30:55mrpeters-islyeah, kind of just taking a blind stab at it but maybe something to try playing with
#11:31:23agJohnMuch appreciated. I hadn't come up with anything coherent to blindly stab at!
#11:31:35mrpeters-islmaybe adjust one of your inserted circs to include -5 and see what happens
#11:32:02mrpeters-islhttp://stackoverflow.com/questions/1789862/scheduling-scripts-at-a-different-timezone
#11:34:56mrpeters-islagJohn: http://pastie.org/2526956 (from TimeZone.pm)
#11:35:20mrpeters-islthis has gotta be the problem
#11:38:23mrpeters-islagJohn: also see "If you specify an ambiguous time, then the latest UTC time is always used, in effect always choosing standard time. In this case, you can simply subtract an hour to the object in order to move to saving time" on http://search.cpan.org/~drolsky/DateTime-0.70/lib/DateTime.pm
#11:38:59agJohnYes, but, the problem should only occur in the Spring on the night when transitioning to CDT. For instance, the UTC value that corresponds to CST 2:30 am does not exist in the timezone--there is no 2:30 am (it jumps from 2:00 am to 3:00 am).
#11:41:47agJohnThat's not to say it couldn't be a bug that leads to incorrectly deciding that this is the case when it is not.
#11:43:05dbs has quit IRC
#11:44:11agJohnThat is, if the time were ambiguous by an hour, it wouldn't matter. But, my guess is that you are correct and that the time being 23:59:59 (with the date) is invalid because it's effectively changing the date. In which case, dbs's solution of moving the time to close to noon rather than midnight should fix it.
#11:50:46agJohnE.g. 2010-09-09 24:02:03
#11:51:45agJohnis an invalid time. But I think it's more likely that the 23:59:59 time is the problem and it might end up being 24:59:59.
#11:51:50akilsdonk has joined #evergreen
#11:52:57DyrconaTime: such a simple concept, yet not.
#11:54:03Dyrcona"It's a bunch of wibbly-wobbly, timey-wimey stuff."
#11:54:15tsbereberick: That is to preserve existing behaviour(ish) on upgraded systems from before usr was checked at all
#11:56:42tsbereberick: See http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=Open-ILS/src/sql/Pg/110.hold_matrix.sql;hb=refs/heads/rel_2_0#l77
#11:59:22dbs has joined #evergreen
#12:02:38kmlussier has quit IRC
#12:02:59kmlussier has joined #evergreen
#12:03:10moodaepophasefx: Helps prevent spammers if I hadn't forgotten to disable open registration...DO'H
#12:03:29phasefxoy
#12:04:27moodaepoI haven't allowed/created any new users so if you could take a quick look through users.auth.php and make sure they are legit it would be great, none of the users popped out when I looked just now.
#12:05:25bericktsbere: i guess I'm unclear on why, now that usr is checked, we want recipient.profile to bet set to requestor.profile. i would have assumed that circ.holds.usr_not_requestor only affected what the code uses as the requestor profile. IOW, http://paste.lisp.org/display/124641
#12:05:36eeevilso ... meeting?
#12:05:39bericks/bet set/be set/
#12:06:45tsbereberick: That paste isn't even valid, I don't think. Mine, as the comment says, swaps the two, rather than duplicating user into requestor.
#12:07:08bericktsbere: right, i'm saying duplicating is what we want
#12:07:18berickthe sql may not be valid, i don't know
#12:07:19tsberetwas a decision based on "before my code usr wasn't used, at all"
#12:08:46tsbereThe code as is lets you still do things based on user and requestor groups, but if you have that setting enabled swaps them. Which may be confusing, but still allows for things to function after upgrades.
#12:08:47berickagain, if I'm reading this right, in the 2_0 code, the only value that's changed is current_requestor_group (i.e. requestor_object.profile). In the latest code, both requestor_object.profile and user_object.profile are changed
#12:09:33tsbereand in the 2_0 code the usr_grp field in the table is ignored, 100%.
#12:10:12tsbereeeevil: Meeting sounds good.
#12:10:33berickok, i think there's some confusion about what circ.holds.usr_not_requestor is supposed to do, and it could very well be on my part. /me tables for now
#12:21:11berick*tap* *tap*
#12:26:03bshumWell, there was supposed to be a meeting. Anybody care to lead or note take? (I can roll through the agenda too)
#12:26:08bshumhttp://evergreen-ils.org/dokuwiki/doku.php?id=dev:meetings:2011-09-13
#12:26:24bshumThough I just noticed it's marked meeting leader: tsbere
#12:26:27bshum:)
#12:27:02tsbere led a previous meeting but made no promises for future ones
#12:27:18bshumMight just be a carryover from the previous meeting.
#12:29:02bshumAnywho, should we have the meeting or delay (since it's already past time and pretty quiet)
#12:29:20bshumThere's 3 action items listed, we could run through them quickly enough too
#12:29:27bshumIf everyone is here.
#12:29:41berick is here
#12:30:56akilsdonk has quit IRC
#12:31:42akilsdonk has joined #evergreen
#12:32:05phasefx is here
#12:33:36csharp shows up because decisions are made by those who show up
#12:33:49bshumHeh
#12:34:07bshumWell, the action items are about 2.1 status and tt-opac release notes.
#12:34:09phasefx moves that we rename Evergreen to Turpentine
#12:34:23bradl seconds
#12:34:35moodaepo motion carries
#12:34:45csharp changes the website and logo
#12:34:56akilsdonk has quit IRC
#12:35:23akilsdonk has joined #evergreen
#12:35:24moodaepobshum: Is the release notes berick & dbs then?
#12:35:35bshummoodaepo: That's right.
#12:36:36bshumGiven how quiet it is, I guess we're skipping this meeting officially. Unofficially I suppose we can talk about 2.1 and such too. Since I'm always interested to know when we get 2.1.0 cut :)
#12:36:48moodaepo+1
#12:37:31denialsbah, dbs was here but connection timed out
#12:37:34bericktpac release notes http://evergreen-ils.org/dokuwiki/doku.php?id=dev:opac:template-toolkit:release_notes
#12:37:45denialsberick++
#12:37:45dbs has quit IRC
#12:37:53moodaepoI guess meeting is back on...bshum
#12:38:16moodaepoberick++
#12:38:58denialsFWIW, Conifer is hoping to migrate to 2.2-ish in December, primarily for TPac
#12:39:18moodaepoconifer++
#12:39:29csharpTPac lives!
#12:39:44denialsmoodaepo: have you done any testing of the absolute latest TPac? Particularly interested in your keen web design eye
#12:40:11moodaepodenials: I moved the test server from hardy to lucid so got slowed down since yesterday
#12:40:47moodaepoBut hope to have an update in channel by the end of today
#12:41:17denialssweet: the more eyes, the shallower I am
#12:41:28senatormerge! merge! merge! feature branches off feature branches are getting too hard to keep up with
#12:41:33dbs has joined #evergreen
#12:41:40berickif there is no frantic waving of arms, I'm going to merge tpac to master after the meeting
#12:42:09dbs waves arms in excitement, not to be confused with franticness
#12:42:14tlilleberg has joined #evergreen
#12:42:22eeevil calls meeting to a close, so merging can commence
#12:42:22gmcharlt is frantically waving his arms doing the +1 cheer
#12:42:35jeff+1 \o/
#12:42:58moodaepo+1
#12:43:20berickexcellent
#12:44:38mmorgan has joined #evergreen
#12:45:22akilsdonk has quit IRC
#12:46:34moodaepoeeevil: About cutting 2.1 thoughts?
#12:47:16eeevilI want to do it right now
#12:47:21dbsthe "2.1 blockers" discussion had some candidates at the start but kind of devolved a bit
#12:47:26eeevilbut I've been waved off
#12:47:56gmcharlt will have some patches for the EDI blockers this week
#12:48:21moodaepogmcharlt++
#12:48:22dbsjamesrf mentioned https://bugs.launchpad.net/evergreen/+bug/800477 and https://bugs.launchpad.net/evergreen/+bug/800478
#12:48:23eeevilsome fixes have been ... I hesitate to say "demanded", but ... but, has anyone "strongly requesting" these fixes happen before 2.1.0 looked into them?
#12:49:00dbs did some groundwork exploration of some of the EDI madness
#12:49:14jeffhttps://bugs.launchpad.net/evergreen/+bug/843961 should probably be considered a blocker for those in replicated setups.
#12:49:53gmcharltjeff: that one is also in an ESI queue for this week
#12:50:02eeevilthere's an apparent problem with the marc editor, and its current inability to pick a record type (or show the record type dropdown) that I would add to the blockers list ... and will try to work on right away
#12:50:27jeffgmcharlt++
#12:50:40dbsgmcharlt++
#12:51:19gmcharltjeff: speaking of libraries using replication ... if you can do a once over to scare up any more, that would be great
#12:51:25dbsIs the "Funds transfer always transfers entire fund, not specified amount" bug (https://bugs.launchpad.net/evergreen/+bug/800478) on anybody's list?
#12:51:44gmcharltglitches, that is, not libraries using replication -- pretty I know who most of them are :)
#12:51:54eeevildbs: that may have been addressed actually, I'll check
#12:52:58jeffgmcharlt: if we find any, i'll be sure to pass them along. offhand, the "Refresh" button in holdings maintenance could probably benefit from being authoritative, but 1) not as large an issue as the bug I linked, and 2) might even be the same api call -- i haven't checked.
#12:53:29dbseeevil: cool; the other bug jamesrf reported (amounts are off when you have both encumbered and spent funds) is of interest too :) https://bugs.launchpad.net/evergreen/+bug/800477
#12:55:08berick will take a crack at 800478 and 800477
#12:56:48dbsberick++
#12:59:08berick grabs 0621
#13:02:08dbsjeff: fwiw, it's possible that debian improved their backports such that postgresql 8 + 9 could co-exist; they managed to do that in the past with 7 + 8
#13:02:46dbsjeff (or anybody else) - it would be great if that could be confirmed and all of the detection/removal hackery ripped out
#13:03:29jeffso, install squeeze -- install old libpq stuff, try to install 9 from backports without removing things?
#13:04:25dbsjeff: install squeeze + OpenSRF Makefile.install + 9 from backports (without Evergreen Makefile.install) for the most accurate test, I think
#13:04:57dbsIIRC, libpq gets pulled in by OpenSRF Makefile.install in the first place
#13:05:11berickjeff: http://svn.open-ils.org/trac/ILS-Contrib/browser/ESI-Examples/trunk/tools/eg_dev_squeeze_installer
#13:05:43berickit's a good reference, if you don't want the whole shebang
#13:06:20berickit installs pg via backports before anything else, which seems to work ok
#13:07:38berick lulz
#13:07:38berick# On branch master
#13:07:38berick# Your branch is ahead of 'origin/master' by 821 commits.
#13:07:47dbsawesome
#13:09:18eeevil821 delicious, templaty commits
#13:10:09agJohnIs there someplace in EV that gets the timezone other than just from the OS?
#13:10:33eeevilagJohn: the database can have its own TZ
#13:10:38akilsdonk has joined #evergreen
#13:10:53eeevilALTER DATABASE SET TIMEZONE TO 'America/New_York'; etc
#13:10:55agJohnThat part I understand; I'm just trying to verify that they're not out of sync.
#13:11:40agJohn(That is, the DB thinks it's in Central timezone and EV is picking it up from somewhere else.)
#13:12:02eeevilright, the db is other than the OS ... beyond that, no (unless you modify the env of the user starting evergreen processes)
#13:13:06eeevilUpdating 83e5388..b77e56f WHEEEE
#13:14:23agJohnSo does EV get the TZ from the DB or the OS? (If you can change it via the env of the user starting the EV processes)?
#13:14:42dbsberick: did you guys do any performance / stress-testing that compares oldPAC to newPAC? That would make a great blog post
#13:14:43eeevilagJohn: the db gets it from the db, the perl and c get it from the os
#13:15:05agJohnThanks.
#13:18:06berickdbs: we did load testing to look for memory leaks and make sure we could get good overall throughput, but it's difficult to compare UI apples to oranges (programaticaly) since rendering is handled so differently between the two.
#13:19:00berickif you run a web spider against tpac, you are getting pretty close to real page-delivery performance numbers, but jspac is a whole other beast
#13:19:16dbsberick: ah, that makes sense. You would need to do something like automate a browser and have it tell you when all jspac requests are complete for a given page
#13:19:29dbsE_OUT_OF_BOUNDS for our purposes :)
#13:20:05berickright, though we have collected API calls made on a given page for jspac and pouned on those, but yeah, still not the same
#13:20:12berick*pounded
#13:24:13csharpwow - that git commit message was 4MB large and required administrative approval ;-)
#13:26:07Dyrconattopac-master-merge was merged. :)
#13:33:31akilsdonk has quit IRC
#13:39:39edoceo has quit IRC
#13:53:07edoceo has joined #evergreen
#13:53:09csharpI'm doing a practice 1.6.1.8 - 2.0.9 upgrade on a snapshot of the PINES production DB...
#13:53:51tspindler has joined #evergreen
#13:53:57csharpwhen I run the 1.6-2.0 upgrade script, I get: ERROR: could not access file "$libdir/slony1_funcs": No such file or directory
#13:54:22csharpso, does that mean that slony-I is required for upgrading servers?
#13:54:42csharpit's not in the pre-reqs for a standalone DB server, so I didn't have it installed
#13:54:43eeevilcsharp: you didn't remove some slony triggers from your restored db
#13:55:18csharpeeevil: ah - thought I had gotten them by removing the replication table I dropped
#13:55:39eeeviltable? no, lots more than one table
#13:55:42gmcharltcsharp: try a drop schema _replication cascade;
#13:56:57csharpok - thanks for that eeevil and gmcharlt
#13:57:11csharpthis is one reason I'm doing this - to learn ;-)
#13:58:55Dyrconaalways better to practice a few times before doing it for real.
#13:59:54gmcharltDyrcona: no sense of adventure ... ;)
#13:59:59csharpDyrcona: yeah - this is my "break - rebuild - repeat" box
#14:00:24csharp has always been intimidated by postgres
#14:01:27csharpI'll say in the same breath though, that the more I learn, the more straightforward it all seems
#14:01:49edoceo has quit IRC
#14:03:27bshumYay for upgrades, wish I were upgrading already
#14:04:16csharpbshum: you can come visit when we upgrade to 2.0 and relive the memories }:-)
#14:05:55bshumcsharp: I would be depressed thinking about the cache issues with our 2.0 upgrade. 2.1+ ftw!
#14:06:15csharpaw frak - I forgot about that!
#14:06:31csharp had tried to wash the memories away with booze and pills
#14:07:09bshumI keep adding things to my list of reasons I'm so eager to upgrade out of 2.0.
#14:07:41bshumPerhaps PINES should consider skipping over it ;)
#14:08:07dbscsharp: jeff and _bott_ went from 1.6 -> 2.1
#14:08:42csharpdbs: might be worth considering...
#14:08:43jeffthat statement gives me far too much credit. _bott_ and dkyle did the upgrade. :-)
#14:10:30phasefxmoodaepo: btw, I browsed through this and didn't see any more spammy links: dokuwiki/data/pages# grep -R 'http://' * | cut -f2- -d: | perl -ne 'while (/(http:.+?)[\s\]]/g) { print "$1\n"; }' | sort | uniq | less
#14:10:51phasefxbut there's a lot there
#14:12:43dbs just went through the soul-destroying task of cleaning deferred mail (spam) out of the security list
#14:13:35csharpuh oh - postgres problems: http://pastebin.com/PHi3in5P
#14:15:08jamesrfdid anyone notice that xulrunner 1.9.2 disappeared off of releases.mozilla.org?
#14:15:51sal_jamesrf: Its renumbered replacement works...
#14:16:10jamesrfwhat's the renumbered replacement?
#14:16:36sal_3.6.20
#14:16:44jamesrfok thanks i'll give that a whirl
#14:17:00sal_(I ran into this in August--see logs from 8/17-18)
#14:17:59csharp would like to see the EG community host those kinds of dependencies within our own universe - CPAN stuff too
#14:19:50collum has quit IRC
#14:21:14sal_csharp: does that include Postgres 9.0 (gdr)
#14:22:14csharpsal_: it's just an idea (I sure people would point out downsides), but I would think we could host any specific versions of software EG requires
#14:22:37dbswe already do, for things like libdbi
#14:22:58csharpif the packaging project continues and has committed maintainers, they could be in .deb/.rpm format
#14:23:08sal_* only brings it up because she seems to have been the first (vocal) one burned by both postgres and xulrunner version changes... :-)
#14:23:25csharpyou're not the first!
#14:23:27csharp:-)
#14:23:31gmcharlt would prefer that we do the bare minimum of maintaining packages for other projects, however
#14:23:38sal_* just the loudest ;-)
#14:23:48gmcharlti.e., do it if we have no other choice
#14:23:55edoceo has joined #evergreen
#14:24:30csharpwell, Mozilla's a great example - they have pulled older xulrunner versions down before
#14:24:49phasefxlong term I'm in favor of jumping ship there
#14:25:02csharpphasefx: you know I agree with you there ;-)
#14:25:48csharpbut the CPAN stuff too - somebody's typo somewhere else can blow up an Evergreen install
#14:25:49phasefxwe could lock down on whatever the last of the 1.9.2/3.6 happens to be.. warn folks not to put remote sites in their portal pages (bad idea even now)
#14:25:56bshumWell, there's precedent with keeping older xulrunners around if I remember the steps for 1.4 SC building included pulling a copy from the phasefx directory.
#14:26:40phasefx was actually really excited about not having to do that and finally being able to follow the latest xulrunners (moving away from 1.8), right up until remote xul went away
#14:26:43Dyrconacsharp: That's the joy of CPAN. It doesn't just affect Evergreen.
#14:27:14jeffdbs: inspired by your earlier performance musings, and something i've both been wanting to do for a long time and suddenly have a good reason to spend time on... here are some quick and dirty load-search-results tests using selenium and python: http://paste.lisp.org/display/124644
#14:27:17dbssomeone made a CPAN bundle for Evergreen ages ago :)
#14:27:18csharpDyrcona: agreed - I'm just saying we could keep a repo of known working versions and let CPAN be CPAN
#14:28:07gmcharltcsharp: until our working versions become non-working versions because of (say) a security update to a CPAN module that doesn't get propagated
#14:28:13csharpthat volatility also means that fully replicating the EG 2.0.9 I build today might be very difficult later
#14:28:57gmcharltI'm not unsympathetic -- but it can be a surprisingly large amount of extra work that trusting to the broader Perl ecosystem can help deal with
#14:29:00dbsjeff: cool! now you just need to run a ton of those against jspac vs. tpac and come up with some amazing comparisons!
#14:29:11csharpgmcharlt: (not volunteering here - just musing) that could be a volunteer role in the project - to periodically check for updates and rationales behind them
#14:29:22dbs hopes that the amazing comparison isn't "tpac is surprisingly slower" :)
#14:29:40phasefx puts csharp in charge of the Evergreen Linux Distribution :)
#14:29:46Dyrconasixpac and twopac?
#14:30:09dbscsharp: I was thinking of something similar - putting together a list of "Ancient Things Upon Which Evergreene Dependeth" and associated bugs for people interested in tackling
#14:30:09jefftoward that end, is there a current install somewhere that exposes both the opac and tt-opac?
#14:30:13csharpphasefx: I can dig out the email I sent to Open-ILS-General in 2008 saying I'd love to see a debian installer hack
#14:30:59Dyrconajeff: my dev machine does, but its closed to most of the world.
#14:31:23dbse.g. Class::DBI 0.9.7 / 3.0.1, Dojo 1.3, XULRunner the remote XUL edition - many of which will prevent Debian/Fedora/other official packaging
#14:31:29dbsfire alarm
#14:31:30Dyrconait also hasn't been updated since yesterday morning.
#14:31:35jeffdbs: have fun!
#14:32:07berick looks for the fire alarm in his basement
#14:32:21Dyrconawe're about due for a fire drill ourselves....
#14:32:26csharpif more of my time could be spent on that kind of thing I would definitely do something around packaging/maintaining
#14:32:39csharp wishes he had a clone sometimes
#14:32:50csharpcp csharp csharp-clone
#14:33:04Dyrconadefinitely an advantage in keeping a clone of Dojo, since Eg requires some additional patches.
#14:33:35DyrconaCSharp clone = Object.clone(csharp);
#14:33:49edoceo has quit IRC
#14:33:54csharpheh
#14:33:55gmcharltDyrcona: more of an argument to upgrade to current Dojo; ditto for Class::DBI -> something more recent
#14:35:48jamesrfphasefx: was wondering if you saw this: https://github.com/jvillalobos/Remote-XUL-Manager
#14:35:55csharpwell, if the idea catches fire, GPLS can provide hardware (or another VM) - FYI to all
#14:36:27phasefxjamesrf: I had not
#14:37:09edoceo has joined #evergreen
#14:37:58bjwebb has joined #evergreen
#14:38:05tsbereIf there is a whitelist, we should be able to manipulate it.
#14:38:13phasefxjamesrf: I think remote xul is going to be even more of a non-first-class citizien going forward; stuff was already broken in prior versions
#14:39:07edoceo has quit IRC
#14:39:10Dyrconadoes the whitelist also exist in XulRunner?
#14:39:12phasefxbut.. sure would be nice to stick it out until it becomes painful again
#14:39:21edoceo has joined #evergreen
#14:39:30Dyrcona finds XulRunner to be painful anyway.
#14:39:33edoceo has quit IRC
#14:40:31edoceo has joined #evergreen
#14:40:51tsberephasefx: I can look into that at some point in the near(ish) future
#14:41:02edoceo has joined #evergreen
#14:41:23phasefxtsbere++ sounds good to me. jamesrf++
#14:41:24jamesrfyeah it's really probably a question of buying some time, i have no idea how much work removing the remote xul would be
#14:41:36tsbere looks at a hold targeting issue first, though
#14:43:08phasefxwe can move bits and pieces to local xul incrementally.. I tried something wholesale/automated, and it scared me. Alternately, we can embrace the dojo and replace things with it incrementally, and eventually drop xulrunner. More fun, more pain, would be throw it all away and start over with some new hot technology stack :)
#14:43:29phasefxlike tcl/tk
#14:43:48jeffapache rivets!
#14:44:10phasefx _has_ been playing with ncurses
#14:44:16tsbereFrom a printing POV I think we still need an actual client
#14:44:29Dyrconalpr ?
#14:44:31jeffi'm favoring a helper app for printing.
#14:44:42phasefxif we do web-ased, we could still.. yeah, plugin, extension, helper app
#14:44:46phasefxweb-ased :)
#14:45:05Dyrconamissing an 's'
#14:45:12phasefxmissing a letter, but which one .. yeah :D
#14:45:43Dyrconacould have a competition to see who can produce the coolest client.
#14:46:45DyrconaI know some people who would like to see it all in the browser, as tsbere pointed out though, printing there is a pain.
#14:49:01jeffi can see the marc editor being potentially problematic as well, but a not-web cataloging client and web everything-else seems attainable.
#14:50:09jeffbrowser offline storage capabilities may have matured enough to make offline-mode circ possible as well. i've been doing a bit of thinking/playing. perhaps time for a blog/list post.
#14:50:35dbsMOAR COAD
#14:51:13phasefxreally need more interest from folks with resources
#14:51:21jeffdbs: i just fed you a working branch -- you're hungry again? ;-)
#14:51:24jeff ducks
#14:51:47dbsMOAR COAD MOAR COAD
#14:53:30Dyrconaphasefx: we will soon have slightly more resources.
#14:53:53phasefxyay
#14:56:12tsbereFor the record, it is currently possible to get a frozen hold to capture. :(
#14:56:32_bott_ has quit IRC
#14:56:44jefftsbere: i've seen scattered examples of that. have you found a code path?
#14:57:17_bott_ has joined #evergreen
#14:57:23tsberejeff: Yep. I can reproduce it!
#14:57:29tsbereI can also PATCH it. :D
#14:58:09tsberehttp://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/tsbere/hold_frozen_no_targeting
#15:00:33jefftsbere++
#15:00:51tsbere goes to open a launchpad bug
#15:02:37phasefxman, they want to drop enablePrivilege as well
#15:03:32tsbereI suspect https://bugs.launchpad.net/evergreen/+bug/849312 should go into 2.1. Maybe 2.0?
#15:03:37jeffso, if cataloging was xulrunner, and autoupdates handled pushing xul (thus, no remote xul), what does the elimination of enablePrivilege break?
#15:05:09phasefxfor an all local app, I can't think of anything
#15:06:29tsbereI think circ would need to be xulrunner too, for receipt printing purposes.
#15:06:50dbsjeff: was the reason for echoing LIBPQ & the next layer of indenting primarily debuggin? Considering replacing with: if [[ -n "$LIBPQ" && "$LIBPQ" -eq "8" ]]
#15:07:10tsbereBecause I don't want to think about the horror of "make sure you are using the right browser with the right extension loaded" at circ desks
#15:07:27phasefxfolks print receipts with web-based selfcheck
#15:08:01phasefxI'd hope they don't remove the print silently pref, even though we may have to start setting it by hand (or extension)
#15:08:02tsbereAnd that is wonderful until you hit "holds may print to a different printer than other circ-related receipts"
#15:08:22tsbereAnd the inability for browser-based to pick printers for security reasons
#15:10:18collum has joined #evergreen
#15:10:32phasefxyeah, printing from web browsers suck
#15:10:58bshumSpeaking of printing receipts off the web-based selfcheck...
#15:10:58phasefxbut it may be "good enough"
#15:11:03phasefxor not
#15:11:51bshumIs it possible to change the template definition (or find some other way) to make it print as though it were on a receipt printer roll instead of normal sized paper?
#15:11:51Dyrconaprinting in general is a joke on computers.
#15:12:17tsberebshum: Printer settings in the browser?
#15:12:24DyrconaI do believe printing began when some guys at IBM were bored and said, "What happens if we hook one of these up to a Selectric?"
#15:12:40tsbere finds he has to select "Roll Paper" on all the epson drivers when a non-receipt printer was selected before
#15:13:12bshumtsbere: Right, I changed the options there and I can do one of two things, have it print at scale (meaning tiny, tiny fonts resized to fit the page onto the roll paper) or full size, leaving the edges of the receipt going off the edges.
#15:13:28bshumSince the template was designed with full sized paper in mind.
#15:13:38bshumAnd the lines don't seem to wrap
#15:13:55tsbereDunno. When I select roll paper everything starts wrapping.
#15:13:57bshumJust curious, didn't mean to derail the brainstorming of clients :(
#15:14:22Dyrconabshum: You are selecting roll paper in the Windows printer driver, right?
#15:14:45bshumDyrcona: Well, it's not a windows machine it's a Ubuntu workstation, but yes, I believe that was selected.
#15:15:11DyrconaAh....Good luck with that! :)
#15:15:37bshumThat's kind of what I thought :)
#15:16:12DyrconaI don't print receipts from Ubuntu, much, 'cept when I use our little thin client. (Not sure if it is Ubuntu.)
#15:16:54bshumIt was easier to setup the selfcheck workstation at the time using Ubuntu, though now I'm filled with regrets as always.
#15:17:20jeffdbs: sorry, the echo snuck in. twas debugging.
#15:17:48tsberebshum: Still haven't had issues on ubuntu with roll paper. But haven't done much beyond transit slips there.
#15:17:50jeffdbs: i attempted to use -n tests and was unsuccessful for unknown reasons.
#15:18:22dbsjeff: hmm. seemed to work here; I'll deinstall all postgresql stuff and try it again
#15:18:28bshumtsbere: Right, we were playing with those fancy self-check receipts that are generated using A/T on-demand, I think. The contents of those pages hated the roll paper.
#15:18:58jeffdbs: i'll re-test here. i'm also installing squeeze to test "is this even needed"
#15:19:08dbssweet
#15:20:05dbs was doing light research on the occasional failure of self checkouts to desensitize materials and has concluded that we should just turn our gates off
#15:20:14phasefxhttp://www.amplesdk.com/examples/markup/xul/views/ (I know we've seen this before)
#15:20:45Dyrcona is doing heavy research on the failure of SIP2 self-checks to occasionally pay fines.
#15:23:46phasefxwe really make too much use of stuff like xulG though.. that code is tied to mozilla, and a xul-like won't help
#15:24:08tsbereYou know, the client needs so much work to make it work after the current xulrunner major version we are using I am not sure it is worth figuring out some stuff right now. <_<
#15:24:33tsbere can't test xul whitelist stuff without some other overhauling, for example
#15:24:55dbsjeff: hmm, looks like backports now happily upgrades libpq* to 9.0
#15:25:19dbsbut... what? libapache2-mpm-prefork and libapache2-mod-perl2 get removed?
#15:27:06dbsprolly should have done safe-upgrade first, might be confusing state of locally installed packages
#15:27:16dbs changes nick to dbstreamofconsciousness
#15:28:40dbs recommends we solve the web client printing problem the obvious way: Google Cloud Print
#15:29:06dbsThat should make the paranoid / legally not allowed to use such services really freak out
#15:30:20Dyrcona freaks out.
#15:30:25Dyrcona:)
#15:30:35Dyrconaor printeron.
#15:31:56phasefxpoint a polaroid at the screen
#15:32:16tsbereThat mean we need to supply wooden tables?
#15:34:00sal_ has quit IRC
#15:35:35sal_ has joined #evergreen
#15:40:41tsbere still can't get later versions of xulrunner to *start*, with or without evergreen stuff in them
#15:40:46dbsas far as I can tell, debian lenny no longer freaks out about libpq5 8 vs. 9; it will upgrade libpq 8 to 9, and not remove postgresql 8.4 server in the process
#15:41:20dbsSo that leaves just ubuntu-lucid, which I do not have a VM to test with; then maybe we can make this whole mess go away.
#15:41:36sal_dbs: will maverick work?
#15:41:47sal_I have plenty of VMs :-)
#15:42:11dbssal_: we only recommend LTS releases so really kind of have to test Lucid
#15:42:28bshumdbs: What are we testing with Lucid? I have PG 8 installed on a few.
#15:43:24dbsbshum: seeing whether backports will happily run install_pgsql_client_debs_90 without all of the existing libpq5 detection / removal hackery
#15:43:48Dyrconadbs: we used psql 9 on lucid. in dev and production.
#15:43:51bshumAh, so, grab a copy from master or some other branch that we're testing on.
#15:44:20dbsDyrcona: that's not the question
#15:44:30Dyrconayou're talking about for upgrades.
#15:44:36Dyrconanever mind.
#15:44:43dbsbshum: just running "aptitude postgresql-client-9.0" on an updated Lucid with backports should give a good feel
#15:44:54dbserr, aptitude install postgresql-client-9.0
#15:45:21dbscourse that'll be 9.1 one of these days :)
#15:45:33bshumHeh
#15:46:13jeffdbs: i pushed a (mostly pointless, now) update to that working branch removing the echo statement and simplifying the logic. if debian no longer requires the removal of those packages, great! do we have any point where we recommend the user enable backports in sources.list or equivalent?
#15:46:31dbsIn the fine README
#15:46:32tsberephasefx: Given the issues I keep having with later versions of xulrunner (aka, can't even get the profile manager to show) I recommend we stick with the older variant.
#15:46:46bshumdbs: It didn't like that, saying that libpq-dev package is broken.
#15:46:55DyrconaQt/WebKit here we come! :p
#15:47:24jeffdbs: got it :-)
#15:47:35eeevilmarc editor fiximicated ... wheee!
#15:47:38dbsbshum: hmm, maybe you could try out jeff's version of Makefile.install?
#15:47:44jeffeeevil++
#15:47:51dbseeevil++ # two lines of glory!
#15:48:29dbslines != amount of head scratching
#15:48:43phasefxtsbere: let's make sure we keep a copy somewhere handy
#15:49:09dbsbshum: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/jeff/lp801624_fix_bash_test if you have the chance
#15:49:10tsberephasefx: As mentioned, the re-numbered variant is probably fine. They don't look to be pulling it anytime soon.
#15:49:13shopkins has quit IRC
#15:49:24dbslet's torrent it
#15:49:39phasefxlet the staff client distribute itself
#15:49:56kmlussier has quit IRC
#15:50:26eeevildbs: yeah ... not sure how it ever worked, TBH ... but it did
#15:53:17tsberephasefx: Basically, "bumping" the version to 3.6.22 works fine. But going to anything after the 3.6 run is causing me headaches.
#15:53:56tsbereWe don't even have to change application.ini
#15:54:29phasefxtsbere: you were just trying for the whitelist thing, right?
#15:55:13tsbereI have tried several times for various reasons, and have a local branch with various changes I have gone through to try and make sure things might work.
#15:55:13dbsgive my PyQt or give me death
#15:55:15bshumdbs: Tested the makefile.install and tried "install_pgsql_client_debs_90" and it installed postgresql-client-9.0 and upgraded my libpq-dev and libpq5 (to 9.1.0 versions)
#15:55:43dbsbshum: okay - and it didn't blow away your postgresql 8.4 server?
#15:55:53bshumdbs: It does not appear to be gone.
#15:56:02tsberephasefx: End result, I have yet to attempt to code the whitelist thing, but I have a pile of local changes that may make other things support xulrunner 6+ that we would have issues with otherwise.........but I can't test them because I can't get the later versions to *start* properly, let alone run the code.
#15:56:20bshumdbs: Or wait
#15:56:25bshumdbs: I can't connect to it.
#15:56:57eeevilbshum: might have been moved to another port
#15:57:09bshumeeevil: Good point, checking on that now...
#15:57:09tsbereTry 5433
#15:57:11tsbere;)
#15:57:15phasefxtsbere: being stuck on 1.9/3.6 is where I expected us :( did you try the extension route with Firefox?
#15:57:31dbsweird. normally debian would put a new server at a new port
#15:57:42tsberephasefx: I am considering a patch to rip all the extension stuff *out* at this point. <_< Never worked well enough for me.
#15:57:45dbsbshum was just upgrading the client
#15:58:17bshumWacky.... I thought this server had 8.4 installed on it and I see data files for it, but it's like it's not here...
#15:58:32bshumBad test
#15:58:35phasefxtsbere: I could agree with that; we really don't want to push folks to stick with Firefox 3.6 :)
#16:00:30Meliss has quit IRC
#16:05:56tspindler has quit IRC
#16:07:29sal_Minor and unrelated question...is my change to SIP/Patron.pm:charge_ok to report denial of privileges in the SIP patron status field a bug fix (for a bug I should report) or a patch?
#16:07:57sal_(And was that a runon sentence?)
#16:09:05Dyrconasal_: I don't think I know enough about the context of the question to be able to answer.
#16:09:56akilsdonk has joined #evergreen
#16:10:07DyrconaMy suggestion would be create a launchpad bug and attach code.
#16:10:15jeffsal_: open a bug in launchpad with the details and either include your patch or a link to a working branch/etc.
#16:10:25jeffwhat Dyrcona said :)
#16:11:02DyrconaI think we should have a developer/community meeting devoted to discussing the future of the client.
#16:11:10sal_thanks. I shall.
#16:11:51bjwebb has quit IRC
#16:12:30bshumdbs: Alright, tested again with another lucid server that actually had PG 8.4 installed and running on it.
#16:12:30akilsdonk has quit IRC
#16:12:38dbs awaits anxiously
#16:12:42bshumThings connected just fine, and the database is still there.
#16:12:53dbsAWESOME
#16:13:22dbs will rip out the current hackery and credit jeff and bshum for helping discover that much pain is gone
#16:13:29akilsdonk has joined #evergreen
#16:13:53bshumWait, just to check on one last thing
#16:14:02bshumHow do you verify that you're using the right psql version?
#16:14:05dbs waits
#16:14:20dbspsql --version
#16:14:35bshumHmm, that came back with 8.4.8
#16:14:42collum has quit IRC
#16:14:45dbsand "show server_version" once you're connected
#16:14:45DyrconaThat matters less than the libs and server version, though.
#16:14:58bshumThough postgresql-client-9.0 definitely installed along with upgraded versions of libpq-dev and libpq5
#16:15:20Dyrconathe 8.4 client works well with 9.0+ servers. it just doesn't have any new features of the 9.0+ clients.
#16:15:21dbswell, given that bshum installed postgresql-client-9.0 it is a bit surprising :)
#16:15:27bshumI guess the DB itself not being blown away is good though.
#16:15:35dbsthat's the primary concern
#16:15:36Dyrconadbs: that happened to me until i uninstalled the 8.4 client.
#16:15:45dbsprobably /etc/alternatives or the like
#16:15:48bshumLet me try uninstalling the pg 8.4 client then
#16:15:50Dyrconayes
#16:15:53jeffokay, i'm getting breakage here.
#16:15:57jeffinstalled debian squeeze.
#16:16:16jeffinstalled opensrf 2.0.1 pre-reqs with debian-squeeze target in Makefile.install
#16:16:39jeffadd squeeze-backports line in sources.list, apt-get update, then:
#16:16:47bshumOh, oops, definitely not doing that. It wants to kill the 8.4 server along with the client when I do that.
#16:17:06Dyrconabshum: what are you running?
#16:17:12Dyrconathe command I mean.
#16:17:38bshumAh, maybe that's what I'm doing wrong... apt-get remove postgresql-client-8.4
#16:18:06bshumpostgresql-8.4 depends on the 8.4 client it seems.
#16:18:38Dyrconapostgresql-8.4 is a metapackage, not the server itself.
#16:18:41jeffrunning aptitude -t squeeze-backports -yq install libpq5 libpq-dev postgresql-client-9.0, i get an unmet dependencies error from aptitude- postgresql-client-9.0: Depends: libpq5 (>= 9.0~) but 8.4.8-0squeeze2 is installed.
#16:18:42tsberephasefx: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/tsbere/no_ff_extension
#16:18:46bshumDyrcona: Ahh, I see.
#16:18:49Dyrconait's a shortcut to install everything.
#16:18:49jeffso, we seem to still have the original issue requiring the workaround.
#16:19:04jeffnot sure why it worked once for me last night
#16:19:09dbs wonders if we're on different mirrors
#16:19:34jeffor i did something unusual last night that i promptly forgot
#16:19:46dbsjeff: slowoutofdate.debian.org is not reliable, fwiw
#16:20:05jeffso, here's an alternate workaround:
#16:20:48jeffdrop the -9.0 from postgresql-client package name. then it upgrades just fine... but when squeeze-backports gets 9.1, we may have issues :-)
#16:21:33jeffi'll bet i did that last night at some point.
#16:21:53bshumEww, doing that on Lucid definitely gets me the 9.1 client.
#16:22:43jeff.bash_history confirms, i manually installed postgresql-client from backports before running the Evergreen pre-reqs.
#16:22:44dbs9.1 isn't an issue, thanks to tsbere
#16:22:48bshumpitti's ppa has the 9.1 stuff in it, so I have to be more explicit about which versions I want to have.
#16:23:24dbsgiven that 9.1 was released yesterday-ish, I'm sure it's safe
#16:23:42dbsFamous Last Words(TM)
#16:24:13bshumHeh, dbs++
#16:24:24bshumAnd tsbere++ too, 9.1 support
#16:24:27jeffso, the issue requiring the workaround is still an issue. we have an updated workaround (dbs + my changes), or we can install postgresql-client instead of postgresql-client-9.0 -- i can't weigh the pros/cons right now, just enumerate two possible options. :-)
#16:25:05dbsgiven that postgresql 9.0 support is going to be pulled from the backports / ppa in a few months, apparently?
#16:25:14dbs would lean towards 9.1
#16:25:25dbsbut /me is not upgrading to 2.1 anytime soon
#16:26:53akilsdonk has quit IRC
#16:26:55bshumAs long as we know PG 9.1 is the intended target for an EG 2.1, then that seems fine to me. Good to know which direction to plan in.
#16:27:09bshumFor the sites already on PG 9.0 well... hmm. We have to upgrade eventually right?
#16:27:19akilsdonk has joined #evergreen
#16:27:39bshumDirection to plan in / for newbies to install with.
#16:28:05dbswell, there we're in your boat; on 9.0 with 2.0. so you can take some comfort :)
#16:28:37bshumdbs: Actually, our production is still 8.4 with 2.0. I can go anywhere I want! :D
#16:29:41bshumHas the 9.1 support been backported to 2.1 already?
#16:29:51bshumI might try to install it later tonight to see how it plays.
#16:31:20bshumAh yes, there it is.
#16:33:54jamesrfdid i catch it right that 2.1 is now going to require 9.1?
#16:34:14tsbereRequire? Probably not. Support? Probably.
#16:34:56sal_Rumor has it that 9.0 is going away altogether (having never actually been included in any official distributions, it may never be.)
#16:35:06dbsjamesrf: we're considering making a default Makefile.install install the 9.1 client
#16:35:21dbsbut the server would still be under your control
#16:35:45jamesrfhm yeah we're just sort of starting to look at upgrading our 8.4 server to 9.0 in anticipation of 2.1 but maybe 9.1 would be better?
#16:35:45dbs holds up his Fedora 15 and shakes it in sal_'s face
#16:36:37jeff wishes for a launchpad "bugs i've recently commented on"
#16:36:50dbs thinks this would make a fine topic for the "2.1 blockers" thread: "PostgreSQL 9.0 seems to be hard to install on Debian Squeeze / Ubuntu Lucid and 9.1 seems to be the direction backports are going in"
#16:37:24jeffadvanced search has it. launchpad++
#16:37:25dbsnot quite a blocker, but we need to have a consensus on what we want to try to support as a standard
#16:37:28sal_dbs: was quoting Martin Pitt, before the big stink :-)
#16:37:40dbsah
#16:38:14jamesrfhmm yeah it would be nice to get through a major eg version without having to upgrade postgres again or at least to know what to expect
#16:39:42Dyrconatrouble is we're an open source project in an open source ecosystem with "customers" who are used to a siloed experience.
#16:41:23jeffyeah, forget that "postgresql-client" fixes it -- it installed / stayed with 8.4.
#16:42:50dbs has no idea what state things are in now
#16:42:52dbs goes home
#16:42:55dbs has quit IRC
#16:44:13jeffstill wondering what in the world i did last night that it worked :P
#16:45:14moodaepo thinks 8.x to 9.0 will be the same as 8.x to 9.0 and 9.0 to 9.1 shouldn't be a pain
#16:46:38jamesrfanyone tested eg 2.0 + pg 9.1?
#16:47:55moodaepojamesrf: That is my next test...once I finish setting up our demo tt_opac server
#16:48:40jeff re-tests
#16:50:21elene has joined #evergreen
#16:53:00elene has left #evergreen
#16:53:34elene has joined #evergreen
#16:54:24elenehi everyone :)
#16:54:43jeffgreetings, elene!
#16:55:24elenecould someone please help me cope with one issue about record's OPAC visibility
#16:56:50jeffask away!
#16:56:58jeff(no need to ask to ask)
#16:57:21elenethanks :) I have this strange problem on 1.6.0.1: when I create a record from staff client and attach a copy
#16:57:35eleneeverything seems to work, but the record does not show up on OPAC
#16:57:59jeffBy default some copy statuses are not opac visible. If the copy's status is In Progress, it won't show in public searches.
#16:58:05eleneand later even from Staff Client, I can only retrieve the record by its ID, not by searching by keywords
#16:58:25elenethanks. I set copy status as 'available'
#16:58:42eleneand the record is not even visible from staff client
#16:58:51eleneunless I search for it by its record ID
#16:58:55jeffer, "In Process" is what I meant. no big difference there. :-)
#16:59:42elenei see
#17:01:56jeffIt sounds like the record itself might not be properly indexed/ingested.
#17:02:14elenei see. could you please remind me the reingest command?
#17:02:33jeffediting the marc record and re-saving it may just do the trick.
#17:03:20tlilleberg has quit IRC
#17:04:19eleneI see. I just tried it, but strangely, I can no longer retrieve the record, even by its record ID. it seems to be gone :(
#17:05:49eleneis there such thing as 'reingest' in 1.6.0.1? or a 'repair database' script / command
#17:08:11moodaepoelene: I think jeff's sugestion about editing marc record and saving works only in 2.0 and above, 1.6.0.1 seems so long ago I forget how it was done.
#17:08:54eleneI see. Thanks, moodaepo. Would you happen to have any other suggestions?
#17:09:03moodaepoelene: I think there is a script one sec
#17:10:04bshumIf you can't even retrieve it by record ID that seems unusual.
#17:10:20bshumEven if it were a deleted bib, it would come up by its id.
#17:14:19mmorgan has left #evergreen
#17:21:03moodaepoelene: The script I remembered is used when we are loading records on the server using scripts not via the client so it won't be of much use to you. In any case it's mentioned here http://open-ils.org/dokuwiki/doku.php?id=evergreen-admin:importing:bibrecords moe specifically look under "Example: Importing the Project Gutenberg records" for usage example.
#17:22:20elenemoodaepo: Thank you. I recently imported holdings using staging table, so I may have missed the command that does 'reingest'
#17:28:22Dyrcona has quit IRC
#17:59:22jenny has left #evergreen
#18:06:55elene has quit IRC
#18:26:14sal_ has quit IRC
#18:43:43yboston has quit IRC
#18:51:02elene has joined #evergreen
#18:55:02elene has quit IRC
#18:56:50elene has joined #evergreen
#19:03:13akilsdonk has quit IRC
#19:05:17elenehi again. i have the same problem on 1.6.0.1: I create record from staff client, i attach copies. set status to 'availabe' but the record does not show up on OPAC. Also, it is not searchable from staff client, unless I retrieve it by record ID
#19:05:53eleneI have tried editing and re-saving the record from stall client, but no luck
#19:06:48eleneI checked record_entry, call number and copy tables and the record is there
#19:07:00elenealong with holdings info
#19:07:50shadowspar is now known as latefordinner
#19:09:45latefordinner is now known as shadowspar
#19:15:11jeffokay, on the "that didn't fix it" -- i was using -t debian-backports -- not -t squeeze-backports :-)
#19:15:22jeffi'll update the bug once i've confirmed.
#19:29:14moodaepoelene: I don't suppose the web catalog is available publicly?
#19:29:43elenemoodaepo: yes, it's library.ac.ge
#19:31:44elene has quit IRC
#19:34:07elene has joined #evergreen
#19:36:31elene.
#19:43:07elenethe title of the test record is 'kiev test 2'
#19:48:28bjwebb has joined #evergreen
#19:52:49eleneCould my manually adding the holding info have somehow damaged the ingest function?
#19:53:58eleneI did not do very clean import of holdings info. All I did was manually adding info in asset - call_numbers table and then relevant data in asset - copy table.
#19:54:47eleneStaging table somehow did not work, so as I used manual way, I may have missed some other required tables to update
#19:55:07jeffit is possible that you have asset.call_number or asset.copy entries that do not have proper circ_lib / owning_lib or other info. have you tried adding volumes and copies from a staff client?
#19:56:05eleneyes, and they add without problems, though the record is still not findable and not visible unless retrieved by id
#19:56:53elenelast entry befor ebatch import in asset.call_number was "22571", so I started adding new call numbers from "52424"
#19:57:27eleneso now I have a gap in asset.call_number like this: "22569", "22570", "22571", "52424", "52425", "52426"
#19:57:50eleneCould that have created any issues?
#20:00:51tsbere wonders if triggers are disabled
#20:17:11akilsdonk has joined #evergreen
#20:23:40akilsdonk has quit IRC
#20:41:21bjwebb has quit IRC
#20:48:59dbs_n1 has joined #evergreen
#20:49:41dbs_n1elene: you need to run the metarecord mapping sql
#20:50:52dbs_n1tsbere: elene is on 1.6.0.1 when ingest was mostly outside the database
#20:51:08tsberedbs_n1: Good to know.
#20:51:18tsbere has minimal clue how most things work in 1.6.anything
#20:53:43dbs_n1http://evergreen-ils.org/dokuwiki/doku.php?id=scratchpad:random_magic_spells#how_to_generate_metarecords_for_a_newly_loaded_bib_batch
#20:54:22dbs_n1tsbere: it was perl to spidermonkey and back to perl
#20:54:34dbs_n1good fun
#20:55:31tsbereHeh
#20:56:36tsberedbs_n1: Any thoughts on "circ.transit.suppress_hold" and "circ.transit.suppress_non_hold" as OU setting names for suppressing hold and non-hold transits?
#20:57:30dbs_n1is non-hold really all?
#20:59:16tsbereI aimed for "if you want to stop all transits you need to set both"
#20:59:16dbs_n1 has quit IRC
#21:55:43jeffhrm. i still thought that saving a record would generate the metabib... dbs++ for the forgotten link to generate them all, though :-)
#22:02:59tsbereAnyone have thoughts? http://git.mvlcstaff.org/?p=tsbere/ILS.git;a=commit;h=4d861d7673d78eb8cc441698be8b4b0954c909aa
#22:14:59jeffi reached the fourth paragraph until i understood what the intended use case was... :-)
#22:15:49jeffthe same-setting-id bit is clever, and eliminates potential complexity from "don't transit to this array of OUs" kind of approaches.
#22:15:56tsbereyea
#22:16:16tsbere thought that was the easiest way to handle it
#22:16:56jeffi wonder if it's "too clever", but that's what good documentation and clear settings descriptions are for, right?
#22:17:38tsbereI think it is easier than trying to keep both ends of a "don't transit to these ous" setting in sync
#22:17:52jeffphasefx and i talked of such library-within-a-library setups once, but went with copy stat cats instead, not least of which due to transits.
#22:18:58tsbereThis has the benefit of "you can suppress reshelving transits but still keep multiple hold shelves going" or "you can send things to the right part of the library but share a common hold shelf"
#22:19:52jeffyeah. next up would be a "present these children as one library in the public opac" feature, i suppose. :-)
#22:20:28jeffwhat led you to want to use multiple OUs for a library?
#22:20:39jeffdepartmental splitting of holds pull list / etc?
#22:20:55tsbereWe have one library with a children's department as a branch.
#22:20:56jeffwe've considered shelving location hierarchy for that sort of thing.
#22:21:00tsbereBeyond that, though, this isn't for us
#22:21:12tsbere wrote this in response to an internal RFP
#22:21:35tsbereOne of the other MassLNC libraries is looking to have departments under the branch or something like that
#22:21:37jeffwhat are the reasons leading up to that department being a branch / reasons for it remaining a distinct org unit?
#22:21:45tsbereor MassLNC consortia or whatever ;)
#22:22:03tsbereI *think* they want to be able to have departmental circ rules and such
#22:22:07tsberenot sure.
#22:22:17jeffhrm
#22:22:25jeffcurious, that's all.
#22:23:01jeffi've had reasonable success with "why are you asking me for this -- there may be a better way" today. :-)
#22:23:22tsbereI don't attend enough meetings to have asked that.
#22:23:23tsbere;)
#22:24:45tsbereHmm
#22:24:57tsbereI seem to recall, now that I think about it, something about search scoping too.
#22:25:02tsbereAs for the "why"
#22:26:58jeffsomething that shelving location hierarchy could do also, difference being it doesn't exist yet, and your transit supression/elimination org unit settings do.
#22:27:57jeffalso, shelving location hierarchy could require creating of more shelving locations than currently are needed in a system, and circ_lib/owning_lib just needs an org unit to point at.
#22:29:01tsbereI don't know the full set of reasons they want it. I just know they want a feature to make transits not happen. And hey, I wrote such a feature.
#22:29:11jeff nods
#22:29:19tsbereAnd one (single, solitary) library in our group might find it useful too
#22:57:57enhancin has joined #evergreen
#23:00:34enhancinI'm having an issue with the public account and ejabberd. I get errors in the srfsh.log that ejabberd as nothing to send a message to
#23:48:18enhancin has quit IRC
< Monday, September 12th, 2011Raw Log FileWednesday, September 14th, 2011 >