Re: [R-pkg-devel] How to request for an Non Maintainer update - NMU

[obrl soil]

Hi,

A note for the list, since this may pop up again: ggtern is not abandoned, and 
is back on CRAN. The active development repo is on bitbucket at 
https://bitbucket.org/nicholasehamilton/ggtern/src/master/ 

There is also a github repo https://github.com/nicholasehamilton/ggtern that is 
not active, but does get pinged regularly because its not been made clear that 
development is ongoing elsewhere. The package DESCRIPTION URL field points to 
http://www.ggtern.com/, but its not obvious where the active repo is until you 
navigate to http://www.ggtern.com/docs/ and look at the dev url quoted. 

I wonder if it should be CRAN policy that the DESCRIPTION URL points only to an 
active repo, but I imagine there would be a significant policing burden 
associated with such a change.

L

From: R-package-devel  on behalf of 
Bernd.Gruber 
Sent: Tuesday, June 6, 2023 6:04 PM
To: r-package-devel@r-project.org 
Subject: [R-pkg-devel] How to request for an Non Maintainer update - NMU 
 
Hi everyone,

I am the maintainer of a package (dartR) that depends on ggtern (a package that 
seems not to be maintained anymore).
Currently the package was removed from CRAN (about 4 weeks ago) due to a simple 
error, which can be easily fixed. This was kindly achieved by Roger Bivand 
(simply the remove of a backslash does the trick).

In an github exchange he also suggested to have an non maintainer update (NMU) 
for the package in the short term (and find a replacement of orphan the package 
and find a new maintainer in the long term).

Here is my first question as I did not find an answer googling it.

How can I ask, request for an NMU? Would I simply write to CRAN and describe 
the situation and send the files that need to be replaced?

The second question is, how I would request to orphan the package and what is 
the procedure to find a new maintainer (as it relies on ggplot code and this is 
not really my strength, hence I would try to find someone else to take over).

Thanks a lot, Bernd



==
Dr Bernd Gruber  )/_
 _.--..---"-,--c_
