remove py3-pywinpty which should never have been added, as it require… (

#36706) We had a failing package update PR that popped up in sustaining: - #31028 On closer inspection, this was a win32 package, and should never have been added to wolfi. Whilst it may have been compiling before, it was non-functional. It's highly likely it was wrongly imported when jupyter-server was built / imported. **Please see the following GH issue comments for more information:** - #31028 (comment) This PR cleans up the package, as well as adds it to the withdrawn list. There are no other packages (in wolfi or elsewhere), or images with dependencies on this broken package. Signed-off-by: Mark McCormick <[email protected]>
wolfi-dev · Dec 13, 2024 · ff38257 · ff38257
1 parent e995645
commit ff38257
Show file tree

Hide file tree

Showing 3 changed files with 1 addition and 82 deletions.
diff --git a/py3-jupyter-server.yaml b/py3-jupyter-server.yaml
@@ -20,7 +20,6 @@ package:
       - py3-overrides
       - py3-packaging
       - py3-prometheus-client
-      - py3-pywinpty
       - py3-pyzmq
       - py3-send2trash
       - py3-terminado

diff --git a/py3-pywinpty.yaml b/py3-pywinpty.yaml
diff --git a/withdrawn-packages.txt b/withdrawn-packages.txt
@@ -11,3 +11,4 @@ repmgr-5.5.0-r2.apk
 repmgr-dev-5.5.0-r3.apk
 repmgr-5.5.0-r3.apk
 repmgr-bitnami-compat-5.5.0-r3.apk
+py3-pywinpty-2.0.13-r3.apk