Example: The field "AUTHOR" is set in ~/meta/recipes-graphics/tslib/tslib_1.1.bb but in the database it appears as "Not Available". Traceback (most recent call last): File "/home/brandusa/poy-toaster/bitbake/lib/toaster/orm/tests.py", line 473, in test_quality_Recipe self.assertEqual(all_values[i].author, author) AssertionError: u'Not Available' != 'Russell King w/ plugins by Chris Larson et. al.'
FWIW, my opinion is Toaster shouldn't be handling this variable at all. It's not really consistently set in the metadata, nor does it seem particularly useful.
(In reply to comment #1) > FWIW, my opinion is Toaster shouldn't be handling this variable at all. It's > not really consistently set in the metadata, nor does it seem particularly > useful. I'd be happy with that, as long as we get rid of the field then (I don't like the idea of having broken fields lying around).
Alex: is there a patch for this and, if yes, what does it do? Does it fix the field or does it get rid of the field?
Gets rid of the field.
Merged in origin/master and origin/dora-toaster
The author field is gone from the database, but the column is still in the simple interface (screenshot attached). Could we remove it? Also, I've removed the author api call from the api documentation.
Created attachment 1630 [details] author-column-in-simple-interface.png
Fixed in poky-contrib toaster/master:0146a6f76fd001204f7e3bd1f0311ff881129794
The db in master no longer has the author field.
Verified in master:3ada51f7aa26fc95d5f9ba4498c0ea54acc6e42e