Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-10 Thread Uwe Ligges
OK, the original message will be resend privately in a minute. Best, Uwe Ligges On 10.03.2013 16:54, Kevin Hendricks wrote: Sorry if you considered this a waste of bandwidth. I did not know CRAN had its own mailing list. The reason I never responded to any mail is that I never received a

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-10 Thread Kevin Hendricks
Sorry if you considered this a waste of bandwidth. I did not know CRAN had its own mailing list. The reason I never responded to any mail is that I never received any message in January (I searched my inbox for it and found nothing). It probably was stripped out by the sympatico mail server

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-10 Thread Jari Oksanen
"What we've got here is failure to communicate. Some men you just can't reach. So you get what we had here last week, which is the way he wants it. Well, he gets it. I don't like it any more than you men." (from "Cool hand Luke" -- but whose fault?) Cheers, Jari Oksanen On 10/03/2013, at 17:18

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-10 Thread Uwe Ligges
I wonder why you do not ask on CRAN@...? List members here cannot know the answer. And we typically do not discuss such matters in public. I wonder why you do not read the e-mail message you get from the CRAN team? Please see the message with subject line "Registering .External entry points" y

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
Hi Dan, In case this catches anyone else ... FWIW, I found the issue ... in my Rinit.c, my package uses the .External call which actually takes one SEXP which points to a "varargs-like" list. Under 2.15.X and earlier, I thought the proper entry for an .External call was as below since it onl

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
Hi Dan, Thank you! I dig up a Mac at work and recreate this. Kevin On 2013-03-09, at 5:52 PM, Dan Tenenbaum wrote: > On Sat, Mar 9, 2013 at 2:17 PM, Kevin Hendricks > wrote: >> Hi, >> One last quick question ... does anyone archive older CRAN package check >> summaries? I searched the web

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Dan Tenenbaum
On Sat, Mar 9, 2013 at 2:17 PM, Kevin Hendricks wrote: > 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 t

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
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.

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
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

Re: [Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Henrik Bengtsson
On Sat, Mar 9, 2013 at 12:25 PM, Kevin Hendricks 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 w

[Rd] question on why Rigroup package moved to Archive on CRAN

2013-03-09 Thread Kevin Hendricks
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