Today following bug #543780 I've find, that bugzilla silently refuses to accept build.log file: * Messages for package x11-libs/gtk+-3.14.9: * ERROR: x11-libs/gtk+-3.14.9::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=x11-libs/gtk+-3.14.9::gentoo'`, * the complete build log and the output of `emerge -pqv '=x11-libs/gtk+-3.14.9::gentoo'`. * The complete build log is located at '/var/tmp/portage/x11-libs/gtk+-3.14.9/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/x11-libs/gtk+-3.14.9/temp/environment'. * Working directory: '/var/tmp/portage/x11-libs/gtk+-3.14.9/work/gtk+-3.14.9-abi_x86_64.amd64' * S: '/var/tmp/portage/x11-libs/gtk+-3.14.9/work/gtk+-3.14.9' $ ls -l gtk+-3.14.9/ итого 628 -rw-r----- 1 root root 455986 мар 19 13:38 build.log -rw-r--r-- 1 root root 174999 мар 19 13:38 environment The compressed one: $ ls -l gtk+-3.14.9/ итого 248 -rw-r----- 1 root root 68727 мар 19 13:38 build.log.Z is accepted. To my mind bugzilla should provide error message on each error and should NEVER silently ignore user commands. For described particular ussue I expect a message like: "Please, compress log files before attaching them." To my mind following this idea we should require compression of all text files (maybe above 1k size), not only logs.
when did you try to attach it ? on the initial bug page ? or did you try to attach after filing the bug ?
(In reply to SpanKY from comment #1) > when did you try to attach it ? on the initial bug page ? or did you try > to attach after filing the bug ? AFAIR this issue was taken while trying to attach file on initial report page. And confirmed on update page (that is right, the same action should be handled in the same way).
*** This bug has been marked as a duplicate of bug 375481 ***
