[
http://jira.codehaus.org/browse/MRPM-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=226170#action_226170
]
Shashi Velur edited comment on MRPM-51 at 6/23/10 2:26 PM:
-----------------------------------------------------------
Thanks again for the quick response.
Let me try to explain our scenario:
When we deploy multiple RPM packages, we use different Unix user accounts to
run the maven rpm plugin. It looks like the Sha1header file is created when you
have files listed in the %files section.
As a result, RPM will run into a permission issue when trying to write to a
file not created by the current user account.
So, if the RPM plugin is run under a different user and Sha1header had already
been created, the error is thrown.
Here is the error:
"error: cannot open Sha1header index using db3 - Permission denied (13)"
Hence the above workaround (code changes for adding an additional boolean flag
in the maven pom config options) to make sure that file list is generated in a
separate file rather than directly in the specification (so that they do not
get overwritten).
Is my assumption right about Sha1header file being created when you have files
listed in the %files section?
Are there any other suggestions to get around this problem?
Cheers,
Shashi
was (Author: shashivelur):
Thanks again for the quick response.
Let me try to explain our scenario:
When we deploy multiple RPM packages, we use different Unix user accounts to
run the maven rpm plugin. It looks like the Sha1header file is created when you
have files listed in the %files section.
As a result, RPM will run into a permission issue when trying to write to a
file not created by the current user account.
So, if the RPM plugin is run under a different user and Sha1header had already
been created, the error is thrown.
Here is the error:
"error: cannot open Sha1header index using db3 - Permission denied (13)"
Hence the above workaround (code changes) to specify the file location so that
they do not get overwritten.
Are there any other suggestions to get around this problem?
Cheers,
Shashi
> Add support for the -f option in the %files section of the rpm spec
> -------------------------------------------------------------------
>
> Key: MRPM-51
> URL: http://jira.codehaus.org/browse/MRPM-51
> Project: Mojo RPM Plugin
> Issue Type: New Feature
> Components: rpm
> Environment: Red hat Linux
> Reporter: Dudley Fox
> Assignee: Brett Okken
> Attachments: patch.tgz, rpm-4.zip
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> We have a.rpm and b.rpm. And we have user_a and user_b.
> We install a.rpm as user_a, and then b.rpm as user_b. The installation
> of b.rpm fails, because it does not have permission to overwrite the
> file Sha1header (part of the rpm database), which is created when you
> have files under your %files section.
>
> We know we can fix this if we use something like: %files -f $PWD/$Name.list
> At this point, it looks as if we will need to add this functionality
> ourselves, as soon
> as we have the patch (or more details) I will add them to this issue.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
