-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I have noticed the following differences after restarting acng:
# ll
/var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/*(.)
- -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 86939 Jun 25 15:44
/var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release
- -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 836 Jun 25 07:59
/var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release.gpg
- -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 249 Jun 25 07:59
/var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release.gpg.head
- -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 247 Jun 25 15:44
/var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release.head
# ll var/**/*(.)
- -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 86939 Jun 25 00:04
var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release
- -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 836 Jun 25 07:59
var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release.gpg
- -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 249 Jun 25 07:59
var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release.gpg.head
- -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 247 Jun 25 00:04
var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release.head
The Release file has the same size, but its contents differs:
# diff
{,/}var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release
< Date: Sun, 24 Jun 2012 21:01:22 UTC
< Valid-Until: Wed, 04 Jul 2012 21:01:22 UTC
- ---
> Date: Mon, 25 Jun 2012 02:01:25 UTC Valid-Until: Thu, 05 Jul 2012
> 02:01:25 UTC
120,122c120,122
< 59dd60091a76ae5dcc0f47d6b2fdd35a 1250354 main/binary-armel/Packages
< ed49d3f3e1fc9ef9921d95ef65e626fc 220269
main/binary-armel/Packages.bz2
< a68dd520f5ba8fb6410e3a7dc72ff2b7 278365 main/binary-armel/Packages.gz
- ---
> 5cce7446ebcc3b96625d732853705602 1252596
> main/binary-armel/Packages 2573eaa1aaad3eeac8c870657f48d7fb
> 220609
main/binary-armel/Packages.bz2
> 7006ac03fe87aa58bcc8572d31a3fa8b 279170
> main/binary-armel/Packages.gz
421,423c421,423
< b7bce4ef0780a9ef2616491da4d0d5377649840d 1250354
main/binary-armel/Packages
< 97ae90e95cd92ef5320d7a63dab3369fad84ba84 220269
main/binary-armel/Packages.bz2
< d7f1fc34840ed2818afe2c2d51f3340de7fb357d 278365
main/binary-armel/Packages.gz
- ---
> f4bbb3319ea03240552ff97c0b2bf5f9ba90a1ee 1252596
main/binary-armel/Packages
> 4ae68649dda55521511bea2ccd8c6666fd104b06 220609
main/binary-armel/Packages.bz2
> 85aa8c749562fad08b01183b2ddcd0a0ffacba1b 279170
main/binary-armel/Packages.gz
722,724c722,724
< 3a7d8d961295989ba7c92c9ec7a7dc113c9df723eb52022448b80c7e9ca7d512
1250354 main/binary-armel/Packages
< 12c3d5b3f732147b12290b03de4a50a5bdcaa1969970c395583ec572fe7ad5cc
220269 main/binary-armel/Packages.bz2
< ee927c95d79707c2bfd588893e8339d80e7687b4c7c6089f9c0ea3a17e0ed698
278365 main/binary-armel/Packages.gz
- ---
> 00c9a51718ff1cd8e68baf7f3d776ba86edf38456af74cdc44214a662e90705a
1252596 main/binary-armel/Packages
> d42434e9e12cd4fbd88b96bf696afa22089b68df926d2696a21621337843a5d6
220609 main/binary-armel/Packages.bz2
> 15025319c484642f96d83e7e4e11ed241b1b9e44e08a640d2530aed3b4ccc0fa
279170 main/binary-armel/Packages.gz
# diff
{,/}var/cache/apt-cacher-ng/security.debian.org/dists/squeeze/updates/Release.head
< Last-Modified: Sun, 24 Jun 2012 21:01:22 GMT
- ---
> Last-Modified: Mon, 25 Jun 2012 02:01:26 GMT
7c7
< Date: Sun Jun 24 22:04:55 2012
- ---
> Date: Mon Jun 25 13:44:44 2012
I could imagine that acng had updated the GPG signature, but not the
Release
file itself and therefore causing this error.
The same might apply to the list of md5sums (which come from the
Packages file, too AFAIK).
Maybe acng does not update the Release file if it has the same size as
the one stored?
- --
http://daniel.hahler.de/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFP6G4PfAK/hT/mPgARAhLGAJ98ikzLaIQYWy6Hyc24jA8Gnb9ZEgCfX1dS
YDQw49t0+RyoBFhyCccRShI=
=BkW8
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
