On Monday 23 April 2012 20:21:40 Greg Madden wrote:
On Monday 23 April 2012 9:03:56 am Lisi wrote:
Hello, all!
I am trying to install Trinity 3.5.12 on Squeeze, with LXDE already
installed, (sources.list below).
Having edited my sources.list, I then:
# apt-key adv --keyserver
keyserver.quickbuild.pearsoncomputing.net
--recv-keys 2B8638D0 # aptitude update
# aptitude install desktop-base-trinity kde-trinity
I got a long list of unsatisfied dependencies and a suggested resolution.
I tried, as I usually do, to see what was unresolved and what I wanted to
do about it, but this proved so difficult in LXDE's terminal that I
finally decided to install whatever it would install, and take it from
there.
It installed nothing. (Or, as it put it 0.)
I did exactly this a couple of weeks ago on another computer, and ended
up with Trinity 3.5.12 up and running. Can anyone spot what I have done
wrong this time?
To make matters worse, I have to get this done by tomorrow. :-(
Thanks.
Lisi
<quote>
#
# deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 NETINST
Binary-1 20110205-14:34]/ squeeze main
#deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official i386 NETINST
Binary-1 20110205-14:34]/ squeeze main
deb
http://mirror.ox.ac.uk/debian/ squeeze main
deb-src
http://mirror.ox.ac.uk/debian/ squeeze main
deb
http://security.debian.org/ squeeze/updates main
deb-src
http://security.debian.org/ squeeze/updates main
deb
http://mirror.ox.ac.uk/debian/ squeeze-updates main
deb-src
http://mirror.ox.ac.uk/debian/ squeeze-updates main
deb
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/debian
squeeze main
deb-src
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity/debian
squeeze main
deb
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps/debi
an squeeze main
deb-src
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps/debi
an squeeze main
</quote>
I would trim your sources list, do you need 'deb-src' entries ? You also
have two security entries, i use the ~sqeeze/updates one. Sometimes a when
a sources entry fails to connect you can get missing packages/depends.
I don't think that having too many apt source entries is the issue; I have
even more repo entries than Lisi. And neither would a package manager simply
fail silently, leaving an unmet dependency because it can't find a repo
included in the apt sources; it'll say that it can't find that repo and
prompt you to fix the problem (we're not on windows anymore, where it's
normal for things to silently fail for unknowable and mysterious reasons).
I've had similar problems installing 3.5.12 on squeeze recently too, and I've
had to mess about manually satisfying a few fundamental dependencies, mixing
packages from lenny and squeeze to get 3.5.12 running on squeeze.
I just had a look to see exactly which version of the trinity packages that
[...]trinity/debian squeeze pointed to and they seem to be version 3.5.12 but
I seem to recall that, at one point, after 3.5.13 was released, it used to
point to the 3.5.13 packages. Also, when 3.5.13 was released, the 3.5.12
repo seemed to have been rebuilt for lenny and not squeeze.
I suspect therefore that the current default 'squeeze' repo has been switched
back to 3.5.12, because of the problems many of us experienced with 3.5.13,
but because it seems to have been rebuilt for lenny, after 3.5.13 was
released, it now contains dependencies from lenny which will be unmet in
squeeze.
Perhaps Tim or one of the other devs knows exactly what has happened but I
don't think there's a quick fix for this; I think that for a painless 3.5.12
install on squeeze all the 3.5.12 debs would have to built against the
current squeeze.
LeeE