During an upgrade of the jenkins package via the official repository, the /etc/sysconfig/jenkins and /etc/init.d/jenkins files are moved to .rpmsave and new versions created instead.
I have a custom configuration for our environment and upgrading jenkins breaks things bad when it rotates out my configs.
The rpm should create a new config with .rpmnew instead of rotating out existing configs.
Originally reported by thomasmorse, imported from: Redhat/Centos rpm moves aside existing config files during install/upgrade
- status: Resolved
- priority: Major
- component(s): core, other
- label(s): rpm
- resolution: Fixed
- resolved: 2011-08-09T21:40:15+00:00
- votes: 1
- watchers: 3
- imported: 2025-11-24
Raw content of original issue
During an upgrade of the jenkins package via the official repository, the /etc/sysconfig/jenkins and /etc/init.d/jenkins files are moved to .rpmsave and new versions created instead.
I have a custom configuration for our environment and upgrading jenkins breaks things bad when it rotates out my configs.
The rpm should create a new config with .rpmnew instead of rotating out existing configs.
- environment:
Redhat, Centos 5 and Fedora
During an upgrade of the jenkins package via the official repository, the /etc/sysconfig/jenkins and /etc/init.d/jenkins files are moved to .rpmsave and new versions created instead.
I have a custom configuration for our environment and upgrading jenkins breaks things bad when it rotates out my configs.
The rpm should create a new config with .rpmnew instead of rotating out existing configs.
Originally reported by thomasmorse, imported from: Redhat/Centos rpm moves aside existing config files during install/upgrade
Raw content of original issue
Redhat, Centos 5 and Fedora