Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionAlexander Todorov
2012-06-01 07:56:03 UTC
Description of problem:
Performed everything package set install to test for clean install.log
Installing hsqldb-1.8.0.10-9.el6.noarch
ln: target `hsqldb.jar' is not a directoryln: target `servlet.jar' is not a directorywarning: %post(hsqldb-1:1.8.0.10-9.el6.noarch) scriptlet failed, exit status 1
Version-Release number of selected component (if applicable):
hsqldb-1:1.8.0.10-9
How reproducible:
Steps to Reproduce:
1. Install with
*
-@conflicts-Server
2.
3.
Actual results:
%post script error
Expected results:
No errors, clean install.log
Additional info:
Comment 3Stanislav Ochotnicky
2012-06-01 15:16:25 UTC
I'll assume it was Deepak work on bug 816735 that caused this. Reassigning
I cannot see how my changes could have caused this error as I changed nothing in the code that related to what %post does.
Also, I am unable to reproduce this in a local VM:
[root@dhcp-10-15-16-104 tmp]# rpm -q hsqldb
hsqldb-1.8.0.10-8.el6.x86_64
[root@dhcp-10-15-16-104 tmp]# rpm -Uvh hsqldb-1.8.0.10-9.el6.noarch.rpm
Preparing... ########################################### [100%]
1:hsqldb ########################################### [100%]
[root@dhcp-10-15-16-104 tmp]# rpm -e hsqldb
[root@dhcp-10-15-16-104 tmp]# rpm -q hsqldb
package hsqldb is not installed
[root@dhcp-10-15-16-104 tmp]# rpm -ivh hsqldb-1.8.0.10-9.el6.noarch.rpm
Preparing... ########################################### [100%]
1:hsqldb ########################################### [100%]
[root@dhcp-10-15-16-104 tmp]#
It would have been interesting to see what the state of the system was when the error happened.
The error message in the original report is shown when ln is given 2+ args and the last is not a directory. It is from these line in %post:
ln -s $(build-classpath hsqldb) hsqldb.jar
ln -s $(build-classpath apache-tomcat-apis/tomcat-servlet2.5-api) servlet.jar
That means that both, $(build-classpath hsqldb) and $(build-classpath apache-tomcat-apis/tomcat-servlet2.5-api) returned more than one value.. it is wierd that build-classpath saw two or more jars for each of them.
So is it okay to close this bug as WORKSFORME?
Comment 21Mikolaj Izdebski
2012-09-19 08:39:01 UTC
*** Bug 845539 has been marked as a duplicate of this bug. ***
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0334.html