Cirrus: Strip out static nix build

Unfortunately the maintainer of this is no longer available

Signed-off-by: Chris Evich <cevich@redhat.com>

.cirrus.yml

@@ -323,36 +323,6 @@ alt_build_task:
     always: *binary_artifacts
 
 
-# Confirm building a statically-linked binary is successful
-static_alt_build_task:
-    name: "Static Build"
-    alias: static_alt_build
-    only_if: *not_docs
-    depends_on:
-        - build
-    # Community-maintained task, may fail on occasion.  If so, uncomment
-    # the next line and file an issue with details about the failure.
-    # allow_failures: $CI == $CI
-    gce_instance: *bigvm
-    env:
-        <<: *stdenvars
-        TEST_FLAVOR: "altbuild"
-        # gce_instance variation prevents this being included in alt_build_task
-        ALT_NAME: 'Static build'
-        # Do not use 'latest', fixed-version tag for runtime stability.
-        CTR_FQIN: "docker.io/nixos/nix:2.3.6"
-        # Authentication token for pushing the build cache to cachix.
-        # This is critical, it helps to avoid a very lengthy process of
-        # statically building every dependency needed to build podman.
-        # Assuming the pinned nix dependencies in nix/nixpkgs.json have not
-        # changed, this cache will ensure that only the static podman binary is
-        # built.
-        CACHIX_AUTH_TOKEN: ENCRYPTED[df0d4d0a67474e8ea49cc503221dcb912b7e2ba45c8ec4bf2e5fd9c49a18ac21c24bacee59b5393355ed9e4358d2baef]
-    setup_script: *setup
-    main_script: *main
-    always: *binary_artifacts
-
-
 # Confirm building the remote client, natively on a Mac OS-X VM.
 osx_alt_build_task:
     name: "OSX Cross"
@@ -734,7 +704,6 @@ success_task:
         - swagger
         - consistency
         - alt_build
-        - static_alt_build
         - osx_alt_build
         - docker-py_test
         - unit_test

RELEASE_PROCESS.md

@@ -241,15 +241,11 @@ spelled with complete minutiae.
       * `Cirrus CI / Alt Arch. Cross` - tarball for each architecture
       * `Cirrus CI / OSX Cross` - two zip files (amd64 and arm64)
       * `Cirrus CI / Windows Cross` - an `msi` file
-      * `Cirrus CI / Static Build` - the `bin/podman-remote` file
 
       Under the "Artifacts" section of each task, click the "gosrc" link,
       find and download the release archive (`zip`, `tar.gz` or `.msi`).
       Save the the archive with a meaningful name, for example
       `podman-v3.0.0.msi`.
-   1. For the "Static Build" task, find the compiled `podman` and `podman-remote`
-      binaries under the "binary", then "bin" links.  Tar these files as
-      `podman-static.tar.gz`.
    1. The `podman-vX.Y.Z.dmg` file is produced manually by someone in
       possession of a developer signing key.
    1. In the directory where you downloaded the archives, run
@@ -267,7 +263,6 @@ spelled with complete minutiae.
 
       * podman-remote-release-darwin.zip
       * podman-remote-release-windows.zip
-      * podman-remote-static.tar.gz
       * podman-vX.Y.Z.msi
       * shasums
    1. Save the release.