[GNC-dev] help
Mike Donovan
donovan.michael.g at gmail.com
Sun Jan 27 14:56:45 EST 2019
Kindly unsubscribe. My perceived problem was due to operator error.
Thanks,
Mike Donovan
Sent from Mail for Windows 10
From: gnucash-devel-request at gnucash.org
Sent: Sunday, January 27, 2019 12:00
To: gnucash-devel at gnucash.org
Subject: gnucash-devel Digest, Vol 190, Issue 35
Send gnucash-devel mailing list submissions to
gnucash-devel at gnucash.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
or, via email, send a message with subject or body 'help' to
gnucash-devel-request at gnucash.org
You can reach the person managing the list at
gnucash-devel-owner at gnucash.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of gnucash-devel digest..."
Today's Topics:
1. Re: Test failure (Stephen M. Butler)
2. Re: Test failure (Christopher Lam)
3. GnuCash Maint - general problem to enter year for 30.12. +
31.12. ? (Carsten Rinke)
4. Re: Test failure (John Ralls)
5. Re: GnuCash Maint - general problem to enter year for 30.12.
+ 31.12. ? (John Ralls)
6. Re: Test failure (Stephen M. Butler)
----------------------------------------------------------------------
Message: 1
Date: Sat, 26 Jan 2019 23:04:44 -0800
From: "Stephen M. Butler" <kg7je at arrl.net>
To: Christopher Lam <christopher.lck at gmail.com>, "Stephen M. Butler"
<kg7je at arrl.net>
Cc: gnucash-devel <gnucash-devel at gnucash.org>
Subject: Re: [GNC-dev] Test failure
Message-ID: <6e534fa0-bcd6-05d8-d0aa-0a3f5775caeb at gmail.com>
Content-Type: text/plain; charset=utf-8
On 1/26/19 10:54 PM, Christopher Lam wrote:
> Stephen please spend some CPU burning time on my chartJS branch which
> needs beta testing?
>
> $git clone
> https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart
Thought I'd start this while headed toward some z's.? Too tired to
figure out what happened.
?git clone
https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart
Cloning into 'maint-chartjs-budget-barchart'...
fatal: repository
'https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart/'
not found
--Steve
>
>
> On 27/1/19 2:52 pm, Stephen M. Butler wrote:
>> On 1/26/19 10:29 PM, John Ralls wrote:
>>> Stephen,
>>>
>>> By all means learn about git bisect, it's an extremely useful
>>> troubleshooting tool. But don't exercise yourself too much about
>>> this particular failure, Chris and I know exactly what commit caused
>>> it and that the underlying cause is a bug in ICU (International
>>> Components for Unicode, http://site.icu-project.org/) versions 57-62.
>> I figured the devs were way ahead of me.? And I'm burning the CPU this
>> evening finding that I can't compile 3.4-21 thru (I'm guessing) 3.4-38.
>> I'm up to 3.4-29 at this point and already know that -37 and -38 don't
>> compile on my box.? But -39, -40, and -43 do.? Don't know about -41 and
>> -42 (and probably won't check them).
>>
>> Busy day tomorrow so I doubt the cpu will even get warmed up!? It's
>> pushing 11 pm so I'll call it quits on this exercise.
>>
>> Thanks for the details.
>>
>> --Steve
>>
>>> I had thought that the problem was confined to 1969, but tonight got
>>> https://bugs.gnucash.org/show_bug.cgi?id=797067 which makes me think
>>> that it's every year, so more testing needed.
>>>
>>> Regards,
>>> John Ralls
>>>
>>>
>>>> On Jan 26, 2019, at 5:55 PM, Stephen M. Butler <kg7je at arrl.net> wrote:
>>>>
>>>> On 1/26/19 3:13 AM, Christopher Lam wrote:
>>>>> Another experiment. Try prefix your build with "TZ=UTC " on current
>>>>> maint.
>>>>>
>>>>> Eg if using ninja, it'll be "TZ=UTC ninja check"
>>>> TZ=UTC dpkg- -rfakeroot -b -uc
>>>>
>>>> ....
>>>>
>>>> End testing: Jan 27 01:47 UTC
>>>> + exit 2
>>>> debian/rules:65: recipe for target 'override_dh_auto_test' failed
>>>> make[1]: *** [override_dh_auto_test] Error 2
>>>> make[1]: Leaving directory '/home/steve/Projects/GnuCash/gnucash'
>>>> debian/rules:24: recipe for target 'build' failed
>>>> make: *** [build] Error 2
>>>> dpkg-buildpackage: error: debian/rules build subprocess returned exit
>>>> status 2
>>>>
>>>> Same error -- Test 109 that fails.
>>>>
>>>>
>>>> This is with the patches for 3.4.? I verified before Sabbath that 3.4
>>>> builds and passes the tests.? Tried your test first thing this evening
>>>> after git checkout maint and git pull.? I am at 3.4-43-g84d1c3645
>>>> which
>>>> builds but doesn't pass the tests.? So, I could build turning off the
>>>> test step.
>>>>
>>>> However, Friday I was learning more about git bisect to see if I could
>>>> figure out which patch caused the tests to start failing.? However, a
>>>> couple of items got in the way:? 1--time;? 2--some commits don't
>>>> build.
>>>> That messed me up a bit.? So, I may start over again with the bisect
>>>> (just for my own edification) and see what happens.? Maybe this time
>>>> I'll do a git describe each time and take notes so I'll be a little
>>>> more
>>>> cognizant of what I'm learning.? <<did that make sense>>
>>>>
>>>>
>>>> --Steve (in the dark)
>>>>
>>>>> On Fri., 25 Jan. 2019, 11:52 Stephen M. Butler <kg7je at arrl.net
>>>>> <mailto:kg7je at arrl.net> wrote:
>>>>>
>>>>> ??? On 1/24/19 7:36 PM, Christopher Lam wrote:
>>>>>> Revert is a git terminology, not a gnucash one. Welcome to version
>>>>>> control.
>>>>> ??? That's the manual to which I referred.? It meant something
>>>>> else to my
>>>>> ??? mind when I first saw your post.? But, after further thought, my
>>>>> ??? previous thought was faulty.
>>>>>
>>>>>
>>>>> ??? My first boss after college would draw a picture to describe the
>>>>> ??? difference between a bug and a feature.
>>>>>
>>>>> ??? I can't draw so a word will have to do (at less than a thousand
>>>>> ??? words)!
>>>>>
>>>>> ??? BUG:? draw stick figure.
>>>>>
>>>>>
>>>>> ??? FEATURE:? Add pants, tie, gloves, shoes and a top hat.
>>>>>
>>>>>
>>>>> ??? MORAL:? A feature is a bug all dressed up and ready to go out.
>>>>>
>>>>>> Please remember this revert is reverting a buggy code with a
>>>>> ??? previous
>>>>>> buggy code, so, cannot be consisted safe to package; best wait until
>>>>>> the clever devs can find a proper fix for gnc-date.
>>>>>>
>>>>>> On Fri., 25 Jan. 2019, 05:46 Stephen M. Butler <kg7je at arrl.net
>>>>> ??? <mailto:kg7je at arrl.net>
>>>>>> <mailto:kg7je at arrl.net <mailto:kg7je at arrl.net>> wrote:
>>>>>>
>>>>>> ????? OH!? Light bulb on!
>>>>>> ????? OK.? I understand what you said earlier.? I'll put the patches
>>>>>> ????? back into
>>>>>> ????? the packaging.
>>>>>>
>>>>>> ????? Thanks for clearing that up.
>>>>>>
>>>>>> ????? --Steve
>>>>>>
>>>>>> ????? PS Looking in manual for 'revert' command.
>
--
Stephen M Butler, PMP, PSM
Stephen.M.Butler51 at gmail.com
kg7je at arrl.net
253-350-0166
-------------------------------------------
GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8
------------------------------
Message: 2
Date: Sun, 27 Jan 2019 15:20:19 +0800
From: Christopher Lam <christopher.lck at gmail.com>
To: "Stephen M. Butler" <kg7je at arrl.net>
Cc: gnucash-devel <gnucash-devel at gnucash.org>
Subject: Re: [GNC-dev] Test failure
Message-ID: <c7f9fd04-b001-9a6b-4ea2-26c127b12db4 at gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Ok my bad
May be safer to reuse your own gnucash repository
* cd gnucash
* git remote add chris https://github.com/christopherlam/gnucash.git
* git fetch --all
* git checkout chris/maint-chartjs-budget-barchart
* dpkg etc
and to revert to main branch:
* git checkout maint
On 27/1/19 3:04 pm, Stephen M. Butler wrote:
> On 1/26/19 10:54 PM, Christopher Lam wrote:
>> Stephen please spend some CPU burning time on my chartJS branch which
>> needs beta testing?
>>
>> $git clone
>> https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart
>
> Thought I'd start this while headed toward some z's.? Too tired to
> figure out what happened.
>
> ?git clone
> https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart
> Cloning into 'maint-chartjs-budget-barchart'...
> fatal: repository
> 'https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart/'
> not found
>
>
> --Steve
>
>>
>> On 27/1/19 2:52 pm, Stephen M. Butler wrote:
>>> On 1/26/19 10:29 PM, John Ralls wrote:
>>>> Stephen,
>>>>
>>>> By all means learn about git bisect, it's an extremely useful
>>>> troubleshooting tool. But don't exercise yourself too much about
>>>> this particular failure, Chris and I know exactly what commit caused
>>>> it and that the underlying cause is a bug in ICU (International
>>>> Components for Unicode, http://site.icu-project.org/) versions 57-62.
>>> I figured the devs were way ahead of me.? And I'm burning the CPU this
>>> evening finding that I can't compile 3.4-21 thru (I'm guessing) 3.4-38.
>>> I'm up to 3.4-29 at this point and already know that -37 and -38 don't
>>> compile on my box.? But -39, -40, and -43 do.? Don't know about -41 and
>>> -42 (and probably won't check them).
>>>
>>> Busy day tomorrow so I doubt the cpu will even get warmed up!? It's
>>> pushing 11 pm so I'll call it quits on this exercise.
>>>
>>> Thanks for the details.
>>>
>>> --Steve
>>>
>>>> I had thought that the problem was confined to 1969, but tonight got
>>>> https://bugs.gnucash.org/show_bug.cgi?id=797067 which makes me think
>>>> that it's every year, so more testing needed.
>>>>
>>>> Regards,
>>>> John Ralls
>>>>
>>>>
>>>>> On Jan 26, 2019, at 5:55 PM, Stephen M. Butler <kg7je at arrl.net> wrote:
>>>>>
>>>>> On 1/26/19 3:13 AM, Christopher Lam wrote:
>>>>>> Another experiment. Try prefix your build with "TZ=UTC " on current
>>>>>> maint.
>>>>>>
>>>>>> Eg if using ninja, it'll be "TZ=UTC ninja check"
>>>>> TZ=UTC dpkg- -rfakeroot -b -uc
>>>>>
>>>>> ....
>>>>>
>>>>> End testing: Jan 27 01:47 UTC
>>>>> + exit 2
>>>>> debian/rules:65: recipe for target 'override_dh_auto_test' failed
>>>>> make[1]: *** [override_dh_auto_test] Error 2
>>>>> make[1]: Leaving directory '/home/steve/Projects/GnuCash/gnucash'
>>>>> debian/rules:24: recipe for target 'build' failed
>>>>> make: *** [build] Error 2
>>>>> dpkg-buildpackage: error: debian/rules build subprocess returned exit
>>>>> status 2
>>>>>
>>>>> Same error -- Test 109 that fails.
>>>>>
>>>>>
>>>>> This is with the patches for 3.4.? I verified before Sabbath that 3.4
>>>>> builds and passes the tests.? Tried your test first thing this evening
>>>>> after git checkout maint and git pull.? I am at 3.4-43-g84d1c3645
>>>>> which
>>>>> builds but doesn't pass the tests.? So, I could build turning off the
>>>>> test step.
>>>>>
>>>>> However, Friday I was learning more about git bisect to see if I could
>>>>> figure out which patch caused the tests to start failing.? However, a
>>>>> couple of items got in the way:? 1--time;? 2--some commits don't
>>>>> build.
>>>>> That messed me up a bit.? So, I may start over again with the bisect
>>>>> (just for my own edification) and see what happens.? Maybe this time
>>>>> I'll do a git describe each time and take notes so I'll be a little
>>>>> more
>>>>> cognizant of what I'm learning.? <<did that make sense>>
>>>>>
>>>>>
>>>>> --Steve (in the dark)
>>>>>
>>>>>> On Fri., 25 Jan. 2019, 11:52 Stephen M. Butler <kg7je at arrl.net
>>>>>> <mailto:kg7je at arrl.net> wrote:
>>>>>>
>>>>>> ??? On 1/24/19 7:36 PM, Christopher Lam wrote:
>>>>>>> Revert is a git terminology, not a gnucash one. Welcome to version
>>>>>>> control.
>>>>>> ??? That's the manual to which I referred.? It meant something
>>>>>> else to my
>>>>>> ??? mind when I first saw your post.? But, after further thought, my
>>>>>> ??? previous thought was faulty.
>>>>>>
>>>>>>
>>>>>> ??? My first boss after college would draw a picture to describe the
>>>>>> ??? difference between a bug and a feature.
>>>>>>
>>>>>> ??? I can't draw so a word will have to do (at less than a thousand
>>>>>> ??? words)!
>>>>>>
>>>>>> ??? BUG:? draw stick figure.
>>>>>>
>>>>>>
>>>>>> ??? FEATURE:? Add pants, tie, gloves, shoes and a top hat.
>>>>>>
>>>>>>
>>>>>> ??? MORAL:? A feature is a bug all dressed up and ready to go out.
>>>>>>
>>>>>>> Please remember this revert is reverting a buggy code with a
>>>>>> ??? previous
>>>>>>> buggy code, so, cannot be consisted safe to package; best wait until
>>>>>>> the clever devs can find a proper fix for gnc-date.
>>>>>>>
>>>>>>> On Fri., 25 Jan. 2019, 05:46 Stephen M. Butler <kg7je at arrl.net
>>>>>> ??? <mailto:kg7je at arrl.net>
>>>>>>> <mailto:kg7je at arrl.net <mailto:kg7je at arrl.net>> wrote:
>>>>>>>
>>>>>>> ????? OH!? Light bulb on!
>>>>>>> ????? OK.? I understand what you said earlier.? I'll put the patches
>>>>>>> ????? back into
>>>>>>> ????? the packaging.
>>>>>>>
>>>>>>> ????? Thanks for clearing that up.
>>>>>>>
>>>>>>> ????? --Steve
>>>>>>>
>>>>>>> ????? PS Looking in manual for 'revert' command.
------------------------------
Message: 3
Date: Sun, 27 Jan 2019 14:20:47 +0100
From: Carsten Rinke <carsten.rinke at gmx.de>
To: gnucash-devel <gnucash-devel at gnucash.org>
Cc: "Stephen M. Butler" <kg7je at arrl.net>, gnucash-devel
<gnucash-devel-bounces+c.holtermann=gmx.de at gnucash.org>
Subject: [GNC-dev] GnuCash Maint - general problem to enter year for
30.12. + 31.12. ?
Message-ID: <34b41e79-c091-3eaa-93fb-4ff23392fa96 at gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Hi,
today after building from the maint branch I noticed following behaviour:
Enter a new transaction with a date 31.12.2018 and press enter:
31.12.2019 is displayed.
Try to edit and set it back to 2018 by "ctrl -" and press enter:
31.12.2019 is displayed.
Try to set it to 30.12.2019 by using "-": 30.12.2020 is displayed.
Once that you change to 29.12. the year can be set normally again.
I went back and built again from the 3.4 release snapshot:
Here the issue is not reproducable.
Does anyone else see this, too?
Kind regards,
Carsten
------------------------------
Message: 4
Date: Sun, 27 Jan 2019 07:17:06 -0800
From: John Ralls <jralls at ceridwen.us>
To: Christopher Lam <christopher.lck at gmail.com>
Cc: "Stephen M. Butler" <kg7je at arrl.net>, gnucash-devel
<gnucash-devel at gnucash.org>
Subject: Re: [GNC-dev] Test failure
Message-ID: <9A0605F7-BF25-4D7A-BE38-C32C7C62E196 at ceridwen.us>
Content-Type: text/plain; charset=us-ascii
You can do it that way or you can do
git clone https://github.com/christopherlam/gnucash.git -b maint-chartjs-budget-barchart/
or
git clone https://github.com/christopherlam/gnucash.git
git checkout -b maint-chartjs-budget-barchart/
or the way we do for testing pull requests; this is a bit fiddly because of the possible merge commit and conflicts, but it doesn't permanently add a remote:
git checkout -b maint-chartjs-budget-barchart maint
git pull https://github.com/christopherlam/gnucash.git maint-chartjs-budget-barchart/
You can get a fast-forward if you go to https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart, click the "20,557 Commits", and scroll down to find the first commit by someone else, in this case it's f9f714c. Use that instead of maint as the last argument to git checkout.
You can't clone a GitHub tree URL, that's not a repository.
Regards,
John Ralls
> On Jan 26, 2019, at 11:20 PM, Christopher Lam <christopher.lck at gmail.com> wrote:
>
> Ok my bad
>
> May be safer to reuse your own gnucash repository
>
> * cd gnucash
> * git remote add chris https://github.com/christopherlam/gnucash.git
> * git fetch --all
> * git checkout chris/maint-chartjs-budget-barchart
> * dpkg etc
>
> and to revert to main branch:
>
> * git checkout maint
>
>
>
> On 27/1/19 3:04 pm, Stephen M. Butler wrote:
>> On 1/26/19 10:54 PM, Christopher Lam wrote:
>>> Stephen please spend some CPU burning time on my chartJS branch which
>>> needs beta testing?
>>>
>>> $git clone
>>> https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart
>>
>> Thought I'd start this while headed toward some z's. Too tired to
>> figure out what happened.
>>
>> git clone
>> https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart
>> Cloning into 'maint-chartjs-budget-barchart'...
>> fatal: repository
>> 'https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart/'
>> not found
>>
>>
>> --Steve
>>
>>>
>>> On 27/1/19 2:52 pm, Stephen M. Butler wrote:
>>>> On 1/26/19 10:29 PM, John Ralls wrote:
>>>>> Stephen,
>>>>>
>>>>> By all means learn about git bisect, it's an extremely useful
>>>>> troubleshooting tool. But don't exercise yourself too much about
>>>>> this particular failure, Chris and I know exactly what commit caused
>>>>> it and that the underlying cause is a bug in ICU (International
>>>>> Components for Unicode, http://site.icu-project.org/) versions 57-62.
>>>> I figured the devs were way ahead of me. And I'm burning the CPU this
>>>> evening finding that I can't compile 3.4-21 thru (I'm guessing) 3.4-38.
>>>> I'm up to 3.4-29 at this point and already know that -37 and -38 don't
>>>> compile on my box. But -39, -40, and -43 do. Don't know about -41 and
>>>> -42 (and probably won't check them).
>>>>
>>>> Busy day tomorrow so I doubt the cpu will even get warmed up! It's
>>>> pushing 11 pm so I'll call it quits on this exercise.
>>>>
>>>> Thanks for the details.
>>>>
>>>> --Steve
>>>>
>>>>> I had thought that the problem was confined to 1969, but tonight got
>>>>> https://bugs.gnucash.org/show_bug.cgi?id=797067 which makes me think
>>>>> that it's every year, so more testing needed.
>>>>>
>>>>> Regards,
>>>>> John Ralls
>>>>>
>>>>>
>>>>>> On Jan 26, 2019, at 5:55 PM, Stephen M. Butler <kg7je at arrl.net> wrote:
>>>>>>
>>>>>> On 1/26/19 3:13 AM, Christopher Lam wrote:
>>>>>>> Another experiment. Try prefix your build with "TZ=UTC " on current
>>>>>>> maint.
>>>>>>>
>>>>>>> Eg if using ninja, it'll be "TZ=UTC ninja check"
>>>>>> TZ=UTC dpkg- -rfakeroot -b -uc
>>>>>>
>>>>>> ....
>>>>>>
>>>>>> End testing: Jan 27 01:47 UTC
>>>>>> + exit 2
>>>>>> debian/rules:65: recipe for target 'override_dh_auto_test' failed
>>>>>> make[1]: *** [override_dh_auto_test] Error 2
>>>>>> make[1]: Leaving directory '/home/steve/Projects/GnuCash/gnucash'
>>>>>> debian/rules:24: recipe for target 'build' failed
>>>>>> make: *** [build] Error 2
>>>>>> dpkg-buildpackage: error: debian/rules build subprocess returned exit
>>>>>> status 2
>>>>>>
>>>>>> Same error -- Test 109 that fails.
>>>>>>
>>>>>>
>>>>>> This is with the patches for 3.4. I verified before Sabbath that 3.4
>>>>>> builds and passes the tests. Tried your test first thing this evening
>>>>>> after git checkout maint and git pull. I am at 3.4-43-g84d1c3645
>>>>>> which
>>>>>> builds but doesn't pass the tests. So, I could build turning off the
>>>>>> test step.
>>>>>>
>>>>>> However, Friday I was learning more about git bisect to see if I could
>>>>>> figure out which patch caused the tests to start failing. However, a
>>>>>> couple of items got in the way: 1--time; 2--some commits don't
>>>>>> build.
>>>>>> That messed me up a bit. So, I may start over again with the bisect
>>>>>> (just for my own edification) and see what happens. Maybe this time
>>>>>> I'll do a git describe each time and take notes so I'll be a little
>>>>>> more
>>>>>> cognizant of what I'm learning. <<did that make sense>>
>>>>>>
>>>>>>
>>>>>> --Steve (in the dark)
>>>>>>
>>>>>>> On Fri., 25 Jan. 2019, 11:52 Stephen M. Butler <kg7je at arrl.net
>>>>>>> <mailto:kg7je at arrl.net> wrote:
>>>>>>>
>>>>>>> On 1/24/19 7:36 PM, Christopher Lam wrote:
>>>>>>>> Revert is a git terminology, not a gnucash one. Welcome to version
>>>>>>>> control.
>>>>>>> That's the manual to which I referred. It meant something
>>>>>>> else to my
>>>>>>> mind when I first saw your post. But, after further thought, my
>>>>>>> previous thought was faulty.
>>>>>>>
>>>>>>>
>>>>>>> My first boss after college would draw a picture to describe the
>>>>>>> difference between a bug and a feature.
>>>>>>>
>>>>>>> I can't draw so a word will have to do (at less than a thousand
>>>>>>> words)!
>>>>>>>
>>>>>>> BUG: draw stick figure.
>>>>>>>
>>>>>>>
>>>>>>> FEATURE: Add pants, tie, gloves, shoes and a top hat.
>>>>>>>
>>>>>>>
>>>>>>> MORAL: A feature is a bug all dressed up and ready to go out.
>>>>>>>
>>>>>>>> Please remember this revert is reverting a buggy code with a
>>>>>>> previous
>>>>>>>> buggy code, so, cannot be consisted safe to package; best wait until
>>>>>>>> the clever devs can find a proper fix for gnc-date.
>>>>>>>>
>>>>>>>> On Fri., 25 Jan. 2019, 05:46 Stephen M. Butler <kg7je at arrl.net
>>>>>>> <mailto:kg7je at arrl.net>
>>>>>>>> <mailto:kg7je at arrl.net <mailto:kg7je at arrl.net>> wrote:
>>>>>>>>
>>>>>>>> OH! Light bulb on!
>>>>>>>> OK. I understand what you said earlier. I'll put the patches
>>>>>>>> back into
>>>>>>>> the packaging.
>>>>>>>>
>>>>>>>> Thanks for clearing that up.
>>>>>>>>
>>>>>>>> --Steve
>>>>>>>>
>>>>>>>> PS Looking in manual for 'revert' command.
> _______________________________________________
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
------------------------------
Message: 5
Date: Sun, 27 Jan 2019 07:19:38 -0800
From: John Ralls <jralls at ceridwen.us>
To: Carsten Rinke <carsten.rinke at gmx.de>
Cc: gnucash-devel <gnucash-devel at gnucash.org>, "Stephen M. Butler"
<kg7je at arrl.net>, gnucash-devel
<gnucash-devel-bounces+c.holtermann=gmx.de at gnucash.org>
Subject: Re: [GNC-dev] GnuCash Maint - general problem to enter year
for 30.12. + 31.12. ?
Message-ID: <315C9502-2535-4A0E-BE71-117C7BD82AF0 at ceridwen.us>
Content-Type: text/plain; charset=us-ascii
> On Jan 27, 2019, at 5:20 AM, Carsten Rinke <carsten.rinke at gmx.de> wrote:
>
> Hi,
>
> today after building from the maint branch I noticed following behaviour:
>
> Enter a new transaction with a date 31.12.2018 and press enter: 31.12.2019 is displayed.
>
> Try to edit and set it back to 2018 by "ctrl -" and press enter: 31.12.2019 is displayed.
>
> Try to set it to 30.12.2019 by using "-": 30.12.2020 is displayed.
>
> Once that you change to 29.12. the year can be set normally again.
>
>
> I went back and built again from the 3.4 release snapshot:
>
> Here the issue is not reproducable.
>
>
> Does anyone else see this, too?
Carsten,
Yes, Mike Alexander noticed it and filed https://bugs.gnucash.org/show_bug.cgi?id=797067 yesterday. I think there's a good chance it's the same ICU bug as the one in the "Test Failure" thread but I haven't yet had a chance to test it.
Regards,
John Ralls
------------------------------
Message: 6
Date: Sun, 27 Jan 2019 08:07:58 -0800
From: "Stephen M. Butler" <kg7je at arrl.net>
To: Christopher Lam <christopher.lck at gmail.com>, "Stephen M. Butler"
<kg7je at arrl.net>
Cc: gnucash-devel <gnucash-devel at gnucash.org>
Subject: Re: [GNC-dev] Test failure
Message-ID: <0d532edd-a283-36c3-2703-b877b63d7113 at gmail.com>
Content-Type: text/plain; charset=utf-8
On 1/26/19 11:20 PM, Christopher Lam wrote:
>
> Ok my bad
>
> May be safer to reuse your own gnucash repository
>
> * cd gnucash
> * git remote add chris https://github.com/christopherlam/gnucash.git
> * git fetch --all
> * git checkout chris/maint-chartjs-budget-barchart
> * dpkg etc
>
> and to revert to main branch:
>
> * git checkout maint
>
>
Just a quick note before running out the door for the day.? It compiled
and passed test 109 (with the 3.4 build patch in place).? I'm presuming
you don't have the broken patch in this branch.
--Steve
PS? Saw the note from John and decided that was a 400 series course.?
Options -- too many options.?
>
> On 27/1/19 3:04 pm, Stephen M. Butler wrote:
>> On 1/26/19 10:54 PM, Christopher Lam wrote:
>>> Stephen please spend some CPU burning time on my chartJS branch which
>>> needs beta testing?
>>>
>>> $git clone
>>> https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart
>> Thought I'd start this while headed toward some z's.? Too tired to
>> figure out what happened.
>>
>> ?git clone
>> https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart
>> Cloning into 'maint-chartjs-budget-barchart'...
>> fatal: repository
>> 'https://github.com/christopherlam/gnucash/tree/maint-chartjs-budget-barchart/'
>> not found
>>
>>
>> --Steve
>>
>>> On 27/1/19 2:52 pm, Stephen M. Butler wrote:
>>>> On 1/26/19 10:29 PM, John Ralls wrote:
>>>>> Stephen,
>>>>>
>>>>> By all means learn about git bisect, it's an extremely useful
>>>>> troubleshooting tool. But don't exercise yourself too much about
>>>>> this particular failure, Chris and I know exactly what commit caused
>>>>> it and that the underlying cause is a bug in ICU (International
>>>>> Components for Unicode, http://site.icu-project.org/) versions 57-62.
>>>> I figured the devs were way ahead of me.? And I'm burning the CPU this
>>>> evening finding that I can't compile 3.4-21 thru (I'm guessing) 3.4-38.
>>>> I'm up to 3.4-29 at this point and already know that -37 and -38 don't
>>>> compile on my box.? But -39, -40, and -43 do.? Don't know about -41 and
>>>> -42 (and probably won't check them).
>>>>
>>>> Busy day tomorrow so I doubt the cpu will even get warmed up!? It's
>>>> pushing 11 pm so I'll call it quits on this exercise.
>>>>
>>>> Thanks for the details.
>>>>
>>>> --Steve
>>>>
>>>>> I had thought that the problem was confined to 1969, but tonight got
>>>>> https://bugs.gnucash.org/show_bug.cgi?id=797067 which makes me think
>>>>> that it's every year, so more testing needed.
>>>>>
>>>>> Regards,
>>>>> John Ralls
--
Stephen M Butler, PMP, PSM
Stephen.M.Butler51 at gmail.com
kg7je at arrl.net
253-350-0166
-------------------------------------------
GnuPG Fingerprint: 8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8
------------------------------
Subject: Digest Footer
_______________________________________________
gnucash-devel mailing list
gnucash-devel at gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
------------------------------
End of gnucash-devel Digest, Vol 190, Issue 35
**********************************************
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
More information about the gnucash-devel
mailing list