Sorry, this seems to be something (slightly) different than bug
#33362, I'm afraid. I'm using the latest Dapper already.
As I understand, bug #33362 refers to the fact that we should use
/var/run rather than /dev/shm. My bug report was meant to point out
that this transition is not handled cleanly by the postinst script.
The typical breezy installation will have a link
/etc/resolvconf/run -> /dev/shm/resolvconf *and* this link will be
canonicalisable at the time of the upgrade. Therefore, the postinst
script won't touch this link although it really should change it to
/var/run/resolvconf -- and rebuild this directory which is, as I
understand, taken care of by the initscript.
Sorry, this seems to be something (slightly) different than bug
#33362, I'm afraid. I'm using the latest Dapper already.
As I understand, bug #33362 refers to the fact that we should use
/var/run rather than /dev/shm. My bug report was meant to point out
that this transition is not handled cleanly by the postinst script.
The typical breezy installation will have a link
/etc/resolvconf/run -> /dev/shm/resolvconf *and* this link will be
canonicalisable at the time of the upgrade. Therefore, the postinst
script won't touch this link although it really should change it to
/var/run/resolvconf -- and rebuild this directory which is, as I
understand, taken care of by the initscript.
Sorry if I'm getting something wrong here.