Invalid 'Date' entry in Release file /var/lib/apt/lists/partial/archive.ubuntu.com_ubuntu_dists_yakkety-proposed_InRelease
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
New
|
Undecided
|
Unassigned |
Bug Description
Continuously get that warning when using synaptic to reload the sources. This happen with apt 1.3-exp2 only.
This seems a regression as per that old report:
https:/
ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: apt 1.3~exp2
ProcVersionSign
Uname: Linux 4.6.0-7-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jun 17 08:19:22 2016
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)
For the SRU:
[Impact]
Prevent adding this regression to 1.2.16
[Test case]
Parse (Release file with) date where hour is single digit
[Regression potential]
Should be very low, we are running this in yakkety too, and in Debian since quite some time.
description: | updated |
This is caused by the usage of relatively new c++11 features, namely std::get_time, as described in this libstdc++6 upstream bug: https:/ /gcc.gnu. org/bugzilla/ show_bug. cgi?id= 71556
The Release for yakkety-proposed currently reads: "Date: Fri, 17 Jun 2016 6:30:29 UTC". Note the "6" as hour.
Reverting commit 9febc2b238e1e32 2dce1f94ecbed46 d595893b52, which introduced the usage of std::get_time has the disadvantage of opening the 'problem' it is supposed to fix again and the 'bonus' the commit mentions is removed, too, which seems small, but is a surprising gotcha in unsuspecting applications (which are either not fiddling with locale at all or are multithreaded).