Trixie/ bulleyes deployment issue

Community Cloud
1

Hi Streamlit Team,

I’m encountering a persistent deployment error on Streamlit Community Cloud due to an expired InRelease file for the bullseye-security repository. This is blocking the installation of my dependencies (poppler-utils, tesseract-ocr, libtesseract-dev), even though they are available in trixie.

Error Logs:

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
E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 48min 26s). Updates for this repository will not be applied.

What I’ve Tried:

  • Modified packages.txt to use only trixie-compatible packages.
  • Added commands to ignore expiration (Acquire::Check-Valid-Until=false).
  • Used alternative mirrors (e.g., archive.debian.org).
  • Created a pre_install.sh script (not executed by the build system).

Request:
Could you remove or update the bullseye-security repository from the Streamlit Community Cloud build environment? Alternatively, is there a way to force the use of trixie only for dependency installation?

Context:
My app requires poppler-utils, tesseract-ocr, and libtesseract-dev, all of which are available in trixie. The bullseye-security repository is unnecessary for my deployment and is causing the failure.

Thank you for your help—I’d greatly appreciate a quick resolution!

Best regards,

Frak

2

Hey Frak, thanks for reaching out and for the detailed error logs—super helpful! :rocket: It seems likely that this issue is due to Streamlit Community Cloud’s build environment being pinned to Debian Bullseye, and the expired bullseye-security InRelease file is blocking apt operations. Unfortunately, users can’t remove or override the default repositories or force apt to use only trixie; the build environment and its sources are managed by Streamlit and not customizable per app. Attempts like using pre_install.sh or custom apt flags aren’t supported in the current deployment workflow.

My understanding is that the best workaround (for now) is to wait for the Streamlit team to update the base image or repository configuration. In the past, similar issues were resolved by the Streamlit team updating their infrastructure, and sometimes deleting and redeploying the app after a fix is rolled out helps. If you haven’t already, please share your minimum reproducible example and repo link in the forum so others can chime in or upvote. For more info, see the discussion in the community forums and the official docs on dependency management and status/limitations.

Sources:

3

Hey @Frak1 , 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:

4

Hello,
Thank you very much. I have re-activated my packages.txt and everything is back to normal!
:slight_smile: