package tftpd-hpa (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tftp-hpa (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
&
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tftpd-hpa (not installed)
ProcVersionSign
Uname: Linux 4.4.0-47-generic i686
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Mon Nov 28 11:30:39 2016
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
InstallationDate: Installed on 2016-09-14 (77 days ago)
InstallationMedia: Lubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160720)
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.15
SourcePackage: tftp-hpa
Title: package tftpd-hpa (not installed) failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)
Hi and thank you for taking the time to report this bug and helping to make Ubuntu better.
From the log it seems that the config is modified in an incompatible way:
дек 01 08:54:21 hostname tftpd[939]: unknown option -?
дек 01 08:54:21 hostname systemd[1]: Failed to start LSB: HPA's tftp server.
дек 01 08:54:21 hostname systemd[1]: tftpd-hpa.service: Failed with result 'exit-code'.
I can't read most of the rest but that is what is killing tftp-hpa on the restart that is triggered after the upgrade.
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.