| non port: www/py-django22/Makefile |
Number of commits found: 40 |
|
Thursday, 30 Jun 2022
|
19:54 Rene Ladan (rene) 
cleanup: Remove expired ports:
2022-06-30 www/py-django22: Django 2.2 is now in Extended Support, receives
security fixes only and will reach End-Of-Life on 2022-04-01. Upgrade to a later
Django version. See https://www.djangoproject.com/download/
2022-06-30 www/py-jsonfield2: Obsolete, please use www/py-jsonfield instead
    56dc108 |
|
Tuesday, 12 Apr 2022
|
00:43 Wen Heping (wen)
www/py-django22: Update to 2.2.28
aa35fb1 |
|
Thursday, 10 Feb 2022
|
05:57 Wen Heping (wen)
www/py-django22: Update to 2.2.27
2f4bd2f |
|
Tuesday, 18 Jan 2022
|
17:34 Kai Knoblich (kai)
www/py-django22: Deprecate and set to expire
Set a deprecation note and let it expire to the end of June to give
enough time to switch all affected ports over to Django 3.2 which is the
next LTS release.
PR: 261313
Reviewed by: koobs
Approved by: dbaio, sunpoet (python, maintainer)
Differential Revision: https://reviews.freebsd.org/D33793
75cf1a4 |
|
Monday, 10 Jan 2022
|
15:15 Stefan Eßer (se)
Fix CONFLICTS entries of multiple ports
There have been lots of missing CONFLICTS_INSTALL entries, either
because conflicting ports were added without updating existing ports,
due to name changes of generated packages, due to mis-understanding
the format and semantics of the conflicts entries, or just due to
typoes in package names.
This patch is the result of a comparison of all files contained in
the official packages with each other. This comparison was based on
packages built with default options and may therefore have missed
further conflicts with optionally installed files.
Where possible, version numbers in conflicts entries have been
generalized, some times taking advantage of the fact that a port
cannot conflict with itself (due to logic in bsd.port.mk that
supresses the pattern match result in that case).
A few ports that set the conflicts variables depending on complex
conditions (e.g. port options), have been left unmodified, despite
probably containing outdated package names.
These changes should only affect the installation of locally built
ports, not the package building with poudriere. They should give an
early indication of the install conflict in cases where currently
the pkg command aborts an installation when it detects that an
existing file would be overwritten,
Approved by: portmgr (implicit)
bcaf25a |
|
Wednesday, 5 Jan 2022
|
06:16 Wen Heping (wen)
www/py-django22: Update to 2.2.26
1c78d85 |
|
Thursday, 9 Dec 2021
|
01:52 Wen Heping (wen)
www/py-django22: Update to 2.2.25
77f4b2d |
|
Wednesday, 22 Sep 2021
|
02:39 Wen Heping (wen)
www/py-django22: Remove django111 from CONFLICTS_INSTALL
418da1c |
|
Wednesday, 30 Jun 2021
|
20:44 Po-Chuan Hsieh (sunpoet)
www/py-django22: Update to 2.2.24
Changes: https://docs.djangoproject.com/en/2.2/releases/
94b1300 |
|
Wednesday, 5 May 2021
|
07:25 Wen Heping (wen)
www/django{22,31,32} : Update django to 3.2.1, 3.1.9 and 2.2.21
d98ab32 |
|
Sunday, 11 Apr 2021
|
23:48 Wen Heping (wen)
Add new port: www/py-django32
Update CONFLICTS
0ee9911 |
|
Thursday, 8 Apr 2021
|
02:48 Wen Heping (wen)
- Update www/py-django to 3.1.8, 3.0.14 and 2.2.20
9530284 |
|
Tuesday, 6 Apr 2021
|
14:31 Mathieu Arnold (mat)
Remove # $FreeBSD$ from Makefiles.
305f148 |
|
Saturday, 20 Mar 2021
|
22:13 dbaio
www/py-django*: Fix build (extract) with static bsdtar(1)
===> Extracting for py37-django22-2.2.19
=> SHA256 Checksum OK for python/Django-2.2.19.tar.gz.
tar: Pathname can't be converted from UTF-8 to current locale.
tar: Error exit delayed from previous errors.
===> Failed to extract "/portdistfiles/python/Django-2.2.19.tar.gz".
*** Error code 1
See more details for the same issue in bug 246618 and
https://portsfallout.com/fallout?port=www%2Fpy-django
Reported by: pkg-fallout
Approved by: portmgr blanket
  |
