Siduction Forum

Siduction Forum => Software - Support => Topic started by: clubex on 2013/11/09, 11:27:26

Title: Can't continue dist-upgrade
Post by: clubex on 2013/11/09, 11:27:26
Yesterday's seem to go OK but today all I get is the following:
apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
gcj-4.8-jre-headless : Depends: libgcj14 (= 4.8.2-2) but 4.8.2-1 is installed
E: Unmet dependencies. Try using -f.


A forced install just produces the unmet dependencies message. Also trying to purge libgcj14 bring up unmet dependencies for other packages eg gcj-4.8-jre-headless.

In short I cannot dist-upgrade until this issue is resolve.

Can anyone come to my rescue?





Title: Re: Can't continue dist-upgrade
Post by: melmarker on 2013/11/09, 11:48:24

2 Points:
* apt-get -f install isn't forced - it't a fix install
* For the dependencies - why do you uses gcj? Is there any reason to do so? In any case the solution is: Wait.
Title: Re: Can't continue dist-upgrade
Post by: Santa on 2013/11/10, 15:36:55
Quote from: clubex on 2013/11/09, 11:27:26
Yesterday's seem to go OK but today all I get is the following:
apt-get dist-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
You might want to run 'apt-get -f install' to correct these.
The following packages have unmet dependencies:
gcj-4.8-jre-headless : Depends: libgcj14 (= 4.8.2-2) but 4.8.2-1 is installed
E: Unmet dependencies. Try using -f.


A forced install just produces the unmet dependencies message. Also trying to purge libgcj14 bring up unmet dependencies for other packages eg gcj-4.8-jre-headless.

In short I cannot dist-upgrade until this issue is resolve.

Can anyone come to my rescue?


See: http://forum.siduction.org/index.php?topic=3982.0
I'm trying to fix this. The package in question (gcc-4.8) takes too much time to build, so it's going to take some time to fix this in siduction (if debian doesn't fix it earlier).