Skip to content

django: Security update to 1.3.2 and 1.4.1.#78

Merged
7c6f434c merged 2 commits intoNixOS:masterfrom
aszlig:django-security-update
Aug 1, 2012
Merged

django: Security update to 1.3.2 and 1.4.1.#78
7c6f434c merged 2 commits intoNixOS:masterfrom
aszlig:django-security-update

Conversation

@aszlig
Copy link
Member

@aszlig aszlig commented Jul 31, 2012

Django 1.4.0 and 1.3.1 have serious security vulnerabilities which are addressed in those releases, for details, please see:

https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/

Django 1.4.0 and 1.3.1 have serious security vulnerabilities which are addressed
in those releases, for details, please see:

https://www.djangoproject.com/weblog/2012/jul/30/security-releases-issued/
@7c6f434c
Copy link
Member

7c6f434c commented Aug 1, 2012

Maybe add a django_1_3 attribute so that not every update like that needs manual action by every user for clean update?

@aszlig
Copy link
Member Author

aszlig commented Aug 1, 2012

okay, makes sense...

The django team tries very hard to not introduce backwards-incompatible changes
into patch versions, so I guess it is safe to only use the major and minor
version number for specific Django versions.

This way, it doesn't require manual action by users who have added django_1_3_*
into system packages or local overrides/custom derivations.

Thanks to @7c6f434c for the suggestion.
7c6f434c added a commit that referenced this pull request Aug 1, 2012
django: Security update to 1.3.2 and 1.4.1.
@7c6f434c 7c6f434c merged commit dda816b into NixOS:master Aug 1, 2012
@veprbl veprbl mentioned this pull request May 31, 2020
10 tasks
Profpatsch pushed a commit that referenced this pull request Jun 20, 2020
Fix unusable Lenovo Thinkpad X1 profile
notklea pushed a commit to notklea/nixpkgs that referenced this pull request Dec 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants