[Bug 1692420] Comment bridged from LTC Bugzilla
Steve Langasek
steve.langasek at canonical.com
Tue Sep 5 06:13:53 UTC 2017
On Mon, Sep 04, 2017 at 11:50:09AM -0000, bugproxy wrote:
> > Further information regarding the verification process can be found at
> > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
> > advance!
> Tried to install package from proposed, getting below error.
> root at alp10:~# apt-get install powerpc-utils/zesty-proposed
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Release 'zesty-proposed' for 'powerpc-utils' was not found
That is not valid apt syntax. Please
see https://wiki.ubuntu.com/QATeam/PerformingSRUVerification for guidance on
how to run tests for SRUs.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to powerpc-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1692420
Title:
[SRU] powerpc-utils commands exhibits "command substitution: ignored
null byte in input" warning message
Status in The Ubuntu-power-systems project:
New
Status in powerpc-utils package in Ubuntu:
Fix Released
Status in powerpc-utils source package in Zesty:
Fix Committed
Bug description:
[Impact]
The current version of powerpc-utils in Ubuntu Zesty and Artful
carries a bug exposed by bash 4.4+ which causes a warning to be logged
to stderr in 4 different commands: ls-veth, ls-vscsi, lsdevinfo, and
ofpathname. Bash is unable to store the NUL bytes in the result of a
command substitution, prior to 4.4 it silently dropped the NUL bytes,
but since 4.4 it drops the NUL bytes with a warning: "command
substitution: ignored null byte in input".
Additionally to that the ofpathname command also had a bug that caused
a "cd: too many arguments" warning.
Upstream has fixed both [1] and they now need to be backport to Zesty.
[Test Case 1]
Call any of the affected commands without arguments, they should
output "command substitution: ignored null byte in input" to stderr.
The same warning can easily be reproduced in bash 4.4+ by executing:
$ x=$(cat < /proc/$$/cmdline)
bash: warning: command substitution: ignored null byte in input
And to fix it:
$ x=$(tr -d '\0' < /proc/$$/cmdline)
<no output, as expected>
[Test Case 2]
Call ofpathname with no arguments:
$ ofpathname
cd: too many arguments
[Regression Potential]
The replacement of 'cat' with 'tr -d "\0"' causes no regression. Also,
both commands are part of coreutils.
The 'cd' fix replaces it with a drop_dir call. In case the requested
path is not found then the previous behavior would be kept (ie. no
directory change).
[Other Info]
Upstream fix link:
[1] https://github.com/ibm-power-utilities/powerpc-utils/commit/4fcc611a09caea70e6bca6a1275211c72ac4bb45
[Old description]
Please cherry pick...
https://github.com/ibm-power-utilities/powerpc-
utils/commit/4fcc611a09caea70e6bca6a1275211c72ac4bb45
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1692420/+subscriptions
More information about the foundations-bugs
mailing list