This is the sort of thing that Debian experimental is good for, you
know...
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
On Wed, 2005-10-05 at 22:05 +0200, Christian Stimming wrote:
> developer team on the best roadmap to a gnome2 release. Something like: "The
[deletia]
> manager around." As a relatively easy technical step to underline our
> commitment to a gnome2 release, I would suggest to merge back the
> gnu
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
make: *** No rule to make target `codeset.m4', needed by `distdir'. Stop.
Yea, looks like lots of this stuff got added in.
Note: I do have gettextize installed, but I don't think it's being
used, if I follow autogen.sh correctly. Is that the pro
On Thu, Oct 06, 2005 at 04:43:58PM -0400, Chris Shoemaker wrote:
> On Thu, Oct 06, 2005 at 04:26:33PM -0400, Derek Atkins wrote:
> > Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
> >
> > >I found:
> > >2003-06-14 gettextize <[EMAIL PROTECTED]>
> > >
> > > * Makefile.am (EXTRA_DIST): Add con
On Thu, Oct 06, 2005 at 04:26:33PM -0400, Derek Atkins wrote:
> Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
>
> >I found:
> >2003-06-14 gettextize <[EMAIL PROTECTED]>
> >
> > * Makefile.am (EXTRA_DIST): Add config.rpath.
> >
> >in ChangeLog. What kind of name is gettextize!? Anyway, is
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
I found:
2003-06-14 gettextize <[EMAIL PROTECTED]>
* Makefile.am (EXTRA_DIST): Add config.rpath.
in ChangeLog. What kind of name is gettextize!? Anyway, is
config.rpath really supposed to be in EXTRA_DIST?
Looks like someone committed t
On Thu, Oct 06, 2005 at 04:12:06PM -0400, Chris Shoemaker wrote:
> On Thu, Oct 06, 2005 at 02:13:23PM -0400, Derek Atkins wrote:
> > Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
> >
> > >Does anyone know of a way to run 'make distcheck' without actually
> > >running the tests?
> >
> > "make dist"
On Thu, Oct 06, 2005 at 02:13:23PM -0400, Derek Atkins wrote:
> Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
>
> >Does anyone know of a way to run 'make distcheck' without actually
> >running the tests?
>
> "make dist" instead of "distcheck"
Thanks. But, I get:
$ make dist
make: *** No rule to
[...]
>
> I've been meaning to set up a website for my current progress, but
> it's never been the most urgent thing. If you think you might be
> interested in helping, it would be more urgent.
Well... I'll have a rush in the next weeks in my job, so I'm not sure
how much time I will be able (or
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
Does anyone know of a way to run 'make distcheck' without actually
running the tests?
"make dist" instead of "distcheck"
Alternatively, does anyone know the last time the tests ran
successfully?
No, but we really need to get them working...
-c
On Thu, Oct 06, 2005 at 01:44:29PM -0400, Chris Shoemaker wrote:
> [ 'make check' actually runs the tests... ]
>
> -chris
>
>
> creating test-xml2-is-file
> make check-TESTS
> make[6]: Entering directory
> `/home/chris/gnucash/release-sandbox/gnucash/src/backend/file/test'
> Executed 20 tests.
I'll be honest that I don't have time to do direct side-by-side
comparisons or use a canonical set of test data (I've got too much real
book-keeping to do...). But I'm more than happy to check out a new
version every couple of weeks, and use it and report back. Obviously,
there are parts of the
[ 'make check' actually runs the tests... ]
-chris
creating test-xml2-is-file
make check-TESTS
make[6]: Entering directory
`/home/chris/gnucash/release-sandbox/gnucash/src/backend/file/test'
Executed 20 tests. All tests passed.
PASS: test-date-converting
FAILURE dom_tree_to_commodity_ref_no_en
On Wed, 2005-10-05 at 17:21 -0700, Andrew Sackville-West wrote:
> Been lurking lately and wonder what is involved in testing and how can I
> help? I'm a daily user running three businesses with gnucash and have
> some very ancient programming experience. If I can help out by testing
> and (hopef
Quoting Christian Stimming <[EMAIL PROTECTED]>:
Hi,
Derek Atkins schrieb:
Can we outline the process?
* clean cvs co
* change GNUCASH_MICRO_VERSION in configure.in
You also need to change the AC_INIT setting in configure.in
Really? I would say the modification belongs in AM_INIT_AUTOMAKE
Hi,
Derek Atkins schrieb:
Can we outline the process?
* clean cvs co
* change GNUCASH_MICRO_VERSION in configure.in
You also need to change the AC_INIT setting in configure.in
Really? I would say the modification belongs in AM_INIT_AUTOMAKE and
thankfully this already uses GNUCASH_MICRO_V
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
Well, want to spend a little time to write the script that does all this?
Honestly, not really. I'm not familiar with the release process.
But, if no one else will, then I guess I can take a whack.
Hehe...
Can we outline the process?
* clean c
On Thu, Oct 06, 2005 at 10:51:45AM -0400, Derek Atkins wrote:
> Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
>
> >>Granted, we could probably write a script that makes the necessary
> >>modifications, commits the changes, tags the release, and runs
> >>./autogen.sh ; make distcheck
> >
> >Yeah, re
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
???
Isn't there usually a diff here?
Yes...
BTW, these emails are automatically generated by cvs server at commit
time, yes?
Yes.
-chris
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student In
On Thu, Oct 06, 2005 at 10:59:14AM -0400, Joshua Sled wrote:
> Log Message:
> ---
> add issue
>
> Tags:
>
> gnucash-gnome2-dev
>
> Modified Files:
> --
> gnucash:
> GNOME2_STATUS
>
> Revision Data
> -
???
Isn't there usually a diff here?
BTW, t
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
Granted, we could probably write a script that makes the necessary
modifications, commits the changes, tags the release, and runs
./autogen.sh ; make distcheck
Yeah, release number increments are easy to automate. And I think the
typical alpha test
On Thu, Oct 06, 2005 at 10:36:14AM -0400, Derek Atkins wrote:
> Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
>
> >I think in the past, we've been focused on what code changes are
> >required for a G2 release. But, at least for alpha releases, can't we
> >just release regularly and see how many re
Quoting Chris Shoemaker <[EMAIL PROTECTED]>:
I think in the past, we've been focused on what code changes are
required for a G2 release. But, at least for alpha releases, can't we
just release regularly and see how many releases it takes to go beta
and then final?
That /is/ what we did for th
On Thu, Oct 06, 2005 at 01:12:28AM +0200, Didier Vidal wrote:
> [...]
> > An interesting side-effect of a 1.8.12 release is that we as a developer
> > team
> > communicate the fact that we're alive and active and caring about the
> > users,
> > all the while such a release is technically quite
On Wed, Oct 05, 2005 at 10:05:29PM +0200, Christian Stimming wrote:
> Hi Developers,
>
> two different issues just popped up about the current gnucash development.
> First, some latest changes in CVS seem to have introduced unexpected
> conflicts, though the changes are considered to be of lower
On Wed, 2005-10-05 at 17:21 -0700, Andrew Sackville-West wrote:
> Been lurking lately and wonder what is involved in testing and how can I
> help? I'm a daily user running three businesses with gnucash and have
> some very ancient programming experience. If I can help out by testing
> and (hopef
Hi Chris,
this is great news! Thanks for coming back on this. I don't think we
have to decide on the gnucash-gnome2 release cycle right now. Right now
it is just sufficient to make that 1.8.12 release, and then continue
coding on the gnome2 code.
Chris Lyttle schrieb:
Well Christian, this i
27 matches
Mail list logo
