dropbear doesn't clean up after being purged

[Andrew Benham]

Installing the dropbear package (2011.54-1ubuntu0.12.04.1) rewrites the initrd image.
Subsequent boots reveal a whole raft of errors "ipconfig not found" from the ramdisk scripts.

So, as I only wanted the dropbearconvert binary for a few minutes, I purged the dropbear package. But the purge didn't rewrite the initrd image, so I still get all the errors on boot.

Not expected behaviour.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: dropbear (not installed)
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
NonfreeKernelModules: fglrx
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Fri May 11 17:54:51 2012
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: dropbear
UpgradeStatus: Upgraded to precise on 2012-05-06 (5 days ago)

[Andrew Benham (z-launchpad-adsb-co-uk)]

Perhaps make use of dropbear (where available) an option in initramfs.conf ?