Author Topic: [SOLVED] Synaptic DB corrupt: The dreaded E: error message.  (Read 1961 times)

Offline CJ

  • Sr. Member
  • ****
  • Posts: 454
Re: Synaptic DB corrupt: The dreaded E: error message.
« Reply #30 on: October 01, 2010, 04:17:53 PM »
Ok, done that, basically the same thing, i.e. no difference, sadly.

Code: [Select]
# rpm -q libbinutils2
libbinutils2-2.19.51.0.2-3pclos2010
libbinutils2-2.19.51.0.2-3pclos2010

CJ

Offline Texstar

  • Administrator
  • Super Villain
  • *****
  • Posts: 12536
Re: Synaptic DB corrupt: The dreaded E: error message.
« Reply #31 on: October 01, 2010, 04:39:40 PM »
Ok, done that, basically the same thing, i.e. no difference, sadly.

Code: [Select]
# rpm -q libbinutils2
libbinutils2-2.19.51.0.2-3pclos2010
libbinutils2-2.19.51.0.2-3pclos2010

CJ


run dupeclean in the terminal in su root mode again.

then try rpm -e --justdb libbinutils2

then apt-get install libbinutils2


Thanks to everyone who donates. You keep the servers running.

Offline CJ

  • Sr. Member
  • ****
  • Posts: 454
Re: Synaptic DB corrupt: The dreaded E: error message.
« Reply #32 on: October 01, 2010, 05:05:09 PM »
Same same, I am afraid:

Code: [Select]
# dupeclean
error: "libbinutils2-2.19.51.0.2-3pclos2010" specifies multiple packages
The following packages were removed: libbinutils2-2.19.51.0.2-3pclos2010
[root@localhost cj]# rpm -e --justdb libbinutils2
error: "libbinutils2" specifies multiple packages
[root@localhost cj]# apt-get install libbinutils2
Reading Package Lists... Done
Building Dependency Tree... Done
Selecting libbinutils2#2.19.51.0.2-3pclos2010 for 'libbinutils2'
Reinstallation of libbinutils2#2.19.51.0.2-3pclos2010 is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 0 removed and 0 not upgraded.
W: There are multiple versions of "libbinutils2" in your system.

This package won't be cleanly updated, unless you leave
only one version. To leave multiple versions installed,
you may remove that warning by setting the following
option in your configuration file:

RPM::Allow-Duplicated { "^libbinutils2$"; };

To disable these warnings completely set:

RPM::Allow-Duplicated-Warning "false";

W: You may want to run apt-get update to correct these problems
[root@localhost cj]# rpm -q libbinutils2
libbinutils2-2.19.51.0.2-3pclos2010
libbinutils2-2.19.51.0.2-3pclos2010

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 4001
Re: Synaptic DB corrupt: The dreaded E: error message.
« Reply #33 on: October 03, 2010, 04:53:41 AM »
Try:
Code: [Select]
rpm -e --nodeps --allmatches --justdb libbinutils2
rpm -q libbinutils2

Please let us know what it shows now.
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline CJ

  • Sr. Member
  • ****
  • Posts: 454
Re: Synaptic DB corrupt: The dreaded E: error message.
« Reply #34 on: October 03, 2010, 12:27:04 PM »
Try:
Code: [Select]
rpm -e --nodeps --allmatches --justdb libbinutils2
rpm -q libbinutils2
Please let us know what it shows now.

Code: [Select]
# rpm -q libbinutils2
package libbinutils2 is not installed

So... it went through!
On opening Synaptic now, it complains about two broken packages... I bet I know which two they are.
I am holding on with the Fix Broken stuff as you asked me to report back firstly.

CJ

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 4001
Re: Synaptic DB corrupt: The dreaded E: error message.
« Reply #35 on: October 03, 2010, 12:44:10 PM »
OK, now run:

Code: [Select]
rpm -ivh --nodeps --justdb /var/cache/apt/archives/libbinutils2-2.19.51.0.2-3pclos2010
And all should be well again.
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

Offline CJ

  • Sr. Member
  • ****
  • Posts: 454
Re: Synaptic DB corrupt: The dreaded E: error message.
« Reply #36 on: October 03, 2010, 04:50:13 PM »
OK, now run:

Code: [Select]
rpm -ivh --nodeps --justdb /var/cache/apt/archives/libbinutils2-2.19.51.0.2-3pclos2010
And all should be well again.

Slight error in the file name, no biggie, but holy gesundheit, yes, it damn well did it! Thank you, that was that!

What did I just do? I mean, in plainer English, what steps did work in the end?

Cheers!
CJ

Offline kjpetrie

  • PCLinuxOS Tester
  • Hero Member
  • *******
  • Posts: 4001
Re: [SOLVED] Synaptic DB corrupt: The dreaded E: error message.
« Reply #37 on: October 04, 2010, 04:16:10 AM »
Great! Super!

Synaptic is a graphical front end for apt-get, which is a command-line front end for rpm, which manages the packages by keeping a record (database) of what is installed. The packages are archives of files to be installed in various locations together with commands to be run before or after installation or removal, and information on dependencies.

Somehow, it seems, the database entry for this package got written twice. Whether that was a bug in rpm's database code, or whether something forced the package to be installed over itself, is anyone's guess. This upset all three programs and they refused to work with it. The matter was complicated by the fact the package concerned contains vital system components without which your computer could not run, and therefore the package could not be removed, even temporarily.

What you did was to remove both entries from the database with "rpm -e --nodeps --allmatches --justdb" - -e means remove the package, --nodeps means ignore the dependencies, because rpm would refuse otherwise to remove a package on which others depend, --allmatches tells it to remove all packages which match the entry, otherwise it just complains there are multiple matches as you saw. --justdb means just update the database as if the package were removed but don't delete any files or run any commands. In other words; delete all entries from the database for this package, but leave the files on the system.

Then the second stage was "rpm -ivh --nodeps --justdb". -i means install, v means be verbose, and h means make a progress meter out of '#'s. The v and h are not essential but give feedback on what's going on. --nodeps and --justdb mean what they meant in the first command, so you were telling rpm to write an entry in the database for the package but not to do anything else. The result is one entry in the database for what was already installed, so the record now matches as it should.

Marvellous! Terrific! You have got where you are today.
« Last Edit: October 04, 2010, 04:18:23 AM by kjpetrie »
-----------
KJP
-----------------------------------------------------------
PClos64 RC1 on Intel D945GCLF2 motherboard (Atom 330), 2GB DDR2 RAM, Maxtor STM325031, HL-DT-ST DVDRAM GSA-H42N, Amilo LSL 3220T monitor. Also Acer 5810TG (with custom kernel) and Asus eeePC 2G surf

vjeko

  • Guest
Re: [SOLVED] Synaptic DB corrupt: The dreaded E: error message.
« Reply #38 on: October 04, 2010, 06:25:42 AM »
i sure hope this gets a sticky, great work

Offline CJ

  • Sr. Member
  • ****
  • Posts: 454
Re: [SOLVED] Synaptic DB corrupt: The dreaded E: error message.
« Reply #39 on: October 06, 2010, 04:27:06 AM »
Kjpetrie, great, supper, indeed! Especially including your detailed answer of what I really did to my box. I must admit, much to my shame, that I lost track and simply did what people suggested without being sure what it was, so your explanation was educational. One of those that has the rare superior form that makes you sit there and go 'so easy, why didn't I think of that'!

Thanks again!
CJ