2026-10-06 GnuCash IRC logs
01:05:39 *** fell has quit IRC
01:06:58 *** fell has joined #gnucash
01:06:58 *** ChanServ sets mode: +o fell
04:18:43 *** rocartur has joined #gnucash
07:58:41 *** leighbb has quit IRC
07:58:49 *** leighbb has joined #gnucash
07:58:49 *** ChanServ sets mode: +v leighbb
09:48:04 *** lmat has joined #gnucash
14:55:51 *** mechtilde has joined #gnucash
14:57:13 *** mechtilde has quit IRC
15:05:58 <jralls> warlord, this morning's try completed with no response from your end, but there's nothing in builds/win32/future.
15:11:49 <warlord> jralls, I see this in the logs:
15:11:50 <warlord> Oct 6 12:28:25 code gnucash-get-artifact[6513]: To get started with GitHub CLI, please run: gh auth login
15:11:50 <warlord> Oct 6 12:28:25 code gnucash-get-artifact[6513]: Alternatively, populate the GH_TOKEN environment variable with a GitHub API authentication token.
15:11:50 <warlord> Oct 6 12:28:25 code gnucash-get-artifact[6537]: Download reported error: 4
15:12:02 <warlord> Oh, I might not have exported GH_TOKEN..
15:13:05 <warlord> Good news is that it decrypted the message.. Bad news... but it's fixed now so NEXT build should be good.
15:16:20 <jralls> Since you've got the run id you can test the rest of the script manually...
15:18:59 <warlord> true. Running manually now.
15:22:26 <warlord> jralls, unfortunately didn't quite work...
15:22:27 <warlord> error downloading gnucash-2026-10-05-393f7d9+.setup.exe: error extracting zip archive: zip: not a valid zip file
15:51:34 <jralls> Apparently older versions of gh expect the download to be zipped and the workflow uploads it unzipped to make for less work when downloading the artifact from a browser. Since we expect browsers to be accessing the downloads from code we can drop that from the workflow and it should work next time.
15:52:27 <jralls> While I'm at it I'll add a manual trigger so that I can run the workflow at will.
15:56:22 <warlord> Ok
15:59:59 <jralls> Running now...
16:02:09 <warlord> watching the logs.
16:03:16 <jralls> Patience, it has to build Gnucash which usually takes 20 min or so. But the first try errored out because github 500'd retrieving the dependencies packages.
16:11:41 <warlord> i have a tail|grep going..
16:17:36 *** lmat has quit IRC
16:22:38 <warlord> jralls, Oct 6 16:22:28 code gnucash-get-artifact[21022]: Download reported success
16:23:05 <warlord> [root@code ~]# ls -l /var/www/html/builds/win32/future/
16:23:05 <warlord> total 0
16:23:05 <warlord> drwxr-xr-x. 2 root root 51 Oct 6 16:22 gnucash-2026-10-05-393f7d9+.setup.exe
16:23:30 <jralls> Woot!
16:25:05 <warlord> Indeed!
16:25:35 <warlord> Oh -- except....
16:25:43 <warlord> it's a directory...
16:25:55 <warlord> The file is one level down:
16:25:55 <warlord> [root@code ~]# ls -l /var/www/html/builds/win32/future/gnucash-2026-10-05-393f7d9+.setup.exe/
16:25:55 <warlord> total 138956
16:25:55 <warlord> -rw-r--r--. 1 root root 142289911 Oct 6 16:22 gnucash-2026-10-05-393f7d9+.setup.exe
16:26:28 <warlord> so it's builds/win32/future//gnucash-2026-10-05-393f7d9+.setup.exe/gnucash-2026-10-05-393f7d9+.setup.exe
16:27:20 <jralls> So I see. I guess that's understandable since it's from a zipfile. So one more step on your end.
16:31:16 <warlord> Yep. Can you run it again?
16:37:13 <jralls> Running. BIAB.
16:51:07 *** rocartur has quit IRC
17:03:55 <jralls> And success. I downloaded, installed, and opened it.
17:05:04 <warlord> Much better now!
17:56:49 <jralls> warlord, that installer will overwrite a release installation. Claude helped me make some changes so that it won't. I'm testing those now in my own repo, I'll push and run the nightly one more time when it works. Will your script overwrite if it gets a new artifact with the same name?
17:57:14 <warlord> Yes.
17:57:25 <warlord> at least, it should... I don't think I tested that.
17:57:51 <warlord> I can use cp -pf instead if cp -p to force the overwrite?
17:59:53 <jralls> Well, we'll find out in an hour or so. Shouldn't be necessary to use -f unless you have an alias that sets -i or -n, but it does no harm. But don't you want to use mv so that you don't clutter up your disk with two copies?
18:00:48 <jralls> Also to make sure that an existing D/L doesn't get in gh's way.
18:51:32 <jralls> It overwrote, so all good from my perspective.
19:54:49 *** fgearhart has joined #gnucash
20:14:48 *** fgearhart has quit IRC
23:10:01 *** jonakeys has quit IRC
23:10:08 *** jonakeys has joined #gnucash