Re: [R-pkg-devel] List of reverse dependencies, including archived packages

2019-02-26 Thread Dirk Eddelbuettel


On 26 February 2019 at 20:38, Uwe Ligges wrote:
| 
| 
| On 26.02.2019 18:59, Iñaki Ucar wrote:
| > On Tue, 26 Feb 2019 at 18:38, Oliver Dechant  wrote:
| >>
| >> Somewhat relatedly is there a way to monitor when a package has new
| >> reverse depends or imports added?
| > 
| > I don't know of any service currently providing this, if that's what
| > you're asking. But it's pretty straightforward to set up a cron job to
| > monitor the DESCRIPTION file of interest.
| 
| Well, if *reverse* dependencies are of interest, rather monitor he 
| package's CRAN webpage which lists reverse dependencis.

Or access the already-parsed-and-ready-to-use info:

R> crandb <- tools::CRAN_package_db()
R> colnames(crandb)
 [1] "Package" "Version" "Priority" 
  
 [4] "Depends" "Imports" "LinkingTo"
  
 [7] "Suggests""Enhances""License"  
  
[10] "License_is_FOSS" "License_restricts_use"   "OS_type"  
  
[13] "Archs"   "MD5sum"  "NeedsCompilation" 
  
[16] "Additional_repositories" "Author"  "Authors@R"
  
[19] "Biarch"  "BugReports"  "BuildKeepEmpty"   
  
[22] "BuildManual" "BuildResaveData" "BuildVignettes"   
  
[25] "Built"   "ByteCompile" "Classification/ACM"   
  
[28] "Classification/ACM-2012" "Classification/JEL"  "Classification/MSC"   
  
[31] "Classification/MSC-2010" "Collate" "Collate.unix" 
  
[34] "Collate.windows" "Contact" "Copyright"
  
[37] "Date""Description" "Encoding" 
  
[40] "KeepSource"  "Language""LazyData" 
  
[43] "LazyDataCompression" "LazyLoad""MailingList"  
  
[46] "Maintainer"  "Note""Packaged" 
  
[49] "RdMacros""SysDataCompression"  "SystemRequirements"   
  
[52] "Title"   "Type""URL"  
  
[55] "VignetteBuilder" "ZipData" "Published"
  
[58] "Path""X-CRAN-Comment"  "Reverse depends"  
  
[61] "Reverse imports" "Reverse linking to"  "Reverse suggests" 
  
[64] "Reverse enhances""MD5sum" 
R> 
R> dim(crandb)
[1] 1377665
R>

Now, if Oliver wants this _through time_ he will have snapshot it. The
information provided is always 'as is' for 'right now'.

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

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


Re: [R-pkg-devel] List of reverse dependencies, including archived packages

2019-02-26 Thread Uwe Ligges




On 26.02.2019 18:59, Iñaki Ucar wrote:

On Tue, 26 Feb 2019 at 18:38, Oliver Dechant  wrote:


Somewhat relatedly is there a way to monitor when a package has new
reverse depends or imports added?


I don't know of any service currently providing this, if that's what
you're asking. But it's pretty straightforward to set up a cron job to
monitor the DESCRIPTION file of interest.


Well, if *reverse* dependencies are of interest, rather monitor he 
package's CRAN webpage which lists reverse dependencis.


Best,
Uwe Ligges




Iñaki

__
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] List of reverse dependencies, including archived packages

2019-02-26 Thread Iñaki Ucar
On Tue, 26 Feb 2019 at 18:38, Oliver Dechant  wrote:
>
> Somewhat relatedly is there a way to monitor when a package has new
> reverse depends or imports added?

I don't know of any service currently providing this, if that's what
you're asking. But it's pretty straightforward to set up a cron job to
monitor the DESCRIPTION file of interest.

Iñaki

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


Re: [R-pkg-devel] List of reverse dependencies, including archived packages

2019-02-26 Thread Oliver Dechant
Somewhat relatedly is there a way to monitor when a package has new
reverse depends or imports added?

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


Re: [R-pkg-devel] Possible Rtools path problem

2019-02-26 Thread Horia Yeb
Hey all and thank you for helping me,
In the end, I re-installed R, and R tools and the check gives me no error
–on this computer. I tried all of the above, didn't solve the problem.

Thanks again anyway!
Horia.

On Mon, 25 Feb 2019 at 19:09, Uwe Ligges 
wrote:

