Re: [GNC] GnuCash 3.2 Released

[David Cousens]

On Wed, 2018-07-04 at 14:54 +0200, Geert Janssens wrote:
> Op dinsdag 3 juli 2018 00:59:51 CEST schreef DaveC49:
> > 
> > Geert,
> > 
> > I had realised the same thing about needing to uninstall before
> > building and
> > shifted the section on uninstalling to before the section on
> > Building on
> > the Wiki page and specifically mentioned using the previous
> > version's build
> > directory. I might make the note clearer about retaining the build
> > directory for uninstalling.
> > 
> Thanks for documenting all this.

No problem my pleasure
> 
> > 
> > From the tarball the source directory installs with the version
> > number
> > attached (from github it is a generic gnucash). It has become my
> > practice to
> > put the build directory inside the source directory (I have had no
> > problems
> > with that) so it is clearly identified which version it is for, or
> > alternatively one could tag the build directory with the version
> > number as
> > there is no real need to keep the source directory once the build
> > is done.
> This is a subtlety I'm not so sure about.
> I think in order for "make/ninja-build uninstall" to work properly
> you need to 
> keep both the source directory and the build directory. In addition
> the source 
> directory should reflect the version of gnucash you wish to
> uninstall.
> 
> Here's a quick experiment to illustrate this:
> I have a build directory outside my source tree and I have
> successfully run
> ninja-build install

Geert,
You are correct here. I tried the experiment and build.ninja looks for
the CMakeLists.txt in the top level of the source directory and fails
when it is not there. It also goes into the source tree. I copied
CMakeLists.txt back and then it failed when files further down the
source tree were not present
> 
>  This also means cmake will check dependencies
> before trying to run "make uninstall". The uninstall command depends
> on "install_manifest.txt".
> That file seems to be a file generated and tracked by the cmake build
> system itself. Our CMakeLists.txt files don't manipulate it
> explicitly. And clearly cmake attempts track dependencies on this
> file (namely each file that got installed).
The install_manifest.txt file is written by cmake_install.cmake which
is in turn called by the uninstall target in build.ninja which reside
in the top level of the build directory
> 
> > 
> > I'm not pushed for space so I don't bother to delete the source
> > files until
> > I've installed another version and I'm happy with it but others
> > won't
> > necessarily have that luxury.
> > 
> > At the moment the uninstall from a ninja build I did is a kludge. I
> > will see
> > if I can find how/where cmake generates the install secion when
> > creating
> > build.ninja and populate the uninstall target. If I succeed, i'll
> > generate
> > a patch.
> Are you referring to the fact that uninstall doesn't remove empty
> directories
> Maybe that can be improved indeed. I don't know. Keep in mind the
> intended final install destination is typically into a set of 
> directories that already contain applications and libraries. 
> So we can't unconditionally delete all directories. We should at
> least verify whether they are empty or not.
> And we probably don't want to delete any common top-level directory 
> like bin or lib when dealing with standard install locations.
>  

No. The uninstall target in build.ninja as written by cmake was just an
empty stub. It was originally:

#
# Utility command for uninstall

build uninstall: phony CMakeFiles/uninstall

#

 I copied the code from the install target:

#
# Utility command for install

build CMakeFiles/install.util: CUSTOM_COMMAND all
  COMMAND = cd /home/david/Applications/gnucash-3.2/build-ninja &&
/usr/bin/cmake -P cmake_install.cmake
  DESC = Install the project...
  pool = console
  restat = 1
build install: phony CMakeFiles/install.util

#

, substituted "uninstall" for "install" so it became:

#
# Utility command for uninstall
build CMakeFiles/uninstall.util: CUSTOM_COMMAND all
  COMMAND = cd /home/david/Applications/gnucash-3.2/build-ninja &&
/usr/bin/cmake -P cmake_uninstall.cmake
  DESC = Uninstall the project...
  pool = console
  restat = 1
build uninstall: phony CMakeFiles/uninstall

#

and then ninja uninstall works in a shell open in the build directory.

cmake_uninstall.cmake existed and had been created by cmake when it
configured the build, but it could not be executed from build.ninja.
Somewhere in the CMakeLists.txt files in the source something is
missing which writes the code into build.ninja to run
cmake_uninstall.cmake. 

I think it would be nice to tidy up the uninstall of the directories as
well. John has pointed out elsewhere 

Re: [GNC] GnuCash 3.2 Released

[John Ralls]

> On Jul 5, 2018, at 12:56 AM, Geert Janssens  
> wrote:
> 
> Op donderdag 5 juli 2018 07:04:21 CEST schreef David Cousens:
>> On Wed, 2018-07-04 at 14:54 +0200, Geert Janssens wrote:
>>> Are you referring to the fact that uninstall doesn't remove empty
>>> directories
>>> 
>> 
>> No. The uninstall target in build.ninja as written by cmake was just an
>> empty stub. 
> 
> 
>> 
>> cmake_uninstall.cmake existed and had been created by cmake when it
>> configured the build, but it could not be executed from build.ninja.
>> Somewhere in the CMakeLists.txt files in the source something is
>> missing which writes the code into build.ninja to run
>> cmake_uninstall.cmake. 
> 
> This is odd in itself. I have been using ninja-build for months and the 
> uninstall target works just fine without your additions (it does leave the 
> directories of course).
> 
> So I don't understand why you would need to modify the generated build.ninja 
> file.
>> 
>> I think it would be nice to tidy up the uninstall of the directories as
>> well. John has pointed out elsewhere that it isn't absolutely necessary
>> to prevent any interference between installs and that this was
>> primarily for developers but with cmake now the primary build
>> configuration, those of us who like to keep ahead of the distro version
>> are likely to be building from source using cmak and ninja. 
>> 
>> With a /usr/local prefix, GnuCash does a nice install where the files
>> are all copied into directories named as gnucash:
>> /usr/local/lib/gnucash/...
>> /usr/local/share/gnucash/...
>> /usr/local/etc/gnucash/...
>> /usr/local/include/gnucash/...
>> 
>> and the directories I referred to were subdirectories of the respective
>> gnucash directories listed above. At present install_manifest.txt has
>> no explicit record of the existence of them as they are created on the
>> fly when files are installed in them by cmake_install.cmake (top level
>> of build directory) rather than being created explicitly with a mkdir.
>> 
>> Removing the above directories with "rm -r /lib/gnucash " and
>> similar commands for the others should do it with the appropriate
>> checking as you mentioned above.
> 
> Indeed. You could add something to that effect in cmake_uninstall.cmake.in
> 
>> 
>> There is a separate target in build.ninja for install/local (but not an
>> uninstall/local) for installing under a user home directory.
>> 
> build.ninja is generated based on the contents of the various CMakeLists.txt 
> and *.cmake files. I only look in build.ninja if a ninja build behaves 
> differently from a make build. Is that the case here ?
> 
> Note I always install in a custom prefix under my home directory. Perhaps 
> that's why my uninstall works where uninstall under /usr/local doesn't ?
> 
> Something to try when I find the time.
> 
>> Do you know if Rob Gowin is continuing to work on the cmake scripts or
>> not? I don't mind going in and trying to patch it, but if it is still a
>> work in progress then I don't want to get in his way, and I'm happy to
>> leave it to Rob if he is still developing them.
> 
> I don't know. I'll let Rob answer this.

Remember that CMake does things differently when told to install anywhere under 
/usr and /opt.

See https://cmake.org/cmake/help/latest/module/GNUInstallDirs.html 


Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Geert Janssens]

Op donderdag 5 juli 2018 07:04:21 CEST schreef David Cousens:
> On Wed, 2018-07-04 at 14:54 +0200, Geert Janssens wrote:
> > Are you referring to the fact that uninstall doesn't remove empty
> > directories
> >
> 
> No. The uninstall target in build.ninja as written by cmake was just an
> empty stub. 


> 
> cmake_uninstall.cmake existed and had been created by cmake when it
> configured the build, but it could not be executed from build.ninja.
> Somewhere in the CMakeLists.txt files in the source something is
> missing which writes the code into build.ninja to run
> cmake_uninstall.cmake. 

