I have an RPM with "%dir /bms/airpex/reports". It gets an error on install
because there is typically an NFS filesystem mounted on that dir.
It tries to set the permissions even though they are already as specified.
error: unpacking of archive failed on file
/bms/airpex/reports: cpio: chown failed - Operation not permitted
a) is this a bug?
b) should I just have a %post to make the dir only if it doesn't exist? How
can the rpm then "own" the directory?
I considered "umount" in %pre and "mount" in %post, but that could disrupt
operation on upgrade. (Actually, the umount would just fail)
The package is for a document repository, and the repository directory
is often mounted on NAS in production.
Another option is to simply leave the directory out of the RPM, and let
the admin create it and mount an appropriate filesystem on it.
Any advice?
--
Stuart D. Gathman <stuart@xxxxxxxx>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list
