[GNC] GnuCash 5.13-2

[Stephen M. Butler]

For unknown reasons that one set of book forgot the CSV Import settings 
file -- didn't show it in the drop down list.  The other books that had 
similar settings worked just fine,

Once I got the settings setup correctly for that missing one, then the 
import worked just fine.

I'm going to chalk this one up to operator panic.

--Steve


On 9/29/25 17:17, John Ralls wrote:
> The simplest is `git clone 
> https://github.com/gnucash/gnucash /new/gnucash/directory from 
> somewhere that isn’t already a git working directory. You’ll also need 
> a new build directory and CMAKE_INSTALL_DIRECTORY. You can use the 
> same CMAKE_PREFIX_PATH pointing at where all of the dependencies are.
>
> To change a working directory to whatever 5.12-62 was you need the 
> sha256 for the 62nd commit after 5.12. To find that enumerate all of 
> the commits since 5.12 and filter the result to get to the 64th entry 
> from the bottom:
>     git log --oneline 5.12..5.13 | tail -n 64 | head -n 1
> Which returns 948e07ac04 Merge latest translations from Weblate. Check 
> that it’s the one you want with
>     git describe 948e07ac04
> It returns 5.12-62-g948e07ac04. Note that you might need to iterate a 
> bit on that part, I tried tail -n 63, tail -n 62, and tail -n 64 to 
> get the one you want.
>
> Now that you have the sha256 you can tell git either
>    git checkout 948e07ac04
> or
>    git reset —hard 948e07ac04
>
> The first takes you off the branch and the second moves the head of 
> the current branch to that commit. If you want to record that position 
> so that you can get back to it easily you can
>   git tag 5.12.62
> After which you can use 5.12.62 instead of the sha256 in any command. 
> You can use anything you want for the tag, 5.12.62 is just an example. 
> You can tag a commit from either a checkout or a git reset.
>
> Regards,
> John Ralls
>
>
>
>> On Sep 29, 2025, at 15:42, Stephen M. Butler <kg7je at arrl.net> wrote:
>>
>> On 9/29/25 14:53, Mark at Lorimark wrote:
>>> Can you just clone the repo to a fresh folder?
>>
>> What does that do for me and how do I do that?
>>>
>>> ~mark petryk
>>> ~w:http://gnucashew.lorimarksolutions.com
>>> ~q:i don't know where it's going to go,
>>> ...and i don't know what to wear when it gets there.
>>>
>>> On 9/29/25 16:28, Stephen M. Butler wrote:
>>>> Something weird on the CSV Transaction import in 5.13-2.  I'll try 
>>>> to figure it out later.
>>>>
>>>> I need to revert back to 5.12-62 (my last compile that worked 
>>>> correctly) in order to get some time sensitive work done.
>>>>
>>>> How can I get git reset to that point?  I've just done a git pull 
>>>> that ended me up at 5.13-2.
>>>>
>>>> Note:  I did have a directory with that build but when I went there 
>>>> to issue the sudo make install it started doing the compiles all 
>>>> over again rather than just installing what had already been 
>>>> compiled in that folder.  So, now I need to force git back to the 
>>>> previous commit point to do a clean compile of 5.12-62 <<sigh>>
>>>>
>>> _______________________________________________
>>> gnucash-user mailing list
>>> gnucash-user at gnucash.org
>>> To update your subscription preferences or to unsubscribe:
>>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>>> -----
>>> 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 at gnucash.org
>> To update your subscription preferences or to unsubscribe:
>> https://lists.gnucash.org/mailman/listinfo/gnucash-user
>> -----
>> Please remember to CC this list on all your replies.
>> You can do this by using Reply-To-List or Reply-All.
>