2025-01-02 GnuCash IRC logs
00:01:15 *** brook has quit IRC
00:59:26 *** brook has joined #gnucash
01:02:26 *** brook has quit IRC
01:04:10 *** fell has quit IRC
01:05:29 *** fell has joined #gnucash
01:05:29 *** ChanServ sets mode: +o fell
02:01:30 *** fell has quit IRC
02:02:49 *** fell has joined #gnucash
02:02:49 *** ChanServ sets mode: +o fell
05:52:59 *** brook has joined #gnucash
05:56:00 *** brook has quit IRC
06:33:51 *** brook has joined #gnucash
06:36:51 *** brook has quit IRC
07:54:07 *** brook has joined #gnucash
07:57:07 *** brook has quit IRC
08:43:52 <warlord> jralls, I don't know how quickly I can update code. It might be easier to create a new VM for flatpak builds.
08:43:52 <gncbot> warlord: Sent 1 week, 6 days, 14 hours, and 24 minutes ago: <fell> Can you upgrade flathub-builder to at least 1.4.4? See above.
08:44:21 <warlord> fell, see my reply to jralls.
08:55:14 *** brook has joined #gnucash
08:57:20 *** brook has quit IRC
08:57:28 *** brook has joined #gnucash
09:00:28 *** brook has quit IRC
10:57:31 *** brook has joined #gnucash
11:00:31 *** brook has quit IRC
11:10:15 *** brook has joined #gnucash
11:13:16 *** brook has quit IRC
11:31:03 *** brook has joined #gnucash
11:34:04 *** brook has quit IRC
12:43:24 <warlord> jralls, fell -- if I'm going to create a new VM as a flatpak builder, how much disk space will it need? My idea is that it would rsync its contents over to code, but it might need a commensurate amount of space. Currently it's using 62GB on code.
12:47:49 <fell> My rule of thumb: double the current usage
12:48:20 <warlord> Sure, that makes sense. Granted, it's easy to update later if necessary. The joys of VMs.
12:59:43 *** brook has joined #gnucash
13:02:43 *** brook has quit IRC
14:00:51 *** brook has joined #gnucash
14:03:51 *** brook has quit IRC
14:13:04 *** brook has joined #gnucash
17:36:48 *** fell has quit IRC
17:38:05 *** fell has joined #gnucash
17:38:05 *** ChanServ sets mode: +o fell
17:42:34 <warlord> I need to figure out how to get flatpak to rsync to a remote-host..
17:59:23 <warlord> @tell gjanssens hey geert -- any idea how I could set custom.sh to remote-rsync the flatpak builds? I want the results to remain on code.gnucash.org, even if the /build/ is done on another system.
17:59:23 <gncbot> warlord: The operation succeeded.
19:21:26 <warlord> I think I may have figured it out. Will test it tomorrow.
19:31:05 <warlord> fell, jralls -- when I migrate the flatpak build, do I still need to build chris' beta branch?
19:36:00 <fell> warlord, IIRC beta became the root of 5.0-stable
19:37:36 <warlord> Okay, so I can stop building his branch. Cool.
19:40:22 <warlord> Oh, looks like I already stopped building it.
19:43:17 <fell> yeah, no such branch anymore
19:47:07 <warlord> Now I need to figure out the rsync mkdir issue:
19:49:17 <warlord> Figured that out. By bad -- typo.
19:50:05 <warlord> So will flatpak-builder-1.4.4-2.fc41.x86_64
19:50:05 <warlord> suffice?
19:54:25 <warlord> I've got it set up to run overnight, now.. Only building stable... But the results are not, yet, exported on code. I'll work on that tomorrow.
19:55:00 <warlord> (I think I need to copy the old output directory to the new location so the rsync -a won't delete the old stuff. I THINK... I will test it all out tomorrow)
20:09:26 <fell> OK
20:22:50 *** brook has quit IRC
21:36:25 *** brook has joined #gnucash
21:39:34 *** brook has quit IRC
22:59:56 *** brook has joined #gnucash
23:02:57 *** brook has quit IRC
23:10:00 *** jonakeys has quit IRC
23:10:06 *** jonakeys has joined #gnucash
23:38:53 *** brook has joined #gnucash
23:41:54 *** brook has quit IRC