FS#4878 - pacman overwrites config on updating apache

Attached to Project: Pacman
Opened by Pierre Schmitz (Pierre) - Monday, 26 June 2006, 20:35 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 27 June 2006, 06:32 GMT
Task Type Bug Report
Category
Status Closed
Assigned To Judd Vinet (judd)
Architecture not specified
Severity High
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When I update apache via pacman the files in /etc/httpd/conf/extra are replaced by an example configuration; pacman dos not make any backup. This results in an unusable apache and I have to configure it again.

pacman should never overwrite config-files which were changed by the user.
This task depends upon

Closed by  Aaron Griffin (phrakture)
Wednesday, 03 January 2007, 06:19 GMT
Reason for closing:  Fixed
Additional comments about closing:  Apache properly backs up its configs now. This is a packaging issue, really, not a pacman one, so I'm closing it out.
Comment by Rohan Sheth (Rohan) - Tuesday, 27 June 2006, 17:09 GMT
Ah....my Apache died! No wait...configs were overwritten. Naughty naughty!
Comment by Roman Kyrylych (Romashka) - Wednesday, 28 June 2006, 08:53 GMT
That is because there is backup=(etc/httpd/conf/httpd.conf home/httpd/html/index.html) in PKGBUILD. So Pacman doesn't know about /etc/httpd/conf/extra/*
All files from ectra/ should be added to backup array to fix this problem.
Comment by Arto Puranen (Purch) - Thursday, 26 October 2006, 18:12 GMT
I just found that apache logs are gone from the past 30 days. After some digging it looks that /etc/logrotate.d/httpd should be added to the apache PKGBUILD backup array.

Shouldn't all config files be in backup array by default in every PKGBUILD?
Comment by Roman Kyrylych (Romashka) - Thursday, 26 October 2006, 19:53 GMT
> Shouldn't all config files be in backup array by default in every PKGBUILD?
IMHO, in most situatations, yes.

Loading...