Upgrade your desktop: Ubuntu 26.04.1 LTS is now available
Thread
Unofficial Hacker News client; not affiliated with Y Combinator.
Upgrade your desktop: Ubuntu 26.04.1 LTS is now available
Unofficial Hacker News client; not affiliated with Y Combinator.
edelbitter · · focus · HN ↗
While most data loss severity bugs reported in the 25.10 round of testing [1] have been resolved, the sheer volume of unexpected breakage suggests that there are more to be discovered. Most impacted are unit tests and shell scripts that expect some utility to return syscall errors in stderr and propagate it to a non-zero exit code, where on Ubuntu 26.04 they might silently swallow (apparent, partial or complete) failure to execute the requested action.
(Also, uutils binaries are ridiculously large, but this is not such big deal: Ubuntu has for many years already built rather large initramfs and has yet to make progress in automatically detecting which firmware blobs cannot possibly be needed on a given system. I did run into an "undersized" partition layout because of Rust duplication.. but only on systems upgraded from ancient times before this was the norm.)
[1]: <a href="https://github.com/uutils/coreutils/issues?q=is%3Aissue+%28label%3Areported-canonical+OR+label%3Areported-canonical-2%29" rel="nofollow">https://github.com/uutils/coreutils/issues?q=is%3Aissue+%28l...
edelbitter · · focus · HN ↗
To get where they are now, uutils needed to do the thing nobody bothered to do for 30 years: proper cli unit tests, the kind with which you can compare busybox/toybox/GNU/uutils/Darwin without depending on implementation details [2]. This will net more future good than current harm. Even if the tools cannot be changed to have fewer nonsensical edge cases for compatibility reasons, at least now I can ask $currentLLM to write me a better manpage, one that includes the gotchas [3] and factual errors that the 1996 (partly updated in 2004) version still fails. And improve shellcheck so even those among future generations that still need the shell as we know it today are not bitten by its warts as much.
[1]: <a href="https://safereddit.com/r/copypasta/comments/av4rl9/what_youre_referring_to_as_linux_is_in_fact/" rel="nofollow">https://safereddit.com/r/copypasta/comments/av4rl9/what_your... [2]: <a href="https://github.com/uutils/coreutils-tracking" rel="nofollow">https://github.com/uutils/coreutils-tracking [3]: <a href="https://www.pixelbeat.org/docs/coreutils-gotchas.html" rel="nofollow">https://www.pixelbeat.org/docs/coreutils-gotchas.html
collinfunk · · focus · HN ↗
When you say that no one bothered to do this testing until uutils existed, it feels like you are discrediting our work. Any other implementation is free to use our test suite, as long as they respect its licensing. Doing so is relatively straightforward; you just need to point a shell variable to the place with the just-built binaries.
Note that the man pages are a quick reference explaining the options. A lot of gotchas and further explanations are located in the texinfo manual, which is over 300 pages in PDF form [1]. If you notice areas where it could be improved, I would be happy to review your bug report sent to bug-coreutils@gnu.org.
[1] <a href="https://www.gnu.org/software/coreutils/manual/coreutils.html" rel="nofollow">https://www.gnu.org/software/coreutils/manual/coreutils.html
edelbitter · · focus · HN ↗
Your work, specifically your attention to the reusability/portability of GNU tests intensifying at the same time the uutils project started to close in on the remaining unusable (for that purpose) tests, is very much appreciated and has helped me well beyond its original scope.