This is odd in itself. I have been using ninja-build for months and the 
uninstall target works just fine without your additions (it does leave the 
directories of course).

So I don't understand why you would need to modify the generated build.ninja 
file.
> 
> I think it would be nice to tidy up the uninstall of the directories as
> well. John has pointed out elsewhere that it isn't absolutely necessary
> to prevent any interference between installs and that this was
> primarily for developers but with cmake now the primary build
> configuration, those of us who like to keep ahead of the distro version
> are likely to be building from source using cmak and ninja. 
> 
> With a /usr/local prefix, GnuCash does a nice install where the files
> are all copied into directories named as gnucash:
> /usr/local/lib/gnucash/...
> /usr/local/share/gnucash/...
> /usr/local/etc/gnucash/...
> /usr/local/include/gnucash/...
> 
> and the directories I referred to were subdirectories of the respective
> gnucash directories listed above. At present install_manifest.txt has
> no explicit record of the existence of them as they are created on the
> fly when files are installed in them by cmake_install.cmake (top level
> of build directory) rather than being created explicitly with a mkdir.
> 
> Removing the above directories with "rm -r /lib/gnucash " and
> similar commands for the others should do it with the appropriate
> checking as you mentioned above.

Indeed. You could add something to that effect in cmake_uninstall.cmake.in

> 
> There is a separate target in build.ninja for install/local (but not an
> uninstall/local) for installing under a user home directory.
> 
build.ninja is generated based on the contents of the various CMakeLists.txt 
and *.cmake files. I only look in build.ninja if a ninja build behaves 
differently from a make build. Is that the case here ?

Note I always install in a custom prefix under my home directory. Perhaps 
that's why my uninstall works where uninstall under /usr/local doesn't ?

Something to try when I find the time.

> Do you know if Rob Gowin is continuing to work on the cmake scripts or
> not? I don't mind going in and trying to patch it, but if it is still a
> work in progress then I don't want to get in his way, and I'm happy to
> leave it to Rob if he is still developing them.

I don't know. I'll let Rob answer this.

Geert



___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Geert Janssens]

Op dinsdag 3 juli 2018 00:59:51 CEST schreef DaveC49:
> Geert,
> 
> I had realised the same thing about needing to uninstall before building and
> shifted the section on uninstalling to before the section on Building on
> the Wiki page and specifically mentioned using the previous version's build
> directory. I might make the note clearer about retaining the build
> directory for uninstalling.
> 
Thanks for documenting all this.

> From the tarball the source directory installs with the version number
> attached (from github it is a generic gnucash). It has become my practice to
> put the build directory inside the source directory (I have had no problems
> with that) so it is clearly identified which version it is for, or
> alternatively one could tag the build directory with the version number as
> there is no real need to keep the source directory once the build is done.

This is a subtlety I'm not so sure about.
I think in order for "make/ninja-build uninstall" to work properly you need to 
keep both the source directory and the build directory. In addition the source 
directory should reflect the version of gnucash you wish to uninstall.

Here's a quick experiment to illustrate this:
I have a build directory outside my source tree and I have successfully run
ninja-build install

Next I move the source tree aside (move source source-org)
And then from my build directory run
ninja-buile uninstall
This gives the following error message:
ninja-build uninstall
[0/1] Re-running CMake...
CMake Error: The source directory "source" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
FAILED: build.ninja 
/usr/bin/cmake -Hsource-Bbuild
ninja: error: rebuilding 'build.ninja': subcommand failed

Cmake tries very hard to detect source changes when running make/ninja-build 
based instructions. This also means cmake will check dependencies before 
trying to run "make uninstall". The uninstall command depends on 
"install_manifest.txt".
That file seems to be a file generated and tracked by the cmake build system 
itself. Our CMakeLists.txt files don't manipulate it explicitly. And clearly 
cmake attempts track dependencies on this file (namely each file that got 
installed).

> I'm not pushed for space so I don't bother to delete the source files until
> I've installed another version and I'm happy with it but others won't
> necessarily have that luxury.
> 
> At the moment the uninstall from a ninja build I did is a kludge. I will see
> if I can find how/where cmake generates the install secion when creating
> build.ninja and populate the uninstall target. If I succeed, i'll generate
> a patch.

Are you referring to the fact that uninstall doesn't remove empty directories 
?
Maybe that can be improved indeed. I don't know. Keep in mind the intended 
final install destination is typically into a set of directories that already 
contain applications and libraries. So we can't unconditionally delete all 
directories. We should at least verify whether they are empty or not. And we 
probably don't want to delete any common top-level directory like bin or lib 
when dealing with standard install locations.

Regards,

Geert


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[DaveC49]

Geert,

I had realised the same thing about needing to uninstall before building and
shifted the section on uninstalling to before the section on Building on the
Wiki page and specifically mentioned using the previous version's build
directory. I might make the note clearer about retaining the build directory
for uninstalling.

>From the tarball the source directory installs with the version number
attached (from github it is a generic gnucash). It has become my practice to
put the build directory inside the source directory (I have had no problems
with that) so it is clearly identified which version it is for, or
alternatively one could tag the build directory with the version number as
there is no real need to keep the source directory once the build is done.
I'm not pushed for space so I don't bother to delete the source files until
I've installed another version and I'm happy with it but others won't
necessarily have that luxury.

At the moment the uninstall from a ninja build I did is a kludge. I will see
if I can find how/where cmake generates the install secion when creating
build.ninja and populate the uninstall target. If I succeed, i'll generate a
patch.

 I take John's point that ninja,  and cmake to a lesser extent now that it
is the only build configuration route, are primarily developers tools. 

David



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[John Ralls]

> On Jul 1, 2018, at 11:13 PM, DaveC49  wrote:
> 
> John,
> 
> Just some further information. I rebuilt GnuCash with the -G Ninja option.
> 
> The build.ninja seems to contain a build uninstall target but it has no
> commands. If I run 
> sudo ninja install
> it installs GnuCash (in/usr/local the prefix I set with cmake) and creates
> install_manifest.txt.
> 
> If i copy the install target in build.ninja to the blank uninstall section
> and modify it as follows
> 
> # Utility command for uninstall
> build CMakeFiles/uninstall.util: CUSTOM_COMMAND all
>  COMMAND = cd /home/david/Applications/gnucash-3.2/build-ninja &&
> /usr/bin/cmake -P cmake_uninstall.cmake
>  DESC = Uninstall the project...
>  pool = console
>  restat = 1
> build uninstall: phony CMakeFiles/uninstall
> 
> and then issue
> 
> sudo ninja uninstall
> 
> Gnucash is correctly uninstalled except that it leaves:
>   an empty gnucash directory in /etc;
>  /include has an empty gnucash folder;
>  /lib has a guncash directory with a scm/ccache/2.2 directory containing
> gnucash, json and qif-import 
> folders
>  /share has a gnucash directory with subdirectories but no files
> 
> It appears the uninstall is removing all files but not necessarily the
> directory structure the files were in. OK unless that changes between
> versions.
> 
> I haven't checked whether the uninstall behavior is any different for the
> make version but a diff on the make and ninja versions of
> install_manifest.txt produces no differences so I would expect that the
> uninstall is the same given the cmake_uninstall.cmake files were essentially
> the same.
> 
> Getting cmake to correctly create the build.ninja uninstall target should be
> enough to get the ninja uninstall working as well.

David,

Remember that cmake is a tool for developers. Installing and uninstalling 
several times an hour isn’t uncommon when coding or debugging.

As for the rest, seems like a lot of work when `xargs rm < 
install_manifest.txt` works well (though it does leave the directory structure, 
but the goal is to get rid of the installable modules and old compiled scheme 
files so that the don’t confuse the new build). It also has the advantage of 
not talking to cmake so it’s not affected by changes in the source directory.

Incidentally, if you’ve already deleted install_manifest.txt, `rm -rf 
/lib/gnucash` will get rid of enough to get a clean build.


Regards,
John Ralls
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[DaveC49]

John,

Just some further information. I rebuilt GnuCash with the -G Ninja option.

