Re: authors/id/B/BS/BSORAHAN/CHECKSUMS

>>>>> On Tue, 13 Sep 2011 19:47:35 +0200 (CEST), "Henk P. Penning" <[email protected]> said:

  > Hi,
  >   does anyone understand what's up with

  >     authors/id/B/BS/BSORAHAN/CHECKSUMS

  >   The past 2 weeks it appears to be in a create/delete cycle.

A checksums file should never be in delete state. There is only one
event on the PAUSE end that causes a delete of a CHECKSUMS file and that
is when the whole directory disappears.

BSORAHAN currently has three files plus checksums file:

>21:03:03 k@pause:~ftp/pub/PAUSE/authors/id/B/BS/BSORAHAN% ls -ltr
total 280
-rw-rw-r-- 1 root root   2966 2011-09-07 05:31:41 WWW-EchoNest-v0.0.2.readme
-rw-rw-r-- 1 root root   2081 2011-09-07 05:31:41 WWW-EchoNest-v0.0.2.meta
-rw-rw-r-- 1 root root 272333 2011-09-07 05:33:42 WWW-EchoNest-v0.0.2.tar.gz
-r--r--r-- 1 root root    994 2011-09-08 05:33:42 CHECKSUMS


The checksums file was created on Sep 7 and is unchanged since then:

>21:04:23 k@pause:~ftp/pub/PAUSE/authors/id/B/BS/BSORAHAN% head -10 CHECKSUMS
0&&<<''; # this PGP-signed message is also valid perl
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

# CHECKSUMS file written on Wed Sep  7 04:27:23 2011 GMT by CPAN::Checksums (v2.00)
$cksum = {
  'WWW-EchoNest-v0.0.2.meta' => {
    'md5' => 'f268d6ce0ab2555437cfba789ca17fef',
    'mtime' => '2011-09-07',
    'sha256' => 'd719a292bc9e697e590515ce2daac4c4a2e7ceaa96fcfae906a384cc75377e3f',


For debugging purposes you can always go to PAUSE directly and inspect
the RECENT files in /authors/ or /modules/. Because what Ask produces is
a made from ingredients from PAUSE and funet and what inotify then sees
on disk. Here is a glance at current state of RECENT files on PAUSE wrt.
BSORAHAN:

>21:08:15 k@pause:~ftp/pub/PAUSE/authors% grep -A1 BSORAHAN RECENT* 
RECENT-1M.yaml:    path: id/B/BS/BSORAHAN/CHECKSUMS
RECENT-1M.yaml-    type: new
--
RECENT-1M.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.2.meta
RECENT-1M.yaml-    type: new
--
RECENT-1M.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.2.readme
RECENT-1M.yaml-    type: new
--
RECENT-1M.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.2.tar.gz
RECENT-1M.yaml-    type: new
--
RECENT-1M.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.1.meta
RECENT-1M.yaml-    type: delete
--
RECENT-1M.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.1.readme
RECENT-1M.yaml-    type: delete
--
RECENT-1M.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.1.tar.gz
RECENT-1M.yaml-    type: delete
--
RECENT-1Q.yaml:    path: id/B/BS/BSORAHAN/CHECKSUMS
RECENT-1Q.yaml-    type: new
--
RECENT-1Q.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.2.meta
RECENT-1Q.yaml-    type: new
--
RECENT-1Q.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.2.readme
RECENT-1Q.yaml-    type: new
--
RECENT-1Q.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.2.tar.gz
RECENT-1Q.yaml-    type: new
--
RECENT-1Q.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.1.meta
RECENT-1Q.yaml-    type: delete
--
RECENT-1Q.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.1.readme
RECENT-1Q.yaml-    type: delete
--
RECENT-1Q.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.1.tar.gz
RECENT-1Q.yaml-    type: delete
--
RECENT-1W.yaml:    path: id/B/BS/BSORAHAN/CHECKSUMS
RECENT-1W.yaml-    type: new
--
RECENT-1W.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.2.meta
RECENT-1W.yaml-    type: new
--
RECENT-1W.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.2.readme
RECENT-1W.yaml-    type: new
--
RECENT-1W.yaml:    path: id/B/BS/BSORAHAN/WWW-EchoNest-v0.0.2.tar.gz
RECENT-1W.yaml-    type: new


I could imagine the delete comes from a mirroring event from a broken
source.


-- 
andreas