package postfix 3.4.13-0ubuntu1.2 failed to install/upgrade: new postfix package pre-installation script subprocess returned error exit status 127
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postfix (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Could not upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: postfix 3.4.13-0ubuntu1.2
ProcVersionSign
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.11-
Architecture: amd64
CasperMD5CheckR
Date: Sun Dec 25 15:29:48 2022
Dependencies:
ErrorMessage: new postfix package pre-installation script subprocess returned error exit status 127
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2
PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
RelatedPackageV
dpkg 1.19.7ubuntu3.2
apt 2.0.9
SourcePackage: postfix
Title: package postfix 3.4.13-0ubuntu1.2 failed to install/upgrade: new postfix package pre-installation script subprocess returned error exit status 127
UpgradeStatus: Upgraded to focal on 2022-12-25 (0 days ago)
tags: | removed: need-duplicate-check |
Thanks for taking the time to report this bug and trying to make Ubuntu better.
This is the installation error:
Preparing to unpack .../04- postfix_ 3.6.4-1ubuntu1_ amd64.deb ... main.cf. proto modified, not updating. master. cf.proto modified, not updating. master. cf: No such file or directory master. cf: No such file or directory dpkg/tmp. ci/preinst: 175: retry_warning: not found dpkg-install- fsuCF5/ 04-postfix_ 3.6.4-1ubuntu1_ amd64.deb (--unpack):
/etc/postfix/
/etc/postfix/
grep: /etc/postfix/
grep: /etc/postfix/
/var/lib/
dpkg: error processing archive /tmp/apt-
new postfix package pre-installation script subprocess returned error exit status 127
Could you confirm if you have the file /etc/postfix/ master. cf in place? There is nothing much than that we can infer from the logs.
I am setting this bug to Incomplete while we wait for more information, once you add it please set it back to New and we will revisit it.