He he, just to make things a bit more complicated and realistic:
> Sent: Sunday, May 13, 2018 at 6:42 PM
> From: "John Ralls"
> To: "Adrien Monteleone"
> Cc: gnucash-devel@gnucash.org
> Subject: Re: [GNC-dev] pricedb policy
>
> Just get local currency at a bank
If you're on a weekend trip this
Hi All,
I hit another snag in working on the BZ migration -- we need to
"predefine" any keywords we wish to use. I can try to determine which
ones we DO use (so far I've seen "documentation"), but I figured I would
put this out there first to decide how we want to handle them.
First, keywords n
Here you go, a prices-report.scm which can be dropped into standard-reports
folder and adds a rudimentary forex analysis. If rebuilding you'll need to
add onto CMakeLists.txt as well.
It scans *only* transactions which involve 2 different commodities. eg
GBP<->EUR or AAPL<->USD.
It calculates and
> On May 14, 2018, at 6:47 AM, Derek Atkins wrote:
>
> Hi All,
>
> I hit another snag in working on the BZ migration -- we need to
> "predefine" any keywords we wish to use. I can try to determine which
> ones we DO use (so far I've seen "documentation"), but I figured I would
> put this out
Hi,
On Mon, May 14, 2018 11:41 am, John Ralls wrote:
>
>
> The existing keywords don’t seem terribly useful to me and they’re in any
> case not used consistently enough: only 364 out of 8590 GnuCash bugs have
> a keyword on them. I don’t think that there’s any need to import them
> unless BZ requi
Am 14.05.2018 um 18:10 schrieb Derek Atkins:
> Hi,
>
> On Mon, May 14, 2018 11:41 am, John Ralls wrote:
>>
>>
>> The existing keywords don’t seem terribly useful to me and they’re in any
>> case not used consistently enough: only 364 out of 8590 GnuCash bugs have
>> a keyword on them. I don’t thin
On Mon, May 14, 2018 1:11 pm, Frank H. Ellenberger wrote:
>> The problem I'm seeing when I leave the
>> dup_iud field is that I get an error from the migration script:
>>
>> Starting to create Bug 84690
>> Can't use string ("Bugzilla::Bug") as a HASH ref while "strict refs" in
>> use at Bugzil
On Mon, May 14, 2018 1:22 pm, Derek Atkins wrote:
>
>>> Starting to create Bug 84690
>>> Can't use string ("Bugzilla::Bug") as a HASH ref while "strict refs" in
>>> use at Bugzilla/Bug.pm line 3322.
>>>
>>> I will continue to explore this issue.
>>
>> The default policy was: close the younger repo
> On May 14, 2018, at 10:11 AM, Frank H. Ellenberger
> wrote:
>
> Am 14.05.2018 um 18:10 schrieb Derek Atkins:
>> Hi,
>>
>> On Mon, May 14, 2018 11:41 am, John Ralls wrote:
>>>
>>>
>>> The existing keywords don’t seem terribly useful to me and they’re in any
>>> case not used consistently e
On Mon, May 14, 2018 2:16 pm, John Ralls wrote:
>
[snip]
> A spot check shows they seem mostly to be added at bug creation time by
> bug reporters, few of whom are likely to be able to make an informed
> choice. But as you say it's more important to get BZ up and running, and
> we may yet decide
Hi Everyone,
tl;dr: I have a partial migration up and running (~105 / 8588 bugs) and I
think my migration script is "complete" -- please test. Also, please let
me know if you know of any bugs that use the see_also field.
Long Version:
As you all know, we use Gnome's bugzilla instance, and they
> On May 14, 2018, at 2:00 PM, Derek Atkins wrote:
>
> Hi Everyone,
>
> tl;dr: I have a partial migration up and running (~105 / 8588 bugs) and I
> think my migration script is "complete" -- please test. Also, please let
> me know if you know of any bugs that use the see_also field.
>
> Long
I suppose you’re still revising things.
Currently, I see components listed, but no bugs found.
I also tried a password reset but never received the email.
Is this only for official developers to test right now, or anyone who has a
Gnome Bugzilla account and participated in bug reports?
Regards
13 matches
Mail list logo
