Bug 13014
Summary: | Core dumping after --rebuilddb on rpm-4.0-0.45 | ||
---|---|---|---|
Product: | [Retired] Red Hat Raw Hide | Reporter: | Reuben Farrelly <reuben-redhatbugzilla> |
Component: | rpm | Assignee: | Jeff Johnson <jbj> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0 | CC: | satan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-07-07 01:04:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Reuben Farrelly
2000-06-25 14:34:24 UTC
Get the source from CVS http://www.rpm.org/cvs.html follow the CVS instructions to dowload the directory (get cvs rpm's if you don't have cvs installed). Also get the latest libtool (1.3.5) as you need this. Once you have this all you need to do is to run the autogen.sh and make and make install. This converts the databases and does everything else without a glitch. I also used rpm.spec in cvs to build new rpms for 4.0-0.45 and they worked fine. I am not sure what rawhide is doing so that their rpm's for rpm-4.0 are having lots of problems. This was the same story with 0.33! Argg, I can't get the source from the CVS tree to compile. Would someone be so kind as to email me their own good RPM? Any help would be greatly appreciated! <sting.com> That gdb of your core dump is useless, look cloesly near the beginning of the gdb output: warning: core file may not match specified executable file. Core was generated by `/usr/lib/rpm/rpmq -q -- rpm'. try doing: gdb /usr/lib/rpm/rpmq core That will get an accurate core dump to do a bt on. When you do, post it here, otherwise not much can be extracted from your gdb output. -Stan Bubrouski Is this still a problem? If so, send me mail <jbj> and I'll send you a conversion procedure. Otherwise, I'll chalk this problem up to converting from db3-3.0.55 -> db3->3.1.14 between beta1 and beta2. |