6 Nov
2012
6 Nov
'12
12:11 p.m.
On Tuesday 06 November 2012 04:53:42 you wrote:
In article
<201211060024.59517.gomadtroll(a)gci.net>et>,
Greg Madden <trinity-users(a)lists.pearsoncomputing.net> wrote:
Thank you, indeed apt pinning in the way.
--
Peace,
Greg
root@trinity:~# apt-cache policy libqt3-mt
libqt3-mt:
Installed: 3:3.3.8b-7+b1
Candidate: 3:3.3.8b-7+b1
Version table:
3:3.3.8d-1ubuntu0+ax1~squeeze 0
500
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/d
ebian/ squeeze/main amd64 Packages
*** 3:3.3.8b-7+b1 0
990 http://192.168.0.4/debian/ squeeze/main amd64 Packages
100 /var/lib/dpkg/status
You seem to have a private squeeze repository there on 192.168.0.4,
which is apt-pinned via /etc/apt/preferences to 3.3.8b. The
specialness of priorities over 900 leads me to guess that you might
have had to do a downgrade at some time and this situation may be
left over from that.
You'll need to downgrade the priority of that repo to no higher than
500, perhaps by removing it entirely from /etc/apt/preferences,
either that or increase the Trinity repo's priority to match.
I recently upgraded 3.5.12 directly to 3.5.13.1 on squeeze and it all
went very cleanly, so hopefully once you have done that you should be
able to upgrade the rest of the way.
Nick