newt: Remove python_init_once.patch

It was pointed out in #11504 that the code in python_init_once.patch is
incorrect; the patch does not prevent newtInit() from being called more
than once (in fact it is called twice the first time initScreen() is
called).

Testing without the patch, using the example code from the corresponding
Debian bug report[1], did not result in any segfaults.

This removes the patch from the package build.

Supersedes #11504.

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557960#5

Signed-off-by: Jeffery To <jeffery.to@gmail.com>

1 files changed, 0 insertions, 24 deletions

diff --git a/libs/newt/patches/python_init_once.patch b/libs/newt/patches/python_init_once.patch
deleted file mode 100644
index 3d52b4486..000000000
--- a/libs/newt/patches/python_init_once.patch
+++ /dev/null
@@ -1,24 +0,0 @@
-Author: Alastair McKinstry <mckinstry@debian.org>
-Description: newtInit() should only be called once
-Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557960
-Forwarded: no
-Last-Updated: 2014-06-11
-
---- a/snack.c
-+++ b/snack.c
-@@ -377,10 +377,15 @@ static snackWidget * snackWidgetNew (voi
- }
- 
- static PyObject * initScreen(PyObject * s, PyObject * args) {
-+    static int init_newt = 1;
-     suspend.cb = NULL;
-     suspend.data = NULL;
-     
-     newtInit();
-+    if (init_newt) { 
-+	newtInit();
-+	init_newt = 0;
-+    }
-     newtCls();
- 
-     Py_INCREF(Py_None);