bug#53801: [PATCH] tests: have printf(1) use octal numbers for POSIX conformance
"Brian C. Lane" <[email protected]> Mon, 7 Feb 2022 09:10:12 -0800
| Newsgroups | gmane.comp.gnu.parted.bugs |
|---|---|
| Message-ID | <YgFSdHPXxDftU/[email protected]> |
On Mon, Feb 07, 2022 at 08:52:33AM -0800, Brian C. Lane wrote: > On Sat, Feb 05, 2022 at 10:44:29AM +0000, Kerin Millar wrote: > > Hello, > > > > The attached patch rectifies some test failures that were reported at https://bugs.gentoo.org/774363. Whether it be a builtin of sh(1) or not, POSIX does not require for the printf utility to support hexadecimal notation. > > > > -- > > Kerin Millar > > Thanks for the patch. I'll have to ponder this for a bit. So the issue > is showing up in Gentoo because it uses dash, right? The issue I have > with the change is that it then obscures what's being written. Everyone > knows what 0x55aa is :) I'd prefer a solution that continues to use hex > so that future users don't have to figure out what's going on. Actually, on Fedora at least, printf comes from coreutils so the shell shouldn't matter at all. The tests are single quoted to prevent shell expansion, so maybe dash is using a builtin printf that's different? Brian -- Brian C. Lane (PST8PDT) - weldr.io - lorax - parted - pykickstart