Re: [GNC-dev] Need help - several tests fail
Op donderdag 22 augustus 2019 05:37:12 CEST schreef John Ralls: > > On Aug 21, 2019, at 3:28 PM, Christian Gruber > > wrote: > > > > Ok, that was a useful hint. Clearing the guile cache helped. I'm one step > > further. I have no idea, what led to this situation. I couldn't reproduce > > this again. > > > > Next problem is that still several tests fail with the following output: > > > > ERROR: no code for module (gnucash engine test srfi64-extras) > > Which means that they're not finding > libgnucash/engine/test/srfi64-extras.scm or perhaps srfi64-extras.go Can > you figure out why? It might help to run make with VERBOSE=1 so that the > whole command is printed for each step or to switch to ninja which dumps > any failed commands without being asked and is also about 10x faster than > make. > > Regards, > John Ralls It can also be an as of yet undiscovered build dependency issue (there still are a few on maint). You didn't post any error output (or full build log) so it's hard to tell. In the build logs do you find a message logging the build of engine/test/ srfi64-extras.go before you get your errors ? Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] [MAINT] Cleaning up Code (the server)
Op dinsdag 13 augustus 2019 22:53:34 CEST schreef John Ralls: > > On Aug 13, 2019, at 9:14 AM, Derek Atkins wrote: > >> There don't seem to be any flatpak release builds. Should there be and if > >> so should I include them in the release downloads on SourceForge and > >> Github? > > > > Not yet. Remember that right now code is sitting behind a tiny straw. > > Once I can move back to my main network then we can advertise that. > > This wouldn't be advertising, it would be me downloading one flatpack at > release and uploading it to SF and Github just as I do with Windows > releases. Flatpak by default works slightly differently: instead of distributing a selfcontained installer it stores all builds in a public repo and that's where users would expect to get it from. The most widely known and used repo is currently flathub.org. Also you don't upload a fully built package to flathub. Instead you commit the build manifest and their buildsystem will use that to reproduce the necessary build artefacts that allows users to install the newest gnucash package from flathub. I have recently become co-maintainer (well, defacto maintainer) of the gnucash repo on flathub. I have been tweaking their build manifest file to be closer to the one we use for our nightly builds. My ultimate goal is to be able to simply push the manifest generated for our release nightly build to flathub. The idea is that if our nightly build server can successfully build the release, flathub will be able to as well. As they use the same strictly defined sandboxes that should work most of the cases. The only caveat: flathub builds for 4 architectures (arm, aarch64, i386, x86_64), we build only for one. So if we have architecture incompatibilities, things may break anyway. That would require manual tweaks of the manifest for flathub. The typical handling of package failures (on distros as well) is adding patches to fix the issue. These patches would probably also be applied to our source repos so they'll become incorporated in the next release tarball. Regards, Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
[GNC-dev] OARS classification of gnucash
Gnome and Flathub use age rating data to classify applications as appropriate or not for certain groups of users. Both are using the Open Age Rating Service (OARS) [1] for this. I went to the trouble of filling the questionnaire for gnucash and ended up with this rating: mild "social-info" may be a bit odd, but when selecting this option, I was considering the AlphaVantage API key which I presume can/will be used by Alpha Vantage to track the user. Does anyone have remarks/issues with this classification ? If so, please share, otherwise I'll use this for the next gnucash release. Regards, Geert [1] https://hughsie.github.io/oars/ ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] OARS classification of gnucash
> On Aug 22, 2019, at 10:00 AM, Geert Janssens > wrote: > > Gnome and Flathub use age rating data to classify applications as appropriate > or not for certain groups of users. Both are using the Open Age Rating > Service > (OARS) [1] for this. > > I went to the trouble of filling the questionnaire for gnucash and ended up > with this rating: > > >mild > > > "social-info" may be a bit odd, but when selecting this option, I was > considering the AlphaVantage API key which I presume can/will be used by > Alpha > Vantage to track the user. > > Does anyone have remarks/issues with this classification ? If so, please > share, otherwise I'll use this for the next gnucash release. > > Regards, > > Geert > > [1] https://hughsie.github.io/oars/ I don't know that it matters much, I wouldn't really expect a 12 year old to be interested in GnuCash anyway... and besides, 12 year olds know how to get around most age restrictions. I don't think that there's anything tracking related that the Alphavantage API key gets them. They can already get the requesting IP and associate the list of requested prices with it just like all of the other price sources. That's not to say that GnuCash users who use price quotes or online banking aren't exposed to tracking, just that it's not limited to Alphavantage. It's anyway pretty minor compared to web-browser use, so I went looking for Epiphany's age rating and couldn't find one. Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] OARS classification of gnucash
Op donderdag 22 augustus 2019 19:50:38 CEST schreef John Ralls: > > On Aug 22, 2019, at 10:00 AM, Geert Janssens > > wrote: > > > > Gnome and Flathub use age rating data to classify applications as > > appropriate or not for certain groups of users. Both are using the Open > > Age Rating Service (OARS) [1] for this. > > > > I went to the trouble of filling the questionnaire for gnucash and ended > > up > > > > with this rating: > > > > > >mild > > > > > > > > "social-info" may be a bit odd, but when selecting this option, I was > > considering the AlphaVantage API key which I presume can/will be used by > > Alpha Vantage to track the user. > > > > Does anyone have remarks/issues with this classification ? If so, please > > share, otherwise I'll use this for the next gnucash release. > > > > Regards, > > > > Geert > > > > [1] https://hughsie.github.io/oars/ > > I don't know that it matters much, I wouldn't really expect a 12 year old to > be interested in GnuCash anyway... and besides, 12 year olds know how to > get around most age restrictions. > Sure, it doesn't matter that much, but the OARS piqued my curiosity. Also you're probably looking for more in it than it really does. It just labels applications. There's no actual restricting going on. Having said that, it is thanks to a system as OARS that users can easily know our application is not riddled with advertisements or trackers. For us that may be obvious. We're so used to this in the open source world. Flathub (or the Ubuntu app store for that matter) however also ships commercial applications, which do have advertisements or language that's not acceptable in all circumstances. > I don't think that there's anything tracking related that the Alphavantage > API key gets them. They can already get the requesting IP and associate the > list of requested prices with it just like all of the other price sources. > That's not to say that GnuCash users who use price quotes or online banking > aren't exposed to tracking, just that it's not limited to Alphavantage. > It's anyway pretty minor compared to web-browser use, so I went looking for > Epiphany's age rating and couldn't find one. The age rating is fairly new and still voluntary. So many applications don't do it yet. Further the definition of "Mild" according to the OARS is: "Using any online api" We do use online api's via Finance::Quote so that's why I selected it. How much tracking actually goes on we don't know. We don't have to. We only warn the user they may potentially be tracked. Regards, Geert ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
Re: [GNC-dev] German online banking users would need a 3.7 release before mid-September...
> On Aug 11, 2019, at 11:43 AM, Christian Stimming > wrote: > > Am Samstag, 10. August 2019, 20:32:00 CEST schrieb John Ralls: > >> Regardless, we can do a snap release as soon as we can get the registration >> number issue sorted and I can make time to do the release. > > The windows nightly has built last night. On gnucash-de I asked windows-users > to start testing it. Let's see whether this is indeed sufficiently > implemented. Once some positive feedback has arrived, a 3.7 release sometime > in August would indeed be great - as it fits best for you. Christian, Has there been sufficient testing to proceed with a release this weekend? Regards, John Ralls ___ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
