Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#13103 - Backup /etc/nscd.conf in glibc

Attached to Project: Arch Linux
Opened by Kaiting Chen (Phoenixfire159) - Monday, 02 February 2009, 22:25 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 17 March 2009, 11:06 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Andreas Radke (AndyRTR)
Allan McRae (Allan)
Architecture All
Severity Medium
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

I'm not sure if this is the proper behavior or not, but I edited /etc/nscd.conf, and after upgrading to the latest glibc, all my edits were gone. It brought down my system for a while until I had to go in and boot using a recovery disk to fix it. Also, editing any file in /etc/rc.d/, and subsequently upgrading the corresponding package does not preserve your changes.

The entire /etc directory should really be protected.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 17 March 2009, 11:06 GMT
Reason for closing:  Fixed
Additional comments about closing:  commited to trunk
Comment by Greg (dolby) - Tuesday, 03 February 2009, 01:40 GMT
Thats not a pacman issue. Pacman already gives the ability to packagers to backup any file they want to. nscd.conf wasnt added in backup array of glibc for some reason.
Comment by Kaiting Chen (Phoenixfire159) - Tuesday, 03 February 2009, 02:38 GMT
Should I open a new bug/task?
Comment by Greg (dolby) - Tuesday, 03 February 2009, 02:47 GMT
No, i dont think so. If editing of the title or severity is needed someone else can do it for you. eg. change title to "glibc should backup /etc/nscd.conf"
BTW you say "The entire /etc directory should really be protected.". As i explained above pacman does that seperately for the config files
its considered appropriate to do so.
I dont know if you would like to propose a different approach (if thats actually possible). If you indeed want to, then the pacman section
might be more suitable for that.
Comment by Glenn Matthys (RedShift) - Wednesday, 04 February 2009, 22:38 GMT
The rc.d/ files shouldn't be backed up, and you shouldn't make any changes to them either. They are controlled by their counterpart in conf.d/ which should be backed up by the PKGBUILD.
Comment by Aaron Griffin (phrakture) - Wednesday, 04 February 2009, 22:51 GMT
For the sake of this bug, let's just assume we want to get nscd.conf added to the backup array. The "backup all of etc" issue is different, and will not be implemented - pacman implements backups on a file-by-file basis, as some files the packagers WANT to overwrite. This one was probably just an oversight.
Comment by Kaiting Chen (Phoenixfire159) - Thursday, 05 February 2009, 01:18 GMT
I understand if the initscripts shouldn't be backed up by the packages. I do have some stuff in there that is outside of the scope of what some packages install by default, but I'll handle the support for that myself. The important thing is that nscd.conf gets added to the glibc backup array, since nscd is quite an important service.

Loading...