[Bug 2126954] Re: stat -c output difference versus coreutils-gnu: double quotes vs single-quotes

[Paul Dooley]

This bug also affects wg-quick, causing the following error:

/usr/bin/wg-quick: line 46: ((: ( &  & 0007) == 0: syntax error: operand
expected (error token is "&  & 0007) == 0")

Reverting to gnu fixes the problem.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to rust-coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/2126954

Title:
  stat -c output difference versus coreutils-gnu: double quotes vs
  single-quotes

Status in rust-coreutils package in Ubuntu:
  Confirmed
Status in rust-coreutils source package in Questing:
  Confirmed

Bug description:
  There is a minor difference in the stat -c %N command out put in rust-
  coreutils stdout which uses double-quotes versus gnu-coreutils which
  uses single quotes. This breaks some minor integration tests in the
  cloud-init project.

  This affects Ubuntu questing.

  I've filed an ustream bug which seems to be actively be worked and may
  land shortly: https://github.com/uutils/coreutils/issues/8789

  
  Bug Details below:

  Non-critical change in behavior of the output of stat -c %N in rust-coreutils:
  version: rust-coreutils 0.2.2-0ubuntu2 amd64

  Expected gnu-coreutils (9.5-1ubuntu1) behavior:

  ~$ stat -c %N /lib
  '/lib' -> 'usr/lib'
  Current rust-coreutils behavior:

  ~$  stat -c %N /lib
  "/lib" -> "usr/lib"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rust-coreutils/+bug/2126954/+subscriptions