Professor Ecological Modelling  \|..'   ._O__)_
Tel: (02) 6206 3804 ,=.    _.+   _ \..--( /
Fax: (02) 6201 2328   \\.-''_.-' \ ( \_
Institute for Applied Ecology  `'''   `\__   /\
Faculty of Science and Technology  ')
University of Canberra   ACT 2601 AUSTRALIA
Email: bernd.gru...@canberra.edu.au
WWW: 
bernd-gruber

Australian Government Higher Education Provider Number CRICOS #00212K
NOTICE & DISCLAIMER: This email and any files transmitted with it may contain
confidential or copyright material and are for the attention of the addressee
only. If you have received this email in error please notify us by email
reply and delete it from your system. The University of Canberra accepts
no liability for any damage caused by any virus transmitted by this email.
==

[UC Logo]

[Research Festival,5-8 June 
2023]



The Ngunnawal people are the Traditional Custodians of the ACT where UC's Bruce 
Campus is situated and are an integral and celebrated part of UC's culture. We 
also acknowledge other First Nations Peoples.

Australian Government Higher Education Registered Provider (CRICOS) #00212K. 
TEQSA Provider ID: PRV12003 (Australian University)
Email 
Disclaimer

[UC Facebook]    [UC Twitter] 
 [UC Instagram] 
 [UC Linkedin] 
 [UC Youtube] 
 [University of Canberra] 


    [[alternative HTML version deleted]]

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

[R-pkg-devel] New R CMD check warnings for html files

[arilamstein]

Background: An old package that I maintain on CRAN recently stopped working
due to changes in R 4.3.0. In a previous post (
https://stat.ethz.ch/pipermail/r-package-devel/2023q2/009268.html) people
here helped me find the best solution to the crash bug.

I would like to push this fix to CRAN as quickly as possible. However, when
I run R CMD check I now get a ton of warnings in what I assume is the
conversion of the man files from .Rd to .html files. I assume that CRAN
will reject the package due to the warnings. However, I don't really
understand the warnings, or why they are occurring now (they did not happen
before). Can someone here help me?

The last group of the warnings:

visualize_df_by_race_ethnicity_party.html:4:1
(visualize_df_by_race_ethnicity_party.Rd:5): Warning:  inserting
"type" attribute
visualize_df_by_race_ethnicity_party.html:12:1
(visualize_df_by_race_ethnicity_party.Rd:5): Warning: 

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[David Hugh-Jones]

I think trying to guess where topics have moved will be hard. I'll consider
version links.
David


On Fri, 30 Jun 2023 at 17:04, Duncan Murdoch 
wrote:

> I agree, really nice.
>
> One suggestion would be to check for the existence of the corresponding
> topic link.
>
> For example,
>  links to
> ,
>
> which doesn't exist.  The generic is now in the base package, at
> .
>
> Duncan Murdoch
>
> On 30/06/2023 11:37 a.m., Ben Bolker wrote:
> > Nice! (I like "A longer description will go here eventually.")
> >
> >It would be cute/handy to have navigation links available for "go to
> > this help page in the next (previous) version of R" (if it's not a huge
> > pain)
> >
> > On 2023-06-30 11:10 a.m., David Hugh-Jones wrote:
> >> OK, so I took Jeff's hint and did this myself!
> >>
> >> https://github.com/hughjonesd/r-help
> >>
> >> Sample page for ?plot from the first version of R (at least, the first
> >> version that is on svn):
> >>
> >> https://hughjonesd.github.io/r-help/0.60/base/plot.html
> >>
> >> Not everything is guaranteed to work, so please report bugs if you find
> any.
> >>
> >> Cheers,
> >> David
> >>
> >>
> >> On Fri, 30 Jun 2023 at 13:23, David Hugh-Jones <
> davidhughjo...@gmail.com>
> >> wrote:
> >>
> >>>
> >>> There are plenty of places to find current docs. I think it’s fine to
> have
> >>> versioned ones also. I agree it would be a good idea to clearly signal
> >>> “hey, this is an old version” - indeed I’ve been bitten by that in
> python
> >>> before. I’m working on this now… will see what I can do.
> >>>
> >>> Does anyone happen to know if it’s possible to create 00index files
> >>> without installing the relevant package? (Loading R 0.60 is
> challenging…)
> >>>
> >>> D
> >>>
> >>>
> >>>
> >>> On Fri, 30 Jun 2023 at 13:02, Duncan Murdoch  >
> >>> wrote:
> >>>
>  On 30/06/2023 7:57 a.m., David Hugh-Jones wrote:
> > Static web pages get indexed by google.
> 
>  Isn't that an argument against having static pages?  If I do a Google
>  search for "R lm" I think it's better to find the current docs rather
>  than dozens of obsolete versions.  It's rare that someone wants to see
>  changes across versions, so doing that should take extra work.
> 
>  Duncan Murdoch
> 
> >
> > David
> >
> >
> > On Fri, 30 Jun 2023 at 09:55, Duncan Murdoch <
> murdoch.dun...@gmail.com
> > > wrote:
> >
> >   Why store them?  Download the source on demand, and convert it.
>  Seems
> >   pretty simple.
> >
> >   Duncan Murdoch
> >
> >   On 30/06/2023 1:19 a.m., David Hugh-Jones wrote:
> >> This is for the rcheology package. I run a Shiny web app
> which
> >   lets you
> >> examine changes to functions across R versions:
> >>
> >> https://hughjonesd.shinyapps.io/rcheology/
> >   
> >>
> >> Manually storing and converting the Rd might be possible,
> but it
> >   would be
> >> burdensome in terms of data (and my time). And if the Rd
> spec has
> >   changed
> >> across versions, that’s another problem.
> >>
> >> More generally, shouldn’t there be publicly available
> versioned
> >> documentation? Python has had this for a long time.
> >>
> >> David
> >>
> >>
> >> On Fri, 30 Jun 2023 at 01:01, Jeff Newmiller
> >   mailto:jdnew...@dcn.davis.ca.us>>
> >> wrote:
> >>
> >>> Sure. On your computer. Install the old version of R and
> let it
> >   serve the
> >>> relevant docs.
> >>>
> >>> Dunno of anyone doing this historical dive online for you
> >   though. Why
> >>> would you want preformatted docs if you didn't have those
> old
> >   versions
> >>> installed?
> >>>
> >>> On June 29, 2023 4:23:55 PM PDT, David Hugh-Jones <
> >>> davidhughjo...@gmail.com  >>
>  wrote:
> >>>> That’s useful to know. But is there anywhere with
> preformatted
> >   HTML pages?
> >>>>
> >>>> Cheers, D
> >>>>
> >>>> On Thu, 29 Jun 2023 at 21:46, Ivan Krylov
> >   mailto:krylov.r...@gmail.com>> wrote:
> >>>>
> > On Thu, 29 Jun 2023 20:22:47 +0100
> > David Hugh-Jones  >   > wrote:
> >
> >> I'm looking for a source of online help for R base
> >  

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[Duncan Murdoch]

I agree, really nice.

One suggestion would be to check for the existence of the corresponding 
topic link.


For example, 
 links to 
, 
which doesn't exist.  The generic is now in the base package, at 
.


Duncan Murdoch

On 30/06/2023 11:37 a.m., Ben Bolker wrote:

Nice! (I like "A longer description will go here eventually.")

   It would be cute/handy to have navigation links available for "go to
this help page in the next (previous) version of R" (if it's not a huge
pain)

On 2023-06-30 11:10 a.m., David Hugh-Jones wrote:

OK, so I took Jeff's hint and did this myself!

https://github.com/hughjonesd/r-help

Sample page for ?plot from the first version of R (at least, the first
version that is on svn):

https://hughjonesd.github.io/r-help/0.60/base/plot.html

Not everything is guaranteed to work, so please report bugs if you find any.

Cheers,
David


On Fri, 30 Jun 2023 at 13:23, David Hugh-Jones 
wrote:



There are plenty of places to find current docs. I think it’s fine to have
versioned ones also. I agree it would be a good idea to clearly signal
“hey, this is an old version” - indeed I’ve been bitten by that in python
before. I’m working on this now… will see what I can do.

Does anyone happen to know if it’s possible to create 00index files
without installing the relevant package? (Loading R 0.60 is challenging…)

D



On Fri, 30 Jun 2023 at 13:02, Duncan Murdoch 
wrote:


On 30/06/2023 7:57 a.m., David Hugh-Jones wrote:

Static web pages get indexed by google.


Isn't that an argument against having static pages?  If I do a Google
search for "R lm" I think it's better to find the current docs rather
than dozens of obsolete versions.  It's rare that someone wants to see
changes across versions, so doing that should take extra work.

