On 5-Jan-10, at 9:18 AM, Adrian Perez wrote:
Seem like you did a "remove" instead of "purge" for libswt-gtk-3.4-
java.
Although doing the same in my system gives the proper results, so I'm
kind of lost about it.
Try this:
`sudo aptitude purge libswt-gtk-3.4-java && sudo aptitude install
libswt-gtk-3.5-java`
Sadly, can't still reproduce.
With that procedure I get the symlink installed correctly. In fact,
I'm finding it difficult to reproduce by manipulating the libswt
packages directly.
What does trigger it, however, is upgrading azureus from 4.3.0.0-1
(which depends on 3.4) to 4.3.0.6-1 (which depends on 3.5). Doing
this, aptitude produces the following:
Selecting previously deselected package libswt-gtk-3.5-jni.
(Reading database ... 118846 files and directories currently installed.)
Unpacking libswt-gtk-3.5-jni (from .../libswt-gtk-3.5-
jni_3.5.1-2_i386.deb) ...
Selecting previously deselected package libswt-gtk-3.5-java.
Unpacking libswt-gtk-3.5-java (from .../libswt-gtk-3.5-
java_3.5.1-2_i386.deb) ...
Preparing to replace azureus 4.3.0.0-1 (using .../
azureus_4.3.0.6-1_all.deb) ...
Unpacking replacement azureus ...
Processing triggers for man-db ...
(Reading database ... 118861 files and directories currently installed.)
Removing libswt-gtk-3.4-java ...
Removing libswt-gtk-3.4-jni ...
Setting up libswt-gtk-3.5-jni (3.5.1-2) ...
Setting up libswt-gtk-3.5-java (3.5.1-2) ...
Setting up azureus (4.3.0.6-1) ...
So it seems that aptitude unpacks 3.5, removes 3.4, then configures
3.5. This should explain why the symlink disappears.
--
Tony 'Nicoya' Mantler - Master of Code-fu
-- [email protected] -- http://www.ubb.ca/ --
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
