On Wednesday 01 February 2006 16:33, Christian Stimming wrote:
> FTR: We didn't recomment to wildly revert something. When someone says
> "you probably have a svn conflict", you need to find out which file has
> these conflicts. Instead of using some unspecified "svn revert", you are
> instead supp
Eildert Groeneveld schrieb:
This is clearly an SVN merge issue. Are you sure you reverted the
correct file?
then I am sure I did it wrong: in the gnucash-svn directory I issued:
svn revert .
After that - just to make sure - ran
FTR: We didn't recomment to wildly revert something. When s
On Wednesday 01 February 2006 16:13, Derek Atkins wrote:
> This is clearly an SVN merge issue. Are you sure you reverted the
> correct file? It's unclear to me that "svn revert" by itself
> is recursive, so what exact command did you run? Did you then run
> a "make install" after you reverted?
Quoting Eildert Groeneveld <[EMAIL PROTECTED]>:
On Wednesday 01 February 2006 11:34, Eildert Groeneveld wrote:
Backtrace:
In unknown file:
?: 0* [primitive-load-path "report.scm"]
?: 1* <<<
: In expression <<<:
: Unbound variable: <<<
Anybody there who can shed light onto t
On Wednesday 01 February 2006 11:34, Eildert Groeneveld wrote:
>
> Backtrace:
> In unknown file:
>?: 0* [primitive-load-path "report.scm"]
>?: 1* <<<
>
> : In expression <<<:
> : Unbound variable: <<<
>
> Anybody there who can shed light onto this issue?
>
> my revision: 13064
Hi,
Eildert Groeneveld schrieb:
Backtrace:
In unknown file:
?: 0* [primitive-load-path "report.scm"]
?: 1* <<<
: In expression <<<:
: Unbound variable: <<<
you almost surely have an SVN conflict here. "svn revert" will do the trick.
Christian
___
Hello Folks
some time ago there was discussion on the slib problems in Debian unstable.
It was the conclusion, that downgrading to slib_3a1-4.2_all.deb
would do the trick. This did in deed work. Only after another upgrade gnucash
also worked (at least for me) with the slib_3a2-5_all.deb
Oddly en
Eildert Groeneveld <[EMAIL PROTECTED]> writes:
> On Monday 16 January 2006 19:54, Thomas Bushnell BSG wrote:
>> Eildert Groeneveld <[EMAIL PROTECTED]> writes:
>> > As already indicated by Thomas: the current slib problems (abort on
>> > startup) went away once down graded:
>> >
>> > dpkg -i slib_3
On Monday 16 January 2006 19:54, Thomas Bushnell BSG wrote:
> Eildert Groeneveld <[EMAIL PROTECTED]> writes:
> > As already indicated by Thomas: the current slib problems (abort on
> > startup) went away once down graded:
> >
> > dpkg -i slib_3a1-4.2_all.deb
>
> Which guile-1.6-libs package are you
Eildert Groeneveld <[EMAIL PROTECTED]> writes:
> As already indicated by Thomas: the current slib problems (abort on startup)
> went away once down graded:
>
> dpkg -i slib_3a1-4.2_all.deb
Which guile-1.6-libs package are you using together with this?
_
As already indicated by Thomas: the current slib problems (abort on startup)
went away once down graded:
dpkg -i slib_3a1-4.2_all.deb
So that problem is circumvented.
However, I get an error on reading the 1.8 version data files. This is big
(around 8MB), its read in for some time and then (loo
11 matches
Mail list logo
