[New: openFATE 314816] Notify User of rpmnew config files
Feature added by: Richard Brown (RBrownCCB) Feature #314816, revision 1 Title: Notify User of rpmnew config files openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Richard Brown (rbrownccb) Partner organization: openSUSE.org Description: Details to be added... -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Richard Brown (RBrownCCB) Feature #314816, revision 2 - Title: Notify User of rpmnew config files + Title: Notify user of rpmnew and rpmsav config files openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Richard Brown (rbrownccb) Partner organization: openSUSE.org Description: Details to be added... -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Richard Brown (RBrownCCB) Feature #314816, revision 3 Title: Notify user of rpmnew and rpmsav config files openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Richard Brown (rbrownccb) Partner organization: openSUSE.org Description: - Details to be added... + When packages are installed with new/restyled configuration files, they + generate .rpmnew or .rpmsave files to ensure the changes don't clash + with existing system configurations + The theory is, a sysadmin can then visit the files, assess the changes, + and merge those changes with their existing files + It would be great if we could get Zypper (and therefore YaST) to track + those situations and at least inform the user that they have files to + review. + zypper.log shows that libzypp is already aware of when rpmnew and + rpmsave files are being crated, so it should be possible to capture + those and inform the user at the end of any zypper or YaST package + install + Taking the idea to a next step, tools to help/automate the merging + might be a nice feature once this has been accomplished. -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Richard Brown (RBrownCCB) Feature #314816, revision 5 - Title: Notify user of rpmnew and rpmsav config files + Title: Notify user of rpmnew config files openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Richard Brown (rbrownccb) Partner organization: openSUSE.org Description: When packages are installed with new/restyled configuration files, they generate .rpmnew or .rpmsave files to ensure the changes don't clash with existing system configurations The theory is, a sysadmin can then visit the files, assess the changes, and merge those changes with their existing files It would be great if we could get Zypper (and therefore YaST) to track those situations and at least inform the user that they have files to review. zypper.log shows that libzypp is already aware of when rpmnew and rpmsave files are being crated, so it should be possible to capture those and inform the user at the end of any zypper or YaST package install Taking the idea to a next step, tools to help/automate the merging might be a nice feature once this has been accomplished. -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Andreas Mrvka (mrv) Feature #314816, revision 6 Title: Notify user of rpmnew config files openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Richard Brown (rbrownccb) Partner organization: openSUSE.org Description: When packages are installed with new/restyled configuration files, they generate .rpmnew or .rpmsave files to ensure the changes don't clash with existing system configurations The theory is, a sysadmin can then visit the files, assess the changes, and merge those changes with their existing files It would be great if we could get Zypper (and therefore YaST) to track those situations and at least inform the user that they have files to review. zypper.log shows that libzypp is already aware of when rpmnew and rpmsave files are being crated, so it should be possible to capture those and inform the user at the end of any zypper or YaST package install Taking the idea to a next step, tools to help/automate the merging might be a nice feature once this has been accomplished. + Discussion: + #1: Andreas Mrvka (mrv) (2013-02-03 23:58:55) + would be a nice feature for server-side services ;-) -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Richard Brown (RBrownCCB) Feature #314816, revision 7 Title: Notify user of rpmnew config files - openSUSE Distribution: Unconfirmed + openSUSE Distribution: Implementation Priority Requester: Important Requested by: Richard Brown (rbrownccb) + Developer: Misha Mayorov (misha) Partner organization: openSUSE.org Description: When packages are installed with new/restyled configuration files, they generate .rpmnew or .rpmsave files to ensure the changes don't clash with existing system configurations The theory is, a sysadmin can then visit the files, assess the changes, and merge those changes with their existing files It would be great if we could get Zypper (and therefore YaST) to track those situations and at least inform the user that they have files to review. zypper.log shows that libzypp is already aware of when rpmnew and rpmsave files are being crated, so it should be possible to capture those and inform the user at the end of any zypper or YaST package install Taking the idea to a next step, tools to help/automate the merging might be a nice feature once this has been accomplished. Discussion: #1: Andreas Mrvka (mrv) (2013-02-03 23:58:55) would be a nice feature for server-side services ;-) -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Richard Brown (RBrownCCB) Feature #314816, revision 8 Title: Notify user of rpmnew config files openSUSE Distribution: Implementation Priority Requester: Important Requested by: Richard Brown (rbrownccb) - Developer: Misha Mayorov (misha) Partner organization: openSUSE.org Description: When packages are installed with new/restyled configuration files, they generate .rpmnew or .rpmsave files to ensure the changes don't clash with existing system configurations The theory is, a sysadmin can then visit the files, assess the changes, and merge those changes with their existing files It would be great if we could get Zypper (and therefore YaST) to track those situations and at least inform the user that they have files to review. zypper.log shows that libzypp is already aware of when rpmnew and rpmsave files are being crated, so it should be possible to capture those and inform the user at the end of any zypper or YaST package install Taking the idea to a next step, tools to help/automate the merging might be a nice feature once this has been accomplished. Discussion: #1: Andreas Mrvka (mrv) (2013-02-03 23:58:55) would be a nice feature for server-side services ;-) -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Richard Brown (RBrownCCB) Feature #314816, revision 9 Title: Notify user of rpmnew config files openSUSE Distribution: Implementation Priority Requester: Important Requested by: Richard Brown (rbrownccb) + Developer: urban bozicnik (miska) Partner organization: openSUSE.org Description: When packages are installed with new/restyled configuration files, they generate .rpmnew or .rpmsave files to ensure the changes don't clash with existing system configurations The theory is, a sysadmin can then visit the files, assess the changes, and merge those changes with their existing files It would be great if we could get Zypper (and therefore YaST) to track those situations and at least inform the user that they have files to review. zypper.log shows that libzypp is already aware of when rpmnew and rpmsave files are being crated, so it should be possible to capture those and inform the user at the end of any zypper or YaST package install Taking the idea to a next step, tools to help/automate the merging might be a nice feature once this has been accomplished. Discussion: #1: Andreas Mrvka (mrv) (2013-02-03 23:58:55) would be a nice feature for server-side services ;-) -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Christian Boltz (cboltz) Feature #314816, revision 10 Title: Notify user of rpmnew config files openSUSE Distribution: Implementation Priority Requester: Important Requested by: Richard Brown (rbrownccb) Developer: urban bozicnik (miska) Partner organization: openSUSE.org Description: When packages are installed with new/restyled configuration files, they generate .rpmnew or .rpmsave files to ensure the changes don't clash with existing system configurations The theory is, a sysadmin can then visit the files, assess the changes, and merge those changes with their existing files It would be great if we could get Zypper (and therefore YaST) to track those situations and at least inform the user that they have files to review. zypper.log shows that libzypp is already aware of when rpmnew and rpmsave files are being crated, so it should be possible to capture those and inform the user at the end of any zypper or YaST package install Taking the idea to a next step, tools to help/automate the merging might be a nice feature once this has been accomplished. + Relations: + - put /etc under (git) version control (feature/id: 310713) Discussion: #1: Andreas Mrvka (mrv) (2013-02-03 23:58:55) would be a nice feature for server-side services ;-) + #2: Christian Boltz (cboltz) (2013-02-04 13:15:21) + See /etc/init.d/rpmconfigcheck - that's a script to find and list *. + rpmnew and *.rpmorig files. + See also feature 310713 - put /etc under (git) version control -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Richard Brown (RBrownCCB) Feature #314816, revision 11 Title: Notify user of rpmnew config files openSUSE Distribution: Implementation Priority Requester: Important Requested by: Richard Brown (rbrownccb) - Developer: urban bozicnik (miska) Partner organization: openSUSE.org Description: When packages are installed with new/restyled configuration files, they generate .rpmnew or .rpmsave files to ensure the changes don't clash with existing system configurations The theory is, a sysadmin can then visit the files, assess the changes, and merge those changes with their existing files It would be great if we could get Zypper (and therefore YaST) to track those situations and at least inform the user that they have files to review. zypper.log shows that libzypp is already aware of when rpmnew and rpmsave files are being crated, so it should be possible to capture those and inform the user at the end of any zypper or YaST package install Taking the idea to a next step, tools to help/automate the merging might be a nice feature once this has been accomplished. Relations: - put /etc under (git) version control (feature/id: 310713) Discussion: #1: Andreas Mrvka (mrv) (2013-02-03 23:58:55) would be a nice feature for server-side services ;-) #2: Christian Boltz (cboltz) (2013-02-04 13:15:21) See /etc/init.d/rpmconfigcheck - that's a script to find and list *. rpmnew and *.rpmorig files. See also feature 310713 - put /etc under (git) version control -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Michal Hrusecky (-miska-) Feature #314816, revision 12 Title: Notify user of rpmnew config files openSUSE Distribution: Implementation Priority Requester: Important Requested by: Richard Brown (rbrownccb) Partner organization: openSUSE.org Description: When packages are installed with new/restyled configuration files, they generate .rpmnew or .rpmsave files to ensure the changes don't clash with existing system configurations The theory is, a sysadmin can then visit the files, assess the changes, and merge those changes with their existing files It would be great if we could get Zypper (and therefore YaST) to track those situations and at least inform the user that they have files to review. zypper.log shows that libzypp is already aware of when rpmnew and rpmsave files are being crated, so it should be possible to capture those and inform the user at the end of any zypper or YaST package install Taking the idea to a next step, tools to help/automate the merging might be a nice feature once this has been accomplished. Relations: - put /etc under (git) version control (feature/id: 310713) Discussion: #1: Andreas Mrvka (mrv) (2013-02-03 23:58:55) would be a nice feature for server-side services ;-) #2: Christian Boltz (cboltz) (2013-02-04 13:15:21) See /etc/init.d/rpmconfigcheck - that's a script to find and list *. rpmnew and *.rpmorig files. See also feature 310713 - put /etc under (git) version control + #3: Michal Hrusecky (-miska-) (2013-02-04 23:18:40) + See sr#151188 -- openSUSE Feature: https://features.opensuse.org/314816
Feature changed by: Richard Brown (RBrownCCB) Feature #314816, revision 13 Title: Notify user of rpmnew config files - openSUSE Distribution: Implementation + openSUSE Distribution: Done Priority Requester: Important Requested by: Richard Brown (rbrownccb) Developer: Michal Hrusecky (-miska-) Partner organization: openSUSE.org Description: When packages are installed with new/restyled configuration files, they generate .rpmnew or .rpmsave files to ensure the changes don't clash with existing system configurations The theory is, a sysadmin can then visit the files, assess the changes, and merge those changes with their existing files It would be great if we could get Zypper (and therefore YaST) to track those situations and at least inform the user that they have files to review. zypper.log shows that libzypp is already aware of when rpmnew and rpmsave files are being crated, so it should be possible to capture those and inform the user at the end of any zypper or YaST package install Taking the idea to a next step, tools to help/automate the merging might be a nice feature once this has been accomplished. Relations: - put /etc under (git) version control (feature/id: 310713) Discussion: #1: Andreas Mrvka (mrv) (2013-02-03 23:58:55) would be a nice feature for server-side services ;-) #2: Christian Boltz (cboltz) (2013-02-04 13:15:21) See /etc/init.d/rpmconfigcheck - that's a script to find and list *. rpmnew and *.rpmorig files. See also feature 310713 - put /etc under (git) version control #3: Michal Hrusecky (-miska-) (2013-02-04 23:18:40) See sr#151188 -- openSUSE Feature: https://features.opensuse.org/314816
participants (1)
-
fate_noreply@suse.de