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#12973 - filesystem: /etc/services is not backed up

Attached to Project: Arch Linux
Opened by - (rasta) - Sunday, 25 January 2009, 16:50 GMT
Last edited by Aaron Griffin (phrakture) - Monday, 26 January 2009, 18:46 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When the 'filesystem' package is upgraded, /etc/services is overwritten without being backed up first.
This causes any local services added to the file to get lost.
Please add /etc/services to the backup=() array in the PKGBUILD.

Additional info:
* package version(s): filesystem 2009.01-1 (base)
This task depends upon

Closed by  Aaron Griffin (phrakture)
Monday, 26 January 2009, 18:46 GMT
Reason for closing:  Not a bug
Comment by Dan McGee (toofishes) - Monday, 26 January 2009, 03:26 GMT
I think I disagree on this. Put it in either NoExtract or NoUpgrade, this is a distro-managed file for 99% of people.
Comment by Aaron Griffin (phrakture) - Monday, 26 January 2009, 18:05 GMT
I agree with Dan here. /etc/services isn't really intended to be user-managed. What services have you added that weren't there to begin with?
Comment by - (rasta) - Monday, 26 January 2009, 18:17 GMT
In this case it was glftpd. Giving it a second thought though, this isn't a big issue for me. I don't know how uncommon it is for other applications to require manual modification of /etc/services, but I guess my initial thought was that it wouldn't hurt to do a {,.backup} , if the file had changed since package was installed.
Whatever you decide, thanks for your time. :)
Comment by - (rasta) - Monday, 26 January 2009, 18:31 GMT
After some further investigation, I found a better way to achieve a custom port for a service, namely by adding this to /etc/xinetd.d/<whateverservice> :
type = UNLISTED
port = XXX
(where XXX is the port)

This seems like a less intrusive and more proper solution.
Feel free to close this bug.
Sorry for the noise :)

Loading...