Comment 17 for bug 443311

I think it happened due to the non-native packaging I was trying to keep using when preparing the update; I thought I had redone it properly when I switched to native, but it seems not, not sure why; uploading a fix.