apt-get problem (Problem parsing dependency Depends)
Hi,
I have this report from the apt-get update; Code:
E: Problem parsing dependency Depends However... I am documenting it here this time, for posterity, as it has happened more than once. What solutions do you suggest, please? My thanks in advance. |
I think we would have to see your sources.list, at least, to have a clue.
|
Hi,
Sure thing. Here it is... Code:
# /var/lib/dpkg/status I am presently ploughing my way through it. The problem, in this instance, started right after installing Chromium web browser, via synaptic (because Google keeps complaining that Iceweasel 3.5.16, which I normally use, is "outdated"!!). By the way, this is on my 64 bit rig, which runs standard "Squeeze" AMD64. Thanks. EDIT: So, tell me if I have made a mess of things. In /var/lib/dpkg, there was a file; status-old I backed up my original status file (status-faulty) and renamed status-old to status. Then, I changed my sources list to my nearest mirrors - Mexico. My new sources list; Code:
# deb cdrom:[Debian GNU/Linux 6.0.0 _Squeeze_ - Official Snapshot amd64 LIVE/INSTALL Binary 20110206-06:35]/ squeeze main When the process gets to the pre-configure part, it starts identifying the lines in another file that present errors. That file is; /var/lib/dpkg/available This is now familiar, as it was the same thing the last time. There are character errors in the file (eg; "daem/n" instead of "daemon"), and it is a case now of locating these and correcting them, unless anyone knows a better way? Anyway, at least I have it documented here this time... Thanks in advance! |
You should not be getting these problems and you should certainly not be messing around in /var/lib/dpkg/ as those files are irreplaceable. If you insist on messing about in there make a backup of the whole directory first.
I would suggest you back up your data and reinstall. A corrupt package database is going to be a nightmare in the long run. Be careful of what you install from outside of the repos in future. |
Yes, that sounds like a real good idea. I do not like reinstalling on general principles but it is the best route for some problems.
One thing, and I will get jumped on for this, that I would recommend is quit using Update Mangler. I don't like it because I have had problems with it. Use Synaptic to do your update/upgrade chores if you want a gui. Apt-get or aptitude is even a better idea. |
Hi,
Quote:
1. I do not "mess around" with any system folders or files while the system is up and running in good order. My prerogative is the old adage; "if it ain't broke, don't fix it". The problem described has occurred on the occasions it has after perfectly legitimate use of apt-get, Synaptic Package Manager or Update Manager, using only the Debian repositories. The Chromium Web Browser I installed was from these repo's, not the one that pops up on Google saying "install Chrome". I am clear on that. 2. Here is a list of programs installed from source, none of which ever caused any problems subsequently; Code::Blocks, Allegro 5.0.4, Stellarium, and from separate downloadable debs, Google Earth and Skype, for AMD64. Any dependencies these applications required were installed by apt-get. 3. After restoring the status-old file as status (with the respective backing up, as always - I am relatively new to Linux but not to computers or OS's by a long shot, say since 1986) the terminal itself points me to the errors in the available file (during the upgrade phase), even identifying the line numbers where the error is, and what to look for. I assume this information is provided in order to give the problem the required attention(?). It is all working fine again, now. I am loathe to reinstall the whole OS, really, and keep that solution as a last resort, or else I am not learning anything about the "new OS" maintenance. If I post the problem here it is with the express purpose acquiring the knowledge (if anyone is kind enough to impart it, of course) of any specific procedures or tools available that I may not be aware of. Seems there's none for this particular one. Now, what might be the root causes of the dpkg file corruptions that occur from time to time? Is it possible that sporadic interruptions to the internet connection could be causing the file to corrupt during the apt-get update sequence? In any case; all is well. Thank you! |
Quote:
|
what ended up being the root cause of this issue? I have a Debian Squeeze box that doesnt even run a gui (doesnt even have any installed, no less), and i came up today with a disturbingly similar error to yours, feeblebrain.
Code:
Reading package lists... Error! |
and i raise my hands to the sky and thank google for all the answers i could ask for. after deleting the status file and replacing it with status-old, i ended up getting the following:
Code:
Segmentation faultsts... 21% Code:
sudo rm /var/cache/apt/*.bin |
Quote:
First, dpkg has some neat options for fixing some problems, especially those with the "available" file. Here's the link... debianadmin ...of particular use is the... Code:
dpkg --clear-avail Code:
rm /var/lib/apt/lists/* --force Again, very sorry for the necropost... |
All times are GMT -5. The time now is 08:06 AM. |