On Monday 23 April 2012 22:10:20 Lisi wrote:

On Monday 23 April 2012 20:21:40 Greg Madden wrote:

...

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.

Thanks! I'll certainly comment out the src lines - as you say, I do not really need them, and can uncomment them if I ever do..

But the two squeeze updates are not in fact the same thing. deb http://security.debian.org/ squeeze/updates main is, as it says, security, so is necessary.

deb http://mirror.ox.ac.uk/debian/ squeeze-updates main is not security - there is no mention of security. It is the replacement for volatile.

Still, I could certainly comment both out temporarily.

I am still baffled as to why the same procedure worked a week or two ago and doesn't work now!!!

Anyway, now to try your suggestions. Thanks for them.

I commented out virtually everything, and got exactly the same result.

I am wondering whether I should try 3.5.13 with Slavek's patches, but that is really the result of desperation!! I am a little worried because this is not my computer, and I have never tried to use patches before.

It occurs to me to wonder whether a possible explanation is that I had tried to install 3.5.13 before and failed because of problems with the repositories. I simply don't remember how far I got, if I got anywhere.

So I think I'll try that next, before I resort to tearing my hair out. :-(

Thanks again, Lisi

On Monday 23 April 2012 22:22:11 leee wrote:

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/de bi an squeeze main deb-src http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps/de bi 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.

Thanks, Lee. I always find oyur copmments very helpful.

Trying to install 3.5.13 is going fine, so that was obviously the problem. All I have to do now, is find out how to install Slavek's patches. :-(

Lisi

On Monday 23 April 2012 20:21:40 Greg Madden wrote:

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.

Thanks, Greg. You appear to have delivered a resuscitating electric shock to my brain. At least I now know what was going wrong.

All I have to do now is sort out 3.5.13. If I can't, now I know what the problem was, I can always reinstall.

Lisi

On Tuesday 24 April 2012 00:33:40 Greg Madden wrote:

On Monday 23 April 2012 1:38:29 pm Lisi wrote:

...

On Monday 23 April 2012 20:21:40 Greg Madden wrote:

...

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.

Thanks, Greg. You appear to have delivered a resuscitating electric shock to my brain. At least I now know what was going wrong.

All I have to do now is sort out 3.5.13. If I can't, now I know what the problem was, I can always reinstall.

Lisi

I used this line to get slavek's packages. The package manager of your choice will automagically use his packages

'deb http://ppa.quickbuild.pearsoncomputing.net/slavek-banko/axis/ubuntu squeeze main'

Thanks, Greg and Slavek!

I have the patches installed. One minor problem taht I would like ot sort out is that for some reason the login has changwd from kdm, which I chose at Trinity installation, has been changed back to gdm. :-/

Lisi

On Tuesday 24 April 2012 09:26:34 leee wrote:

On Tuesday 24 April 2012 08:49:08 Lisi wrote:

...

On Tuesday 24 April 2012 00:33:40 Greg Madden wrote:

...

On Monday 23 April 2012 1:38:29 pm Lisi wrote:

...

On Monday 23 April 2012 20:21:40 Greg Madden wrote:

...

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.

Thanks, Greg. You appear to have delivered a resuscitating electric shock to my brain. At least I now know what was going wrong.

All I have to do now is sort out 3.5.13. If I can't, now I know what the problem was, I can always reinstall.

Lisi

I used this line to get slavek's packages. The package manager of your choice will automagically use his packages

'deb http://ppa.quickbuild.pearsoncomputing.net/slavek-banko/axis/ubuntu squeeze main'

Thanks, Greg and Slavek!

I have the patches installed. One minor problem taht I would like ot sort out is that for some reason the login has changwd from kdm, which I chose at Trinity installation, has been changed back to gdm. :-/

Lisi

Either choose kdm in alternatives or uninstall gdm.

If you've got galternative installed (a gnome package) you can use that but otherwise I think you'll have to use update-alternatives, which is a bit cryptic and not so easy to use.

Thanks, Lee.

Lisi