10-15-2016, 08:23 AM
(10-15-2016, 02:43 AM)kflorek46 Wrote: Usually this would be a dependency conflict, where two programs or packages require the same package, except that the versions required conflict.Thanks for your feed back. I tried twice, now I am going to install a different version. This is the one I am going to try now. Again, I am a Linux newbie, so I am learning. debian-mate-jessie-20160701-lenny.raposo-longsleep-pine64-8GB
Programs often consist of pieces some of which may be in other packages, which is called a dependency. These packages may in turn require other packages, and so on. It is difficult to have tens of thousands of packages available without having any of them conflict with any other.
There are packages where all they do is create dependencies, and things like ubuntu-mate-desktop typically are that. That is how one package ends up needing 1000 other packages.
But since you are installing Ubuntu from scratch, it is not likely that you have any packages installed that would create a conflict with ubuntu-mate-desktop. In addition, this same installing procedure is known to have worked on the same hardware.
One possibility is that Ubuntu has made a change which has created a conflict.
Another possibility is that the repositories are in the midst of being updated. A large amount of updating occurs when Ubuntu issues a newer version, which they did October 13, 2016. (I updated my regular computer to this version (16.10 or Yakkety), and it went fine (or just about.)) The repositories for ARM CPUs have to be entirely separated from Intel style CPUs, because the CPUs do not implement identical computer instructions. (Linux is implemented in computer languages that do not depend on base-level CPU instructions, and is then converted for different CPUs.) So it may be that some repositories are not completely updated or in sync.
You could try
sudo apt-get update
sudo apt-get install libqt5libqgtk2
and see what happens. If it succeeds, then the script to install Mate may be able to go on. If not, then it may be this package is not present in the repositories.
It may be that the Mate installation script ignores errors, and the data for the repositories has simply not been updated consistently, so trying the script again may work, if everything updates fully the next time.
When I try updating with apt-get, I do get some 404 (= not found) errors every time, but I am not sure that it hasn't always been that way.
Since I already have Mate installed on my Pine64, I cannot check to see if I get the same error you do, because it just says it is already installed.