Duncan Murdoch



David


On Fri, 30 Jun 2023 at 09:55, Duncan Murdoch mailto:murdoch.dun...@gmail.com>> wrote:

  Why store them?  Download the source on demand, and convert it.

Seems

  pretty simple.

  Duncan Murdoch

  On 30/06/2023 1:19 a.m., David Hugh-Jones wrote:
   > This is for the rcheology package. I run a Shiny web app which
  lets you
   > examine changes to functions across R versions:
   >
   > https://hughjonesd.shinyapps.io/rcheology/
  
   >
   > Manually storing and converting the Rd might be possible, but it
  would be
   > burdensome in terms of data (and my time). And if the Rd spec has
  changed
   > across versions, that’s another problem.
   >
   > More generally, shouldn’t there be publicly available versioned
   > documentation? Python has had this for a long time.
   >
   > David
   >
   >
   > On Fri, 30 Jun 2023 at 01:01, Jeff Newmiller
  mailto:jdnew...@dcn.davis.ca.us>>
   > wrote:
   >
   >> Sure. On your computer. Install the old version of R and let it
  serve the
   >> relevant docs.
   >>
   >> Dunno of anyone doing this historical dive online for you
  though. Why
   >> would you want preformatted docs if you didn't have those old
  versions
   >> installed?
   >>
   >> On June 29, 2023 4:23:55 PM PDT, David Hugh-Jones <
   >> davidhughjo...@gmail.com >

wrote:

   >>> That’s useful to know. But is there anywhere with preformatted
  HTML pages?
   >>>
   >>> Cheers, D
   >>>
   >>> On Thu, 29 Jun 2023 at 21:46, Ivan Krylov
  mailto:krylov.r...@gmail.com>> wrote:
   >>>
    On Thu, 29 Jun 2023 20:22:47 +0100
    David Hugh-Jones mailto:davidhughjo...@gmail.com>> wrote:
   
   > I'm looking for a source of online help for R base
   > packages, which covers all versions (for some reasonable

value of

   > "all"). So e.g. the equivalent of `?lm` for R 4.1.0.
   
    These live in the R source tree, under src/library:
    https://svn.r-project.org/R/trunk/src/library/
  
   
    For the actual releases of R, you may have to go looking at

the

    branches inside that repository, e.g., the following command:
   
    svn log \
   
   
   >>


https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd
<
https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd


   
    ...should tell you the history of ?lm until the latest
  R-4.1-patched.
   
    Do the Git mirrors track these release branches? The branching
  model of
    Subversion [*] is different from the Git model, so perhaps

not.

   

Re: [R-pkg-devel] devtools::submit_cran() failure

[Ivan Krylov]

В Fri, 30 Jun 2023 14:39:31 +0100
Alan Inglis  пишет:

> Error in if (new_url$query$submit == "1") { : argument is of length
> zero

If this isn't a one-off network hiccup that cannot be subsequently
reproduced, this seems to be a problem in devtools. The code doesn't
check the value returned from httr::parse_url(...) for correctness
before trying to find out whether it was redirected to a URL containing
...=1:

https://github.com/r-lib/devtools/blob/69d6104/R/release.R#L308-L311

You can report this problem at
.

Meanwhile, submit the package using the web form at
. Perhaps you'll get a
human-readable error message that will help devtools developers handle
cases like this in the future.

-- 
Best regards,
Ivan

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

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[Ben Bolker]

  Nice! (I like "A longer description will go here eventually.")

 It would be cute/handy to have navigation links available for "go to 
this help page in the next (previous) version of R" (if it's not a huge 
pain)


On 2023-06-30 11:10 a.m., David Hugh-Jones wrote:

OK, so I took Jeff's hint and did this myself!

https://github.com/hughjonesd/r-help

Sample page for ?plot from the first version of R (at least, the first
version that is on svn):

https://hughjonesd.github.io/r-help/0.60/base/plot.html

Not everything is guaranteed to work, so please report bugs if you find any.

Cheers,
David


On Fri, 30 Jun 2023 at 13:23, David Hugh-Jones 
wrote:



There are plenty of places to find current docs. I think it’s fine to have
versioned ones also. I agree it would be a good idea to clearly signal
“hey, this is an old version” - indeed I’ve been bitten by that in python
before. I’m working on this now… will see what I can do.

Does anyone happen to know if it’s possible to create 00index files
without installing the relevant package? (Loading R 0.60 is challenging…)

D



On Fri, 30 Jun 2023 at 13:02, Duncan Murdoch 
wrote:


On 30/06/2023 7:57 a.m., David Hugh-Jones wrote:

Static web pages get indexed by google.


Isn't that an argument against having static pages?  If I do a Google
search for "R lm" I think it's better to find the current docs rather
than dozens of obsolete versions.  It's rare that someone wants to see
changes across versions, so doing that should take extra work.

Duncan Murdoch



David


On Fri, 30 Jun 2023 at 09:55, Duncan Murdoch mailto:murdoch.dun...@gmail.com>> wrote:

 Why store them?  Download the source on demand, and convert it.

