I'm not sure this is actually a bug, but working as designed.
As being used one is specifying that input-file is coming off of stdin,
so it uses hardcoded permissions (since it doesn't have anything else to
really go on). Also not that when you are saying 'uuencode x' you 'x'
is simple the output-name that will be put into the uuencode header, not
the actual out-put filename, so it can be derived from that argument
either.
So instead specifiy an input file if you want permissions to be derived
from the actual input file:
jgrimm@jgrimm-ThinkPad-X250:~/tmp$ touch x
jgrimm@jgrimm-ThinkPad-X250:~/tmp$ chmod 755 x
jgrimm@jgrimm-ThinkPad-X250:~/tmp$ uuencode x x
begin 755 x
`
end
** Changed in: sharutils (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/283087
Title:
uuencode does not correctly encode file permissions when reading from
stdin
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sharutils/+bug/283087/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
