Re: [GNC-dev] Bugzilla Migration Status Update (2018-05-24)

[Geert Janssens]

Op vrijdag 1 juni 2018 01:38:43 CEST schreef John Ralls:
> > On May 24, 2018, at 9:40 AM, Derek Atkins  wrote:
> > 
> > Hi all,
> > 
> > Just another Bugzilla migration update.
> > 
> > tl;dr:  DB was blown away again; Multiple products have been split and
> > 
> >bugs have been migrated to them.  User/group permissions have
> >been updated. Please take a look and let me know your thoughts.
> > 
> > First, yes, I blew away the DB again.  If you had reset your password
> > before, I'm sorry, you'll need to do it again.  Note that this will
> > happen again at the final migration, too.
> > 
> > Some of the major changes this time around:
> > 
> > - I created three additional products: Website, Documentation, and
> > 
> >  Packaging.
> > 
> > - Each of these products has at least one but often time more-than-one
> > 
> >  component.  These new components inherit the settings of the original.
> > 
> > - I tried to file bugs appropriately into the new components.  This was
> > 
> >  done using heuristics to look for certain key words or phrases in the
> >  bugs of the original component and split them apart into the new
> >  ones.  Please take a look.  If you find issues please let me know and
> >  I can try to adjust my heuristics for the final migration.
> > 
> > - I've added a GnuCash_developers group with appropriate permissions on
> > 
> >  all the groups, and I've taken everyone who was listed as a GnuCash
> >  developer from GnomeBZ and added them to GnuCash_developers with both
> >  Membership and Bless permissions (which means any dev can add new
> >  devs).  I did not check to see if this was the case previously.
> > 
> > - I've removed the TestProduct.
> > 
> > KNOWN ISSUES:
> > 
> > - BUG CREATION DOES NOT WORK.  I know it wont work, so please don't test
> > 
> >  it.  It will just create a broken remnant in the database and you'll
> >  just receive an error in the process.  This is unfortunately due to
> >  required code-changes to make the migration work properly.
> > 
> > - Some of the old pages from GnomeBZ don't exist.  For example, the
> > 
> >  /page.cgi?id=browse.html page does not exist (which is where you get
> >  to from the Browse link in the header). I am pretty sure this was a
> >  GnomeBZ customization.  I can look at installing it -- but if you have
> >  a pointer to it that would help.
> > 
> > - I still am not properly dealing with the attachment status.
> > 
> > WHAT I'D LIKE FROM YOU:
> > 
> > - Please take a look at how I refiled the bugs into the various
> > 
> >  products/components.  If you see issues with them, please let me
> >  know.  Pointing me to a bug# and where it should be would be useful.
> > 
> > - Take a look at configuration issues -- what did GnomeBZ have that we
> > 
> >  don't (or vice versa).  What config changes do I need to make?  What
> >  GnomeBZ extensions do you really want me to find/install?
> 
> Looked through the bugs moved to other products. There are a few misses in
> packaging: 786202 should be in packaging:MacOS; 731864, 737646, 784161,
> 788372, and 793461 should be in packaging:Windows. That's OK, there are
> only a few and it would be too hard to write a perfect binning script. We
> can fix those up after the final migration.
> 
Also 792226 was misclassified as Website, but that's because it was already 
wrong on gnome 
bz. I have fixed that, it should now appear in Documentation.

> The only Product/Component question I have is about Tip of the Day and man
> page bugs. The current script puts them in the Documentation product, but
> the code for them is in gnucash rather than gnucash-docs. Which Product
> should they go in?

Good question. I can find motivations for both options.

I imagine these bugs are typically something for a "Documentation team" handle, 
or someone 
interested in working on Documentation bugs (we're too small to talk in terms 
of teams). So 
such person would more likely find the bug if it was under the documentation 
product.

