Blair Noctis

Thanks for the detailed analysis. Some rough thoughts: - "Encode" package version info in HTML page **creation** time, and compare it with man page "last updated" time, leaving modification time...

https://tracker.debian.org/pkg/bacon Unstable only yet.

Now it's in testing and, after the freeze, will be part of Debian 13/trixie.

Basically building any project that depends on some -sys crate, that is, a C/C++ shared library, without first installing such a library. A minimal reproducer is an empty `cargo new`...

Uh, this "reproducer" actually correctly showed "Command error code: 101". My case was [ripasso](https://github.com/cortex/ripasso), which requires a clone but works to demonstrate the problem.

Hmm, this seems to happen fairly intermittently, and the problem actually lies in cargo, which occasionally returns with status code 0 even when there are errors. Should be directed to...

That "kludge" dates back to 2007, so it's probably unlikely to be (by itself) the culprit. Unsure how much programmatical use less (and zstdless) gets... to have a significant impact...

Hmm, I seem to have mistakenly assumed it's OK to only listen for interrupt if the duration is known. The sound is then not played at all, not yet sure...

> Alternatively we could ask the use for a max duration to play from the sound. Sure could do, add an option `duration` to `[sound.collection]` entries and maybe the `play-sound`...

The culprit of rodio being unable to read duration should be https://github.com/RustAudio/rodio/issues/696, fixed in https://github.com/RustAudio/rodio/pull/697, merged early last month. I've asked if they could release it to avoid a git+rev...