Re: [GNC-dev] AppImage

2019-01-15 Thread Derek Atkins
Michael,

"Fross, Michael"  writes:

> Hello Derek,
>
> Is the goal to have a Flatpak image be part of the standard release process? 
> By this I mean to say, will there be a Flatpak build released with the windows
> and mac builds upon a new release?
>
> I think that would be a great addition and help ease a lot of the build
> challenges Linux users go through with each release.
>
> Michael

The immediate goal is to have nightly builds.  The longer term goal is,
yes, to automate a flatpak build as part of the release process.  Right
now that part isn't quite automated, and indeed the tag-build script
isn't working properly (Geert is working on it).

Some of this will need to wait until I can upgrade code to a newer OS
which includes a newer flatpak-builder.  I will need to schedule some
time to perform that maintenance -- maybe during the Superbowl ;)

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


[GNC-dev] [MAINT] server upgrade planned Feb 3, 2019 1200-2300 US/EST

2019-01-15 Thread Derek Atkins
Hi,

PLANNED MAINTENANCE
WHAT:  Upgrading Operating System on Code
WHEN:  Feb 3, 2019  1200-2300 US/EST (1700-0400 UTC)


tl;dr: I am planning to upgrade the OS on code.gnucash.org on February
3, 2019 from 1200-2300 US/EDT (1700-0400 UTC).  During this
time, git master, wiki, email/mailman, and gncbot/irc logs will
all be unavailable.  I'll be on #gnucash IRC for real-time
updates and notices.


Long version:

The GnuCash "everything" server is getting a little long on the tooth,
and to enable some upgraded build tools I plan to upgrade the server
from Fedora 25 to Fedora 29.  I plan to do this upgrade on Sunday,
February 3, 2019, starting somewhere around 12:00 noon US/EST (although
my personal schedule might push that back, hense the long maintenance
window).  I've upgraded a few systems from F25 -> F29 already, some of
them upgraded in an hour, one system took over 4 hours.

Code has lots of services so I expect it will take a long time to
upgrade and verify that everything is working.

During the upgrade window code will be unavailable, and the services
running on code will be unavailable.  I will stay on IRC during the
upgrade to make real-time announcements.

Please let me know if this time frame does not work for you.

Thanks,

-derek

-- 
   Derek Atkins 617-623-3745
   de...@ihtfp.com www.ihtfp.com
   Computer and Internet Security Consultant
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


[GNC-dev] Alphavantage strategies

2019-01-15 Thread Wm via gnucash-devel
I was unaware [1] until recently that Alphavantage wanted individuals / 
non-subscribers / poor people / whoever doesn't pay / to back off a bit. 
 I don't have a problem with this, it is a good free service and it has 
been obvious they're struggling.


[1] but not surprised to discover

There have been postings in the .user list (one of them being mine) that 
involve editing files in the F:Q install to mitigate this.  Not a good 
idea as the next update overwrites any changes, users shouldn't have to 
get involved, may not be reading the list, sleep(15) is arbitrary, etc.


Let's consider some simple backoff strategies that gnc could implement, 
feel free to add your own.


Wm's suggestion
===
only collect if the most recent price is more than 1 day (or 12 hours, 
etc) old [2].  this sort of fits in with the existing post collection 
query, i.e. always store the good prices that have been obtained, 
instead ask the user, "do you want to try and fetch the other prices / 
rates again".  this provides a natural pause to Alphavantage as gnc 
won't be hitting it for prices it just got a second time and would only 
be requesting the prices it didn't get last time.


[2] I use this in my own collections (external to gnc) run by cron, some 
more obscure currency pairs are only available a few hours a day, I 
don't even try if the most recent is less than a day old.


--
Wm













___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


Re: [GNC-dev] AppImage

2019-01-15 Thread Alen Siljak
That's great news!
I've collected the links I found so far to this issue: 
https://bugs.gnucash.org/show_bug.cgi?id=796019
It is now closed since the AppImage is there and there are ongoing efforts in 
getting an official Flatpak image.

> Sent: Friday, January 11, 2019 at 6:34 PM
> From: "Derek Atkins" 
> To: cicko 
> Cc: gnucash-devel@gnucash.org
> Subject: Re: [GNC-dev] AppImage
>
> For the record, we are working on getting a Flatpak build done locally.
> It's on my to-do to set up a "nightly" build.
> -derek
> 
> cicko  writes:
> 
> > Someone actually created an AppImage repo for GnuCash at
> > https://github.com/ecmu/gnucash.AppImage
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel