By downloading updates, the system says it is impossible to delete old program package

[enrico]

no detail

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: amavisd-new 1:2.10.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
Date: Sat Dec 2 16:22:48 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2017-05-12 (203 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt 1.2.24
SourcePackage: amavisd-new
Title: package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

[enrico (enricofantozzi)]

I do not understand what is asked of me, apologise

[Christian Ehrhardt  (paelzer)]

Hi enrico,
the package amavisd-new that you have installed needs a proper configuration.
A common place for this to fail is the hostname - it needs a fully qualified domain name [1] but quite often users have only set up a short hostname.

From your log:
dic 02 16:22:48 Casa amavis[6748]: The value of variable $myhostname is "...en
dic 02 16:22:48 Casa amavis[6748]: a fully qualified domain name; perhaps...h.
dic 02 16:22:48 Casa amavis[6748]: You must explicitly assign a FQDN of t...me
dic 02 16:22:48 Casa amavis[6748]: in /etc/amavis/conf.d/05-node_id, or f...'s
dic 02 16:22:48 Casa amavis[6748]: network name!
dic 02 16:22:48 Casa amavis[6748]: (failed).

Do as it says and set up a valid FQDN in that file and the service will start.

[1]: https://en.wikipedia.org/wiki/Fully_qualified_domain_name

[Christian Ehrhardt  (paelzer)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

On upgrading a service this service has to be restarted to pick up the fixes.
Rather rarely a real issue occurs that the newer version does e.g. fail with the formerly working configuration.
But most of the time what happens is, that a service was installed, but stays unconfigured or experimented with but left in a broken state.

Now on any update of the related packages that service has to be restarted, but since its config is incomplete/faulty it fails to restart.
Therefore the update of that package has to consider itself incomplete.

Depending on your particular case there are two solutions:
- either remove the offending package if you don't want to continue using it.
- Or if you do want to keep it please fix the configuration so that re-starting the service will work.

Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.

[Launchpad Janitor (janitor)]

[Expired for amavisd-new (Ubuntu) because there has been no activity for 60 days.]