---

This section details on the original issue you should resolve

<issue_title>cannot access '/home/runner/cache-apt-pkgs/*.tar': No such file or directory</issue_title>
<issue_description>We're seeing this failure in one of our repositories. This repository is private, the exact same configuration appears to still work in public repositories. Those working repositories are also older though.

- uses: awalsh128/cache-apt-pkgs-action@latest
  with:
    packages: qemu-user qemu-user-static qemu-system-s390x gcc-s390x-linux-gnu gcc-i686-linux-gnu g++-s390x-linux-gnu
    version: 1.0

This gives the following output, where some errors are reported near the end, although the action as a whole does "succeed" in that no non-zero exit code is emitted:

Validating action arguments (version='1', packages='g++-s390x-linux-gnu=4:13.2.0-7ubuntu1 gcc-i686-linux-gnu=4:13.2.0-7ubuntu1 gcc-s390x-linux-gnu=4:13.2.0-7ubuntu1 qemu-system-s390x=1:8.2.2+ds-0ubuntu1.9 qemu-user=1:8.2.2+ds-0ubuntu1.9 qemu-user-static=1:8.2.2+ds-0ubuntu1.9')...
done

Creating cache key...
- CPU architecture is 'x86_64'.
- Value to hash is 'g++-s390x-linux-gnu=4:13.2.0-7ubuntu1 gcc-i686-linux-gnu=4:13.2.0-7ubuntu1 gcc-s390x-linux-gnu=4:13.2.0-7ubuntu1 qemu-system-s390x=1:8.2.2+ds-0ubuntu1.9 qemu-user=1:8.2.2+ds-0ubuntu1.9 qemu-user-static=1:8.2.2+ds-0ubuntu1.9 @ 1 3'.
- Value hashed as '6dccb7f633f210b4be418fe11245cfd7'.
done
Hash value written to /home/runner/cache-apt-pkgs/cache_key.md5
Run actions/cache/restore@v4
Cache hit for: cache-apt-pkgs_6dccb7f633f210b4be418fe11245cfd7
Received 516 of 516 (100.0%), 0.0 MBs/sec
Cache Size: ~0 MB (516 B)
/usr/bin/tar -xf /home/runner/work/_temp/f3b45cd8-9534-455e-a1ff-4db74837e43c/cache.tzst -P -C /home/runner/work/foo/bar --use-compress-program unzstd
Cache restored successfully
Cache restored from key: cache-apt-pkgs_6dccb7f633f210b4be418fe11245cfd7
Run ${GITHUB_ACTION_PATH}/post_cache_action.sh \
Found 3 files in the cache.
- cache_key.md5
- install.log
- manifest_main.log

Reading from main requested packages manifest...
- g++-s390x-linux-gnu=4 13.2.0-7ubuntu1
- gcc-i686-linux-gnu=4 13.2.0-7ubuntu1
- gcc-s390x-linux-gnu=4 13.2.0-7ubuntu1
- qemu-system-s390x=1 8.2.2+ds-0ubuntu1.9
- qemu-user-static=1 8.2.2+ds-0ubuntu1.9
- qemu-user=1 8.2.2+ds-0ubuntu1.9
done

ls: cannot access '/home/runner/cache-apt-pkgs/*.tar': No such file or directory
Restoring 0 packages from cache...
done

cat: /home/runner/cache-apt-pkgs/manifest_all.log: No such file or directory
/home/runner/work/_temp/a9039e66-1aec-493e-bc3d-b49c52ab4970.sh: line 8: -1: substring expression < 0

The packages are not installed:

Run i686-linux-gnu-gcc --version
/home/runner/work/_temp/7e1c1f5f-862e-480b-bfe5-5cc29ac6a8b3.sh: line 1: i686-linux-gnu-gcc: command not found

This looks a lot like #110, at least some of the reported errors are the same. That issue does seem fixed though?

I'm really not sure what is happening here. It might be our fault, although the action hitting an error but not failing is probably a bug at least?
</issue_description>

Comments on the Issue (you are @copilot in this section)

@awalsh128 This sounds very familiar to #116. #110 had a fix PR merged and released but needs confirmation. Check out the install part of the action. You can trigger this by changing the `version` input and it will create a different cache key. This will confirm if your issue is the same as #116.