Time |
Nick |
Message |
00:59 |
|
dbwells__ joined #evergreen |
01:01 |
|
j_scott joined #evergreen |
02:12 |
|
Bmagic|2 joined #evergreen |
02:32 |
|
RBecker joined #evergreen |
02:32 |
|
linuxhiker_away joined #evergreen |
02:33 |
|
jboyer_isl joined #evergreen |
02:43 |
|
dbwells_ joined #evergreen |
03:05 |
|
jeff joined #evergreen |
03:28 |
|
saravanakumar joined #evergreen |
05:17 |
saravanakumar |
Hello everyone i am pasted my error in this link http://paste.evergreen-ils.org/46 |
08:08 |
|
akilsdonk joined #evergreen |
08:34 |
|
Shae joined #evergreen |
08:43 |
|
_bott_ joined #evergreen |
09:01 |
|
krvmga joined #evergreen |
09:56 |
|
mllewellyn joined #evergreen |
09:57 |
|
Guest81527 joined #evergreen |
10:04 |
phasefx_ |
saravanakumar: yeah, I'm stumped. What version of apache? |
10:05 |
bshum |
That's something I was wondering. Which OS/apache versions involved. |
10:08 |
saravanakumar |
Server version: Apache/2.2.22 (Ubuntu) |
10:08 |
saravanakumar |
Ubuntu 12.04.2 LTS \n \l |
10:09 |
bshum |
Well that's not unusual. |
10:09 |
bshum |
Hmm |
10:10 |
saravanakumar |
yes .... |
10:10 |
tsbere |
Lack of perl modules, perhaps? I know when I didn't have business::issn, I think it was, eg_startup failed... |
10:11 |
saravanakumar |
i beleive ... if its lack of perl module it should say unable to fine something.pm |
10:11 |
saravanakumar |
find* |
10:12 |
tsbere |
I find that varies with log levels and such, and at least once I found those entries made it into an entirely different log file. :/ |
10:17 |
phasefx_ |
for giggles, you could make a barebones eg_startup with no perl modules just to see if it gets past that step |
10:17 |
phasefx_ |
EG won't work with it, of course, but it'd be useful information |
10:20 |
tsbere |
Hmmm |
10:20 |
tsbere |
How about running "perl /etc/apache2/eg_startup" outright? Any missing modules should be reported then |
10:21 |
tsbere |
Oh, other possibilities: Incorrect user on apache, so permissions aren't letting eg_startup read the config file(s)? |
10:24 |
phasefx_ |
here's their earlier paste: http://paste.evergreen-ils.org/45 |
10:24 |
phasefx_ |
I tried giving my file all those read/write/execute permissions just to see if apache would complain, and it didn't |
10:25 |
tsbere |
What about envvars and apache_run_user, or are we no longer supposed to need to change that? |
10:26 |
bshum |
It's supposed to be opensrf |
10:27 |
bshum |
For the time being |
10:33 |
|
RoganH joined #evergreen |
10:41 |
saravanakumar |
i am running as opensrf user |
10:49 |
phasefx_ |
saravanakumar: I would try that experiment tsbere mentioned, as user opensrf, perl /etc/apache2/eg_startup You should get no output |
11:02 |
saravanakumar |
okay le me check |
11:09 |
|
smyers_ joined #evergreen |
11:10 |
bshum |
Hmm, I wonder how hard it'd be to export to RefWorks with a list (bookbag, bucket, whatever it's called) instead of doing it individually record by record via the link in details. |
11:11 |
mrpeters |
saravanakumar: we've asked several times....please paste the output of this command ---- ls -ltrh /etc/apache2 |
11:12 |
mrpeters |
oops....i was scrolled up too far didn't see the replies already |
11:12 |
mrpeters |
saravanakumar: what version of Evergreen are you installing? |
11:13 |
* mrpeters |
reminds everyone of http://archive.georgialibraries.org/ if you want to install a stock 2.5.1 with apt-get |
11:19 |
saravanakumar |
thanks phasefx when i ran perl /etc/apache2/eg_startup i given two dependencies error Bussiness & SRU/Request.pm |
11:19 |
saravanakumar |
now its loaded into apache |
11:20 |
saravanakumar |
Thanks a lot for your patience and kind help |
11:21 |
saravanakumar |
mrpeters i have pasted and pasted the link to by yesterday itself |
11:21 |
saravanakumar |
http://paste.evergreen-ils.org/46 |
11:22 |
saravanakumar |
now i am getting the error Exception: OpenSRF::EX 2013-12-27T11:21:34 main -e:0 : No ils_events file found in settings config\n |
11:23 |
saravanakumar |
http://paste.evergreen-ils.org/45 |
11:23 |
mrpeters |
saravanakumar: reinstall ubuntu and use the repo :P |
11:23 |
mrpeters |
you'll be up and running to play around in no time! |
11:24 |
mrpeters |
and then you can examine the configuration to see what you might have missed (permissions, etc.) |
11:25 |
bshum |
saravanakumar: When you said Ubuntu 12.04 LTS earlier, was that desktop or server? Or some other flavoring |
11:25 |
mrpeters |
^^ good question bshum |
11:25 |
saravanakumar |
its a desktop bshum |
11:26 |
saravanakumar |
but we are using it as testing machine |
11:26 |
bshum |
Evergreen was only tested and supported with the server editions, so I don't know if there's quirks at play with others (though missing dependencies seems like bad install problems) |
11:26 |
saravanakumar |
hmm |
11:26 |
bshum |
I know there's been reported troubles by others in the past with desktop edition of ubuntu. |
11:26 |
saravanakumar |
but its 64bit machine |
11:26 |
bshum |
Since it's not supported for Evergreen, we've skipped most of it. |
11:29 |
bshum |
But basically, Evergreen is well tested (and running) with libraries on Ubuntu 12.04 LTS server, the 64-bit edition. |
11:29 |
bshum |
I don't think we test at all with 32-bit anymore. And not for desktop edition. |
11:30 |
mrpeters |
install ubuntu server 12.04 and add a desktop environment later if you need it |
11:35 |
bshum |
The missing deps above make me nervous that something went screwy with the Makefile.install ; which wouldn't surprise me if it blew up over the wrong edition of Ubuntu :( |
12:20 |
saravanakumar |
ubuntu has same kernel for server and desktop environment from 12.04. So that should work on desktop env too |
12:20 |
tsbere |
saravanakumar: The problem is more "we expect the server packages, not the desktop packages" |
12:21 |
tsbere |
aka, they install different things by default, and desktop isn't "server plus GUI" |
12:23 |
saravanakumar |
okay so please include this in your documentation.. |
12:23 |
mrpeters |
ehhh...i think its pretty obvious that you'd need a server OS |
12:24 |
mrpeters |
http://docs.evergreen-ils.org/2.5/_system_requirements.html#_server_minimum_requirements |
12:24 |
mrpeters |
"Server" is pretty clearly stated |
12:24 |
tsbere |
maybe we should remove the "desktop" from "An available desktop, server or virtual image" |
12:25 |
mrpeters |
well, it can be a desktop pc |
12:25 |
mrpeters |
just needs a server OS |
12:25 |
mrpeters |
im sure we could ask dig to clarify, but i don't think this has come up before |
12:25 |
saravanakumar |
Yes please remove desktop from your documentation |
12:26 |
mrpeters |
saravanakumar: a desktop is perfectly valid...you could take an old P4 desktop with 2GB of ram and run evergreen on it, you just have to install Ubuntu/Debian/Fedora/etc. SERVER |
12:27 |
tsbere |
Perhaps change "Linux Operating System" to "Linux Server Operating System" then? |
12:27 |
mrpeters |
tsbere++ |
12:27 |
saravanakumar |
mrpeters i understand please add like "Operating system should be server operating sysem" |
12:27 |
mrpeters |
im sure DIG can hook that up |
12:34 |
bshum |
DIG = Documentation Interest Group. |
12:35 |
bshum |
For saravanakumar: The Evergreen community has several volunteer groups and committees, one of which handles documentation interests. |
12:43 |
phasefx_ |
we mention specific operating systems in the pre-req fetching step; maybe need to emphasize those? |
12:43 |
bshum |
Maybe we should add a new preamble section to the README that states from the get go which Linux distributions are considered supported. (kind of like what was put in the release notes for OpenSRF 2.2 series) |
12:44 |
bshum |
And also refactor the OpenSRF README to be more specific |
12:44 |
bshum |
Evergreen README / OpenSRF README |
12:44 |
bshum |
Gah :0 |
12:45 |
phasefx_ |
maybe have a prominently linked compatability page |
12:46 |
phasefx_ |
and linked bugs for anything specific to a server, device, browser, etc. |
12:47 |
bshum |
Something to ponder for 3.0. |
12:47 |
bshum |
:) |
12:52 |
phasefx_ |
anyone running a wheezy server? |
12:53 |
bshum |
Not presently. |
12:53 |
phasefx_ |
this is driving me nuts: http://paste.evergreen-ils.org/47 |
12:54 |
phasefx_ |
that Cannot determine local time zone is happening with the perl live tests in EG on this one server |
12:54 |
phasefx_ |
http://testing.evergreen-ils.org/~live/test.22.html |
13:01 |
* phasefx_ |
will try an earlier version of DateTime::Timezone |
13:03 |
bshum |
I was about to ask, what's the expected output supposed to be? |
13:03 |
bshum |
My Ubuntu test server listed 0.70 and 1.42 for versions, respectively. |
13:03 |
bshum |
But the output lines following were just the directory I was in, twice. |
13:04 |
phasefx_ |
on my squeeze system: DateTime->VERSION 0.61 / DateTime::TimeZone->VERSION 1.20 / /home/opensrf / /home/opensrf |
13:04 |
phasefx_ |
no errors |
13:04 |
bshum |
I see, so it's supposed to show nothing. Got it :) |
13:10 |
phasefx_ |
okay, so an old snapshot of wheezy, prior to an apt-get update, I have versions 0.75 and and 1.58 with no errors |
13:10 |
* phasefx_ |
tries updating |
13:11 |
bshum |
What's in /etc/timezone on your unhappy server? :) |
13:12 |
bshum |
(just curious) |
13:12 |
phasefx_ |
SystemV/EST5 |
13:12 |
phasefx_ |
alright, after an upgrade, that perl snippet reports the same versions but we get the error. The debian version of datetime::timezone did go up |
13:13 |
phasefx_ |
from 1:1.58-1+2013c to 1:1.58-1+2013h |
13:14 |
phasefx_ |
debian changelog shows updates to an "Olson database" |
13:15 |
phasefx_ |
I don't know if this affects anything other than the local server-side perl tests |
13:15 |
phasefx_ |
well, it does affect srfsh |
13:15 |
phasefx_ |
if doing a checkout.full through it |
13:17 |
phasefx_ |
is simply changing the conents of /etc/timezone a sane thing to try? <tries it anyway> |
13:17 |
phasefx_ |
ha, that worked |
13:17 |
phasefx_ |
changed it to America/New_York |
13:18 |
phasefx_ |
bshum++ |
13:18 |
bshum |
Oh cool |
13:18 |
bshum |
I was off googling SystemV/ESTS |
13:18 |
bshum |
I had no clue what that meant :) |
13:18 |
phasefx_ |
EST5 |
13:18 |
eeevil |
yeah, EST5 is not an olson format tz |
13:20 |
eeevil |
i guess debian got a bit more strict in their tz db update for dt::tz... |
13:21 |
phasefx_ |
probably worth adding a variation of that perl snippet to settings-tester |
13:21 |
phasefx_ |
or a perl live test |
13:27 |
|
mceraso joined #evergreen |
13:27 |
|
bshum joined #evergreen |
13:30 |
|
kmlussier joined #evergreen |
14:16 |
bshum |
phasefx++ |
14:47 |
|
stevenyvr2 joined #evergreen |
15:06 |
* jeff |
creates some working branches for user editor bugfixes and improvements |
15:10 |
* bshum |
likes the sound of that |
15:12 |
jeff |
believe they're all tagged "usereditor": https://bugs.launchpad.net/evergreen/+bugs?field.tag=usereditor |
15:12 |
jeff |
just added working branch and pullrequest tag on 1246846 |
15:12 |
jeff |
bug 1246846 |
15:12 |
pinesol_green |
Launchpad bug 1246846 in Evergreen "User editor considers an empty username as valid" (affected: 1, heat: 6) [Medium,In progress] https://launchpad.net/bugs/1246846 |
15:16 |
jeff |
and bug 1246836 |
15:16 |
pinesol_green |
Launchpad bug 1246836 in Evergreen "Duplicate username detection can false positive on the current user" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1246836 |
15:16 |
jeff |
some of these are not at all exciting. :-) |
15:17 |
* bshum |
likes good bug fixes either way |
15:17 |
bshum |
jeff++ |
15:20 |
jeff |
bug 1246843 |
15:20 |
pinesol_green |
Launchpad bug 1246843 in Evergreen "Contact invalidators show in user editor for staged/cloned users" (affected: 1, heat: 6) [Undecided,New] https://launchpad.net/bugs/1246843 |
15:25 |
jeff |
for bugfixes, should i target to 2.4.5 and 2.5.2 and leave untargeted for 2.next, or target all three? |
15:27 |
bshum |
jeff: What I've been doing is to target the main bug at 2.5.whichever, since 2.next hasn't had a plan laid out yet. |
15:27 |
jeff |
got it. |
15:27 |
jeff |
so target a bugfix toward 2.4.5 and 2.5.2 only |
15:28 |
bshum |
Yes. |
15:29 |
jeff |
hrm. is there a secret to targeting one bug at multiple milestones? |
15:30 |
jeff |
"also affects project" and select evergreen again with a different milestone? |
15:30 |
tsbere |
multiple version indicators |
15:30 |
jeff |
or am i thinking about this the wrong way? |
15:30 |
bshum |
"Target to series" |
15:30 |
bshum |
Is the link you want |
15:31 |
bshum |
If you don't have it, then... hmm, maybe we haven't promoted you high enough in the bug food chain yet. |
15:31 |
jeff |
i have it. |
15:31 |
jeff |
so for target to series, pick 2.4, 2.5, and master? |
15:31 |
jeff |
using bug 1246846 as an example |
15:31 |
pinesol_green |
Launchpad bug 1246846 in Evergreen "User editor considers an empty username as valid" (affected: 1, heat: 6) [Medium,In progress] https://launchpad.net/bugs/1246846 |
15:32 |
bshum |
My tendency is to only target the backport target |
15:32 |
bshum |
So in that case, 2.4 |
15:33 |
bshum |
Assigning to 2.5 series would be fine too; just means it'll create another line for it. |
15:33 |
bshum |
Which you could assign two lines to the same milestone, but I always thought that looked funky :) |
15:35 |
jeff |
oh. i think i get it. |
15:36 |
jeff |
hah! now i can't "un" target to series |
15:36 |
bshum |
The little red minus symbol next to the series number should untarget it |
15:37 |
bshum |
untarget/delete |
15:37 |
jeff |
ah! got it. |
15:37 |
bshum |
Don't forget to set the status too, since you're at it :) |
15:38 |
bshum |
jeff: See - http://evergreen-ils.org/dokuwiki/doku.php?id=dev:bug_wrangler:faq |
15:38 |
jeff |
okay, so https://bugs.launchpad.net/evergreen/+bug/1246846 is i think set from a launchpad milestone/series standpoint |
15:38 |
pinesol_green |
Launchpad bug 1246846 in Evergreen 2.4 "User editor considers an empty username as valid" (affected: 1, heat: 6) [Medium,In progress] |
15:38 |
jeff |
bshum: doh. i should have reviewed that first! |
15:38 |
* bshum |
chuckles lightly at the section for Milestones |
15:38 |
bshum |
"Needs expansion" |
15:39 |
jeff |
heh. i just saw that also. :-) |
15:40 |
bshum |
I think that's one of the many long-standing things I'm supposed to work on before the next dev meeting. |
15:40 |
bshum |
:( |
15:41 |
jeff |
so does the bug i just linked look correct? the "Evergreen" series has a milestone of 2.5.2, and the "2.4" series has a milestone of 2.4.5? |
15:41 |
bshum |
That'll work. |
15:42 |
jeff |
and does that mesh with yours and tsbere's usual practice in terms of "tendency is to only target the backport target"? |
15:42 |
bshum |
Yeah, that's good for me. |
15:42 |
jeff |
i'd rather not create my own unique way of doing things -- better IMO to use launchpad the way others are. |
15:43 |
* bshum |
is still not sure he's using it the right way either. |
15:43 |
tsbere |
jeff: I have no usual practice. I avoid versions, focusing only on master. <_< |
16:19 |
jeff |
meanwhile, a wishlist bug like bug 1246853 -- should not target 2.4 and not even 2.5, since it isn't a bugfix? |
16:19 |
pinesol_green |
Launchpad bug 1246853 in Evergreen "Add button in user editor to update expire date" (affected: 1, heat: 6) [Wishlist,In progress] https://launchpad.net/bugs/1246853 |
16:22 |
bshum |
jeff: Yes, that would fit better towards 2.next |
16:22 |
jeff |
should i target it, or leave it untargeted, but with pullrequest tag? |
16:23 |
bshum |
Target it if it's ready. Pullrequest tagged tickets without targets have a tendency to disappear |
16:24 |
jeff |
targeted. |
19:14 |
|
stevenyvr2 left #evergreen |
23:04 |
|
stevenyvr2 joined #evergreen |
23:12 |
|
stevenyvr2 left #evergreen |