Seems

 pretty simple.

 Duncan Murdoch

 On 30/06/2023 1:19 a.m., David Hugh-Jones wrote:
  > This is for the rcheology package. I run a Shiny web app which
 lets you
  > examine changes to functions across R versions:
  >
  > https://hughjonesd.shinyapps.io/rcheology/
 
  >
  > Manually storing and converting the Rd might be possible, but it
 would be
  > burdensome in terms of data (and my time). And if the Rd spec has
 changed
  > across versions, that’s another problem.
  >
  > More generally, shouldn’t there be publicly available versioned
  > documentation? Python has had this for a long time.
  >
  > David
  >
  >
  > On Fri, 30 Jun 2023 at 01:01, Jeff Newmiller
 mailto:jdnew...@dcn.davis.ca.us>>
  > wrote:
  >
  >> Sure. On your computer. Install the old version of R and let it
 serve the
  >> relevant docs.
  >>
  >> Dunno of anyone doing this historical dive online for you
 though. Why
  >> would you want preformatted docs if you didn't have those old
 versions
  >> installed?
  >>
  >> On June 29, 2023 4:23:55 PM PDT, David Hugh-Jones <
  >> davidhughjo...@gmail.com >

wrote:

  >>> That’s useful to know. But is there anywhere with preformatted
 HTML pages?
  >>>
  >>> Cheers, D
  >>>
  >>> On Thu, 29 Jun 2023 at 21:46, Ivan Krylov
 mailto:krylov.r...@gmail.com>> wrote:
  >>>
   On Thu, 29 Jun 2023 20:22:47 +0100
   David Hugh-Jones mailto:davidhughjo...@gmail.com>> wrote:
  
  > I'm looking for a source of online help for R base
  > packages, which covers all versions (for some reasonable

value of

  > "all"). So e.g. the equivalent of `?lm` for R 4.1.0.
  
   These live in the R source tree, under src/library:
   https://svn.r-project.org/R/trunk/src/library/
 
  
   For the actual releases of R, you may have to go looking at

the

   branches inside that repository, e.g., the following command:
  
   svn log \
  
  
  >>


https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd
<
https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd


  
   ...should tell you the history of ?lm until the latest
 R-4.1-patched.
  
   Do the Git mirrors track these release branches? The branching
 model of
   Subversion [*] is different from the Git model, so perhaps

not.

  
   --
   Best regards,
   Ivan
  
   [*]
 https://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html
 >
  >> --
  >> Sent from my phone. Please excuse my brevity.
  >>
  >> __
  >> R-package-devel@r-project.org
  mailing list
  >> https://stat.ethz.ch/mailman/listinfo/r-package-devel
 

[R-pkg-devel] devtools::submit_cran() failure

[Alan Inglis]

Hi,

I'm getting the following error when using devtools::submit_cran()

--|
Ready to submit colouR (0.1.0) to CRAN?

1: No
2: U... Maybe?
3: For sure

