2020-02-20 GnuCash IRC logs

00:14:28 *** omnireq_ has quit IRC
00:14:38 *** omnireq_ has joined #gnucash
00:35:28 *** omnireq_ has quit IRC
00:35:38 *** omnireq_ has joined #gnucash
00:59:43 *** fell_laptop has quit IRC
01:03:05 *** fell_laptop has joined #gnucash
01:03:05 *** ChanServ sets mode: +o fell_laptop
01:42:11 *** fell has joined #gnucash
01:42:12 *** ChanServ sets mode: +o fell
01:44:00 *** frank_laptop_ has joined #gnucash
01:44:00 *** ChanServ sets mode: +o frank_laptop_
01:44:00 *** fell has quit IRC
01:44:04 *** fell_laptop has quit IRC
01:51:30 *** sbluhm has joined #gnucash
01:51:30 *** ChanServ sets mode: +v sbluhm
01:54:30 *** sbluhm has quit IRC
01:54:36 *** Mechtilde has quit IRC
02:07:16 *** frank_laptop_ has quit IRC
02:08:45 *** frank_laptop_ has joined #gnucash
02:08:45 *** ChanServ sets mode: +o frank_laptop_
02:12:28 *** sbluhm has joined #gnucash
02:12:28 *** ChanServ sets mode: +v sbluhm
02:31:37 *** Aussie_matt has quit IRC
03:01:10 *** Mechtilde has joined #gnucash
03:25:20 *** gjanssens has joined #gnucash
03:25:20 *** ChanServ sets mode: +o gjanssens
03:25:25 <gjanssens> .
03:25:25 <gncbot> gjanssens: Sent 7 hours and 7 minutes ago: <jralls> See the Member Functions section in Effective C++ 3rd edition Item 3 for implementing a non-const override to a const member function. get_value and get_default_value should be const but not set_value so find option needs a const version to call the first two on and a non-const one for set_value.
03:41:43 *** frank_laptop_ is now known as fell
03:42:31 <fell> gjanssens, you should from time to time check messages for gjannsens. ;-)
03:46:00 <fell> @tell gour What is wrong with LANG hr? It is one of the most current and complete translations, we have.
03:46:00 <gncbot> fell: The operation succeeded.
03:51:19 *** gjanssens sets mode: +o gncbot
03:53:08 <gjanssens> @notes gjannsens
03:53:08 <gncbot> gjanssens: Sent 7 hours and 32 minutes ago: <jralls> it's been a few weeks since I wrote it but IIRC the compiler complained about using this->find_option. I don't remember what the complaint was.
03:53:12 <gjanssens> @notes gjannsens:
03:53:12 <gncbot> gjanssens: Error: I have no notes for that nick.
03:53:41 <gjanssens> @notes gjanssens:
03:53:41 <gncbot> gjanssens: Sent 3 weeks, 3 days, 5 hours, and 11 minutes ago: <chris> Bill 00007 is special because its lot doesn't have gncOwner slot; it has gncInvoice slot but that's not sufficient for gncInvoiceGetInvoiceFromLot to successfully find it
04:00:15 <gjanssens> Hmm that was an old note, no longer relevant right now. We discussed this properly here https://lists.gnucash.org/logs/2020/01/27.html#T05:14:20
04:11:33 *** storyjesse has joined #gnucash
04:40:34 <gjanssens> jralls: gcc 9.2.1 seems to be perfectly happy with this->find_option.
04:45:02 *** gour has joined #gnucash
04:45:02 *** ChanServ sets mode: +v gour
04:51:03 <fell> gjanssens: while todays maint flatpak got uploaded, yesterday it was successful built, but not uploaded
04:54:14 *** Gerd has quit IRC
05:03:12 <gjanssens> fell: what did you see exactly ?
05:03:42 *** gour has quit IRC
05:04:53 <fell> https://code.gnucash.org/builds/flatpak/build-logs/maint/2020-02/build-maint-2020-02-19-01-00-02.logend ends with: Uploading log file 'build-maint-2020-02-19-01-00-02.log'
05:05:21 *** User has joined #gnucash
05:05:35 <fell> but there is none in https://code.gnucash.org/builds/flatpak/maint/?C=M;O=D
05:05:58 *** Mechtilde has quit IRC
05:06:51 *** bertbob has quit IRC
05:07:32 <fell> oops, I meant the line Uploading flatpakref file 'gnucash-maint-C3.8b-163-g0e6c9e219-D3.8b-14-g2e426e4.flatpakref'
05:09:26 <fell> Oh, that is the file with today's modify date.
05:10:46 <gjanssens> Yes. If code nor docs change the name of the flatpakref file remains identical and on synching only the date will change
05:10:51 *** bertbob has joined #gnucash
05:10:52 *** ChanServ sets mode: +v bertbob
05:12:06 <gjanssens> jralls: while gcc doesn't complain clang does and it's probably a valid warning:
05:12:07 <fell> Shouldn''t we skip the build/upload if nothing changed?
05:12:18 <gjanssens> jralls: /home/janssege/Development/gnucash/master/libgnucash/app-utils/gnc-optiondb-impl.hpp:89:119: error: all paths through this function will call itself
05:15:41 <fell> Ah, if we change a dependency, but neither code nor docs changed, it is worth to create a new file. but with the same ID?
05:16:34 <gjanssens> Early versions of the build script tried to check this, but it quickly got too complicated.
05:17:02 <gjanssens> For example if you update the version of aqbanking, neither code nor docs change but you do want to have a new flatpak
05:17:32 <gjanssens> So eventually I deferred the need to rebuild to flatpak-builder, which is fairly smart about it.
05:18:05 <gjanssens> In the end the local repo is simply synchronized with the remote one using rsync.
05:18:42 <fell> Another number of changes on the -on-flatpak repo since last release?
05:18:43 <gjanssens> If there really was no build then that would only update a few date stamps without any file transfers (except of course the build log which is unique every day)
05:19:58 <gjanssens> Yes, that could be done in theory, but again, flatpak-builder is much smarter than my manual efforts in knowing when to rebuild something.
05:20:06 <gjanssens> So I prefer not to worry about that.
05:21:04 <fell> It is not very important, but a user with an aqbanking bug might be worried: Should I today update again - the file ID did not change?
05:25:02 <gjanssens> Rsync checks on file modified timestamp and file size to determine when to (re-)upload.
05:26:14 <gjanssens> For simplicity currently the local manifest and flatpakref files are always generated, which means they will always have a more recent modified time stamp even if they don't really change
05:28:32 <gjanssens> We may change this bit and only write a new manifest file if it's effectively different in content.
05:28:57 <gjanssens> In which case the time stamps on the server would remain at when the file was first created.
05:29:40 <gjanssens> However that still doesn't give aqbanking users anything useful to play with as a changed aqbanking version won't change the flatpak ref file.
05:31:08 <gjanssens> The only way to know that is to look in the manifest's aqbanking.json module.
05:31:15 <gjanssens> Today's is here: https://code.gnucash.org/builds/flatpak/manifests/maint/maint-C3.8b-163-g0e6c9e219-D3.8b-14-g2e426e4/modules/aqbanking.json
05:31:51 <gjanssens> If that shows a different version than you currently have, you need to update your gnucash flatpak
05:32:53 <gjanssens> If code and docs haven't changed, this can be as simple as running "flatpak update" (because it's effectively the same flatpak "branch")
05:33:40 <gjanssens> If either has, there will be a new flatpak ref you can use to install a newer flatpak "branch"
05:39:38 <gjanssens> Personally I would love to do away with the branch-per-build and just have a maint and a master branch
05:40:02 <gjanssens> But so far I haven't found a way to easily switch between builds on a single branch in a flatpak repo
05:40:20 <gjanssens> A flatpak repo is not a git repo but an ostree repo
05:40:47 <gjanssens> And it has different semantics, so a branch in flatpak/ostree is not the same as a branch in git
05:41:26 <gjanssens> And as far as I have been able to discover there's no such thing as tags in ostree otherwise I would have used that to tag nightly builds on a given branch
05:42:00 <gjanssens> I have asked again on the flatpak irc channel, perhaps the experts can point me in the right direction after all.
05:42:47 *** fell_laptop has joined #gnucash
05:42:47 *** ChanServ sets mode: +o fell_laptop
05:43:35 *** fell has quit IRC
05:49:06 *** GabrieleV has quit IRC
05:51:34 *** User has quit IRC
05:52:04 *** GabrieleV has joined #gnucash
05:54:02 *** fell_laptop is now known as fell
06:03:34 *** Jimraehl1 has joined #gnucash
06:05:06 *** Jimraehl1 has quit IRC
06:28:22 *** Mechtilde has joined #gnucash
06:29:32 <gjanssens> fell: no tags for flatpak repos :(
06:30:10 <fell> Too bad.
06:30:54 <gjanssens> The only alternative approach would involve a two-step install for testers
06:31:09 <gjanssens> Here is how that would work:
06:31:27 <gjanssens> Instead of a branch per nightly build, we have a maint and a master branch
06:31:45 <gjanssens> Each nightly build pushes a commit to the respective branch
06:32:23 <gjanssens> If a user wants to test a certain nightly, s/he first has to install the giving branch (via the maint or master flatpak repo file or directly from flatpak install)
06:32:34 <gjanssens> That would install the most recent nightly at all times
06:33:25 <gjanssens> Next the user has to find the proper commit via flatpak remote-info --log <reponame> org.gnucash.GnuCash//maint (or master)
06:33:57 <gjanssens> And then run flatpak update --commit=<commit-found-in-log> org.gnucash.GnuCash
06:34:34 <gjanssens> So three steps really. Be we could publish the log ourselves on our website if we want.
06:35:00 <gjanssens> The advantage is there would be less proliferation of installed gnucash nightly builds on your local system (which we have currently)
06:35:13 <gjanssens> That comes at the expense of making it harder to install nightlies.
06:35:27 <gjanssens> I'm not sure if that is really worth it.
06:36:54 <gjanssens> jralls: Effective C++ 3rd edition is not the same as Effective Modern C++ right ? I don't have a copy of the former unfortunately. Is it worth buying still ?
06:44:15 *** Mechtilde has quit IRC
06:44:17 <fell> No, easy installation is more important.
06:44:52 *** Mechtilde has joined #gnucash
06:45:47 <fell> Because of the number of features in online banking the devs need man testers.
06:46:13 <fell> many
06:57:54 * chris just wondering if (ice-9 match) explanation is clear enough for everyone
06:59:32 * chris will still stick around for any easy bug fixes
07:25:24 *** Mechtilde has quit IRC
07:25:58 *** Mechtilde has joined #gnucash
07:39:03 *** chris1 has joined #gnucash
07:44:35 <chris> compiling master: why would my libguile.h suddenly cannot be found?
07:47:15 *** chris has quit IRC
07:48:12 *** chris has joined #gnucash
07:48:12 *** ChanServ sets mode: +v chris
07:50:52 <chris> found it, because libguile is no longer in engine
07:57:26 *** KevinDB has quit IRC
07:57:51 <gjanssens> :)
07:58:17 <gjanssens> Switching between maint and master needs a clean build directory for the time being.
07:58:35 <gjanssens> I have simply set up different clones for maint and master with their own build directories
07:58:42 *** KevinDB has joined #gnucash
07:58:42 *** ChanServ sets mode: +v KevinDB
07:59:08 <gjanssens> (well, I have multiple build directories per branch even, master, master-clang, master-cmake-make,...)
07:59:32 <gjanssens> All to test various build configurations without having to start from scratch all the time
08:00:41 <gjanssens> Though I only really use my my default build (gcc + cmake/ninja) regularly. The others only when I have to verify something specific to that config
08:02:14 *** Gerd has joined #gnucash
08:13:50 *** KevinDB has quit IRC
08:15:05 *** KevinDB has joined #gnucash
08:15:05 *** ChanServ sets mode: +v KevinDB
09:02:13 <chris> ok that's enough whacking the branch.
09:10:30 *** Gerd has quit IRC
09:23:26 *** Gerd has joined #gnucash
09:34:21 <warlord> fell, gjanssens just FYI I am okay with advertising flatpaks from code now.
09:34:54 <gjanssens> warlord: thanks, though you did say that before :)
09:35:11 <warlord> I know, but some things never mind repeating.
09:50:58 *** fell has quit IRC
09:51:09 *** Gerd has quit IRC
09:57:02 <gjanssens> :D
09:57:39 <gjanssens> chris: you have been pushing changes faster than I could formulate my answer...
09:59:13 *** fell has joined #gnucash
09:59:13 *** ChanServ sets mode: +o fell
09:59:28 *** omnireq_ has quit IRC
10:00:49 *** omnireq_ has joined #gnucash
10:12:32 <chris> the changes were merely cleanup/remove dead pasted code. all done now because time to sleep. will review and try tomorrow maybe.
10:14:04 <gjanssens> Good night!
10:14:51 <fell> warlord: we have the links hidden in https://wiki.gnucash.org/wiki/Flatpak#Test_version_from_gnucash.org [de & en] and https://wiki.gnucash.org/wiki/De/Feedback#Ist_das_Problem_bereits_gel.C3.B6st.3F [de only AFAIIK]. Perhaps we should add a section like the latter form into https://www.gnucash.org/download.phtml?
10:19:29 <warlord> fell, I think it's really a question of how hard we want to push (advertise) the flatpak / dailies?
10:20:38 <gjanssens> Not more than we want to push the windows nightlies
10:21:02 <gjanssens> I don't see those mentioned on download.phtml and I don't really see reason to do so.
10:21:45 <warlord> ok
10:21:49 <gjanssens> These are meant to help debugging issues
10:21:54 <fell> Thats the reason for my suggestion of a table like in de/Feedback.
10:21:58 *** omnireq_ has quit IRC
10:22:08 *** omnireq_ has joined #gnucash
10:22:26 <gjanssens> If we put them mainstream, we will get support requests on those as well
10:23:50 *** jervin has joined #gnucash
10:25:16 <gjanssens> I'm ok with that for the cases where we specifically ask a user for it, but I'm not to keen of getting plenty extra requests on versions that are not considered stable just because it's easily accessible.
10:25:55 <gjanssens> I do understand the aqbanking situation makes this slightly awkward right now, but in general users are supposed to install stable versions.
10:27:50 *** Mechtilde has quit IRC
10:29:36 <fell> With a disclaimer "Do not expect any support outside of already existing bugzilla reports"?
10:30:57 *** jervin has quit IRC
10:31:10 *** jervin has joined #gnucash
10:31:15 *** fell has quit IRC
10:31:18 *** fell_laptop has joined #gnucash
10:31:18 *** ChanServ sets mode: +o fell_laptop
10:32:03 *** Gerd has joined #gnucash
10:35:38 <warlord> fell_laptop, nobody reads those disclaimers.
10:35:58 *** fell_laptop is now known as fell
10:38:27 *** jervin has quit IRC
10:38:55 *** omnireq_ has quit IRC
10:40:58 *** sbluhm has quit IRC
11:21:03 *** omnireq has joined #gnucash
11:21:03 *** ChanServ sets mode: +v omnireq
11:49:46 *** storyjesse has joined #gnucash
11:51:42 *** Gerd has quit IRC
11:52:47 *** Gerd has joined #gnucash
12:15:50 *** Gerd has quit IRC
12:31:18 *** gjanssens has quit IRC
12:39:53 *** gjanssens has joined #gnucash
12:39:53 *** ChanServ sets mode: +o gjanssens
12:42:57 *** gjanssens has quit IRC
12:54:36 *** storyjesse has quit IRC
13:00:44 *** Han has joined #gnucash
13:17:31 *** Mechtilde has joined #gnucash
13:27:15 *** guak has joined #gnucash
13:33:10 *** calvinct has joined #gnucash
13:35:51 <jralls> @tell gjanssens Meyers says that Effective C++ is still relevant, but he *does* have an ulterior motive. It was the first C++ book aimed at actual practitioners (as opposed to e.g. James Coplein's seminal Multiparadigm Programming in C++" that was aimed more at the folks writing what was to become the standard library). The 3rd ed. is updated through the 2003 TSes and although some of it is superseded by Effective Modern C++ (e.g. *do not user aut
13:35:51 <gncbot> jralls: The operation succeeded.
13:35:51 <jralls> o_ptr*) there's still a lot of valuable guidance in there.
13:36:16 <jralls> @tell gjanssens o_ptr*) there's still a lot of valuable guidance in there.
13:36:16 <gncbot> jralls: The operation succeeded.
13:39:38 <jralls> @tell gjanssens Another older book still worth rereading from time-to-time is Herb Sutter's Exceptional C++, especially the second section on exception safety, though that material is also available online in the Guru-of-the-week archive at https://herbsutter.com/.
13:39:38 <gncbot> jralls: The operation succeeded.
13:44:39 <warlord> jralls, what's wrong with auto_ptr?
13:46:28 <jralls> It was a failed attempt at std::unique_ptr, deprecated in C++ 11 with a stern warning from the committee to cease its use and switch to unique_ptr--boost's if one couldn't immediately use C++ 11--and was removed from the language in C++ 17.
13:49:33 <jralls> http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1856.html#20.4.5%20-%20Class%20template%20auto_ptr
13:53:04 *** sbluhm has joined #gnucash
13:53:04 *** ChanServ sets mode: +v sbluhm
13:53:22 *** Gerd has joined #gnucash
13:55:28 *** goedible has joined #gnucash
13:55:32 <warlord> Hmm. Interesting.
13:57:45 <goedible> I wonder what the protocol is for asking questions here?
13:59:42 <warlord> goedible, just ask
14:01:12 <jralls> goedible: https://en.wikipedia.org/wiki/Internet_Relay_Chat
14:08:03 <warlord> Hahahah
14:11:14 <goedible> If you have experience with the business side of gNU cash: How can a split transaction be assigned for multiple invoice payments https://www.gnucash.org/docs/v3/C/gnucash-help/busnss-ar-payment1.html. For example my bank statement has a 800$ deposit. That was 3 cheques from three customers. I have created the three invoices. I'm not sure if I have to create a split transaction (
14:12:32 <goedible> or dlete the original and create three separate transactions on my bank statement.
14:12:52 <goedible> or something else...
14:13:08 <warlord> goedible, or just know that when you reconcile that bank account to check off the three payments in that one liner.
14:16:15 <goedible> warlord Thanks. I don't understand. How is it possible to "process as payment" if I do what you suggest?
14:18:54 <warlord> So you can just "ignore" it and know to reconcile 3-in-1. Or you can create a "suspense" account that combines them, but then you lose the mapping to the bank
14:19:20 <warlord> oh, you're importing from the bank and then trying to assign it??
14:20:32 <warlord> You *MAY* be able to split the payment transaction post-import so you have 3 splits into A/R and then apply each split. BUT I don't know if that would work. I was thinking you would just Process Payment each payment manually and so when you reconcile the bank you have 3 transactions.
14:20:38 * warlord doesn't import
14:22:05 <goedible> Warlord: "oh, you're importing from the bank and then trying to assign it??" yes
14:22:38 <warlord> My first response to that is, don't do that. ;)
14:23:04 <goedible> warlord Ye, I have been able to split it. I haven't been able to process the splits individually as payments :(
14:23:17 <warlord> So you'll have two options. One that I KNOW will work, but you'll lose the direct mapping from AR to Bank. The other would keep the mapping *if* it works, but I don't know if it will.
14:23:58 <warlord> Your other option is a suspense account. $800 Suspense-> Bank and then 3 individual transactions from A/R -> Suspense
14:24:24 <warlord> Honestly, it would be easier if you just ran Process Payment when the checks came in and didn't import ;)
14:25:53 <goedible> Yeah so maybe I'll use a "Cheques in Wallet" account to create the 3 entries for processing as payment.
14:26:45 <warlord> That works.
14:27:02 <goedible> suspense account=(cheques in wallet) THanks.
14:27:22 <warlord> Yes
14:28:29 *** frakturfreak has joined #gnucash
14:30:08 *** goedible has quit IRC
14:36:46 *** calvinct has quit IRC
14:43:41 <fell> warlord: And if the bank returns the one or other cheque? ;-)
14:44:42 <warlord> fell, if it's imported then that wouldn't have happened.
14:49:37 *** jervin has joined #gnucash
15:02:17 *** fell has quit IRC
15:02:29 *** fell has joined #gnucash
15:02:29 *** ChanServ sets mode: +o fell
15:04:29 *** Gerd has quit IRC
15:06:36 *** Gerd has joined #gnucash
15:06:46 *** Gerd1 has joined #gnucash
15:08:33 *** fell has quit IRC
15:09:02 *** fell has joined #gnucash
15:09:02 *** ChanServ sets mode: +o fell
15:09:36 *** Gerd has quit IRC
15:09:36 *** Gerd1 is now known as Gerd
15:11:07 *** fell has quit IRC
15:11:08 *** fell_laptop has joined #gnucash
15:11:08 *** ChanServ sets mode: +o fell_laptop
15:25:16 *** JayC has quit IRC
15:28:34 *** JayC has joined #gnucash
15:28:35 *** ChanServ sets mode: +v JayC
15:28:43 *** fell_laptop has quit IRC
15:29:01 *** fell_laptop has joined #gnucash
15:29:01 *** ChanServ sets mode: +o fell_laptop
15:29:49 *** fell_laptop is now known as fell
15:35:59 *** Mechtilde has quit IRC
15:36:22 *** trwww has joined #gnucash
15:36:23 *** ChanServ sets mode: +v trwww
15:46:53 *** fell has quit IRC
15:48:40 *** fell_laptop has joined #gnucash
15:48:40 *** ChanServ sets mode: +o fell_laptop
15:48:40 *** fell_laptop is now known as fell
15:48:59 *** fell has joined #gnucash
15:48:59 *** ChanServ sets mode: +o fell
16:04:31 *** fell has quit IRC
16:04:41 *** fell has joined #gnucash
16:04:41 *** ChanServ sets mode: +o fell
16:10:39 *** Gerd has quit IRC
16:47:05 *** jervin has quit IRC
16:47:17 *** jervin has joined #gnucash
16:48:42 *** Aussie_matt has joined #gnucash
16:48:59 *** Han has quit IRC
16:50:10 <trwww> I'm building from source and want gnucash in /opt/gnucash
16:50:19 <trwww> I did cmake with: cmake -DCMAKE_INSTALL_PREFIX=/opt ../gnucash-3.8
16:50:19 <trwww> make failed on its first file install trying to install in opt/share
16:50:28 <trwww> I deleted and rebuilt my build dir, this time with: cmake -DCMAKE_INSTALL_PREFIX=/opt/gnucash ../gnucash-3.8
16:50:36 <trwww> It looks like this time it did install gnucash, but 'make install' failed before finishing with:
16:50:45 <trwww> Make Error at gnucash/cmake_install.cmake:73 (file):
16:50:45 *** fell has quit IRC
16:50:46 <trwww> file cannot create directory: /etc/opt/gnucash/gnucash.
16:50:55 *** fell has joined #gnucash
16:50:55 *** ChanServ sets mode: +o fell
16:52:22 <jralls> The /opt layout enforced by cmake requires installing the config files in /etc so if you're going to use /opt you must `sudo make install`.
16:54:30 <trwww> hrm
16:55:11 *** fell has quit IRC
16:55:21 *** fell has joined #gnucash
16:55:21 *** ChanServ sets mode: +o fell
17:00:30 <trwww> fun: $ /opt/gnucash/bin/gnucash
17:00:30 <trwww> Trace/breakpoint trap (core dumped)
17:01:00 *** User has joined #gnucash
17:05:27 *** fell has quit IRC
17:05:48 *** fell has joined #gnucash
17:05:48 *** ChanServ sets mode: +o fell
17:08:19 *** frakturfreak has quit IRC
17:53:09 *** User has quit IRC
18:08:08 *** oozer has joined #gnucash
18:14:48 *** sbluhm has quit IRC
18:20:58 *** o01eg_ has joined #gnucash
18:22:06 *** o01eg has quit IRC
18:24:06 *** fell_laptop has joined #gnucash
18:24:06 *** ChanServ sets mode: +o fell_laptop
18:24:06 *** fell has quit IRC
18:24:22 *** fell_laptop is now known as fell
18:33:41 *** o01eg_ has quit IRC
18:33:49 *** o01eg_ has joined #gnucash
18:42:29 *** fell has quit IRC
18:42:37 *** fell has joined #gnucash
18:42:37 *** ChanServ sets mode: +o fell
19:13:55 *** omnireq has quit IRC
19:21:59 *** fell has quit IRC
19:29:13 *** fell has joined #gnucash
19:29:13 *** ChanServ sets mode: +o fell
19:41:59 *** Gerd has joined #gnucash
19:49:17 *** fell has quit IRC
19:51:38 *** fell has joined #gnucash
19:51:38 *** ChanServ sets mode: +o fell
20:04:29 *** Gerd has quit IRC
20:14:26 *** omnireq has joined #gnucash
20:18:19 *** Gerd has joined #gnucash
20:36:02 *** jervin has quit IRC
20:37:37 *** oozer has quit IRC
20:43:28 *** guak has quit IRC
21:13:25 *** Gerd has quit IRC
21:16:26 *** Gerd has joined #gnucash
22:01:39 *** flynn has joined #gnucash
22:18:11 *** Gerd1 has joined #gnucash
22:19:08 *** Gerd has quit IRC
22:19:08 *** Gerd1 is now known as Gerd
22:50:07 *** flynn has quit IRC