Re: [GNC] Data format compatibility between recent versions

2018-05-14 Thread Adrien Monteleone 
For backwards compatibility, my understanding is you’ll need version 2.6.21 on 
the Ubuntu box. (but why not just use 3.1 there as well?)

Regards,
Adrien

> On May 14, 2018, at 2:45 PM, John Pastore  wrote:
> 
> I reviewed FAQ section 3.3, but it does not cover more recent versions of
> Gnucash.
> 
> I use Gnucash 3.1 on Windows (7) and Gnucash 2.6.12 on Linux (Ubuntu 16.04
> LTS), soon to transition to 2.6.19 on Ubuntu 18.04 LTS.
> 
> Data file portability appears to be fine in both directions, but I just
> want to make sure there are no specific cases that might result in data
> file corruption.
> 
> Any advice much appreciated!
> 
> John
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
> 


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Data format compatibility between recent versions

2018-05-14 Thread John Ralls 
Dave,

Yes, there are some features in 3.1 that will block using earlier versions of 
2.6. You can see the list and the earliest version for each at 
https://github.com/Gnucash/gnucash/blob/maint/libgnucash/engine/gnc-features.c#L42
 
.

Regards,
John Ralls


> On May 14, 2018, at 6:25 PM, David Carlson  
> wrote:
> 
> John,
> 
> I was not clear.  I really wanted clarification from the developers.  I
> suspect that you may not be using features that are not compatible between
> the versions as I know that there are some features that are not backward
> compatible.
> 
> David C
> 
> On Mon, May 14, 2018, 7:59 PM John Pastore  wrote:
> 
>> Not sure if you meant you need clarification from ME or ...?
>> 
>> Anyway, here's my history:
>> 
>> 1) Created original data file using GNC 2.6.12 on Ubuntu 16.04 LTS
>> 
>> 2) Months later installed GNC 2.6.19 on Win 7 and copied datafile from #1
>> with no issues.
>> - this datafile included (1) monthly scheduled transaction and about (20)
>> securities each with about (5) manual price history updates
>> 
>> 3) Weeks later installed GNC 3.1 on Win 7 and used same datafile from #2
>> with no issues.
>> 
>> 4) Weeks later got Finance::Quote automatic price updates working via
>> AlphaVantage on #3.
>> 
>> 5) Days later copied datafile from #4 back to GNC 2.6.12 on Ubuntu.
>> Everything looked fine including:
>> - scheduled transaction notice for monthly transaction whose date had
>> since passed by
>> - price history for all securities including more recent entries from
>> Finance::Quote
>> - security details including (to my surprise) updated source for online
>> updates to "Unknown:AlphaVantage" from "Single:Vanguard" (which had never
>> worked) for all (20) securities.
>> 
>> 6) Days later (just now) copied most recent datafile from #4 back to GNC
>> 2.6.12 on Ubuntu just to see if prior success had been a fluke.  Everything
>> still looks fine.
>> 
>> Hope this history is helpful.
>> 
>> John
>> 
>> On Mon, May 14, 2018 at 6:22 PM, David Carlson <
>> david.carlson@gmail.com> wrote:
>> 
>>> We need clarification on this because I recall seeing that files touched
>>> by testing releases in the 2.7 group and 3.0 and 3.1 were changed so they
>>> were no longer readable by releases prior to 2.6.21.
>>> 
>>> David C
>>> 
>>> On Mon, May 14, 2018 at 2:45 PM, John Pastore 
>>> wrote:
>>> 
 I reviewed FAQ section 3.3, but it does not cover more recent versions of
 Gnucash.
 
 I use Gnucash 3.1 on Windows (7) and Gnucash 2.6.12 on Linux (Ubuntu
 16.04
 LTS), soon to transition to 2.6.19 on Ubuntu 18.04 LTS.
 
 Data file portability appears to be fine in both directions, but I just
 want to make sure there are no specific cases that might result in data
 file corruption.
 
 Any advice much appreciated!
 
 John
 ___
 gnucash-user mailing list
 gnucash-user@gnucash.org
 To update your subscription preferences or to unsubscribe:
 https://lists.gnucash.org/mailman/listinfo/gnucash-user
 If you are using Nabble or Gmane, please see
 https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
 -
 Please remember to CC this list on all your replies.
 You can do this by using Reply-To-List or Reply-All.
 
>>> 
>>> 
>> 
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Data format compatibility between recent versions

2018-05-14 Thread David Carlson 
John,

I was not clear.  I really wanted clarification from the developers.  I
suspect that you may not be using features that are not compatible between
the versions as I know that there are some features that are not backward
compatible.

David C

On Mon, May 14, 2018, 7:59 PM John Pastore  wrote:

