> On Sep 27, 2019, at 2:17 PM, Colin Law wrote:
>
> On Fri, 27 Sep 2019 at 19:15, Tommy Trussell wrote:
>>
>> I see (some? all?) of them (plus a few OTHER things we've discussed here
>> even in the past few days) in the git log for GnuCash after the 3.7 tag.
>> :-/ Such is the nature of mov
On Fri, 27 Sep 2019 at 19:15, Tommy Trussell wrote:
>
> I see (some? all?) of them (plus a few OTHER things we've discussed here
> even in the past few days) in the git log for GnuCash after the 3.7 tag.
> :-/ Such is the nature of moving targets!
Do you mean that the version which calls it is 3
On Fri, Sep 27, 2019 at 12:57 PM John Ralls wrote:
> > On Sep 27, 2019, at 9:59 AM, Tommy Trussell
> wrote:
> >
> > I just noticed Gianfranco Costamagna patched
> and
> > uploaded GnuCash 3.7 for Ubuntu 19.10 "Eoan Ermine":
> >
> > https://launchpad.net/ubuntu/+source/gnucash
> >
> > I was just
Your first post in this thread ended with a cmake command line with a bunch of
extra options. I guess try using the whole lot of them and see if that works
and what errors you get.
Regards,
John Ralls
> On Sep 27, 2019, at 10:43 AM, Stephen M. Butler wrote:
>
> On 9/26/19 5:53 PM, Stephen M.
> On Sep 27, 2019, at 9:59 AM, Tommy Trussell wrote:
>
> I just noticed Gianfranco Costamagna patched and
> uploaded GnuCash 3.7 for Ubuntu 19.10 "Eoan Ermine":
>
> https://launchpad.net/ubuntu/+source/gnucash
>
> I was just looking at the packaging diff hoping I would find it
> instructive
On 9/26/19 5:53 PM, Stephen M. Butler wrote:
> make went faster than expected. Ended with these beautiful lines:
>
> [100%] Built target gnucash_core_c
> Scanning dependencies of target swig-gnucash-core
> [100%] Built target swig-gnucash-core
> Scanning dependencies of target gnucash-core-c-py
>
I just noticed Gianfranco Costamagna patched and
uploaded GnuCash 3.7 for Ubuntu 19.10 "Eoan Ermine":
https://launchpad.net/ubuntu/+source/gnucash
I was just looking at the packaging diff hoping I would find it
instructive. It looks like Gianfranco added a lot of patches to get it to
build.
htt
Hi,
Am 27.09.19 um 13:33 schrieb Geert Janssens:
> Here's what I use as personal guidelines:
>
> * If I was able to reproduce the bug before applying the fix and I no longer
> can after the fix, I mark the issue as resolved. I typically add a message
> that the reporter can reopen the bug if the i
Here's what I use as personal guidelines:
* If I was able to reproduce the bug before applying the fix and I no longer
can after the fix, I mark the issue as resolved. I typically add a message
that the reporter can reopen the bug if the issue still persists, asking for
more details in that cas
Hi,
What is the correct way to mark bugs fixed.
Should I be marking them as RESOLVED/FIXED if I think I have fixed the
reported bug with appropriate text asking for the reporter to test and
reopen if not fixed.
or
leave it as NEEDINFO with some text asking for the reporter to test and
update the b
10 matches
Mail list logo
