2011-02-07T00:08:46 *** eby_ has joined #evergreen 2011-02-07T00:44:45 *** mfaizali has left #evergreen 2011-02-07T07:13:42 *** Dmagick has quit IRC 2011-02-07T08:05:00 *** sfortin has joined #evergreen 2011-02-07T08:16:44 *** rickd_ has joined #evergreen 2011-02-07T08:32:08 *** AaronZ-PLS has joined #evergreen 2011-02-07T08:32:57 *** rickd_ has quit IRC 2011-02-07T08:36:24 *** gdunbar has joined #evergreen 2011-02-07T08:45:27 *** dbwells has joined #evergreen 2011-02-07T08:50:25 *** rickd_ has joined #evergreen 2011-02-07T08:52:16 brian_f: i'm not seeing a 2.0.1 client on your google docs 2011-02-07T08:53:49 *** 92AACCK5J has joined #evergreen 2011-02-07T08:53:52 *** alxp has joined #evergreen 2011-02-07T08:56:57 *** mjg_ has joined #evergreen 2011-02-07T09:03:40 *** bshum has joined #evergreen 2011-02-07T09:03:46 *** bshum has joined #evergreen 2011-02-07T09:05:16 *** bshum has joined #evergreen 2011-02-07T09:10:45 *** Meliss has joined #evergreen 2011-02-07T09:14:50 *** kcollier has joined #evergreen 2011-02-07T09:30:16 *** 92AACCK5J is now known as Dmagick 2011-02-07T09:34:14 *** Dyrcona has joined #evergreen 2011-02-07T09:42:36 *** dbs has joined #evergreen 2011-02-07T09:42:36 *** dbs has joined #evergreen 2011-02-07T09:46:57 *** yboston has joined #evergreen 2011-02-07T09:51:42 *** phasefx has joined #evergreen 2011-02-07T09:55:05 *** jenny has joined #evergreen 2011-02-07T09:55:28 *** atz has joined #evergreen 2011-02-07T09:55:41 *** rsinger_ has joined #evergreen 2011-02-07T09:56:29 *** rsinger has quit IRC 2011-02-07T09:56:29 *** rsinger_ is now known as rsinger 2011-02-07T10:05:40 where are we at with http://evergreen-ils.org/dokuwiki/doku.php?id=dev:evergreen:release_checklist for 2.0.1? I've created a 2.0.1 VM but haven't seen any patches for downloads.php; I guess I can go ahead and update it for 2.0.1 2011-02-07T10:06:44 dbs: I think we have the staff client, wiki needs updating (I can do that right now) 2011-02-07T10:07:08 yeah, saw brian_f's update on the staff client 2011-02-07T10:08:21 bshum: while you're in the wiki, Debian Squeeze (6.0.0) is officially out now - download link is http://www.debian.org/distrib/ 2011-02-07T10:08:36 dbs: Yeah I was just downloading a new copy of it to see how it works. 2011-02-07T10:08:52 I was reading a rumor that something weird happened with Squeeze and the packaged postgres 2011-02-07T10:08:57 Not sure if it applies to us 2011-02-07T10:09:15 Weirder than the normal Debian / PostgreSQL packagin? 2011-02-07T10:09:35 http://petereisentraut.blogspot.com/2011/02/squeeze-postgresql-broken.html 2011-02-07T10:09:38 It was just a blog post 2011-02-07T10:09:45 Haven't gotten to digging deeper yet 2011-02-07T10:09:55 *** kmlussier has joined #evergreen 2011-02-07T10:10:48 dbs: I'll add that link to the official Squeeze though 2011-02-07T10:12:56 *** dneimeier has quit IRC 2011-02-07T10:14:20 dbs: Wiki updated 2011-02-07T10:15:02 bshum++ 2011-02-07T10:29:39 Procedurally, if we do a checkout of the evergreen-ils.org folder off ILS-contrib, modify the downloads.php and create a patch 2011-02-07T10:29:45 That's what you're looking for, right dbs? 2011-02-07T10:29:56 bshum: yeah, but I'm basically done now 2011-02-07T10:30:02 For future reference 2011-02-07T10:30:03 :) 2011-02-07T10:30:05 Thanks 2011-02-07T10:31:03 bshum: svn co svn://svn.open-ils.org/ILS-Contrib/evergreen-ils.org; # modify downloads.php to your liking ; svn diff > downloads.patch ; send patch 2011-02-07T10:31:49 dbs: Yep, just tried that (I'm not really familiar with svn so it took me a couple pokes) 2011-02-07T10:32:05 Good to know though. 2011-02-07T10:34:21 dbs: wanted to get your opinion on something.. 2011-02-07T10:34:58 i integrated locale::maketext into TT in a test branch. it supports loading translations from .po/.mo files 2011-02-07T10:35:09 sounds good so far 2011-02-07T10:35:18 and there's an xgettext.pl plugin that will extract strings from .tt2 files for us 2011-02-07T10:35:32 here's the commit : http://git.esilibrary.com/?p=evergreen-equinox.git;a=commitdiff;h=977c8d2978e962ea1a010818d251ca37cb818d8d;hp=f32a110922f639e4304d9cdb63bf26e50eb0af97 2011-02-07T10:35:52 anyway, i'm just curious if you have any opinion on the approach 2011-02-07T10:36:12 locale::maketext seems like the most common approach for TT translations 2011-02-07T10:37:55 there's some sample strings in the commit. syntax is basically [% l('I want [_1] apples', apple_count) %] 2011-02-07T10:39:41 *** dneimeier has joined #evergreen 2011-02-07T10:41:25 berick: cool! can you do the quant() thing for that kind of example? [% l('I want [quant, _1, apple, apples]', apple_count) %] 2011-02-07T10:41:25 arg ... all my svn checkouts are unhappy with the Great Perl Module Move of Ought-Eleven 2011-02-07T10:41:35 eeevil: see? svn sucks 2011-02-07T10:42:16 Hi all - I am simultaneously attacking my problem on this IRC channel and the listservs. I have posted my problems starting the Perl Module of OpenSRF (new install). I am getting an "unable to connect" error. I have searched the forums and have done all suggested troubleshooting (kill processes, delete pid files, restart manually, ensure passwords are correct) 2011-02-07T10:42:30 dbs: and git is incomprehensible :) 2011-02-07T10:42:35 I have followed the wiki for OpenSRF1.6.2 to the letter and verified several times. 2011-02-07T10:42:48 dneimeier: okay, so you've stopped using Bundle::OpenSRF? 2011-02-07T10:42:59 dbs: i can find out.. 2011-02-07T10:43:00 I did buld the dependencies in src/extras (as per the wiki) with no errors 2011-02-07T10:43:23 Sorry, yes, I have stopped using Bundle::OpenSRF 2011-02-07T10:43:59 eeevil: I found http://ebb.org/bkuhn/blog/2011/01/23/git-shared-repository-tutorial.html helped me learn enough to start submitting pull requests for buildbot 2011-02-07T10:45:25 dbs: I don't think git is really incomprehensible, I just don't like it's interface ... I was just using an equiv argument to "svn sucks!" ('cause I'm moody today ... apologies) 2011-02-07T10:45:57 dbs: however, I'll read through that git tut now 2011-02-07T10:46:30 eeevil: understandable, I agree with you that git's interface seems overly prickly for something that should have been smoothed down like the rocks in a river by now 2011-02-07T10:47:43 svn did piss me off massively though when I was trying to move piecemeal towards the Module::Build approach and discovered that it refused to revert "svn mv" for the directory change 2011-02-07T10:47:51 statements like this don't make me feel better... "everyone who uses git has a different perception of what the master branch should embody" ... :P 2011-02-07T10:48:21 * eeevil shuts it and clones berick's clone 2011-02-07T10:50:50 eeevil: that's more of a software development perspective than a particular VCS issue, I think. correspondingly, we could argue that nothing should be in our SVN trunk that hasn't already been fully developed and tested in an SVN feature branch, right? 2011-02-07T10:52:47 eeevil: let me know if I can be of assistance 2011-02-07T10:52:51 * dbs updates downloads.php on server, notices that staff client hasn't been uploaded there yet 2011-02-07T10:53:01 dbs: the way it reads in that tutorial, it sounds like "it's just a thing, do what you will with it" ... it's one of the core D vs not-D VCS issues for which I'm still trying to find the right medication to address in my head ;) 2011-02-07T10:53:47 eeevil: right, so for our purposes we could define "git master branch at git.evergreen-ils.org" as the equivalent of SVN trunk. I think. 2011-02-07T10:53:52 *** kmlussier has quit IRC 2011-02-07T10:54:33 dbs: re: quant, it's supposed to work. xgettext works, but the l::m::lexicon::gettext isn't creating the correct lexicon even though the docs say it should. poking... 2011-02-07T10:54:34 crazy google docs folders 2011-02-07T10:54:37 dbs: yes, I have stopped using Bundle::OpenSRF 2011-02-07T10:54:51 *** afterl has joined #evergreen 2011-02-07T10:55:10 dbs: understood ... I wish there was a concise project-specific document about "how we would use git for Evergreen and OpenSRF" to pin down what /we'd/ do as opposed to what's possible 2011-02-07T10:55:57 eeevil: hey, that sounds like what I asked for! from the more git-experienced folks :) 2011-02-07T10:55:58 * eeevil thinks this is akin to my Merican revulsion to eating live grubs ... I understand that they are full of good protein, perhaps the perfect food, but ... ew 2011-02-07T10:56:10 'merican 2011-02-07T10:56:16 heh 2011-02-07T10:56:26 we have a chicken and egg problem, it would seem 2011-02-07T10:56:58 no one wants to put the effort into a tutorial until we decide that's the route we're taking, but no one wants to pick the route w/o a tutorial 2011-02-07T10:57:28 dneimeier: can you: 1) shut down all opensrf services; 2) remove all of your opensrf logs (rm -f /openils/var/log/*log); 3) start up your opensrf instance 4) post your logs somewhere? 2011-02-07T10:58:16 dbs: doing that right now. Will post to the large paste site in a minute 2011-02-07T10:58:33 dneimeier: it would also be useful to know what commands you're using to start/stop opensrf, as well as what your /openils/conf/opensrf.xml and /openils/conf/opensrf_core.xml files contain, and whatever contents /var/log/ejabberd contains as well 2011-02-07T10:58:57 dneimeier: the paste site probably won't handle the logs, would work better if you could upload them to something like Google Docs 2011-02-07T10:59:44 perhaps as a starting point someone with git-ocity could look at the efficacy of http://wiki.postgresql.org/wiki/Working_with_Git ... Postgres just changed from CVS to git (much bigger jump, IMO) so what they do might be informative 2011-02-07T10:59:53 *** rsinger has quit IRC 2011-02-07T10:59:53 dbs: no problems. Using the start/stop command in the wiki and manually starting/stopping each module 2011-02-07T11:00:34 dneimeier: with or without the "-l" flag? (where "-l" means "dash ell", not "dash one") 2011-02-07T11:00:51 eeevil: a starting point such as http://wiki.koha-community.org/wiki/Version_Control_Using_Git perhaps? 2011-02-07T11:01:12 i always liked that doc 2011-02-07T11:01:24 the main difference is that I'd expect that we'd be doing more merging of branches from the start than was the case with Koha 2011-02-07T11:01:25 gmcharlt: I'll read that too 2011-02-07T11:02:47 dbs: witht he -l flag - I have set up witht he localhost configuration. 2011-02-07T11:05:10 if nobody else has the desire/resources, I expect to be able to establish continually updating a github repo from svn... i.e. a more official git repo. 2011-02-07T11:05:37 if that would be useful to other ppl 2011-02-07T11:06:39 atz: please don't go labeling anything official until it's really decided. which it's not, yet 2011-02-07T11:07:19 this doesn't imply moving to git. it just makes using it easier, and knowing which repo to clone easier. 2011-02-07T11:07:54 sitka already publishes a git-svn clone for trunk on github, updated every four hours 2011-02-07T11:08:05 ok, cool... that should be good enough 2011-02-07T11:08:47 atz: understood, but if/when we move from svn to something else, would that not break whatever github "more official" repo? IOW, wouldn't having that repo's origin go away cause problems? 2011-02-07T11:09:26 s/atz/atz, dbs, sitka/ I guess 2011-02-07T11:09:33 not if it were git 2011-02-07T11:09:59 um ... it's svn 2011-02-07T11:10:03 and even bzr might work (via git-bzr) 2011-02-07T11:10:11 eeevil: I really don't know. I thought that git-svn clone to git-svn clone got confused relatively easily 2011-02-07T11:10:38 <-- I claim no real knowledge! 2011-02-07T11:10:41 eeevil: it being the "something else", i mean 2011-02-07T11:11:15 sorry ... I'm not saying this well ... the sitka git-svn clone is tracking an svn repo ... what happens when that svn repo goes away (becomes non-authoritative) 2011-02-07T11:11:59 eeevil: I think they're just cloning svn until it goes away, at which point they'll start cloning the git repo (or bzr repo, if we moved that direction, as atz suggests) 2011-02-07T11:12:01 what happens to the sitka "mildly more official because it's on github and auto-updating" clone, I mean 2011-02-07T11:12:04 they can either start tracking a bzr repo (and still pushing to github as git changes), or start tracking a git repo (and pushing the changes even more easily) 2011-02-07T11:12:35 it's just for their convenience, rather than every individual developer having to maintain their own git-svn clone. because people like to commit locally and branch offline and such 2011-02-07T11:12:37 right, but anybody downstream of the sitka clone is going to be depending on that clone's hashes, etc 2011-02-07T11:12:55 or if the official repo is itself a github repo, they can ask github support to make their repo a "fork" off the official one 2011-02-07T11:12:55 *** Meliss has quit IRC 2011-02-07T11:13:27 and then the need to autoupdate goes away 2011-02-07T11:13:39 sure ... my point is we should not call something "the git clone, for now" if it's going to break soon -- because we're intending to move and that (might? could? will?) break that 2011-02-07T11:13:44 *** rsinger has joined #evergreen 2011-02-07T11:13:47 eeevil: it's possible to detach a git-svn repo from svn 2011-02-07T11:13:57 gmcharlt: sure 2011-02-07T11:14:07 eeevil: sure, it makes sense to mention it 2011-02-07T11:14:26 eeevil: i think that's understood 2011-02-07T11:14:28 gmcharlt: but can you re-attach it to some other upstream repo? 2011-02-07T11:14:51 dbs: https://docs.google.com/document/d/18dZYTh9Md6-abO1zxYVifbwB7E7u7kbvpWmy2pTGdtA/edit?hl=en&authkey=CPnevskE 2011-02-07T11:14:55 https://github.com/sitka/evergreen "Unofficial git clone of the official open-ils SVN repository, updated every 4 hours. Contact us if you'd like another branch tracked" 2011-02-07T11:15:23 *** youdonotexist has joined #evergreen 2011-02-07T11:15:45 dbs: the document is editable. Double-checking to make sure I've given you everything... 2011-02-07T11:15:57 *** Meliss has joined #evergreen 2011-02-07T11:16:23 dneimeier: just a quick thought, try using just alpha-numerics for the opensrf/router ejabberd passwords. maybe the Perl code doesn't escape special chars like "$" properly? 2011-02-07T11:16:26 dbs: right, I'm not arguing against having that ... not in the least! my concern is a march towards official-dom for any one source, at least until after the in-person brawl at egc2011 (which is not what you are suggesting, I know!) 2011-02-07T11:17:10 dbs: OH MAN! Didn't even consider that.. Trying now. 2011-02-07T11:17:11 oh, i thought the EG con already happened. when is it? 2011-02-07T11:17:43 eeevil: as far as a source is concerned, I'd rather we have a git/bzr/whatever.evergreen-ils.org anyway 2011-02-07T11:17:56 lot easier to have fine-grained access control to push to branches 2011-02-07T11:17:58 atz: http://pines.georgialibraries.org/evergreen2011/ (really?) 2011-02-07T11:18:16 gmcharlt: right, indeed, me too 2011-02-07T11:18:18 as well as a central point for hosting other EG and EG-related trees 2011-02-07T11:18:58 i haven't been following it closely.... just had the vague impression it preceded code4lib 2011-02-07T11:19:21 or did it get rescheduled/relocated? 2011-02-07T11:20:00 * dbs thirds dvcs.evergreen-ils.org for the "official" source 2011-02-07T11:20:03 it got relocated 2011-02-07T11:20:10 eeevil: did some checking, commit hashes in the sitka repo are same as a local git-svn clone I'm using 2011-02-07T11:20:51 gmcharlt: that's encouraging ... so, theoritically, one could manually re-point a branch between the two? 2011-02-07T11:21:02 eeevil: quite easily, in fact 2011-02-07T11:21:11 assuming no crazy rebasing etc 2011-02-07T11:21:24 or timeline rewriting or whatever 2011-02-07T11:21:46 right, and whatever variants one has in a Git workflow, there's one that always applies 2011-02-07T11:22:02 Thou Shalt Not Rebase In a (important) Public Branch 2011-02-07T11:24:02 dbs: GOOD CATCH!! I should have known... 2011-02-07T11:24:34 dneimeier: really? yikes. Please file a bug at http://bugs.launchpad.net/opensrf - that's /not/ good! 2011-02-07T11:25:04 time to get out the quotemeta brand duct tape 2011-02-07T11:25:29 dneimeier: were any of the characters <, >, or & - i.e., significant in XML? 2011-02-07T11:28:28 gmcharlt: 0P3N$RF 2011-02-07T11:28:31 (so, no) 2011-02-07T11:29:52 gmcharlt: I had a $ that was not escaped. Maybe a password validation looking for characters that need to be escaped.? When I get the system operational, I will test this. It may work simply be escaping special character... 2011-02-07T11:31:48 gmcharlt: by "using more merges" than Koha did, do you mean not sending everything as a patch to an evergreen-patches list? 2011-02-07T11:32:42 dbs: potentially, yes, at least insofar as we're likely to get more pull requests from the get-go 2011-02-07T11:32:59 but instead posting "please [review|test|pull] git.coffeecode.net/evergreen/some/branch"? 2011-02-07T11:33:25 to say nothing of potential for major committer A asking for pull, review, and signoff before merging a set of changes into master 2011-02-07T11:33:49 and major committers B, C, etc. doing exactly that 2011-02-07T11:35:36 *** bshum has quit IRC 2011-02-07T11:40:15 dbs: bug posted 2011-02-07T11:42:57 dneimeier++ 2011-02-07T11:43:39 * dbs poking at OpenSRF::Utils::SettingsParser::XML2perl 2011-02-07T11:48:09 dneimeier: just to be sure, it wasn't the shell mangling the passwords when you used ejabberdctl? 2011-02-07T11:48:37 * dbs confirms that XML2perl is passing the $ back just fine 2011-02-07T11:49:57 *** jamesrf has joined #evergreen 2011-02-07T11:50:13 phasefx: I was wondering the same when I typed that password in at the shell 2011-02-07T11:50:18 * tsbere wonders how many clones of the svn exist in gitland, given that he set a local one up at mvlc last week 2011-02-07T11:50:45 * phasefx has a local git-svn clone of trunk 2011-02-07T11:50:58 tsbere: lots, that was one of my points in my email about biting the bullet and moving to a DVCS for real instead of having umpteen *-svn clones 2011-02-07T11:51:12 I made our clone public too, and it clones all the branches automatically. 2011-02-07T11:52:10 * tsbere mainly wanted a "we don't have to go to the net" mirror, though 2011-02-07T11:52:12 * phasefx was using bzr-svn for a while 2011-02-07T11:55:19 *** dpearsa has joined #evergreen 2011-02-07T11:56:39 back to my "filter by profile" staff client enhancement from last week, i'm getting closer on the UI side of it, thanks to some phasefx but somehow I've broken search_form_overlay.xul and can't seem to track down what I've done to break it 2011-02-07T11:56:50 http://paste.lisp.org/display/119438 has the error, along with the new search_form_overlay.xul 2011-02-07T11:57:16 my additions run from line 158 thru line 181 2011-02-07T11:57:21 BTW, I should point out that MVLC's git clone is basically already split off of SVN, at least the public one. A second clone is the one that actually knows SVN and then pushes whatever SVN handed over to the public one, but without the direct connection to SVN. 2011-02-07T11:57:33 phasefx, dneimeier: cranking ejabberd logs up to "debug" says - phasefx was right 2011-02-07T11:57:34 or... actually, looks like an ejabberd limitation 2011-02-07T11:57:35 even if I single-quote 'pri$vosrf' to ejabberdctl, only 'pri' gets passed along as the password to ejabberd - maybe an ejabberdctl bug 2011-02-07T11:57:35 and then some additinos to the