Your message dated Sat, 28 Feb 2026 18:30:36 +0200
with message-id <aaMYLMGxL6IvEkUY@localhost>
and subject line Fixed upstream in 1.8.0
has caused the Debian Bug report #1126698,
regarding tealdeer: 404 error
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1126698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126698
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tealdeer
Version: 1.7.2-1+b1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: [email protected]
Dear Maintainer,
`tldr --update` fails on debian stable due to a 404 error. I believe they
fixed this upstream in version 1.8.0. This renders the program just about
unusable as this has to be run to populate the database after installing.
If one has automatic updates, it becomes unusable even after initial
installation.
Thanks a bunch.
-- System Information:
Debian Release: 13.3
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.63+deb13-rt-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C.utf8, LC_CTYPE=C.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tealdeer depends on:
ii libc6 2.41-12+deb13u1
ii libgcc-s1 14.2.0-19
ii libssl3t64 3.5.4-1~deb13u2
tealdeer recommends no packages.
tealdeer suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.8.0-1
Fixed upstream (and in unstable) with 1.8.0.
cu
Adrian
--- End Message ---
