Time |
Nick |
Message |
00:41 |
|
Mark__T joined #evergreen |
02:17 |
|
Callender_ joined #evergreen |
02:18 |
|
Callender_ joined #evergreen |
03:11 |
|
berick joined #evergreen |
03:18 |
|
berick_ joined #evergreen |
06:40 |
|
rlefaive joined #evergreen |
07:15 |
|
TARA joined #evergreen |
07:34 |
|
JBoyer joined #evergreen |
07:42 |
|
rjackson_isl joined #evergreen |
07:54 |
|
ericar joined #evergreen |
08:07 |
|
mrpeters joined #evergreen |
08:11 |
|
Dyrcona joined #evergreen |
08:40 |
|
mmorgan joined #evergreen |
08:42 |
JBoyer |
Are there any unapi/MVF experts about? (paging miker) |
08:43 |
miker |
JBoyer: 'sup, sir |
08:43 |
JBoyer |
I'm trying to figure out how to make use of some additions that ESI built for CenTec and their selfchecks. |
08:44 |
JBoyer |
Basically how to set up ISBNs as MVF values to get this URL to return results on our server: http://dev203.esilibrary.com/opac/extras/unapi?id=tag:open-ils.org,2014-09-10:U2@acp/ACQ140%7Bacn,bre,mra%7D/-/0/barcode&format=xml |
08:45 |
|
mmorgan joined #evergreen |
08:47 |
JBoyer |
Currently all I get is "Sorry, xml isn't a valid format for this record" and changing the format to marcxml gives a ISE. |
08:48 |
miker |
JBoyer: you want to use U2 urls, is that right? |
08:49 |
JBoyer |
I suppose, if that's what CenTec users need. |
08:49 |
JBoyer |
I've never looked at unapi, so I'm a bit in the dark. :-/ |
08:50 |
miker |
I don't think I'm following yet. the dev server url uses a barcode search ... but you mention ISBNs |
08:50 |
JBoyer |
Hang on |
08:55 |
jeff |
Is the objective to take an item barcode and receive an ISBN, for the CenTec self checkout kiosk to display a cover image or novelist query or something? |
08:55 |
JBoyer |
I think it's for some kind of loyalty program / gamification thing. |
08:56 |
jeff |
(based presumably on an item barcode from msg64_summary_datatype being set to barcode, presumably? |
08:56 |
jeff |
presumably-presumably) |
08:57 |
JBoyer |
jeff: from what I can tell they want to use an unapi call to our catalog in addition to SIP for the checkouts. |
09:00 |
Dyrcona |
So, thanks to the fun that I had with Ubuntu 14.04's old package of Node.js yesterday, I'm going to try build a 16.04/xenial vm this week or weekend. |
09:01 |
Dyrcona |
I'd like to merge the branches into master at/by the conference hackfest. |
09:01 |
Dyrcona |
Official release of 16.04 is scheduled for April 21. |
09:02 |
Dyrcona |
And, hey. The Node issue still happens on 14.04. |
09:03 |
Dyrcona |
It didn't happen installing bower in the prerequisites, but it happened while doing the web staff client steps. |
09:03 |
JBoyer |
Dyrcona, yeah, I've been disappointed in how old some packages on 14.04 are. Apparently "consistency" or "stability" or something is more important than whether or not the contents actually function at all. |
09:03 |
Dyrcona |
JBoyer: That, and I wonder if anyone actually maintains some of these packages, at least for older releases. |
09:04 |
Dyrcona |
I know there's a general rule about not upgrading major versions, but still, if the package is broken, it should be upgraded. |
09:04 |
JBoyer |
I can only hope the answer is no, because the alternative is essentially malicious laziness. |
09:06 |
Dyrcona |
Well, time is limited and the focus could be on the upcoming release, if you want to give them the benefit of the doubt. |
09:06 |
Dyrcona |
Linux From Scratch is looking more attractive by the day. :p |
09:07 |
Dyrcona |
Given the situation, I may just try to build that xenial vm today. |
09:11 |
* Dyrcona |
wonders if I should switch from kvm to lxd. |
09:14 |
miker |
for the room, the CenTec stuff wants unapi2 to pull marcxml (for isbn and 300) and MRA (for item type) by copy barcode, which landed in 2.10 instead of the originally targetted 2.6 or 2.7 |
09:16 |
* Dyrcona |
wonders if we should recommend that people not install the web staff client stuff on Ubuntu 14.04? |
09:18 |
JBoyer |
miker++ # for the explanation and informing the logs. |
09:19 |
JBoyer |
Dyrcona I thought they were rolling back the gzip thing so it should work again? Surely they are well aware that "uh, install from source, pls" isn't a viable mainstream fix. |
09:19 |
JBoyer |
At least for a while. |
09:19 |
Dyrcona |
JBoyer: They did, and it just fails at a different point, now. |
09:19 |
Dyrcona |
Same symptoms. |
09:20 |
JBoyer |
Oh. :-/ |
09:20 |
Dyrcona |
Though, I might have had something cached locally. |
09:20 |
Dyrcona |
I suppose I could go through building a whole new VM to find out for sure. |
09:23 |
Dyrcona |
BTW, there is supposed to be a developers' meeting at 3:00PM EDT today. |
09:23 |
Dyrcona |
Are we going to skip this one? |
09:26 |
Dyrcona |
At least the creation of the VM is going faster today. |
09:27 |
csharp |
@praise The VM Creator |
09:27 |
* pinesol_green |
In days of old, it was prophesied that a hero would come and restore karmic balance to #evergreen. The VM Creator is that hero. |
09:28 |
Dyrcona |
heh |
09:29 |
Dyrcona |
@praise vmbuilder |
09:29 |
* pinesol_green |
In days of old, it was prophesied that a hero would come and restore karmic balance to #evergreen. vmbuilder is that hero. |
09:29 |
* csharp |
glares at gnarly SQL created by a bad reports template |
09:29 |
Dyrcona |
pinesol_green: You need to reseed your prng. |
09:29 |
pinesol_green |
Dyrcona: It reads like a Nigerian 419 scam, but I think it is a sincere question sent to the wrong list. |
09:29 |
pinesol_green |
Dyrcona: I am only a bot, please don't think I'm intelligent :) |
09:30 |
* Dyrcona |
now has a new gamertag: Nigerian PRNG. :) |
09:31 |
Dyrcona |
@praise The Nigerian Prince |
09:31 |
* pinesol_green |
Shall I compare The Nigerian Prince to a summer's day? The Nigerian Prince is more lovely and more temperate. |
09:32 |
csharp |
pinesol_green: nobody thinks you're intelligent - jeez! |
09:32 |
pinesol_green |
csharp: I am only a bot, please don't think I'm intelligent :) |
09:32 |
pinesol_green |
csharp: Thank you csharp! But our princess is in another castle! |
09:32 |
Dyrcona |
VM is ready, I'll be back in about half an hour to say yay or nay if the test works. |
09:36 |
|
maryj joined #evergreen |
09:36 |
|
yboston joined #evergreen |
09:47 |
|
kmlussier joined #evergreen |
09:51 |
kmlussier |
I'll repost the question I asked yesterday after everyone went home for the day. Will people be available for today's dev meeting? If so, I'll get an agenda ready and send out a meeting reminder. |
09:54 |
Dyrcona |
I'll be available, but I'm not sure what we'd need to talk about. I suppose I could talk about Node.js issues on Ubuntu 14.04, if they persist. |
09:56 |
kmlussier |
We could also talk about plans for the conference hackfest |
09:57 |
Dyrcona |
Hackfest day is also a monthly release day. |
09:58 |
Dyrcona |
I signed up for the Red Hat tour that afternoon, but I may take my name off the list. |
09:58 |
Dyrcona |
On Node.js: ubuntu-trusty-developer prereqs install OK, now. |
09:59 |
Dyrcona |
I'm going to build evergreen manually to see where in the web staff client steps things blow up if at all. |
09:59 |
csharp |
Bmagic++ # games |
10:03 |
Bmagic |
awwww shucks |
10:07 |
|
jwoodard joined #evergreen |
10:11 |
|
mllewellyn joined #evergreen |
10:16 |
Dyrcona |
On Node.js: npm install blows up. |
10:16 |
Dyrcona |
npm http 200 https://registry.npmjs.org/lodash |
10:16 |
Dyrcona |
npm ERR! SyntaxError: Unexpected token |
10:16 |
Dyrcona |
npm ERR! �Y[o�6�+��X��T�ڭ�!���a��r��s$C�S�A���8☃�4N<π����D�����G�≠���ː°U=ﲃ켁→≠*� |
10:16 |
Dyrcona |
�Z" |
10:17 |
Dyrcona |
So, looks like Node.js will need to be installed from source or from alternate packages on Ubuntu 14.04. |
10:19 |
|
rlefaive joined #evergreen |
10:22 |
rlefaive |
just want to say thanks to kmlussier for the awesome summary of keyword search issues http://markmail.org/message/5ymsy6vb6iyoht2j |
10:35 |
|
rlefaive joined #evergreen |
10:42 |
kmlussier |
rlefaive: Thanks! I'm glad you found it helpful. |
10:42 |
Dyrcona |
kmlussier++ |
10:42 |
Dyrcona |
So, I think we might to adjust the README to suggest installing Node.js from source on Ubuntu 14.04. |
10:42 |
Dyrcona |
I'll see if I can find a version that works. |
10:43 |
rlefaive |
kmlussier: was this one of the reasons for the recent discussions of “how should we do search” in EG? |
10:43 |
Dyrcona |
But, that may have to wait until later. |
10:46 |
kmlussier |
rlefaive: No, not those issues specifically, although we still haven't addressed them locally. I think we mostly raised the discussion because, before we build more features on top of search, which is something MassLNC wants to do, we think it's worthwhile to take a step back to take a look at the underlying infrastructure. |
10:46 |
* kmlussier |
is actually working today on pulling something together from those focus group discussions. |
10:46 |
rlefaive |
kmlussier++ |
10:47 |
rlefaive |
Do you know if anyone has hacked up a solr search interface? |
10:51 |
Dyrcona |
Someone has talked about it and/or lucene, but I don't know if it went beyond talk. |
10:51 |
rlefaive |
sweet, thanks Dyrcona. |
10:52 |
kmlussier |
rlefaive: jeff has worked on something with ElasticSearch. |
10:53 |
|
abowling joined #evergreen |
10:54 |
kmlussier |
rlefaive: artunit also once sent me something on an experiment with Solr that happened a long time ago. |
10:54 |
* kmlussier |
tries to find where she posted that information. |
10:55 |
kmlussier |
Actually, I'll have to look later. |
10:55 |
rlefaive |
kmlussier thanks for your help already! I can try to dig that up. |
10:55 |
jeff |
edoceo had a solr experiment that he demonstrated a while back also. |
10:56 |
* rlefaive |
wonders if she can make a demo before the conference in 2 weeks. |
10:57 |
jeff |
i believe http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/solr_sync was cited as being the evergreen trigger side of the artunit solr bento box search. |
10:58 |
rlefaive |
thanks Jeff! I didn’t expect to see Discovery Garden coming up - have they been involved in the EG community since 2012? |
10:58 |
jeff |
kmlussier: did you still have a document from artunit regarding solr that you were going to add to the wiki? |
10:59 |
kmlussier |
jeff: I added it somewhere. I don't know if it's on the wiki or in a Google doc. I'll have to look for it later. |
10:59 |
jeff |
rlefaive: Discovery Garden isn't a noun that I recognize... ah, islandora? |
10:59 |
rlefaive |
jeff: yes. *waves upei flag* |
11:00 |
jeff |
This is what we're using for pulling records from Evergreen and inserting them into an Elasticsearch cluster: https://github.com/tadl/marc-indexing-for-es |
11:01 |
jeff |
and https://catalog.apps.tadl.org/ gets promoted to being catalog.tadl.org tomorrow. |
11:02 |
jeff |
(technically, "gets promoted to handling the bulk of requests to catalog.tadl.org" tomorrow) |
11:02 |
berick |
for ES 2.x, I had to make the following change to jeff's code: https://github.com/berick/marc-indexing-for-es/commit/db98f7571f5e595caff042d7ffae73c998d5acdd |
11:02 |
berick |
if anyone is going that route |
11:03 |
jeff |
berick++ -- we're using 1.7 still, but I've been chewing through the "breaking changes" docs for 2.3 |
11:03 |
rlefaive |
beric++ jeff++ |
11:04 |
berick |
jeff: not sure if this is a 2.x thing, but I also had to tweak some of the queries for nested data. E.g. https://github.com/berick/marc-indexing-for-es/commit/665ff895a064ce64e81be5f3809e3f3734e94b4b |
11:08 |
jeff |
berick: ah! yep, I likely didn't update the rest of the examples when I added https://github.com/tadl/marc-indexing-for-es/commit/5ae1b4380fecef1fb40f9eb2f79753019ba77053 |
11:08 |
jeff |
(heh. that test is pretty... specific to us.) |
11:09 |
berick |
jeff: oh, cool, glad I'm on the right track. |
11:10 |
berick |
jeff: whoa, you're moving to catalog.apps.tadl.org as your main catalog? |
11:11 |
jeff |
not until tomorrow. :-) |
11:11 |
berick |
jeff: does the patron login go back to the tpac or did you all implement a new/mobile my-account UI? |
11:11 |
jeff |
but yeah, it's been the in-building interface for a few months. |
11:12 |
berick |
nice |
11:12 |
|
montgoc1 joined #evergreen |
11:12 |
jeff |
berick: new UI. we even added support for lists, since we knew some folk would miss it and didn't want that to be the number one feedback. |
11:13 |
jeff |
i should throw up an instance backed by a sample db. |
11:13 |
berick |
jeff++ |
11:13 |
|
Christineb joined #evergreen |
11:13 |
berick |
look forward to hearing how it goes |
11:27 |
|
bmills joined #evergreen |
11:33 |
mrpeters |
jeff++ that is AWESOME |
11:50 |
|
sandbergja joined #evergreen |
11:56 |
gmcharlt |
http://libmail.georgialibraries.org/pipermail/open-ils-general/2016-April/012920.html |
11:58 |
kmlussier |
gmcharlt++ |
11:59 |
kmlussier |
@later tell rlefaive I found the Solr document - https://drive.google.com/file/d/0B74gDMUDwDXqX2Nsa3ItLWJIZVE/view?usp=sharing |
11:59 |
pinesol_green |
kmlussier: The operation succeeded. |
12:00 |
rhamby |
gmcarlt++ |
12:00 |
rhamby |
gmcharlt++ even |
12:01 |
|
rlefaive joined #evergreen |
12:26 |
|
krvmga joined #evergreen |
12:32 |
|
mmorgan joined #evergreen |
12:36 |
|
bwicksall joined #evergreen |
12:40 |
|
brahmina joined #evergreen |
12:59 |
|
jihpringle joined #evergreen |
13:11 |
krvmga |
advice needed: i have been working on opac customizations for our academics |
13:11 |
krvmga |
this has led me in the direction of "modularizing" parts of the opac as it exists now - making chunks that can be plugged in wherever needed |
13:12 |
krvmga |
i'm feeling pulled in the direction to do this for the whole public opac |
13:12 |
krvmga |
make everything into building blocks that can be assembled as wanted/needed |
13:12 |
krvmga |
kmlussier suggested i put something about this on launchpad |
13:12 |
Dyrcona |
krvmga: Sounds like a good idea and a lot of work. |
13:12 |
krvmga |
i'm fine with that but where would i put it |
13:13 |
krvmga |
Dyrcona: /me is not afraid of hard work. :) |
13:13 |
Dyrcona |
krvmga: On Evergreen bugs with priority set to wishlist. |
13:13 |
krvmga |
wait - that "/me" didn't work right lol |
13:13 |
krvmga |
Dyrcona: okay, that's what i'll do. thanks! |
13:13 |
krvmga |
Dyrcona++ |
13:13 |
Dyrcona |
The /me has to be the very first thing on the line. |
13:14 |
krvmga |
:) |
13:14 |
Dyrcona |
krvmga++ |
13:14 |
Dyrcona |
krvmga: If you worked a detailed design document that could be shared under blueprints or whatever, but that doesn't get much use at the moment. |
13:15 |
Dyrcona |
krvmga: You can link them to bugs, IIRC. |
13:21 |
krvmga |
Dyrcona: i'm going to put together something that's more than a sentence or two and then put it up. |
13:21 |
krvmga |
i'm also thinking to stop by the developer meeting this afternoon. do you think that's worthwhile? |
13:21 |
Dyrcona |
krvmga: OK. For the blueprints, I was thinking of something that's a few pages or more. |
13:22 |
Dyrcona |
Could be. We have some things on the agenda. |
13:23 |
krvmga |
maybe i'll wait then, till i've got stuff put together |
13:24 |
Dyrcona |
krvmga: No harm in opening a bug and fleshing it out later. |
13:25 |
krvmga |
Dyrcona: right. i'll do that. |
13:34 |
krvmga |
https://bugs.launchpad.net/evergreen/+bug/1566995 |
13:34 |
pinesol_green |
Launchpad bug 1566995 in Evergreen "Build a component-based TT OPAC" [Undecided,New] |
14:01 |
* Dyrcona |
thinks he just found the sweet spot for doing pingest on his development database. |
14:20 |
|
kmlussier joined #evergreen |
14:30 |
kmlussier |
Heads up. The dev meeting begins in about 30 minutes. |
14:31 |
kmlussier |
Feel free to volunteer at any time if you want to run the meeting! :) |
14:37 |
|
mmorgan joined #evergreen |
14:38 |
|
mnsri joined #evergreen |
14:43 |
jeff |
kmlussier: if nobody jumps in before I return around 3:15, sure! ;-) |
14:44 |
kmlussier |
jeff: Thanks! But hopefully somebody who will be here at 3 will volunteer. :) |
14:45 |
jeff |
hopefully. but in the meantime it was a good way to casually mention that i wouldn't be here until after the start. :-) |
14:47 |
|
gsams joined #evergreen |
14:49 |
|
b_bonner joined #evergreen |
14:49 |
|
rashma_away joined #evergreen |
14:49 |
|
mnsri_away joined #evergreen |
14:51 |
|
mtcarlson joined #evergreen |
14:53 |
|
bmills joined #evergreen |
14:58 |
* gmcharlt |
can run the meeting |
14:58 |
berick |
gmcharlt++ |
14:59 |
Dyrcona |
gmcharlt++ |
15:00 |
|
jlitrell joined #evergreen |
15:00 |
gmcharlt |
#startmeeting Evergreen Development Meeting, 6 April 2016 |
15:00 |
pinesol_green |
Meeting started Wed Apr 6 15:00:37 2016 US/Eastern. The chair is gmcharlt. Information about MeetBot at http://wiki.debian.org/MeetBot. |
15:00 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
15:00 |
pinesol_green |
The meeting name has been set to 'evergreen_development_meeting__6_april_2016' |
15:00 |
gmcharlt |
#info Agenda is http://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2016-03-06 |
15:00 |
gmcharlt |
#topic Introductions |
15:01 |
gmcharlt |
#info Galen Charlton, ESI |
15:01 |
phasefx |
#info Jason Etheridge, ESI |
15:01 |
jeffdavis |
#info Jeff Davis, Sitka |
15:01 |
kmlussier |
gmcharlt++ |
15:01 |
kmlussier |
#info Kathy Lussier, MassLNC |
15:01 |
rhamby |
#info Rogan Hamby, ESI |
15:01 |
Dyrcona |
#info Jason Stephenson, MVLC |
15:01 |
JBoyer |
#info Jason Boyer, ISL |
15:02 |
|
gsams joined #evergreen |
15:02 |
berick |
#info berick Bill Erickson, KCLS |
15:02 |
brahmina |
#info Brahmina Burgess, Sitka |
15:02 |
dbwells |
#info dbwells = Dan Wells, Hekman Library (Calvin College) |
15:02 |
remingtron |
#info remingtron = Remington Steed, Hekman Library (Calvin College) |
15:03 |
jeffdavis |
brahmina is new to Sitka, she is replacing Liam who has moved on to another position |
15:03 |
Dyrcona |
Welcome, brahmina! |
15:03 |
kmlussier |
Welcome brahmina! |
15:03 |
gmcharlt |
welcome, brahmina! |
15:03 |
rhamby |
Welcome brahmina! |
15:03 |
brahmina |
Thanks! :) |
15:03 |
berick |
welcome brahmina; give our regards to Liam |
15:03 |
gmcharlt |
#topic OpenSRF release |
15:04 |
gmcharlt |
we have some patches queued up for both a 1.5.0 and a 1.4.x release |
15:04 |
gmcharlt |
I'll try to cut them before the Evergreen Conference, but may well end up cutting them AT the Evergreen Conference |
15:04 |
gmcharlt |
otherwise, not much to say unless folks have questions |
15:05 |
miker |
#info miker Mike RYlander, ESI |
15:06 |
gmcharlt |
OK, moving on |
15:06 |
gmcharlt |
#topic Evergreen release |
15:06 |
|
DPearl joined #evergreen |
15:06 |
gmcharlt |
and we had a few releases last month: 2.8.7, 2.9.3, 2.10.0, and 2.10.1 |
15:06 |
gmcharlt |
and if I'm remembering the discussion correctly, 2.8.x will hit EOL after the release of 2.8.8 this month |
15:07 |
gmcharlt |
any questions |
15:07 |
gmcharlt |
? |
15:08 |
kmlussier |
Are the next point releases still happening as scheduled on hackfest day? |
15:08 |
kmlussier |
Or should they be rescheduled? |
15:08 |
JBoyer |
That seems like a lot happening on the same day. |
15:08 |
Dyrcona |
I'm OK with doing 2.9.4 at the hackfest. |
15:08 |
gmcharlt |
and ditto for 2.10.2 |
15:09 |
Dyrcona |
berick? |
15:10 |
berick |
works for me |
15:10 |
gmcharlt |
OK, moving on then |
15:10 |
gmcharlt |
#topic Conference hackfest ideas page |
15:11 |
gmcharlt |
#link http://wiki.evergreen-ils.org/doku.php?id=dev:hackfest:eg2016 |
15:11 |
gmcharlt |
please add your ideas, or else we will ALL be perching on berick's shoulder as he works on the Angular 1.5 patches |
15:11 |
gmcharlt |
;) |
15:11 |
berick |
sounds like a super hackfest ;) |
15:12 |
gmcharlt |
moving on |
15:12 |
gmcharlt |
#topic Call for Release Manager for 2.11 |
15:12 |
gmcharlt |
#info RM nominations and self-nominations accepted through 15 April |
15:12 |
gmcharlt |
#info Vote to be held in #evergreen week of 18 April |
15:13 |
gmcharlt |
questions? |
15:13 |
jeffdavis |
I'm just curious to see who volunteers, which isn't really a question :) |
15:13 |
* Dyrcona |
nominates jeffdavis. |
15:13 |
kmlussier |
Feel free to speak up now! :) |
15:14 |
* jeffdavis |
shakes fist at Dyrcona |
15:14 |
krvmga |
lol |
15:14 |
Dyrcona |
:) |
15:15 |
gmcharlt |
we're calling for nominations...not inescapable mandates! ;) |
15:15 |
gmcharlt |
anyway, moving on |
15:15 |
gmcharlt |
#topic Follow-up on search discussion |
15:15 |
kmlussier |
I don't have much on that. I had hoped to be done with my work by meeting time. :) |
15:16 |
kmlussier |
But I'll be sharing more info on the dev list by the end of the week. As you know, we did some focus group discussions in IRC to get feedback on where the community wants to see search going. |
15:16 |
kmlussier |
I'm compiling that information now and will be sharing it with the community to make sure I didn't misunderstand anything. |
15:17 |
kmlussier |
My next step was to put together a survey based on those discussion to help us prioritize the ideas that were raised. I'll share it with all of you first for feedback before sending it out to the larger community. |
15:17 |
kmlussier |
Maybe we can discuss it further at the hackfest to maybe identify some next steps. |
15:17 |
kmlussier |
That's all I have for now. |
15:18 |
gmcharlt |
thanks, kmlussier |
15:19 |
gmcharlt |
#topic npm is failing to install Node.js packages on Ubuntu 14.04 |
15:19 |
gmcharlt |
er, is there a bug filed for this? |
15:19 |
Dyrcona |
As previously mentioned in IRC, I've been failing to get the web staff client working on Ubuntu 14.04 this week. |
15:19 |
Dyrcona |
Not a Launchpad bug, but that could be an action item for me if you like. |
15:19 |
gmcharlt |
please |
15:20 |
Dyrcona |
The problems appear to be related to this closed github issue. |
15:20 |
Dyrcona |
#link : https://github.com/npm/npm/issues/12196#issuecomment-205855393 |
15:20 |
Dyrcona |
Can I action item myself, or does the chair have to do that? |
15:21 |
gmcharlt |
#action Dyrconra to write up bug report for nodejs installation item on Ubuntu 14.04 |
15:21 |
gmcharlt |
er |
15:21 |
Dyrcona |
Close enough. :) |
15:21 |
gmcharlt |
heh |
15:21 |
Dyrcona |
I'll put this in the bug report, but my idea is to update the README to explain how to install Node.js from source, and remove the prerequisites from Makefile.install. |
15:22 |
gmcharlt |
https://github.com/nodesource/distributions also looks interesting |
15:22 |
Dyrcona |
So that's all I've got for now. |
15:22 |
gmcharlt |
#topic Change supported Ubuntu distros |
15:23 |
gmcharlt |
i.e., propose to drop supported for 12.04 and add it for 16.04 |
15:23 |
gmcharlt |
I see we have bug 1551084 already |
15:23 |
bshum |
Historically, Ubuntu support has always been current LTS and previous. So when 16.04 arrives on the scenes, 12.04 should go away. Assuming 16.04 isn't going to completely upend everything... |
15:23 |
pinesol_green |
Launchpad bug 1551084 in Evergreen "Add Evergreen support for Ubuntu 16.04 Xenial Xerus" [Wishlist,Triaged] https://launchpad.net/bugs/1551084 |
15:24 |
bshum |
https://bugs.launchpad.net/opensrf/+bug/1551090 for OpenSRF too |
15:24 |
pinesol_green |
Launchpad bug 1551090 in OpenSRF "Add OpenSRF support for Ubuntu 16.04 Xenial Xerus" [Wishlist,Triaged] |
15:24 |
Dyrcona |
Yeah, so I'm volunteering to work on those branches between now and the conference. |
15:24 |
gmcharlt |
cool |
15:25 |
Dyrcona |
16.04 release is scheduled for 4/21, day two (one?) of the confernce. |
15:25 |
gmcharlt |
#action Dyrcona will work on Xenial Xerus Evergreen and OpenSRF support between now and the EG conference |
15:25 |
Dyrcona |
I plan to make the changes in master only, unless the consensus is to backport. |
15:25 |
JBoyer |
Seems reasonable. |
15:26 |
bshum |
I'd like to suggest also that we only target this change for Ubuntu towards the next major series for each. Backporting to older versions may not be immediately necessary since 12.04 will still be "supported" till 2017 (through the end of planned life for 2.9 and 2.10 too, probably) |
15:26 |
bshum |
What Dyrcona said :) |
15:26 |
gmcharlt |
backporting Xenial support to rel_2_10 would be a niceness |
15:26 |
gmcharlt |
though I don't care muchly either way |
15:27 |
gmcharlt |
as far as 12.04 goes, one thing to mention is that it ships Pg 9.1 by default |
15:27 |
Dyrcona |
Right and that leads into a later topic. :) |
15:27 |
gmcharlt |
anything else to say about Ubuntu? |
15:28 |
Dyrcona |
Not at the moment. |
15:28 |
gmcharlt |
#topic Dropping Debian Squeeze support |
15:28 |
gmcharlt |
#link https://bugs.launchpad.net/evergreen/+bug/1559121 |
15:28 |
pinesol_green |
Launchpad bug 1559121 in OpenSRF 2.5 "Drop Debian Squeeze support" [Medium,New] |
15:28 |
bshum |
+1 |
15:29 |
|
jihpringle_ joined #evergreen |
15:29 |
Dyrcona |
what bshum said. :) |
15:32 |
gmcharlt |
#info We are all agreed that nobody expect the Spanish Inquisition!!! (er, that Debian Squeeze support is to be dropped) |
15:32 |
gmcharlt |
#topic Minimum Pg version to support |
15:32 |
gmcharlt |
#info Pg 9.1 support is deprecated as of EG 2.10.x, and will be removed in 2.11.0 |
15:32 |
gmcharlt |
so, that leaves the question of what minimum Pg version we wish to require |
15:33 |
miker |
9.2 support ends slightly before the EOL for 2.11 |
15:33 |
miker |
I think |
15:34 |
miker |
(just for a data point) |
15:34 |
Dyrcona |
9.3 ships with the at the moment current supported distros. |
15:34 |
Dyrcona |
another data point. |
15:34 |
miker |
9.6 it is, then! ;) |
15:34 |
jeffdavis |
Is there any reason not to move to 9.3? |
15:34 |
Dyrcona |
:) |
15:35 |
* Dyrcona |
just hopes it works on 9.5 for xenial. |
15:35 |
bshum |
Doesn't Jessie install on PG 9.4 ? |
15:35 |
miker |
jeffdavis: no, and that would be my preferred minimum |
15:35 |
gmcharlt |
bshum: jessie ships 9.4 |
15:35 |
Dyrcona |
Yeah, I'd prefer 9.3 also. |
15:35 |
bshum |
gmcharlt: Gotcha, right. |
15:35 |
miker |
prefer 9.3 to 9.2, I mean |
15:36 |
JBoyer |
Is 9.2 the default install on any supported OS? I don't know much about the redhat related distros. |
15:36 |
bshum |
It wasn't as far as I could remember. |
15:36 |
JBoyer |
(Also +1 to 9.3 ) |
15:36 |
kmlussier |
+1 to 9.3 |
15:37 |
gmcharlt |
JBoyer: I don't know what RHEL-likes ship by default, but they do have access to http://yum.postgresql.org/ |
15:37 |
miker |
related to absolute minimums, I have another "supported PG question" ... if/when features of a more modern PG allow us to do Great Things(tm), what is the general opinion on saying "for 3.0 (say) you have to start with PG 9.7 or later" and skipping the ability to use older PGs? |
15:38 |
miker |
(and, as a cousin to yum.postgresql.org, there's the PGDG apt repo) |
15:38 |
jeff |
miker: Great Things are worth ensuring recent PostgreSQL version, IMO. |
15:38 |
JBoyer |
gmcharlt, miker: good points. Certainly beats git clone... |
15:39 |
miker |
jeff: that was the rule back in the wild west days, but I don't think we've codified that in the new order |
15:39 |
kmlussier |
I'm in favor of high minimums to do great things, especially if supporting lower versions is holding as back, but I'm also not a sys admin who needs to worry about keeping up to date. |
15:39 |
Dyrcona |
I think it is OK to do that for future releases, as long as there is no attempt to backport the new features so enabled. |
15:39 |
kmlussier |
holding *us* back. |
15:39 |
miker |
kmlussier: fwiw, it's already holding us back to a degree ... :( |
15:39 |
gmcharlt |
miker: to toss out a suggested rule of thumb: when we want to bump up minimum required Pg, do so soon enough so that we can announce a deprecation the major release before we want to jump to a newer Pg |
15:39 |
kmlussier |
miker: yeah |
15:39 |
bshum |
"New is always better"? |
15:40 |
miker |
*after the new special tweaks have been identified |
15:41 |
miker |
gmcharlt: my thought was "only make major jumps when the first number changes, or PG drops support near a second-number release" |
15:41 |
gmcharlt |
and given some of Pg's brown bags the past couple years... there is reason not to be too quick to jump |
15:41 |
miker |
that sentence may not have enough context... |
15:41 |
Dyrcona |
miker: Wasn't that one of the old rules for versioning? |
15:42 |
Dyrcona |
"Bump the major version if a Pg version requirement goes up?" |
15:42 |
miker |
Dyrcona: indeed it was. maybe we need to just go through them and make sure they either make sense and are officially "adopted" or cut them |
15:43 |
jeffdavis |
Is this something we need a general rule about, or can/should it be something decided on a case by case basis? |
15:43 |
Dyrcona |
Probably cut them at this point. |
15:43 |
kmlussier |
Are those rules posted somewhere? |
15:43 |
miker |
jeffdavis: well, it helps with planning big changes ... where they'll land |
15:44 |
gmcharlt |
I'm inclined to consider it on a case-by-base basis as new Pg features warrant bumping up; my main other concern is just allowing adequate notice to EG sysadmins |
15:44 |
miker |
but it doesn't have to be The Law, things like that can be "official guidelines" |
15:45 |
kmlussier |
Yes, so if we decided to go with 9.3 as a minimum for 2.11, the notice should probably go out now to give adequate notice. |
15:45 |
gmcharlt |
I'm much less concerned about where EG version numbers fit into the schema (beyond the principle that maintenance releases should never have the required dependencies change underneath them absent extreme provocation) |
15:45 |
gmcharlt |
to step back a bit |
15:45 |
gmcharlt |
I think we have a consensus to require Pg 9.3 as the minimum for Evergreen 2.11 |
15:45 |
* Dyrcona |
pretty much agrees with gmcharlt and miker. |
15:46 |
bshum |
PG 9.3 buys us a year to decide what happens next time 'round |
15:46 |
gmcharlt |
any disagreement with that (i.e., somebody who wants to aim for 9.4 or 9.5)? |
15:46 |
bshum |
Well more than a year anyways |
15:46 |
bshum |
Plus I feel like there are already lots of us on PG 9.3 or better |
15:46 |
bshum |
So it should be "well tested" |
15:46 |
miker |
9.3 FTW |
15:47 |
gmcharlt |
going once... |
15:47 |
jeffdavis |
FWIW, looks like CentOS 6 (EOL 2020) comes with PG8.4, and CentOS 7 (EOL 2024) comes with PG9.2; not sure if major PG version advances happen in minor CentOS releases |
15:47 |
jeffdavis |
that's based on a quick look, we don't use CentOS |
15:47 |
gmcharlt |
going twice... |
15:47 |
jeffdavis |
I don't think it's worth maintaining old PG versions for that long of a support cycle though, so +1 to 9.3 |
15:47 |
miker |
berick: you're using PGDG, yes? |
15:48 |
Dyrcona |
jeffdavis: And that's pretty much why we discourage the use of CenOS for Evergreen. |
15:48 |
miker |
oh, you're off RH, nm |
15:48 |
dbs |
Most PostgreSQL people discourage the use of RedHat/CentOS packages anywya |
15:48 |
berick |
miker: not sure, actually. maybe source. either way +1 to 9.3 |
15:48 |
gmcharlt |
dbs: in favor of source or yum.pg.org? |
15:49 |
dbs |
yum |
15:49 |
gmcharlt |
OK |
15:49 |
gmcharlt |
so, I think I'll call it |
15:49 |
gmcharlt |
#agreed PostgreSQL 9.3 will be the minimum required version for Evergreen 2.11 |
15:49 |
berick |
(we're upgrading to 2.7 this weekend. 2.11 is a distant idea ATM). |
15:49 |
gmcharlt |
#action gmcharlt will send an email to the mailing lists announcing the Pg dependency change |
15:50 |
kmlussier |
berick: Wow! |
15:51 |
berick |
kmlussier: gettin' there... |
15:52 |
dbwells |
berick: from where you started, 2.7 sounds like a pretty major accomplishment, good job! |
15:53 |
berick |
thanks, dbwells |
15:53 |
Dyrcona |
Did we talk about sqitch? Do we need to? |
15:53 |
kmlussier |
It was an outstanding action item from the last meeting. |
15:54 |
berick |
the sqitch branch is ready for wider testing. |
15:54 |
gmcharlt |
I can make some time between now and the EG conference to test |
15:54 |
berick |
if nothing else, it would be great if someone else got a feel for how it works |
15:54 |
Dyrcona |
I should see what it's about, but I have enough action items already. :) |
15:54 |
berick |
so I'm not stabbing too long in the dark. i only have my own experiences |
15:55 |
gmcharlt |
but a question, berick: how much of a pain for you if we merge pull requests that touch the schema? |
15:55 |
gmcharlt |
"will it be" |
15:55 |
berick |
gmcharlt: I have to cross-port each Pg/upgrade/* file. Not a huge pain, but each change does cause work |
15:56 |
gmcharlt |
berick: shall we set the EG conference as a date for the merge? |
15:56 |
miker |
gmcharlt: have we decided it's a done deal? |
15:56 |
berick |
miker: that's kind of my question too |
15:56 |
gmcharlt |
well, that would depend on testing, ultimately |
15:57 |
berick |
gmcharlt: right |
15:57 |
gmcharlt |
I think to rephrase: assuming that we end up /agreeing/ to run with sqitch, the conference would be a good time to make the switch |
15:57 |
jeff |
we usually have a dev meeting at the conf -- if enough people have tested and gotten a feel for squitch in general we could make a merge/no-merge call then? |
15:58 |
miker |
I do a good bit of db mangling ... and I won't have time to really dig in before the conf. I'm certainly not The Decider, but I'd like to hear the pitch (I know I missed one at the hack-a-way ... no way I could have made it there, though) |
15:58 |
berick |
i'm happy to review, discuss, etc at the conf. |
15:58 |
bshum |
It's a cool pitch. I like the concept, just have to see it in practice more. |
15:59 |
bshum |
Well, work with it in practice I mean |
15:59 |
kmlussier |
Should we hold off on merging code with schema changes until after the conference then? |
15:59 |
berick |
kmlussier: i'd vote no on that. i'd rather not disrupt the flow |
16:00 |
jeff |
that's a long time to go without schema changes (though, ever-shorter as the conf nears). since berick sounds okay with cross-porting... :-) |
16:00 |
|
rlefaive joined #evergreen |
16:00 |
Dyrcona |
Well, I'd like to learn more if means changing how upgrade scripts are written or if there are extra steps required. |
16:00 |
gmcharlt |
kmlussier: berick: agreed; we've got some stuff in the queue that I'd hate to see wait to be merged indefinteily |
16:01 |
berick |
I'm OK x-porting if there is motion toward a decision either way |
16:02 |
jeff |
berick: mind being verbose and calling attention to the next cross-port you do, for purposes of practical example? |
16:02 |
berick |
jeff: sure. I also have such an example in the wiki page of a crossport |
16:03 |
jeff |
heh. i was just going to ask/look... sorry. :-) |
16:03 |
|
mnsri_ joined #evergreen |
16:03 |
bshum |
#info bshum = Ben Shum |
16:03 |
bshum |
(before the end!) |
16:04 |
Dyrcona |
heh |
16:04 |
Bmagic |
#info Bmagic = Blake GH, MOBIUS |
16:05 |
gmcharlt |
OK, I got distracted there for a moment |
16:05 |
gmcharlt |
but I think we can summarize with |
16:06 |
gmcharlt |
#action Various folks will do more detailed evaluation/testing of Sqitch prior to the EG conference, with an eye towards having more informed discussions |
16:07 |
berick |
cool, thanks everyone |
16:08 |
DPearl |
#info DPearl = Dan Pearl, C/W MARS |
16:09 |
dbs |
#info dbs = Dan Scott, Laurentian University |
16:09 |
dbs |
Last! |
16:09 |
kmlussier |
dbs: Now I'm so tempted to introduce myself again so that I can be last. ;) |
16:10 |
kmlussier |
Going back to one of our earlier agenda items (sorry, I was only half paying attention at the time), I'll send out a message to the dev list with a link to the hackfest ideas page so that people who are not here know about it. |
16:11 |
brahmina |
dbs: are you Clayton Scott's cousin? |
16:13 |
berick |
hopefully, dbs is Bon Scott's cousin |
16:13 |
dbs |
Hells Bells! |
16:14 |
kmlussier |
heh |
16:14 |
jlitrell |
#info jlitrell = Jake Litrell, MassLNC |
16:14 |
gmcharlt |
OK |
16:14 |
jlitrell |
nyaah |
16:14 |
gmcharlt |
#endmeeting |
16:14 |
pinesol_green |
Meeting ended Wed Apr 6 16:14:42 2016 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
16:14 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-04-06-15.00.html |
16:14 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-04-06-15.00.txt |
16:14 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-04-06-15.00.log.html |
16:14 |
gmcharlt |
thanks, everybody! |
16:14 |
jlitrell |
IBTL! |
16:14 |
bshum |
jlitrell++ # ninja |
16:14 |
Dyrcona |
heh |
16:15 |
dbs |
jlitrell++ |
16:15 |
kmlussier |
ha ha ha! |
16:15 |
miker |
gmcharlt++ |
16:15 |
kmlussier |
gmcharlt+ |
16:15 |
jlitrell |
gmcharlt++ |
16:15 |
Dyrcona |
gmcharlt++ |
16:15 |
JBoyer |
gmcharlt++ |
16:15 |
brahmina |
gmcharlt++ |
16:15 |
kmlussier |
That is, gmcharlt++ |
16:16 |
Dyrcona |
And, according to othiym23 on github, the npm registry folks will have all the issues resolved shortly. |
16:16 |
dbwells |
gmcharlt++ |
16:16 |
jeffdavis |
gmcharlt++ |
16:16 |
Dyrcona |
Apparently, the CDN cache does not work as the documentation describes. |
16:16 |
rhamby |
gmcharlt++ |
16:31 |
|
gsams joined #evergreen |
16:34 |
|
rlefaive joined #evergreen |
16:43 |
berick |
Dyrcona: regarding you earlier questions about Sqitch adding work... couple things, if you're still interested. |
16:43 |
Dyrcona |
Maybe tomorrow. I'm involved in something else, now. |
16:44 |
berick |
Dyrcona: k, raincheck |
17:12 |
|
mrpeters left #evergreen |
17:16 |
Bmagic |
alright, so I get the patron object $r = OpenSRF::AppSession->create('open-ils.actor')->request('open-ils.actor.user.fleshed.retrieve', $authtoken, $r, 0)->gather(1); |
17:16 |
Bmagic |
then try to update it $r = OpenSRF::AppSession->create('open-ils.actor')->request('open-ils.actor.patron.update', $authtoken, $r); |
17:17 |
Bmagic |
no errors, but the row in the DB doesn't get changed (I skipped a step here where I changed the day_phone $r->day_phone('test'); |
17:20 |
Bmagic |
hmmm, maybe it's because there are no addresses in the system for the patron. Looking at the osrfsys.log |
17:21 |
|
mmorgan left #evergreen |
17:24 |
StomproJosh |
Ahh, I wish I could delete my launchpad comments within a few seconds. sigh. |
17:25 |
gmcharlt |
hmm? |
17:26 |
StomproJosh |
I just did a re-post with a bunch of horrible formatting... I forgot I added my branch to the ticket last week. |
17:32 |
|
bmills joined #evergreen |
18:56 |
|
TARA joined #evergreen |
19:56 |
|
TARA joined #evergreen |
20:08 |
|
hbrennan joined #evergreen |
20:21 |
|
geoffsams joined #evergreen |
21:01 |
|
TARA joined #evergreen |
23:06 |
|
genpaku_ joined #evergreen |