> >>>
> > Would you prefer we start with oldest or newest unconfirmed bugs. Maybe
> > each of us should start from different end.
>
> I don't have a preference. Just being able to close out bugs that
> are no longer a factor, or bugs that cannot be reproduced... and pushing
> back bugs that don't
For a few months now the GC archives are searchable and I am using this
functionality a lot. This is a great addition to the site.
I do have a suggestion how to make it maybe a little bit better.
Would it be possible to add the link "Next Page" also to the bottom of the
page? This way a user woul
During my first attempt I was able to get a bit further into the process
but now I am getting stuck during the installation of MinGW.
I've used several different mirrors but I get the same error message no
matter which one I use.
I guess nobody else has ran into this?
$ ./install.sh
###
I also keep having problems building gnucash recently.
I've been able to build gnucash from SVN many times before but since
last week or so I am running into problems. I know that some of these
problems are related to the version of g-wrap but since yesterday
I am seeing the following error mess
> Does anyone of the active developers have a amd64 machine at hand? (I
> don't.) I would certainly believe that some tests will fail on amd64
as
> long as this is none of our actively developed target platforms...
I'm not an active developer but I do have an AMD64 running FC4 sitting
at
home.
> I've now been able to compile GnuCash on my 64-bit system
Just noticed that even though I can compile GC (without the
--enable-hbci
option) I can not run it:
[EMAIL PROTECTED] ~]$ /opt/gnucash/bin/gnucash
ERROR: In procedure dynamic-link:
ERROR: file: "libgw-wct", message: "/usr/lib/libgw
> I took Karl up on this offer, and David Hampton and I were able to
> squish the happily-small number of 64-bit compilation issues. If you
> see others, please speak up.
I've now been able to compile GnuCash on my 64-bit system but only
when I drop the --enable-hbci option. With it the compila
> Okay, this should now be fixed.. Can you "svn update"
> your goffice-update branch and re-try?
I did that. Now I am getting the same error that I reported originally
with the trunk:
cc1: warnings being treated as errors
gog-graph.c: In function 'gog_graph_ref_data':
gog-graph.c:414: warning
> > Would you like me to report these as well or should I ignore them at
the
> > moment?
>
> I don't think these are related to Gnucash. Maybe a bug in ALSA or a
> permissions problem, but that's just a guess.
>
> -chris
>
Oh, there are plenty of other messages that are definitely related to
> Uhh... What makes you think that these two bugs are the same? IMHO
> these two are _not_ the same bug. 88517 is about cut-and-paste losing
> transaction information, whereas 92484 is about bulk moves of
> transactions. They are certainly different in my mind. Why do you
> consider them the sa
Title: Re: Bug Triage
Derek,
I was wondering how we should be handling duplicate bugs that we identify. I've found Bug 88517 and 92484 being identical (assigned to two different developers). Should we contact the developers to have them review and mark these as duplicates themselves or w
11 matches
Mail list logo
