On Tue, Feb 17, 2009 at 09:21:52AM +0000, Richard Kettlewell <[email protected]> was heard to say: > E: Problem executing scripts DPkg::Post-Invoke 'if [ -d > /var/lib/update-notifier ]; then touch > /var/lib/update-notifier/dpkg-run-stamp; fi' > E: Sub-process returned an error code
Looks like a bug in update-notifier. On the other hand, > touch: setting times of `/var/lib/update-notifier/dpkg-run-stamp': > Function not implemented looks like you have /var/lib on a really unusual file system. And aptitude's "a package failed, trying to recover" message ... well, I think that's probably as good as it can do (all it knows is that the apt "run dpkg" function failed for some reason). I guess I'll reassign this to update-notifier for the time being. I don't know what they use dpkg-run-stamp for; they might just tell you that /var/run has to be on a filesystem that allows times to be set. I'm curious what sort of a filesystem that is on -- according to utime(), which I imagine is what "touch" uses, the only acceptable errors are EACCES (access denied), ENOENT (file does not exist), EPERM (permission denied), and EROFS (filesystem is read-only). It sounds like you're getting ENOSYS. The output of "mount" would be useful for figuring out what's going on. Daniel -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
