Description of problem: | # rpm -Uvh servletapi5-5.0.18-1jpp_3fc.noarch.rpm servletapi5-javadoc-5.0.18-1jpp_3fc.noarch.rpm | Preparing... ########################################### [100%] | 1:servletapi5-javadoc ########################################### [ 50%] | rm: cannot remove `/usr/share/javadoc/servletapi5': Read-only file system | rm: cannot remove `/usr/share/javadoc/jsp-api': Read-only file system | ln: creating symbolic link `/usr/share/javadoc/servletapi5/servletapi5-5.0.18' to `servletapi5-5.0.18': Read-only file system | ln: creating symbolic link `/usr/share/javadoc/jsp-api/jsp-api-5.0.18' to `jsp-api-5.0.18': Read-only file system | error: %post(servletapi5-javadoc-5.0.18-1jpp_3fc) scriptlet failed, exit status 1 | 2:servletapi5 ########################################### [100%] This is caused by the | $ rpm -q --scripts servletapi5-javadoc | postinstall scriptlet (using /bin/sh): | rm -f /usr/share/javadoc/servletapi5 | rm -f /usr/share/javadoc/jsp-api | ln -s servletapi5-5.0.18 /usr/share/javadoc/servletapi5 | ln -s jsp-api-5.0.18 /usr/share/javadoc/jsp-api script which does not check whether /usr/share is mounted read-only. Note that the %post script of the main-package is ok; it uses 'update-alternatives' which seems to operate in a more clever way. See bug #51193 for additional information. Version-Release number of selected component (if applicable): servletapi5-5.0.18-1jpp_3fc How reproducible: 100% Additional info: afais, most of the other java-packages are affected also.
/usr/share mounted as read-only is not supported. Out of curiosity, why would someone want to do that? Regards.
read-only /usr/share is supported. Please read bug #51193 for details.
a more java-package specific explaination can be found in bug #122713
No, our Java packages belong to the RHAPS product that does NOT support read-only /usr/share. If this feature is deemed necessary, please create an appropriate "feature request" so it can be evaluated by PM, work estimated, scheduled and implemented. In the meanwhile I have raised the issue of bug #51193 upstream for opinions on the feasibility of a solution.
Correction, the Java-related bug that is to be discussed upstream is bug #122713
No, the java-packages belong to the Fedora Core project which supports %_netsharedpath.
OK, so I am reassigning it so it is handled in a Fedora Core-only context.
http://listman.redhat.com/archives/fedora-devel-list/2004-December/msg00214.html
*** This bug has been marked as a duplicate of 122713 ***