using a new gnucash db created with r19971 in postgres a few odd things
happen.
1. On reopening the db the following notices appear in the output in the
command prompt window. Are these tables being receated every time?
NOTICE: CREATE TABLE will create implicit sequence "recurrences_id_seq1"
fo
My vote is that 2.4.0 goes ahead this week as planned. This needs to be fixed
for 2.4.1.
Phil
-
I used to be a hypochondriac AND a kleptomaniac. So I took something for it.
From: Keith Bellairs
To: gnucash-devel
Sent: Tue, December 21, 2010 10:23:2
Absolutely. The bug needs to be fixed, but the release should go ahead
anyway. Thanks!
Christian
Zitat von Phil Longstaff :
My vote is that 2.4.0 goes ahead this week as planned. This needs
to be fixed
for 2.4.1.
Phil
-
I used to be a hypochondriac AND a kleptomaniac. So I too
On Dec 21, 2010, at 7:23 AM, Keith Bellairs wrote:
> using a new gnucash db created with r19971 in postgres a few odd things
> happen.
>
> 1. On reopening the db the following notices appear in the output in the
> command prompt window. Are these tables being receated every time?
>
> NOTICE:
On Dec 21, 2010, at 9:59 AM, Keith Bellairs wrote:
> Since these are not replicated, I'll start with a make clean before I do
> anything else.
>
> On Tue, Dec 21, 2010 at 11:58 AM, John Ralls wrote:
>
> On Dec 21, 2010, at 7:23 AM, Keith Bellairs wrote:
>
> > using a new gnucash db created w
After a clean build (make clean; make), I cannot replicate the issues with a
fresh database. The problems persist for a pg database created in 2.3.17 a
few builds ago. Given that 2.4 comes out clean, I think these are not a
bug.
On Tue, Dec 21, 2010 at 1:14 PM, John Ralls wrote:
>
> On Dec 21,
Ok, I have tested this on Windows and the images stay within the 510px
constraint there as well. They look ugly though. It appears the scaling
capability of the Windows help browser is very limited.
It may be a good idea to scale the images beforehand with a more capable tool
(like imagemagick)
John,
will 2.4.0 have critical problems if I go ahead with 2.4.0 without this change?
FYI, John had mentioned reverting this in an off-list e-mail to me. I told him
to go ahead if it solved a critical problem. This e-mail just brings the issue
back to the list.
Phil
-
I used to be a
On Dec 21, 2010, at 12:26 PM, Phil Longstaff wrote:
> John,
>
> will 2.4.0 have critical problems if I go ahead with 2.4.0 without this
> change?
>
> FYI, John had mentioned reverting this in an off-list e-mail to me. I told
> him
> to go ahead if it solved a critical problem. This e-mail
On Dec 21, 2010, at 11:28 AM, Keith Bellairs wrote:
> After a clean build (make clean; make), I cannot replicate the issues with a
> fresh database. The problems persist for a pg database created in 2.3.17 a
> few builds ago. Given that 2.4 comes out clean, I think these are not a bug.
>
Rig
I'll tag r19974 as 2.4.0-OSX.
Phil
-
I used to be a hypochondriac AND a kleptomaniac. So I took something for it.
From: John Ralls
To: Phil Longstaff
Cc: gnucash-devel@gnucash.org
Sent: Tue, December 21, 2010 5:06:17 PM
Subject: Re: r19974 - gnucash/
Note that this will cause a Win32 build ;)
-derek
On Tue, December 21, 2010 7:08 pm, Phil Longstaff wrote:
> I'll tag r19974 as 2.4.0-OSX.
>
> Phil
> -
> I used to be a hypochondriac AND a kleptomaniac. So I took something for
> it.
>
>
>
>
>
> From: John
12 matches
Mail list logo
