On 10/21/2012 03:33 PM, Keith Daniels wrote: > > On 10/21/2012 02:50 PM, Timothy Pearson wrote: >>> Following the instructions for "For Precise [Ubuntu 12.04] LTS >>> (v3.5.13.1)" from: >>> >>> http://www.trinitydesktop.org/wiki/bin/view/Documentation/UbuntuBinaryInstallation. >>> >>> I got these "Failed to fetch" messages with "apt-get update": >>> ----------- >>> From: >>> http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu/dists/quantal/main/ >>> >>> source/Sources >>> binary-amd64/Packages >>> binary-i386/Packages >>> >>> Error: 404 Not Found >>> >>> From: >>> http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.13/ubuntu/dists/quantal/main >>> >>> /source/Sources >>> /binary-amd64/Packages >>> /binary-i386/Packages >>> >>> Error: 404 Not Found >>> ---------- >>> >>> I assume this is why I got so many "unmet dependencies" when I tried >>> "apt-get install" >> <snip> >> >> Why are you attempting to use Quantal repositories? Check your >> /etc/apt/sources.list file and ensure that "precise", not "quantal", is >> part of the four TDE lines. >> >> Tim >> > I added these, in my sources.list file, as the instructions said: > > deb > http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu precise > main > deb-src > http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/ubuntu precise > main > deb > http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.13/ubuntu > precise main > deb-src > http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.13/ubuntu > precise main > > And that is what produced the above problems/results. > > I too wondered about the Quantal issue, but assumed they would work, so > you did not need to change the names...? These 404 errors might not > make any difference (i.e. be ignored), when installing and have nothing > to do with the errors produced when I ran "apt-get install" . > > I have the list of "unmet dependencies" from "apt-get install", if you > want me to post them, about 20. > > Keith > The problem was apparently a Lubuntu problem or a fluke event. I tried apt-upgrade on an Ubuntu system and it ran without problems. Keith