#31004: nginx should not own nginx.conf ------------------------------+--------------------------------------------- Reporter: ast@… | Owner: boeyms@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.1 Keywords: | Port: nginx ------------------------------+--------------------------------------------- Changes (by ryandesign@…): * owner: macports-tickets@… => boeyms@… * keywords: nginx.conf delete modified => Old description:

Just hit this one today when I was trying to configure nginx with SSL on my development machine. Had made all the required changes to configure a new server instance in my nginx.conf (I don't use subconfigs on this box), and then got this message:

{{{ valkyrie$ sudo nginx -s reload nginx: [emerg] unknown directive "ssl" in /opt/local/etc/nginx/nginx.conf:99 }}}

Finding this page [http://kete.net.nz/documentation/topics/show/167 -configure-nginx-to-use-ssl], I followed the instructions, but once I'd deactivated nginx, ''it deleted my nginx.conf file!''

Even RPM got this right over 15 years ago, so I can't understand why this package has so much trouble whacking configuration files (see my other ticket: [https://trac.macports.org/ticket/27354]).

The nginx.conf file shouldn't be part of the files managed by the installation, or if it is, it needs to be checked against either a modification time or a hash value of the package one so that these problems don't happen.

New description: Just hit this one today when I was trying to configure nginx with SSL on my development machine. Had made all the required changes to configure a new server instance in my nginx.conf (I don't use subconfigs on this box), and then got this message: {{{ valkyrie$ sudo nginx -s reload nginx: [emerg] unknown directive "ssl" in /opt/local/etc/nginx/nginx.conf:99 }}} Finding this page [http://kete.net.nz/documentation/topics/show/167 -configure-nginx-to-use-ssl], I followed the instructions, but once I'd deactivated nginx, ''it deleted my nginx.conf file! '' Even RPM got this right over 15 years ago, so I can't understand why this package has so much trouble whacking configuration files (see my other ticket: [https://trac.macports.org/ticket/27354]). The nginx.conf file shouldn't be part of the files managed by the installation, or if it is, it needs to be checked against either a modification time or a hash value of the package one so that these problems don't happen. -- Comment: Apologies for the trouble. You're right, nginx should not own the nginx conf file. Instead it should install a ''sample'' conf file, and advise the user how to copy it. Many of our other ports do this, but nginx has not yet been set up that way. -- Ticket URL: <https://trac.macports.org/ticket/31004#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#31004: nginx should not own nginx.conf ------------------------------+--------------------------------------------- Reporter: ast@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.1 Keywords: | Port: nginx ------------------------------+--------------------------------------------- Description changed by ryandesign@…: Old description:

Just hit this one today when I was trying to configure nginx with SSL on my development machine. Had made all the required changes to configure a new server instance in my nginx.conf (I don't use subconfigs on this box), and then got this message:

{{{ valkyrie$ sudo nginx -s reload nginx: [emerg] unknown directive "ssl" in /opt/local/etc/nginx/nginx.conf:99 }}}

Finding this page [http://kete.net.nz/documentation/topics/show/167 -configure-nginx-to-use-ssl], I followed the instructions, but once I'd deactivated nginx, ''it deleted my nginx.conf file! ''

Even RPM got this right over 15 years ago, so I can't understand why this package has so much trouble whacking configuration files (see my other ticket: [https://trac.macports.org/ticket/27354]).

The nginx.conf file shouldn't be part of the files managed by the installation, or if it is, it needs to be checked against either a modification time or a hash value of the package one so that these problems don't happen.

New description: Just hit this one today when I was trying to configure nginx with SSL on my development machine. Had made all the required changes to configure a new server instance in my nginx.conf (I don't use subconfigs on this box), and then got this message: {{{ valkyrie$ sudo nginx -s reload nginx: [emerg] unknown directive "ssl" in /opt/local/etc/nginx/nginx.conf:99 }}} Finding this page [http://kete.net.nz/documentation/topics/show/167 -configure-nginx-to-use-ssl], I followed the instructions, but once I'd deactivated nginx, ''it deleted my nginx.conf file! '' Even RPM got this right over 15 years ago, so I can't understand why this package has so much trouble whacking configuration files (see my other ticket: #27354). The nginx.conf file shouldn't be part of the files managed by the installation, or if it is, it needs to be checked against either a modification time or a hash value of the package one so that these problems don't happen. -- -- Ticket URL: <https://trac.macports.org/ticket/31004#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#31004: nginx should not own nginx.conf -------------------------------+-------------------------------------------- Reporter: ast@… | Owner: cal@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.0.1 Resolution: fixed | Keywords: Port: nginx | -------------------------------+-------------------------------------------- Changes (by cal@…): * status: new => closed * resolution: => fixed Comment: This has already been fixed for `nginx.conf` for quite a while now. I applied the relevant parts from #34188 for the other files in `$prefix/etc/nginx` in r92300. -- Ticket URL: <https://trac.macports.org/ticket/31004#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS