grok

  1. Bug #162248
  2. Comment #3

Comment 3 for bug 162248

Revision history for this message
Martijn Faassen (faassen) wrote :

Unfortunately it does seem to be a 0.11 issue after all. I now saw this with broken objects and Grok 0.11 packages.