App deployment failing - "Release file for bullseye-security is expired"

Community Cloud
, ,
1

Título: App deployment failing - “Release file for bullseye-security is expired”

Corpo:
My app has been failing to deploy for over 24 hours with the following error during the apt dependencies installation step:

E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 1d 3h+ and counting). Updates for this repository will not be applied.

App URL: iaagro-app-kvrwxtkugla8pqe7dgqeue.streamlit.app
Repo: luciano880/iaagro-app (branch: main)

My packages.txt just contains:
tesseract-ocr
tesseract-ocr-por
libgl1
libzbar0

I’ve tried:

  • Rebooting the app multiple times
  • Deleting and redeploying the app from scratch

Same error every time. This seems to be an issue with the apt mirror/base image used by Streamlit Cloud, not with my repository. Could someone from the Streamlit team take a look?

Full log:
[00:46:42] Processing dependencies…
[00:46:42] Apt dependencies were installed from /mount/src/iaagro-app/packages.txt using apt-get.
Hit:1 Index of /debian-security bullseye-security InRelease
Hit:2 Index of /debian trixie InRelease
Get:3 Index of /debian trixie-updates InRelease [47.3 kB]
Get:4 Index of /debian-security trixie-security InRelease [43.4 kB]
E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 1d 3h 33min 38s). Updates for this repository will not be applied.
[00:46:43] installer returned a non-zero exit code
[00:46:43] Error during processing dependencies!

2

Hey there, thanks for sharing your question and all those helpful details (and welcome if this is your first post! :balloon:). The error “Release file for bullseye-security is expired” during apt dependencies installation is due to the Debian security repository’s InRelease file being expired, which is an upstream issue with the Debian mirror used by Streamlit Community Cloud—not a problem with your code or packages.txt.

This issue has affected many users recently and is not something you can fix from your end. The best course of action is to wait for the Streamlit team (or the Debian maintainers) to refresh the repository metadata. In the past, similar issues have been resolved automatically after some time, or after the Streamlit team updates their base images. You can track status or report the issue on the Streamlit forums if you haven’t already, but no workaround is available until the repository is updated. For more on apt dependencies and related errors, see the official docs.

Sources: