After that, dpkg complained about "cannot access archive: No such file or directory". The deb archive was postfix_2.11.0-1ubuntu1_amd64.deb.
I've run the dpkg through strace, and I found the following:
stat("postfix_2.11.0-1_amd64.deb", 0x7ffcaa79c310) = -1 ENOENT (No such file or directory)
So, I've renamed the file postfix_2.11.0-1ubuntu1_amd64.deb to postfix_2.11.0-1_amd64.deb, and it successfully installed.
I have no idea what is causing this, but this was a "solution".
The strangest thing is that now even the first archive is installing correctly. (dpkg -i postfix_2.11.0-1ubuntu1_amd64.deb).
Looks like I've added this to a duplicate bug, so here it is again:
I've had this problem today, I was applying a patch to postfix, based on the following: /www.howtoforge .com/virtual- users-and- domains- with-postfix- courier- mysql-and- squirrelmail- ubuntu- 14.04-lts# -apply- the-quota- patch-to- postfix
https:/
After that, dpkg complained about "cannot access archive: No such file or directory". The deb archive was postfix_ 2.11.0- 1ubuntu1_ amd64.deb.
I've run the dpkg through strace, and I found the following: 2.11.0- 1_amd64. deb", 0x7ffcaa79c310) = -1 ENOENT (No such file or directory)
stat("postfix_
So, I've renamed the file postfix_ 2.11.0- 1ubuntu1_ amd64.deb to postfix_ 2.11.0- 1_amd64. deb, and it successfully installed.
I have no idea what is causing this, but this was a "solution".
The strangest thing is that now even the first archive is installing correctly. (dpkg -i postfix_ 2.11.0- 1ubuntu1_ amd64.deb) .