[bug-notifications] [libpcre0 0004922]: pkgadd fails; corrupted pkginfo file

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4922 
====================================================================== 
Reported By:                philkirsch
Assigned To:                
====================================================================== 
Project:                    libpcre0
Issue ID:                   4922
Category:                   other
Reproducibility:            always
Severity:                   crash
Priority:                   normal
Status:                     new
====================================================================== 
Date Submitted:             2012-03-13 04:56 CET
Last Modified:              2012-03-13 08:32 CET
====================================================================== 
Summary:                    pkgadd fails; corrupted pkginfo file
Description: 
I downloaded 88 CSW packages hoping to run nmap and was adding them in the
order recommended. When I got to CSWlibpcre0, ran "pkgadd -d
libpcre0-8.21,REV=2-11.12.13-Sun-S5.9-i386-CSW.pkg" the system recognized
that package and asked if I wanted to add "all". Of course that was the
only package I was added at the moment, so I typed "all" and pressed
"Enter". At this point the entire system rebooted without notice. I tried
"pkgrm CSWlibpcre0" and that ran, but repeat of the pkgadd resulted in
another reboot.

I have not even tried reproducing it on another system, but I've tried a
total of three times on this system.

Even more frustrating "pkginfo -l" stops after CSWlibjpeg7 with the
message: "pkginfo: ERROR: pkginfo file is corrupt or missing"
====================================================================== 

---------------------------------------------------------------------- 
 (0009720) maciej (developer) - 2012-03-13 08:32
 https://www.opencsw.org/mantis/view.php?id=4922#c9720 
---------------------------------------------------------------------- 
Based on the description, these symptoms are likely to be caused by
hardware failures. Can you check that?

- Faulty memory
- Bad sectors