The build.ninja seems to contain a build uninstall target but it has no
commands. If I run 
sudo ninja install
it installs GnuCash (in/usr/local the prefix I set with cmake) and creates
install_manifest.txt.

If i copy the install target in build.ninja to the blank uninstall section
and modify it as follows

# Utility command for uninstall
build CMakeFiles/uninstall.util: CUSTOM_COMMAND all
  COMMAND = cd /home/david/Applications/gnucash-3.2/build-ninja &&
/usr/bin/cmake -P cmake_uninstall.cmake
  DESC = Uninstall the project...
  pool = console
  restat = 1
build uninstall: phony CMakeFiles/uninstall

and then issue

sudo ninja uninstall

Gnucash is correctly uninstalled except that it leaves:
   an empty gnucash directory in /etc;
  /include has an empty gnucash folder;
  /lib has a guncash directory with a scm/ccache/2.2 directory containing
gnucash, json and qif-import 
 folders
  /share has a gnucash directory with subdirectories but no files

It appears the uninstall is removing all files but not necessarily the
directory structure the files were in. OK unless that changes between
versions.

I haven't checked whether the uninstall behavior is any different for the
make version but a diff on the make and ninja versions of
install_manifest.txt produces no differences so I would expect that the
uninstall is the same given the cmake_uninstall.cmake files were essentially
the same.

Getting cmake to correctly create the build.ninja uninstall target should be
enough to get the ninja uninstall working as well.

Cheers
David




-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[DaveC49]

John,

I'm using CMake v 3.5.1. Presumably the same or similar could be used to
create an uninstall target for Ninja. Their argument for providing a default
uninstall target seems a bit weak to me as you are not going to be issuing
the command in a build directory unless you really intend to uninstall those
useful files. 

The cmake_uninstall.cmake file contains a reference to

# This is taken from
https://cmake.org/Wiki/CMake_FAQ#Can_I_do_.22make_uninstall.22_with_CMake.3F

which has now been moved to Kitware
https://gitlab.kitware.com/cmake/community/wikis/FAQ

which has a very slow server by the look of it but eventually i found 
https://gitlab.kitware.com/cmake/community/wikis/FAQ#can-i-do-make-uninstall-with-cmake

Can I do "make uninstall" with CMake?

By default, CMake does not provide the "make uninstall" target, so you
cannot do this. We do not want "make uninstall" to remove useful files
from the system.

If you want an "uninstall" target in your project, then nobody prevents
you from providing one. You need to delete the files listed in
install_manifest.txt file. Here is how to do it. First create file
cmake_uninstall.cmake.in in the top-level directory of the project:

if(NOT EXISTS "@CMAKE_BINARY_DIR@/install_manifest.txt")
  message(FATAL_ERROR "Cannot find install manifest:
@CMAKE_BINARY_DIR@/install_manifest.txt")
endif(NOT EXISTS "@CMAKE_BINARY_DIR@/install_manifest.txt")

file(READ "@CMAKE_BINARY_DIR@/install_manifest.txt" files)
string(REGEX REPLACE "\n" ";" files "${files}")
foreach(file ${files})
  message(STATUS "Uninstalling $ENV{DESTDIR}${file}")
  if(IS_SYMLINK "$ENV{DESTDIR}${file}" OR EXISTS "$ENV{DESTDIR}${file}")
exec_program(
  "@CMAKE_COMMAND@" ARGS "-E remove \"$ENV{DESTDIR}${file}\""
  OUTPUT_VARIABLE rm_out
  RETURN_VALUE rm_retval
  )
if(NOT "${rm_retval}" STREQUAL 0)
  message(FATAL_ERROR "Problem when removing $ENV{DESTDIR}${file}")
endif(NOT "${rm_retval}" STREQUAL 0)
  else(IS_SYMLINK "$ENV{DESTDIR}${file}" OR EXISTS "$ENV{DESTDIR}${file}")
message(STATUS "File $ENV{DESTDIR}${file} does not exist.")
  endif(IS_SYMLINK "$ENV{DESTDIR}${file}" OR EXISTS "$ENV{DESTDIR}${file}")
endforeach(file)
Then in the top-level CMakeLists.txt add the following logic:

# uninstall target
if(NOT TARGET uninstall)
configure_file(
"${CMAKE_CURRENT_SOURCE_DIR}/cmake_uninstall.cmake.in"
"${CMAKE_CURRENT_BINARY_DIR}/cmake_uninstall.cmake"
IMMEDIATE @ONLY)

add_custom_target(uninstall
COMMAND ${CMAKE_COMMAND} -P
${CMAKE_CURRENT_BINARY_DIR}/cmake_uninstall.cmake)
endif()
Now you will have an "uninstall" target at the top-level directory of
your build tree.

Instead of creating an "uninstall" target, Unix users could enter this
command in the shell:

xargs rm < install_manifest.txt



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Geert Janssens]

It was actually implemented by Rob Gowin in February last year:
https://github.com/Gnucash/gnucash/commit/6b14dc5b59ee

But while thinking of this I suspect the uninstall target should equally be 
run from the build directory that was used to install the old gnucash version. 
If you have already updated the source directory to the newer gnucash version 
invoking the uninstall target (be it from ninja-build or make) will probably 
trigger an update of the install-manifest file to match the newer sources 
before the uninstall itself will be triggered. And in that case it would still 
not uninstall obsolete files.

Geert

Op zondag 1 juli 2018 17:28:46 CEST schreef John Ralls:
> David,
> 
> That’s apparently new and undocumented behavior, maybe in CMake 3.10. Thanks
> for reporting it.
> 
> Regards,
> John Ralls
> 
> > On Jun 30, 2018, at 1:26 AM, DaveC49  wrote:
> > 
> > Hi John,
> > 
> > If GnuCash is not built with Ninja, there is a cmake_uninstall.cmake file
> > in the top level of the build directory which seems to read the
> > install_manifest.txt file. The Makefile in the same level produced by
> > CMake
> > has an uninstall target - not sure how it executes the commands in the
> > cmake_uninstall.cmake file but it appears to.
> > 
> > Executing "make uninstall" ( prefixed with sudo if installed in a system
> > location) in the build directory does remove all of the GnuCash files
> > installed in the  specified to cmake. (GnuCash V3.2 from the
> > SourceForge tarball on Linux Mint 18.3 built using Cmake, make and -
> > should
> > be the same for Ubuntu).
> > 
> > Not sure that happens if it is built with Ninja rather than make though.
> > 
> > David Cousens
> > 
> > 
> > 
> > -
> > David Cousens
> > --
> > Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> > ___
> > gnucash-user mailing list
> > gnucash-user@gnucash.org
> > To update your subscription preferences or to unsubscribe:
> > https://lists.gnucash.org/mailman/listinfo/gnucash-user
> > If you are using Nabble or Gmane, please see
> > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. -
> > Please remember to CC this list on all your replies.
> > You can do this by using Reply-To-List or Reply-All.
> 
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information. -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.




___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[John Ralls]

David,

That’s apparently new and undocumented behavior, maybe in CMake 3.10. Thanks 
for reporting it.

Regards,
John Ralls

> On Jun 30, 2018, at 1:26 AM, DaveC49  wrote:
> 
> Hi John,
> 
> If GnuCash is not built with Ninja, there is a cmake_uninstall.cmake file in
> the top level of the build directory which seems to read the
> install_manifest.txt file. The Makefile in the same level produced by CMake
> has an uninstall target - not sure how it executes the commands in the
> cmake_uninstall.cmake file but it appears to. 
> 
> Executing "make uninstall" ( prefixed with sudo if installed in a system
> location) in the build directory does remove all of the GnuCash files
> installed in the  specified to cmake. (GnuCash V3.2 from the
> SourceForge tarball on Linux Mint 18.3 built using Cmake, make and - should
> be the same for Ubuntu).
> 
> Not sure that happens if it is built with Ninja rather than make though.
> 
> David Cousens
> 
> 
> 
> -
> David Cousens
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[DaveC49]

Hi John,

If GnuCash is not built with Ninja, there is a cmake_uninstall.cmake file in
the top level of the build directory which seems to read the
install_manifest.txt file. The Makefile in the same level produced by CMake
has an uninstall target - not sure how it executes the commands in the
cmake_uninstall.cmake file but it appears to. 

