Debian repository with bigv client has started giving errors recently


I have the following in my debian (testing) sources.list.d directory


which contains

deb ./

Yet when I try the u command within aptitude it complains

W:Failed to fetch Invalid 'Date' entry in Release file /var/lib/apt/lists/client.bigv.io_apt_._Release
E: Some index files failed to download.  They have been ignored, or old ones used instead.

I must admit, I haven’t used the bigv client for sometime now (18 months ish) and I can’t remember what it was for. So I don’t know if I can un-install it.


I don’t know if it’s related, but Bytemark might want to take a look at this odd invalid Content-Type.

$ curl -sSI
HTTP/1.1 200 OK
Server: nginx
Date: Sat, 19 Dec 2015 12:18:08 GMT
Content-Type: application/x-gzip -9n
Content-Length: 219
Connection: keep-alive
Cache-Control: public, max-age=112
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-Hostname-Matched: (?-mix:^client\d?$)
X-Brochure-Server: BrochureServer_client
X-Cache-Status: MISS


When the content arrives, it’s not gzip’d at all.

$ curl -sS
Archive: all
Label: BigV client package repository
Origin: Bytemark Hosting
Architectures: all
Components: main
 c634b20daffb7dd0c9e2816fa18a7f46 6193 Packages
 45bcde483299213696941bdb1cb0b344 1816 Packages.gz


hmm, that’s odd.

Thanks for reporting it - i’ll take a look.



I don’t see to see it here - are you still having the same problem there, or was it just a transient caching problem?

root@test:~# apt-get update && apt-get dist-upgrade && apt-get clean
Ign ./ InRelease
Ign jessie InRelease
Ign ./ InRelease
Hit jessie-updates InRelease
Hit ./ Release.gpg
Hit jessie Release.gpg
Hit ./ Release.gpg
Hit jessie Release
Hit ./ Release
Hit ./ Release
Hit jessie/updates InRelease
Hit jessie-updates/main Sources
Ign ./ InRelease
Hit jessie-updates/contrib Sources
Get:1 ./ Release.gpg [836 B]
Get:2 ./ Release [219 B]
Hit jessie-updates/non-free Sources
Get:3 jessie-updates/main amd64 Packages/DiffIndex [367 B]
Hit jessie-updates/contrib amd64 Packages
Hit ./ Sources
Hit jessie-updates/non-free amd64 Packages
Hit ./ Packages
Hit jessie-updates/contrib Translation-en
Hit jessie-updates/main Translation-en
Hit jessie-updates/non-free Translation-en
Hit ./ Sources
Hit jessie/main Sources
Hit ./ Packages
Hit jessie/non-free Sources
Hit jessie/contrib Sources
Hit jessie/main amd64 Packages
Hit jessie/non-free amd64 Packages
Hit jessie/contrib amd64 Packages
Get:4 ./ Packages [1,886 B]
Hit jessie/contrib Translation-en
Hit jessie/main Translation-en
Hit jessie/non-free Translation-en
Hit jessie/updates/main Sources
Ign ./ Translation-en_GB
Ign ./ Translation-en
Ign ./ Translation-en_GB
Ign ./ Translation-en
Hit jessie/updates/contrib Sources
Hit jessie/updates/non-free Sources
Hit jessie/updates/main amd64 Packages
Hit jessie/updates/contrib amd64 Packages
Hit jessie/updates/non-free amd64 Packages
Hit jessie/updates/contrib Translation-en
Hit jessie/updates/main Translation-en
Hit jessie/updates/non-free Translation-en
Ign ./ Translation-en_GB
Ign ./ Translation-en
Fetched 3,308 B in 1s (1,750 B/s)
Reading package lists… Done
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.




ok, I see it now.

I tried aptitude and that was fine, updated to “testing”, and I see the error now - so it’s something odd in Debian Testing.

I’m seeing it with other repos too.



Appears to be a badly worded error - it’s because there is no Date entry in there:

It looks like we also need to provide SHA* hashes on the bigv repo too.

root@test:~# apt-get update && apt-get dist-upgrade && apt-get clean
Ign:1 ./ InRelease
Hit:2 testing InRelease
Hit:3 testing-updates InRelease
Ign:4 ./ InRelease
Hit:5 ./ Release
Hit:6 ./ Release
Hit:7 testing/updates InRelease
Ign:8 ./ InRelease
Get:9 ./ Release [219 B]
Fetched 219 B in 0s (451 B/s)
Reading package lists… Done
W: Failed to fetch Invalid ‘Date’ entry in Release file /var/lib/apt/lists/
W: Failed to fetch Invalid ‘Date’ entry in Release file /var/lib/apt/lists/
W: Failed to fetch No Hash entry in Release file /var/lib/apt/lists/client.bigv.io_apt
._Release, which is considered strong enough for security purposes
E: Some index files failed to download. They have been ignored, or old ones used instead.

This is something we’re going to have to look at.

Some of these repos are dynamically generated so we’ll have to make/deploy some code changes to sort this.



ok, the ones are fixed.

The bigv client one is a bit more tricky as it’s dynamically generated - will post back when that one is fixed.


Ok! - is that working ok for you now?

Seems ok here now.



Yes - problem disappeared for me.



Recycling old topic since the bug appears to be recycled…

I get a similar error from the new bytemark_client repo, using apt-get from Debian sid:

root@miraculix:/tmp# apt-get update
Hit:1 sid InRelease
Hit:2 ./ InRelease                      
Reading package lists... Done                                                             
W: Invalid 'Date' entry in Release file /var/lib/apt/lists/