|
Sunday, 21 Feb 2021
|
07:45 wen
- Update django to 3.1.7, 3.0.13 and 2.2.19(security releases)
MFH: 2021Q1
|
|
Friday, 5 Feb 2021
|
12:29 wen
- Update Django to 3.1.6, 3.0.12 and 2.2.18
(include security fix of CVE-2021-3281)
MFH: 2021Q1
|
|
Thursday, 14 Jan 2021
|
14:34 dbaio
Remove PY_SPHINX from ports using Python 3
Approved by: portmgr blanket
Differential Revision: https://reviews.freebsd.org/D28093
|
|
Tuesday, 3 Nov 2020
|
01:00 wen
- Update to django to 3.1.3, 3.0.11 and 2.2.17(bugfix releases)
MFH: 2020Q4
|
|
Saturday, 5 Sep 2020
|
21:35 sunpoet
Update to 2.2.16
Changes: https://docs.djangoproject.com/en/2.2/releases/
Security: 002432c8-ef6a-11ea-ba8f-08002728f74c
MFH: 2020Q3
|
|
Wednesday, 5 Aug 2020
|
02:10 wen
- Update to 2.2.15(bugfix release)
- Adjust CONFLICTS to welcome Django31
MFH: 2020Q3
|
|
Friday, 3 Jul 2020
|
11:50 wen
- Update to 2.2.14
|
|
Thursday, 4 Jun 2020
|
13:59 wen
- Update django to 3.0.7 and 2.2.13
- Remove django21 from CONFLICTS_INSTALL
MFH: 2020Q2
Security: CVE-2020-13254, CVE-2020-13596
|
|
Monday, 11 May 2020
|
23:51 dbaio
Update Sphinx
- Repocopy textproc/py-sphinx to textproc/py-sphinx18
Update it to 1.8.5 (latest version from 1.8.X).
This version supports Python 2 and 3.
Add test target.
- textproc/py-sphinx: Update to 3.0.2
Python 3 only (3.5+).
Add test target.
- Mk/Uses/python.mk: Add PY_SPHINX
Shared macro to use with flavors and not break
ports with USES=python (all versions).
Python >=3.5 --> textproc/py-sphinx (v3.0.2)
Python < 3.5 --> textproc/py-sphinx18 (v1.8.5)
All ports that uses sphinx were changed to use the new variable
${PY_SPHINX} in the dependency line, exceptions:
* Ports that fails to build with sphinx 3.0.2 because of code.
They are pointing to textproc/py-sphinx18 directly.
There aren't many ports.
* Ports that doesn't know Python flavors.
- Add several patches to fix Sphinx consumers
The most common issues are related with pkg-plist, the output
files from Sphinx changes between versions, keep this dynamically
is the better approach.
This will save time in future sphinx updates.
PR: 245629
Exp-run by: antoine
|
|
Wednesday, 1 Apr 2020
|
12:15 wen
- Update django to 3.0.5 and 2.2.12
|
|
Thursday, 12 Mar 2020
|
01:09 wen
- Update Django to 3.0.4, 2.2.11 and 1.11.29(security release)
MFH: 2020Q1
Security: CVE-2020-9402
|
|
Tuesday, 4 Feb 2020
|
18:17 sunpoet
Update to 2.2.10
Changes: https://docs.djangoproject.com/en/2.2/releases/
Security: 5a45649a-4777-11ea-bdec-08002728f74c
MFH: 2020Q1
|
|
Saturday, 4 Jan 2020
|
16:29 fluffy
www/py-django[22|30]: Unbreak with MySQL, switch to py-mysqlclient
According to official docs, mysqlclient >=1.3.13 is the recommended
choice instead of outdated pyMySQLdb
PR: 243077
Submitted by: fluffy
Approved by: sunpoet (maintaner, python@)
MFH: 2020Q1
|
|
Thursday, 19 Dec 2019
|
13:52 wen
- Update Django to 1.11.27, 2.2.9 and 3.0.1
(include security fix)
MFH: 2019Q4
Security: CVE-2019-19844
|
|
Tuesday, 3 Dec 2019
|
00:06 wen
- Adjust CONFLICTS_INSTALL to welcome py-django30
|
|
Monday, 2 Dec 2019
|
13:40 wen
- Update py-django22 to 2.2.8 and py-django21 to 2.1.15
(security fix: CVE-2019-19118)
MFH: 2019Q4
|
|
Wednesday, 6 Nov 2019
|
02:26 wen
- Update django to 2.2.7, 2.1.14 and 1.11.26
|
|
Wednesday, 2 Oct 2019
|
01:08 wen
- Update Django to 2.2.6, 2.1.13 and 1.11.25
|
|
Tuesday, 3 Sep 2019
|
19:12 sunpoet
Update to 2.2.5
Changes: https://docs.djangoproject.com/en/2.2/releases/
|
|
Thursday, 8 Aug 2019
|
09:52 wen
- Add TEST_DEPENDS and do-test
|
|
Saturday, 3 Aug 2019
|
20:57 sunpoet
Update to 2.2.4
Changes: https://docs.djangoproject.com/en/2.2/releases/
Security: 6e65dfea-b614-11e9-a3a2-1506e15611cc
MFH: 2019Q3
|
|
Monday, 1 Jul 2019
|
13:46 wen
- Update Django to 1.11.22, 2.1.10 and 2.2.3
(include security fix)
MFH: 2019Q3
|
|
Monday, 3 Jun 2019
|
14:01 wen
- Update Django to 1.11.21, 2.1.9 and 2.2.2(security releases)
MFH: 2019Q2
|
|
Friday, 31 May 2019
|
10:28 sunpoet
Update CONFLICTS_INSTALL
|
|
Thursday, 2 May 2019
|
07:13 wen
- Update to 2.2.1
|
|
Monday, 1 Apr 2019
|
23:45 wen
- Repocopy www/py-django21 --> www/py-django22 and update to 2.2
|
Number of commits found: 40 |
As an Amazon Associate I earn from qualifying purchases.