Bug 224411 - Update port: www/mod_wsgi4 Upgrade to 4.5.24
Summary: Update port: www/mod_wsgi4 Upgrade to 4.5.24
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Wen Heping
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-18 00:48 UTC by Douglas Thrift
Modified: 2018-04-01 08:21 UTC (History)
1 user (show)

See Also:

Attachments
www/ap24-mod_wsgi4-4.5.24.diff (1.28 KB, patch)
2017-12-18 00:48 UTC, Douglas Thrift 		douglas: maintainer-approval+
Details | Diff
www/ap24-mod_wsgi-4.5.24.diff (500 bytes, patch)
2017-12-21 02:17 UTC, Douglas Thrift 		douglas: maintainer-approval+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Douglas Thrift 2017-12-18 00:48:01 UTC 
Created attachment 188918 [details]
www/ap24-mod_wsgi4-4.5.24.diff

Upgraded www/mod_wsgi to 4.5.24 [1].

[1] https://modwsgi.readthedocs.io/en/develop/release-notes/version-4.5.24.html

portlint: OK (0 fatal errors and 1 warning found.)
testport: OK (poudriere: 103i386, 103amd64, 111i386, 111amd64)
Comment 1 commit-hook freebsd_committer freebsd_triage 2017-12-21 01:25:38 UTC 
A commit references this bug:

Author: wen
Date: Thu Dec 21 01:25:20 UTC 2017
New revision: 456879
URL: https://svnweb.freebsd.org/changeset/ports/456879

Log:
  - Update to 4.5.24

  PR:		224411
  Submitted by:	douglas@douglasthrift.net(maintainer)

Changes:
  head/www/mod_wsgi4/Makefile
  head/www/mod_wsgi4/distinfo
Comment 2 Wen Heping freebsd_committer freebsd_triage 2017-12-21 01:27:11 UTC 
Hi, Douglas:

  Since there is no mod_wsgi3 now, would you remove the CONFLICTS and PKGNAMESUFFIX lines ?

wen
Comment 3 Douglas Thrift 2017-12-21 02:17:45 UTC 
Created attachment 189005 [details]
www/ap24-mod_wsgi-4.5.24.diff

Wen, I have attached a patch to do that.
Comment 4 Douglas Thrift 2018-04-01 08:21:11 UTC 
comment #2 is addressed in bug #227160 as well.