[R-pkg-devel] making packages available for 3.4.2

[Jim Lemon]

Hi Uwe,
I don't know what the problem was, but I just tried again and
everything went smoothly. I did use a different mirror (Perth instead
of Canberra), but the problem appears to be solved.

Jim


On Mon, Oct 23, 2017 at 8:46 AM, Uwe Ligges
<ligges at statistik.tu-dortmund.de> wrote:
> Not sure what you did, but e.g.
> https://cran.r-project.org/web/packages/plotrix/index.html
> shows that the sources and binaries are available and I just verified that
> the Windows binary is actually on the CRAN master.
>
> So perhaps your internet connection was flaky or you used a broken mirror?
>
> Best,
> Uwe Ligges
>
>
>
>
>
> On 22.10.2017 23:27, Jim Lemon wrote:
>>
>> Hi Uwe,
>> I know that plotrix and prettyR return this message when I tried to
>> install them last night (I'm not on my usual PC). I also maintain
>> clinsig, crank and eventInterval. I'll try to install these to see if
>> the same thing happens.
>>
>> Jim
>>
>> On Mon, Oct 23, 2017 at 8:23 AM, Uwe Ligges
>> <ligges at statistik.tu-dortmund.de> wrote:
>>>
>>> It would be helpful to know which packages you are talking about.
>>>
>>> Best,
>>> Uwe Ligges
>>>
>>>
>>>
>>> On 22.10.2017 23:22, Jim Lemon wrote:
>>>>
>>>>
>>>> I noticed yesterday that at least two packages that I maintain were
>>>> "not available for R-3.4.2". Obviously I would not like to drift into
>>>> obsolescence, and I know that the packages function with 3.4.2 as I
>>>> have been using them on a daily basis. Clearly I have missed something
>>>> about package management that marks a package as suitable for the
>>>> current version. Any hints will be greatly appreciated.
>>>>
>>>> Jim
>>>>
>>>> ______________________________________________
>>>> R-package-devel at r-project.org mailing list
>>>> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>>>>
>>>
>