[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#872337: marked as done (Release file generates "W: Invalid 'Date' entry in Release file")



Your message dated Thu, 17 Aug 2017 07:39:50 +0200
with message-id <CADk7b0NGuqRjV3puYBZtOCzed4NNLtBc-wn=4hDNh-fD21hSFQ@mail.gmail.com>
and subject line Re: Bug#872337: Release file generates "W: Invalid 'Date' entry in Release file"
has caused the Debian Bug report #872337,
regarding Release file generates "W: Invalid 'Date' entry in Release file"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
872337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872337
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt-utils
Version: 1.4.7


Generating a (In)Release file with apt-ftparchive, I get this date format:
Date: Tuesday, 15 August 2017 23:16:52

APT returns this warning message when attempting to download the Release file:
[...]
W: Invalid 'Date' entry in Release file [...]
[...]

Looking at an official (In)Release file (for instance
ftp://ftp.debian.org/debian/dists/unstable/Release), I can see the
date format is slightly different:
Date: Wed, 16 Aug 2017 08:29:09 UTC

-- 
Cheers,
Luca

--- End Message ---
--- Begin Message ---
Hi David,

2017-08-16 16:42 GMT+02:00 David Kalnischkies <david@kalnischkies.de>:
> Are you _*SURE*_ this is generated by apt-ftparchive and not some
> handwritten Release file?

Oops, you're right. Indeed the release file was created by
apt-ftparchive, but I was passing a -o APT::FTPArchive::Release::Date
option with the offending format, therefore the sane default was not
taken into account. After removing the option, I was able to get the
correct date.

Sorry I haven't noticed this before submitting the bug!

-- 
Cheers,
Luca

--- End Message ---

Reply to: