| 1 |
El sáb, 18-10-2014 a las 13:19 -0400, Michael Orlitzky escribió: |
| 2 |
> On 10/18/2014 01:00 PM, Diego Elio Pettenò wrote: |
| 3 |
> > All the stack is at https://github.com/gentoo/tboxanalysis |
| 4 |
> > |
| 5 |
> > The opening of the bug report is done by a piece of meatware called |
| 6 |
> > "me". The UI displays a link that I can click to pre-fill the bug |
| 7 |
> > report. The rest of the information is filled in manually and submitted. |
| 8 |
> > Also remember that the linked logs might be too big for Bugzilla to |
| 9 |
> > attach uncompressed... and some of them even compressed. |
| 10 |
> > |
| 11 |
> > I take it that at least one person (you) will object at me keeping the |
| 12 |
> > process as is, so for the moment I won't be wasting my time on this. |
| 13 |
> > Call me back if you find a way to fix that without requiring more of my |
| 14 |
> > time. |
| 15 |
> > |
| 16 |
> |
| 17 |
> Perhaps a stupid question, but: why is it a problem if the logs are |
| 18 |
> linked rather than attached? |
| 19 |
> |
| 20 |
> |
| 21 |
|
| 22 |
Supposedly we always must attach files to bug reports to ensure they are |
| 23 |
kept forever with that bug reports instead of relying on external |
| 24 |
resources that could disappear in the future (or far future). If I don't |
| 25 |
misremember, flameeyes was paying for having that logs kept in that |
| 26 |
amazon resource for a long long time... but some people were stricter |
| 27 |
applying this rule and asked him to attach the file instead... leading |
| 28 |
to the bug being closed as NEEDINFO and... |
Archives