apt-get returns unmet dependencies error with python2.3-sip4-qt3 package
not to long ago i wanted to configure the AIO Super Karamba widget, so i needed PyQt
no problem, im running debian, so i do an apt-cache search and get all teh relevant packages, well now im having this issue here, which is disabling me from grabbing anything at all with apt Leviathan:/home/ron1n# apt-get install naim Reading package lists... Done Building dependency tree... Done You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies. python2.3-qt3: Depends: python2.3-sip4-qt3 (>= 4.3) but it is not going to be installed Depends: python2.3-sip4-qt3 (< 4.4) but it is not going to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). so i follow the recommendation Leviathan:/home/ron1n# apt-get -f install Reading package lists... Done Building dependency tree... Done Correcting dependencies...Done The following extra packages will be installed: python2.3-sip4-qt3 The following NEW packages will be installed python2.3-sip4-qt3 0 upgraded, 1 newly installed, 0 to remove and 26 not upgraded. 2 not fully installed or removed. Need to get 0B/68.7kB of archives. After unpacking 176kB of additional disk space will be used. Do you want to continue [Y/n]? y Xlib: connection to ":0.0" refused by server Xlib: No protocol specified dpkg-preconfigure: cannot connect to X server :0.0 debconf: unable to initialize frontend: Kde debconf: (DISPLAY problem?) debconf: falling back to frontend: Dialog (Reading database ... 93713 files and directories currently installed.) Unpacking python2.3-sip4-qt3 (from .../python2.3-sip4-qt3_4.3.1-1_i386.deb) ... dpkg: error processing /var/cache/apt/archives/python2.3-sip4-qt3_4.3.1-1_i386.deb (--unpack): trying to overwrite `/usr/lib/python2.3/site-packages/sipconfig.py', which is also in package python2.3-sip-qt3 Errors were encountered while processing: /var/cache/apt/archives/python2.3-sip4-qt3_4.3.1-1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) i have attempted to apt-get --purge remove the package, dpkg -r --force-remove-reinstreq python2.3-sip4-qt3 the package, and dpkg --purge remove it, they all tell me that the package isnt installed so i resort to one last final option, i see teh line /var/cache/apt/archives/python2.3-sip4-qt3_4.3.1-1_i386.deb and leads me to beleive that if i run apt-get clean it will remedy the issue, but find out that it doesnt im all out of ideas, if u can help please do |
When I get error messages like that, I just plain cheat. From the lines you posted, the conflict is over
/usr/lib/python2.3/site-packages/sipconfig.py [EDIT] That is, two different packages have their own copies of that file, so apt will not install one of them. [/EDIT] So I would just move that to /usr/lib/python2.3/site-packages/sipconfig.py.old And try the installation again. The installation will probably succeed and you should be able to resume using apt normally. The downside is, if two packages use /usr/lib/python2.3/site-packages/sipconfig.py, it's possible that one won't work correctly. You may be able to find more information about the problem on the Debian mailing lists - maybe with a fix. |
Would you by any chance be able to tell me the app that will be crippled?
i have oython2.3 and python2.4 both installed on this system, could that be the issue? |
You won't cripple any packages. You only need one of each file. If dpkg complains that it won't install a package because one of the files in the package already exists on the system, you do:
mv file file.old Then dpkg will install the file it wouldn't install before, which is the same file you moved to file.old. If something turns out to not work you do: mv file.old file and put the old file back. |
Quote:
In this particular case, I think you're right that it won't be a problem. I would bet sipconfig.py is identical between the two packages. |
I meant to say the exact same name and totally different contents.
|
All times are GMT -5. The time now is 09:12 AM. |