9.10 autobuild upgrade for 0.22 corrupts dpkg scripts

[rasos]

I first did an upgrade from Mythbuntu 9.04 (64bit) with 0.21 fixes to 9.10. When activating the automatic upgrade to 0.22 fixes, as recommended on the Mythbuntu homepage, the linux-headers fail to be updated. I did a 2nd completely fresh install with the same effect - any further update procedure for the kernel seem to fail.

status half-configured linux-image-2.6.31-16-generic 2.6.31-16.53

/var/log7apt/term.log reports an unknown group postdrop in the statoverride file. This group is not available and the file looks like this:
cat /var/lib/dpkg/statoverride
root postdrop 02555 /usr/sbin/postqueue
hplip root 755 /var/run/hplip
root mlocate 2755 /usr/bin/mlocate
postfix postdrop 02710 /var/spool/postfix/public
root postdrop 02555 /usr/sbin/postdrop

Here is the /var/log7apt/term.log Log started: 2009-12-29 15:27:53
dpkg: nicht behebbarer fataler Fehler, Abbruch:
    Syntaxfehler: unbekannte Gruppe »postdrop« in statoverride-Datei

Richte linux-image-2.6.31-16-generic ein (2.6.31-16.53) ... dpkg (Unterprozess): kann installiertes post-installation-Skript nicht ausführen: Exec format error dpkg: Fehler beim Bearbeiten von linux-image-2.6.31-16-generic (--configure):

    Unterprozess installiertes post-installation-Skript gab den Fehlerwert 2 zurück

Richte linux-headers-2.6.31-16-generic ein (2.6.31-16.53) ... dpkg (Unterprozess): kann installiertes post-installation-Skript nicht ausführen: Exec format error dpkg: Fehler beim Bearbeiten von linux-headers-2.6.31-16-generic (--configure):

--rasos

[Mario Limonciello (superm1)]

This appears to be a bug with the linux-headers package in Ubuntu, marking the task appropriately.

[Mitch Towner (kermiac)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 512096, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.