R devel - Mar 2013 - question on why Rigroup package moved to Archive on CRAN

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.

Thanks,

Kevin

On Sat, Mar 9, 2013 at 12:25 PM, Kevin Hendricks
<kevin.hendricks at 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 at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel

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 only does take one pointer as an argument:

#include "Rigroup.h"

/* Automate using sed or something. */
#if _MSC_VER >= 1000
__declspec(dllexport)
#endif

   static const R_ExternalMethodDef R_ExtDef[] = {
	{"igroupFuns", (DL_FUNC)&igroupFuns, 1},
	{NULL, NULL, 0},
   };

void R_init_Rigroup(DllInfo *info)
{
 R_registerRoutines(info,NULL,NULL,NULL,R_ExtDef);
}


But now according to the latest online docs on building your own package it
says:

"For routines with a variable number of arguments invoked viathe .External
interface, one specifies -1 for the number of arguments which tells R not to
check the actual number passed. Note that the number of arguments passed to
.External are not currently checked but they will be in R 3.0.0."

So I need to change my Rinit.c to change the "1" to a "-1"
and that error should go away.

Thanks again for all your help with this.  I will update my package and resubmit
it once version 3.0 gets released and I get a chance to verify that this does in
fact fix the problem.

Kevin

I wonder why you do not ask on CRAN at ...? 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" you got on January 20. You never answered nor fixed the package, 
hence the package has been archived.

Best,
Uwe Ligges




On 10.03.2013 02:43, Kevin Hendricks wrote:
> 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 only does take one pointer as an argument:
>
> #include "Rigroup.h"
>
> /* Automate using sed or something. */
> #if _MSC_VER >= 1000
> __declspec(dllexport)
> #endif
>
>     static const R_ExternalMethodDef R_ExtDef[] = {
> 	{"igroupFuns", (DL_FUNC)&igroupFuns, 1},
> 	{NULL, NULL, 0},
>     };
>
> void R_init_Rigroup(DllInfo *info)
> {
>   R_registerRoutines(info,NULL,NULL,NULL,R_ExtDef);
> }
>
>
> But now according to the latest online docs on building your own package it
says:
>
> "For routines with a variable number of arguments invoked viathe
.External interface, one specifies -1 for the number of arguments which tells R
not to check the actual number passed. Note that the number of arguments passed
to .External are not currently checked but they will be in R 3.0.0."
>
> So I need to change my Rinit.c to change the "1" to a
"-1" and that error should go away.
>
> Thanks again for all your help with this.  I will update my package and
resubmit it once version 3.0 gets released and I get a chance to verify that
this does in fact fix the problem.
>
> Kevin
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel
>

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 as spam.

The reason I asked here was that my package seemed to pass all tests on the
current version and I was honestly confused as to why it was removed.   In
addition, I thought others in a similar situation may benefit.   Years ago
people here were quite helpful when I first designed the package (and from the
responses many still are).  My question was not meant as an attack on you or
your processes, it was honest confusion as to why it was removed.
 
Kevin

On 2013-03-10, at 11:18 AM, Uwe Ligges <ligges at
statistik.tu-dortmund.de> wrote:
> I wonder why you do not ask on CRAN at ...? 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" you got on January 20. You never answered nor fixed the package,
hence the package has been archived.
> 
> Best,
> Uwe Ligges
> 
> 
> 
> 
> On 10.03.2013 02:43, Kevin Hendricks wrote:
>> 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 only does take one pointer as an argument:
>> 
>> #include "Rigroup.h"
>> 
>> /* Automate using sed or something. */
>> #if _MSC_VER >= 1000
>> __declspec(dllexport)
>> #endif
>> 
>>    static const R_ExternalMethodDef R_ExtDef[] = {
>> 	{"igroupFuns", (DL_FUNC)&igroupFuns, 1},
>> 	{NULL, NULL, 0},
>>    };
>> 
>> void R_init_Rigroup(DllInfo *info)
>> {
>>  R_registerRoutines(info,NULL,NULL,NULL,R_ExtDef);
>> }
>> 
>> 
>> But now according to the latest online docs on building your own
package it says:
>> 
>> "For routines with a variable number of arguments invoked viathe
.External interface, one specifies -1 for the number of arguments which tells R
not to check the actual number passed. Note that the number of arguments passed
to .External are not currently checked but they will be in R 3.0.0."
>> 
>> So I need to change my Rinit.c to change the "1" to a
"-1" and that error should go away.
>> 
>> Thanks again for all your help with this.  I will update my package and
resubmit it once version 3.0 gets released and I get a chance to verify that
this does in fact fix the problem.
>> 
>> Kevin
>> 
>> ______________________________________________
>> R-devel at r-project.org mailing list
>> https://stat.ethz.ch/mailman/listinfo/r-devel
>> 
>

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 any message in January  (I searched my inbox for it and found nothing).
It probably was stripped out by the sympatico mail server as spam.
>
> The reason I asked here was that my package seemed to pass all tests on the
current version and I was honestly confused as to why it was removed.   In
addition, I thought others in a similar situation may benefit.   Years ago
people here were quite helpful when I first designed the package (and from the
responses many still are).  My question was not meant as an attack on you or
your processes, it was honest confusion as to why it was removed.
>
> Kevin
>
> On 2013-03-10, at 11:18 AM, Uwe Ligges <ligges at
statistik.tu-dortmund.de> wrote:
>
>> I wonder why you do not ask on CRAN at ...? 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" you got on January 20. You never answered nor fixed the
package, hence the package has been archived.
>>
>> Best,
>> Uwe Ligges
>>
>>
>>
>>
>> On 10.03.2013 02:43, Kevin Hendricks wrote:
>>> 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 only does take one pointer as an argument:
>>>
>>> #include "Rigroup.h"
>>>
>>> /* Automate using sed or something. */
>>> #if _MSC_VER >= 1000
>>> __declspec(dllexport)
>>> #endif
>>>
>>>     static const R_ExternalMethodDef R_ExtDef[] = {
>>> 	{"igroupFuns", (DL_FUNC)&igroupFuns, 1},
>>> 	{NULL, NULL, 0},
>>>     };
>>>
>>> void R_init_Rigroup(DllInfo *info)
>>> {
>>>   R_registerRoutines(info,NULL,NULL,NULL,R_ExtDef);
>>> }
>>>
>>>
>>> But now according to the latest online docs on building your own
package it says:
>>>
>>> "For routines with a variable number of arguments invoked
viathe .External interface, one specifies -1 for the number of arguments which
tells R not to check the actual number passed. Note that the number of arguments
passed to .External are not currently checked but they will be in R 3.0.0."
>>>
>>> So I need to change my Rinit.c to change the "1" to a
"-1" and that error should go away.
>>>
>>> Thanks again for all your help with this.  I will update my package
and resubmit it once version 3.0 gets released and I get a chance to verify that
this does in fact fix the problem.
>>>
>>> Kevin
>>>
>>> ______________________________________________
>>> R-devel at r-project.org mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-devel
>>>
>>
>