My Emacs configuration https://git.cjennings.net/dotemacs/atom?h=main 2026-08-25T12:30:04+00:00 2026-08-25T12:30:04+00:00 Craig Jennings c@cjennings.net 2026-08-25T12:30:04+00:00 urn:sha1:91fbac722e83cd108a295542a3c88de66d209fe8 MELPA's 2026-08-18 telega raised telega-tdlib-min-version to 1.8.66. The pinned upstream image ships 1.8.64, so telega killed its own server on every launch. Upstream's only 1.8.66 image won't start: it's missing libglycin (zevlg/telega.el#596). docker/telega-server/Dockerfile derives from that upstream image, pinned by digest, and adds the one missing package. make telega-image builds it as cj/telega-server:1.8.66-glycin, cj/telega-docker-image defaults to that tag, and a test holds the two equal. cj/telega now refuses to launch with a make telega-image hint when the image isn't built, since docker would otherwise try to pull a local-only tag from the registry. setup-telega.sh points at the make target instead of M-x telega-server-build. I chose the local build over pinning the telega package back to 20260706.2147. The derived image satisfies both machines' floors. package.el can't pin a version and MELPA serves only its latest build, so nothing would enforce the package pin. When #596 is fixed upstream the pin returns to a registry digest and the Dockerfile goes. 2026-08-25T00:43:05+00:00 Craig Jennings c@cjennings.net 2026-08-25T00:43:05+00:00 urn:sha1:ac1d034d09dd37305e84d08438fef268ed8173bc MELPA's 2026-08-18 telega build raised telega-tdlib-min-version to 1.8.66. The pinned zevlg/telega-server image ships 1.8.64, so telega kills its own server on every launch and nothing reports it. The note carries the measurements and why the armed death alert wasn't seen, which is still unmeasured. It also records why zevlg/telega-server:latest isn't a fix (zevlg/telega.el#596: missing libglycin), the derived image I verified, and the pinning decision I haven't made yet.