Re: [trinity-users] Installing Trinity 3.5.12 on Squeeze - semi-SOLVED

On Monday 23 April 2012 20:21:40 Greg Madden wrote: 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.