Time |
Nick |
Message |
02:42 |
|
StomproJ joined #evergreen |
04:51 |
pinesol_green |
Incoming from qatests: Test Failure - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html> |
06:42 |
|
mceraso joined #evergreen |
06:47 |
|
bshum joined #evergreen |
07:08 |
|
phasefx joined #evergreen |
07:08 |
|
eeevil joined #evergreen |
07:08 |
|
Callender joined #evergreen |
07:30 |
|
sarabee joined #evergreen |
07:57 |
|
rjackson-isl joined #evergreen |
08:00 |
|
collum joined #evergreen |
08:08 |
|
mtate joined #evergreen |
08:09 |
csharp |
@tea |
08:09 |
* pinesol_green |
brews and pours a pot of Home, and sends it sliding down the bar to csharp (http://ratetea.com/) |
08:11 |
|
graced joined #evergreen |
08:11 |
|
wsmoak joined #evergreen |
08:30 |
|
Stompro joined #evergreen |
08:30 |
|
wjr joined #evergreen |
08:31 |
|
kmlussier joined #evergreen |
08:31 |
|
mrpeters joined #evergreen |
08:35 |
|
Dyrcona joined #evergreen |
08:37 |
|
mmorgan joined #evergreen |
08:39 |
|
akilsdonk joined #evergreen |
08:44 |
kmlussier |
@coffee |
08:44 |
* pinesol_green |
brews and pours a cup of Sulawesi Toraja, and sends it sliding down the bar to kmlussier |
08:49 |
wsmoak |
So… from http://evergreen-ils.org -> Get Involved I can get to Mailing Lists and then I noticed the Git Repositories link at the bottom to http://git.evergreen-ils.org |
08:50 |
wsmoak |
I’m missing the “how to check out [clone] and build the project” info. |
08:51 |
wsmoak |
possibly it would be obvious to a git expert… I’m still mapping svn concepts over onto git :) any hints? |
08:53 |
Dyrcona |
http://evergreen-ils.org/dokuwiki/doku.php?id=dev:git#quick_start_for_evergreen_contributors |
08:53 |
Dyrcona |
Basically, you need to git clone one of the repositories. |
08:54 |
|
jwoodard joined #evergreen |
08:54 |
wsmoak |
yep, it’s the url I couldn’t work out by guessing. ah, just missed the protocol bit. |
08:55 |
Dyrcona |
This might prove helpful: http://git-scm.com/book/en/v2 |
08:56 |
wsmoak |
thanks. just haven’t run across a repo that uses git:// instead of https:// and didn’t think of that. |
08:56 |
Dyrcona |
http didn't work with our repos? |
08:56 |
wsmoak |
…. and, rats. that’s going to need a firewall rule. |
08:56 |
Dyrcona |
I thought it would, but never tried. |
08:57 |
wsmoak |
nope. fatal: repository 'http://git.evergreen-ils.org/Evergreen.git/' not found |
08:57 |
Dyrcona |
Note that if you're going to contribute, you will need to submit a public ssh key to an email address that I never can remember. |
08:58 |
Dyrcona |
OK. Guess gitweb or whatever we're using isn't set up that way. |
08:58 |
kmlussier |
wsmoak: I find http://evergreen-ils.org/dokuwiki/doku.php?id=dev:git to be very helpful. |
08:59 |
Dyrcona |
The instructions for that are a bit higher up in the dokuwiki page I shared earlier. |
08:59 |
wsmoak |
would be nice if it’s easy. :) I have to go bug the paranoid network administrator to open (I assume) 9418 now. |
08:59 |
Dyrcona |
wsmoak: Outgoing? Those ports will vary, 'cause your computer picks them at random. |
08:59 |
|
ericar joined #evergreen |
09:00 |
Dyrcona |
'Course I don't know what the block was, so, I'm just guessing. |
09:00 |
Dyrcona |
@coffee kmlussier |
09:00 |
* pinesol_green |
brews and pours a cup of Ibonia Kenya Peaberry, and sends it sliding down the bar to kmlussier |
09:00 |
* Dyrcona |
figured you could use another. ;) |
09:00 |
Dyrcona |
@tea |
09:00 |
* pinesol_green |
An error has occurred and has been logged. Please contact this bot's administrator for more information. |
09:01 |
Dyrcona |
Huh. No tea. |
09:01 |
kmlussier |
Dyrcona: I can always use more caffeine. :) |
09:01 |
kmlussier |
I thought we had tea |
09:01 |
kmlussier |
Yes, csharp just poured some tea today |
09:02 |
kmlussier |
@tea |
09:02 |
* pinesol_green |
brews and pours a pot of Huang Shan Mao Feng Green Tea, and sends it sliding down the bar to kmlussier (http://ratetea.com/tea/teavivre/huang-shan-mao-feng-green-tea/6041/) |
09:02 |
wsmoak |
outbound. http://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols implies the git daemon is probably listening on 9418 on your side. |
09:02 |
Dyrcona |
That's OK. The wireless doesn't like me either, so I'm plugged in. |
09:02 |
* wsmoak |
reads some wiki pages |
09:03 |
kmlussier |
@tea Dyrcona |
09:03 |
* pinesol_green |
brews and pours a pot of Keemun Full Leaf Tea, and sends it sliding down the bar to Dyrcona (http://ratetea.com/tea/foojoy/keemun-full-leaf/6686/) |
09:03 |
Dyrcona |
wsmoak: OK. I usually allow just about anything from inside to talk to anything outside, but block incoming stuff based on destination port. I'm not so paranoid as people think. ;) |
09:03 |
Dyrcona |
When it comes to firewall configuration that is. |
09:03 |
csharp |
wsmoak: 9418/tcp open git - yep |
09:05 |
wsmoak |
thanks csharp. |
09:07 |
wsmoak |
thanks Dyrcona — this network definitely win the paranoia prize — everything is blocked unless specifically named and allowed. and it’s at my *house* ! |
09:14 |
kmlussier |
I've had a question about the instructions at http://evergreen-ils.org/dokuwiki/doku.php?id=dev:git that I keep forgetting to ask. In the Quick Start for Evergreen contributors and the Signing off on commits sections, the instructions list the fetch --all step |
09:14 |
kmlussier |
Shouldn't we add a step after that one to do a git merge or git rebase? |
09:15 |
kmlussier |
Or have I been doing things wrong? :) |
09:16 |
Dyrcona |
kmlussier: We'd prefer git rebase over merge in Evergreen. |
09:17 |
Dyrcona |
It is usually not necessary, unless some one else has made changes to code you've been working on. |
09:18 |
kmlussier |
Dyrcona: Really? I thought I previously had trouble pushing changes to the working repository because I hadn't done a rebase. If it's not necessary, then I guess it doesn't need to be added as a step. |
09:19 |
Dyrcona |
Doing a rebase will cause you to have to force push over a previously pushed branch, actually. |
09:19 |
Dyrcona |
Not doing a rebase your changes will push over your previous branch with no problems. |
09:21 |
jeff |
like most things with git, "it kinda' depends" |
09:22 |
kmlussier |
I also noticed that the git instructions at http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:how-to-contribute-documentation#make_and_contribute_changes_command_line are slightly different than the ones on the main git page. |
09:23 |
kmlussier |
I think it would be easier for new users if there was consistency between the two sets of instructions. On the doc page, it recommends a git pull. |
09:24 |
jeff |
a fetch followed by an ff-only merge (which may fail, where you would then fall back to a rebase of your local changes on top of the changes brought in by the git fetch) |
09:30 |
jeff |
hrm. returning to my desk, that was a half-thought. |
09:30 |
jeff |
maybe it would make more sense if i prefixed with "i usually go with" |
09:36 |
kmlussier |
It's the first time I've heard of an ff-only merge. :) |
09:36 |
jeff |
if you rebase your local commits and you haven't pushed them anywhere else, then you won't have need for force pushing, you won't be changing commits out from under someone who might have built changes on your commits, etc. |
09:37 |
jeff |
kmlussier: it's handy! --ff-only argument to git-merge. |
09:37 |
kmlussier |
Ah, that does sound handy. |
09:37 |
jeff |
kmlussier: if I *know* i don't want a merge commit, I use it. |
09:38 |
jeff |
there's also --no-ff, for when I want to force a merge commit (usually in repos other than evergreen) |
09:46 |
|
yboston joined #evergreen |
09:53 |
|
sbrylander joined #evergreen |
10:01 |
|
jboyer-isl joined #evergreen |
10:21 |
|
mdriscoll joined #evergreen |
10:42 |
|
jwoodard joined #evergreen |
11:03 |
|
jwoodard joined #evergreen |
11:04 |
|
vlewis joined #evergreen |
11:04 |
|
vlewis_ joined #evergreen |
11:05 |
|
vlewis__ joined #evergreen |
12:08 |
|
sandbergja joined #evergreen |
12:15 |
|
buzzy joined #evergreen |
12:21 |
|
ericar joined #evergreen |
12:30 |
|
buzzy joined #evergreen |
12:50 |
bshum |
@dessert |
12:50 |
* pinesol_green |
grabs some Coconut Cream Cake for bshum |
12:51 |
bshum |
Ugh, that's what I get for asking for a tasty treat after midnight :( |
12:53 |
kmlussier |
I'll take it! |
12:53 |
kmlussier |
@dessert bshum |
12:53 |
* pinesol_green |
grabs some Chocolate Pudding for bshum |
12:54 |
csharp |
@dessert bshum |
12:54 |
* pinesol_green |
grabs some Banana Puddin' for bshum |
12:54 |
csharp |
@dessert [someone] |
12:54 |
* bshum |
apparently needs more puddin' in his life. |
12:54 |
* pinesol_green |
grabs some Apple Pie for pinesol_green |
12:54 |
Dyrcona |
Evidently, pinesol_green has a thing for pie. |
12:54 |
kmlussier |
pinesol_green: that's not very nice. You should share with the rest of us. |
12:54 |
pinesol_green |
kmlussier: Mr. Spock: Something fascinating just happened. |
12:54 |
pinesol_green |
kmlussier: I am only a bot, please don't think I'm intelligent :) |
13:03 |
|
sarabee joined #evergreen |
13:24 |
|
kmlussier1 joined #evergreen |
13:53 |
wsmoak |
clicking around the source code tree http://git.evergreen-ils.org/?p=Evergreen.git;a=tree … where is the bulk of the code (in what language?) |
13:55 |
dbs |
wsmoak: Lots of Perl in Open-ILS/src/perlmods/lib |
14:00 |
wsmoak |
okay. then I will plan to stay safely on the other side of whatever apis you expose. ;) |
14:02 |
Dyrcona |
wsmoak: Guess where those APIs are documented. |
14:02 |
wsmoak |
lol… in that write-once language? I can’t even read my *own* perl stuff if I let it sit for a month. |
14:04 |
* Dyrcona |
doesn't take the bait. |
14:04 |
phasefx |
if you have a running Evergreen, you can query it for API documentation |
14:05 |
Dyrcona |
Except that not everything is properly documented that way. Very often the options are missing. |
14:05 |
phasefx |
yeah |
14:05 |
Dyrcona |
And, if you ask for all of the cstore or pcrud methods that are mostly dynamic, the system times out before returning the full list. |
14:06 |
Dyrcona |
Hmm... maybe just srfsh times out, but anyway. |
14:07 |
wsmoak |
I was looking at the install instructions. has anyone run it on OSX ? |
14:07 |
dbs |
wsmoak: not for a very very long time, to my knowledge |
14:07 |
Dyrcona |
wsmoak: The server on OS X? Not as far as I know. |
14:08 |
bshum |
Not for awhile. |
14:08 |
wsmoak |
(not in production, just to run it locally for development.) |
14:08 |
dbs |
in the mists of time (like 2008), artunit once claimed to have it mostly working on OS X |
14:08 |
Dyrcona |
berick and I worked a bit on getting it to build on FreeBSD. |
14:08 |
bshum |
SITKA tried once, if memory serves... but there were quirks and it didn't end well? |
14:09 |
Dyrcona |
bshum: Why are you not sleeping? |
14:09 |
jcamins |
Dyrcona: how did that go? I tried to get Koha installed on FreeBSD a few times. It was very unpleasant. |
14:09 |
Dyrcona |
;) |
14:09 |
bshum |
Dyrcona: I'll sleep... eventually. |
14:10 |
wsmoak |
okay. I guess that’s what ec2 is for nowadays. ;) |
14:10 |
Dyrcona |
jcamins: I don't think I ever really finished installing it. |
14:10 |
Dyrcona |
Too many other obligations. |
14:10 |
jcamins |
wsmoak: VirtualBox works if you have a newish Mac. |
14:10 |
jcamins |
With lots of RAM. |
14:11 |
jcamins |
(well, VirtualBox always works, but if you don't have a Mac with lots of RAM, you won't be able to create a VM large enough for EG) |
14:12 |
jcamins |
(where "always" means "in my limited experience") |
14:12 |
Dyrcona |
Yeah, you'll want at least 4GB to kick the tires. |
14:13 |
jcamins |
If, like me, you want to only use 3 or 3.5GB, you will spend a lot of time trying to find services you can shut down. |
14:13 |
bshum |
4 is best. You can squeak by with 3 if you only use demo data :) |
14:13 |
bshum |
Well, 2.5 anyways. |
14:14 |
* berick |
runs dev vm's with 1.5G w/ the stock demo data |
14:14 |
Dyrcona |
I run 6GB on my development VM with real data. |
14:14 |
berick |
they're not amazing, but they get the job done for light use |
14:16 |
jcamins |
berick: I'm amazed by them. |
14:16 |
* wsmoak |
tries to remember what she wanted to do before getting buried in infrastructure |
14:18 |
jeffdavis |
bshum: If we ever tried running the server on OSX, either I didn't hear about it or I've repressed the memory. Either is possible. :) |
14:19 |
bshum |
jeffdavis: Maybe I was thinking of something James worked on once. Or maybe I'm just wildly mistaken :) |
14:19 |
|
nhilton joined #evergreen |
14:21 |
bshum |
These days, I find that my memory isn't quite what it used to be... :( |
14:22 |
berick |
accidental_puns++ |
14:22 |
wsmoak |
Maybe a Docker container for it. Looks like that’s what all the cool kids are doing now. |
14:24 |
bshum |
Heh |
14:24 |
bshum |
Wasn't someone working on a Dockerized Evergreen once upon a time too? |
14:24 |
dbs |
jbfink (over in #code4lib) was tearing his hair out over it |
14:25 |
bshum |
Ah that's it. |
14:25 |
dbs |
He subsequently wrote an article about Docker for libraries in journal.code4lib.org |
14:26 |
|
mrpeters1 joined #evergreen |
14:26 |
dbs |
Evergreen got a (dis)honourable mention in the final sentence: And for regular systems administration tasks, who wouldn’t be happy to see a huge installation procedure [33] boiled down to a single command? |
14:28 |
bshum |
Heh |
14:28 |
bshum |
Special |
14:28 |
Dyrcona |
Meh. |
14:29 |
Dyrcona |
Or should I say, Get off my lawn!? |
14:39 |
bshum |
"Thank you Mario! But our Princess is in another castle!" |
14:41 |
* dbs |
would, for the record, love to see Evergreen's installation procedure boiled down to a single command... |
14:41 |
bshum |
"sudo apt-get install evergreen" right? :D |
14:41 |
Dyrcona |
And when it doesn't work, I'll send all of the questions to you! ;) |
14:42 |
bshum |
Noooooo |
14:43 |
jeff |
./install-evergreen.sh [optional arguments here] -- output is either a [should-be] working install [possibly after asking other not-specified-as-arguments questions] or an error that you don't seem to be running in an environment supported by the install script? :-) |
14:46 |
berick |
related, I just got around to porting the wheezy installer to trusty at random/collab/berick/trusty-auto-installer |
14:46 |
berick |
bonus points for being called "trusty auto installer" ;) |
14:47 |
bshum |
berick++ # that's awesome sounding :D |
14:50 |
phasefx |
berick++ Do we want to separate out the qa stuff from the wheezy installer, or bundle all installers + qa together? It looks like the trusty one would still work with the qa tests with the way it's producing output |
14:51 |
* berick |
wonders if anyone has had a chance to look at bug #1366964 |
14:51 |
pinesol_green |
Launchpad bug 1366964 in Evergreen "Transaction Issues with libdbi 0.9.0" (affected: 1, heat: 6) [Undecided,Confirmed] https://launchpad.net/bugs/1366964 |
14:51 |
berick |
phasefx: i like having the QA stuff in there |
14:51 |
berick |
though, admittedly, I don't often use it all. |
14:52 |
bshum |
berick: I was just looking at the code, but I'm not in a position to test till next week sometime. |
14:53 |
* berick |
nods |
14:53 |
|
dcook__ joined #evergreen |
14:54 |
bshum |
Eager to try it out though, of course :) |
14:54 |
phasefx |
berick: I think we should option out the timezone stuff.. it's important for the qa tests, maybe, but not for someone in some arbitrary timezone |
14:55 |
phasefx |
s/arbitrary/different/ |
14:55 |
berick |
phasefx: ah, hadn't thought about that |
14:55 |
* berick |
forgets what all is in the tests |
14:55 |
phasefx |
something prompted us to set the timezone for the qa vm, I think |
14:56 |
bshum |
Ugh, speaking of timezones.... good night folks. See you all again in a week. |
14:57 |
berick |
sleep well, bshum |
14:58 |
* phasefx |
very helpfully put "configure the timezone" in the commit message :-/ |
14:58 |
csharp |
@who will "configure the timezone"? |
14:58 |
pinesol_green |
jeff will configure the timezone. |
15:00 |
phasefx |
jeff: could you get rid of DST from the world? |
15:00 |
csharp |
@blame DST |
15:00 |
pinesol_green |
csharp: DST musta been an Apple employee. |
15:11 |
Dyrcona |
Russia is no longer doing DST. This was their last year. |
15:11 |
Dyrcona |
It's all an illusion anyway. |
15:13 |
kmlussier |
Time changes make me grumpy |
15:15 |
* csharp |
experiments with KVM/Spice/GNOME Boxes as a replacement for VirtualBox |
15:16 |
csharp |
berick: this walkthrough got me up and running with a bridged connection on NetworkManager on Fedora 20: https://www.happyassassin.net/2014/07/23/bridged-networking-for-libvirt-with-networkmanager-2014-fedora-21/ |
15:16 |
csharp |
(since we were chatting about that at the Hack-A-Way |
15:16 |
csharp |
) |
15:18 |
berick |
csharp: cool. i've seen that one. haven't tried it yet, though. |
15:20 |
csharp |
apparently another hoop to jump through to get the bridge working with Boxes, however: http://xkahn.zoned.net/blog/2013/11/26/networking-and-gnome-boxes/, but that looks doable |
15:29 |
hbrennan |
Does anyone know when the next version of OpenSRF (2.4.next, beta) will be released? |
15:35 |
* csharp |
imagines a line of Evergreeners waiting outside overnight outside Evergreen™ Headquarters waiting for their copy of OpenSRF 2.4 |
15:35 |
csharp |
hbrennan: I think gmcharlt is your source for that answer |
15:35 |
hbrennan |
I am in that line! |
15:36 |
csharp |
heh |
15:36 |
csharp |
I guess I am too |
15:36 |
gmcharlt |
hbrennan: take your ticket! take your ticket! |
15:36 |
hbrennan |
IT director is waiting for his firstborn baby to arrive and the clock is ticking to get an upgrade in before he takes off |
15:36 |
gmcharlt |
seriously, some time next week |
15:36 |
hbrennan |
Thanks, gmcharlt |
15:36 |
* csharp |
saw a huge crowd of people at the Apple Store at Lenox Mall standing around for hours *just in case* a shipment of new iPhones arrived |
15:37 |
hbrennan |
I'm glad that's not even a choice for me |
15:37 |
csharp |
hbrennan: fwiw, we're running our test 2.7.0 cluster on OpenSRF 2.4 alpha, and we haven't seen problems |
15:38 |
* csharp |
pets his trusty Galaxy Note 2 |
15:38 |
bshum |
hbrennan: fwiw, we run 2.7.0ish in production with OpenSRF 2.4 alpha and haven't seen any explosions either. |
15:38 |
hbrennan |
That's good to know, thanks csharp |
15:38 |
* bshum |
tries to sleep again |
15:38 |
csharp |
@blame insomnia |
15:38 |
pinesol_green |
csharp: insomnia stole bradl's tux doll! |
15:38 |
hbrennan |
csharp++ gmcharlt++ bshum++ |
15:38 |
bshum |
Well, OpenSRF master |
15:38 |
bshum |
:) |
15:38 |
hbrennan |
I need to log off/back in.. new conversations are hiding past the scroll.... |
15:39 |
bshum |
Insomnia and minor kerfuffles in server land. |
15:39 |
|
hbrennan joined #evergreen |
15:39 |
bshum |
Nothing some magic SQL can't solve though :D |
15:39 |
* bshum |
loves PostgreSQL magic |
15:40 |
bshum |
@loves PostgreSQL magic |
15:40 |
pinesol_green |
bshum: (loves [<channel>] [<user>]) -- Find out what <user> loves |
15:40 |
bshum |
Sigh |
15:40 |
bshum |
@love PostgreSQL magic |
15:40 |
pinesol_green |
bshum: The operation succeeded. bshum loves PostgreSQL magic. |
15:46 |
|
nhilton_ joined #evergreen |
16:19 |
dbs |
csharp: but can you run Evergreen on your Galaxy Note 2? |
16:51 |
jeffdavis |
Anyone got a few minutes to take a gander at bug 1353643 ? The proposed fix is complex and could use more eyeballs. |
16:51 |
pinesol_green |
Launchpad bug 1353643 in Evergreen "URI $9 displayes too many links in TPAC" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1353643 |
17:03 |
|
mdriscoll left #evergreen |
17:11 |
|
mmorgan left #evergreen |
17:34 |
|
kmlussier left #evergreen |
18:17 |
* gmcharlt |
tosses out bug 1386905 for critique |
18:17 |
pinesol_green |
Launchpad bug 1386905 in Evergreen "make TPAC handle HEAD requests better" (affected: 1, heat: 6) [Wishlist,New] https://launchpad.net/bugs/1386905 |
18:39 |
hbrennan |
ESI folks, would Veterans Day be a terrible time to expect support people on duty? |
18:53 |
|
nhilton joined #evergreen |
18:57 |
eeevil |
hbrennan: we're always on call, regardless. I'll check the calendar, though. sec |
18:58 |
hbrennan |
eeevil: I know you're always on call, but I don't want to be difficult! |
18:58 |
eeevil |
hbrennan: confirmed: we are not closed |
18:58 |
hbrennan |
eeevil: So it would be better than a Sunday? |
18:59 |
hbrennan |
Upgrading on an open day was not fun last time.. I'm just dreaming that I can convince others to join me on another day |
19:00 |
eeevil |
ah. well, November's schedule is pretty full. please request asap so we can get you in if it's not already full :) |
19:01 |
hbrennan |
Oh, we'll be doing the upgrade ourselves.. just less stressful if we know you're "there" |
19:02 |
hbrennan |
eeevil: Thanks for the info. Stay tuned. Lots of convincing yet to do on my end |
19:04 |
eeevil |
hbrennan_away: staying tuned. we'll be there for you, and thanks for the heads up! |
20:43 |
|
kmlussier joined #evergreen |
20:45 |
kmlussier |
@later tell csharp I think we may be having trouble with the oversight board list. There are recent 3 messages in the archive that don't appear to have been sent out. |
20:45 |
pinesol_green |
kmlussier: The operation succeeded. |
22:13 |
* jeff |
shakes his fist a marc_stream_importer.pl |
22:13 |
jeff |
quote the script, "Failed to import 1 records" |
22:19 |
jeff |
quoth, even. |
22:20 |
jeff |
(not to be confused with Kvothe) |
22:29 |
jeff |
ah. |
22:29 |
jeff |
1) marc_stream_importer.pl requires a full path for the spool file if running in --no-daemon mode |
22:30 |
jeff |
2) marc_stream_importer.pl deleted the spool file |
22:30 |
jeff |
3) the permissions in this particular test database are... in an interesting state. |
22:42 |
* jeff |
runs smack dab into bug 1170514 |
22:42 |
pinesol_green |
Launchpad bug 1170514 in Evergreen "vandelay.auto_overlay_bib_record discrepancy" (affected: 1, heat: 8) [Undecided,Confirmed] https://launchpad.net/bugs/1170514 |
23:14 |
|
dcook joined #evergreen |