Executing "make uninstall" ( prefixed with sudo if installed in a system
location) in the build directory does remove all of the GnuCash files
installed in the  specified to cmake. (GnuCash V3.2 from the
SourceForge tarball on Linux Mint 18.3 built using Cmake, make and - should
be the same for Ubuntu).

Not sure that happens if it is built with Ninja rather than make though.

David Cousens



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Stephen M. Butler]

On 06/29/2018 12:43 AM, DaveC49 wrote:
> Stephen,
>
> It is generally a good idea to remove the previous version before installing
> a new one. Gnucash will generally overwrite any existing files of the same
> name, but you may be left with unnecessary files in some cases. Going from
> 3.1 to 3.2 should be OK as there are unlikey to be major changes in the file
> structure, but between major version could be problematical There are
> instructions on the Wiki in the build instructions for Ubuntu 16.04 for
> doing uninstalls in a variety of circumstances including manually deleting
> all the files which will be the same for 18.04. I'll put a note in there re
> uninstalling previous versionsbefore the build instructions to make it
> clearer.
>
> If you still have the 3.1 build directory:
>  open a shell and cd to the build directory then type 
>  sudo make uninstall

Sadly, I aggressively removed it when bringing in 3.2  :-(
So a learning experience that, hopefully, I can help others avoid.
>
> then do the install of V3.2
>
> This uses a manifest created when Gnucash was installed to uninstall all of
> the program files. It leaves user preference files untouched.
>
> David
>
>
>
> -
> David Cousens
> --
> Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> ___
> gnucash-user mailing list
> gnucash-user@gnucash.org
> To update your subscription preferences or to unsubscribe:
> https://lists.gnucash.org/mailman/listinfo/gnucash-user
> If you are using Nabble or Gmane, please see 
> https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
> -
> Please remember to CC this list on all your replies.
> You can do this by using Reply-To-List or Reply-All.
>

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Geert Janssens]

Op vrijdag 29 juni 2018 09:43:59 CEST schreef DaveC49:
> Stephen,
> 
> It is generally a good idea to remove the previous version before installing
> a new one. Gnucash will generally overwrite any existing files of the same
> name, but you may be left with unnecessary files in some cases. Going from
> 3.1 to 3.2 should be OK as there are unlikey to be major changes in the
> file structure,

Unfortunately one file change did slip through in the report files between 3.1 
and 3.2. If not uninstalling it would leave two .scm files and two .go files 
from the 3.1 installation that conflict with the new files in 3.2.

Geert


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[DaveC49]

Stephen,

It is generally a good idea to remove the previous version before installing
a new one. Gnucash will generally overwrite any existing files of the same
name, but you may be left with unnecessary files in some cases. Going from
3.1 to 3.2 should be OK as there are unlikey to be major changes in the file
structure, but between major version could be problematical There are
instructions on the Wiki in the build instructions for Ubuntu 16.04 for
doing uninstalls in a variety of circumstances including manually deleting
all the files which will be the same for 18.04. I'll put a note in there re
uninstalling previous versionsbefore the build instructions to make it
clearer.

If you still have the 3.1 build directory:
 open a shell and cd to the build directory then type 
 sudo make uninstall

then do the install of V3.2

This uses a manifest created when Gnucash was installed to uninstall all of
the program files. It leaves user preference files untouched.

David



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Stephen M. Butler]

On 06/29/2018 02:17 PM, Geert Janssens wrote:
> Op vrijdag 29 juni 2018 21:04:31 CEST schreef Stephen M. Butler:
>> On 06/29/2018 11:02 AM, Geert Janssens wrote:
>>> Op vrijdag 29 juni 2018 19:54:04 CEST schreef Stephen M. Butler:
 On 06/29/2018 12:42 AM, Geert Janssens wrote:
> Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler:
>> Further research:
>>
>> It appears that net-charts.scm is a replacement for two other files in
>> standard-reports:  net-linecharts.scm and net-barcharts.scm
>>
>> I renamed those two to have a .old extension on them and GnuCash now
>> starts up without complaining about duplicate report IDs.
> Ah indeed. As you indicated you didn't uninstall first, the old files
> remained in the installation directory causing the conflict.
 Hopefully I remember for the next upgrade.

> The formal way to uninstall is a bit picky. You should run "make
> uninstall" in your build directory *before* changing the source
> directory
> to a newer version (be it a new git checkout or pull, or installing a
> new
> release tar ball).
>
> If you installed gnucash in it's own prefix (by adding
> -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as
> easy as deleting this prefix.
>
> But in this case manually removing/renaming the offending files works as
> well. I would remove/rename the corresponding .go files in gnucash'
> lib64/gnucash/ scm/ccache/ directory as well though.
 Hmm.  Can't find that path.  Here is what is in /lib64 on my Ubuntu
 18.04 box:
>>> Oh, right. I believe debian and derivates use a different scheme for
>>> 64-bit
>>> applications
>>>
>>> Do you have
>>> /usr/lib/x86_64-linux-gnu/gnucash/scm/ccache ?
>>>
>>> Geert
>> Not that I see -- I am using a 64-bit O/S so maybe 32 bit apps are the
>> odd member here?
>>
>> I did find them here though:
>> /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports
>> Occasionally find can be useful!
>>
>> sudo find / -name net-barchart.go
>> /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports/net-ba
>> rchart.go
>>
>> I removed both.
> Ah, indeed. If you don't specify a prefix, cmake will use /usr/local. Sorry 
> for sending you around on different wrong paths.
>
> Geert
>
>
>
>

No problem.  Forces me to figure out what _is_ happening.  At least you
told me about the .go files.
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Geert Janssens]

Op vrijdag 29 juni 2018 21:04:31 CEST schreef Stephen M. Butler:
> On 06/29/2018 11:02 AM, Geert Janssens wrote:
> > Op vrijdag 29 juni 2018 19:54:04 CEST schreef Stephen M. Butler:
> >> On 06/29/2018 12:42 AM, Geert Janssens wrote:
> >>> Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler:
>  Further research:
>  
>  It appears that net-charts.scm is a replacement for two other files in
>  standard-reports:  net-linecharts.scm and net-barcharts.scm
>  
>  I renamed those two to have a .old extension on them and GnuCash now
>  starts up without complaining about duplicate report IDs.
> >>> 
> >>> Ah indeed. As you indicated you didn't uninstall first, the old files
> >>> remained in the installation directory causing the conflict.
> >> 
> >> Hopefully I remember for the next upgrade.
> >> 
> >>> The formal way to uninstall is a bit picky. You should run "make
> >>> uninstall" in your build directory *before* changing the source
> >>> directory
> >>> to a newer version (be it a new git checkout or pull, or installing a
> >>> new
> >>> release tar ball).
> >>> 
> >>> If you installed gnucash in it's own prefix (by adding
> >>> -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as
> >>> easy as deleting this prefix.
> >>> 
> >>> But in this case manually removing/renaming the offending files works as
> >>> well. I would remove/rename the corresponding .go files in gnucash'
> >>> lib64/gnucash/ scm/ccache/ directory as well though.
> >> 
> >> Hmm.  Can't find that path.  Here is what is in /lib64 on my Ubuntu
> > 
> >> 18.04 box:
> > Oh, right. I believe debian and derivates use a different scheme for
> > 64-bit
> > applications
> > 
> > Do you have
> > /usr/lib/x86_64-linux-gnu/gnucash/scm/ccache ?
> > 
> > Geert
> 
> Not that I see -- I am using a 64-bit O/S so maybe 32 bit apps are the
> odd member here?
> 
> I did find them here though:
> /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports
> Occasionally find can be useful!
> 
> sudo find / -name net-barchart.go
> /usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports/net-ba
> rchart.go
> 
> I removed both.

Ah, indeed. If you don't specify a prefix, cmake will use /usr/local. Sorry 
for sending you around on different wrong paths.

Geert



___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Stephen M. Butler]

