Re: [GNC] Up grade from 2.6.xx to 3.1

Yes, I ran the autoremove I then tried the rm commands and it seems the directories are already gone after the autoremove. wheris gnucash returned emtpy. Thanks, Dennis On Fri, May 11, 2018 at 5:34 PM, Adrien Monteleone < adrien.montele...@lusfiber.net> wrote: > Nope. > > Just: > > sudo

Re: [GNC] Up grade from 2.6.xx to 3.1

Nope. Just: sudo apt autoremove will do. Then run the rm commands. After that, there should be nothing left of gnucash’s prior installation. Regards, Adrien > On May 11, 2018, at 4:32 PM, Dennis Powless wrote: > > Ok > Do I have to include anymore information or just

Re: [GNC] Up grade from 2.6.xx to 3.1

Ok Do I have to include anymore information or just type sudo apt autoremove Yes, those directories contain files. D On Fri, May 11, 2018 at 5:07 PM, Adrien Monteleone < adrien.montele...@lusfiber.net> wrote: > You can run the dpkg command. I don’t suspect it will remove anything > extra. If

Re: [GNC] Up grade from 2.6.xx to 3.1

You can run the dpkg command. I don’t suspect it will remove anything extra. If not, then you can proceed with the rm commands. You might want to take a look at those directories. It’s possible they are now empty, but the directories were not removed. (It seems /etc/gnucash is gone now however)

Re: [GNC] Up grade from 2.6.xx to 3.1

This was the output. dennis@dennis-XPS-8500:~$ sudo apt list --installed | grep gnucash [sudo] password for dennis: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. gnucash-common/xenial-getdeb,xenial-getdeb,now 1:2.6.17-1~getdeb1 all

Re: [GNC] Up grade from 2.6.xx to 3.1

Dennis, sudo apt list --installed | grep gnucash will give you a list of any gnucash packages installed with the Ubuntu package manager. If you don’t see gnucash listed, you built it from source. (I still see gnucash-common-2.6.12 when I run that command because I had that version from the

Re: [GNC] Up grade from 2.6.xx to 3.1

Dennis,  If you use the --purge switch with apt remove i.e. sudo apt-get remove --purge gnucash  it should remove those configuration files in /usr/etc and /usr/include and /usr/share files as well. A post on AskUbuntu  indicates that the --purge switch does not remove configuration and data files

Re: [GNC] Up grade from 2.6.xx to 3.1

Dennis, The instructions for v3.1 should work. The only problem I had when i compiled 2.6.21 after upgrading to 3.1 was that I had installed guile 2.2.3 and v 2.6.21 looks for guile-1.8 or guile-2.0. It is possible to have several versions of the guile libraries and headers installed as they

Re: [GNC] Up grade from 2.6.xx to 3.1

I read up on uninstalling programs and about the - -purge command but didn’t know how to combine it with the dbkg command. To be honest, I don’t remember how I installed it gnucash on that machine. Sent from my iPhone > On May 10, 2018, at 8:30 PM, David Cousens

Re: [GNC] Up grade from 2.6.xx to 3.1

Dennis, As dpkg tells you, only the config files are on the system. Those are not removed by a ‘remove’ command, you need to purge as the command response advises. Try ONE of the following: (as far as I’m aware, these three produce identical results in this case) sudo apt purge gnucash sudo

Re: [GNC] Up grade from 2.6.xx to 3.1

I was able to use the remove feature in Ubuntu Software. however after I ran that, I did the whereis gnucash and this is the output. dennis@dennis-XPS-8500:~$ whereis gnucash gnucash: /etc/gnucash /usr/include/gnucash /usr/share/gnucash I then did sudo apt-get remove gnucash repeated

Re: [GNC] Up grade from 2.6.xx to 3.1

> On May 9, 2018, at 3:19 PM, DaveC49 wrote: > > Dennis > > It is probbaly a good idea to uninstall the previous build of 2.6.x before > upgrading. With the changes between 2.6 and 3.1 there may have been changes > in the libraries/library names such that some older

Re: [GNC] Up grade from 2.6.xx to 3.1

Dennis It is probbaly a good idea to uninstall the previous build of 2.6.x before upgrading. With the changes between 2.6 and 3.1 there may have been changes in the libraries/library names such that some older libraries may not necessarilybe overwritten. How to remove it will depend upon how you