Description of problem: F-19 regresses against F-18; it broke some parts of the GDB testsuite. Version-Release number of selected component (if applicable): FAIL: sharutils-4.13.3-1.fc19.x86_64 PASS: sharutils-4.11.1-5.fc18.x86_64 How reproducible: Always. Steps to Reproduce: rm -f hello;echo hello|uuencode hello >hello.uu;uudecode -o - hello.uu;rm -f hello.uu Actual results: uudecode usage error: You cannot specify an output file when processing multiple input files. uudecode (GNU sharutils) - decode an encoded file - Ver. 4.13.3 USAGE: uudecode [ -<flag> [<val>] | --<name>[{=| }<val>] ]... [ file ... ] <+missing newline at the end of this help textt> Expected results: hello Additional info: I do not see where are upstream mailing lists and/or bug tracker.
The only upstream contact is <bug-gnu-utils> mailing list where [sharutils] must be specified in subject. I confirm this is new bug in uudecode.
Ok, I have forwarded the bug report. It will show up in archive <http://lists.gnu.org/archive/html/bug-gnu-utils/2013-01/threads.html> after moderator approves the post.
man uudecode > BUGS > Please put sharutils in the subject line for emailed bug reports. It > helps to spot the message. > [...] > Please send bug reports to: bug-gnu-utils There is a fix for this in a pre-release. Until I am replaced, "bkorb" can also be used as an address....
Created attachment 685851 [details] Fix ported from developement 4.13.4pre2
This is not the only problem. There is bug `-o -' writes into ./- instead to FD 1.
Created attachment 685949 [details] Fix not to open - ported from 4.13.4pre2