If you incorrectly add a layer (see bug 8952) there appears to be no way to remove it from database.
We have a few 'delete'-related things to do: see bug 8132 and bug 6238. We should probably do all those in 2.2
Nice bug find! Umm, a request: could you add a steps to reproduce? Something like 1) import layer button 2) import python-networking from .... ty :)
Sorry, poor bug report. Here's an example use case 1. You import a layer with recipes, say github.com/old-iot-stuff/layer 2. You find out you imported an un-maintained layer, you should have imported github.com/new-iot-stuff/layer 3. You want to remove the old-iot-stuff layer from toaster as it will only ever cause problems 4. You remove from a project, but you can't remove it form toaster Expected behavior ----------------- 1. Import a layer with recipes, say github.com/old-iot-stuff/layer 2. You realize it's a stale layer and want to remove it 3. Remove from toaster using (say) "remove layer from database" button Observed behavior ----------------- 1. Import a layer with recipes, say github.com/old-iot-stuff/layer 2. You realize it's a stale layer and want to remove it 3. You can't remove it form toaster
merged to master http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=8813726f1d5ea1d78fced7fe52abdf826e529e62