Selection: 3
ℹ Uploading package & comments
ℹ Confirming submission
Error in if (new_url$query$submit == "1") { : argument is of length zero

--|

I saw people having a similar issue here:
https://www.mail-archive.com/r-package-devel@r-project.org/msg06256.html

and here: https://github.com/r-lib/devtools/issues/2208

However, no solution was presented. I'm not sure where I should go from
here!?

Thanks,
Alan

[[alternative HTML version deleted]]

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

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[David Hugh-Jones]

OK, so I took Jeff's hint and did this myself!

https://github.com/hughjonesd/r-help

Sample page for ?plot from the first version of R (at least, the first
version that is on svn):

https://hughjonesd.github.io/r-help/0.60/base/plot.html

Not everything is guaranteed to work, so please report bugs if you find any.

Cheers,
David


On Fri, 30 Jun 2023 at 13:23, David Hugh-Jones 
wrote:

>
> There are plenty of places to find current docs. I think it’s fine to have
> versioned ones also. I agree it would be a good idea to clearly signal
> “hey, this is an old version” - indeed I’ve been bitten by that in python
> before. I’m working on this now… will see what I can do.
>
> Does anyone happen to know if it’s possible to create 00index files
> without installing the relevant package? (Loading R 0.60 is challenging…)
>
> D
>
>
>
> On Fri, 30 Jun 2023 at 13:02, Duncan Murdoch 
> wrote:
>
>> On 30/06/2023 7:57 a.m., David Hugh-Jones wrote:
>> > Static web pages get indexed by google.
>>
>> Isn't that an argument against having static pages?  If I do a Google
>> search for "R lm" I think it's better to find the current docs rather
>> than dozens of obsolete versions.  It's rare that someone wants to see
>> changes across versions, so doing that should take extra work.
>>
>> Duncan Murdoch
>>
>> >
>> > David
>> >
>> >
>> > On Fri, 30 Jun 2023 at 09:55, Duncan Murdoch > > > wrote:
>> >
>> > Why store them?  Download the source on demand, and convert it.
>> Seems
>> > pretty simple.
>> >
>> > Duncan Murdoch
>> >
>> > On 30/06/2023 1:19 a.m., David Hugh-Jones wrote:
>> >  > This is for the rcheology package. I run a Shiny web app which
>> > lets you
>> >  > examine changes to functions across R versions:
>> >  >
>> >  > https://hughjonesd.shinyapps.io/rcheology/
>> > 
>> >  >
>> >  > Manually storing and converting the Rd might be possible, but it
>> > would be
>> >  > burdensome in terms of data (and my time). And if the Rd spec has
>> > changed
>> >  > across versions, that’s another problem.
>> >  >
>> >  > More generally, shouldn’t there be publicly available versioned
>> >  > documentation? Python has had this for a long time.
>> >  >
>> >  > David
>> >  >
>> >  >
>> >  > On Fri, 30 Jun 2023 at 01:01, Jeff Newmiller
>> > mailto:jdnew...@dcn.davis.ca.us>>
>> >  > wrote:
>> >  >
>> >  >> Sure. On your computer. Install the old version of R and let it
>> > serve the
>> >  >> relevant docs.
>> >  >>
>> >  >> Dunno of anyone doing this historical dive online for you
>> > though. Why
>> >  >> would you want preformatted docs if you didn't have those old
>> > versions
>> >  >> installed?
>> >  >>
>> >  >> On June 29, 2023 4:23:55 PM PDT, David Hugh-Jones <
>> >  >> davidhughjo...@gmail.com >
>> wrote:
>> >  >>> That’s useful to know. But is there anywhere with preformatted
>> > HTML pages?
>> >  >>>
>> >  >>> Cheers, D
>> >  >>>
>> >  >>> On Thu, 29 Jun 2023 at 21:46, Ivan Krylov
>> > mailto:krylov.r...@gmail.com>> wrote:
>> >  >>>
>> >   On Thu, 29 Jun 2023 20:22:47 +0100
>> >   David Hugh-Jones > > > wrote:
>> >  
>> >  > I'm looking for a source of online help for R base
>> >  > packages, which covers all versions (for some reasonable
>> value of
>> >  > "all"). So e.g. the equivalent of `?lm` for R 4.1.0.
>> >  
>> >   These live in the R source tree, under src/library:
>> >   https://svn.r-project.org/R/trunk/src/library/
>> > 
>> >  
>> >   For the actual releases of R, you may have to go looking at
>> the
>> >   branches inside that repository, e.g., the following command:
>> >  
>> >   svn log \
>> >  
>> >  
>> >  >>
>> >
>> https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd
>> <
>> https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd
>> >
>> >  
>> >   ...should tell you the history of ?lm until the latest
>> > R-4.1-patched.
>> >  
>> >   Do the Git mirrors track these release branches? The branching
>> > model of
>> >   Subversion [*] is different from the Git model, so perhaps
>> not.
>> >  
>> >   --
>> >   Best regards,
>> >   Ivan
>> >  
>> >   [*]
>> > https://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html
>> > > >
>> >  
>> >  >>
>> >  >> --
>> >  >> Sent from my phone. Please excuse my brevity.
>> >  >>
>> >  >> 

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[David Hugh-Jones]

There are plenty of places to find current docs. I think it’s fine to have
versioned ones also. I agree it would be a good idea to clearly signal
“hey, this is an old version” - indeed I’ve been bitten by that in python
before. I’m working on this now… will see what I can do.

Does anyone happen to know if it’s possible to create 00index files without
installing the relevant package? (Loading R 0.60 is challenging…)

D



On Fri, 30 Jun 2023 at 13:02, Duncan Murdoch 
wrote:

> On 30/06/2023 7:57 a.m., David Hugh-Jones wrote:
> > Static web pages get indexed by google.
>
> Isn't that an argument against having static pages?  If I do a Google
> search for "R lm" I think it's better to find the current docs rather
> than dozens of obsolete versions.  It's rare that someone wants to see
> changes across versions, so doing that should take extra work.
>
> Duncan Murdoch
>
> >
> > David
> >
> >
> > On Fri, 30 Jun 2023 at 09:55, Duncan Murdoch  > > wrote:
> >
> > Why store them?  Download the source on demand, and convert it.
> Seems
> > pretty simple.
> >
> > Duncan Murdoch
> >
> > On 30/06/2023 1:19 a.m., David Hugh-Jones wrote:
> >  > This is for the rcheology package. I run a Shiny web app which
> > lets you
> >  > examine changes to functions across R versions:
> >  >
> >  > https://hughjonesd.shinyapps.io/rcheology/
> > 
> >  >
> >  > Manually storing and converting the Rd might be possible, but it
> > would be
> >  > burdensome in terms of data (and my time). And if the Rd spec has
> > changed
> >  > across versions, that’s another problem.
> >  >
> >  > More generally, shouldn’t there be publicly available versioned
> >  > documentation? Python has had this for a long time.
> >  >
> >  > David
> >  >
> >  >
> >  > On Fri, 30 Jun 2023 at 01:01, Jeff Newmiller
> > mailto:jdnew...@dcn.davis.ca.us>>
> >  > wrote:
> >  >
> >  >> Sure. On your computer. Install the old version of R and let it
> > serve the
> >  >> relevant docs.
> >  >>
> >  >> Dunno of anyone doing this historical dive online for you
> > though. Why
> >  >> would you want preformatted docs if you didn't have those old
> > versions
> >  >> installed?
> >  >>
> >  >> On June 29, 2023 4:23:55 PM PDT, David Hugh-Jones <
> >  >> davidhughjo...@gmail.com >
> wrote:
> >  >>> That’s useful to know. But is there anywhere with preformatted
> > HTML pages?
> >  >>>
> >  >>> Cheers, D
> >  >>>
> >  >>> On Thu, 29 Jun 2023 at 21:46, Ivan Krylov
> > mailto:krylov.r...@gmail.com>> wrote:
> >  >>>
> >   On Thu, 29 Jun 2023 20:22:47 +0100
> >   David Hugh-Jones  > > wrote:
> >  
> >  > I'm looking for a source of online help for R base
> >  > packages, which covers all versions (for some reasonable
> value of
> >  > "all"). So e.g. the equivalent of `?lm` for R 4.1.0.
> >  
> >   These live in the R source tree, under src/library:
> >   https://svn.r-project.org/R/trunk/src/library/
> > 
> >  
> >   For the actual releases of R, you may have to go looking at the
> >   branches inside that repository, e.g., the following command:
> >  
> >   svn log \
> >  
> >  
> >  >>
> >
> https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd
> <
> https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd
> >
> >  
> >   ...should tell you the history of ?lm until the latest
> > R-4.1-patched.
> >  
> >   Do the Git mirrors track these release branches? The branching
> > model of
> >   Subversion [*] is different from the Git model, so perhaps not.
> >  
> >   --
> >   Best regards,
> >   Ivan
> >  
> >   [*]
> > https://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html
> > 
> >  
> >  >>
> >  >> --
> >  >> Sent from my phone. Please excuse my brevity.
> >  >>
> >  >> __
> >  >> R-package-devel@r-project.org
> >  mailing list
> >  >> https://stat.ethz.ch/mailman/listinfo/r-package-devel
> > 
> >  >>
> >
>
> --
Sent from Gmail Mobile

[[alternative HTML version deleted]]

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

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[Duncan Murdoch]

On 30/06/2023 7:57 a.m., David Hugh-Jones wrote:

Static web pages get indexed by google.


Isn't that an argument against having static pages?  If I do a Google 
search for "R lm" I think it's better to find the current docs rather 
than dozens of obsolete versions.  It's rare that someone wants to see 
changes across versions, so doing that should take extra work.


Duncan Murdoch



David


On Fri, 30 Jun 2023 at 09:55, Duncan Murdoch > wrote:


Why store them?  Download the source on demand, and convert it.  Seems
pretty simple.

Duncan Murdoch

On 30/06/2023 1:19 a.m., David Hugh-Jones wrote:
 > This is for the rcheology package. I run a Shiny web app which
lets you
 > examine changes to functions across R versions:
 >
 > https://hughjonesd.shinyapps.io/rcheology/

 >
 > Manually storing and converting the Rd might be possible, but it
would be
 > burdensome in terms of data (and my time). And if the Rd spec has
changed
 > across versions, that’s another problem.
 >
 > More generally, shouldn’t there be publicly available versioned
 > documentation? Python has had this for a long time.
 >
 > David
 >
 >
 > On Fri, 30 Jun 2023 at 01:01, Jeff Newmiller
mailto:jdnew...@dcn.davis.ca.us>>
 > wrote:
 >
 >> Sure. On your computer. Install the old version of R and let it
serve the
 >> relevant docs.
 >>
 >> Dunno of anyone doing this historical dive online for you
though. Why
 >> would you want preformatted docs if you didn't have those old
versions
 >> installed?
 >>
 >> On June 29, 2023 4:23:55 PM PDT, David Hugh-Jones <
 >> davidhughjo...@gmail.com > wrote:
 >>> That’s useful to know. But is there anywhere with preformatted
HTML pages?
 >>>
 >>> Cheers, D
 >>>
 >>> On Thu, 29 Jun 2023 at 21:46, Ivan Krylov
mailto:krylov.r...@gmail.com>> wrote:
 >>>
  On Thu, 29 Jun 2023 20:22:47 +0100
  David Hugh-Jones mailto:davidhughjo...@gmail.com>> wrote:
 
 > I'm looking for a source of online help for R base
 > packages, which covers all versions (for some reasonable value of
 > "all"). So e.g. the equivalent of `?lm` for R 4.1.0.
 
  These live in the R source tree, under src/library:
  https://svn.r-project.org/R/trunk/src/library/

 
  For the actual releases of R, you may have to go looking at the
  branches inside that repository, e.g., the following command:
 
  svn log \
 
 
 >>
https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd 

 
  ...should tell you the history of ?lm until the latest
R-4.1-patched.
 
  Do the Git mirrors track these release branches? The branching
model of
  Subversion [*] is different from the Git model, so perhaps not.
 
  --
  Best regards,
  Ivan
 
  [*]
https://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html

 
 >>
 >> --
 >> Sent from my phone. Please excuse my brevity.
 >>
 >> __
 >> R-package-devel@r-project.org
 mailing list
 >> https://stat.ethz.ch/mailman/listinfo/r-package-devel

 >>



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

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[David Hugh-Jones]

Static web pages get indexed by google.

David


On Fri, 30 Jun 2023 at 09:55, Duncan Murdoch 
wrote:

> Why store them?  Download the source on demand, and convert it.  Seems
> pretty simple.
>
> Duncan Murdoch
>
> On 30/06/2023 1:19 a.m., David Hugh-Jones wrote:
> > This is for the rcheology package. I run a Shiny web app which lets you
> > examine changes to functions across R versions:
> >
> > https://hughjonesd.shinyapps.io/rcheology/
> >
> > Manually storing and converting the Rd might be possible, but it would be
> > burdensome in terms of data (and my time). And if the Rd spec has changed
> > across versions, that’s another problem.
> >
> > More generally, shouldn’t there be publicly available versioned
> > documentation? Python has had this for a long time.
> >
> > David
> >
> >
> > On Fri, 30 Jun 2023 at 01:01, Jeff Newmiller 
> > wrote:
> >
> >> Sure. On your computer. Install the old version of R and let it serve
> the
> >> relevant docs.
> >>
> >> Dunno of anyone doing this historical dive online for you though. Why
> >> would you want preformatted docs if you didn't have those old versions
> >> installed?
> >>
> >> On June 29, 2023 4:23:55 PM PDT, David Hugh-Jones <
> >> davidhughjo...@gmail.com> wrote:
> >>> That’s useful to know. But is there anywhere with preformatted HTML
> pages?
> >>>
> >>> Cheers, D
> >>>
> >>> On Thu, 29 Jun 2023 at 21:46, Ivan Krylov 
> wrote:
> >>>
>  On Thu, 29 Jun 2023 20:22:47 +0100
>  David Hugh-Jones  wrote:
> 
> > I'm looking for a source of online help for R base
> > packages, which covers all versions (for some reasonable value of
> > "all"). So e.g. the equivalent of `?lm` for R 4.1.0.
> 
>  These live in the R source tree, under src/library:
>  https://svn.r-project.org/R/trunk/src/library/
> 
>  For the actual releases of R, you may have to go looking at the
>  branches inside that repository, e.g., the following command:
> 
>  svn log \
> 
> 
> >>
> https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd
> 
>  ...should tell you the history of ?lm until the latest R-4.1-patched.
> 
>  Do the Git mirrors track these release branches? The branching model
> of
>  Subversion [*] is different from the Git model, so perhaps not.
> 
>  --
>  Best regards,
>  Ivan
> 
>  [*]
> https://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html
> 
> >>
> >> --
> >> Sent from my phone. Please excuse my brevity.
> >>
> >> __
> >> R-package-devel@r-project.org mailing list
> >> https://stat.ethz.ch/mailman/listinfo/r-package-devel
> >>
>
>

[[alternative HTML version deleted]]

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

Re: [R-pkg-devel] length() conflict with C++17

[Gábor Csárdi]

Yeah, I think both `R_NO_REMAP` and rearranging the includes are good
solutions, personally I would do both.

There is a container at https://r-hub.github.io/containers/ if you
want to make sure that you fixed everything:
docker run -ti ghcr.io/r-hub/containers/clang17 bash

Or, you can try the new rhub2 package, which uses the same container on GHA:
https://github.com/r-hub/rhub2#readme

Best,
Gabor


On Fri, Jun 30, 2023 at 11:39 AM Duncan Murdoch
 wrote:
>
> rgl has a lot of C++ code which is now getting errors in the clang17
> tests on CRAN:
>
>https://www.stats.ox.ac.uk/pub/bdr/clang17/rgl.log
>
> I haven't looked at the whole list yet, but many of the errors arise
> because R's include/Rinternals.h defines a length() macro, and that
> conflicts with a definition in clang's library.  For example,
>
>   /lib64/glib-2.0/include -I/usr/include/sysprof-4 -pthread  -Iext
> -Iext/glad/include  -isystem /usr/local/clang-trunk/include
> -I/usr/local/clang/include-fpic  -O3 -Wall -pedantic -frtti
> -Wp,-D_FORTIFY_SOURCE=3  -c PlaneSet.cpp -o PlaneSet.o
>   In file included from NULLgui.cpp:9:
>   In file included from ./NULLgui.h:4:
>   In file included from ./gui.h:9:
>   In file included from ./glgui.h:8:
>   In file included from
> /usr/local/clang-trunk/bin/../include/c++/v1/vector:322:
>   In file included from
> /usr/local/clang-trunk/bin/../include/c++/v1/__format/formatter_bool.h:21:
>   In file included from
> /usr/local/clang-trunk/bin/../include/c++/v1/__format/formatter_integral.h:32:
>   In file included from
> /usr/local/clang-trunk/bin/../include/c++/v1/locale:203:
>   /usr/local/clang-trunk/bin/../include/c++/v1/__locale:961:34: error:
> too many arguments provided to function-like macro invocation
>961 | int length(state_type& __st, const extern_type* __frm,
> const extern_type* __end, size_t __mx) const
>|  ^
>   /data/gannet/ripley/R/R-flang/include/Rinternals.h:968:9: note: macro
> 'length' defined here
>968 | #define length(x)   Rf_length(x)
>
> For those R users who know C++ better than me, is there a standard way
> to avoid this?  I can think of a couple that should work (e.g. defining
> R_NO_REMAP globally, or rearranging the order of includes).  I'd like to
> use the standard one if there is such a thing.
>
> Duncan Murdoch
>
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel

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

[R-pkg-devel] length() conflict with C++17

[Duncan Murdoch]

rgl has a lot of C++ code which is now getting errors in the clang17 
tests on CRAN:


  https://www.stats.ox.ac.uk/pub/bdr/clang17/rgl.log

I haven't looked at the whole list yet, but many of the errors arise 
because R's include/Rinternals.h defines a length() macro, and that 
conflicts with a definition in clang's library.  For example,


 /lib64/glib-2.0/include -I/usr/include/sysprof-4 -pthread  -Iext 
-Iext/glad/include  -isystem /usr/local/clang-trunk/include 
-I/usr/local/clang/include-fpic  -O3 -Wall -pedantic -frtti 
-Wp,-D_FORTIFY_SOURCE=3  -c PlaneSet.cpp -o PlaneSet.o

 In file included from NULLgui.cpp:9:
 In file included from ./NULLgui.h:4:
 In file included from ./gui.h:9:
 In file included from ./glgui.h:8:
 In file included from 
/usr/local/clang-trunk/bin/../include/c++/v1/vector:322:
 In file included from 
/usr/local/clang-trunk/bin/../include/c++/v1/__format/formatter_bool.h:21:
 In file included from 
/usr/local/clang-trunk/bin/../include/c++/v1/__format/formatter_integral.h:32:
 In file included from 
/usr/local/clang-trunk/bin/../include/c++/v1/locale:203:
 /usr/local/clang-trunk/bin/../include/c++/v1/__locale:961:34: error: 
too many arguments provided to function-like macro invocation
  961 | int length(state_type& __st, const extern_type* __frm, 
const extern_type* __end, size_t __mx) const

  |  ^
 /data/gannet/ripley/R/R-flang/include/Rinternals.h:968:9: note: macro 
'length' defined here

  968 | #define length(x)   Rf_length(x)

For those R users who know C++ better than me, is there a standard way 
to avoid this?  I can think of a couple that should work (e.g. defining 
R_NO_REMAP globally, or rearranging the order of includes).  I'd like to 
use the standard one if there is such a thing.


Duncan Murdoch

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

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[Duncan Murdoch]

On 29/06/2023 4:46 p.m., Ivan Krylov wrote:

On Thu, 29 Jun 2023 20:22:47 +0100
David Hugh-Jones  wrote:


I'm looking for a source of online help for R base
packages, which covers all versions (for some reasonable value of
"all"). So e.g. the equivalent of `?lm` for R 4.1.0.


These live in the R source tree, under src/library:
https://svn.r-project.org/R/trunk/src/library/

For the actual releases of R, you may have to go looking at the
branches inside that repository, e.g., the following command:

svn log \
  https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd

...should tell you the history of ?lm until the latest R-4.1-patched.

Do the Git mirrors track these release branches? The branching model of
Subversion [*] is different from the Git model, so perhaps not.



The wch/r-source mirror tracks the releases.  It takes svn tags and 
branches and converts them all to git branches.  For example, here's the 
help for Rd2HTML from R 2.9.0:



https://github.com/wch/r-source/blob/tags/R-2-9-0/src/library/tools/man/Rd2HTML.Rd

Duncan Murdoch

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

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[Duncan Murdoch]

Why store them?  Download the source on demand, and convert it.  Seems 
pretty simple.


Duncan Murdoch

On 30/06/2023 1:19 a.m., David Hugh-Jones wrote:

This is for the rcheology package. I run a Shiny web app which lets you
examine changes to functions across R versions:

https://hughjonesd.shinyapps.io/rcheology/

Manually storing and converting the Rd might be possible, but it would be
burdensome in terms of data (and my time). And if the Rd spec has changed
across versions, that’s another problem.

More generally, shouldn’t there be publicly available versioned
documentation? Python has had this for a long time.

David


On Fri, 30 Jun 2023 at 01:01, Jeff Newmiller 
wrote:


Sure. On your computer. Install the old version of R and let it serve the
relevant docs.

Dunno of anyone doing this historical dive online for you though. Why
would you want preformatted docs if you didn't have those old versions
installed?

On June 29, 2023 4:23:55 PM PDT, David Hugh-Jones <
davidhughjo...@gmail.com> wrote:

That’s useful to know. But is there anywhere with preformatted HTML pages?

Cheers, D

On Thu, 29 Jun 2023 at 21:46, Ivan Krylov  wrote:


On Thu, 29 Jun 2023 20:22:47 +0100
David Hugh-Jones  wrote:


I'm looking for a source of online help for R base
packages, which covers all versions (for some reasonable value of
"all"). So e.g. the equivalent of `?lm` for R 4.1.0.


These live in the R source tree, under src/library:
https://svn.r-project.org/R/trunk/src/library/

For the actual releases of R, you may have to go looking at the
branches inside that repository, e.g., the following command:

svn log \



https://svn.r-project.org/R/branches/R-4-1-branch/src/library/stats/man/lm.Rd


...should tell you the history of ?lm until the latest R-4.1-patched.

Do the Git mirrors track these release branches? The branching model of
Subversion [*] is different from the Git model, so perhaps not.

--
Best regards,
Ivan

[*] https://svnbook.red-bean.com/nightly/en/svn.branchmerge.using.html



--
Sent from my phone. Please excuse my brevity.

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



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

Re: [R-pkg-devel] Public URLs for help for versions of base packages

[Ivan Krylov]

On Fri, 30 Jun 2023 06:19:33 +0100
David Hugh-Jones  wrote:

> it would be burdensome in terms of data (and my time)

> More generally, shouldn’t there be publicly available versioned
> documentation? Python has had this for a long time.

CRAN has a searchable archive of R documentation for the whole CRAN at
https://search.r-project.org/, but only for the latest version of
everything. I would expect adding support for the whole history of R
base packages to be burdensome in terms of their time too, even without
considering the history of CRAN package documentation.

I suppose you could apply for a grant from the R Consortium (which
reports revenue similar to that of the Python Software Foundation) in
September or wait until next January or February and propose a Google
Summer of Docs project in order to have it done, but people in general
seem to dislike having to support infrastructure forever from now on for
projects that linearly grow in size.

-- 
Best regards,
Ivan

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