| Time |
Nick |
Message |
| 06:51 |
|
collum joined #evergreen |
| 07:10 |
|
kworstell-isl joined #evergreen |
| 07:26 |
|
redavis joined #evergreen |
| 07:27 |
|
collum joined #evergreen |
| 07:34 |
|
redavis joined #evergreen |
| 07:35 |
|
collum joined #evergreen |
| 08:07 |
|
BDorsey joined #evergreen |
| 08:11 |
|
cbrown joined #evergreen |
| 08:47 |
|
mmorgan joined #evergreen |
| 08:52 |
|
dguarrac joined #evergreen |
| 09:24 |
|
mantis joined #evergreen |
| 09:24 |
|
collum joined #evergreen |
| 10:27 |
|
Dyrcona joined #evergreen |
| 11:07 |
Dyrcona |
Hmmm.. Logins are failing on my concerto vm... |
| 11:08 |
Dyrcona |
And, it's literally ils event 1000 login failed. |
| 11:08 |
* Dyrcona |
tries reloading the database. |
| 11:09 |
|
BDorsey joined #evergreen |
| 11:11 |
Dyrcona |
OK. That fixed it. |
| 11:12 |
redavis |
++ |
| 11:42 |
pinesol |
News from commits: LP2084835 fix for perm check when sharing bucket <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=2be8dbbd0300413cdb51e266d11c3fbb573ab2c1> |
| 11:44 |
Dyrcona |
I am going to try OpenSRF 3.3.2 on a fresh Ubuntu 24.04 system today. I had trouble with OpenSRF main on Ubuntu 24.04 yesterday. I want to see if it is consistent or if maybe it was just something broken on the other virtual machine. |
| 11:45 |
redavis |
phasefx++ Dyrcona++ |
| 11:48 |
|
Christineb joined #evergreen |
| 11:50 |
Dyrcona |
heh.. Working on the ejabberd.yml, I have a suspicion of what was wrong because I've seen that exact behavior before when I forgot to increase the max_user_sessions setting. |
| 11:53 |
Dyrcona |
Yeah, that was probably the issue. Everything starts up fine today. |
| 11:55 |
Dyrcona |
At least we don't have a weird new issue to deal with. |
| 11:56 |
redavis |
Thank goodness |
| 11:57 |
|
collum joined #evergreen |
| 11:59 |
Dyrcona |
I have a question about releases next week. When I do 3.14.0, should I make the upgrade script from the new release of 3.13, i.e. 3.13.5, or should I use 3.13.4? I'd like to use 3.13.5, but that means the tag branch for 3.13.5 needs to be done first. |
| 12:00 |
Dyrcona |
Noon on a Friday in IRC is probably the wrong time and place to ask that question. :) |
| 12:00 |
redavis |
I think you could do from 3.13.4 |
| 12:00 |
Dyrcona |
redavis: I could, but I'd prefer 3.13.5... |
| 12:01 |
redavis |
Well, it's up to you, but there will also be a 3.13.6. Will the upgrade script be changed for each point release? |
| 12:01 |
redavis |
(eventually a 3.13.6 |
| 12:02 |
Dyrcona |
No, it's not. It's done from the current point release at the time it is made. |
| 12:02 |
|
mantis left #evergreen |
| 12:03 |
Dyrcona |
Which makes upgrading from later point releases trickier, and we don't do anything to help anyone with that. |
| 12:03 |
redavis |
right |
| 12:05 |
Dyrcona |
I might as well finish installing Evergreen on this vm. I can use it for testing. |
| 12:17 |
mmorgan |
Dyrcona: Friday brain talking, but I think regardless of whether you do it from 3.13.4 or 3.13.5, upgrading from later 3.13 point releases will be trickier. |
| 12:17 |
mmorgan |
So I would think doing it from whatever is the latest release when you actually build is the best you can do. |
| 12:18 |
|
jihpringle joined #evergreen |
| 12:29 |
Dyrcona |
Yeahp. We'll see how it goes. |
| 13:01 |
Dyrcona |
hrm. Somtimes I wonder if things should be a shell script or a function, or even an alias..... |
| 13:32 |
* Dyrcona |
goes to find some lunch. Back in a a while. |
| 14:48 |
|
Dyrcona joined #evergreen |
| 15:21 |
Dyrcona |
"Bring on the night. I couldn't stand another hour of daylight." |
| 17:03 |
|
mmorgan left #evergreen |
| 22:29 |
|
sherbertbc joined #evergreen |
| 22:33 |
|
sherbertbc left #evergreen |
