Mantis - apache2
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
4948 | packaging | tweak | always | 2012-05-24 01:34 | 2012-08-02 18:47 |
|
|||||
Reporter: | briandking | Platform: | |||
Assigned To: | bwalton | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | |||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | |||
|
|||||
Summary: | 0004948: packaging of envvars clobbers local envvars on an upgrade | ||||
Description: |
I would like to suggest that the envvars file be packaged the same way httpd.conf is, so that when apache is upgraded, it doesn't clobber a site specific envvars file. E.g. httpd.conf is not clobbered because it's packaged as httpd.conf.CSW: /opt/csw/apache2/etc/httpd.conf.CSW f none 0644 root bin 17158 11884 1326427072 CSWapache2 envvars is clobbered because it's packaged twice: /opt/csw/apache2/sbin/envvars f none 0644 root bin 976 18721 1326427061 CSWapache2 /opt/csw/apache2/sbin/envvars-std f none 0644 root bin 976 18721 1326427061 CSWapache2 If the /opt/csw/apache2/sbin/envvars was dropped, an example envvars would still be distributed, and the local envvars would not be overwritten. |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: | |||||
|
|||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2012-05-24 01:34 | briandking | New Issue | |||
2012-05-31 01:52 | bwalton | Status | new => assigned | ||
2012-05-31 01:52 | bwalton | Assigned To | => bwalton | ||
2012-05-31 03:13 | bwalton | Note Added: 0009886 | |||
2012-06-02 02:24 | bwalton | Note Added: 0009891 | |||
2012-08-02 18:47 | bwalton | Note Added: 0010077 | |||
2012-08-02 18:47 | bwalton | Status | assigned => closed | ||
2012-08-02 18:47 | bwalton | Resolution | open => fixed |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|