Given the sources for both live in the gnucash repo means they rather follow 
the release 
cadence of the gnucash product not the documentation one. As we usually release 
those 
together that rarely matters. Another possible motivation to keep them under 
the Gnucash 
product could be repo/bugtracker integration where changes in a repo would 
update related 
bugs. We currently don't have such integration so at that also doesn't matter 
at present.

I'm inclined to keep them under Documentation for now. We can always move them 
later on if 
needed.

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Possible bug in Tax Schedule Report?

[Derek Atkins]

Hi,

Clint Redwood  writes:

> Hi,
>
> I’ve been doing my taxes and have found a potential issue with the
> report. When calculating the transactions on an asset account, it
> appears to take the opening balance as at the opening of
> Report-Start-Date minus 1 day, and then process all the transactions
> during the reporting period, thus giving the final balance on the
> closing date.
>
> However, if there are any transactions on RSD-1, these are ignored, so
> the opening balance is prior to these transactions (which is what I
> think is wrong) and then the correct transactions are processed, and
> you are left with the ending balance being out by the value of the
> RSD-1 transactions.

[snip]

> Is this a bug, or am I using the report wrongly? 

Sounds like a bug -- a holdover from the time when there were timestamps
in dates and therefore the balance at a date *did* take those day's
transactions into account because you could use the time-of-day to order
them.

Please file a bug report (unless another dev speaks up and says it's not
an issue).

> Thanks!
>
> Yours,
>
> Clint Redwood 
>
> Screwtape Limited, Registered 06663232, Babington House, 26 College
> Road, Chilwell, Nottingham NG9 4AS

-derek

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] GnuCash 3 on Linux

[Chris Good]

Hi,

 

I'm working on my BackupGnuCash stand-alone app.

 

I have 2 questions today:

 

1.

I'm a little uncertain about where the saved reports and metadata files are
in GnuCash 3.0 for Linux.

I suspect they are by default:

~/.local/share/gnucash/saved-reports-2.4

~/.local/share/gnucash/books/[BOOK].gnucash.gcm

unless overridden by XDG_DATA_HOME.

 

Can some-one please confirm?

 

2.

I tried to get version 3 on Linux (Ubuntu 16.04) running to test myself.

I found gnucash_3.0-1 at the Debian Archive [1] but when I tried to install
it, 

the following packages were not available:

 

guile-2.2-libs is only available for bionic (18.04LTS) -> 18.10

libaqbanking35 is available in 16.04 -> 18.10

libboost-*.62.0 only available in 17.10 -> 18.10

libgtk-3-0 (>= 3.21.5) only available on 17.10 -> 18.10

libgwenhywfar60 (>= 3.99.16) available on 14.04 -> 18.10

libicu57 (>= 57.1- only available on 17.10

 

Looks like I should upgrade to 18.04 (I mostly only use this VM for testing
GnuCash) or is there an easy way to install the required packages without
overriding the standard packages? I guess on 16.04, I could compile the new
package versions to /usr/local?

 

Maybe I should upgrade to 18.04 then try to build from gnucash maint source?

 

I'm a little worried the Debian Archive 3.0-1 was built on a system with a
not easily reproducible mixture of package versions. I cannot find any
documentation saying what you need to run it.

 

The https://wiki.gnucash.org/wiki/BuildUbuntu16.04 page mentions only
guile-2.0 not guile-2.2.

Does the current gnucash maint build OK on Ubuntu 18.04?

 

[1] http://ftp.us.debian.org/debian/pool/main/g/gnucash/

 

Thanks in advance,

 

Regards, Chris Good

 

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] GnuCash 3 on Linux

[John Ralls]

