Exercise 1: Debian Stable's "Old" Package Versions — Possible Solution
====================================================================

WHY THIS ISN'T A BUG
------------------------------
Per this chapter's own warn-box, "someone installing Debian Stable
expecting the newest release of a language runtime or application will
often find something noticeably behind what's available elsewhere -
this is the frozen-at-release-time trade-off working exactly as
intended, not a sign of neglect." Debian Stable deliberately freezes
package versions at the moment of release and only issues security
patches afterward, per this chapter's own three-tier pipeline
explanation - the older version the user is seeing is the direct,
intended result of that freeze, not an oversight or a maintenance gap.

WHY THE FREEZE IS A DELIBERATE CHOICE, NOT AN ACCIDENT
------------------------------
Per this chapter, "boring" is Debian's own explicitly "stated,
deliberate value - stability chosen consciously over freshness." A
multi-year support window built around a frozen, well-tested baseline
necessarily means the software inside it ages relative to upstream
releases that continue moving forward - this is the direct, expected
cost of the stability Debian Stable is specifically built to provide.

THE TWO REAL OPTIONS WITHOUT ABANDONING STABLE ENTIRELY
------------------------------
Per this chapter, "real workarounds exist for genuinely needing
something newer without abandoning Stable entirely: the official
backports repository, or app-sandboxing formats like Flatpak, both
covered further in Chapter 6." The backports repository offers newer
versions of specific packages, built against the current Stable release
rather than requiring the whole system to move to Testing or Unstable.
Flatpak (and similar sandboxed formats) install a newer version of a
specific application in its own isolated environment, independent of
the base system's own frozen package versions entirely.

WHY THIS IS BETTER THAN SWITCHING TO TESTING OR UNSTABLE OUTRIGHT
------------------------------
Both options let the user get a specific newer piece of software without
giving up Stable's own broader reliability guarantee for the rest of
the system - switching the whole machine to Testing or Unstable, by
contrast, would trade away exactly the stability the user presumably
chose Debian Stable for in the first place, just to gain one or two
newer packages.

WHY THIS WORKS AS AN ANSWER
------------------------------
It explains why the older version is the intended result of a
deliberate, named design choice rather than a bug, and names the two
specific alternatives this chapter identifies for getting newer
software without sacrificing Stable's own reliability guarantee.