I tried to reproduce is but it is now working with the symlink to pixz.
When it happened(from memory) I saw something unusual scroll past and I scrolled up to see, in the output, that message you get when you try to invoke pixz wrong, "Usage: pixz [OPTION]... [FILE]..." followed by half a page of helpful suggestions, followed by tons of modules getting stripped, signed, installed, and exited with some error. I removed the symlink and restored the xz executable and the packages were built so I assumed that was the problem. I was actually pretty confident it would be easy to reproduce if somebody asked and yet I cannot.
I'm using bookworm and notice an xz typo results in a one liner followed by the suggestion to try "xz --help" so it was definitely some mis-invocation on behalf of one of the scripts in a way that suggests pixz was the source of the complaint. I relinked it today the symlink is working as expected.
When it happened(from memory) I saw something unusual scroll past and I scrolled up to see, in the output, that message you get when you try to invoke pixz wrong, "Usage: pixz [OPTION]... [FILE]..." followed by half a page of helpful suggestions, followed by tons of modules getting stripped, signed, installed, and exited with some error. I removed the symlink and restored the xz executable and the packages were built so I assumed that was the problem. I was actually pretty confident it would be easy to reproduce if somebody asked and yet I cannot.
I'm using bookworm and notice an xz typo results in a one liner followed by the suggestion to try "xz --help" so it was definitely some mis-invocation on behalf of one of the scripts in a way that suggests pixz was the source of the complaint. I relinked it today the symlink is working as expected.
Statistics: Posted by miekl — 2024-06-30 04:58 — Replies 2 — Views 81