On Thu, Feb 08, 2018 at 03:07:54PM +0100, Julian Andres Klode wrote:
> Hey guys,
>
> APT will shortly start validating that the Date field in a release
> file is not (too far) in the future. This might have implications
> for installing on devices with an inaccurate clock, as they might
> now fail
On Thu, Feb 08, 2018 at 09:05:50PM +0100, Philip Hands wrote:
> On Thu, 08 Feb 2018, Julian Andres Klode wrote:
> > Hey guys,
> >
> > APT will shortly start validating that the Date field in a release
> > file is not (too far) in the future. This might have implications
> > for installing on devic
On Thu, 08 Feb 2018, Julian Andres Klode wrote:
> Hey guys,
>
> APT will shortly start validating that the Date field in a release
> file is not (too far) in the future. This might have implications
> for installing on devices with an inaccurate clock, as they might
> now fail.
>
> There are two p
On Thu, Feb 08, 2018 at 03:25:16PM +, Holger Levsen wrote:
> On Thu, Feb 08, 2018 at 03:07:54PM +0100, Julian Andres Klode wrote:
> > It's a bit unclear if this only affects validation of the Date field,
> > or also turns off Validation of the Valid-Until field (as a generic "turn
> > off all d
On Thu, Feb 08, 2018 at 03:07:54PM +0100, Julian Andres Klode wrote:
> It's a bit unclear if this only affects validation of the Date field,
> or also turns off Validation of the Valid-Until field (as a generic "turn
> off all date-related checks" option). Opinions on that?
there definitly should
Hey guys,
APT will shortly start validating that the Date field in a release
file is not (too far) in the future. This might have implications
for installing on devices with an inaccurate clock, as they might
now fail.
There are two primary workarounds:
* Set Acquire::Check-Date to false
* Set c
6 matches
Mail list logo
