6 Nov
2012
6 Nov
'12
9:24 a.m.
Debian Squeeze i386, TDE3.5.12
Changed my sources list to include TDE v. 3.5.13
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-v3.5.13/debian
squeeze main
http://ppa.quickbuild.pearsoncomputing.net/trinity/trinity-builddeps-v3.5.1…
squeeze main
Apt-get update, apt-get ugrade : 31 upgraded, 0 newly installed, 0 to
remove and 246 not upgraded
apt-get dist-upgrade:26 upgraded, 2 newly installed, 248 to remove and 5
not upgraded
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/debian/
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
Buzulla: [kdelibs] startkde fails because of undefined symbol
_ZN7QObject18childrenListObjectEv seems related.
My guess is libqt3-mt fails to upgrade, not recognized as a higher
version, apt-get either remove most of
trinity or olds back the majority of packages.
Is there a upgrade path from 3.5.12 > 3.5.13.1? Instructions somewhere?
-- -- --
Peace,
Greg
6 Nov
6 Nov
1:53 p.m.
In article <201211060024.59517.gomadtroll(a)gci.net>et>,
Greg Madden <trinity-users(a)lists.pearsoncomputing.net> wrote:
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/debian/
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
--
"The Internet, a sort of ersatz counterfeit of real life"
-- Janet Street-Porter, BBC2, 19th March 1996
8:11 p.m.
New subject: [trinity-users] Re: possible to upgrade TDE3.5.12 > TDE 3.5.13.1?
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
4192
days inactive
4192
days old
2 comments
2 participants
participants (2)
-
Greg Madden -
Nick Leverton