On 06/29/2018 11:02 AM, Geert Janssens wrote:
> Op vrijdag 29 juni 2018 19:54:04 CEST schreef Stephen M. Butler:
>> On 06/29/2018 12:42 AM, Geert Janssens wrote:
>>> Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler:
 Further research:

 It appears that net-charts.scm is a replacement for two other files in
 standard-reports:  net-linecharts.scm and net-barcharts.scm

 I renamed those two to have a .old extension on them and GnuCash now
 starts up without complaining about duplicate report IDs.
>>> Ah indeed. As you indicated you didn't uninstall first, the old files
>>> remained in the installation directory causing the conflict.
>> Hopefully I remember for the next upgrade.
>>
>>> The formal way to uninstall is a bit picky. You should run "make
>>> uninstall" in your build directory *before* changing the source directory
>>> to a newer version (be it a new git checkout or pull, or installing a new
>>> release tar ball).
>>>
>>> If you installed gnucash in it's own prefix (by adding
>>> -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as
>>> easy as deleting this prefix.
>>>
>>> But in this case manually removing/renaming the offending files works as
>>> well. I would remove/rename the corresponding .go files in gnucash'
>>> lib64/gnucash/ scm/ccache/ directory as well though.
>> Hmm.  Can't find that path.  Here is what is in /lib64 on my Ubuntu
>> 18.04 box:
> Oh, right. I believe debian and derivates use a different scheme for 64-bit 
> applications
>
> Do you have
> /usr/lib/x86_64-linux-gnu/gnucash/scm/ccache ?
>
> Geert
>
>
Not that I see -- I am using a 64-bit O/S so maybe 32 bit apps are the
odd member here?

I did find them here though:
/usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports
Occasionally find can be useful!

sudo find / -name net-barchart.go
/usr/local/lib/gnucash/scm/ccache/2.0/gnucash/report/standard-reports/net-barchart.go

I removed both.

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Stephen M. Butler]

On 06/29/2018 12:42 AM, Geert Janssens wrote:
> Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler:
>> Further research:
>>
>> It appears that net-charts.scm is a replacement for two other files in
>> standard-reports:  net-linecharts.scm and net-barcharts.scm
>>
>> I renamed those two to have a .old extension on them and GnuCash now
>> starts up without complaining about duplicate report IDs.
>>
> Ah indeed. As you indicated you didn't uninstall first, the old files 
> remained 
> in the installation directory causing the conflict.

Hopefully I remember for the next upgrade.
> The formal way to uninstall is a bit picky. You should run "make uninstall" 
> in 
> your build directory *before* changing the source directory to a newer 
> version 
> (be it a new git checkout or pull, or installing a new release tar ball).
>
> If you installed gnucash in it's own prefix (by adding
> -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as easy 
> as deleting this prefix.
>
> But in this case manually removing/renaming the offending files works as 
> well. 
> I would remove/rename the corresponding .go files in gnucash' lib64/gnucash/
> scm/ccache/ directory as well though.

Hmm.  Can't find that path.  Here is what is in /lib64 on my Ubuntu
18.04 box:
drwxr-xr-x  2 root root 4096 May  6 20:28 ./
drwxr-xr-x 26 root root 4096 Jun 12 10:04 ../
lrwxrwxrwx  1 root root   32 Apr 16 13:14 ld-linux-x86-64.so.2 ->
/lib/x86_64-linux-gnu/ld-2.27.so*
lrwxrwxrwx  1 root root   20 May  6 20:28 ld-lsb-x86-64.so.2 ->
ld-linux-x86-64.so.2*
lrwxrwxrwx  1 root root   20 May  6 20:28 ld-lsb-x86-64.so.3 ->
ld-linux-x86-64.so.2*

And here is the location of all lib64 directories (via sudo find / -name
lib64

/usr/src/linux-headers-3.19.0-28/arch/sh/lib64
/usr/src/linux-headers-3.19.0-26/arch/sh/lib64
/usr/src/linux-headers-3.19.0-25/arch/sh/lib64
/usr/src/linux-headers-4.15.0-23/arch/sh/lib64
/usr/src/linux-headers-3.19.0-29/arch/sh/lib64
/usr/src/linux-headers-4.15.0-22/arch/sh/lib64
/usr/src/linux-headers-3.19.0-27/arch/sh/lib64
/usr/src/linux-headers-3.19.0-23/arch/sh/lib64
/usr/src/linux-headers-3.19.0-24/arch/sh/lib64
/usr/src/linux-headers-3.16.0-32/arch/sh/lib64
/lib64
/var/tmp/mkinitramfs_pYKPbh/lib64
/var/tmp/mkinitramfs_edihqS/lib64
/var/tmp/mkinitramfs_JevWJj/lib64
/var/tmp/mkinitramfs_dZ5Hy3/lib64
/var/tmp/mkinitramfs_2s7hMA/lib64
/var/tmp/mkinitramfs_ncQdoR/lib64
/var/tmp/mkinitramfs_fF6uQ0/lib64
/var/tmp/mkinitramfs_pWngoT/lib64
/var/tmp/mkinitramfs_gE5Jr7/lib64
/var/tmp/mkinitramfs_9spxCx/lib64
/var/tmp/mkinitramfs_Qr12to/lib64
/var/tmp/mkinitramfs_FJaQ9o/lib64
/snap/core/4830/lib64
/snap/core/4571/lib64
/snap/core/4650/lib64
/opt/wine-devel/lib64
/opt/sophos-av/lib64
/opt/sophos-av/update/cache/Primary/sav-linux/x86/64/lib64
/opt/epson-inkjet-printer-201208w/lib64
> Geert
>
>

Thanks,
-- Steve
___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Geert Janssens]

Op vrijdag 29 juni 2018 19:54:04 CEST schreef Stephen M. Butler:
> On 06/29/2018 12:42 AM, Geert Janssens wrote:
> > Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler:
> >> Further research:
> >> 
> >> It appears that net-charts.scm is a replacement for two other files in
> >> standard-reports:  net-linecharts.scm and net-barcharts.scm
> >> 
> >> I renamed those two to have a .old extension on them and GnuCash now
> >> starts up without complaining about duplicate report IDs.
> > 
> > Ah indeed. As you indicated you didn't uninstall first, the old files
> > remained in the installation directory causing the conflict.
> 
> Hopefully I remember for the next upgrade.
> 
> > The formal way to uninstall is a bit picky. You should run "make
> > uninstall" in your build directory *before* changing the source directory
> > to a newer version (be it a new git checkout or pull, or installing a new
> > release tar ball).
> > 
> > If you installed gnucash in it's own prefix (by adding
> > -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as
> > easy as deleting this prefix.
> > 
> > But in this case manually removing/renaming the offending files works as
> > well. I would remove/rename the corresponding .go files in gnucash'
> > lib64/gnucash/ scm/ccache/ directory as well though.
> 
> Hmm.  Can't find that path.  Here is what is in /lib64 on my Ubuntu
> 18.04 box:

Oh, right. I believe debian and derivates use a different scheme for 64-bit 
applications

Do you have
/usr/lib/x86_64-linux-gnu/gnucash/scm/ccache ?

Geert


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[John Ralls]

> On Jun 29, 2018, at 12:42 AM, Geert Janssens  
> wrote:
> 
> Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler:
>> Further research:
>> 
>> It appears that net-charts.scm is a replacement for two other files in
>> standard-reports:  net-linecharts.scm and net-barcharts.scm
>> 
>> I renamed those two to have a .old extension on them and GnuCash now
>> starts up without complaining about duplicate report IDs.
>> 
> 
> Ah indeed. As you indicated you didn't uninstall first, the old files 
> remained 
> in the installation directory causing the conflict.
> 
> The formal way to uninstall is a bit picky. You should run "make uninstall" 
> in 
> your build directory *before* changing the source directory to a newer 
> version 
> (be it a new git checkout or pull, or installing a new release tar ball).
> 
> If you installed gnucash in it's own prefix (by adding
> -DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as easy 
> as deleting this prefix.
> 
> But in this case manually removing/renaming the offending files works as 
> well. 
> I would remove/rename the corresponding .go files in gnucash' lib64/gnucash/
> scm/ccache/ directory as well though.

