Bug#995833: busybox: uudecode doesn't recognise the special decode_pathname /dev/stdout

[Christoph Anton Mitterer <calestyo@scientia.net>]

Package: busybox
Version: 1:1.30.1-7+b1
Severity: normal
Tags: upstream patch


Hey.

Since it's unclear whether and when upstream will react and how long it then
takes that this actually lands in Debian, could you possibly consider to
cherry pick the patch I provided at:
https://bugs.busybox.net/show_bug.cgi?id=14241

for inclusion in the Debian package?


The issue is basically, that uudecode is mandated by POSIX to consider
/dev/stdout as a special symbol (and not a file) that causes output written
to standard output (and not to whichever file the uuENcoded data indicates.

Under normal user space this wouldn't be that much of an issue, since
/dev/stdout exists and is a symlink to /proc/self/fd/1.

But within the initramfs, this symlink doesn't sem to exist, so any output
that should go to stdout would actually go to that file (or cause error
if that's not writable).


I should also note, that the sharutils version of uudecode behaves correctly
and completely ignores any file /dev/stdout if it exists.


Thanks,
Chris.