> On Jun 5, 2018, at 5:53 AM, Chris Good  wrote:
> 
> Hi,
> 
> 
> 
> I'm working on my BackupGnuCash stand-alone app.
> 
> 
> 
> I have 2 questions today:
> 
> 
> 
> 1.
> 
> I'm a little uncertain about where the saved reports and metadata files are
> in GnuCash 3.0 for Linux.
> 
> I suspect they are by default:
> 
> ~/.local/share/gnucash/saved-reports-2.4
> 
> ~/.local/share/gnucash/books/[BOOK].gnucash.gcm
> 
> unless overridden by XDG_DATA_HOME.
> 
> 
> 
> Can some-one please confirm?
> 
> 
> 
> 2.
> 
> I tried to get version 3 on Linux (Ubuntu 16.04) running to test myself.
> 
> I found gnucash_3.0-1 at the Debian Archive [1] but when I tried to install
> it, 
> 
> the following packages were not available:
> 
> 
> 
> guile-2.2-libs is only available for bionic (18.04LTS) -> 18.10
> 
> libaqbanking35 is available in 16.04 -> 18.10
> 
> libboost-*.62.0 only available in 17.10 -> 18.10
> 
> libgtk-3-0 (>= 3.21.5) only available on 17.10 -> 18.10
> 
> libgwenhywfar60 (>= 3.99.16) available on 14.04 -> 18.10
> 
> libicu57 (>= 57.1- only available on 17.10
> 
> 
> 
> Looks like I should upgrade to 18.04 (I mostly only use this VM for testing
> GnuCash) or is there an easy way to install the required packages without
> overriding the standard packages? I guess on 16.04, I could compile the new
> package versions to /usr/local?
> 
> 
> 
> Maybe I should upgrade to 18.04 then try to build from gnucash maint source?
> 
> 
> 
> I'm a little worried the Debian Archive 3.0-1 was built on a system with a
> not easily reproducible mixture of package versions. I cannot find any
> documentation saying what you need to run it.
> 
> 
> 
> The https://wiki.gnucash.org/wiki/BuildUbuntu16.04 page mentions only
> guile-2.0 not guile-2.2.
> 
> Does the current gnucash maint build OK on Ubuntu 18.04?
> 
> 
> 
> [1] http://ftp.us.debian.org/debian/pool/main/g/gnucash/
> 

Chris,

Our Travis CI tests on Ubuntu 14.04 so it should work on any Ubuntu later than 
that. You can copy-and-paste the apt-get and git clone commands from 
https://github.com/Gnucash/gnucash/blob/maint/util/ci/ubuntu-14.04-docker 
 to 
get a ready-to-go build environment.

Regards,
John Ralls


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] GnuCash 3 on Linux

[Geert Janssens]

Op dinsdag 5 juni 2018 14:53:44 CEST schreef Chris Good:
> Hi,
> 
> 
> 
> I'm working on my BackupGnuCash stand-alone app.
> 
> 
> 
> I have 2 questions today:
> 
> 
> 
> 1.
> 
> I'm a little uncertain about where the saved reports and metadata files are
> in GnuCash 3.0 for Linux.
> 
> I suspect they are by default:
> 
> ~/.local/share/gnucash/saved-reports-2.4
 2.8, not 2.4. If not 2.8 file is found, gnucash 3 and up will search for a 
saved-reports-2.4, but it will only save to saved-reports-2.8.
> 
> ~/.local/share/gnucash/books/[BOOK].gnucash.gcm
> 

Yes. Do note it can be [BOOK].gnucash_.gcm if you have several data 
files named [BOOK]. And the gnucash part in that file name is only there if 
the data file is called [BOOK].gnucash. Older versions of gnucash also allowed 
to save to files without extension or with the .xac extension.
So it's really [BOOK-WITH-EXTENSION].gcm

> unless overridden by XDG_DATA_HOME.
> 
If you override XDG_DATA_HOME the files will be searched for and saved in
$XDG_DATA_HOME/gnucash/

However this can be overridden even with GNC_DATA_HOME. If that's set, gnucash 
will search and save in
$GNC_DATA_HOME (which may or may not end in "/gnucash" unlike the 
XDG_DATA_HOME to which gnucash will always append "/gnucash")

Regards,

Geert


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel