[NBLUG/talk] RPM Segmentation Fault

Todd Cary todd at aristesoftware.com
Sun Dec 7 17:46:01 PST 2003


Mark -

I have been using it as a means of verifying the package, however, I 
have no in depth experience in this area.

Verify options (with -V or --verify):
  --nomd5                          don't verify MD5 digest of files
  --nofiles                        don't verify files in package
  --nodeps                         don't verify package dependencies
  --noscript                       don't execute verify script(s)
  -a, --all                        query/verify all packages
  -f, --file                       query/verify package(s) owning file
  -g, --group                      query/verify package(s) in group
  -p, --package                    query/verify a package file
  --specfile                       query a spec file
  --whatrequires                   query/verify the package(s) which 
require a
                                   dependency
  --whatprovides                   query/verify the package(s) which 
provide a
                                   dependency
I an the -K option and here is what I got:

FirebirdSS-1.5.0.4027-RC7.i686.rpm: sha1 md5 OK

I have not tried the --replacepkgs option....

Todd


Mark Street wrote:

>On Sunday 07 December 2003 13:48, Todd Cary wrote:
>  
>
>>After the yum update,
>># rpm -VP FirebirdSS...
>>creates a Segmentation Fault
>>    
>>
>
>I have never heard of the P option in rpm....
>
>Do this;
>
>rpm -K FirebirdSS...rpm    tell us what you get.
>
>You should see something like this;
>FirebirdSS-1.5.0.4027-RC7.i686.rpm: sha1 md5 OK
>
>Then do
>rpm -qip FirebirdSS...rpm   tell us what you get.
>
>Then do 
>
>rpm --rebuilddb
>
>wait.....
>
>Then do
>
>rpm -ivh FirebirdSS...rpm
>
>  
>
>>Mark Street wrote:
>>    
>>
>>>Hmmm, my experience stated below is with a fedora box with all updates
>>>installed using yum.  I have since installed and erased both Firebird and
>>>Interbase at least twice since your initial post without a hiccup....  And
>>>by the way I built the php rpm in such a way that an UPdate if and when
>>>it becomes available will NOT overwrite my custom package, but it will
>>>download the src rpm for me and get it ready for a custom build.  Then
>>>all I have to do is tweak the .spec file, build it and install it. 
>>>consistency...... custom
>>>
>>>It's hard to give you any advice with the information you provide and the
>>>inability to reproduce said behavior on my fedora box.
>>>
>>>Is it rpm that is seg faulting on the install?
>>>
>>>Try cleaning up the rpm database, rebuild it and try again after your
>>>up2date. (I have never used up2date.... ; ) , but hey..)  I really don't
>>>think this is all worth another install of fedora though.  I think you
>>>are wasting your time doing all these installs.  I prefer a sniper to a
>>>shotgun.
>>>
>>>To rebuild the rpm database....
>>># rpm --rebuilddb
>>>
>>>Then try to install Firebird....
>>>
>>>I don't know what to tell you, I have never known or seen rpm seg
>>>fault..... I have seen it hang and do other strange behaviors from time
>>>to time... but never seg fault.
>>>
>>>You might try using the strace command with your rpm install of firebird
>>>to see where it is bombing.
>>>
>>>strace rpm -ivh Firebird-blah...rpm   you will get a ton of shit but it
>>>may hand you a clue.
>>>
>>>Anyone else have any ideas on where to find clues to this strangeness. 
>>>Maybe a bad RAM module?
>>>      
>>>
>
>  
>

-- 




More information about the talk mailing list