Deployment issue with Debian packages

Community Cloud
,
1

Hello,
My app, that has been working perfectly for many months now, could not be deployed easier today.
error log shows:

[22:08:16] 📦 Apt dependencies were installed from /mount/src/ks_sim/packages.txt using apt-get.

Hit:1 http://deb.debian.org/debian-security bullseye-security InRelease

Hit:2 http://deb.debian.org/debian trixie InRelease

Hit:3 http://deb.debian.org/debian trixie-updates InRelease

Hit:4 http://deb.debian.org/debian-security trixie-security InRelease

Hit:5 https://packages.microsoft.com/debian/11/prod bullseye InRelease

Reading package lists...[2026-09-07 22:08:17.586140]

E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 55min 12s). Updates for this repository will not be applied.

[22:08:17] ❗️ installer returned a non-zero exit code
I am trying to install the tesseract-orc packages.

Is there something that I can do?
Thank you very much in advance for the help!

2

Hey there, thanks for sharing your question and welcome to the community! :rocket: The error “Release file for … bullseye-security/InRelease is expired” means the Debian security repository’s metadata is out of date, so apt-get can’t fetch or install packages (like tesseract-ocr) from it. This is a server-side issue with the Debian repo, not your code or Streamlit config. You can’t fix this directly—it’s usually resolved when the repository maintainers update the release file, or when the Streamlit Community Cloud environment refreshes its package cache. For now, you can try rebooting or redeploying your app later.

If you want to double-check your setup: make sure tesseract-ocr is listed in packages.txt (not requirements.txt), and that packages.txt is in your repo’s root directory. For more info, see the official docs on apt-get dependencies and managing dependencies. If the issue persists after a few hours, check the Streamlit Community Cloud status page or the forum for updates. Community members, feel free to jump in if you’ve seen a workaround!

Sources:

3

Hey @Frak1,

Thanks so much for flagging! This is an issue the team is aware of and there’s currently a fix in flight! :rocket: