Bug#809329: apt: "Invalid 'Date' entry in Release file" when missing the Date, brakes backward competability
Package: apt
Version: 1.0.1ubuntu2.10
Severity: important
* What led up to the situation?
When the Release file is missing the 'Date' field, in the new 'apt'
version (1.1.x), the client fails with "Invalid 'Date' entry in Release file".
This brakes backward competability since currently the 'Date' field is
documented as optional:
https://wiki.debian.org/RepositoryFormat#A.22Release.22_files
"These optional fields are purely functional and used mostly internally by
packaging tools.
Date
Valid-Until
MD5Sum, SHA1, SHA256
NotAutomatic and ButAutomaticUpgrades "
* What exactly did you do (or not do) that was effective (or
ineffective)?
running "apt-get update" with "https://dl.bintray.com/sbt/debian";
resulted in:
W: Failed to fetch https://dl.bintray.com/sbt/debian/Release Voce "Date" nel
file Release /var/lib/apt/lists/dl.bintray.com_sbt_debian_Release non valida
The expectation is that this will not fail since, as mentioned above, the
'Date' field is documented as 'Optional'
-- Package-specific info:
-- (no /etc/apt/preferences present) --
-- (/etc/apt/sources.list present, but not submitted) --
-- System Information:
Debian Release: jessie/sid
APT prefers trusty-updates
APT policy: (500, 'trusty-updates'), (500, 'trusty-security'), (500, 'trusty'), (100, 'trusty-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.13.0-74-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages apt depends on:
ii gnupg 1.4.16-1ubuntu2.3
ii libapt-pkg4.12 1.0.1ubuntu2.10
ii libc6 2.19-0ubuntu6.6
ii libgcc1 1:4.9.1-0ubuntu1
ii libstdc++6 4.8.4-2ubuntu1~14.04
ii ubuntu-keyring 2012.05.19
apt recommends no packages.
Versions of packages apt suggests:
pn apt-doc <none>
ii dpkg-dev 1.17.5ubuntu5.5
ii python-apt 0.9.3.5ubuntu2
ii synaptic 0.81.1ubuntu1
-- no debconf information
Reply to: