"If someone started reading all the package descriptions and READMEs we're meant to be thoroughly familiar with when Trixie was released a few days ago, they'd still be reading them."

Another option might be to reduce the amount of software one is "blindly"^1 using and relying upon

For example, I have been making own Linux distribution, not following Linux from Scratch (although that is a useful reference)

This is for both learning but also reliability and robustness purposes (where "robustness" includes ability to recover quickly from losing everything)

IME starting from scratch gives a better appreciation for the "inconveniences" that maintainers must endure

"Inconvenience" may be putting it mildly

Certainly, the inconvenience varies depending on the software

Some software builds even on the most deficient/broken installations

Other software is absurdly difficult to compile, often due to minor oversights, sometimes due to obivous carelessness

The wild inconsistencies from one project to another is itself part of the inconvenience

The ease with which software can be compiled by me, and presumably anyone else, on any computer, including underpowered ones, with minimal dependencies, is among the factors I consider when choosing whether to rely on any particular software

1. Here "blindly" means the user has zero curiosity about where it comes from or how it works

No comment on this particular software or the Debian maintainer

I have up on X11 many years ago

I never liked that Debian maintainers make subjective, opinionated changes to other peoples' software, especially since it seems like the majority of Debian users do not compile from source