I haven't gotten back to this, but meanwhile
brew install apache-httpd
installs Apache/2.4.29 and creates /usr/local/bin/apachectl
- Sam Ruby
On Sun, Jan 21, 2018 at 10:19 PM, Sam Ruby wrote:
> On Sun, Jan 21, 2018 at 9:52 PM, sebb wrote:
>> The apachectl script uses the following launch
On Sun, Jan 21, 2018 at 9:52 PM, sebb wrote:
> The apachectl script uses the following launch config:
>
> /System/Library/LaunchDaemons/org.apache.httpd.plist
>
> If the change is made to the copy in /Library/LaunchDaemons/ then
> apachectl won't pick it up.
>
> Unfortunately it does not seem to b
The apachectl script uses the following launch config:
/System/Library/LaunchDaemons/org.apache.httpd.plist
If the change is made to the copy in /Library/LaunchDaemons/ then
apachectl won't pick it up.
Unfortunately it does not seem to be possible to override this.
Possible work-rounds:
- Crea
On Sun, Jan 21, 2018 at 8:56 PM, sebb wrote:
>
> At least the live Whimsy seems to be OK on 5.1.12.
I have no issue on Ubuntu.
- Sam Ruby
On 22 January 2018 at 01:33, Sam Ruby wrote:
> On Sun, Jan 21, 2018 at 8:19 PM, sebb wrote:
>> However when I tried updating to version 5.1.12 I got messages of the form:
>>
>> +[__NSCFConstantString initialize] may have been in progress in
>> another thread when fork() was called. We cannot safe
On Sun, Jan 21, 2018 at 8:19 PM, sebb wrote:
> However when I tried updating to version 5.1.12 I got messages of the form:
>
> +[__NSCFConstantString initialize] may have been in progress in
> another thread when fork() was called. We cannot safely call it or
> ignore it in the fork() child proces
However when I tried updating to version 5.1.12 I got messages of the form:
+[__NSCFConstantString initialize] may have been in progress in
another thread when fork() was called. We cannot safely call it or
ignore it in the fork() child process. Crashing instead.
The blog here [1] explains why, b
I'm using High Sierra. Passenger status says:
Version : 5.1.11
Date: 2018-01-21 23:56:09 +
Instance: 2l0pXx76 (Apache/2.4.28 (Unix) Phusion_Passenger/5.1.5)
This works fine for me.
On 21 January 2018 at 23:21, Sam Ruby wrote:
> See https://github.com/phusion/passenger/issues/1986
>
> I
See https://github.com/phusion/passenger/issues/1986
I'm exploring brew install apache-httpd to see if that is any better.
- Sam Ruby
Secretary workbench has been updated:
https://github.com/apache/whimsy/commit/dee30b73b5637f33806d8369cf9c5e9e528635fd
If there are any problems that are suspected to be caused by this
change, feel free to remove that line.
- Sam Ruby
On Mon, Jan 15, 2018 at 4:08 PM, Sam Ruby wrote:
> TL;DR:
[
https://issues.apache.org/jira/browse/WHIMSY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333699#comment-16333699
]
Sebb commented on WHIMSY-177:
-
Putting list name first:
commit ede2f24d1e447d56abdde8562bde4e
[
https://issues.apache.org/jira/browse/WHIMSY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333485#comment-16333485
]
Sebb commented on WHIMSY-177:
-
Maybe the whole screen needs rethinking.
In most cases, the pr
[
https://issues.apache.org/jira/browse/WHIMSY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333482#comment-16333482
]
Sebb commented on WHIMSY-177:
-
Added text to screen:
commit 8b5da77c455c78e08c23f2dd393d26f41
Sebb created WHIMSY-177:
---
Summary: Better handling of unsubscribe feature
Key: WHIMSY-177
URL: https://issues.apache.org/jira/browse/WHIMSY-177
Project: Whimsy
Issue Type: Improvement
Repor
14 matches
Mail list logo