Can't run 2.4.10 (was: GnuCash 2.4.10 released)

[John Ralls]

On Feb 10, 2012, at 7:02 AM, Geert Janssens wrote:

> Op donderdag 9 februari 2012 08:43:31 schreef John Ralls:
>> On Feb 9, 2012, at 8:27 AM, Geert Janssens wrote:
>>> Op donderdag 9 februari 2012 17:01:22 schreef Geert Janssens:
>>>> Op woensdag 8 februari 2012 18:02:36 schreef John Ralls:
>>>>> I just looked, and there was a snap re-release (2.24.10) on Monday,
>>>>> and
>>>>> the Win32 binaries are up at ftp.gnome.org. After testing that it
>>>>> builds, I committed a change to the GC 2.4 branch, so you and Geert
>>>>> can
>>>>> try tomorrow's nightly.
>>>> 
>>>> I have just ran a successful test with the latest nightly. It works
>>>> fine on my 16bit remote desktop connection. Yay !
>>>> 
>>>> Geert
>>> 
>>> Just wondering:
>>> - this one fix probably doesn't warrant a new release, does it ?
>>> - with this fix, it looks like the 2.4 Windows build is fully working
>>> with the newer gtk. Have all the required fixes been forward-ported to
>>> trunk already ?
>> No, I don't think so.  What would the buildbot do if I change defaults.sh on
>> the 2.4.10 tag? Or make a new 2.4.10-1 tag and change defaults.sh there?
> From what I read in the build_tags.sh script (which you can find in 
> packaging/win32), both may result in a new tag build for 2.4.10, though I'm 
> not really sure.
> 
> If changing defaults.sh in the 2.4.10 directory would increment the revision 
> number on the directory itself, that would trigger a new build.
> 
> Tagging with 2.4.10-1 creates a new tag, which should also trigger a build. I 
> think this approach would be cleaner than to modify an officially released 
> tag.
> 

OK, I just tagged r21977 as 2.4.10-1, and I'll replace the download on SF and uptdate the website pointers tomorrow morning after it builds.

I think that leaves just one M$Win/Gtk-2.24 crash outstanding, 668891.

Regards,
John Ralls