CMake doesn’t create an uninstall target. To uninstall, use `xargs rm < 
install_manifest.txt` from the build directory. (In Windows CMake writes 
install_manifest.txt with windows paths so you have to use a Powershell window 
and do `get-contents install_manifest.txt | remove-item`).

On a related note, CMake’s clean target seems broken for makefiles but works 
fine for ninja.

Regards,
John Ralls

___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Geert Janssens]

Op donderdag 28 juni 2018 22:11:49 CEST schreef Dennis West:
> I'm sure you like to get feedback from someone with absolutely no
> problems at all.
> 
> I was using 2.6.21 on my primary computer and testing 3.1/3.2 on my
> standby testbed (both on Win 10.1803).  I finally decided to take the
> plunge and upgraded my primary computer form 2.6.21 to 3.2.  The
> experience was flawless and now my testbed pc is eagerly awaiting vs 4.0.
> 
> Dennis

Dennis,

That's nice to hear :)

Geert


___
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: [GNC] GnuCash 3.2 Released

[Geert Janssens]

Op maandag 25 juni 2018 19:42:37 CEST schreef Stephen M. Butler:
> Further research:
> 
> It appears that net-charts.scm is a replacement for two other files in
> standard-reports:  net-linecharts.scm and net-barcharts.scm
> 
> I renamed those two to have a .old extension on them and GnuCash now
> starts up without complaining about duplicate report IDs.
> 

Ah indeed. As you indicated you didn't uninstall first, the old files remained 
in the installation directory causing the conflict.

The formal way to uninstall is a bit picky. You should run "make uninstall" in 
your build directory *before* changing the source directory to a newer version 
(be it a new git checkout or pull, or installing a new release tar ball).

If you installed gnucash in it's own prefix (by adding
-DCMAKE_INSTALL_PREFIX=xyz to your cmake run), uninstalling would be as easy 
as deleting this prefix.

But in this case manually removing/renaming the offending files works as well. 
I would remove/rename the corresponding .go files in gnucash' lib64/gnucash/
scm/ccache/ directory as well though.

Geert

> 
> Stephen M Butler, PMP, PSM
> stephen.m.butle...@gmail.com
> kg...@arrl.net
> 253-350-0166
> ---
> GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8
> 
> On 06/25/2018 10:20 AM, Stephen M. Butler wrote:
> > Compiled and installed on Ubuntu 18.04.
> > 
> > When starting up it reports several duplicate report IDs.  Should I have
> > uninstalled 3.1 first?  I did these commands (with an empty mybuild):
> > 
> > cd mybuild
> > 
> > cmake ../gnucash-3.2
> > 
> > make
> > 
> > sudo make install
> > 
> > 
> > Stephen M Butler, PMP, PSM
> > stephen.m.butle...@gmail.com
> > kg...@arrl.net
> > 253-350-0166
> > ---
> > GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8
> > 
> > On 06/24/2018 08:40 PM, John Ralls wrote:
> >> The GnuCash development team announces GnuCash 3.2, the second release of
> >> the 3.x stable release series.
> >> 
> >> Changes
> >> 
> >> Between 3.0 and 3.2, the following bugfixes were accomplished:
> >>• Bug 787401 - Test Report System - Report Definition.
> >>• Bug 794617 - Can't compile with -DWITH_GNUCASH=NO due to
> >>scm-gnome-utils.
> >>• Bug 795101 - Scroll Bar in Reconcile Window Floats in and covers 
the
> >>check boxes. • Bug 795247 - datepicker broken in Persian. GnuCash
> >>passes dates as integer y/m/d without using locale-specific formats, 
so
> >>we need to strip out 'E' and 'O' from the format when scanning dates 
or
> >>determining separators in gnc-date. None of '-', 'E', or 'O' are
> >>supported by boost (and '-' causes errors), so strip them out from
> >>formatters in gnc-datetime as well. • Bug 795253 - Have problems 
input
> >>Chinese.
> >>• Bug 795272 - QIF importer causes application crash if action is
> >>invalid.
> >>• Bug 795276 - Invalid date on price stops file from being parsed.
> >>• Bug 795362 - Special variable "i" not parsed in function calls. Due 
to
> >>balance tests with insane random values. • Bug 795471 - Impossible to
> >>Edit Budget Unless Maximized.
> >>• Bug 795519 - Credit card payment after reconciliation.
> >>• Bug 795666 - Backslash '\' in Description field spoils CSV Import
> >>without helpful error message. • Bug 795831 - When read only 
threshold
> >>set, dates are silently changed. Display a message box informing the
> >>user of the change. • Bug 795944 - Cannot store change to Business
> >>Suppliers data.
> >>• Bug 796079 - Repeatable Crash in Tax Report Options.
> >>• Bug 796081 - Tax Schedule Report - An error occurred while running 
the
> >>report. • Bug 796083 - Reconcile Selection Doesn't Work Anymore.
> >>• Bug 796117 - Connecting 3.1 to an existing mysql db drops all data.
> >>Provide a backup recovery function that instead of dropping primaries
> >>and restoring backups merges the primaries and backups. This should
> >>handle a worst-case safe-save failure where the backup tables don't
> >>have a complete set of rows for some reason. • Bug 796256 - Main 
Window
> >>stays hidden when starting after closing main window while minimized. 
•
> >>Bug 796369 - Notes lost or perhaps just not displaying when using
> >>SQLite backend. This bug caused data loss if you saved your SQLite3
> >>database to a different file or database. The problem is that in
> >>SQLite3 (though not in MySQL or PgSQL) the subquery ((SELECT DISTINCT
> >>guid FROM transactions)) (note the double parentheses) returns only 
the
> >>first guid in the subquery's results. Some transactions are loaded by
> >>special queries and those queries are also used to retrieve the
> >>transaction's slots so they weren't affected. • Bug 796398 - Restrict
> >>accelerator keys to valid date range.
> >>• Bug 796409 - Incorrect 

Re: [GNC] GnuCash 3.2 Released

[Dennis West]

I'm sure you like to get feedback from someone with absolutely no 
problems at all.


I was using 2.6.21 on my primary computer and testing 3.1/3.2 on my 
standby testbed (both on Win 10.1803).  I finally decided to take the 
plunge and upgraded my primary computer form 2.6.21 to 3.2.  The 
experience was flawless and now my testbed pc is eagerly awaiting vs 4.0.


Dennis


On 6/24/2018 22:40, John Ralls wrote:

The GnuCash development team announces GnuCash 3.2, the second release of the 
3.x stable release series.

Changes

Between 3.0 and 3.2, the following bugfixes were accomplished:

