GNOME Bugzilla – Bug 654522
Don't fail builds if the manifest is not set
Last modified: 2011-07-13 18:12:29 UTC
Created attachment 191858 [details] [review] patch When the module has not been updated, we may call the matches function with a files_list of None. This should not fail the build. My build slave was immediately hitting this after updating to the triggers changes.
This is caused by you having an old jhbuild packagedb.xml which doesn't have an installed manifest. You basically need to blow away the root and rerun the build. I will however make jhbuild not crash in this scenario.
Can I suggest that if you commit changes to jhbuild that require everybody to 'blow away the root', it would be a good idea to send a note about this to ddl ?
(In reply to comment #2) > Can I suggest that if you commit changes to jhbuild that require everybody to > 'blow away the root', it would be a good idea to send a note about this to ddl > ? Absolutely, one is overdue =( However I didn't intend to *require* it, just that it's a good idea. And I did push a fix which should solve the issue you hit here.