| Time |
Nick |
Message |
| 08:11 |
|
cbrown joined #evergreen |
| 08:14 |
|
redavis joined #evergreen |
| 08:15 |
|
BDorsey joined #evergreen |
| 08:45 |
|
mmorgan joined #evergreen |
| 08:47 |
|
kworstell-isl joined #evergreen |
| 09:01 |
|
dguarrac joined #evergreen |
| 10:00 |
|
mmorgan1 joined #evergreen |
| 10:13 |
|
mantis joined #evergreen |
| 10:18 |
|
collum joined #evergreen |
| 10:37 |
|
collum joined #evergreen |
| 10:40 |
|
Dyrcona joined #evergreen |
| 10:51 |
|
Christineb joined #evergreen |
| 11:07 |
Dyrcona |
asciidoc.... |
| 11:10 |
Dyrcona |
asciidoc doesn't like the release notes for 3.14, but asciidoctor has no problem with it. |
| 11:12 |
redavis |
hmm... |
| 11:12 |
redavis |
is there something else I can use other than asciidoctor to figure out the problem? |
| 11:12 |
redavis |
let me see if I can refer back to an earlier version and compare. |
| 11:13 |
Dyrcona |
redavis: No. I don't think its anything you can do anything about. I don't think I can. |
| 11:14 |
redavis |
Hmm, okay... |
| 11:14 |
Dyrcona |
toclevels: Is set to 3. leveloffset is +3, and ascidoc complains about our level 3 entries: WARNING: RELEASE_NOTES_3_14.adoc: line 76: missing section: [sect5] |
| 11:14 |
Dyrcona |
. |
| 11:15 |
Dyrcona |
I tried bumping toclevels to 4 and it still complains. The warning lines are dropped. |
| 11:15 |
redavis |
Hmm, I change the TOC levels... |
| 11:16 |
Dyrcona |
I changed them back after getting an error. |
| 11:16 |
redavis |
You changed them from 2 to 3? |
| 11:16 |
Dyrcona |
Yes, because I got an error that I sent you in an email. |
| 11:17 |
redavis |
My email fetch is suspect. Checking |
| 11:17 |
Dyrcona |
Does anyone know if we use asciidoc to asciidoctor for the official documentation? I think my assciidoc may be bugged. |
| 11:17 |
|
collum joined #evergreen |
| 11:18 |
Dyrcona |
It makes the same complaint about the 3.13 release notes for me. |
| 11:18 |
redavis |
Oh, let me look at the code again. I think I might understand what's going on...maybe. |
| 11:19 |
redavis |
n/m. I don't know. |
| 11:19 |
Dyrcona |
:) |
| 11:19 |
Dyrcona |
Yeah, I don't know either. That's why I think it's a bug in whatever version of asciidoc that I have. |
| 11:20 |
Dyrcona |
The headers that issue a warning in asciidoc don't show up, but the markup looks correct. |
| 11:20 |
Dyrcona |
I mean they don't show up in the HTML document. |
| 11:20 |
|
collum joined #evergreen |
| 11:22 |
redavis |
Hmm, I do see...SOMETHING. Let me see if I can figure it out. |
| 11:24 |
Dyrcona |
I'm going to try it on a vm with a different version of asciidoc. Maybe the one on Ubuntu 22.04 is bugged? |
| 11:24 |
redavis |
Okay, and I'll send this updated file |
| 11:25 |
redavis |
Sent |
| 11:26 |
redavis |
Bugger, hold |
| 11:26 |
redavis |
Sending....again :-((((((((( |
| 11:27 |
Dyrcona |
asciidoc 10.2.0 gives a new warning and the same warnings as 10.1.2. |
| 11:27 |
redavis |
Try the incoming. |
| 11:27 |
Dyrcona |
asciidoctor just works. |
| 11:27 |
Dyrcona |
I'll give yours a shot. |
| 11:28 |
Dyrcona |
Nope. Same warnings: asciidoc: WARNING: RELEASE_NOTES_3_14.adoc: line 45: missing section: [sect5] |
| 11:29 |
redavis |
okay, lemme look at that line |
| 11:29 |
Dyrcona |
There are 14 more, and there's nothing wrong with those lines AFAICT. |
| 11:29 |
Dyrcona |
asciidoctor doesn't complain. |
| 11:30 |
Dyrcona |
I think I'll update the release instructions to use asciidoctor instead of asciidoc. Two recent version of asciidoc choke on all of the release notes documents. |
| 11:31 |
redavis |
Yeah, I think it has to do with that being beyond the scope of asciidoc - like it only goes to 5 levels and those represent a sixth. |
| 11:31 |
redavis |
5 header levels |
| 11:31 |
Dyrcona |
I suppose that might be it. I didn't know asciidoc had such a limit. |
| 11:32 |
Dyrcona |
I haven't really started building the tarball, yet. I just wanted to check the release notes for syntax, before getting started. ;) |
| 11:32 |
redavis |
okay, asciidoctor has a limit of six levels...but...hmm. |
| 11:33 |
|
collum joined #evergreen |
| 11:33 |
Dyrcona |
According to Google's AI overview: The section level limit in AsciiDoc is 5. This is because HTML only provides heading tags from h1 to h6. |
| 11:34 |
redavis |
So line 45 should be h6 |
| 11:34 |
redavis |
based on the offset |
| 11:34 |
Dyrcona |
I guess that's because level 1 is meant for the title, which is normally marked up differently from sections. |
| 11:34 |
Dyrcona |
Right, but I think asciidoc is adding 1 internally. |
| 11:35 |
|
collum joined #evergreen |
| 11:35 |
Dyrcona |
I did look at the asciidoc code a bit over a decade ago, but don't remember much, and it has changed a lot since then. The original author abandoned it. |
| 11:35 |
redavis |
Yes...oh. Okay, so...I'll try something else |
| 11:35 |
Dyrcona |
No, don't try anything else. |
| 11:36 |
redavis |
lol, okay. Well, I'm going to because I'm curious, but i won't send it. |
| 11:36 |
Dyrcona |
We'll just use asciidoctor. Looks like we're marking it up for what asciidoctor exprecs. |
| 11:36 |
Dyrcona |
exprecs? Yeah, sure, that's a word.... |
| 11:36 |
Dyrcona |
expects. :) |
| 11:36 |
redavis |
(my try was a fail, fyi) |
| 11:36 |
redavis |
lol, exprecs should be a word |
| 11:37 |
redavis |
Well, the last .adoc I sent is the best one anyway. |
| 11:38 |
Dyrcona |
asciidoc, the format, normally has a title line. That's given h1, so h1 through h5 in asciidoc markup are normally bumped to h2 through h6. asciidoc documenation calls these sections. |
| 11:38 |
Dyrcona |
Looks like asciidoctor will use h1 through h6 for the sections in the absence of a title, but that's just speculation. I've not looked at the code. |
| 11:38 |
redavis |
I suspect there's also a warning at line 78, 85, 91, etc |
| 11:38 |
Dyrcona |
Yeah, 15 lines or so. |
| 11:39 |
redavis |
Those would be being bumped to a non-existant h7 in asciidoc |
| 11:40 |
Dyrcona |
Yeah, that's what I think is happening. sect6 (h7) doesn't exist, so asciidoc wants sect5 (h6). |
| 11:40 |
Dyrcona |
So, leveloffset +2 would fix it, but breaks the hierarchy, I think. |
| 11:40 |
redavis |
Yes |
| 11:41 |
Dyrcona |
That's why you made the original change you sent me this morning. Trouble is, the Evergreen 3.14-RC line inserts a duplicate h1, and asciidoc doesn't like that, either. |
| 11:41 |
redavis |
That's what I had originally done, but it broke other important things. |
| 11:41 |
Dyrcona |
asciidoctor doesn't seem to care as much. |
| 11:42 |
|
jihpringle joined #evergreen |
| 11:44 |
Dyrcona |
Lemme try something else. I'm going to use the title entry for the title. |
| 11:45 |
redavis |
that's what I looking up and then got sidetracked |
| 11:45 |
Dyrcona |
Oh never mind, it's "= Document title". There's not ":title: Document title" for the header. |
| 11:46 |
Dyrcona |
I've been using markdown for my own things lately, so I'm a bit rusty when it comes to asciidoc. |
| 11:47 |
Dyrcona |
I think we're breaking the rules with asciidoctor, too, but it doesn't care: https://docs.asciidoctor.org/asciidoc/latest/sections/titles-and-levels/ |
| 11:48 |
|
collum joined #evergreen |
| 11:49 |
redavis |
I have an idea but need to do a little research |
| 11:50 |
redavis |
It's to change those h7s to just some em text |
| 11:50 |
Dyrcona |
leveloffset +2 would fix the technical issue, but then the categories, Acquistions, etc., would be at the same logical heading level as "New Features". |
| 11:50 |
Dyrcona |
We could just make them bold. |
| 11:50 |
redavis |
exactly |
| 11:50 |
Dyrcona |
Simple matter matter of regex search and replace. |
| 11:51 |
redavis |
Just have to make sure it's within the offset scope |
| 11:51 |
Dyrcona |
Does it matter, or does it matter? ;) |
| 11:51 |
redavis |
lol, it matters. A little. But then again...it doesn't. |
| 11:51 |
Dyrcona |
It's adding Evergreen 3.14-RC that changed things. |
| 11:52 |
redavis |
Yep, but that was something that I should have caught at beta and didn't. |
| 11:52 |
redavis |
It's ACTUALLY (so sorry for using that word) because that release note has too many headings |
| 11:53 |
Dyrcona |
Oh. this is kind of tricky... matching a line that ends with " ===" or nothing and contains a capture group.... Maybe if I make it not greedy? |
| 11:53 |
|
collum joined #evergreen |
| 11:53 |
redavis |
lol, I could just do it manually. It's not many lines |
| 11:55 |
Dyrcona |
Huh. It almost worked... The capture group inclued the " ===" I'll just have to remove those with another search and replace. |
| 11:55 |
redavis |
Also, not all of those === have closing "tags" |
| 11:55 |
redavis |
asciidoctor is just letting it get away with it. |
| 11:56 |
Dyrcona |
Well, yeah. I tried this for regex: ^=== \(.+\)\( ===\)?$ |
| 11:56 |
Dyrcona |
Oh! I see the problem.. I forgot ? after the +. |
| 11:57 |
redavis |
yep, but that last \( ===\)?$ doesn't necessarily exist |
| 11:57 |
Dyrcona |
Well, that's why the ? outside the parenthesis. I'm going to do it again to make sure I get the regex correct. |
| 11:57 |
redavis |
Oh, got it |
| 11:59 |
Dyrcona |
Yeah, this worked: ^=== \(.+?\)\( ===\)?$ |
| 11:59 |
Dyrcona |
That's 3 problems solved. :) |
| 11:59 |
redavis |
Dyrcona |
| 12:00 |
Dyrcona |
** is bold in asciidoc, too, right? I guess I'll find out when I generate a test html doc. |
| 12:00 |
redavis |
Just *[something]* |
| 12:00 |
Dyrcona |
I thought *something* is italics. |
| 12:00 |
Dyrcona |
I'll fix it if I botched it. should be easy enough. |
| 12:01 |
Dyrcona |
markdown: **something** is bold. That's what I'm used to... :) |
| 12:01 |
Dyrcona |
yeah, the output looks OK, now. |
| 12:02 |
Dyrcona |
the former === levels are now bolded. |
| 12:02 |
redavis |
++ |
| 12:03 |
Dyrcona |
Looking at a lot of these, they should be sample blocks, and the bold could be changed to .[something]. |
| 12:04 |
redavis |
Yes |
| 12:04 |
Dyrcona |
Well, some of them, maybe not all or even most. |
| 12:04 |
redavis |
But, I think this change should be enough for right now. And, worth noting that other asciidoc (used in Antora) probably doesn't need to accommodate as much for that offset. |
| 12:05 |
redavis |
I'm not sure about that though |
| 12:06 |
Dyrcona |
I concur. |
| 12:06 |
Dyrcona |
I think the bold is good for now. We can change it later. |
| 12:06 |
redavis |
Or SOMEONE can change it later. |
| 12:07 |
Dyrcona |
:) |
| 12:07 |
|
collum joined #evergreen |
| 12:07 |
Dyrcona |
At my house, someone is usually me. :) |
| 12:07 |
Dyrcona |
I'll fix this up and add your name as a co-author. |
| 12:07 |
redavis |
lol, well...there's that. But in the house of Evergreen...there are plenty of people who can deal with release note/adoc structure. |
| 12:08 |
Dyrcona |
Looks like the 3.13 release notes need a similar fix. |
| 12:09 |
Dyrcona |
I'm a little puzzled though. = is title h1. so ====== should be h6. And === +3 is ======. Something seems off, but whatever. |
| 12:10 |
Dyrcona |
Oh, but right the docs say == is h1.... |
| 12:10 |
Dyrcona |
No.....That's not it either. |
| 12:11 |
Dyrcona |
Ok. read the docs again. I'm good. |
| 12:11 |
redavis |
++ |
| 12:11 |
Dyrcona |
Offset 0, so off by one errors are imminent if not inevitable. |
| 12:17 |
Dyrcona |
We could probably script this conversion from === to ** in the subsections. |
| 12:18 |
|
frank_g joined #evergreen |
| 12:20 |
redavis |
It looks like both * and ** work the same. I've updated the file if you don't have the whole thing done. |
| 12:24 |
frank_g |
Hi all, I am trying to migrate my EG server to a new production server, the librarian is testing on it, and she is trying to create a new marc record, but when she tries to save it it shows the error : "Failed to create new record: {{error}}", and checking on the osrfsys.log there appears this error " open-ils.cstore ERROR inserting |
| 12:24 |
frank_g |
biblio::record_entry object using query [...., ERROR: Can't locate MARC/Record.pm in @INC (you may need to install the MARC::Record module) (@INC entries checked: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.38 |
| 12:24 |
frank_g |
/usr/share/perl/5.38 /usr/local/lib/site_perl) at line 3" |
| 12:25 |
frank_g |
Do I have to install somenting else? or it is a kind of bug? |
| 12:25 |
Dyrcona |
frank_g: You need to install the database perl prerequisites on the database server. |
| 12:27 |
Dyrcona |
Evergreen uses Perl functions in the database. |
| 12:27 |
Dyrcona |
Or, you may need to install the prerequisites on your new server again. That might not be from the database now that I look again. |
| 12:29 |
Dyrcona |
redavis: I've updated the release notes. |
| 12:30 |
redavis |
Dyrcona++ |
| 12:31 |
Dyrcona |
redavis: There is a difference between * and **. '*' has to go around a word or words. '**' can go anywere like **some**thing, and only some will be bolded... What I said before about italics is markdown. |
| 12:32 |
Dyrcona |
"You're in a maze of twisty markup languages all of them alike enough to cause confusion. You are about to be eaten by a Grue." |
| 12:33 |
redavis |
Got it. |
| 12:33 |
* redavis |
probably likes grues. |
| 12:33 |
Dyrcona |
I think I want to get "You are about to be eaten by a Grue." on a t-shirt. It would be good for wearing around Salem, MA, particularly in October. :) |
| 12:33 |
redavis |
lol! |
| 12:34 |
pinesol |
News from commits: Docs: Fix 3.14 release notes syntax <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=b69104ac6a94acad3ff8255040e08032a18fd583> |
| 12:34 |
Dyrcona |
@blame Bewitched |
| 12:34 |
pinesol |
Dyrcona: Bewitched forgot to give the gerbils their chocolate-frosted sugar bombs |
| 12:38 |
Dyrcona |
I guess I'll use the VM that I had set up for last time before I got derailed. |
| 12:39 |
|
collum joined #evergreen |
| 12:51 |
Dyrcona |
Question: When I build the db upgrade for the RC, do I build it from the same base release as the beta (3.13.4) or do I make from the beta? |
| 12:52 |
redavis |
Hmm, if you're asking me (the WORSE person to be asking), I'd say start from the same base release as beta. |
| 12:53 |
|
collum joined #evergreen |
| 12:53 |
Dyrcona |
I'm asking the channel. |
| 12:53 |
redavis |
Whew |
| 12:56 |
Dyrcona |
There is no 3.13.3 to 3.13.4 db upgrade which kind of bothers me. The script was modified to put at least the version number in config.upgrade_log even if there were no database upgrades. |
| 13:03 |
Dyrcona |
Should Bmagic's commit from Oct 3 for the new translations be in rel_3_14? I think so, but I'm not sure. |
| 13:05 |
Dyrcona |
Eh, whatever. Mine is there and includes the same changes as the one from the tag branch. |
| 13:05 |
mmorgan |
Dyrcona: Is that a missed step in a point release build? Should 3.13.3-3.13.4-upgrade-db.sql have been pushed back to main? |
| 13:06 |
* mmorgan |
is not always clear on what needs to get pushed to main. |
| 13:12 |
|
kmlussier joined #evergreen |
| 13:21 |
Dyrcona |
Yeah. It can be confusing. I used to be more sure. |
| 13:23 |
Dyrcona |
Also, ...eg2/locale doesn't get committed, but ...eg2.src/locale does... |
| 13:23 |
Dyrcona |
eg2/src/locale that is. |
| 13:23 |
Dyrcona |
Some of this I figure out by poking around with git ls-tree on other branches. |
| 13:24 |
Dyrcona |
The documentation could be more complete. |
| 13:27 |
Dyrcona |
Oops. forgot to update my working branch. Nothing that a rebase won't fix. |
| 13:28 |
Dyrcona |
Oh... I have to do the translations over again. I'll wager this is not a forgiving process. |
| 13:30 |
Dyrcona |
Oh man... We didn't clean up the adoc files when the beta was released.... |
| 13:30 |
Dyrcona |
Our release process.... We need to fix it. |
| 13:32 |
redavis |
We do. |
| 13:32 |
Dyrcona |
Oh never mind. I'm blind. |
| 13:32 |
Dyrcona |
Well, yeah, we still need to fix this process. |
| 13:33 |
Dyrcona |
I missed 'deleting' at the beginning of the lines when doing git pull. when I tried to find the files they were gone. |
| 13:33 |
redavis |
lol, yes. Fix it. And, I'm not sure about your blindness. |
| 13:33 |
Dyrcona |
I hope POEditor deals with uploading another messages file. |
| 13:34 |
Dyrcona |
This is why I haven't been enthusiastic about doing releases for quite some time. |
| 13:35 |
Dyrcona |
I don't like dealing with POEditor AND Launchpad. I guess if it was just one, it would not be so bad. |
| 13:39 |
redavis |
Question - if we moved away from Launchpad to Github, would that mean using POEditor exclusively for translations or still some POEditor and some Github for translations? |
| 13:40 |
Dyrcona |
Oh nice. Now that I've updated the branch on my working VM, I get a syntax error in ../../Open-ILS/src/templates-bootstrap/opac/parts/cart.tt2 and ../../Open-ILS/src/templates-bootstrap/opac/parts/record/issues-mfhd.tt2 |
| 13:41 |
Dyrcona |
We can use POEditor exclusively for translations even now with Lp for bugs. I think we started using Lp for translations because it was there and we were using it. |
| 13:42 |
Dyrcona |
POEditor can integrate with github, so we could switch to github or just have POEditor grab code from our github mirror. |
| 13:42 |
Dyrcona |
So, looks like I have to fix these syntax errors. |
| 13:42 |
redavis |
okay. I'll think about translations when my stomach isn't upset and my head doesn't hurt. |
| 13:44 |
Dyrcona |
Get some rest. |
| 13:46 |
redavis |
If only. Just gonna slow down a little. strategic plan meeting next and then will rest a little bit. |
| 13:47 |
Dyrcona |
Hmm. that second one doesn't look like a real error. |
| 13:48 |
Dyrcona |
There's an IF and 3 loops in that file, and 4 ENDs. |
| 13:49 |
Dyrcona |
Oh, what there might be is a missing "[%" |
| 13:50 |
|
collum joined #evergreen |
| 13:51 |
|
kworstell-isl joined #evergreen |
| 13:57 |
Dyrcona |
Ok missed an extra ; in one of the files.... |
| 13:58 |
redavis |
It's ALWAYS a semicolon! |
| 14:01 |
Dyrcona |
Grrrr.... Still a problem with that same file. |
| 14:01 |
Dyrcona |
Now, it's ELSEIF where it should be ELSIF.... |
| 14:01 |
Dyrcona |
I love to hate programming. |
| 14:04 |
Dyrcona |
oh damn. I did need that ;..... |
| 14:04 |
pinesol |
News from commits: Fix it again <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=9883f84c3722acc999b33149b1b47044c2e146ab> |
| 14:04 |
pinesol |
News from commits: Fix an additional TT2 syntax error <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=61df59f53042fd002fd27570c4d9b270bdcf801b> |
| 14:04 |
pinesol |
News from commits: Fix TT2 syntax errors <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=ea2b8076bdda733dcd6b9b971450b9eeebcdb008> |
| 14:07 |
Dyrcona |
I hate bashing the commits like that, but I was so sure it was fixed each time... If it was a working branch, I'd squash 'em, but oh well.... |
| 14:07 |
Dyrcona |
crap... |
| 14:08 |
Dyrcona |
Did commit in the wrong tab, now I have to undo that. Maybe I should just give up and let someone else do this. |
| 14:10 |
Dyrcona |
Who knew working with translations would find bugs. |
| 14:15 |
Dyrcona |
brz: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist. |
| 14:16 |
Dyrcona |
That never happened before. |
| 14:16 |
Dyrcona |
jstephenson bazaar.launchpad.net: Permission denied (publickey). |
| 14:20 |
Dyrcona |
Hm.. Maybe I didn't register this SSH key with lp, but I thought that I did. |
| 14:21 |
|
collum joined #evergreen |
| 14:34 |
pinesol |
News from commits: Add back the ; that was removed from cart.tt2 <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=f8092b420a0dd7b58e56351a4c41e62e641e46f5> |
| 14:38 |
|
mmorgan1 joined #evergreen |
| 14:51 |
Dyrcona |
git: because all code must be committed. |
| 15:21 |
* Dyrcona |
grabs a bite to eat. May or may not be back later, but probably will be back. |
| 15:25 |
|
mantis left #evergreen |
| 15:34 |
|
redavis joined #evergreen |
| 15:50 |
abneiman |
redavis: Dyrcona: re above, I can check the relnotes formatting etc. on Friday if it's still giving you trouble |
| 15:50 |
redavis |
It's taken care of. Bmagic is going to test the tarball and then we're good to go to next step. Thank you though. Will let you know if there are additional things. |
| 15:54 |
Bmagic |
will do |
| 15:54 |
|
jihpringle joined #evergreen |
| 15:54 |
abneiman |
++ |
| 16:20 |
|
jihpringle joined #evergreen |
| 17:01 |
|
Dyrcona joined #evergreen |
| 17:02 |
|
mmorgan left #evergreen |
| 17:21 |
|
kmlussier left #evergreen |
| 17:47 |
|
frank_g joined #evergreen |
| 17:47 |
frank_g |
Dyrcona: tks for response, If I want to install Postgres in another server, Do I need to install it with the "make -f Open-ILS/src/extras/Makefile.install postgres-server-ubuntu-noble-15" command? or how Can I install the prerrequisites in a server where postgresl was installed from the pg official repo? |
| 17:50 |
Dyrcona |
frank_g: Do you have everything on 1 server now, or do you have a separate server for PostgreSQL? I assumed you had a separate server, but that could be wrong. |
| 17:50 |
frank_g |
Dyrcona: yes, now I have separate server for PostgreSQL, |
| 17:51 |
Dyrcona |
Let me check something. |
| 18:02 |
Dyrcona |
frank_g: On Ubuntu, you can install the things listed in this document on the database server: https://docs.google.com/document/d/1kBZWgblurHNMJzCblhEUJGiZPL2WPJWaSoGEGkJfBao/edit?usp=sharing |
| 18:02 |
Dyrcona |
I often just install those rather than putting Evergreen on there and using the Makefiles. |
| 18:05 |
|
akilsdonk_ joined #evergreen |
| 18:05 |
jeffdavis |
I've installed prereqs on a Postgres server using that make command (well, the ubuntu-jammy-14 equivalent of it). |
| 18:09 |
Dyrcona |
Yeah, that should work, too, if it is easier. |
| 18:19 |
frank_g |
thanks, I will try both |
| 18:22 |
Dyrcona |
frank_g: You only need to do one or the other. |
| 18:22 |
frank_g |
yes but I will try in two diferent virtual machines |
| 18:23 |
Dyrcona |
OK. |
| 18:23 |
Dyrcona |
Mine only works if you already have the other necessary PostgreSQL packages installed. |
| 18:23 |
Dyrcona |
And, it's about time for me to go again. |
| 18:23 |
Dyrcona |
frank_g: Good luck! I'll be back tomorrow. |
| 18:35 |
frank_g |
thanks |
| 18:48 |
|
jihpringle joined #evergreen |
