App URL: https://derasann-tour-reply-tour-portal-app-featuretour-portal-vdtsz1.streamlit.app
GitHub repo: Private repo, so I can’t share a public link. Relevant dependency files below.
requirements.txt:
streamlit
pandas
openpyxl
xlsxwriter
pillow
pypdf
reportlab
anthropic
jpholiday
python-pptx
pymupdf
gspread
google-auth
google-api-python-client
PyYAML
packages.txt:
libreoffice
Streamlit / Python version: Python 3.14 (set in app Settings). Streamlit version is unpinned in requirements.txt — the build fails during the apt step, before pip even installs Streamlit, so the resolved version is unknown.
Full error message:
[03:16:01] 
Starting up repository: ‘tour_reply’, branch: ‘feature/tour-portal’, main module: ‘tour_portal_app.py’
[03:16:01] 
Cloning repository…
[03:16:03] Cloning into ‘/mount/src/tour_reply’…
[03:16:03] Cloned repository!
[03:16:03] Pulling code changes from Github…
[03:16:04] 
Processing dependencies…
[03:16:04] Apt dependencies were installed from /mount/src/tour_reply/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]
Get:5 Index of /debian/11/prod/ bullseye InRelease [3650 B]
Get:6 Index of /debian-security trixie-security/main amd64 Packages [252 kB]
Get:7 Index of /debian/11/prod/ bullseye/main arm64 Packages [130 kB]
Get:8 Index of /debian/11/prod/ bullseye/main amd64 Packages [312 kB]
Reading package lists…
E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 6h3min0s). Updates for this repository will not be applied.
[03:16:05] 
installer returned a non-zero exit code
[03:16:05] Error during processing dependencies! Please fix the error and push an update, or try restarting the app.
What I’ve tried:
- Rebooting the app multiple times over several hours — same error each time.
- Changing the Python version setting (forces a fresh machine provision, not just a container restart) — still hits the exact same expired
bullseye-securityInRelease file.
Since this reproduces even on a freshly provisioned machine, it looks like an infra-side issue with the base build image’s apt sources, not something fixable from my app config.
