Skip to content

CRAN problem with plyr-1.4.1

9 messages · Douglas Bates, Ian Davis, Hadley Wickham +1 more

#
The first thing to do is try another mirror.  The "official" (or as
official as we ever get about anything) U.S. mirror is

http://cran.us.R-project.org

They tend to be very good about updating.  Presently the source
package for plyr is at version 1.5 and the binary versions are both at
1.4.1
On Mon, Apr 11, 2011 at 1:27 PM, Ian Davis <ian.w.davis at gmail.com> wrote:
#
On 11.04.2011 21:03, Douglas Bates wrote:
Right, and on CRAN master the update process was running and hence you 
got a 440. Or in other words: Please just be a bit patient after a 
package was updated, the automated processes may take a day to complete. 
You can access the repositories without any problem using 
install.packages() and friends.

Uwe Ligges
#
On 12.04.2011 14:52, Ian Davis wrote:
install.packages() works well, it is *not* broken.
yes, but that was not recent since the repository was more recent. And 
updating web pages takes its time for 3000 packages.

download.packages() would have done it fine, since it is not relying on 
the web page. But then, install.packages() worked as well.
No, I just said wait for 24 hours to be on the safe side. I does not 
take 24 hours. For binary package versions, you need to wait 72 hours 
(at least that is what we promise).


 > This means that on any given
They can always be installed, since a repository is up to date at once, 
just the web pages are not updates at once.
Unreliable mirrors are removed from the list of mirrors from time to 
time. Mirrors are updates at least twice a week.

Best,
Uwe Ligges
#
On 12.04.2011 17:08, Ian Davis wrote:
Then, can we have the ERROR message, please?
Otherwise the only explanation I can guess is that a mirror grabs the 
contents of a repository exactly in the second the repository is updated 
and that is unlikely, particularly if more than one mirror is involved.
We do care, but the mirrors seem to be fine and hence we cannot debug 
what you have seen before.

Best,
Uwe
#
Isn't one possible explanation that PACKAGES.gz on the mirror was
updated before the package directory was?  That would seem to me a
plausible hypothesis to me, because rsync seems to send files in the
top level directory before files in directories below.

Hadley
1 day later
#
On 12.04.2011 17:29, Hadley Wickham wrote:
It is in the same directory.

Uwe