Your message dated Sun, 28 Nov 2010 19:06:11 -0600
with message-id <20101128190611.0b20b...@panther>
and subject line Invalid Bug
has caused the Debian Bug report #586050,
regarding Does not ignore /etc/nginx/sites-enabled/*~ (and perhaps other backup
files too)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
586050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=586050
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nginx
Version: 0.7.65-6
Severity: minor
Backup files created by editors can result in (in my case harmless)
configuration errors or duplication.
-- System Information:
Debian Release: squeeze/sid
APT prefers stable
APT policy: (500, 'stable'), (490, 'testing'), (450, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_AU, LC_CTYPE=en_AU (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages nginx depends on:
ii libc6 2.11.1-3 Embedded GNU C Library: Shared lib
ii libgeoip1 1.4.7~beta5+dfsg-1 A non-DNS IP-to-country resolver l
ii libpcre3 7.8-3 Perl 5 Compatible Regular Expressi
ii libssl0.9.8 0.9.8n-1 SSL shared libraries
ii lsb-base 3.2-23.1 Linux Standard Base 3.2 init scrip
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
nginx recommends no packages.
nginx suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
I'm marking this as closed as I feel it is invalid.
When expanded, the files included from nginx.conf with file globs are:
/etc/nginx/sites-enabled/*
/etc/nginx/conf.d/*.conf
By adding *.conf as a requirement for the end of the file name, the tilde (~)
appended by most editors that create backup files excludes the file from that
glob as the inclusion would need to be /etc/nginx/conf.d/*.conf~ to get those.
The /etc/nginx/sites-enabled/* inclusion is meant to behave similarly to Apache
which many have grown accustomed to. As such, it is expected that files are
created and edited in /etc/nginx/sites-available/ and symbolic links are
created in /etc/nginx/sites-enabled/ that point at those files. The backup
files created are then not included at this point.
Unless you are editing files directly in /etc/nginx/sites-enabled/ which is
against design, then you should not encounter this issue. Even if you choose to
do so, it's not the place of the application to know every possible way an
editor may create a backup file. It is rather the editor that should deal with
with this issue within the editor.
--- End Message ---
