On 08.06.2016 15:01, Adam Osuchowski wrote:
Elan Ruusamäe wrote:
yours had invalid timestamp, so i assumed mine is correct
Valid timestamp should be 2016.06.07 because, according to
http://dev.maxmind.com/geoip/legacy/geolite/, databases are updated
on the first Tuesday of each month, and it was June 7th not 6th.
no, valid timestamp is 2016.06.06, if look at the file in UTC timestamp:
[~/rpm/geo-packages/GeoIP-db-IPASNum(2016.06.06) (master)⚡] ➔ TZ=UTC
LC_ALL=C ls -l *gz
-rw-r----- 1 glen users 2070384 Jun 6 22:35 GeoIPASNum-2016.06.06.dat.gz
[~/rpm/geo-packages/GeoIP-db-IPASNum(2016.06.06) (master)⚡] ➔ TZ=CET
LC_ALL=C ls -l *gz
-rw-r----- 1 glen users 2070384 Jun 7 00:35 GeoIPASNum-2016.06.06.dat.gz
[~/rpm/geo-packages/GeoIP-db-IPASNum(2016.06.06) (master)⚡] ➔ TZ=EET
LC_ALL=C ls -l *gz
-rw-r----- 1 glen users 2070384 Jun 7 01:35 GeoIPASNum-2016.06.06.dat.gz
[~/rpm/geo-packages/GeoIP-db-IPASNum(2016.06.06) (master)⚡] ➔
so, you got correct md5, but wrong timestamp
i got wrong md5 but correct timestamp
so anyway, updated md5 and distfiles was able to fetch it
--
glen
_______________________________________________
pld-devel-en mailing list
[email protected]
http://lists.pld-linux.org/mailman/listinfo/pld-devel-en
