Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix creating keystore when upgrading #29121

Merged
merged 1 commit into from
Mar 17, 2018
Merged

Fix creating keystore when upgrading #29121

merged 1 commit into from
Mar 17, 2018

Commits on Mar 17, 2018

  1. Fix creating keystore when upgrading 

    When upgrading via the RPM package, we can run into a problem where
the keystore fails to be created. This arises because the %post script
on RPM runs after the new package files are installed but before the
removal of the old package files. This means that the contents of the
lib folder can contain files from the old package and the new package
and thus running the create keystore tool can encounter JAR hell
issues and fail. To solve this, we move creating the keystore to the
%posttrans script which runs after the old package files are
removed. We only need to do this on the RPM package, so we add a
switch in the shared post-install script.
    @jasontedor
    jasontedor committed Mar 17, 2018
    Configuration menu
    Copy the full SHA
    ed78f5e View commit details
    Browse the repository at this point in the history