Deployment fails: "Release file for debian-security/bullseye-security is expired"

Community Cloud
1

If you’re creating a debugging post, please include the following info:

  1. Share the link to the public app (deployed on Community Cloud).
  2. Share the link to your app’s public GitHub repository (including a requirements file).
  3. Share the full text of the error message (not a screenshot).
  4. Share the Streamlit and Python versions.

My app deployment is failing during the apt dependency installation step with this error:

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

This happens on every reboot attempt (tried twice). My packages.txt hasn’t changed
recently, so this looks like an infrastructure-level issue with the build environment’s
base image still referencing the old “bullseye” Debian suite.

App: mockup-home-page-dvc6pnckaptrkivfbvgicp.streamlit.app

2

Hey, thanks for sharing all the details and welcome to the Streamlit community! :rocket: The error E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 7h+) is an infrastructure-level issue with the Debian package repository used by Streamlit Community Cloud. This isn’t caused by your app or packages.txt, but rather by the upstream Debian security repo’s metadata expiring, which prevents apt from installing dependencies during deployment.

This type of issue has occurred before and is resolved on the Streamlit side when the base image or repository metadata is refreshed. There’s no action needed on your end except to wait for the Streamlit team or Debian maintainers to update the repository. For more info, see similar reports and resolutions in the forum: Deployment error: package.txt, Debian repo bullseye-security changed its codename, and App dependencies for your Community Cloud app.

Sources:

3

Hey @wenwenfu621,

Thanks so much for flagging. Yep, this is a wider issue… the team is aware of it and the fix is currently in the works! :rocket:

4

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