Project

Profile

Help

Actions
Send by e-mail Copy link

Backport #8758

closed

Backport 8691 to pulpcore 3.11

Added by newswangerd over 3 years ago. Updated over 3 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
bmbouter
Category:
-
Sprint/Milestone:
3.11.2
Start date:
Due date:
% Done:

100%

Estimated time:
Triaged:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 97
Quarter:

Description

We'd like to have https://pulp.plan.io/issues/8691 backported to 3.11 so we can use django 2.2.23 with galaxy_ng 4.3 for execution environments.

Related issues

Related to Pulp - Issue #8691: Pulp fails against django 2.2.21CLOSED - CURRENTRELEASEbmbouterActions
Actions
Copy link
 #1

Updated by fao89 over 3 years ago

  • Triaged changed from No to Yes
  • Sprint set to Sprint 97
Actions
Copy link
 #2

Updated by fao89 over 3 years ago

  • Assignee set to bmbouter
Actions
Copy link
 #3

Updated by pulpbot over 3 years ago

  • Status changed from NEW to POST

Added by bmbouter over 3 years ago

Revision fb5e0602 | View on GitHub

Fixes Pulp compatability with Django 2.2 LTS

Adjusts the upload machinery to be compatible with Django 2.2.21+. The 2.2.21 release was too strict in its checking, and 2.2.23 loosen it, so we require 2.2.23 with this PR.

backports #8691

fixes #8758

(cherry picked from commit 446fc631cd148acd79a40ed0ee57c79e68f0b8c5)

Actions
Copy link
 #5

Updated by bmbouter over 3 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by bmbouter over 3 years ago

  • Sprint/Milestone set to 3.11.2
Actions
Copy link
 #7

Updated by bmbouter over 3 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Copy link
 #8

Updated by ttereshc over 3 years ago

  • Related to Issue #8691: Pulp fails against django 2.2.21 added
Actions
Send by e-mail Copy link

Also available in: Atom PDF