Time |
Nick |
Message |
04:57 |
|
gk-1wm-su joined #evergreen |
05:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
07:10 |
|
rjackson_isl joined #evergreen |
07:31 |
|
agoben joined #evergreen |
07:33 |
|
kmlussier joined #evergreen |
08:43 |
|
mmorgan joined #evergreen |
08:48 |
|
bos20k joined #evergreen |
09:00 |
|
NawJo joined #evergreen |
09:05 |
|
mmorgan1 joined #evergreen |
09:13 |
|
collum joined #evergreen |
09:15 |
|
mmorgan joined #evergreen |
09:19 |
|
yboston joined #evergreen |
09:20 |
|
rlefaive joined #evergreen |
09:23 |
|
terran joined #evergreen |
09:48 |
|
mmorgan1 joined #evergreen |
10:00 |
|
rlefaive_ joined #evergreen |
10:33 |
|
maryj joined #evergreen |
10:42 |
|
Dyrcona joined #evergreen |
10:49 |
|
rlefaive joined #evergreen |
10:52 |
Dyrcona |
Heh. There's a package called python3-itsdangerous. |
11:02 |
bshum |
That's awesome Dyrcona. :) |
11:15 |
|
NawJO_ joined #evergreen |
11:31 |
|
khuckins joined #evergreen |
11:46 |
bshum |
Hmmmm, https://github.com/phhusson/quassel-irssi |
11:49 |
Stompro |
When changing the bib source on a title, is a reingest needed for visibility changes to be seen, or is it a memcache results cache of some sort that I need to wait to time out? |
11:51 |
berick |
Stompro: catalog searches are temporarily cached |
11:51 |
berick |
you can bypass the cache with minor search tweaks, though, to test |
11:51 |
berick |
like foo -zzzzzz |
11:54 |
Stompro |
berick, thanks. |
12:02 |
|
brahmina joined #evergreen |
12:10 |
|
mmorgan joined #evergreen |
12:16 |
|
rlefaive joined #evergreen |
12:23 |
|
jihpringle joined #evergreen |
12:32 |
|
sandbergja joined #evergreen |
12:37 |
kmlussier |
It's a good thing my regular work is putting me on Launchpad this week. Otherwise, I would be doing nothing for Bug Squashing week. |
12:38 |
* mmorgan |
is pulling on bug squashing galloshes as we speak :) |
12:42 |
|
mmorgan1 joined #evergreen |
12:57 |
kmlussier |
@hates |
12:57 |
pinesol_green |
kmlussier hates Launchpad search; Internet Explorer; snow; scheduling meetings; Starbucks; negative balances; undrinkable coffee; winter; blizzards; spam; dojo interfaces; Windows line endings; peanut M&Ms; and bad technology days |
12:58 |
kmlussier |
@hate authorities |
12:58 |
pinesol_green |
kmlussier: The operation succeeded. kmlussier hates authorities. |
12:59 |
kmlussier |
The singular form would work there too. |
13:00 |
Bmagic |
@hates |
13:00 |
pinesol_green |
Bmagic hates marc |
13:00 |
Dyrcona |
@hates |
13:00 |
pinesol_green |
Dyrcona hates MARC; Launchpad Search; and printing |
13:01 |
Dyrcona |
I deleted some. :) |
13:01 |
Bmagic |
I like kmlussier 's list more |
13:01 |
Bmagic |
lol, Windows line endings |
13:02 |
Bmagic |
kmlussier: do you like marc? |
13:03 |
Bmagic |
pinesol_green needs a call to parse everyone's list and show the differences |
13:03 |
pinesol_green |
Bmagic: Thank you Bmagic! But our princess is in another castle! |
13:03 |
kmlussier |
Bmagic: I don't have much feeling one way or another for MARC. I don't hate it as much as most people in here do. |
13:03 |
pinesol_green |
Bmagic: I am only a bot, please don't think I'm intelligent :) |
13:03 |
kmlussier |
@loves |
13:03 |
pinesol_green |
kmlussier loves parts; YAOUS; Fridays; clam chowder; coffee; new fanged email thing; quassel; magic eightball; trivia; Evergreeners; BBQ; spell check; mobile catalog; new edit links in the catalog; vim; pizza; grep; spring; summer; fall; clam chowdah; ginger beer; DokuWiki; the random magic spells page; Evergreen, the whole kit and caboodle; bug squashing day; acq; reducing mouse clicks; (1 more message) |
13:03 |
kmlussier |
@more |
13:03 |
pinesol_green |
kmlussier: quickpick; developers who bring us the features we need just when we need them; git; IRC practice time; git quickpick; and rolos |
13:03 |
kmlussier |
@love bug squashing week |
13:03 |
pinesol_green |
kmlussier: The operation succeeded. kmlussier loves bug squashing week. |
13:04 |
Bmagic |
"Evergreen, the whole kit and caboodle" |
13:05 |
bshum |
Sounds like a great title for someone's memoirs |
13:05 |
bshum |
Well, maybe a chapter or two ;) |
13:05 |
Bmagic |
@love Resistance |
13:05 |
pinesol_green |
Bmagic: The operation succeeded. Bmagic loves Resistance. |
13:34 |
|
rlefaive joined #evergreen |
13:51 |
|
mmorgan joined #evergreen |
14:30 |
Bmagic |
so, I am attempting to add other language support to my installation of Evergreen for the first time. I'm having trouble connecting the dots. |
14:30 |
Bmagic |
http://docs.evergreen-ils.org/2.9/_setting_a_default_language_and_adding_optional_languages.html |
14:30 |
|
rlefaive joined #evergreen |
14:31 |
Bmagic |
tells me that all I need to do is add three lines to eg.conf - but my installation of Evergreen does not contain a directory here /openils/var/data/local |
14:32 |
Bmagic |
Leads me to the conclusion that I need to add some switches to the ./configure or perhaps the make command? |
14:32 |
berick |
Bmagic: did you install directly from git or tarball? |
14:32 |
Bmagic |
git |
14:33 |
berick |
in that case you'll have to build the locale files. i don't remember all the steps OTTOMH, but you can see what make_release does |
14:35 |
berick |
may have to add some dependencies for building those, like the 'packager' Makefile.install target |
14:36 |
Bmagic |
alright, I will see what I can find |
14:37 |
Bmagic |
thanks for pointing me in the right direction! |
14:45 |
bshum |
Bmagic: I think I wrote up a quicker example |
14:45 |
Bmagic |
I found this one |
14:45 |
Bmagic |
https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:2.8 |
14:45 |
bshum |
https://bugs.launchpad.net/evergreen/+bug/1661661/comments/7 |
14:45 |
pinesol_green |
Launchpad bug 1661661 in Evergreen "Support for right-to-left languages" [Wishlist,Fix released] |
14:45 |
Bmagic |
Oh good! |
14:45 |
bshum |
In that comment, I threw up some quicker go-to's for master |
14:46 |
Bmagic |
bshum++ |
14:46 |
bshum |
Since now we sync the PO's more regularly |
14:46 |
berick |
bshum++ |
14:46 |
bshum |
So we've got some reasonable copies to utilize if you're just looking for POs for TPAC |
14:46 |
Bmagic |
lol, just copy the files.... haha |
14:46 |
Bmagic |
no make, no nothing |
14:46 |
bshum |
If you were building stuff for XUL, more comprehensive |
14:46 |
bshum |
And you have to do more dancing with make |
14:46 |
bshum |
I think |
14:47 |
bshum |
TPAC and webstaff are much simpler |
14:48 |
bshum |
Though webstaff is buggy |
14:48 |
bshum |
And a whole other set of problems over there |
14:48 |
Bmagic |
I see, well, I need the xul staff client to support it as well, so back to the other method... |
14:49 |
bshum |
There might be additional clues on https://wiki.evergreen-ils.org/doku.php?id=evergreen-admin:customizations:i18n |
14:50 |
bshum |
But like berick says, the make_release script does most of that stuff automagically these days for tarballs |
14:50 |
bshum |
So I haven't done it by hand in... quite awhile |
14:51 |
* bshum |
hopes that the language you're trying is complete enough for XUL to operate well enough |
14:57 |
* bshum |
thinks there's still outstanding i18n bugs for XUL though |
14:57 |
* bshum |
stops issuing disclaimer warnings |
14:57 |
Bmagic |
:) |
15:02 |
|
mmorgan1 joined #evergreen |
15:23 |
|
Dyrcona joined #evergreen |
16:06 |
|
khuckins_ joined #evergreen |
16:11 |
kmlussier |
Just came across bug 1607487 today. Guess I'm behind the times! |
16:11 |
pinesol_green |
Launchpad bug 1607487 in Evergreen "Broken link in NACO Normalize seed data description" [Low,Fix committed] https://launchpad.net/bugs/1607487 |
16:13 |
kmlussier |
Hatch is on the placeholder agenda for the dev meeting now. Does that need to be there every month? |
16:18 |
berick |
kmlussier: no, i don't think so |
16:18 |
kmlussier |
OK, I'll remove it. |
16:18 |
|
dkyle1 left #evergreen |
16:28 |
kmlussier |
Meeting tomorrow! https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2017-03-01 |
16:38 |
|
mmorgan joined #evergreen |
16:38 |
terran |
I am working on the SQL upgrade script to insert a new action trigger event definition, but the others all seem to have specific record IDs in the INSERT statements... |
16:39 |
terran |
How can I make sure not to conflict with the ID of another action trigger event definition? |
16:40 |
terran |
Copy of what I have so far: https://docs.google.com/document/d/1gb4LDmejWz0AP0eryTeig8tn7Lp3zncRmZWCF5tXxNA/edit?usp=sharing |
16:40 |
bshum |
terran: Well, usually I'd say, whatever was the most recent ID, go one up from there |
16:41 |
bshum |
From the seed data I mean |
16:41 |
bshum |
But yeah, it depends on how quickly it's merged |
16:41 |
bshum |
And it doesn't account for any custom stuff that people might have inserted on their own |
16:41 |
terran |
Yeah, that's what I'm concerned about |
16:41 |
bshum |
Though these days, I think custom A/T definitions start past 1000 probably |
16:41 |
bshum |
So anything below 100 or 1000 are usually reserved for "system" use or "stock" stuff |
16:41 |
bshum |
You could also try shipping it active = false by default |
16:42 |
mmorgan |
terran: It looks like local action trigger event definitions get ids that start with 101, so there should be room for more seed triggers. The last seed trigger I see in a quick glance is id 53 |
16:42 |
bshum |
And tell people to turn it on in the release note |
16:42 |
terran |
Yes, I'm definitely putting it in as active=false since not everyone will want it anyhow |
16:42 |
bshum |
I can't remember if the unique constraint says only worry about it if it's active |
16:43 |
bshum |
In theory, with just an INSERT upgrade like that, in the past, when I was the RM, I tended to move that action outside the regular upgrade script commit block (during release cutting time) and doing the insert on its own |
16:43 |
bshum |
Just in case it fails due to conflict, so that it doesn't screw up the whole upgrade |
16:43 |
bshum |
I don't think you can accurately predict what people do in their own databases |
16:44 |
bshum |
So just go with what mmorgan says :) |
16:44 |
mmorgan |
I see UNIQUE (owner, name) and UNIQUE (owner, hook, validator, reactor, delay, delay_field) |
16:44 |
bshum |
And cross your fingers |
16:44 |
bshum |
Oh, so active doesn't even factor in, goodie |
16:44 |
terran |
Should put it both in 950.data.seed-values.sql as well as in a separate upgrade script? |
16:44 |
bshum |
Anything that affects sql files should have a corresponding upgrade script |
16:44 |
bshum |
So, yes |
16:44 |
bshum |
Basically the upgrade script is intended for existing users |
16:44 |
bshum |
And the other files are for new installations |
16:45 |
bshum |
So if you don't put it in both places, it'll mess somebody up somewhere some day |
16:45 |
terran |
bshum++ and mmorgan++ thank you! |
16:46 |
bshum |
The fun part for the committer is making sure that if they add your code with id 54 let's say, that we don't accidentally merge someone else's code where they also decide to use 54, etc. |
16:46 |
bshum |
If there were multiple people touching it at the same time |
16:46 |
terran |
exactly |
16:46 |
kmlussier |
That's why we should test the upgrade scripts before we merge. |
16:46 |
bshum |
First come, first serve. Next person has to update and rebase. |
16:47 |
bshum |
But this is all new stuff for 2.next / 3.0 right? :D |
16:47 |
bshum |
So we got time to figure it out too |
16:48 |
terran |
Yes, well, it's just an action trigger that we having working in 2.11.1 so someone could use it now if they wanted to - I'm sure it would work in an earlier version too |
16:48 |
bshum |
kmlussier: Well, I usually do :) |
16:48 |
bshum |
terran: yeah, that sort of backporting to existing versions is what makes upgrades to finnicky later on :) |
16:48 |
terran |
true! |
16:48 |
bshum |
But I don't judge |
16:48 |
bshum |
I've done it plenty of times |
16:49 |
bshum |
Just one of those, oh by the way, watch out for this in your upgrade experience |
16:49 |
bshum |
aka, write a good release note about it |
16:49 |
terran |
I shall do my best |
16:49 |
bshum |
And maybe put some -- comments in your upgrade script about it |
16:49 |
bshum |
So that if/when we merge it for testing, we can put it in hopefully safer places |
16:49 |
terran |
good idea |
16:51 |
bshum |
Maybe someday when we're on PG 9.5 for more folk, we can use https://wiki.postgresql.org/wiki/UPSERT |
16:51 |
bshum |
Or we could probably do some smarter upgrade scripting to think through the problem too... hmm |
16:51 |
terran |
Oooh |
16:57 |
Bmagic |
I got the xul staff client recompiled from these instructions https://wiki.evergreen-ils.org/doku.php?id=backend-devel:i18n |
16:59 |
Bmagic |
but now, on the login box, I can choose my new language, I click "apply locale" and I get xml parsing error: chrome://open_ils_staff_client/content/main/main.xul. Line 21, <window id="main_win" |
16:59 |
Bmagic |
XML Parsing Error: undefined entity |
17:01 |
pinesol_green |
News from qatests: Test Success <http://testing.evergreen-ils.org/~live> |
17:03 |
bshum |
Bmagic: Just a guess based on some old threads, but maybe try a fresh profile |
17:03 |
bshum |
http://markmail.org/message/vatzumzzq74w3uay |
17:03 |
Bmagic |
ah, I'll try a fresh one |
17:04 |
bshum |
Could be something else awry though |
17:04 |
bshum |
Like maybe the language file has something wonky in it |
17:04 |
Bmagic |
funny, I cannot pass the -p switch to it without another xml parsing error |
17:05 |
* bshum |
wanders off to pick up pizza |
17:05 |
Bmagic |
I'll keep banging on it |
17:06 |
|
mmorgan left #evergreen |
17:11 |
terran |
Now all I can think about is pizza. |
17:23 |
|
khuckins__ joined #evergreen |
21:12 |
pinesol_green |
[evergreen|Galen Charlton] LP#1668725: fix Z39.50 overlay when no profile set - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=bcdaec0> |