>>>>> On Fri, 30 Sep 2011 20:01:43 -0400, David Golden <xda...@gmail.com> said:
> On Fri, Sep 30, 2011 at 7:48 PM, Henk P. Penning <penn...@uu.nl> wrote: >> 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: [etc] >> >> When I "went to PAUSE" I noticed that I couldn't see anything relevant >> pertaining to the problem at hand ; hence my request. > Ah. Even I had to do some digging as I didn't remember the URLs. > You don't need a PAUSE ID -- he's talking about these files: > ftp://pause.perl.org/pub/PAUSE/ I'm sorry for the lack of clearer communication. Yes, David is right but I also meant the "authors" and "modules" slots in the pause rsync server which can be accessed more efficiently than with ftp: % rsync pause.perl.org:: PAUSE authors modules scripts pausedata pausecode The rrr code was born on pause in the two directories authors/ and modules/. It was deployed separately for the two directories. The first incarnation of the code was (and still is) based on hooks in the PAUSE code such that every (relevent) change in the file system is reflected in RECENT files. So when some file is uploaded, there is some hook that cares for the necessary manipulation in some RECENT file. Likewise when some checksum is calculated on PAUSE's behalf there is some call to a hook that makes sure that the according RECENT file is updated. Same for deletions, etc. Since CPAN is more than the two directories authors/ and modules/ we needed a different approach on the cpan master site. Instead of having hooks we opted for an inotify based mechanism as provided by linux. On the CPAN master site we have inotify running, on PAUSE we have hooks. If in doubt, hooks are better than inotify but they need more human attention. Comparing the RECENT files in PAUSE and the cpan master will help finding out where a bug is coming from. -- andreas