> One of the programs that don't work is find from R tools if it is behind
> C:\Windows\system32 where the ompletely different windows find is found.
>
> Best,
> Uwe Ligges
>
>
> On 25.02.2019 19:06, Duncan Murdoch wrote:
> > On 25/02/2019 11:01 a.m., Dirk Eddelbuettel wrote:
> >>
> >> The R-on-Windows FAQ has recommends to NOT install in a path with
> spaces.
> >>
> >> The R Installer on Windows defaults to a path with spaces.
> >>
> >> I cannot reconcile it either. Such is life, sometimes.
> >>
> >> But when I had to work on that platform in the past I put my open source
> >> stuff into c:/opt/ -- so maybe try reinstalling?
> >>
> >> Rtools also had (has ?) a gotcha requiring c:/ placement.
> >>
> >
> > Those might be the problem, but to me it looks more like a path order
> > problem:
> >
> >> *My path.getenv is : *
> >>
> >>
> >>  [1] "C:\\Users\\ USER\\Documents\\R\\R-3.5.2\\bin\\i386"
> >>
> >>  [2] "C:\\Program Files (x86)\\Intel\\Intel(R) Management Engine
> >> Components\\iCLS\\"
> >>  [3] "C:\\Program Files\\Intel\\Intel(R) Management Engine
> >> Components\\iCLS\\"
> >>  [4] "C:\\WINDOWS\\system32"
> >>
> >>  [5] "C:\\WINDOWS"
> >>
> >>  [6] "C:\\WINDOWS\\System32\\Wbem"
> >>
> >>  [7] "C:\\WINDOWS\\System32\\WindowsPowerShell\\v1.0\\"
> >>
> >>  [8] "C:\\Program Files (x86)\\Intel\\Intel(R) Management Engine
> >> Components\\DAL"
> >>  [9] "C:\\Program Files\\Intel\\Intel(R) Management Engine
> >> Components\\DAL"
> >> [10] "C:\\Program Files (x86)\\Intel\\Intel(R) Management Engine
> >> Components\\IPT"
> >> [11] "C:\\Program Files\\Intel\\Intel(R) Management Engine
> >> Components\\IPT"
> >> [12] "C:\\Program Files\\CMake\\bin"
> >>
> >> [13] "C:\\Program Files\\R\\R-3.5.0\\bin"
> >>
> >> [14] "C:\\WINDOWS\\System32\\OpenSSH\\"
> >>
> >> [15] "C:\\HashiCorp\\Vagrant\\bin"
> >>
> >> [16] "C:\\ProgramData\\chocolatey\\bin"
> >>
> >> [17] "C:\\Program Files\\Microsoft SQL Server\\130\\Tools\\Binn\\"
> >>
> >> [18] "C:\\Program Files\\Java\\jdk1.8.0_181\\bin"
> >>
> >> [19] "C:\\Qt\\Tools\\QtCreator\\bin"
> >>
> >> [20] "C:\\Qt\\5.11.1\\msvc2017_64\\bin"
> >>
> >> [21] "C:\\Windows\\System32"
> >>
> >> [22] "C:\\Program Files (x86)\\GnuWin32\\bin"
> >>
> >> [23] "C:\\Program Files\\Git\\cmd"
> >>
> >> [24] "C:\\Rtools\\bin"
> >>
> >> [25] "C:\\Rtools\\MinGW\\bin"
> >>
> >> [26] "C:\\Users\\ USER\\AppData\\Local\\Microsoft\\WindowsApps"
> >>
> >> [27] "C:\\Users\\ USER\\AppData\\Local\\atom\\bin"
> >>
> >> [28] "C:\\Users\\ USER\\AppData\\Local\\Programs\\MiKTeX
> >> 2.9\\miktex\\bin\\x64\\"
> >
> > The OP has 23 directories in the path ahead of the Rtools directories;
> > I'd guess one of them contains a like-named command that is messing
> > things up.  From the message
> >
> >> 1: In FUN(X[[i]], ...) : this requires 'nm' to be on the PATH
> >
> > my guess would be that there's a bad 'nm.exe' somewhere in there.  The
> > real one is likely in directory 25 (I haven't got current Rtools
> > installed, so can't tell), but if there's another one earlier, things
> > won't work.
> >
> > I'd recommend putting the Rtools directories first.  That might mess up
> > one of the other programs that also wants to be first, so I wouldn't do
> > it globally, just set up a batch or cmd file to modify the path when you
> > want to use Rtools.
> >
> > Duncan Murdoch
> >
> > __
> > 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] List of reverse dependencies, including archived packages

2019-02-26 Thread Peter Carbonetto
That works quite well! Thank you for the suggestion.

Peter

On Tue, Feb 26, 2019 at 1:45 AM Iñaki Ucar  wrote:

> On Tue, 26 Feb 2019 at 05:29, Peter Carbonetto
>  wrote:
> >
> > I'm wondering if there is a way to get a list of reverse dependencies on
> > CRAN that includes archived packages.
> >
> > I am asking because "ashr", an R package I maintain, was recently removed
> > from CRAN, and now it is back after I fixed the critical problem.
> However,
> > some of the downstream packages that were affected by this removal are no
> > longer listed as a reverse dependency.
>
> I think that the easiest way is to use Microsoft's CRAN time machine
> [1]. Simply set the session's repo to the day before the archiving
> date, and then you can get the complete list using regular procedures.
>
> [1] https://mran.microsoft.com/timemachine
>
> Iñaki
>

[[alternative HTML version deleted]]

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