The first error was because you were not in the same directory as the .deb 
files. You could still run the command in that case, but then you’d have to 
specify the exact location of each .deb. It is much easier to just be in the 
same directory.

I’m not sure why those files had architecture specifications on them (amd64) as 
I don’t think GC supports 32 bit any longer. (I could be mistaken)

Anyhow, those three notes were simply telling you it was going to install the 
packages under different names. (more generic ones) This *might* have something 
to do with the way they were packaged.

Regardless, the result of your last two commands tell you the following:

which gnucash

means the executable is in the standard location `/usr/bin`. That is, you don’t 
need to specify to the OS where to find it. It just launches it.

sudo dpkg -l | grep gnucash

reports that you have successfully installed 3.5 and there are no other 
versions lying around. (though I do see gnucash-docs is at version 3.4, you can 
remove that and manually download the 3.5 versions if you like, but I don’t 
think the docs are packaged as gnucash-docs accordingly, you’ll just have 2 pdf 
files for reference)

Regards,
Adrien

> On Apr 19, 2019, at 2:01 PM, Lawrence Joy <lawrence_...@yahoo.com> wrote:
> 
> A synopsis of what I did to get V3.5 loaded and working on my Ubuntu 18.04.1 
> LTS OS. The files:
> MyNamed.gnucash
> MyNamed.gnucash.20190304113239.log
> MyNamed.gnucash.20190304124553.log
> MyNamed.gnuchas.20190304124553.gnucash
> are in /home/larry and gnucash-3.5 is in /home/larry/Downloads.
> 
> I downloaded the three files by Stephen Butler off of Google Drive.--Thanks 
> for that information as I had not seen it any other place before. Those three 
> files were put in /home/larry/Downloads. Per instructions I did 'sudo apt 
> install ./*_3.5_*.deb' in my /home/larry directory as that was where my 
> gnucash files were. It came back with:
> "Reading package lists... Done"
> "E: Unsupported file ./*_3.5_*.deb given on commandline"
> 
> I then went to /home/larry/Downloads directory and entered the same thing. It 
> came back with
> "Reading package lists... Done"
> "Building dependency tree"
> "Reading state information... Done"
> "Note, selecting 'gnucash' instead of './gnucash_3.5_amd64.deb"
> "Note, selecting 'gnucash-common' instead of './gnucash-common_3.5_all.deb"
> "Note, selecting 'python3-gnucash' instead of 
> './python3-gnucash_3.5_amd64.deb"
> "Do you want to continue? [Y/n]" The three notes bothered me but I went ahead 
> and answered Y.
> It took about an hour and a half to do the download/programming.
> 
> Now when I push the Super Key and then push G the gnucash icon shows up, 
> which I click on, and when I check Help>About it says its GnuCash V3.5. 
> Hurray!
> 
> On the terminal I run 'which gnucash' and get back "usr/bin/gnucash".
> On the terminal I also run 'sudo dpkg -l | grep gnucash' and get back
> ii  gnucash                                    1:3.5                          
>                    amd64        personal and small-business 
> financial-accounting software
> ii  gnucash-common                             1:3.5                          
>                    all          common files for the financial-accounting 
> software Gnucash
> ii  gnucash-docs                               3.4-0+bionic~ppa1              
>                    all          Documentation for gnucash, a personal finance 
> tracking program
> ii  python3-gnucash                            1:3.5                          
>                    amd64        Gnucash interface for Python
> 
> Everything seems to be okay now. Thanks for all your help.
> --Larry


_______________________________________________
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.

Reply via email to