package tzdata 2017c-0ubuntu0.16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tzdata (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
i'm just doing what the thing is saying .By the way, great to be back with Ubuntu.
May the Source be with you!
Relevant dpkg terminal log lines:
```
Current default time zone: 'Europe/London'
date: invalid date 'Sun Mar 25 01:58:44 UTC 2018'
dpkg: error processing package tzdata (--configure):
subprocess installed post-installation script returned error exit status 1
```
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tzdata 2017c-0ubuntu0.
ProcVersionSign
Uname: Linux 4.4.0-40-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Sun Mar 25 02:58:44 2018
DistributionCha
# This is a distribution channel descriptor
# For more information see http://
canonical-
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2018-03-11 (17 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47
PackageArchitec
RelatedPackageV
dpkg 1.18.4ubuntu1.4
apt 1.2.26
SourcePackage: tzdata
Title: package tzdata 2017c-0ubuntu0.
UpgradeStatus: No upgrade log present (probably fresh install)
tags: | removed: need-duplicate-check |
Relevant dpkg terminal log lines:
```
Current default time zone: 'Europe/London'
date: invalid date 'Sun Mar 25 01:58:44 UTC 2018'
dpkg: error processing package tzdata (--configure):
subprocess installed post-installation script returned error exit status 1
```
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #1672111, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.