Next | Query returned 30 messages, browsing 11 to 20 | Previous

History of commit frequency

CVS Commit History:


   2018-12-11 10:46:23 by Adam Ciarcinski | Files touched by this commit (4) | Package updated
Log message:
py-mod_wsgi: updated to 4.6.5

Version 4.6.5

Bugs Fixed
* When running mod_wsgi-express and serving up static files from the document \ 
root, and the WSGI application was mounted at a sub URL using --mount-point, the \ 
static files in the document root outside of the mount point for the WSGI \ 
application would no longer be accessible.
* If no system mime types file can be found, fall back to /dev/null so that \ 
Apache can still at least start up.

Features Changed
* On macOS, use /var/tmp as default parent directory for server root directory \ 
rather than value of $TMPDIR. The latter can produce a path which is too long \ 
and UNIX socket cannot be written there.

New Features
* Now possible to use mod_wsgi-express in an a zipapp created using shiv. This \ 
entailed a special workaround to detect when shiv was used, so that the unpacked \ 
site-packages directory could be added to the Python module search path for \ 
mod_wsgi-express.
   2018-04-14 11:34:15 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-mod_wsgi: updated to 4.6.4

Version 4.6.4:
Bugs Fixed
In more recent Python versions, the config directory in the Python installation \ 
incorporates the platform name. This directory was added as an additional \ 
directory to search for Python shared libraries when installing using the \ 
setup.py file or pip. It should not even be needed for newer Python versions but \ 
still check for older Python versions. The only issue arising from the wrong \ 
directory, not incorporating the platform name, being used, was a linker warning \ 
about the directory not being present.

Installing mod_wsgi on Windows would fail as hadn’t exclude mod_wsgi daemon \ 
mode specific code from Windows build. This would result in compile time error \ 
about wsgi_daemon_process being undefined. This problem was introduced to \ 
Windows in version 4.6.0. A prior attempt to fix this in 4.6.3 missed one place \ 
in the code which needed to be changed.

Version 4.6.3
Bugs Fixed

When compiled for Python 2.6, when run mod_wsgi would fail to load into Apache \ 
due to misisng symbol PyFrame_GetLineNumber. This was only introduced in Python \ 
2.7. Use alternate way to get line number which still yields correct answer. \ 
This issue was introduced in mod_wsgi version 4.6.0 in fix to have correct line \ 
numbers generated for stack traces on shutdown due to request timeout.

Installing mod_wsgi on Windows would fail as hadn’t exclude mod_wsgi daemon \ 
mode specific code from Windows build. This would result in compile time error \ 
about wsgi_daemon_process being undefined. This problem was introduced to \ 
Windows in version 4.6.0.

When using runmodwsgi management command integration for Django, the file \ 
containing the WSGI application entry point was specified via a full filesystem \ 
path, rather than by module import path. This meant that relative imports from \ 
that file would fail. The file is now imported as a module path based on what \ 
WSGI_APPLICATION is set to in the Django settings module. This means the file is \ 
imported as part of package for the project and relative imports will work.
   2018-01-01 11:23:09 by Thomas Klausner | Files touched by this commit (145)
Log message:
apache22: remove, it was eol'd in June 2017

Remove packages that only work with apache22.
Remove apache22 references.
   2017-12-17 16:38:23 by Adam Ciarcinski | Files touched by this commit (1) | Package updated
Log message:
PLIST should have also been updated
   2017-12-16 08:46:30 by Adam Ciarcinski | Files touched by this commit (2) | Package updated
Log message:
py-mod_wsgi: updated to 4.5.24

Version 4.5.24:
Bugs Fixed
Using mod_wsgi in daemon mode on Solaris would cause a process hang or max out \ 
CPU usage. Caused by change of variable type to unsigned to get rid of compiler \ 
warnings, without fixing how condition check using variable was done.

Problem could also affect non Solaris systems if total number of HTTP headers \ 
and other variables passed in WSGI environ was greater than 1024. Affected \ 
Solaris all the time due to it having a limit of only 16 in operating system for \ 
same code, meaning hit problem immediately.
   2017-12-14 14:25:22 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-mod_wsgi: updated to 4.5.23

Bugs Fixed
Incorrect check around whether apxs was present on system would result in pip \ 
install failing on Windows, and possibly also when using latest Xcode on MacOS \ 
X.
   2017-11-23 11:35:43 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-mod_wsgi: updated to 4.5.22

4.5.22:
Bugs Fixed:
Change in version 4.5.21 caused Windows builds to break with undefined symbol \ 
wsgi_daemon_shutdown.
   2017-10-11 09:17:38 by Adam Ciarcinski | Files touched by this commit (3) | Package updated
Log message:
py-mod_wsgi: update to 4.5.20

Version 4.5.20:
Bugs Fixed
Installation on MacOS X using setup.py or pip would fail if Xcode 9.0 was installed.
   2017-09-01 09:06:43 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
Version 4.5.18:
When using --url-alias with mod_wsgi-express and the target of the URL doesn’t \ 
exist, it will now be assumed that it will be a directory rather than a file, \ 
when finally created. This is to accomodate where may have used --setup-only \ 
option or setup-server command to pre-generate config files before the directory \ 
is created.
   2017-07-07 17:45:55 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
4.5.17:
Bugs Fixed
Addition in mod_wsgi-express of --allow-override option in 4.5.16 caused \ 
--url-alias option to break.

Next | Query returned 30 messages, browsing 11 to 20 | Previous