Hi,
One last quick question ... does anyone archive older CRAN package check 
summaries?  I searched the web but could not find any.  My package was archived 
in February of this year so any package check summary from earlier than that 
should help me figure out what is broken on MacOSX or Windows.  
Thanks,
Kevin


Sent from my iPad

On 2013-03-09, at 4:38 PM, Kevin Hendricks <kevin.hendri...@sympatico.ca> wrote:

> Hi, 
> Thanks for that info.  It works/builds without error or warnings on my RedHat 
> Enterprise 6  with R 2.15.2 version which I use but must be broken somehow on 
> later versions.  I will see if I can find the autobuild warnings error report 
> someplace.
> 
> Kevin
> 
> 
> Sent from my iPad
> 
> On 2013-03-09, at 4:00 PM, Henrik Bengtsson <h...@biostat.ucsf.edu> wrote:
> 
>> On Sat, Mar 9, 2013 at 12:25 PM, Kevin Hendricks
>> <kevin.hendri...@sympatico.ca> wrote:
>>> Hi,
>>> 
>>> Who should I ask about my package Rigroup_0.83 being moved to Archive 
>>> status on CRAN and no longer available via install.package?  I have no 
>>> problems with the move if this was simply because of low demand.  However, 
>>> if there was a build issue with the newest releases that caused problems, I 
>>> would be happy to address it.  I'll just ask my students to install it from 
>>> my own locally hosted source archive.
>> 
>> Most likely yourself; from the 'CRAN Repository Policy'
>> [http://cran.r-project.org/web/packages/policies.html]:
>> 
>> "Packages will not normally be removed from CRAN: however, they may be
>> archived, including at the maintainer's request.
>> 
>> Packages for which R CMD check gives an ‘ERROR’ when a new R x.y.0
>> version is released will be archived (or in exceptional circumstances
>> updated by the CRAN team) unless the maintainer has set a firm
>> deadline for an upcoming update (and keeps to it).
>> 
>> Maintainers will be asked to update packages which show any warnings
>> or significant notes, especially at around the time of a new x.y.0
>> release. Packages which are not updated are liable to be archived."
>> 
>> /Henrik
>> 
>>> 
>>> Thanks,
>>> 
>>> Kevin
>>> ______________________________________________
>>> R-devel@r-project.org mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-devel
> 
> ______________________________________________
> R-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel

Reply via email to