Created attachment 1672 [details] database Example: { "pk": 93, "model": "orm.package", "fields": { "installed_size": 0, "name": "libcidn", "license": "", "description": "", "recipe": null, "summary": "", "version": "", "build": 1, "size": 0, "section": "", "revision": "" } }, { "pk": 94, "model": "orm.package", "fields": { "installed_size": 0, "name": "eglibc-thread-db", "license": "", "description": "", "recipe": null, "summary": "", "version": "", "build": 1, "size": 0, "section": "", "revision": "" } { "pk": 105, "model": "orm.package", "fields": { "installed_size": 0, "name": "libc-staticdev", "license": "", "description": "", "recipe": null, "summary": "", "version": "", "build": 1, "size": 0, "section": "", "revision": "" } Tested on toaster/master:7e7b2a24952c904fe934565068b1f6583eacd450 I attach the database.
This also happens in master:bc1e359aaefeeddf8525b46eb80ac14db7f637b3
This is not a bug, unfortunately. If a package was build outside the current build, and it's not included in any of the built images, but is referenced in a dependecy, it will have an entry, in order to be able to record the dependency chain. However data will be missing from that entry. This is normal.
Verified. IonutC