> Not sure if you meant you need clarification from ME or ...?
>
> Anyway, here's my history:
>
> 1) Created original data file using GNC 2.6.12 on Ubuntu 16.04 LTS
>
> 2) Months later installed GNC 2.6.19 on Win 7 and copied datafile from #1
> with no issues.
> - this datafile included (1) monthly scheduled transaction and about (20)
> securities each with about (5) manual price history updates
>
> 3) Weeks later installed GNC 3.1 on Win 7 and used same datafile from #2
> with no issues.
>
> 4) Weeks later got Finance::Quote automatic price updates working via
> AlphaVantage on #3.
>
> 5) Days later copied datafile from #4 back to GNC 2.6.12 on Ubuntu.
> Everything looked fine including:
> - scheduled transaction notice for monthly transaction whose date had
> since passed by
> - price history for all securities including more recent entries from
> Finance::Quote
> - security details including (to my surprise) updated source for online
> updates to "Unknown:AlphaVantage" from "Single:Vanguard" (which had never
> worked) for all (20) securities.
>
> 6) Days later (just now) copied most recent datafile from #4 back to GNC
> 2.6.12 on Ubuntu just to see if prior success had been a fluke.  Everything
> still looks fine.
>
> Hope this history is helpful.
>
> John
>
> On Mon, May 14, 2018 at 6:22 PM, David Carlson <
> david.carlson@gmail.com> wrote:
>
>> We need clarification on this because I recall seeing that files touched
>> by testing releases in the 2.7 group and 3.0 and 3.1 were changed so they
>> were no longer readable by releases prior to 2.6.21.
>>
>> David C
>>
>> On Mon, May 14, 2018 at 2:45 PM, John Pastore 
>> wrote:
>>
>>> I reviewed FAQ section 3.3, but it does not cover more recent versions of
>>> Gnucash.
>>>
>>> I use Gnucash 3.1 on Windows (7) and Gnucash 2.6.12 on Linux (Ubuntu
>>> 16.04
>>> LTS), soon to transition to 2.6.19 on Ubuntu 18.04 LTS.
>>>
>>> Data file portability appears to be fine in both directions, but I just
>>> want to make sure there are no specific cases that might result in data
>>> file corruption.
>>>
>>> Any advice much appreciated!
>>>
>>> John
>>> ___
>>> gnucash-user mailing list
>>> gnucash-user@gnucash.org
>>> To update your subscription preferences or to unsubscribe:
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> If you are using Nabble or Gmane, please see
>>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>>> -
>>> Please remember to CC this list on all your replies.
>>> You can do this by using Reply-To-List or Reply-All.
>>>
>>
>>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Data format compatibility between recent versions

2018-05-14 Thread John Pastore 
Not sure if you meant you need clarification from ME or ...?

Anyway, here's my history:

1) Created original data file using GNC 2.6.12 on Ubuntu 16.04 LTS

2) Months later installed GNC 2.6.19 on Win 7 and copied datafile from #1
with no issues.
- this datafile included (1) monthly scheduled transaction and about (20)
securities each with about (5) manual price history updates

3) Weeks later installed GNC 3.1 on Win 7 and used same datafile from #2
with no issues.

4) Weeks later got Finance::Quote automatic price updates working via
AlphaVantage on #3.

5) Days later copied datafile from #4 back to GNC 2.6.12 on Ubuntu.
Everything looked fine including:
- scheduled transaction notice for monthly transaction whose date had since
passed by
- price history for all securities including more recent entries from
Finance::Quote
- security details including (to my surprise) updated source for online
updates to "Unknown:AlphaVantage" from "Single:Vanguard" (which had never
worked) for all (20) securities.

6) Days later (just now) copied most recent datafile from #4 back to GNC
2.6.12 on Ubuntu just to see if prior success had been a fluke.  Everything
still looks fine.

Hope this history is helpful.

John

On Mon, May 14, 2018 at 6:22 PM, David Carlson 
wrote:

> We need clarification on this because I recall seeing that files touched
> by testing releases in the 2.7 group and 3.0 and 3.1 were changed so they
> were no longer readable by releases prior to 2.6.21.
>
> David C
>
> On Mon, May 14, 2018 at 2:45 PM, John Pastore  wrote:
>
>> I reviewed FAQ section 3.3, but it does not cover more recent versions of
>> Gnucash.
>>
>> I use Gnucash 3.1 on Windows (7) and Gnucash 2.6.12 on Linux (Ubuntu 16.04
>> LTS), soon to transition to 2.6.19 on Ubuntu 18.04 LTS.
>>
>> Data file portability appears to be fine in both directions, but I just
>> want to make sure there are no specific cases that might result in data
>> file corruption.
>>
>> Any advice much appreciated!
>>
>> John
>> ___
>> gnucash-user mailing list
>> gnucash-user@gnucash.org
>> To update your subscription preferences or to unsubscribe:
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> If you are using Nabble or Gmane, please see
>> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
>> -
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>>
>
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] Data format compatibility between recent versions

2018-05-14 Thread David Carlson 
We need clarification on this because I recall seeing that files touched by
testing releases in the 2.7 group and 3.0 and 3.1 were changed so they were
no longer readable by releases prior to 2.6.21.

David C

On Mon, May 14, 2018 at 2:45 PM, John Pastore  wrote:

> I reviewed FAQ section 3.3, but it does not cover more recent versions of
> Gnucash.
>
> I use Gnucash 3.1 on Windows (7) and Gnucash 2.6.12 on Linux (Ubuntu 16.04
> LTS), soon to transition to 2.6.19 on Ubuntu 18.04 LTS.
>
> Data file portability appears to be fine in both directions, but I just
> want to make sure there are no specific cases that might result in data
> file corruption.
>
> Any advice much appreciated!
>
> John
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

[GNC] Data format compatibility between recent versions

2018-05-14 Thread John Pastore 
I reviewed FAQ section 3.3, but it does not cover more recent versions of
Gnucash.

I use Gnucash 3.1 on Windows (7) and Gnucash 2.6.12 on Linux (Ubuntu 16.04
LTS), soon to transition to 2.6.19 on Ubuntu 18.04 LTS.

Data file portability appears to be fine in both directions, but I just
want to make sure there are no specific cases that might result in data
file corruption.

Any advice much appreciated!

John
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.