Is it OK to stabilize =sys-apps/cciss_vol_status-1.09-r1 ? If so, please CC all arches which have stable keywords for older versions of this package and add STABLEREQ keyword to the bug.
Agreed, with robbat2's fix this is viable for stable. Arches, please compile test and mark stable: =sys-apps/cciss_vol_status-1.09-r1 Could the last arch please remove: =sys-apps/cciss_vol_status-1.03 =sys-apps/cciss_vol_status-1.09 Without hardware, the output from the utility will not be particularly informative. However, you should be able to confirm that the crontab entry installs and that the utility can not be crashed with command line input.
I have also confirmed that the cron jobs work in both cases. x86, all drives OK ------------------- # cciss_vol_status /dev/cciss/c0d0 /dev/cciss/c0d0: (Smart Array 5i) RAID 5 Volume 0 status: OK. At least one spare drive designated. At least one spare drive remains available. /dev/cciss/c0d0: (Smart Array 5i) Enclosure (S/N: #) on Bus 1, Physical Port J2 status: OK. amd64, one drive failed ----------------------- # cciss_vol_status /dev/cciss/c0d0 /dev/cciss/c0d0: (Smart Array P400) RAID 1 Volume 0 status: OK. At least one spare drive designated. At least one activated on-line spare drive is completely rebuilt on this logical drive. At least one spare drive activated. Failed drives: connector 2I box 1 bay 3 HP DG146ABAB4 3NM2LR9D00009802006S HPDE Drives currently substituted for by spares: connector 1I box 1 bay 7 HP EG0146FAWHU 6SD05XZ20000B03927DF HPDE Total of 1 failed physical drives detected on this logical drive.
x86 stable. Thanks Michael.
amd64 stable. Last arch, closing
