Feature Request - New veeam-release RPM should not override previous repo config file

[tgm]

Dear Veeam Team,

What happens: If an veeam-release rpm is already installed and a new one is available (update) then the existing repository file (which is a config file in the rpm world i would say) gets overwritten.

That's not the way what a user of an rpm based OS expects. There, the normal way is that the new config file is named with the extension (postfix) .rpmnew

Veeam Case: 04358678

To solve this (as i know from my rpm's ) you have to mark the file as config file in the %file section of the spec file
a.e.:

Code: Select all

%files
%attr(0644, root, root) %config(noreplace) %{_sysconfdir}/yum.repos.d/<name_of_the_veeam_repo_file>

It would be great if this gets fixed

thanks
Tom

[PTide]

Hi,

Noted, thank you!