Comment 7 for bug 182386

Yes, I can confirm that it still does this. For the time being, I'll just use your workaround you used in bug #182219 which involves dropping the source and binary package tables, seeing as it works fine during the first scan.