The patch would solve the issue, but it isn't the right solution in my opinion.
Firstly, if the directory isn't there then there may be a problem until a
reboot and the directory is created.
Secondly, we don't understand the issue properly, at least I don't.
I have downloaded the package locally, and it contains this
directory. It is then created on dpkg --unpack. This means that
it should be present for the configure step.
The only way I have found so far to trigger this bug is to
do the dpkg --unpack, then remove the directory, and then
do the --configure, and I get the error given above.
Does anyone else have any pointers as to what may be
going on.
Hi,
The patch would solve the issue, but it isn't the right solution in my opinion.
Firstly, if the directory isn't there then there may be a problem until a
reboot and the directory is created.
Secondly, we don't understand the issue properly, at least I don't.
I have downloaded the package locally, and it contains this
directory. It is then created on dpkg --unpack. This means that
it should be present for the configure step.
The only way I have found so far to trigger this bug is to
do the dpkg --unpack, then remove the directory, and then
do the --configure, and I get the error given above.
Does anyone else have any pointers as to what may be
going on.
Thanks,
James