Since I'm using ~amd64, it's a regular occurrence that some package won't emerge properly. Since I'm running Gentoo on a server (not a mission critical one!), it's kind of a pain to collect all the info and files together. I have to copy them to a user directory, remember to change the permissions, collect the emerge --info, etc. It's a chore. My first suggestion would be to have failed builds automatically zip up all relevant info into one file that I can attach. build log, environment, emerge --info, etc. Now, I only have to report the failure and attach the one file. My second, complementary suggestion would be to offer a tool that would take that and automatically generate and file the bug report. Reproducible: Always
Well, your idea is not bad, but what you propose is not useful in current bugzilla configuration, for the following reasons: 1) zip files cannot be read directly from bugzie (via a browser), everyone who needs to see the reported information will be forced to download and unzip the files, 2) Your request about a tool for automatic bug reporting will do no good in the hands of inexperienced users. A package may fail to be emerged for *many* *many* reasons, some of them clearly caused by wrong user configuration/ administration/ maintenance. Also, such a tool would make people report duplicate bugs again and again, if they don't try searching in bugzie for an already reported bug. And more. 3) Our current bug wrangling/assignment policies are not ready for such automation. You hit one of our oldest bugs, bug #761 . I'm going to resolve this as duplicate of 761, if you still think there is something we should discuss, you're free to reopen. For reference, see bug #761 bug #287911 I write it again, it's not a bad idea, it's just not that simple to implement it the right way. *** This bug has been marked as a duplicate of bug 761 ***
