Community Cloud apt dependency error: bullseye-security InRelease is expired

Community Cloud
,
1

Hello Streamlit team,

My Streamlit Community Cloud app was working previously, but after rebuilding/redeploying it, the deployment fails while installing apt dependencies.

My app uses Python 3.11, OpenCV, MediaPipe, and Groq.

Repository:

Main file:
main.py

My packages.txt contains:

libgl1
libglib2.0-0t64
libsm6
libxext6

The deployment log shows:

📦 Apt dependencies were installed from .../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
Get:3 http://deb.debian.org/debian trixie-updates InRelease
Get:4 http://deb.debian.org/debian-security trixie-security InRelease

Reading package lists...

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

❗️ installer returned a non-zero exit code
❗️ Error during processing dependencies!

If I remove packages.txt, the deployment proceeds further but OpenCV then fails with:

ImportError: libGL.so.1: cannot open shared object file: No such file or directory

Could you please advise how I should resolve the expired Bullseye security repository issue on Community Cloud?

Thank you.

2

Welcome to the Streamlit community and thanks for sharing your detailed question and repo link! :tada: You’re running into a known issue: the expired bullseye-security repository is causing apt installs (via packages.txt) to fail, which then breaks OpenCV and MediaPipe since they need system libraries like libGL.so.1. This is a Streamlit Community Cloud infrastructure problem, not something you can fix from your end by tweaking packages.txt or requirements.txt alone. Removing packages.txt lets the build proceed, but then OpenCV fails due to missing system libraries, as you’ve seen.

The best practice is to keep only libgl1 in your packages.txt for OpenCV, and avoid adding libglib2.0-0 or similar, since those often fail due to missing dependencies in the current environment. However, when the underlying Debian repository is expired or misconfigured, even this won’t work. In these cases, the only workaround is to wait for the Streamlit team to update their base image or repository configuration. Deleting and redeploying the app sometimes helps if the issue is transient, but with an expired repo, it won’t resolve until Streamlit updates their infrastructure. For more, see the official docs and community troubleshooting threads: Streamlit Docs: App dependencies, libGL.so.1 troubleshooting, and community forum discussions.

Sources:

3

Hey @prakharbarsainya2

Thanks so much for flagging and sorry you’re dealing with this. No need to do anything on your end, this is is a wider issue the team is aware of and the fix is currently in the works! :rocket:

4

Hey @prakharbarsainya2 , thanks for reporting the issue to us! We have rolled out a new version to prod which should fix the issue! Please let us know if something is still not working and sorry for the inconvenience :slight_smile: