| 00:46 |
|
dbwells_ joined #evergreen |
| 00:50 |
|
remingtron joined #evergreen |
| 00:50 |
|
dbwells_ joined #evergreen |
| 04:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:31 |
|
Callender joined #evergreen |
| 08:13 |
|
kmlussier joined #evergreen |
| 09:37 |
Dyrcona |
Java 2 was just marketing hype. |
| 09:37 |
Dyrcona |
They (Oracle) still call it JDK 9, JDK 8. |
| 09:37 |
Dyrcona |
So they have split versioning going on. |
| 09:39 |
Dyrcona |
And my created database finished a few minutes ago. Time to test my eg_staged_bib_overlay script. |
| 09:40 |
Dyrcona |
OK. So I messed up an option, obviously. :) |
| 09:42 |
Dyrcona |
All right. I omitted --dbhost, and this gives me an opportunity to make the script more generic. |
| 09:43 |
|
krvmga joined #evergreen |
| 16:11 |
jeff |
etc :-) |
| 16:12 |
mmorgan |
:) |
| 16:13 |
jeff |
Bmagic: yeah, only minor changes required, and one would probably be handled automatically by git and the other would be a no-op, but I'm commenting on bug 1331174 right now. |
| 16:13 |
pinesol_green |
Launchpad bug 1331174 in Evergreen "Long Overdue processing needs org unit settings separate from Lost Processing" [Wishlist,Confirmed] https://launchpad.net/bugs/1331174 |
| 16:30 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:37 |
|
khuckins__ joined #evergreen |
| 16:39 |
kmlussier |
I tried installing the web client again. I'm getting an error when I run npm install. https://pastebin.com/qevBnNc0 is what I see in the logs. |
| 16:52 |
jeff |
kmlussier: is that at the point where you've installed the LTS version of node and you're running "sudo npm install -g grunt-cli"? |
| 17:04 |
bshum |
I installed everything earlier this afternoon and all was fine |
| 17:05 |
jeff |
bshum: what version of node and npm do you have installed, and what distro are you using? |
| 17:05 |
kmlussier |
OK, I'm going to have to investigate later. I need to run off for the evening. |
| 17:05 |
bshum |
jeff: I was testing the Ubuntu 16.04 ansible stuff |
| 17:05 |
bshum |
So it used the makefile developer target to install node, etc. |
| 17:06 |
bshum |
I'm spinning up a new fresh VM to try that out again |
| 17:06 |
bshum |
On my other computer |
| 17:07 |
jeff |
bshum: looks like you would end up with nodejs-legacy 4.2.6~dfsg-1ubuntu4 in that case, which might be the difference between success and failure in your case vs kmlussier's case |
| 17:08 |
jeff |
bshum: i.e., what might have worked for you earlier today on xenial might not work for kmlussier on trusty. |
| 17:08 |
bshum |
jeff: Oh I see trusty |
| 17:08 |
bshum |
Ah okay no I just didn't scroll up far enough |
| 17:08 |
bshum |
I haven't built on trusty lately |
| 17:08 |
jeff |
16:55:27 < kmlussier> jeff: No. I run ubuntu-trusty-developer Makefile.install target as the root user in an earlier step, which should install the dependencies for me. |
| 17:09 |
bshum |
Or at least, not before the conference |
| 17:09 |
bshum |
It could be also the new stuff we changed for bower->npm... maybe that's unhappy with something on trusty :\ |
| 17:09 |
bshum |
And I broke it when we merged that |
| 17:09 |
bshum |
I'll spin up a trusty VM to check I guess |
| 17:34 |
* bshum |
thumbs his fingers waiting for Evergreen to finish installing pre-reqs |
| 17:36 |
bshum |
Okay, moment of truth coming up |
| 17:39 |
bshum |
Yup, unhappy :( |
| 17:43 |
bshum |
So it is related to the bower/npm switchup |
| 17:43 |
bshum |
It's choking on "angular-order-object-by": "rxfork/ngOrderObjectBy#npm" |
| 17:43 |
bshum |
Maybe our aged version doesn't know what to make of that line |
| 17:44 |
bshum |
I'll try installing a newer node and seeing what it does differently with that. |
| 17:48 |
* bshum |
hacks his trusty makefile to use the wheezy style for installing newer node |
| 17:54 |
* bshum |
waits, and waits, and keeps waiting... |
| 18:02 |
bshum |
Hmmmm |
| 18:02 |
bshum |
Yeah |
| 18:02 |
bshum |
Okay |
| 18:03 |
bshum |
So using a newer version of node helps with the problem |
| 18:03 |
bshum |
But I have discovered that the Makefile for Wheezy has not been updated to work with a newer version of node |
| 18:04 |
bshum |
It's still installing from source for version 0.10.28 |
| 18:04 |
bshum |
Cause that's what it still says in the Makefile.install source file |
| 18:04 |
bshum |
We fixed it in the eg_wheezy_installer for random repo, for the live test building |
| 18:04 |
bshum |
But the actual installer isn't working quite right |
| 18:05 |
bshum |
So we should rip all that stuff out |
| 18:05 |
bshum |
But yeah, Trusty also won't work without a newer node version |
| 18:05 |
* bshum |
goes to eat |
| 18:06 |
* bshum |
brings his laptop to think with while he eats |
| 18:42 |
bshum |
@later tell kmlussier Check out my work in progress branch: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/bshum/newer-node-for-wheezy-and-trusty |
| 18:42 |
pinesol_green |
bshum: The operation succeeded. |
| 18:42 |
bshum |
I ran those Makefile changes through a test on Trusty and ended up with newer nodejs and able to run all the npm package installs for Trusty |
| 18:42 |
bshum |
Same changes should apply towards Wheezy too |
| 18:43 |
bshum |
If it works out, we need some tweaks to the README instructions so that the Wheezy specific steps can go away and we can just stick to recommending use of the -developer make target |
| 18:44 |
bshum |
I think it ought to work for the debian-wheezy-developer target too. |
| 18:44 |
bshum |
But it's untested |
| 18:44 |
bshum |
I'll try more of it later on. |
| 18:44 |
* bshum |
goes out to enjoy his Friday :) |
| 18:47 |
bshum |
dbs++ # for new nodejs inspiration from the auto installer scripts |
| 18:48 |
bshum |
kmlussier++ # for helping to find the problem |
| 18:48 |
* bshum |
disappears |
| 18:57 |
|
kmlussier joined #evergreen |
| 18:58 |
kmlussier |
bshum++ |
| 21:05 |
jeff |
Looking at circ policy for a library that makes a circ-duration distinction between "new" items and "replacement" items... currently they use a circ modifier on the "new" items, and while it's so tempting to use "Item Age <" in a circ policy matrix, that won't do it... |
| 04:31 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 06:51 |
|
dbs_breaker_of_t joined #evergreen |
| 06:52 |
dbs_breaker_of_t |
Okay, now to find out why that path wasn't happy. |
| 09:26 |
|
maryj joined #evergreen |
| 09:28 |
|
yboston joined #evergreen |
| 09:41 |
|
kmlussier joined #evergreen |
| 09:42 |
kmlussier |
dbs: Sometimes phasefx will do an unscheduled livetest run if a fix to the tests is added. |
| 09:46 |
|
terran joined #evergreen |
| 10:00 |
jeff |
just as i was about to remark on how useful irc logs can be, i find a case where i xkcd 979'd myself. |
| 10:00 |
jeff |
"oh hey, there's the error." |
| 15:50 |
Dyrcona |
I haven't tried Haskell, though I've sniffed around the edges. |
| 15:50 |
Dyrcona |
An erlang implementation/transport for OpenSRF seems natural enough without ejabberd. :) |
| 15:51 |
|
kmlussier joined #evergreen |
| 15:51 |
Dyrcona |
But erlang syntax is really weird, and I look at back at the sample/test programs I wrote in 2010/2011, and I wonder, "What does that do, again?" |
| 15:52 |
Dyrcona |
I should write an OpenSRF/gateway client in Emacs Lisp. I might actually have a use for that. |
| 15:52 |
jonadab |
Yeah, I haven't tried Haskell either; from what I know of it, it seems sort like lisp with a higher learning curve, for smarter programmers. Or something. |
| 15:53 |
Dyrcona |
s/smarter programmers/masochists/ # Fixed that for you. :) |
| 16:11 |
Dyrcona |
Lots of database stuff going on. |
| 16:12 |
Dyrcona |
New fingerprints, new 901$s field, browse and facet ingest...something else that update 9 million records in our system, but runs fast compared to the others. |
| 16:21 |
|
mmorgan joined #evergreen |
| 16:32 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 16:33 |
bshum |
yay! success! |
| 16:33 |
bshum |
dbs++ |
| 16:36 |
Dyrcona |
:) |
| 18:16 |
|
jvwoolf left #evergreen |
| 18:20 |
|
Jillianne joined #evergreen |
| 19:45 |
* dbs |
breathes a sigh of relief |
| 19:48 |
jeff |
those hourly test failure charges would have made for a terrible weekend. ;-) |
| 19:52 |
dbs |
jeff: that reminded me to shut down my GCE instance |
| 21:04 |
* gmcharlt |
has the first development update blog post queued up to post tomorrow morning |
| 21:12 |
* bshum |
contemplates renaming "2.next" to "3.next" in LP |
| 02:56 |
|
dbs joined #evergreen |
| 02:57 |
|
Jillianne joined #evergreen |
| 05:01 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:01 |
|
kmlussier joined #evergreen |
| 07:03 |
kmlussier |
I'm going to delete all of those EvergreenILS tweets that suddenly appeared from the Planet Evergreen feed overnight. Not sure what happened there. |
| 08:54 |
dbs |
because they were "new" :) |
| 08:54 |
gsams |
oh, so that's why my RSS went crazy |
| 08:54 |
kmlussier |
Ah! That explains everything. I thought the problem was with the app I use to republish the feed on Twitter. |
| 08:54 |
dbs |
I managed to add a "umm, max of 2 new entries per feed" limit after that |
| 08:55 |
dbs |
but too late for the twitter feed (and I bet it shuffled all of the other entries around too) |
| 08:55 |
dbs |
sorry for the churn folks |
| 08:55 |
dbs |
yes I need coffee as I dive in to see what happened with the test build... I see the karma tests failed but WHY? :) |
| 08:56 |
dbs |
thanks for cleaning up the twitter feed kmlussier |
| 08:56 |
gsams |
@coffee dbs |
| 08:56 |
* pinesol_green |
brews and pours a cup of Bonsai Blend Espresso, and sends it sliding down the bar to dbs |
| 08:56 |
kmlussier |
The Twitter stuff made me forget there was a test failure. |
| 08:57 |
kmlussier |
I'm guessing it's related to the removal of bower? |
| 08:59 |
|
rlefaive_ joined #evergreen |
| 09:00 |
dbs |
yep |
| 09:01 |
|
finnx joined #evergreen |
| 09:02 |
|
finnx joined #evergreen |
| 09:04 |
|
Dyrcona joined #evergreen |
| 09:06 |
dbs |
oh, I have a theory. live-test builds runs "grunt build && grunt test" whereas our install instructions say to use "grunt all" |
| 09:07 |
dbs |
but just tried that with no failures, albeit not on a wheezy system. hmm |
| 09:09 |
dbs |
ah, [33mWARN [watcher]: [39mPattern "/home/opensrf/Evergreen/Open-ILS/web/js/ui/default/staff/node_modules/angular-sanitize/angular-sanitize.min.js" does not match any file. |
| 09:13 |
dbs |
weird, it's installing the right version of angular-sanitize. how is it not finding that file? |
| 09:15 |
Dyrcona |
No wonder reporting is so slow...There are so many views that depend on action.all_circulation, at least in our database. |
| 09:25 |
|
yboston joined #evergreen |
| 09:32 |
miker |
dbs++ # cache busting |
| 14:18 |
berick |
that's probably it |
| 14:18 |
berick |
oh |
| 14:18 |
berick |
i would expect that to work.. |
| 14:19 |
csharp |
I expected it too - I'm going to do some more testing on it to try and nail down what's up |
| 14:22 |
|
rlefaive joined #evergreen |
| 14:32 |
kmlussier |
csharp++ # acq bug squashing |
| 14:37 |
csharp |
berick: behavior right now - on a 4-lineitem PO with one copy per lineitem, I activate it, receive 3 copies (which marks the lineitem received), cancel the copy on the last item (which doesn't affect the lineitem status) then I use the dropdown menu to cancel the lineitem - PO stays "on-order" |
| 16:37 |
Dyrcona |
Yeap. That's what happened, and I have four stashes hanging around. |
| 16:38 |
Dyrcona |
Too much swinging from branch to branch. |
| 17:01 |
berick |
csharp: https://bugs.launchpad.net/evergreen/+bug/1257915/comments/14 |
| 17:01 |
pinesol_green |
Launchpad bug 1257915 in Evergreen "Acq: purchase orders stay "on-order" with some lineitems received and the rest canceled" [Medium,Confirmed] - Assigned to Chris Sharp (chrissharp123) |
| 17:01 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 17:04 |
berick |
gmcharlt: alas, rollover_phone_to_print.pl to print has been disabled here for a while. i'm in the dark on that one. I can eyeball it, though. |
| 17:05 |
|
mmorgan left #evergreen |
| 17:31 |
csharp |
berick: rock on - I'll give your branch a go |
| 18:59 |
|
jvwoolf joined #evergreen |
| 19:26 |
bshum |
dbs: I just added some thoughts for use of pocommentclean on https://bugs.launchpad.net/evergreen/+bug/1681864/comments/1 |
| 19:26 |
pinesol_green |
Launchpad bug 1681864 in Evergreen "db-seed.po files need cleanup to remove duplicate IDs from generated localized seed data" [Medium,Confirmed] |
| 19:26 |
bshum |
In my very limited initial test, I think it'll help us to fix all the IDs in the comments. |
| 19:27 |
* bshum |
will experiment further after dinner. Or maybe tomorrow if he decides to go to bed early instead |
| 19:55 |
|
dcook joined #evergreen |
| 20:12 |
csharp |
berick++ # your branch works for me - signoff on the way |
| 20:39 |
jonadab |
That building was _residential_? I assumed it was office spaces. |
| 21:20 |
jonadab |
Yeah, at the conference. |
| 21:20 |
jonadab |
The blue one. |
| 21:20 |
|
dcook joined #evergreen |
| 22:33 |
dbs |
bshum++ |
| 22:34 |
dbs |
I've had a few issues of the Launchpad "try again later" over the past couple of weeks, yeah |
| 22:34 |
* dbs |
tries to concentrate on the wheezy build issue |
| 22:47 |
dbs |
once this is fixed, maybe it's time to consider jessie or xenial (or both) as the live-testing platforms? |
| 22:47 |
dbs |
wheezy is dead in a year: https://wiki.debian.org/LTS |
| 23:11 |
berick |
can practically hear it wheezing |
| 23:13 |
* dbs |
suspects 'npm --version' returning 1.x when installed with nodejs 0.10.x, vs. npm 3.x with a more modern mode, might be a factor |
| 23:14 |
dbs |
"npm install -g npm" gets us to npm 4.x (and a warning that nodejs 0.10.x is ancient, what are you thinking?!?) and sure enough, angular-sanitize is now installed as a dependency of ng-toast. |
| 23:15 |
dbs |
and that fixed the tests. |
| 23:18 |
dbs |
we should consider updating some of those deps; grunt-cli 0.1.13 was 2014, and as of 2016-04 was at 1.2.0 |
| 23:20 |
dbs |
similar to grunt itself (0.4.5 2014-05; 1.0.1 2016-04) |
| 23:27 |
dbs |
but then we install grunt-cli globally and use that so we get the latest anyway? hmm |
| 23:32 |
dbs |
anyway, pushed a fix to the wheezy_installer so hopefully we'll see the tests back to happy tomorrow |
| 05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:13 |
|
rjackson_isl joined #evergreen |
| 07:22 |
|
agoben joined #evergreen |
| 09:33 |
|
dteston joined #evergreen |
| 09:34 |
|
collum_ joined #evergreen |
| 09:48 |
csharp |
813ac365b |
| 09:48 |
pinesol_green |
csharp: [evergreen|Mike Rylander] We don't have a matched_attr column anymore, because we're using the fancy expression tree, so test for 901c match directly - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=813ac36> |
| 09:53 |
|
mmorgan1 joined #evergreen |
| 09:55 |
jeff |
ah yes, a 2011 vintage commit. code that survives mostly unchanged to this day. excellent selection, sir! |
| 09:58 |
csharp |
jeff++ |
| 09:59 |
csharp |
jeff: the funny thing is, I have hit this bug before: https://bugs.launchpad.net/evergreen/+bug/1170514/comments/5, but I didn't update our production server, just the test server using acq |
| 09:59 |
pinesol_green |
Launchpad bug 1170514 in Evergreen "vandelay.auto_overlay_bib_record discrepancy" [Undecided,Confirmed] |
| 09:59 |
csharp |
life is just endless circles |
| 10:09 |
jeff |
is vandelay.auto_overlay_bib_record the only affected function? |
| 10:10 |
jeff |
but yes, i can also confirm that we have the outdated function |
| 10:11 |
jeff |
i have replaced some other vandelay functions before, but without checking notes i don't know which functions, or the underlying reason for needing to replace them. |
| 10:11 |
jeff |
but apparently not this function. |
| 10:11 |
dbs |
so what's the situation with merging to master / rel_2_12 now? any special processes beyond the usual double sign-off + test(s)? |
| 10:13 |
jeff |
dbs: with the added explicit statement that rel_2_12 would be bugfixes and not new features, I think you've got it correct. |
| 10:14 |
dbs |
okay, thanks for the verification :) |
| 10:20 |
* kmlussier |
catches up to where we left off with the web team two years ago. |
| 10:31 |
pinesol_green |
Launchpad bug 1170514 in Evergreen "vandelay.auto_overlay_bib_record discrepancy" [Undecided,Confirmed] |
| 10:34 |
* Dyrcona |
wonders if make release can make a db upgrade script without making a tarball? |
| 10:43 |
* jeff |
looks askance at this email regarding the non-optional disclosure of certain information to conference exhibitors and sponsors |
| 10:44 |
bshum |
dbs++ # new test |
| 10:45 |
jeff |
is that sharing/disclosure something that attendees agree to when registering on eventbrite? i was not responsible for my registration / signup this year, so i can't pull from my own experience. |
| 10:46 |
jeff |
I know it's pretty typical for many conferences (I still get spam and junk mail over a decade later). I just didn't know that this conference was one of those. |
| 10:46 |
kmlussier |
jeff: In the past, there was a checkbox on the registration form. |
| 10:54 |
kmlussier |
JBoyer: If the vendors are at the conference, though, they would be able to get the list. But was there a list this year? I didn't see one. |
| 10:54 |
jeff |
last year the list was sent to attendees as an expiring dropbox link to an xlsx document. |
| 10:54 |
kmlussier |
My recollection is that the "This list is not to be published..." language was in the footer of every page of the attendee list. Just to make it clear. |
| 10:55 |
bshum |
dbs: I remember encountering https://bugs.launchpad.net/evergreen/+bug/1681864 when I tested the fixes for i18n in db.seed too. But I found that if I were to remove the resulting PO files (git clean or whatnot since we don't track them) and then rebuild, it would align the expected IDs. Presumably when doing make_release for new tarballs from git, this would approach would work similarly as long as we worked on clean repositories, but if any leftover files |
| 10:55 |
bshum |
were in the way, then yeah... duplicates |
| 10:55 |
pinesol_green |
Launchpad bug 1681864 in Evergreen "db-seed.po files need cleanup to remove duplicate IDs from generated localized seed data" [Undecided,Triaged] |
| 10:55 |
jeff |
this year i've not seen a list or mention of a list, other than the one that is apparently being given to sponsors/exhibitors which you can only partially opt out of. |
| 10:55 |
jeff |
it's just a little unusual, either a departure from past practices, or more transparency about what was always done in the past and we just didn't know about it. dunno! |
| 16:44 |
jeff |
oh, hah. |
| 16:44 |
jeff |
[comment redacted] |
| 16:59 |
|
mmorgan left #evergreen |
| 17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:02 |
bshum |
dbs++ # new test is successful! so says the test run above :) |
| 17:08 |
kmlussier |
Yay! |
| 17:08 |
kmlussier |
dbs++ |
| 19:54 |
|
genpaku joined #evergreen |
| 21:35 |
pinesol_green |
[evergreen|Dan Scott] LP#1680624 angular-ui-bootstrap stopped shipping minified files - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=4a068d0> |
| 21:35 |
pinesol_green |
[evergreen|Dan Scott] LP#1680624 Remove bower packaging bits - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c66d632> |
| 21:43 |
dbs |
bshum++ # thanks! |
| 21:49 |
bshum |
Of course, right after I do that |
| 21:49 |
bshum |
I think about the automated builder |
| 21:49 |
bshum |
http://git.evergreen-ils.org/?p=working/random.git;a=shortlog;h=refs/heads/collab/phasefx/wheezy_installer |
| 21:50 |
bshum |
And the fact that the test run tomorrow needs updating |
| 21:50 |
dbs |
well that's the random.git one, yeah, I can poke that |
| 21:50 |
dbs |
really the automated builder should just use the make targets that y'all painstakingly added rather than its own workarounds |
| 21:50 |
bshum |
+1, for sure |
| 04:12 |
|
NxT joined #evergreen |
| 04:13 |
NxT |
Hi all, i'm looking for a guide or info on how to integrate 3M RFID Readers into Evergreen - is this possible? what do i need for this? |
| 04:36 |
|
rlefaive joined #evergreen |
| 05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 05:03 |
|
rlefaive joined #evergreen |
| 06:24 |
|
rlefaive joined #evergreen |
| 06:40 |
|
rlefaive joined #evergreen |
| 11:30 |
alynn26 |
gmcharlt++ |
| 11:30 |
mmorgan |
gmcharlt++ |
| 11:30 |
mmorgan |
Not too hard, I hope;-) |
| 11:32 |
Dyrcona |
Heh. Make sure you run your scripts in the correct test database. :) |
| 11:33 |
Dyrcona |
A missing copy location can cause you problems. |
| 11:43 |
gmcharlt |
alynn26: miker: bit more to the problem, but webby is now fully back up |
| 11:45 |
gmcharlt |
er, mmorgan ^^ |
| 14:05 |
JBoyer |
(provided, of course, that all of the IDL links are accurate and functional) |
| 14:05 |
jeff |
yeah, and reproducing what we have in Jasper in this case might be as simple as defining a creative new report source in the IDL |
| 14:05 |
csharp |
JBoyer: I was just thinking about that |
| 14:05 |
jeff |
i haven't tested, though. |
| 14:07 |
jeff |
grr. google's index of docs.evergreen-ils.org is out of date, and of course the site's search box uses google... |
| 14:07 |
jeff |
if only i had a local git repo that i could grep... |
| 14:07 |
jeff |
oh, wait! |
| 14:08 |
alynn26 |
@dbs that is what I had to do to fix the ones I had in a very large bucket. |
| 14:08 |
pinesol_green |
alynn26: As great as you are man, you'll never be greater than yourself. |
| 14:19 |
dbs |
pinesol_green: I do not like your gender assumptions |
| 16:22 |
Dyrcona |
I may just wipe it out by hand. |
| 16:26 |
Dyrcona |
Yeah, think I'll just purge the packages, then delete anything left behind by hand. |
| 16:26 |
Dyrcona |
Then, I'll link /var/lib/postgresql -> /db before installing the new version. |
| 16:39 |
Dyrcona |
So, on a test vm were i did a pg upgrade, I cannot now remove postgresql-9.2 after running the delete_old_cluster script. |
| 16:40 |
Dyrcona |
The package status is BB in aptitude. |
| 16:41 |
jeff |
presumably you've broken the prerm/postrm scripts' ability to do their jobs. |
| 16:41 |
jeff |
or just one of the two. |
| 16:47 |
Dyrcona |
Well, this is a throwaway vm that I made to practice the pg_upgrade process. |
| 16:47 |
* Dyrcona |
should bet back to actual work. |
| 16:54 |
Dyrcona |
So, on training, I removed the packages and then deleted the leftover data files. |
| 17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:04 |
|
mmorgan left #evergreen |
| 17:22 |
berick |
yay, code4lib '18 in DC |
| 17:24 |
Bmagic |
yep! |
| 03:45 |
bshum |
As is, running the sync work off lupin for now |
| 04:09 |
|
rlefaive joined #evergreen |
| 04:37 |
|
rlefaive joined #evergreen |
| 05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 05:04 |
|
rlefaive joined #evergreen |
| 05:31 |
|
rlefaive joined #evergreen |
| 06:52 |
|
rlefaive joined #evergreen |
| 08:13 |
|
rlefaive joined #evergreen |
| 08:41 |
|
rlefaive joined #evergreen |
| 09:08 |
|
rlefaive joined #evergreen |
| 09:20 |
dbs |
bshum++ |
| 09:21 |
dbs |
I applied the Windows 10 Creators Update on my dual-boot laptop last night because I like being up to date even on OSes that I almost never use |
| 09:22 |
dbs |
And of course it destroyed grub. That Sys Admin IG was timely :) |
| 09:23 |
dbs |
I did get to test my branch for https://bugs.launchpad.net/evergreen/+bug/1681095 last night and force-pushed a fix |
| 09:23 |
pinesol_green |
Launchpad bug 1681095 in Evergreen "Extend browser cache-busting support for all stylesheets, JavaScript, and images in default public catalogue" [Undecided,New] |
| 10:29 |
|
rlefaive joined #evergreen |
| 10:48 |
|
genpaku joined #evergreen |
| 16:15 |
|
Jillianne2 joined #evergreen |
| 16:19 |
dbs |
oh jeff... looks like I beat you home despite leaving 15 hours later than you. delta-- |
| 16:49 |
|
rlefaive joined #evergreen |
| 17:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:17 |
|
rlefaive joined #evergreen |
| 17:52 |
|
kaffenkj- joined #evergreen |
| 18:11 |
|
rlefaive joined #evergreen |
| 00:39 |
|
book` joined #evergreen |
| 05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 05:36 |
|
remingtron joined #evergreen |
| 05:36 |
|
dbwells joined #evergreen |
| 07:07 |
|
rjackson_isl joined #evergreen |
| 12:33 |
|
jihpringle joined #evergreen |
| 12:41 |
|
maryj joined #evergreen |
| 12:43 |
miker |
kmlussier: webstaff collab branch finally sync'd and new stuff pushed |
| 12:55 |
jihpringle |
frank_guel: one my techs add a © to one of our MARC templates on our 2.12 test server and I'm not seeing any weirdness |
| 12:56 |
jihpringle |
maybe there something between 2.8 and 2.12 causing the character issue |
| 12:58 |
frank_guel |
I will try putting a new database without nothing and test |
| 13:04 |
|
ppound joined #evergreen |
| 13:07 |
mmorgan |
Is it possible to use copy criteria in an action trigger filter? |
| 13:08 |
mmorgan |
For example, I want to add "-and" : [ { "target_copy.circ_modifier" :["reserve"] } ] |
| 13:42 |
frank_guel |
that is the postgresql 9.4.10 config |
| 13:42 |
frank_guel |
What Do you refer about the environment that you run the staff client in? |
| 13:43 |
Dyrcona |
OK. That looks OK, but I usually use collation C and character type C. You definitely want UTF-8 encoding in the database. |
| 13:44 |
frank_guel |
I did a test, and the problem is just with the new marc records |
| 13:45 |
Dyrcona |
Created from the template? |
| 13:45 |
frank_guel |
yes, |
| 13:46 |
Dyrcona |
Was the template originally created in a UTF-8 environment? |
| 14:51 |
berick |
yes indeed |
| 14:52 |
Dyrcona |
Might have been nice if the release notes mentioned that. :) |
| 14:53 |
Dyrcona |
But, anyway. I'm looking at the ebook api and it looks I don't need to run the service unless I enable the api. |
| 14:55 |
jeffdavis |
Dyrcona: yes, that should be true. Nothing depends on that service except the integration layer in the OPAC (and some live tests I suppose). |
| 14:55 |
Dyrcona |
jeffdavis: Thanks for confirming. That is what I'm seeing from the code. |
| 14:56 |
Dyrcona |
I've asked the powers that be if we should enable it, yet, or wait for 3.0. |
| 14:56 |
Dyrcona |
jeffdavis++ |
| 15:03 |
pinesol_green |
Dyrcona: The outlook is good. |
| 15:03 |
Dyrcona |
hah |
| 15:23 |
|
khuckins__ joined #evergreen |
| 15:31 |
kmlussier |
Funny, we were just looking at the ebook stuff. |
| 15:33 |
kmlussier |
jeffdavis: I just set up our test server with our Overdrive credentials. I noticed that if I try to use the Download link from e-items checked out tab, it brings me to https://mlnc1.noblenet.org/eg/opac/myopac/undefined |
| 15:33 |
kmlussier |
Did I miss a configuration step? |
| 15:35 |
|
mmorgan joined #evergreen |
| 15:39 |
jeffdavis |
kmlussier: no, that's a bug |
| 15:39 |
kmlussier |
OK, I'll file one then. :) |
| 16:04 |
|
khuckins_ joined #evergreen |
| 16:12 |
JBoyer |
I'm out until the conference next week, see some of you then! |
| 16:32 |
|
khuckins__ joined #evergreen |
| 17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:13 |
|
mmorgan left #evergreen |
| 17:46 |
jeffdavis |
@later tell kmlussier OverDrive download link bug report: https://bugs.launchpad.net/evergreen/+bug/1677813 |
| 17:46 |
pinesol_green |
jeffdavis: The operation succeeded. |
| 03:00 |
|
Jillianne joined #evergreen |
| 04:23 |
|
hawahaniz_ left #evergreen |
| 05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 06:55 |
|
agoben joined #evergreen |
| 07:08 |
|
rjackson_isl joined #evergreen |
| 07:08 |
|
rjackson_isl_ joined #evergreen |
| 12:31 |
JBoyer |
Thats the hope! |
| 12:32 |
kmlussier |
Or, even, 2.12.2. No reason to wait for 3.0. :) |
| 12:32 |
JBoyer |
Well, the hope is that there aren't that many to *be* filed, but you know. |
| 12:32 |
kmlussier |
JBoyer: I always feel very confident that my thorough testing revealed everything there is to find. And then people start using it in production, and I find out I'm wrong. |
| 12:33 |
JBoyer |
"But WHY would anyone do THAT?! That's not how any of this works!" |
| 12:33 |
berick |
JBoyer: vacuum full analyze the whole db? nice |
| 12:35 |
* berick |
has a few vacuum-full's lined up, expects to recover several hundred GB of disk space |
| 12:35 |
berick |
after cleaning up copy auditor and anonymizing holds |
| 12:35 |
JBoyer |
berick, Yeah, that's where all the time will go. I think the db upgrade scripts (minus reingest, of course) only takes a few minutes. I was about to do another test run on our dev server to double check. |
| 12:36 |
JBoyer |
we keep all of our auditors trimmed (we delete 2 hogsheads a fortnight), and we run circ/hold purges daily. I'm hoping it all goes smoothly. |
| 12:36 |
berick |
heh |
| 12:37 |
JBoyer |
I'm reminded though that slony will be the hassle here. Perhaps for the next large upgrade we move to Pg 9.5 and back to the built in sync. |
| 16:06 |
Dyrcona |
I've been too bogged down in the day to day to keep up with everything. |
| 16:28 |
|
mmorgan joined #evergreen |
| 16:33 |
|
khuckins_ joined #evergreen |
| 17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:10 |
|
mmorgan left #evergreen |
| 17:38 |
|
khuckins joined #evergreen |
| 18:56 |
|
kenstir joined #evergreen |
| 19:22 |
jihpringle |
frank_guel: that sounds like a bug to me, I checked our templates which came from 2.10 to 2.12 and we don't have any symbols in our templates so I can't replicate |
| 19:23 |
frank_guel |
could be an accent or a symbol. |
| 19:25 |
jihpringle |
our templates are pretty much just lists of blank fields per item type |
| 19:27 |
frank_guel |
ah ok ok, I did another test, I open the k_book.xml default template, add a word with an accent, and it save it as a weird character, if I open it again and replace the character with the correct word, save the changes and it looks well |
| 19:28 |
jihpringle |
frank_guel: I'll ask one of our techs to add some accents/symbols to one of our templates and see if we can replicate |
| 19:30 |
frank_guel |
that sounds great, thanks |
| 19:30 |
jihpringle |
I'll let you know whether or not we can replicate |
| 01:25 |
|
StomproJ joined #evergreen |
| 05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:08 |
|
rjackson_isl joined #evergreen |
| 07:27 |
pinesol_green |
[evergreen|Jane Sandberg] Docs: adding more to the config.tt2 variable list - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=92ebc0a> |
| 07:31 |
|
agoben joined #evergreen |
| 07:50 |
|
kmlussier joined #evergreen |
| 08:09 |
|
Dyrcona joined #evergreen |
| 15:02 |
|
mmorgan1 joined #evergreen |
| 15:06 |
bshum |
Lucky cricket. |
| 15:08 |
|
frank_guel joined #evergreen |
| 15:09 |
frank_guel |
Hi all, I have a question, I am ussing the 2.12.0EGv in a test server, I am getting the following console error in chrome when I go to the loggin page, "Uncaught Error: Could not load class 'openils.widget.AutoSuggest'. Did you spell the name correctly and use a full path, like 'dijit.form.Button'?" |
| 15:10 |
frank_guel |
I guess it is not an 2.12.0 error because I am ussing the 2.8.4 version in a production system and it happends too |
| 15:12 |
kmlussier |
I don't see it, but I don't have Autosuggest enabled. |
| 15:13 |
kmlussier |
But I just tried another catalog that does use Autosuggest. Yup. I can confirm that the uncaught error does appear in the console. |
| 15:14 |
kmlussier |
And autosuggest does not work on the login page. |
| 15:18 |
bshum |
Fwiw, the same error occurs on Firefox too. Autosuggest / dojo unhappiness. |
| 15:20 |
bshum |
Since we discontinued autosuggest by default with Evergreen 2.6 new installations, I don't think there's been any further movement on it. |
| 15:31 |
|
Jillianne joined #evergreen |
| 15:42 |
pinesol_green |
[evergreen|Jane Sandberg] Docs: Web client no longer has borders around patron name - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=c85e457> |
| 15:48 |
|
jvwoolf joined #evergreen |
| 15:51 |
|
mmorgan joined #evergreen |
| 16:07 |
|
khuckins_ joined #evergreen |
| 16:21 |
|
mmorgan left #evergreen |
| 17:01 |
pinesol_green |
News from qatests: Test Failure <http://testing.evergreen-ils.org/~live> |
| 17:09 |
|
khuckins__ joined #evergreen |
| 20:46 |
|
kenstir joined #evergreen |
| 21:02 |
kenstir |
Hey hi ho. I have a question about services available to the android app through OSRF. |
| 03:14 |
|
Callender joined #evergreen |
| 03:17 |
|
Callender_ joined #evergreen |
| 03:35 |
|
RBecker joined #evergreen |
| 05:02 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 12:53 |
|
Dyrcona joined #evergreen |
| 16:16 |
|
Jillianne joined #evergreen |
| 16:52 |
|
pinesol_green` joined #evergreen |
| 17:02 |
pinesol_green` |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 20:16 |
|
kenstir joined #evergreen |
| 20:34 |
dbs |
heh, bshum, install docs in master still provide instructions for compiling node 0.10.28 from source: http://git.evergreen-ils.org/?p=Evergreen.git;a=blob;f=docs/installation/server_installation.txt;h=539ab85ea1c3037474242e668e5aaa15c8c3028f;hb=refs/heads/master#l154 |
| 20:44 |
dbs |
Also OpenSRF instructions for Debian websockets install assumes wheezy it seems; directions are for apache 2.2 |
| 21:22 |
dbs |
and that enabled me to start it, yay |
| 21:25 |
dbs |
oh yeah, cloud firewall blocking 7682, might as well set up that nginx proxy |
| 21:28 |
dbs |
haha, had to stop apache2 before installing nginx or else I would get "dpkg: dependency problems prevent configuration of nginx nginx depends on nginx-full" |
| 21:31 |
bshum |
dbs: Yeah I think csharp already noted that issue for nginx |
| 21:31 |
bshum |
It should be in the latest OpenSRF master already |
| 21:31 |
bshum |
Maybe the file hasn't been regenerated for the website |
| 21:33 |
bshum |
As for master, I guess we could update it to a newer nodejs version. But the note ahead of it also specifies that if you use the developer make target on Jessie, Trusty, or Xenial, you can skip the building from scratch |
| 21:34 |
bshum |
It's really only for Wheezy that we built from source because the version of nodejs wasn't new enough to do it. Or didn't exist I guess. |
| 21:34 |
* bshum |
hasn't tested with the latest nodejs, but figure it could be an interesting experiment down the road to try |
| 21:36 |
bshum |
Hmm, nope, the OpenSRF-2.5.0 readme has csharp's change for reconfiguring the apache ports first, before installing nginx. |
| 21:36 |
bshum |
Maybe you saw something new dbs |
| 21:39 |
dbs |
yay webby |
| 21:39 |
dbs |
(got it working) |
| 21:40 |
bshum |
dbs: Since you're using the proxy, I might point you in the direction of https://bugs.launchpad.net/evergreen/+bug/1648234 |
| 21:40 |
pinesol_green |
Launchpad bug 1648234 in Evergreen "Internal Apache port leaks when using proxy" [Medium,Confirmed] |
| 21:41 |
dbs |
yeah, I had updated the ports in eg.conf but missed ports.conf |
| 21:41 |
dbs |
there are many ways to get knifed |
| 21:42 |
bshum |
Yeah I feel like not many have really tested it. |
| 21:42 |
bshum |
I know I've only setup nginx proxy twice so far. And haproxy only once, unsuccessfully. So more eyes, the better I'm sure. |
| 21:43 |
dbs |
I've gone through the steps a few times now, but last time was on trusty; this time jessie |
| 21:47 |
dbs |
and time before that was when we upgraded in September to 2.10, so few and far between |
| 21:47 |
dbs |
part of my fun this time around was going back and enabling webby after having already installed evergreen |
| 05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 07:10 |
|
rjackson_isl joined #evergreen |
| 07:46 |
|
agoben joined #evergreen |
| 07:50 |
|
Dyrcona joined #evergreen |
| 08:39 |
pinesol_green |
Launchpad bug 690910 in Evergreen "Apache process spin out of control" [Undecided,Incomplete] https://launchpad.net/bugs/690910 |
| 08:39 |
Dyrcona |
JBoyer: Yes, I believe it is the Perl code that is ultimately responsible. |
| 08:39 |
Dyrcona |
Possibly, Perl itself. |
| 08:40 |
Dyrcona |
I need to do some more testing, but something changes from Perl 5.14 (maybe 5.18) to Perl 5.20 that make DBD::Pg and DBI behave "differently." |
| 08:41 |
Dyrcona |
Of course, this happened on Debian 7 with Perl 5.14 and Apache 2.2, so that wouldn't be the issue here. |
| 08:41 |
Dyrcona |
But, still, if someone did a search that tries to return every record.... |
| 08:48 |
|
mdriscoll joined #evergreen |
| 11:54 |
Dyrcona |
I tried that once, 15+ years ago....not going back. |
| 11:55 |
Dyrcona |
yppasswd opensrf .... |
| 11:55 |
Dyrcona |
Oops.. wrong window :) |
| 11:56 |
Dyrcona |
This'll be fun...testing a db upgrade in a file image on a USB drive.... |
| 11:57 |
Dyrcona |
<spongebob_depressed_announcer_voice>Two months later....</spongebob_depressed_announcer_voice> |
| 11:57 |
jeff |
hah. mostly-quiescent non-production database, ran a vacuum full analyze on it earlier today. shrunk by a few gigs, as you might expect for something that hadn't been vacuumed in a bit and had a bunch of data shuffled around within it. |
| 11:57 |
jeff |
the "hah" was because i just noticed that it grew by a megabyte since then. :-) |
| 11:58 |
Dyrcona |
Well, this'll be a pg_upgrade test with production data, freshly restored, so it'll be small as possible. |
| 11:58 |
Dyrcona |
I tried before with a 600GB image file. It was too smal. |
| 11:59 |
Dyrcona |
The missing 'l' is somehow appropriate. |
| 12:03 |
|
jvwoolf joined #evergreen |
| 15:00 |
rhamby |
which isn't to say I won't do it ...... |
| 15:05 |
kmlussier |
I missed a lot of these tweets the first time around. |
| 15:41 |
|
kipd joined #evergreen |
| 16:35 |
jeffdavis |
hm, I'm getting an error in the web client when I should get an opt-in dialog |
| 16:35 |
jeffdavis |
2.12 beta, still need to test on 2.12.0 |
| 17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:06 |
|
remingtron joined #evergreen |
| 20:42 |
|
jvwoolf joined #evergreen |
| 21:10 |
|
jihpringle_ joined #evergreen |
| 05:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 05:15 |
|
jonadab joined #evergreen |
| 06:07 |
|
jonadab joined #evergreen |
| 06:27 |
|
abowling joined #evergreen |
| 13:30 |
NawJo |
Thank you all for your help, thank you Dyrcona and Berick :) |
| 13:33 |
Dyrcona |
You can login now? |
| 13:36 |
NawJo |
Yes, yes :) |
| 13:37 |
NawJo |
I wrote the rtl stylesheets for web client days ago, and now I want to test them :) |
| 13:38 |
Dyrcona |
OK. Have fun and thanks for the stylesheets. |
| 13:38 |
berick |
NawJo++ |
| 13:39 |
NawJo |
:) thank you all |
| 16:16 |
Dyrcona |
echo...echo.. echo... My brain can spell, it's just my fingers that can't. |
| 16:17 |
berick |
just tried for grins, no dice. I also tried exporting TZ before the srfsh line |
| 16:17 |
* berick |
confirms it's in the osrf message w/ the original command |
| 16:18 |
gmcharlt |
berick: yep, the TZ should be passsed in |
| 16:18 |
gmcharlt |
and I've verified in the srfsh log on my test system that the tz is being passed in the request |
| 16:18 |
gmcharlt |
now checking the cstore side of things |
| 16:18 |
berick |
gmcharlt++ |
| 16:19 |
Dyrcona |
OK. I've never mangled the env with pipes much. |
| 16:19 |
Dyrcona |
It looks...well, weird and wrong. |
| 16:27 |
* berick |
nods |
| 16:35 |
|
BAM_ joined #evergreen |
| 16:39 |
|
kmlussier joined #evergreen |
| 16:40 |
Dyrcona |
I tested with circulation, so transactions. |
| 16:40 |
Dyrcona |
I don't think I thought to test it without a transaction. |
| 16:41 |
Dyrcona |
"I don't think I thought..." heh.... |
| 16:41 |
gmcharlt |
friends don't let friends do circulation transactions outside of transactions |
| 16:41 |
Dyrcona |
:) |
| 16:53 |
bshum |
Leading to a bad video |
| 16:53 |
bshum |
But, hey, fun! |
| 16:53 |
bshum |
:D |
| 17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:08 |
|
mmorgan joined #evergreen |
| 17:14 |
|
mmorgan left #evergreen |
| 17:29 |
|
jvwoolf left #evergreen |
| 21:41 |
bshum |
Oh special. |
| 21:41 |
bshum |
https://bugs.launchpad.net/ubuntu/+source/ejabberd/+bug/1659801 |
| 21:41 |
pinesol_green |
Launchpad bug 1659801 in ejabberd (Ubuntu) "apparmor rules block ejabberdctl" [Undecided,New] |
| 21:41 |
bshum |
Just came across this segmentation error on Ubuntu 16.04 dry run while trying to run through ejabberd user registration :\ |
| 21:41 |
bshum |
Ruined my asciinema recording, bah |
| 21:42 |
bshum |
Guess I'll have to try it all over again |
| 21:43 |
* bshum |
blows away his VM to test anew |
| 21:49 |
* bshum |
considers making the recording on Trusty instead |
| 21:50 |
bshum |
Or Debian... *shudders* |
| 23:05 |
Dyrcona |
I have not encountered that one, but I always start ejabberdctl with sudo. |
| 23:06 |
bshum |
I ran it as root |
| 23:06 |
bshum |
And got that error |
| 11:05 |
berick |
as to me they are the same thing |
| 11:05 |
bshum |
As long as bugs get worked on, I think that's the key goal :D |
| 11:06 |
berick |
very diplomatic ;) |
| 11:06 |
bshum |
gmcharlt: Speaking of, sorry I saw your question... but got distracted, lol. So uh, my answer is maybe |
| 11:06 |
bshum |
gmcharlt: I didn't get to play with it directly myself yet |
| 11:06 |
bshum |
But I'm always happy to test and merge stuff that people push my way |
| 11:07 |
kmlussier |
Yeah, if I were proposing anything, it's probably that bugs get worked on. :) I know core committers are busy, but one or two bugs a month seems reasonable to me. |
| 11:30 |
csharp |
gmcharlt: I'll take a look |
| 11:33 |
gmcharlt |
csharp: great! |
| 15:08 |
berick |
booting_up_the_thunderdome++ |
| 15:09 |
berick |
(it runs on windows 98) |
| 15:09 |
csharp |
https://www.youtube.com/watch?v=tajDxBaPBBM |
| 15:09 |
berick |
you've got mail! |
| 15:10 |
|
kmlussier joined #evergreen |
| 15:11 |
berick |
miker: another thought, assuming a non-hatch version of offline is viable, starting there lowers the barrier to entry for broader testing. |
| 15:12 |
miker |
it does, certainly. (sans printing stuff above) |
| 15:36 |
|
hbrennan joined #evergreen |
| 15:39 |
|
Jillianne joined #evergreen |
| 15:40 |
Dyrcona |
gmcharlt | csharp: https://bugs.launchpad.net/evergreen/+bug/1669868/comments/9 |
| 15:40 |
pinesol_green |
Launchpad bug 1669868 in Evergreen ""make check" failure" [High,Confirmed] |
| 15:40 |
Dyrcona |
I developed that on Ubuntu 16.04. I'll test on wheezy, jessie, and trusty next. |
| 15:41 |
gmcharlt |
Dyrcona: thanks |
| 15:48 |
Dyrcona |
Works for me on jessie. |
| 15:51 |
Dyrcona |
Works on wheezy. |
| 16:27 |
|
mmorgan joined #evergreen |
| 16:52 |
bshum |
Taco time :) See you guys later... |
| 17:00 |
Dyrcona |
I ..am.. outta here! |
| 17:00 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
| 17:09 |
|
mmorgan left #evergreen |
| 17:10 |
|
khuckins joined #evergreen |
| 17:11 |
* kmlussier |
heads out to get pizza. |
