Posted by: Anonymous Coward
on October 22, 2005 09:55 PM
Whatever package is complaining, and whatever dependency it's complaining about,
# apt-get --purge remove (package names)
This wipes out the conflicted packages and all their config info - save any files outside of the system directories if you might need to restore a complicated bit of config.
For particularly broken situations, package names might be a dozen packagess.
Assuming you already -did- an update, if not, do one, it's back to the easy old, # apt-get install for the package that you needed.
Usually, this will install the package that you needed along with several packages that you just uninstalled and one that you never had before that satisfies the dependency correctly.
Typically, when apt-get fails, it's because of replaces- and provides- kinds of issues. Straight up dependencies are generally right. I've always been able to resolve these things by removing and reinstalling the dependency packages - usually just the ones mentioned in errors, but sometimes the whole depends list for a package.
With software outside of the debian project, I'll try to install their<nobr> <wbr></nobr>.deb, but if that fails (or isn't up to date in the first place) I'll just build from tarball with a<nobr> <wbr></nobr>/usr/local prefix. (Which often involves apt-get install somethinglib-dev, but so it goes.)
Learn about Linux
Download Linux
Get Linux help
No, it's easier than that usually...
Posted by: Anonymous Coward on October 22, 2005 09:55 PM# apt-get --purge remove (package names)
This wipes out the conflicted packages and all their config info - save any files outside of the system directories if you might need to restore a complicated bit of config.
For particularly broken situations, package names might be a dozen packagess.
Assuming you already -did- an update, if not, do one, it's back to the easy old,
# apt-get install
for the package that you needed.
Usually, this will install the package that you needed along with several packages that you just uninstalled and one that you never had before that satisfies the dependency correctly.
Typically, when apt-get fails, it's because of replaces- and provides- kinds of issues. Straight up dependencies are generally right. I've always been able to resolve these things by removing and reinstalling the dependency packages - usually just the ones mentioned in errors, but sometimes the whole depends list for a package.
With software outside of the debian project, I'll try to install their<nobr> <wbr></nobr>.deb, but if that fails (or isn't up to date in the first place) I'll just build from tarball with a<nobr> <wbr></nobr>/usr/local prefix. (Which often involves apt-get install somethinglib-dev, but so it goes.)
#