Open Source Integrated Library System

Evergreen on IRC

#evergreen Logs for Monday, October 3rd, 2011

< Sunday, October 2nd, 2011Raw Log FileTuesday, October 4th, 2011 >
#TimeNickMessage
#00:26:29dbs adds another commit to user/dbs/tpac-gradients to replace the tables & images-based dashboard with pure CSS
#00:27:27jamesrf has quit IRC
#00:28:56jamesrf has joined #evergreen
#00:32:07dbs has quit IRC
#00:40:22_bott_ has quit IRC
#00:41:15_bott_ has joined #evergreen
#05:58:26bjwebb has joined #evergreen
#05:58:26bjwebb has joined #evergreen
#06:34:46bjwebb has quit IRC
#07:53:46Dmagick_ has joined #evergreen
#07:57:11gdunbar has joined #evergreen
#07:59:55collum has joined #evergreen
#08:27:34AaronZ-PLS has joined #evergreen
#08:32:13bjwebb has joined #evergreen
#08:32:13bjwebb has joined #evergreen
#08:36:52bjwebb has quit IRC
#08:38:06mrpeters-isljust an FYI, Makefile.in for building staff client in master tries to pull xulrunner 3.6.22 which doesn't seem to exist. Changing the version to 3.6.23 and all is well.
#08:38:46Shae has joined #evergreen
#08:39:17tsbereYea. Tis on my "annoyances this week" list.
#08:39:24mrpeters-isl10-4
#08:39:33mrpeters-isli know it did exist at some point
#08:39:38tsbereMade for good testing of my "make a release script"
#08:39:51tsbereBecause I wanted it to pull down older versions if they were still referenced
#08:40:18mrpeters-islit seems strange that they'd totally remove all traces to that version
#08:40:31tsbereThey only keep the "current" releases on that server
#08:40:36mrpeters-islaha
#08:43:04tsbere rarely notices the version bumps right away because he doesn't delete the old downloads often
#08:54:29Dyrcona has joined #evergreen
#08:58:16fortin has joined #evergreen
#09:10:03Meliss has joined #evergreen
#09:17:47dbs has joined #evergreen
#09:23:29dbsanyone want to coordinate a response to Baptiste Montoya's "questions about Evergreen for the future" post to open-ils-general?
#09:25:01dbs begins with the "get changed out of bike clothes" response
#09:25:20tsberedbs: Some of the questions I was tempted to answer "If someone wants it badly enough to fund it" ;)
#09:28:05dbstsbere: Yeah, although true enough on the one hand, on the other hand I think there would be resistance to adding features like "act as a integrated discovery layer & institutional repository" to core
#09:28:52tsbere has the added problem of not fully understanding some of the terminology used due to not being exposed to it often enough
#09:29:36dbstsbere: I think we have a reasonably good response for most of the questions with no additional funding required; "social" and "acting as a discovery layer" perhaps the outliers that would land, if ever, past 2.2
#09:30:01dbseven on the social front, one could offer up Chilifresh as a means of accomplishing that goal (as dbs holds nose)
#09:30:28dbsanyway - that's why I think a coordinated response might make sense, we all have pockets of understanding to contribute
#09:30:33dbs goes to change
#09:37:22kmlussier has joined #evergreen
#09:39:39fortin has quit IRC
#09:45:14dbsfor those interested in working on a coordinated reply, I dumped the questions here: http://evergreen-ils.org/dokuwiki/doku.php?id=advocacy:replies:2011-10-02-montoya
#09:47:12kmlussier has quit IRC
#09:47:22yboston has joined #evergreen
#09:48:43tspindler has joined #evergreen
#09:54:16tsbereSo I am still in IRC, but can't talk to anything else. :(
#09:54:42DyrconaMe, too.
#09:55:06jeffcongratulations on your pre-existing sessions.
#09:55:18tsbereMy other pre-existing sessions died.
#09:55:27kmlussier has joined #evergreen
#09:55:32tsbereIRC is literally the only thing off of our network that hasn't fallen over dead for me. :(
#09:55:47jeffsomeone has their priorities straight :-)
#09:55:58jeffsorry to hear that, though.
#09:56:46tspindlersomething happen tsbere? our iii servers just went down
#09:57:05bshumDidn't you hear, you're going to Evergreen today tspindler? ;)
#09:57:08Dyrconatspindler: Do you go through UMass for those server?
#09:57:13tsbereThey do, I believe
#09:57:16tsbereUMass has issues. :(
#09:57:21tspindlerDrycona: yes
#09:57:29DyrconaThat explains it.
#09:57:29bshum(j/k, sorry to hear you have troubles)
#09:59:20tspindlerbshum: better that than our iii servers died, we are not quite ready to do an emergency migration
#09:59:37tsbereemergency migrations--
#10:01:22tsbere makes a new 2.0 dev machine
#10:01:34tsbere suspects he isn't getting email, though
#10:01:55tsbereOooh, my XMPP server is back!
#10:02:51tspindlerbshum: got edi running, but some of our orders didn't go through error, I think it may be a set up issue with the provider because for two of the libraries the test orders went ok
#10:03:03tspindlerthis is the error: ut FAILED: put to ftp1.ingrambook.com/ failed with error: Can't call method "put" on an undefined value at /usr/local/share/perl/5.10.1/OpenILS/Utils/RemoteAccount.pm line 552.
#10:03:14tsberetspindler: Your iii servers responding now?
#10:03:36tspindlertsbere: yes
#10:03:58bshumtspindler: Sweet! Glad you're having some better luck with EDI.
#10:04:22tspindlerbshum: it was really stupid problem, forgot to start webrick.bash after rebooting
#10:04:36bshumtspindler: Oh yeah, that's happened to me before.
#10:05:27tspindlerbshum: I should test the patch while at it since I installed it
#10:05:48bshumtspindler: That error feels like something weird happened with the EDI hostname maybe.
#10:10:39dbsI've dumped a bunch of answers into http://evergreen-ils.org/dokuwiki/doku.php?id=advocacy:replies:2011-10-02-montoya - comments / suggestions for revision welcome
#10:13:14kmlussier has quit IRC
#10:14:09bshumdbs++
#10:14:50berickdbs++
#10:15:39dbsnow please commit user/dbs/tpac-gradients @ working for me :)
#10:16:50dbs thinks maybe we should have a list of "TPAC things that are degraded visually but still perfectly functional in IE" - gradient headers would be on that list
#10:17:51dbs also isn't committed to the exact colours used in the gradient header/footer but would like to establish the basic means of providing gradients, rather than nasty repeating images
#10:19:30berickon the tpac topic, facets basically work now http://dev198.esilibrary.com/eg/opac/results?query=jazz%20music. pushing collab branch shortly for further tweaking and styling
#10:20:26berick looks at tpac-gradients
#10:21:45dbsberick++
#10:22:29dbstpac-gradients has a second commit in it that replaces the "My account dashboard" table + images + many many divs with a much simpler CSS approach
#10:22:41dbsso ensure you log in to see that effect
#10:22:52berickwill do
#10:23:33dbs will be afk through 11:00 - will send a response to baptiste when he gets back
#10:31:13abeNd-org has joined #evergreen
#10:32:29mrpeters-isldbs: i can give you color codes I used if you want to try to mirror those in the gradients
#10:34:27mrpeters-isltop: #13533f to bottom:#2e8469, fwiw
#10:35:03eeevilberick: not seeing facets on that link :(
#10:35:26berickyeah, just installed dbs code, which removed my facets. one sec..
#10:35:38eeevil:)
#10:35:46eeevilgradients++
#10:36:03berickeeevil: facets are back
#10:36:16mrpeters-islapparently my transparent logos didn't get pushed to user/mrpeters-isl/green_jungle_skin so i'm fixing that
#10:36:31mrpeters-islthe white logo, no background will probably look better than the current colored/white jpg
#10:38:45kmlussier has joined #evergreen
#10:41:54bshumdbs: I asked afterl to include something about the kid-pac development that we're working on with others to be part of question 5's answer for montoya. Still reading the rest of the bullet points to see if there's anything else to be said.
#10:44:54tspindler has quit IRC
#10:47:21matt_carlson has joined #evergreen
#10:49:08mrpeters-islI pushed user/mrpeters-isl/gradient_friendly_logos to go along with dbs's gradient TTPac
#10:51:50matt_carlson has quit IRC
#10:52:03matt_carlson has joined #evergreen
#11:03:07dbsbshum: cool - the kidpac was in the back of my head this morning but I don't know much about it
#11:03:56bshumdbs: Neither do I actually, I just shuffle around it and pass questions to my other coworkers.
#11:08:01tspindler has joined #evergreen
#11:09:00dbsmrpeters-isl: your color codes are nice! kind of wondering if there's some side-document rationalizing the color scheme somewhere for design-impaired people like me, such that starting with one primary color one could fill in standard complementary colours rather than dog's breakfast-ism
#11:09:50dbs(specifically oriented towards TPAC customization in this case, naturally)
#11:10:57dbsberick++: facets are looking & working nicely!
#11:11:48berickthanks for pokin'
#11:12:20dbsberick: is it ready for pushiness?
#11:12:39berickdbs: as far as I'm concerned it is.
#11:12:40mrpeters-isldbs, i tell ya, i just took the official color to start and then darkened it a good bit
#11:13:36mrpeters-islhttp://colorschemedesigner.com/ is helpful
#11:15:33berickdbs: hmm, it will need some cleanup, though, somewhere along the way, to replace the images with divs/css
#11:16:55wlayton has joined #evergreen
#11:18:05fortin has joined #evergreen
#11:18:41dbsmrpeters-isl: yeah, I know about general color theory and various tools. I'm saying, in the context of the TPAC skin, what should one do.
#11:19:05dbsberick: I know somebody who has some skills in that area
#11:19:19berick thought dbs might know a guy
#11:19:22mrpeters-islah ok, dbs
#11:19:53mrpeters-islis there a particular area you're concerned about complimentary colors?
#11:21:17dbsmrpeters-isl: I'm not just talking about complementary colors, I'm talking about the whole scheme: button colors, tabs on advanced search/prefs pages, etc
#11:21:19berickworking/collab/berick/tpac-facets is the topic branch
#11:22:03mrpeters-islwell, i pushed some recolored buttons/tabs in green_jungle_skin
#11:22:05dbsjspac sort-of had the idea of "4 colors" which sort-of worked for theming :)
#11:22:41mrpeters-islwhen theming, just a simple colorize in Photoshop/GIMP on those images will suffice
#11:22:42dbsyeah, I don't really care about the what, anybody can change anything. the "why" and "how" is more interesting.
#11:23:15mrpeters-islthere's the how :)
#11:23:29mrpeters-islthe why, i just didn't think the blue matched with the green/tan
#11:23:31dbsthat's a how
#11:24:18mrpeters-islsame reason for the buttons
#11:24:19dbsand that's what I'm getting at; rather than one-off decisions about individual elements, it would be nice to have some sort of rationale to work towards
#11:24:53dbs is going to focus on something immediate
#11:31:51mrpeters-isli'm certainly up for a discussion on it when you have time, just ping me
#11:32:19eeevilberick: only problem I can find is reopening a closed facet box
#11:32:22eeevilberick++
#11:33:56mrpeters-islwe should also look at turning questions.png and faqs-btn.png into something else, for i18n purposes
#11:35:15mrpeters-isli can recreate those buttons, and then we could put text over them with css
#11:35:26berickeeevil: ah, yes, if only 1 is closed it won't re-open. will fix
#11:35:31berickthanks for looking
#11:36:07mrpeters-islbetter yet, maybe someone at ESI has those images without the text from developing the KCLS pac?
#11:37:34mrpeters-islnevermind -- ++content aware in CS5
#11:37:46eeevilmrpeters-isl: ESI didn't make the visual elements ... I'll take blame for a lot, but not that! ;)
#11:38:01mrpeters-islno worries, photoshop is amazing
#11:38:27tsbere hasn't installed 2.0 in so long he actually needs to reference the docs
#11:38:47dbsmrpeters-isl: I didn't care about questions & faqs because I assume most libraries will replace their landing page with something meaningful to their site
#11:39:18mrpeters-islperhaps, maybe we can include the blank images in /examples then?
#11:39:37dbsmrpeters-isl: also, not going to put text over images. images = fail
#11:40:25mrpeters-islcool, so including the blank images would probably be a good idea
#11:40:38mrpeters-islwould give skinners a template to work with
#11:40:45dbsmrpeters-isl: that's part of the design rationale that I've been working on. TPAC should be slim, images are evil
#11:41:09dbsI don't get it, why the hell would skinners need blank images for something that doesn't need images in the first place?
#11:41:29mrpeters-isli agree, it doesn't "need" images but it sure looks pretty :)
#11:41:43dbsreplace "FAQ" image with div + CSS + linear gradient and you still have pretty
#11:41:50tsbereimages are not easily dealt with by alternative CSS for alternative devices. Reason enough for avoiding them ;)
#11:42:31dbsmore or less pretty, depending on the skill of the designer (choice of fonts, color, etc) but that's "just" implementation detail (heh)
#11:42:38mrpeters-islyeah, good point...we can even do the drop shadow with css3 it looks like
#11:43:38dbsyep
#11:51:06Montu has joined #evergreen
#11:52:16vikas_ has joined #evergreen
#11:52:56Montuhey someone plz can explain me about transit in evergreen actually is
#11:53:31jeffMontu: a transit is a record of a physical item being sent from one library to another in an evergreen system.
#11:54:32jeffMontu: two of the most common examples of why an item would transit is if a patron at Branch2 places a hold on a title, and an item at Branch1 is targeted and captured, then "transits" to Branch2 to go on the hold shelf for that patron...
#11:54:34Montu<jeff>it's present in there officail pdf too,but very less explanation does it contain
#11:54:47Montuhow can i use it
#11:54:51jeff...or if someone checks out an item from Branch1 and then returns it to Branch2
#11:55:08berickdbs: fyi, pushed small fix to collab/berick/tpac-facets (in case you're doing stuff in there)
#11:56:05dbsberick: cool. probably won't touch it for a while. today is "fix Conifer's localization" day
#11:56:26berick backs away slowly
#11:56:51Dyrcona decides to play some "Weird" Al, thanks dbs!
#11:58:50Montuhow can i do it can anyone tell me step by step
#11:59:01Montubcoz its not present in pdf
#11:59:58DyrconaMontu: transits happen automatically when copies are sent to fill holds or set to return their owning library when checked in elsewhere. there's nothing for you to do except place holds.
#12:02:13Montu<Dyrcona> u mean its just a waste
#12:08:11DyrconaMontu: I mean the system does transits for you when necessary. You don't have to do anything.
#12:08:46DyrconaMontu: By default, they should be allowed for all materials going to any location.
#12:09:57Montu<Dyrcona>ya thank you so much dycrona
#12:18:47mmorgan has joined #evergreen
#12:22:13ybostonAs part of my work with EG DIG, I wanted to humbly propose some minor changes to the EG and OSRF README files. Should I just follow the typical code contribution procedure (clone the repo and submit a patch)?
#12:22:53dbsyboston: sure
#12:23:08dbsor just throw them on the mailing list if they're small
#12:23:36dbsor put the text in the bug description
#12:23:45ybostondbs: thanks
#12:27:13tsbere apparently never noticed the "random user id 1 username/password" bit making it back to 2.0
#12:30:35bjwebb has joined #evergreen
#12:30:35bjwebb has joined #evergreen
#12:32:37matt_carlson has quit IRC
#12:44:07mrpeters-isldbs: https://master.evergreen.lib.in.us/eg/opac/login?redirect_to=%2Feg%2Fopac%2Fmyopac%2Fmain -- positioning is off, but is that what you had in mind?
#12:44:50dbsmrpeters-isl: yep, that's the idea
#12:45:01mrpeters-isl thinks that button style would be attractive to compliment the rounded tabs elsewhere in ttpac instead of the "old school" square ones
#12:46:08dbsjust a radius away, yep.
#12:46:40akilsdonk has joined #evergreen
#12:47:08dbsideally most of the CSS definition could be inherited instead of duplicated for each button. Ergo class = opac_button
#12:49:16mrpeters-islyeah, the only thing that gets tricky is that Questions/FAQs are a bit larger (and probably should be) than the submit/login type buttons
#12:51:00dbssure. you can have two classes, 'opac_button' and 'placeholder_landing_page_button' and override color / size in placeholder_landing_page_button
#12:51:44dbs still suspects that most libraries will not have FAQ & Questions? buttons on their login landing page
#12:52:57mrpeters-islhmm, i disagree partially. I bet most libraries have at least 1 person to contact for support and would want to link to that in the OPAC. FAQ's, maybe not.
#12:53:23mrpeters-island now that we've removed the static text the links can easilly be changed into anything
#12:53:38mrpeters-islsay, a list of databases the library subscribes to
#12:53:41dbsFAQs and Questions. both.
#12:53:58dbsIFAQs for "infrequently asked questions" maybe?
#12:54:10dbsmrpeters-isl: yes, that's the idea
#12:54:23dbsthey're placeholders.
#12:54:39dbsjust like link_1, link_2, the link from the evergreen logo at the top, etc
#12:54:42mrpeters-isli hear you. since theyre stock, we'll make them look good!
#12:57:52dbsWould be good to have a "TPAC: quick customization steps" mini-guide
#13:03:07mrpeters-isl+1
#13:03:17mrpeters-islill try to compile my findings so far
#13:34:56fortin has quit IRC
#13:47:22rsoulliere has joined #evergreen
#13:52:17kmlussier has quit IRC
#13:58:26Montu has quit IRC
#14:04:06jrodge01 has joined #evergreen
#14:04:24berickdbs: since you worked on the asset.uri bits in tpac, i'm bugging you... i'd like to show the 856 links that are not already represented by asset.uri's. presumably that's 856's with no $9? any objection to adding those in the same block w/ the asset.uri data on the record details page?
#14:05:26dbs yacks
#14:05:27eeevilberick: IMO, that's exactly where they should go
#14:05:32tsbere wonders if there is something *other* than going down some of the pullrequests he should be doing to help prep for release(s) today/tomorrow
#14:05:58dbsberick: so - displaying both a located URI and a non-located URI on the same page?
#14:06:32dbsor are you thinking fall-through - basically 1) If not in SFX, then 2) if not a located URI then 3) display any 856 we have, captain
#14:07:49dbstsbere: foreach my $secpatch (@secpatches) { echo "clear documentation on why $secpatch was necessary & steps required for applying $secpatch"; } ?
#14:08:11whyboston2 has joined #evergreen
#14:08:14wolf29 has joined #evergreen
#14:08:33jrodge01I need help with the pg_loader.pl script.
#14:08:33wolf29Hi! is there a meeting today?
#14:08:55dbsberick: long story short - my position is: do not show unadorned 856 fields if there is a located URI to display
#14:09:17bshumwolf29: I believe that's at 2:30 pm ET, so... 21 minutes to go?
#14:09:34bshumwolf29: If you're asking about the DIG meeting
#14:09:39berickdbs: i agree. is the lack of a $9 sufficient test?
#14:09:53Green_ has joined #evergreen
#14:10:06Green_HI
#14:10:07dbsberick: yep, that should be. You _could_ get asset.uri entries without it, by inserting manually, but if you're doing that you deserve what you et
#14:10:35dbss/et/get/ - although I et a cricket on the weekend, and I deserved it
#14:10:58dbsberick: oh wait - miker added support for a subfield other than $9
#14:12:25wolf29Note to self: if updating from eg-2.6, expect to have your postgresql-9.1 installation trampled.
#14:12:27dbsberick: subfield w and subfield n if I'm reading this correct
#14:14:19dbsyeah, biblio.extract_located_uris says 856 $9 / $w / $n are treated as shortname owner fields
#14:14:30bshumwolf29: 2.6 or 1.6? Or wait, what?
#14:15:18berickdbs: good to know
#14:16:36dbs doesn't know why $w and $n were added - particularly $w - but there they are
#14:16:37dbs:0
#14:16:42wlayton has quit IRC
#14:18:12wolf29bshum: 2.06 to 2.1 eventually - but for now, 2.0.6 to 2.0.7
#14:18:15wolf29:-)
#14:19:27jrodge01I have a marc.bre.json file from the marc2bre.pl script, but can't run the pg_loader.pl script properly. I don't kknow the proper commands.
#14:19:45eeevilso, in looking at located uris, I recall someone making them act exactly like copies
#14:20:01wolf29item IV says As the root user, install Evergreen: make STAFF_CLIENT_BUILD_ID=rel_2_0_7 install
#14:20:03wolf29instead of "as root, make install" - which is missing from the instructions. -- http://open-ils.org/dokuwiki/doku.php?id=upgrading:evegreen:2.0.6_to_2.0.7
#14:20:12eeevilwhere searching with a context org of 1 would show located uris anywhere
#14:20:14mrpeters-isljrodge01: i beleive you can find that at http://docs.evergreen-ils.org/2.0/draft/html/migrating_records_using_migration_tools.html
#14:20:45eeevilwhich is different that the initial implementation, where you had to search at or "below" the located uri owner to see them
#14:20:58jrodge01mrpeters-isl: Thanks. I'm reading the documentation, and it isn't very well documented.
#14:21:29eeevilanyone recall when that happened and who made that change? because, I still think it's wrong and broken, and it's making me very itchy
#14:21:30mrpeters-isljrodge01: hmm, i've followed that same documentation several times
#14:21:53jeffeeevil: we had a use case where we wanted searches at SYS1 or BR1 or any other child of SYS1 to show one auri, ideally with needing only a single 856 tag rather than N+number_of_child_ous
#14:22:14jrodge01I'm looking at chapter 11, and it pretty much says "use pg_loader/pl to convert the records".
#14:22:24jeffeeevil: ah, but you're asking about code changes -- nevermind.
#14:22:33mrpeters-isli think you're looking at the wrong documentation then
#14:22:41eeeviljeff: well, that was ostensibly covered by giving the located URI to the system
#14:23:08eeeviljeff: but, yes, I'm talking about a code change (what I consider a code breakage, to be more direct ;) )
#14:23:16jeffat least in 1.6, that required that you search at the system level. maybe this was post-"that change that's making you itchy"
#14:23:25jeff:-)
#14:23:38mrpeters-isljrodge01: parallel_pg_loader.pl -or bre your.bre > pg_loader-output.sql
#14:23:45mrpeters-islthat should be enough, if you're running 2.0
#14:24:04bshumWell, as long as we've been using the located uri's in 2.0, they've been visible at higher depth ou's (we just try to pretend they're not). We didn't get to try them in 1.6.
#14:24:04eeeviljeff: right ... the correct fix would have been "show me records that have located uris at here-or-ancestors"
#14:24:35eeevilwhat we have ATM is "show me records that have located uris at here-or-descendents"
#14:24:41eeevilin master, at least
#14:25:28eeevilhrm.. or, perhaps it's full-path ... which is still wrong, but less broken ;)
#14:25:32eeevil tests
#14:27:12jrodge01mrpeters-isl: I'm in the directory, but when I try to run it, it say s"-bash: parallel_pg_loader.pl: command not found"
#14:27:28eeevilit's full-path
#14:27:56kcollier has joined #evergreen
#14:28:32dbseeevil: I think it was a patch, not something that was actually committed
#14:28:52dbs suspects said patch came from Sitka
#14:28:56mrpeters-isljrodge01: well, does that file actually exist in your working directory?
#14:29:19tsberedbs: Should I include potential ways to exploit the security issues when I have them? :P
#14:29:33jrodge01mrpeters-isl: Yes.
#14:29:39dbstsbere: that would be consistent with CVEs wouldn't it?
#14:29:47mrpeters-isljrodge01: doesn't seem so
#14:30:03bshumwolf29: I'm unclear what you mean by the step being "wrong" for specifying the exact client build ID for an upgrade. It seems to me that without doing so, you'd have no distinct installation directory for the upgraded components. Or it would go to some sort of default path?
#14:30:06jrodge01mrpeters-isl: I use the ls command and it is right there.
#14:30:06jeffbacking up, and not speaking to current code at all: for an 856 $9 with shortname SYS1, i'd want it to show in search results at SYS1 and lower, and for $9 of BR1 I'd want to only see it in results searching BR1. If I wanted something consortium-wide, i'd only want to see bibs in search results if the $9 was CONS.
#14:30:12eeevildbs: it's doing full-path now
#14:30:15eeevilin master
#14:30:30jrodge01mrpeters-isl: Does this need to be ran as root or opensrf?
#14:30:37bshumwolf29: And also, that step should have no bearing on a PG installation...
#14:30:41dbseeevil: huh
#14:30:53dbswhat do you mean by "full path"?
#14:31:06eeeviljeff: right, exactly
#14:31:15dbsjeff: yeah, that's what we wanted too
#14:31:16mrpeters-isljrodge01: i think you may want to use "./" before the script. You need to tell the OS you want to run that file in the current directory. If you don't specify, it's not going to find the script unless your path variables are set up to include /openils/bin
#14:31:21jeffeeevil, dbs: oh, hooray!
#14:31:30mrpeters-islit should run as any user, but try opensrf first
#14:31:40mrpeters-isljust make sure opensrf can write out to the directory you run it in
#14:31:42eeevildbs: as in, it's testing the uri ou against the search context ou's full ancestor and descendent tree
#14:31:56jefffwiw, that's now how it worked when i tested in 1.6, and i thought someone here said "working as expected", with the implied patches welcome. :-)
#14:31:59raynerj has joined #evergreen
#14:32:19eeevildbs: using actor.org_unit_full_path(search_context_ou)
#14:32:23jeff("that's not how it worked" == "it didn't work as i just described it wanting to work")
#14:32:29KN2W has joined #evergreen
#14:32:47eeevilshould be using actor.org_unit_descendants(context,depth)
#14:33:44wolf29bshum: that step wasn't the evil one - it was "make -f Open-ILS/src/extras/Makefile.install <distribution>" which reinstalled my purged postgresql-8.4
#14:34:15kcollierWe'll be starting the DIG meeting momentarily.
#14:34:17dbsjeff: oh, right. I was probably the one who said "working as expected" due to the licensing implications
#14:34:26dbs will shut up
#14:34:33bshumwolf29: Ah that makes slightly more sense then.
#14:34:49bshumwolf29: And not unexpected since 2.0 doesn't actually have 9.1 targets, etc.
#14:34:55eeevil will shush as well
#14:35:07bshum also apologizes to DIG
#14:35:12kcollierCould DIG participants like to start introducing themselves, while other conversations start to wrap up.
#14:35:27dbs would like to know why the DIG git repo uses separate directories and filenames to diff between 1.6 and 2.0 rather than just using two branches, but is largely happy that the docs are under version control in the first place :)
#14:35:31kcollier(no worries, hate to interrupt the discussion in progress)
#14:35:35moodaepobshum: Also that's taken care of in master/2.,1 since we will be using aptitude -P from now on
#14:36:18moodaepo goes back under a rock and leaves DIG meeting alone
#14:36:22kcollier is Karen Collier, Kent County Public Library
#14:36:25rsoulliere is Robert Soulliere from Mohawk College
#14:36:39wolf29bshum: later install extras don't even install postgresql by default - which I like better. An if-then qualifier might be good there
#14:36:48yboston is Yamil Suarez - Berklee College of Music
#14:37:43akilsdonk is Angela Kilsdonk, Equinox Software
#14:37:58kcollierI know Kathy is unable to attend. Anyone else?
#14:38:02AlexR has joined #evergreen
#14:38:08wolf29wolf halton from Lyrasis
#14:38:14kcollierIs there a volunteer to construct minutes from the chat transcript?
#14:38:26tspindler* tspindler Tim Spindler from C/W MARS
#14:38:41AlexR is Alex Reczkowski from Berkshire Athenaeum (part of C/W MARS)
#14:38:46wolf29raises hand to volunteer
#14:38:58rangi is chris cormack from NZ, lurking
#14:39:39kcollierwolf29: minutes?
#14:39:50raynerjraynerj is June Rayner from eiNetwork
#14:41:09kcollierThank you to everyone who's here. Let's get started and any latecomers feel free to introduce yourselves whenever.
#14:41:24kcollierFirst up, updates from content coordinators.
#14:42:03ybostonI can go
#14:42:14kcollierThanks for starting us off. :)
#14:42:30ybostonStarted working on draft changes to EG & OSRF READMEs to eventually improve their clarity and move us closer to having a single installation documentation source
#14:42:37ybostonI trained my student employee, username: berkleeklim on Github, on how to contribute to the EG docs, and she has since done some work under my supervision like...
#14:42:46ybostonconverted a page of serials documentation, from C/W MARS, now found here http://docs.evergreen-ils.org/2.0/draft/html/_serials_creating_a_special_issue_to_receive.html and added images to http://docs.evergreen-ils.org/2.0/draft/html/_alternate_serial_control_view.html#create_an_issuance
#14:42:54ybostonWorking with my student gave me a chance to experiment with different Git/Github workflows that could be used for other DIG collaborators in the future, though nothing is ready for prime time yet
#14:43:07ybostonthat is basically all I have to report
#14:43:18kcollierGreat, thank you.
#14:43:31kcollierIs there a volunteer to report next?
#14:43:37rsoulliereI can go.
#14:43:44rsoulliereOutline for 2.1 is available at: http://open-ils.org/dokuwiki/doku.php?id=evergreen-docs_2.1:outline
#14:43:54rsoullierePlease review sections and see what you would like to contribute. We need to have people familiar with 2.0 and 2.1 to make notes regarding which sections can be ported directly from 2.0 with minimal changes.
#14:44:27rsoulliereNot sure if this was reported in last meeting... Jenny combined the Acquisitions content for into one unified chapter: http://docs.evergreen-ils.org/2.0/draft/html/acquistions.html. A note was sent out on the DIG list before the last meeting.
#14:44:52wolf29I got a call.. I will do the minutes. :-)
#14:45:19rsoulliereIn response to Dan's Question: "why the DIG git repo uses separate directories and filenames to diff between 1.6 and 2.0 rather than just using two branches..."
#14:45:39rsoulliereThat was my bad when I set it up a long time ago and was my first attempt at repository management.
#14:45:57rsoulliereI did wonder if documentation should should the same structure as code?
#14:46:05rsoulliereI was worried about clean backporting from one version of the documentation so I decided on the safest option at the time -- form me.
#14:46:41rsoulliere"for me"
#14:47:16dbsrsoulliere: oh sure - so there would be no objection to converting those to branches, instead, sometime?
#14:47:35rsoulliereI have no objection.
#14:48:16dbsAlso looking forward to yboston's suggested revisions to the EG & OSRF READMEs, fwiw
#14:48:24rsoulliereIn fact, I was originally hoping to have the docs coupled with the code in the "docs" directory in the code repo.
#14:49:26kcollierThat sounds like a reasonable approach. Any downside?
#14:51:25kcollierAny more discussion on the docbook/repository side of things or are we ready to move on to the other reports?
#14:51:38dbs doesn't know if there would be any fear from git repo maintainers of doc commits trampling on code
#14:51:51dbsbut I would in principle support the idea of "one repo for docs & code"
#14:52:28rsoullieredbs: you might need to provide some expert guidance. I am not quite sure how master vs other branches would play out for documentation.
#14:52:43dbsrsoulliere: sure, can discuss it later
#14:53:03rsoulliereI had one more question in my report...
#14:53:10rsoulliereAny ideas about when the feature list will be available for 2.1?...
#14:53:20rsoulliereSomething like the list for 2.0: http://open-ils.org/dokuwiki/doku.php?id=feature_list_2_0
#14:53:46rsoulliereAlways nice to have a summary of changes or new features from the last major version early on in the documentation.
#14:54:30dbsrsoulliere: heh, isn't that the DIG's job? </pass_the_buck>
#14:55:26kcollierDo we know who produced the last one and how they went about collecting the info? Does it come from the commit notes? Or is there some simpler way?
#14:55:30rsoulliereI suppose... I am not sure if there is anyone in the thick of the DIG who is an insider on the 2.1 development or who is working in 2.1 intensely enough.
#14:55:54gdunbarI can probably help you there...
#14:56:30dbskcollier: I believe the 2.0 feature list originally came from gdunbar & one other person(?) and then mrpeters-isl cleaned it up / organized it a bit more
#14:56:53kcollierThanks.
#14:57:11gdunbarI can get eeevil to give me the changelog and I can go over it with berick and eeevil to make sure the entries are reasonably human readable
#14:57:38yboston has quit IRC
#14:57:50kcollierSounds good. :)
#14:58:12gdunbarNo problem. Deadline?
#14:58:25dbsa slightly out of date changelog is at http://evergreen-ils.org/downloads/previews/ChangeLog-2.0-2.1_rc2
#14:58:51gdunbarexcellent. thanks, dbs!
#15:00:08eeevilthat'll be the major featury bits
#15:00:37kcollierGreat! rsoulliere, anything else for your report?
#15:00:48rsoulliereno, all done.
#15:01:16kcollierOkay, that leaves Admin/Development and Reports. Who's next?
#15:01:26raynerjAdmin?
#15:01:36raynerjGot help from yboston and rsoulliere on git workflow - thanks!
#15:01:41kcollierSounds good. (Thanks rsoullliere)
#15:01:53raynerjpushed a new document on adding report sources - this was a request from the reporting group
#15:02:18raynerjLooking for priorities for other system admin docs
#15:04:20kcollierSounds good. :)
#15:05:10raynerjAny suggestions on priorities?
#15:07:38kcollierNothing's coming to mind. Anyone else have any thoughts?
#15:08:01rsoullierecirc policies might be critical...
#15:08:46collum has quit IRC
#15:08:52whyboston2I second Robert
#15:09:17rsoullieree.g. going through the entire process from circ modifiers... etc.
#15:10:02raynerjOK - thanks for the suggestion. I'll take a look at that
#15:10:37rsoulliereSome real-time examples would be great to give people some guidance. Especially for complex consortia I would imagine.
#15:10:57kcollierAnything else from Admin/Development?
#15:11:15raynerjThat's it, thanks!
#15:11:40kcollierIs Jennifer here to address reports?
#15:11:58whyboston2 has to leave for a dentist appointment.
#15:12:01jrodge01.
#15:12:01kcollierBesides Kathy, who I know isn't able to make it, I think that's the only one remaining.
#15:12:12kcollierThank you raynerj for your report.
#15:13:36kcollierKathy asked me to ask if there's anyone who would like to help coordinate the OPAC / Staff Tasks section.
#15:14:08jrodge01mrpeters-isl: I keep getting permission denied errors when I run it as opensrf.
#15:14:24mrpeters-isljrodge01: lets talk after meeting
#15:14:35moodaepokcollier: Jennifer is on the road and won't be addressing reports.
#15:15:16kcolliermoodaepo: thanks
#15:16:31kcollierSo that's something to think about.
#15:17:02kcollierNext item on the agenda is Old Business.
#15:17:30kcollierI don't have anything in particular in mind. Is there any Old Business anyone would like to revisit?
#15:18:53kcollierAny new business?
#15:19:13mrpeters-islyes
#15:19:33kcollierGo ahead.
#15:19:39mrpeters-islI've started a crash course in customizing TTpac
#15:19:45mrpeters-islhttp://open-ils.org/dokuwiki/doku.php?id=dev:customizing_ttpac -- thanks to dbs for the idea
#15:20:25mrpeters-islThis at least gets people in the right locations when making modifications to the default, or to create custom skins
#15:20:38rsoullieremrpeters++ dbs++
#15:20:39wolf29mrpeters-isl: +1
#15:20:51mrpeters-islSo we should probably aim to include something like this in the 2.1 documentation
#15:20:59dbs2.2 docs
#15:21:04dbsttpac isn't in 2.1
#15:21:06mrpeters-isloh, right sorry
#15:21:17dbsmrpeters-isl++
#15:21:50mrpeters-isl++ to those who worked on TTpac. It's so easy to customize compared to jspac
#15:22:18kcollierThat's great. Thank you.
#15:23:46kcollierAny more new business?
#15:25:22kcollierIf not, then I think we can wrap this meeting up. Our next meeting is scheduled to fall on Monday, November 7.
#15:25:39kcollierThank you everyone.
#15:25:50wolf29Question. Is there a minutes page in the wiki I can add a link to?
#15:26:02eeevilwhew! /me unshushes
#15:26:10rsoullierekcollier++
#15:26:50wolf29ok never mind. It just bit me. :-)
#15:26:57eeeviljeff / dbs: working/collab/miker/located_uri_visiblity_fix[_2_1] ... master and 2.1 located uri visibility branches
#15:27:00kcollierPast minutes are archived at http://evergreen-ils.org/dokuwiki/doku.php?id=evergreen-docs:dig_meetings
#15:27:29wolf29kcollier: thanx
#15:27:32rsoulliere has quit IRC
#15:28:11eeeviljeff / dbs: lemme know if that's more in line with what you're expecting
#15:31:38AlexR has quit IRC
#15:33:23tsbere is working on "what security issues are being fixed" type documentation, but isn't sure if he would be sending it out/posting it or if someone else would end up doing so
#15:33:40tsbere also isn't sure how good he is at writing this kind of thing
#15:41:14mrpeters-isljrodge01: permission denied either means the script isn't executable (try chmod +x) or the user you're trying to run it with doesn't have the right permissions
#15:41:30mrpeters-isltry running it with sudo
#15:49:13dbstsbere++
#15:49:14dbstsbere++
#15:49:16dbstsbere++
#15:51:53jrodge01mrpeters-isl: thank you, it converted properly
#15:52:42tsberedbs: Should I be writing this as a "I will be sending this out", or as "someone will be posting this somewhere"?
#15:53:15dbstsbere: prolly will get posted to blog, as well as mailing lists for the announce?
#15:53:50tsbereHmmm. I wonder how I should handle wanting to attach one POC code block then.
#15:54:18mrpeters-isljrodge01: great
#15:55:11matt_carlson has joined #evergreen
#15:55:34bshumeeevil++ # took the changes and put them together with our 2.0 test server.
#15:55:59bshumSeems to hide our electronic resources from view in global now, and only comes up when searching locally.
#15:58:58jrodge01mrpeters-isl: The document you linked me to is great. It covers everything that I need.
#15:59:13akilsdonk has quit IRC
#15:59:21bshumSort of a git question, I noticed that the patch as written was set for master/2.1 (since there's pieces in the function that aren't present in 2.0). If we were to write a 2.0 patch, we'd have to tailor it for 2.0's version of the function and have a different branch for that right?
#15:59:22mrpeters-islgreat
#15:59:27mrpeters-isldig++
#15:59:43jrodge01mrpeters-ils: The official documentation, on the other hand, is horrible. It only covers 1.6, and most of it is no longer applicable. I understand its an early draft, but with 2.1 coming out soon, is it on the table to update the documentation anytime soon?
#15:59:53mrpeters-islbshum: you can try applying the patch to a rel_2_0 branch
#16:00:01mrpeters-islbut it may not apply cleanly, so you may have to hand patch
#16:00:16mrpeters-isljrodge01: hmm, i don't think thats true
#16:00:18bshummrpeters-isl: Gotcha, hand patch. Sounds delicate.
#16:00:35mrpeters-islthe documentation I linked you to is 2.0 documentation
#16:00:59dbssome of the 2.0 docs are just 1.6 docs
#16:00:59abeNd-orgwith evergreen 2.x, anyone had much luck in getting the SP 200 receipt printer to work? Seemed AOK in 1.6.x
#16:01:14jrodge01mrpeters-isl: Compare this: http://docs.evergreen-ils.org/2.0/draft/html/migratingdata.html to this http://docs.evergreen-ils.org/2.0/draft/html/migrating_records_using_migration_tools.html
#16:01:46Meliss has quit IRC
#16:02:05jrodge01mrpeters-isl: You linked me to the next chapter, but its much more informative than the previous one, and more simple. (I just noticed what you linked me to is the next page).
#16:02:40moodaepoHaving not used the patron barcode setting in the staff client library settings editor, does that pre-populate the barcode field during patron registration?
#16:03:59mrpeters-isljust pushed user/mrpeters-isl/i18n_friendly_ttpac_buttons to get rid of the nasty hard coded buttons
#16:04:30abeNd-org^star TSP 200-24
#16:05:08tspindler has quit IRC
#16:06:58dbsmrpeters-isl: your commit message might need amending - seems to be cut off
#16:07:04dbs"Removed the static text from the FAQ and Questions images in help.tt2. This"
#16:07:09dbslooks good though
#16:07:18mrpeters-isljrodge01: hmm, i'm probably the toughest critic about the documentation but I've always found the migration documentation sufficient.
#16:07:22mrpeters-islthanks dbs, will fix
#16:09:20tsbere can't finish his security documentation attempt without more information :(
#16:09:58jefftsbere: asking for that information on the security list sounds like it would be a good place to start.
#16:10:09tsberejeff: I already sent the email.
#16:10:16jefftsbere: great!
#16:10:21tsbere just has no clue when people will get around to responding
#16:11:21akilsdonk has joined #evergreen
#16:12:02mrpeters-islk message fixed. also pushed user/mrpeters-isl/ttpac_tab_style which is minor, but i think it looks better
#16:13:08eeevilback later tonight for cutting of releases, if that's a thing today
#16:17:41abeNd-orgor just ditch the star printer & get something new? is there a HCL for EV2 for receipt printers?
#16:20:25Green_Hello everybody
#16:20:49wolf29bye Y'all
#16:20:50Green_i got this error while testing the Evergreen connection
#16:20:59wolf29 has quit IRC
#16:21:24Green_could any body trace the error and help me to trouble shoot the process
#16:21:28Green_http://pastebin.ca/2086544
#16:21:49dbs responded to tsbere on the sec list
#16:22:32DyrconaWhee!
#16:22:50matt_carlson has quit IRC
#16:22:51DyrconaTook ten clients, but I got one part of a new feature working.....
#16:24:17moodaepoGreen_: You need to go into srfsh as user opensrf not root
#16:24:25Green_ok
#16:24:28senatordbs: i'm going to push your gradients branch if you still want it pushed.
#16:24:47senatormrpeters-isl: i also like your (three?) branches, except that in one of them,
#16:24:58dbssenator: sure, I love you.
#16:25:07Green_i also login as opensrf user
#16:25:09senatorthere seems to be some redundant css between quesbutton and opac-button, for example, and a little more like that
#16:25:45senatormrpeters-isl: that's i18n_friendly_ttpac_buttons. but i'm going to sign off and push the other two now i think
#16:25:56dbs will sort out any conflicts that result with berick's facet branch
#16:26:02Green_moodaepo_
#16:26:29Green_i logedin as a opensrf user for srfsh
#16:26:51mrpeters-islok, i'll see if i can compress it a bit
#16:27:31mrpeters-islalso trying to figure out why the grey bar behind Fines/Payments tab doesn't span the whole width of the screen like the rest of the grey bars do
#16:28:11kcollier_ has joined #evergreen
#16:28:12moodaepoGreen_: Did you try your login test again?
#16:28:18mrpeters-islnot sure which way is "right" but i think it looks better with that not just being a grey bar that dies in the middle of the page, for example http://goo.gl/LL1VC
#16:28:26Green_ok
#16:28:34KN2W has quit IRC
#16:29:49dbsmrpeters-isl: because it is a child of div#main-content which has an explicit width of 974 px
#16:30:22Green_http://pastebin.ca/2086548
#16:30:33Green_yes i tried it as a opensrf user
#16:31:12dbs kind of hates the fixed widths but that's a future step - early experiments suggested that it shouldn't be too problematic to remove them
#16:31:44kcollier has quit IRC
#16:31:53kcollier_ is now known as kcollier
#16:32:12senator+1
#16:32:23senator hates them too, but realizes there could be a mess of visual dependencies in there
#16:32:59JMCraig has joined #evergreen
#16:33:06dbsthere were a few, but we'll kill them in time
#16:34:18agJohn has quit IRC
#16:34:26JMCraig is now known as agJohn
#16:34:39senatordbs: cool. your branch and two of mrp's now pushed
#16:34:46senatordbs: not to seek too bold a quid pro quo, but i was hoping you could eyeball this briefly: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/senator/org-is-mine-depth
#16:35:07senatorand just make sure it isn't insane, since i believe mfhd-based holdings in the jspac are your domain, no?
#16:36:31dbssenator: heh, yes, generally I commit a fix, and then dbwells commits a fix on top of that
#16:36:40berick throws collab/berick/tpac-unadorned-856-record-details into the mix and requests eyes
#16:37:18dbs has eyes fall out of skull
#16:37:24senatordbs: hehe. i think he and i do that to each other, too. here's the problem i'm trying to address: basically, the way it is now, using the stock org tree, let's say you're searching at br1, where you have an mfhd-based holding, you'll see that holding but no others. let's say you use the appropriate dropdown in the jspac to change your search depth to 0 (select "everywhere") aka top of tree
#16:37:51senatornothing changes, you still see your br1 holding, but no hypothetical br3 holding
#16:38:17dbsright - respect the "depth" parm, basically
#16:38:19senatorthis fixes that, unless "that" is not actually wrong in the first place, which is why i was hoping for your eyes on it
#16:38:26senatordbs: exactly
#16:38:44dbswhich traditionally I have been blind to because we have at times tried to prevent people from changing scope :)
#16:39:15dbsit looks good to me, I'll be happy to commit
#16:39:25senatorthanks!
#16:39:49senatordbs++
#16:39:53senatormrpeters-isl++
#16:39:59matt_carlson has joined #evergreen
#16:42:09dbwellssenator: dbs: here is some discussion on MFHD scoping from a few months ago. https://bugs.launchpad.net/evergreen/+bug/790905
#16:43:14senatordbwells: thanks. hmm, so that patch is already in... *rereads more carefully*
#16:43:39dbsdbwells: right. now we're fast-forwarding to "we might consider further emulating the copy scoping in cases where no MFHD would display at all, or a link to 'see all', but that can come later, probably even post TT-opac"
#16:43:59dbwellssenator: right, what dbs said
#16:44:18matt_carlson has quit IRC
#16:44:21Green_Hello I have installed evergreen but it is not working properly
#16:45:03Green_could any body help to trace out the problem
#16:45:14dbwellssenator: at that point we deliberately ignored depth, but I think it is sensible to include it now.
#16:45:15dbsGreen_: your login problem looks very much like you're not logging in with the user and password that you passed to the eg_db_config.pl script for --admin-user and --admin-pass arguments
#16:45:27senatordbwells: gotcha. so it sounds like i answered one of dbwells's questions (1b) but didn't address the others ?
#16:45:28dbsdbwells and senator: and it si done :)
#16:45:38senatordbs: thanks again
#16:46:13Green_how to know that user name and password
#16:46:19dbsI think keeping things as similar to copy scoping as possible makes the most sense, whatever I've said in the past :)
#16:46:24senatordbs: well, as long as we haven't been destructive, now i know to remember to consult that launchpad bug especially when contributing that part of tpac in anyway, since it fleshes out some of the important questions
#16:46:34senators/^dbs/dbwells/
#16:46:38senatoraye
#16:47:19dbsGreen_: you could run eg_db_config.pl again and just pass the --admin-user --admin-pass options and it will reset the administrator account user name and password to whatever you specify
#16:47:39Green_ok
#16:51:36mmorgan1 has joined #evergreen
#16:53:28mmorgan has quit IRC
#16:56:39Green_dbs_ :http://pastebin.ca/2086552
#16:57:01Green_if i run .i am getting this message
#16:57:46Green_could i reset the usernames and passwords
#16:58:30Green_are could i get which user names or which passwords are in use
#16:59:10Green_how to know which password is created for which user
#17:00:16jrodge01 has quit IRC
#17:02:28akilsdonk has quit IRC
#17:04:51raynerj has left #evergreen
#17:06:02abeNd-org has quit IRC
#17:07:43Green_dbs_:
#17:07:44Green_http://pastebin.ca/2086555
#17:08:06_bott_ has quit IRC
#17:08:59moodaepoGreen_: What do you get if you run Open-ILS/src/support-scripts/settings-tester.pl
#17:09:26Green_ok i will check it again
#17:09:38_bott_ has joined #evergreen
#17:10:02moodaepoAlso what dbs said was to just run Open-ILS/src/support-scripts/eg_db_config.pl --admin-user admin --admin-pass abc123
#17:10:36moodaepoNot the whole line mentioned in the installation instructions.
#17:10:43Green_http://pastebin.ca/2086556
#17:10:52matt_carlson has joined #evergreen
#17:11:17Green_if i run Open-ILS/src/support-scripts/settings-tester.pl i got that message
#17:13:26Green_if i run Open-ILS/src/support-scripts/eg_db_config.pl --admin-user admin --admin-pass abc123 i got this http://pastebin.ca/2086557
#17:13:57Shae has quit IRC
#17:14:31moodaepoGreen_: Yea I think your opensrf.conf has incorrect entries for db access
#17:14:40Green_ok
#17:15:09Green_so how to correct that
#17:15:42moodaepoIf this is a fresh install you may jest as well reset the db try running the following line which is the same as what you ran earlier but there was a typo
#17:15:43moodaepoperl Open-ILS/src/support-scripts/eg_db_config.pl --update-config --service all --create-schema --create-offline --user dell --password intel --hostname localhost --port 5432--database evergreen --admin-user evergreen --admin-pass centrino
#17:17:23moodaepoGreen_: One sec there was another typo in that command I just noticed
#17:17:35Green_ok
#17:17:50moodaepoYou need a space after --port 5432
#17:17:58Green_ok
#17:18:38Green_but this is not a fresh install ,i already installed it and now i am testing the connection
#17:19:05moodaepoDo you have any data in the system?
#17:19:49Green_no
#17:21:11moodaepoIn that case just (not jest like earlier : ) run the whole command, it will reset the db, update configs and setup the admin username/password (evergreen/centrino)
#17:21:14mmorgan1 has left #evergreen
#17:21:48Green_ok
#17:22:59kcollier has quit IRC
#17:30:19Dyrcona has quit IRC
#17:32:21hughbris has quit IRC
#17:32:48hughbris has joined #evergreen
#17:34:12hughbris has joined #evergreen
#17:37:54Green_i am getting still that old fatal error
#17:37:57Green_http://pastebin.ca/2086563
#17:39:30Green_where i was wrong
#17:39:46Green_where was i wrong
#17:40:29Green_moodaepo_
#17:40:43moodaepoGreen_: Are you sure the database access username and password are correct (evergreen/intel)?
#17:41:06Green_no i forgot those password and username
#17:41:13Green_how to get acess
#17:42:58moodaepoMight want to google on how to reset or create a new account in postgresql
#17:43:29dbsGreen_: you can always follow the step for "creating a PostgreSQL superuser" again
#17:44:37Green_ok
#17:44:55dbssudo su - postgres
#17:45:00agJohnGreen_: Another option is to log in as postgres:
#17:45:01agJohnsudo su - postgres
#17:45:02dbsdropuser evergreen # just in case it already exists
#17:45:03agJohn(Enter your password when prompted)
#17:45:04agJohnThen do this:
#17:45:06agJohnpsql evergreen
#17:45:07agJohnalter role evergreen password='newPasswd'
#17:45:13Green_ok
#17:45:27dbsthat's an option too
#17:45:33agJohnGreen_: As usual, dbs has the simplest method....
#17:45:34dbsknowledge is power
#17:45:56dbsagJohn's method is non-destructive
#17:46:37Green_ok
#17:47:49dbs wonders why "git pull" on the contrib/Conifer.git repo is dying with "Connection closed by 204.193.129.149 fatal: The remote end hung up unexpectedly"
#17:51:24dbsworked this time
#17:51:24dbs suspects contrib/Conifer has some really ugly stuff in it
#17:53:03dbs has never seen "git rebase" result in long long lists of "Applying: " stream past before
#17:53:22dbsreplaying all of Evergreen's history. crazy
#18:00:56agJohnSounds like it was determined to git ya ;-)
#18:07:00matt_carlson has quit IRC
#18:07:51Green_if i run the command dropuser evergreen i got this message
#18:07:52Green_http://pastebin.ca/2086567
#18:09:39dbsexcellent, then use agJohn's approach
#18:09:56Green_ok
#18:11:33Green_http://pastebin.ca/2086569
#18:11:34Green_Now i got this message
#18:11:35hughbris has quit IRC
#18:11:46Green_what is the next step
#18:13:01agJohnSorry. I left you haning in the middle of the process:
#18:13:03agJohnEnter these lines (the ; just invokes the command):
#18:13:04agJohn;
#18:13:06agJohn\q
#18:13:07agJohnYou'll be back at the Linux cmd line.
#18:13:27agJohnAt which point, enter:
#18:13:29agJohnexit
#18:13:31agJohnTo take you back to the original login.
#18:14:21agJohnperl Open-ILS/src/support-scripts/eg_db_config.pl with the correct logins and passwords.
#18:14:39Green_ok
#18:15:19agJohnBy the way, when you enter the ; to run the alter role command, the database should confirm that it worked by displaying a message similar to this:
#18:15:21agJohnALTER ROLE
#18:15:37agJohnThat means it worked. The \q just quits out of the psql program.
#18:15:41Green_yes
#18:15:47Green_ok
#18:16:39tsberedbs: I find that rebase only works well with things that were split off with git. Things that were split in the SVN days not so much.
#18:20:31dbs has quit IRC
#18:23:41matt_carlson has joined #evergreen
#18:25:53Green_good bye
#18:26:03Green_ has quit IRC
#18:27:53matt_carlson has quit IRC
#18:38:19abeNd-org has joined #evergreen
#19:05:20shadowspar has quit IRC
#19:06:23shadowspar has joined #evergreen
#19:29:40hughbris has joined #evergreen
#19:32:35shadowspar has quit IRC
#19:33:15shadowspar has joined #evergreen
#19:51:17hughbris has quit IRC
#19:52:05hughbris has joined #evergreen
#21:07:19dbs has joined #evergreen
#21:10:14tsbere has decided he dislikes working with 1.6
#21:10:37Dmagick_ has quit IRC
#21:10:37atz_ has quit IRC
#21:10:39denials has quit IRC
#21:10:49bwicksall has quit IRC
#21:10:51berick has quit IRC
#21:10:54sylvar has quit IRC
#21:10:57bjwebb has quit IRC
#21:10:58dkyle has quit IRC
#21:11:03csharp has quit IRC
#21:11:07mrpeters-isl has quit IRC
#21:11:09kbeswick has quit IRC
#21:13:05bjwebb has joined #evergreen
#21:13:05Dmagick_ has joined #evergreen
#21:13:05atz_ has joined #evergreen
#21:13:05sylvar has joined #evergreen
#21:13:05dkyle has joined #evergreen
#21:13:05denials has joined #evergreen
#21:13:05bwicksall has joined #evergreen
#21:13:05csharp has joined #evergreen
#21:13:05mrpeters-isl has joined #evergreen
#21:13:05berick has joined #evergreen
#21:13:05kbeswick has joined #evergreen
#21:14:27dbs weeps as apparently he didn't commit the "make dashboard be CSS instead of images" after all
#21:14:46dbsbut did manage to blow away his local branch
#21:14:48dbsbah
#21:19:04tsbereI love git at times.
#21:19:33tsbere was able to backport a commit by using git format-patch, editing the paths and wiping out a pile of changes that didn't apply, and then importing via git am
#21:20:14tsberegit didn't even find a single conflict, and I didn't touch the changes I left in the patch. :d
#21:20:17tsbere*:D
#21:20:55atz has joined #evergreen
#21:22:13dbs has merged berick's facets branch
#21:23:06atz_ has quit IRC
#21:23:19tsbere is working on backports based on the response dbs provided on the security list
#21:23:34dbs guessed as much, given the 1.6 reference
#21:24:12tsbereI touched one backport for 1.6. I don't think I am touching a second. The first was enough work.
#21:24:44dbstsbere++
#21:24:48dbsabove and beyond
#21:29:24eeevildbs: thoughts on https://bugs.launchpad.net/evergreen/+bug/865817 ? I know it's the 11th hour for 2.1, so no to that won't hurt my feelings, but getting it into master for testing and eventual merge for 2.1.1 would be good, I think
#21:31:44eeevilberick: where's the shwartzian transform, man?! ;)
#21:47:48bshumeeevil: Re: 865817, hand patched your changes into one of our 2.0 test servers earlier in the afternoon. Fwiw, I asked our catalogers and they liked the revised approach for displaying located URI's post-patch.
#21:48:20bshumI'll add something to that effect for the bug ticket history.
#21:54:29eeevilbshum: thanks!
#21:55:07bshumeeevil: Procedural question about that
#21:55:46berickeeevil: heh, which code you referring to?
#21:55:56bshumeeevil: Since you only wrote it for 2.1/master, would a request to have that backported to 2.0 be accompanied with a working branch of my own (I think I can write one up using your example), or ask you to do it, since it's your code :)
#21:56:15eeevilberick: the facet sort-by-count bit
#21:57:13eeevilbshum: I'll make a 2.0 branch, but merging that is a toss-up ... I'm not against it, mind you
#21:57:13berickah, yeah, the pile o' sorting
#21:58:34bshumeeevil: That's reasonable. Thanks!
#22:00:01dbsberick: user/dbs/tpac-dashboard2css @ working - recreated the dang commit
#22:01:40berickdbs: is that the change that was supposed to be in the gradients branch?
#22:02:02dbsberick: correctamundo
#22:02:35berick takes a look-see
#22:03:22tsbere has pushed a small collection of backported branches now
#22:03:53eeevilbshum: http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/miker/located_uri_visibility_fix_2_0
#22:04:15bshumeeevil++
#22:04:22bshumThanks again
#22:05:35tsberedbs: I took the approach of "avoid the feature-ish stuff when backporting". If you think I should backport more commits than I did, let me know. (I mentioned what I did/didn't backport in my email)
#22:05:47dbstsbere++ # you awesome
#22:08:06dbseeevil: I'd rather have the change in for 2.1.0 rather than change behaviour in 2.1.1
#22:08:13berickdbs: looks good. pushed. cleanup++
#22:08:22dbs will do a quick test and commit if it looks good
#22:09:04tsbere can't get his second dev machine to load a 1.6 schema properly, but is glad enough loaded to login and do a couple of other basic things via srfsh
#22:10:09phasefxtsbere: you mentioned something about POC code earlier today, what was that about? If it's a proof-of-concept exploit, I think we should avoid sharing such
#22:10:39dbsberick: i pushed one more commit to make the header less tall
#22:10:45abeNd-org has quit IRC
#22:11:36berick nods
#22:12:37berickvery nice
#22:12:40eeevildbs: I'd rather have it in 2.1.0 as well, fwiw
#22:28:45dbsclaiming 0631
#22:41:47dbscreating wrapped sql upgrade scripts still gives me the willies
#22:53:52tsbere dumps a potential email/whatever to the security list for when all the releases are, er, released
#23:01:31dbs finds the commit he had stashed away in a different local branch for the dashboard. ah well.
#23:14:00eeevilwould anyone else like to see some wasted horizontal space given to the facet sidebar, to hopefully avoid wrapping (slightly) long values?
#23:14:59eeevil dislikes the piles of whitespace in the center column, and along the right hand side of the action-y right-side blob
#23:21:52eeevil shouldn't have looked that closely ... I'm scarred for life
#23:24:36dbs pushes a 1-char fix to get the footer right on results/record display
#23:25:17dbseeevil: I don't want to play with fixed width layouts at all
#23:26:07mrpeters has joined #evergreen
#23:27:38dbseeevil: no doubt you love the table that's used for a single row in the search results summary
#23:28:17mrpeters2.1 cut already?
#23:29:04mrpetersdunno if this would affect a release, but either update_db.sh or 0631 seem to be broken -- http://pastie.org/2635716
#23:29:26mrpeterserr, still broken -- i know berick had patched it recently
#23:33:32dbsmrpeters: confirmed, update_db.sh seems to be broken to me too
#23:34:23mrpetersok just wanted to throw that out, since i thought 2.1 cutting was happening tonight
#23:34:37edoceo has quit IRC
#23:35:04mrpetersim thinking it may just need a -d $DBNAME instead of just $DBNAME
#23:35:07dbsanother two-character fix
#23:35:16dbsnope, that's not it
#23:35:21dbsone sec, I'll push a fix
#23:35:40mrpetersnow that's service! :)
#23:35:51mrpetersdbs++
#23:36:59dbsthanks for the headsup mrpeters
#23:37:04dbspushed
#23:37:09mrpetersnp
#23:37:11mrpeters sleeps
#23:37:35mrpeters has quit IRC
#23:49:12whyboston2 has quit IRC
< Sunday, October 2nd, 2011Raw Log FileTuesday, October 4th, 2011 >