General Support - "*Multicd*" .. apt-error [fix] etorix - 26.05.2006, 07:57 Uhr Titel: "*Multicd*" .. apt-error [fix]
for dpkg-multicd_0.20_all.deb error , in dist-upgrade:
do
'apt-get -f install'
if no fix, then
'dpkg --purge dpkg-multicd'
Crust - 26.05.2006, 19:11 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
I did it by:
apt-get -f install
apt-get remove --purge dpkg-multicd
apt-get install dpkg-multicd
craigevil - 26.05.2006, 23:55 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
Just curious , but itsn't it a bad idea to "force" things to install?
I still have 54 updates that aren't updated because of scare looking bugs and multicd is one of them.
jesseman - 27.05.2006, 00:44 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
"apt-get -f install" is the fix option, not the force option.
stryder - 27.05.2006, 03:32 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
Like Crust, needed remove, then install.
etorix - 27.05.2006, 13:20 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
'dpkg --purge xxxx'
works independently of a possibly confused apt-sub-system
apt-get remove is pretty much the same end-result ..
but wont work if apt itself is stalled
DeepDayze - 27.05.2006, 15:43 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
what about using dpkg -i --force-overwrite to force the file to be replaced?
etorix - 27.05.2006, 17:20 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
-force-overwrite is a kludge
to be avoided at all costs
DeepDayze - 27.05.2006, 17:42 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
i had to use the --force-overwrite before when removing the offending package would result in the removal of numerous dependent packages.
slh - 27.05.2006, 18:37 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
--force is the most stupid thing you could ever do with apt (--force-confnew, --force-confmiss might sometimes be different, but these 2 are the only potential excemptions), period.
jackiebrown - 28.05.2006, 03:05 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
When you do a force overwrite you are changing the ownership of that file to a new deb.
Say I created a deb named jackie.deb that wanted to take ownership of X by modifying it. Apt would and dpkg would rightly complain. If you give --force-overwrite you have just change the ownership of X from xserver-common to jackie.deb.
So now as far as dpkg is concerned, my package is responsible for usr/X11R6/bin/X.
Now obviously I have just violated debian policy and you won't see this in stable. Now I have been informed and fix my package and never touch X again. It doesn't matter, you have already given it to me.
Now you decide jackie.deb sucks (I did write it after all) and you choose to remove it. X will be delete along with the other files in my package. And you will be left wondering why startx is complaining about not finding X when you have xserver-common installed.
It's a short term solution anyways, because next upgrade to xserver-common will have you in the same situation.
DeepDayze - 28.05.2006, 16:46 Uhr Titel: RE: "*Multicd*" .. apt-error [fix]
ahh so the force-oveerwrite will move the file to another package.