For the source patch 0001-add-worker-abort-hook.patch, it is not used.
For the 3 meta patches, only 0001-TIS-gunicorn-19-upgrade.patch is
applied to srpm. And this meta patch just add tis version, and disable
python3 compilation. So it is ok to drop all these patches, and use
rpm to replace srpm.
Story: 2005484
Task: 30578
Depends-On: https://review.opendev.org/653908
Change-Id: I5805cce1dc64dd41be9f415bab985b34791f1506
Signed-off-by: Shuicheng Lin <shuicheng.lin@intel.com>
We have switched to using vanilla django 1.11, and no longer require
these patches
Change-Id: I5830615bf357e9a06a4518adaccd2bcffb7d00be
Story: 2004765
Task: 28883
Depends-On: https://review.openstack.org/#/c/642797
Signed-off-by: Tyler Smith <tyler.smith@windriver.com>
One fuzzy issue introduced in
https://review.openstack.org/#/c/597433/
smart-recommends.patch line 1164
It will cause build issue!
Change patch error and build pass
Closes-Bug: 1801685
Change-Id: I31d23a6287f8eff53fa26c95914ed8b80a8ed7a9
Signed-off-by: zhipengl <zhipengs.liu@intel.com>
In Python 3 print is a function.
Especially for multiple string print, need to import
print_function from __future__.
Story: 2002909
Task: 24560
Signed-off-by: zhangyangyang <zhangyangyang@unionpay.com>
Change-Id: Ie31eb59368af57776eb9785dba494432111cd250
When do Centos 7.5 upgraded, some patches didn't resolve and cause
the fuzzy in the line numbers of the patches. And it may cause
.orig file is created when do patch. And this .orig file will lead
to rpm packaging failure due to the unexpected and unpackaged .orig
file.
Please visit below link to get more detail info:
https://bugs.launchpad.net/starlingx/+bug/1794611
Solution:
Safest solution is to de-fuzz our patches.
Story: 2003389
Task: 26755
Change-Id: Iaf55ba860a02ea096b7cfbfd9b810cc51de18580
Signed-off-by: slin14 <shuicheng.lin@intel.com>
