Time |
Nick |
Message |
06:08 |
|
rlefaive joined #evergreen |
07:38 |
|
sarabee joined #evergreen |
07:57 |
|
rlefaive joined #evergreen |
07:58 |
|
rjackson_isl joined #evergreen |
07:58 |
|
rjackson_isl_ joined #evergreen |
08:02 |
|
rlefaive joined #evergreen |
08:23 |
|
mrpeters joined #evergreen |
08:59 |
|
krvmga joined #evergreen |
09:08 |
|
Dyrcona joined #evergreen |
09:15 |
|
Dyrcona joined #evergreen |
09:22 |
|
TaraC joined #evergreen |
09:23 |
|
yboston joined #evergreen |
09:28 |
kmlussier |
Good morning #evergreen! |
09:29 |
krvmga |
lol |
09:30 |
krvmga |
it's monday. |
09:30 |
krvmga |
evergreen monday |
09:30 |
krvmga |
but everything is going well |
09:30 |
kmlussier |
Yup! That means we should let the coffee flow freely in the channel today. |
09:31 |
krvmga |
except for those things that aren't |
09:31 |
kmlussier |
@coffee [someone] |
09:31 |
krvmga |
@coffee kmlussier |
09:31 |
krvmga |
i did that wrong, i think |
09:31 |
kmlussier |
pinesol_green apparently slept in. |
09:31 |
krvmga |
i'm going to walk to the lobby and refresh my coffee |
09:34 |
|
maryj joined #evergreen |
09:37 |
Dyrcona |
pinesol_green went bye bye last night, just before I signed off. |
09:37 |
Dyrcona |
kmlussier: If you read yesterday's logs, you'll see me mentioning something in the afternoon that jeff commented on. |
09:38 |
Dyrcona |
kmlussier: It will explain why circulation is currently busted on my development vm. :) |
09:38 |
Dyrcona |
So, if you're trying to test anything there today, be warned.... |
09:40 |
Dyrcona |
I probably won't get around to fixing it until tomorrow. |
09:51 |
kmlussier |
Dyrcona: If I like at anything today, it will be cataloging in the web client, so I'm good. |
09:51 |
kmlussier |
Thanks! |
09:58 |
|
pinesol_green joined #evergreen |
09:59 |
jeff |
@coffee pinesol_green |
09:59 |
* bshum |
woke pinesol |
09:59 |
* pinesol_green |
brews and pours a cup of Bolivia Caranavi Cenaproc Co-op, and sends it sliding down the bar to pinesol_green |
10:00 |
bshum |
Not sure why it died this time around either... |
10:01 |
kmlussier |
@coffee [someone] |
10:01 |
* pinesol_green |
brews and pours a cup of Colombia Granja La Esperanza Geisha, and sends it sliding down the bar to sarabee |
10:01 |
kmlussier |
pinesol_green++ |
10:02 |
|
rlefaive joined #evergreen |
10:30 |
|
abowling joined #evergreen |
10:47 |
Bmagic |
@coffee giveittome |
10:47 |
* pinesol_green |
brews and pours a cup of Panama Esmeralda Lot 9, and sends it sliding down the bar to giveittome |
11:23 |
|
sandbergja joined #evergreen |
11:35 |
|
ericar joined #evergreen |
11:56 |
|
rlefaive joined #evergreen |
12:04 |
|
jihpringle joined #evergreen |
12:07 |
gmcharlt |
berick++ # testing stuff even before a pullrequest tag gets applied! |
12:09 |
berick |
gmcharlt: some code is hard to resist :) |
12:11 |
|
graced joined #evergreen |
12:15 |
|
b_bonner_ joined #evergreen |
12:19 |
Dyrcona |
@who wants to be at work today |
12:19 |
pinesol_green |
mmorgan1 wants to be at work today. |
12:21 |
mmorgan1 |
Heh. |
12:23 |
* mmorgan |
on the other hand, may not been quite as enthusiastic ;-) |
12:23 |
mmorgan |
s/been/have been |
12:23 |
mmorgan |
Mondays-- |
12:24 |
Dyrcona |
heh |
12:24 |
mmorgan |
@tea Dyrcona |
12:24 |
* pinesol_green |
brews and pours a pot of Honey Black Tea, and sends it sliding down the bar to Dyrcona (http://ratetea.com/tea/health-and-tea/honey-black-tea/7529/) |
12:24 |
Dyrcona |
Thank you. |
12:24 |
Dyrcona |
:) |
12:42 |
|
jihpringle joined #evergreen |
13:02 |
|
collum joined #evergreen |
13:14 |
* Dyrcona |
wishes he had the power to edit a lp comment.... I said things that wrong. |
13:15 |
Dyrcona |
Hmm... Maybe I do have that power..... |
13:22 |
Dyrcona |
Well, sort of. |
13:22 |
kmlussier |
@eightball Does Dyrcona have the power? |
13:22 |
pinesol_green |
kmlussier: The answer is a resounding no. |
13:22 |
kmlussier |
Ha ha ha! |
13:22 |
Dyrcona |
Heh. |
13:22 |
Dyrcona |
I hid the comment. |
13:22 |
dbs |
@eightball Does Greyskull have the power? |
13:22 |
pinesol_green |
dbs: It shall be. |
13:27 |
Dyrcona |
Comment #2 has the straight dope: https://bugs.launchpad.net/evergreen/+bug/1350916/comments/2 |
13:27 |
pinesol_green |
Launchpad bug 1350916 in Evergreen "Use -i in marc_export exclude records with located URIs.should at least include records with located URIs" [Wishlist,Triaged] |
13:27 |
|
gmcharlt joined #evergreen |
13:27 |
Dyrcona |
Thought that I'd look at some of the marc_export bugs since I'm poking around in there anyway. |
14:37 |
|
mllewellyn joined #evergreen |
15:38 |
Bmagic |
anyone online to help troubleshoot the git working repo logs with my push? |
15:40 |
dbs |
For a few minutes |
15:40 |
dbs |
oh wait, I don't think I have access to the logs |
15:40 |
dbs |
Bmagic: what's happening? |
15:40 |
Bmagic |
The remote end hung up unexpectedly |
15:41 |
Bmagic |
I'm sure it's the chmod of my private key, but I have been playing with it for over an hour. I wonder what the logs say on the server side |
15:41 |
dbs |
git push -vv <blah> ; show anything more? |
15:41 |
Bmagic |
not really |
15:42 |
Bmagic |
it adds one line |
15:42 |
Bmagic |
Pushing to git://git.evergreen-ils.org/working/Evergreen.git |
15:42 |
jeff |
you won't be able to push to that url. |
15:42 |
dbs |
yeah |
15:42 |
Bmagic |
oh? |
15:42 |
Bmagic |
dang |
15:42 |
dbs |
you need git@ |
15:42 |
Bmagic |
jeees, that simple eh!? |
15:43 |
dbs |
working gitgit.evergreen-ils.org:working/Evergreen.git (push) |
15:43 |
dbs |
(from my "git remote -v") |
15:43 |
jeff |
assuming your working repo remote is called "working", this may help: git remote set-url --push working gitgit.evergreen-ils.org:working/Evergreen.git |
15:43 |
dbs |
jeff++ |
15:44 |
Bmagic |
so, git remote add -f working git://git.evergreen-ils.org/working/Evergreen.git then git remote set-url --push working gitgit.evergreen-ils.org:working/Evergreen.git ? |
15:44 |
* dbs |
heads out as threatened |
15:49 |
jeff |
Bmagic: did the command i offered fail? |
15:49 |
Bmagic |
jeff: yep! I had forgot that step apparently |
15:50 |
jeff |
easy to miss til now if this was your first attempt to push to that remote from that local working copy. |
15:50 |
Bmagic |
yeah, new linux machine |
15:54 |
csharp |
linux++ |
15:56 |
Bmagic |
linux++ |
15:56 |
Bmagic |
@later tell jboyer-isl http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/blake/LP1496522_action_trigger_for_periodic_billing_statement |
15:56 |
pinesol_green |
Bmagic: The operation succeeded. |
15:57 |
Bmagic |
windows10++ |
15:57 |
Bmagic |
j/k windows10-- |
15:58 |
bshum |
If you're setting up from scratch, you could do "git remote add working gitgit.evergreen-ils.org:working/Evergreen.git" straight up too. One command instead of two, works for me anyways. |
15:59 |
* Dyrcona |
like to set different URLs..... |
15:59 |
Dyrcona |
for instance, pull from one repo and push to another. :) |
16:00 |
bshum |
That's probably good. |
16:00 |
bshum |
I use different remotes, for origin to make that read-only and a remote called "Community" where I actually can push to. So that I consciously decide to push something up. |
16:00 |
Dyrcona |
That's handy if you have a local copy of the community repo that you pull from, and you want to push to the community repo. |
16:00 |
bshum |
working is just working to me though, blow it up :P |
16:01 |
Dyrcona |
Well, yeah, for working, it doesn't make a whole lot of sense. |
16:01 |
Dyrcona |
I also have one remote, where the local is an empty git repo on my laptop, and the push is my development vm. |
16:02 |
Dyrcona |
That way, if dev is shut down and I fetch, I don't have to wait on it to timeout. |
16:02 |
jeff |
having the push and pull url for a given remote not point at "the same place" (i.e., point at two completely different instances of a repo) is cautioned against in the git documentation. :-) |
16:02 |
Dyrcona |
And, I can push to the remote to distribute the changes for testing. |
16:03 |
jeff |
But it's mostly a "you break it, you fix it" kind of thing. |
16:03 |
Dyrcona |
jeff: of course it is, 'cause it can get confusing if you don't pay attention. |
16:03 |
Dyrcona |
I like the local bare repo trick for pull and something on a vm for push to distribute changes, though. Very handy. |
16:03 |
jeff |
There is support for multiple URLs, but how that behaves isn't well documented in the man page for git-remote. I don't know if it would work, for example to add a non-ssh method as a fallback for pulls. |
16:04 |
Dyrcona |
Well, in my case, I never want to pull anything from that remote. I consider it push-only. |
16:04 |
Dyrcona |
With an empty repo, you can share it with other projects/repos where you want the same setup, for instance OpenSRF and Evergreen. |
16:06 |
Dyrcona |
So, my jasondev repos both pull from ~/src/empty.git/, and push to OpenSRF and Evergreen on my dev vm. |
16:20 |
|
jlitrell joined #evergreen |
16:29 |
Bmagic |
I just had a call with a branch who claims that their "first-time" patrons need to enter their password before* their username in the OPAC in order to log in! Anyone heard of that? |
16:30 |
Bmagic |
Aparently, if you type your username into the box and then click the password box, the OPAC will reload and send the page back to home. |
16:30 |
Bmagic |
Unless, you have logged in before! |
16:38 |
mmorgan |
Bmagic: I have not had reports of that. Could it be a browser thing? Type in the username, press enter key trying to get to the password tab, but the enter acts like "Submit"? |
16:39 |
Bmagic |
yeah, totally bizzare, I cannot think of a scenario where that would happen! I just thought I would float it here in case someone had an idea. For now, we are going to close the books on this one! lol |
16:40 |
Dyrcona |
Sounds like bad folk lore to me. |
16:41 |
Bmagic |
ah! More information here, I was playing around with it. If you press enter after typing the username, the page reloads with no error message |
16:41 |
mmorgan |
That's the enter key submitting the form. |
16:43 |
mmorgan |
But a message would be useful there, telling the user they didn't enter both a username and password. |
16:44 |
Bmagic |
well, yeah. I think there was a breakdown in communication, when they said "main screen" I assumed home, but I think it was probably the login form again |
16:44 |
|
ericar joined #evergreen |
17:01 |
kmlussier |
In the xul client, we have a price field in the copy editor. In the web client, there is a price and a cost field. Anyone know what that's all about? |
17:02 |
Bmagic |
I was wondering that too |
17:02 |
Bmagic |
I just noticed it as a database column, and trained myself to know that it's price that we are using. |
17:03 |
Bmagic |
I suppose the cost is the real cost, and the price is for the patron billing? |
17:05 |
mmorgan |
I noticed the cost column in the db a while back. Don't quote me on this, but my memory tells me the cost field gets populated from acquisitions somehow. |
17:13 |
bshum |
It's acquisitions, yeah |
17:13 |
bshum |
In theory, cost is supposed to contain the actual cost of the material as per what acq says (though I'm unsure if the loaders/PO stuff actually pay attention to this or not) |
17:14 |
bshum |
And price is what displays to everybody else. |
17:14 |
bshum |
And gets charged by the system when applying lost fees, etc. |
17:14 |
bshum |
Or could be, if you're setup that way |
17:14 |
* bshum |
wanders away to go find some dinner. |
17:27 |
|
mmorgan left #evergreen |
18:02 |
|
dcook joined #evergreen |
18:30 |
|
mrpeters left #evergreen |
20:10 |
kmlussier |
Thanks bshum and mmorgan. I suspected it was related to acq, but wasn't sure. So it looks like we're making the data more visible when we move to the web client. |
20:10 |
kmlussier |
@librarian |
20:10 |
pinesol_green |
kmlussier: Management:12, Cataloging:11, Acquisitions:11, Reference:11, Circulation:12, Systems:10, Research:10, Custodial:11 |
23:40 |
|
StomproJ joined #evergreen |