Comment 15 for bug 862129

Analysis of the upgrade logs and further discussion on IRC shows that it's infeasible to fix this in samba. The problem arises when perl-modules is unpacked without libperl5.12/perl-base, and then samba is unpacked. Moving the update-inetd code from the postrm to the prerm may help in some cases, but not in this one, because whichever maintainer script tries to call update-inetd, the modules will be unavailable to perl at that point.

Fixing update-inetd to be more robust (i.e., to not require perl-modules) would help for the future, but would not help for the present upgrade problems.

I think the only way to fix this reliably is via update-manager.