• Bug 787401 - Test Report System - Report Definition.
• Bug 794617 - Can't compile with -DWITH_GNUCASH=NO due to 
scm-gnome-utils.
• Bug 795101 - Scroll Bar in Reconcile Window Floats in and covers the 
check boxes.
• Bug 795247 - datepicker broken in Persian. GnuCash passes dates as 
integer y/m/d without using locale-specific formats, so we need to strip out 
'E' and 'O' from the format when scanning dates or determining separators in 
gnc-date. None of '-', 'E', or 'O' are supported by boost (and '-' causes 
errors), so strip them out from formatters in gnc-datetime as well.
• Bug 795253 - Have problems input Chinese.
• Bug 795272 - QIF importer causes application crash if action is 
invalid.
• Bug 795276 - Invalid date on price stops file from being parsed.
• Bug 795362 - Special variable "i" not parsed in function calls. Due 
to balance tests with insane random values.
• Bug 795471 - Impossible to Edit Budget Unless Maximized.
• Bug 795519 - Credit card payment after reconciliation.
• Bug 795666 - Backslash '\' in Description field spoils CSV Import 
without helpful error message.
• Bug 795831 - When read only threshold set, dates are silently 
changed. Display a message box informing the user of the change.
• Bug 795944 - Cannot store change to Business Suppliers data.
• Bug 796079 - Repeatable Crash in Tax Report Options.
• Bug 796081 - Tax Schedule Report - An error occurred while running 
the report.
• Bug 796083 - Reconcile Selection Doesn't Work Anymore.
• Bug 796117 - Connecting 3.1 to an existing mysql db drops all data. 
Provide a backup recovery function that instead of dropping primaries and 
restoring backups merges the primaries and backups. This should handle a 
worst-case safe-save failure where the backup tables don't have a complete set 
of rows for some reason.
• Bug 796256 - Main Window stays hidden when starting after closing 
main window while minimized.
• Bug 796369 - Notes lost or perhaps just not displaying when using 
SQLite backend. This bug caused data loss if you saved your SQLite3 database to 
a different file or database. The problem is that in SQLite3 (though not in 
MySQL or PgSQL) the subquery ((SELECT DISTINCT guid FROM transactions)) (note 
the double parentheses) returns only the first guid in the subquery's results. 
Some transactions are loaded by special queries and those queries are also used 
to retrieve the transaction's slots so they weren't affected.
• Bug 796398 - Restrict accelerator keys to valid date range.
• Bug 796409 - Incorrect Current Value for Stocks. Missed calculating 
the value in the register summary bar.
• Bug 796423 - Cannot Input Chinese, seems does not work with other IME 
too. Toggles not in view with all rows selected weren't being redrawn.
• Bug 796484 - csv import: iostream error. Unfortunately it turns out 
that we can't use filestreams because they can't take path arguments containing 
Unicode on Windows.
• Bug 796527 - invalid currency on scheduled transactions.
• Don't even check for price/exchange rate on template 
transactions, there's no point.
• Check all split commodities are valid, abort transaction 
creation if not.
• If the template transaction's currency isn't used by any of 
the splits set the new transaction's currency to the first-found currency if 
there is one, otherwise to the first-found commodity.
• Bug 796537 - Transaction Report cannot sort by "num".
• Bug 796586 - QIF import incorrectly converts unicode characters from 
UTF8 encoded file.
• Bug 796595 - QIF Import Select Account button to add a new account is 
labled gnc-account-new but should be New.
• Bug 796600 - stock split cash-in-lieu income/asset labels backwards.
• Bug 796614 - Reconciliation report contains incorrect transactions.
• Bug 796638 - configuration not properly saved for CSV transactions 
import form.
The Following fixes and improvemts were not associated with bug reports:

• Transaction report improvements:
• Performance: Do all filtering ops before sorting.
• Move the options summary before the subtotals table.
• New 

Re: [GNC] GnuCash 3.2 Released

[Stephen M. Butler]

Further research:

It appears that net-charts.scm is a replacement for two other files in
standard-reports:  net-linecharts.scm and net-barcharts.scm

I renamed those two to have a .old extension on them and GnuCash now
starts up without complaining about duplicate report IDs.


Stephen M Butler, PMP, PSM
stephen.m.butle...@gmail.com
kg...@arrl.net
253-350-0166
---
GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8

On 06/25/2018 10:20 AM, Stephen M. Butler wrote:
> Compiled and installed on Ubuntu 18.04.
>
> When starting up it reports several duplicate report IDs.  Should I have
> uninstalled 3.1 first?  I did these commands (with an empty mybuild):
>
> cd mybuild
>
> cmake ../gnucash-3.2
>
> make
>
> sudo make install
>
>
> Stephen M Butler, PMP, PSM
> stephen.m.butle...@gmail.com
> kg...@arrl.net
> 253-350-0166
> ---
> GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8
>
> On 06/24/2018 08:40 PM, John Ralls wrote:
>> The GnuCash development team announces GnuCash 3.2, the second release of 
>> the 3.x stable release series.
>>
>> Changes
>>
>> Between 3.0 and 3.2, the following bugfixes were accomplished:
>>
>>  • Bug 787401 - Test Report System - Report Definition.
>>  • Bug 794617 - Can't compile with -DWITH_GNUCASH=NO due to 
>> scm-gnome-utils.
>>  • Bug 795101 - Scroll Bar in Reconcile Window Floats in and covers the 
>> check boxes.
>>  • Bug 795247 - datepicker broken in Persian. GnuCash passes dates as 
>> integer y/m/d without using locale-specific formats, so we need to strip out 
>> 'E' and 'O' from the format when scanning dates or determining separators in 
>> gnc-date. None of '-', 'E', or 'O' are supported by boost (and '-' causes 
>> errors), so strip them out from formatters in gnc-datetime as well.
>>  • Bug 795253 - Have problems input Chinese.
>>  • Bug 795272 - QIF importer causes application crash if action is 
>> invalid.
>>  • Bug 795276 - Invalid date on price stops file from being parsed.
>>  • Bug 795362 - Special variable "i" not parsed in function calls. Due 
>> to balance tests with insane random values.
>>  • Bug 795471 - Impossible to Edit Budget Unless Maximized.
>>  • Bug 795519 - Credit card payment after reconciliation.
>>  • Bug 795666 - Backslash '\' in Description field spoils CSV Import 
>> without helpful error message.
>>  • Bug 795831 - When read only threshold set, dates are silently 
>> changed. Display a message box informing the user of the change.
>>  • Bug 795944 - Cannot store change to Business Suppliers data.
>>  • Bug 796079 - Repeatable Crash in Tax Report Options.
>>  • Bug 796081 - Tax Schedule Report - An error occurred while running 
>> the report.
>>  • Bug 796083 - Reconcile Selection Doesn't Work Anymore.
>>  • Bug 796117 - Connecting 3.1 to an existing mysql db drops all data. 
>> Provide a backup recovery function that instead of dropping primaries and 
>> restoring backups merges the primaries and backups. This should handle a 
>> worst-case safe-save failure where the backup tables don't have a complete 
>> set of rows for some reason.
>>  • Bug 796256 - Main Window stays hidden when starting after closing 
>> main window while minimized.
>>  • Bug 796369 - Notes lost or perhaps just not displaying when using 
>> SQLite backend. This bug caused data loss if you saved your SQLite3 database 
>> to a different file or database. The problem is that in SQLite3 (though not 
>> in MySQL or PgSQL) the subquery ((SELECT DISTINCT guid FROM transactions)) 
>> (note the double parentheses) returns only the first guid in the subquery's 
>> results. Some transactions are loaded by special queries and those queries 
>> are also used to retrieve the transaction's slots so they weren't affected.
>>  • Bug 796398 - Restrict accelerator keys to valid date range.
>>  • Bug 796409 - Incorrect Current Value for Stocks. Missed calculating 
>> the value in the register summary bar.
>>  • Bug 796423 - Cannot Input Chinese, seems does not work with other IME 
>> too. Toggles not in view with all rows selected weren't being redrawn.
>>  • Bug 796484 - csv import: iostream error. Unfortunately it turns out 
>> that we can't use filestreams because they can't take path arguments 
>> containing Unicode on Windows.
>>  • Bug 796527 - invalid currency on scheduled transactions.
>>  • Don't even check for price/exchange rate on template 
>> transactions, there's no point.
>>  • Check all split commodities are valid, abort transaction 
>> creation if not.
>>  • If the template transaction's currency isn't used by any of 
>> the splits set the new transaction's currency to the first-found currency if 
>> there is one, otherwise to the first-found commodity.
>>  • Bug 796537 - Transaction Report cannot sort by "num".
>> 

Re: [GNC] GnuCash 3.2 Released

[Stephen M. Butler]

Compiled and installed on Ubuntu 18.04.

When starting up it reports several duplicate report IDs.  Should I have
uninstalled 3.1 first?  I did these commands (with an empty mybuild):

cd mybuild

cmake ../gnucash-3.2

make

sudo make install


Stephen M Butler, PMP, PSM
stephen.m.butle...@gmail.com
kg...@arrl.net
253-350-0166
---
GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8

On 06/24/2018 08:40 PM, John Ralls wrote:
> The GnuCash development team announces GnuCash 3.2, the second release of the 
> 3.x stable release series.
>
> Changes
>
> Between 3.0 and 3.2, the following bugfixes were accomplished:
>
>   • Bug 787401 - Test Report System - Report Definition.
>   • Bug 794617 - Can't compile with -DWITH_GNUCASH=NO due to 
> scm-gnome-utils.
>   • Bug 795101 - Scroll Bar in Reconcile Window Floats in and covers the 
> check boxes.
>   • Bug 795247 - datepicker broken in Persian. GnuCash passes dates as 
> integer y/m/d without using locale-specific formats, so we need to strip out 
> 'E' and 'O' from the format when scanning dates or determining separators in 
> gnc-date. None of '-', 'E', or 'O' are supported by boost (and '-' causes 
> errors), so strip them out from formatters in gnc-datetime as well.
>   • Bug 795253 - Have problems input Chinese.
>   • Bug 795272 - QIF importer causes application crash if action is 
> invalid.
>   • Bug 795276 - Invalid date on price stops file from being parsed.
>   • Bug 795362 - Special variable "i" not parsed in function calls. Due 
> to balance tests with insane random values.
>   • Bug 795471 - Impossible to Edit Budget Unless Maximized.
>   • Bug 795519 - Credit card payment after reconciliation.
>   • Bug 795666 - Backslash '\' in Description field spoils CSV Import 
> without helpful error message.
>   • Bug 795831 - When read only threshold set, dates are silently 
> changed. Display a message box informing the user of the change.
>   • Bug 795944 - Cannot store change to Business Suppliers data.
>   • Bug 796079 - Repeatable Crash in Tax Report Options.
>   • Bug 796081 - Tax Schedule Report - An error occurred while running 
> the report.
>   • Bug 796083 - Reconcile Selection Doesn't Work Anymore.
>   • Bug 796117 - Connecting 3.1 to an existing mysql db drops all data. 
> Provide a backup recovery function that instead of dropping primaries and 
> restoring backups merges the primaries and backups. This should handle a 
> worst-case safe-save failure where the backup tables don't have a complete 
> set of rows for some reason.
>   • Bug 796256 - Main Window stays hidden when starting after closing 
> main window while minimized.
>   • Bug 796369 - Notes lost or perhaps just not displaying when using 
> SQLite backend. This bug caused data loss if you saved your SQLite3 database 
> to a different file or database. The problem is that in SQLite3 (though not 
> in MySQL or PgSQL) the subquery ((SELECT DISTINCT guid FROM transactions)) 
> (note the double parentheses) returns only the first guid in the subquery's 
> results. Some transactions are loaded by special queries and those queries 
> are also used to retrieve the transaction's slots so they weren't affected.
>   • Bug 796398 - Restrict accelerator keys to valid date range.
>   • Bug 796409 - Incorrect Current Value for Stocks. Missed calculating 
> the value in the register summary bar.
>   • Bug 796423 - Cannot Input Chinese, seems does not work with other IME 
> too. Toggles not in view with all rows selected weren't being redrawn.
>   • Bug 796484 - csv import: iostream error. Unfortunately it turns out 
> that we can't use filestreams because they can't take path arguments 
> containing Unicode on Windows.
>   • Bug 796527 - invalid currency on scheduled transactions.
>   • Don't even check for price/exchange rate on template 
> transactions, there's no point.
>   • Check all split commodities are valid, abort transaction 
> creation if not.
>   • If the template transaction's currency isn't used by any of 
> the splits set the new transaction's currency to the first-found currency if 
> there is one, otherwise to the first-found commodity.
>   • Bug 796537 - Transaction Report cannot sort by "num".
>   • Bug 796586 - QIF import incorrectly converts unicode characters from 
> UTF8 encoded file.
>   • Bug 796595 - QIF Import Select Account button to add a new account is 
> labled gnc-account-new but should be New.
>   • Bug 796600 - stock split cash-in-lieu income/asset labels backwards.
>   • Bug 796614 - Reconciliation report contains incorrect transactions.
>   • Bug 796638 - configuration not properly saved for CSV transactions 
> import form.
> The Following fixes and improvemts were not associated with bug reports:
>
>   • Transaction report improvements:
>   

[GNC] GnuCash 3.2 Released

[John Ralls]

The GnuCash development team announces GnuCash 3.2, the second release of the 
3.x stable release series.

Changes

Between 3.0 and 3.2, the following bugfixes were accomplished:

• Bug 787401 - Test Report System - Report Definition.
• Bug 794617 - Can't compile with -DWITH_GNUCASH=NO due to 
scm-gnome-utils.
• Bug 795101 - Scroll Bar in Reconcile Window Floats in and covers the 
check boxes.
• Bug 795247 - datepicker broken in Persian. GnuCash passes dates as 
integer y/m/d without using locale-specific formats, so we need to strip out 
'E' and 'O' from the format when scanning dates or determining separators in 
gnc-date. None of '-', 'E', or 'O' are supported by boost (and '-' causes 
errors), so strip them out from formatters in gnc-datetime as well.
• Bug 795253 - Have problems input Chinese.
• Bug 795272 - QIF importer causes application crash if action is 
invalid.
• Bug 795276 - Invalid date on price stops file from being parsed.
• Bug 795362 - Special variable "i" not parsed in function calls. Due 
to balance tests with insane random values.
• Bug 795471 - Impossible to Edit Budget Unless Maximized.
• Bug 795519 - Credit card payment after reconciliation.
• Bug 795666 - Backslash '\' in Description field spoils CSV Import 
without helpful error message.
• Bug 795831 - When read only threshold set, dates are silently 
changed. Display a message box informing the user of the change.
• Bug 795944 - Cannot store change to Business Suppliers data.
• Bug 796079 - Repeatable Crash in Tax Report Options.
• Bug 796081 - Tax Schedule Report - An error occurred while running 
the report.
• Bug 796083 - Reconcile Selection Doesn't Work Anymore.
• Bug 796117 - Connecting 3.1 to an existing mysql db drops all data. 
Provide a backup recovery function that instead of dropping primaries and 
restoring backups merges the primaries and backups. This should handle a 
worst-case safe-save failure where the backup tables don't have a complete set 
of rows for some reason.
• Bug 796256 - Main Window stays hidden when starting after closing 
main window while minimized.
• Bug 796369 - Notes lost or perhaps just not displaying when using 
SQLite backend. This bug caused data loss if you saved your SQLite3 database to 
a different file or database. The problem is that in SQLite3 (though not in 
MySQL or PgSQL) the subquery ((SELECT DISTINCT guid FROM transactions)) (note 
the double parentheses) returns only the first guid in the subquery's results. 
Some transactions are loaded by special queries and those queries are also used 
to retrieve the transaction's slots so they weren't affected.
• Bug 796398 - Restrict accelerator keys to valid date range.
• Bug 796409 - Incorrect Current Value for Stocks. Missed calculating 
the value in the register summary bar.
• Bug 796423 - Cannot Input Chinese, seems does not work with other IME 
too. Toggles not in view with all rows selected weren't being redrawn.
• Bug 796484 - csv import: iostream error. Unfortunately it turns out 
that we can't use filestreams because they can't take path arguments containing 
Unicode on Windows.
• Bug 796527 - invalid currency on scheduled transactions.
• Don't even check for price/exchange rate on template 
transactions, there's no point.
• Check all split commodities are valid, abort transaction 
creation if not.
• If the template transaction's currency isn't used by any of 
the splits set the new transaction's currency to the first-found currency if 
there is one, otherwise to the first-found commodity.
• Bug 796537 - Transaction Report cannot sort by "num".
• Bug 796586 - QIF import incorrectly converts unicode characters from 
UTF8 encoded file.
• Bug 796595 - QIF Import Select Account button to add a new account is 
labled gnc-account-new but should be New.
• Bug 796600 - stock split cash-in-lieu income/asset labels backwards.
• Bug 796614 - Reconciliation report contains incorrect transactions.
• Bug 796638 - configuration not properly saved for CSV transactions 
import form.
The Following fixes and improvemts were not associated with bug reports:

• Transaction report improvements:
• Performance: Do all filtering ops before sorting.
• Move the options summary before the subtotals table.
• New unit tests
• Enable computing averages in subtotal grid.
• Generate the subtotal grid only if the primary sort key 
enables subtotals.
• Fix subtotal grid to support multiple commodities.
• New filters.
• Much cleaning and refactoring of the internals.
• Cache the num-split-action book option to avoid thousands of KVP 
queries