date:20190313

Re: [R-pkg-devel] CRAN review

2019-03-13 Thread Maëlle SALMON via R-package-devel

--- Begin Message ---
 We at Locke Data have made an hourly updated dashboard based on the FTP server
CRAN incoming dashboard • cransays

| 
| 
|  | 
CRAN incoming dashboard • cransays


 |

 |

 |



We hope it makes data more accessible whilst reducing load on the FTP server.
Maëlle.

Den tisdag 12 mars 2019 21:37:12 CET, Henrik Bengtsson 
 skrev:  
 
 You can also "follow" your package submission on the CRAN FTP server:

  ftp://cran.r-project.org/incoming/

/Henrik

On Tue, Mar 12, 2019 at 1:26 PM Duncan Murdoch  wrote:
>
> On 12/03/2019 2:57 p.m., Τόλης Χαλκής wrote:
> > Dear all,
> >
> > We have submitted a package to CRAN in 25th of February and we have not got
> > a
> > positive or a negative answer for the submission since then. Is this
> > normal? Is
> > there any way to get informed for the review process?
>
> Did you get the two messages after submission (one to confirm that you
> are the maintainer, the second to let you know the review has started)?
> They'll both have subject lines like
>
> CRAN submission 
>
>
> The first one will start out saying something like
> >
> > Dear Duncan Murdoch
> > Someone has submitted the package rgl to CRAN.
> > You are receiving this email to confirm the submission as the maintainer of
> > this package.
>
> and then ask you to confirm submission.
>
> The second one will start like
>
> > [This was generated from CRAN.R-project.org/submit.html]
> >
> > The following package was uploaded to CRAN:
> > ===
> >
> > Package Information:
> > Package: rgl
>
> A while later you should get a third message about the automatic checks.
>
> 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  
[[alternative HTML version deleted]]

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

Re: [R-pkg-devel] CRAN review

2019-03-13 Thread Maëlle SALMON via R-package-devel

--- Begin Message ---
 Sorry, the link was removed (by my copy-pasting it wrongly): 
https://itsalocke.com/cransays/articles/dashboard

Den onsdag 13 mars 2019 08:54:00 CET, Maëlle SALMON via R-package-devel 
 skrev:  
 
  We at Locke Data have made an hourly updated dashboard based on the FTP server
CRAN incoming dashboard • cransays

| 
| 
|  | 
CRAN incoming dashboard • cransays


 |

 |

 |



We hope it makes data more accessible whilst reducing load on the FTP server.
Maëlle.

    Den tisdag 12 mars 2019 21:37:12 CET, Henrik Bengtsson 
 skrev:  
 
 You can also "follow" your package submission on the CRAN FTP server:

  ftp://cran.r-project.org/incoming/

/Henrik

On Tue, Mar 12, 2019 at 1:26 PM Duncan Murdoch  wrote:
>
> On 12/03/2019 2:57 p.m., Τόλης Χαλκής wrote:
> > Dear all,
> >
> > We have submitted a package to CRAN in 25th of February and we have not got
> > a
> > positive or a negative answer for the submission since then. Is this
> > normal? Is
> > there any way to get informed for the review process?
>
> Did you get the two messages after submission (one to confirm that you
> are the maintainer, the second to let you know the review has started)?
> They'll both have subject lines like
>
> CRAN submission 
>
>
> The first one will start out saying something like
> >
> > Dear Duncan Murdoch
> > Someone has submitted the package rgl to CRAN.
> > You are receiving this email to confirm the submission as the maintainer of
> > this package.
>
> and then ask you to confirm submission.
>
> The second one will start like
>
> > [This was generated from CRAN.R-project.org/submit.html]
> >
> > The following package was uploaded to CRAN:
> > ===
> >
> > Package Information:
> > Package: rgl
>
> A while later you should get a third message about the automatic checks.
>
> 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  
    [[alternative HTML version deleted]]

__
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
  
[[alternative HTML version deleted]]

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

Re: [R-pkg-devel] CRAN review

2019-03-13 Thread Τόλης Χαλκής

Of course we will resubmit. Thank you all for the info.

Chalkis Apostolos

On Wed, 13 Mar 2019 at 10:05, Maëlle SALMON via R-package-devel <
r-package-devel@r-project.org> wrote:

>
>
>
> -- Forwarded message --
> From: "Maëlle SALMON" 
> To: Duncan Murdoch , Henrik Bengtsson <
> henrik.bengts...@gmail.com>
> Cc: r-package-devel@r-project.org
> Bcc:
> Date: Wed, 13 Mar 2019 07:56:45 + (UTC)
> Subject: Re: [R-pkg-devel] CRAN review
>  Sorry, the link was removed (by my copy-pasting it wrongly):
> https://itsalocke.com/cransays/articles/dashboard
>
> Den onsdag 13 mars 2019 08:54:00 CET, Maëlle SALMON via
> R-package-devel  skrev:
>
>   We at Locke Data have made an hourly updated dashboard based on the FTP
> server
> CRAN incoming dashboard • cransays
>
> |
> |
> |  |
> CRAN incoming dashboard • cransays
>
>
>  |
>
>  |
>
>  |
>
>
>
> We hope it makes data more accessible whilst reducing load on the FTP
> server.
> Maëlle.
>
> Den tisdag 12 mars 2019 21:37:12 CET, Henrik Bengtsson <
> henrik.bengts...@gmail.com> skrev:
>
>  You can also "follow" your package submission on the CRAN FTP server:
>
>   ftp://cran.r-project.org/incoming/
>
> /Henrik
>
> On Tue, Mar 12, 2019 at 1:26 PM Duncan Murdoch 
> wrote:
> >
> > On 12/03/2019 2:57 p.m., Τόλης Χαλκής wrote:
> > > Dear all,
> > >
> > > We have submitted a package to CRAN in 25th of February and we have
> not got
> > > a
> > > positive or a negative answer for the submission since then. Is this
> > > normal? Is
> > > there any way to get informed for the review process?
> >
> > Did you get the two messages after submission (one to confirm that you
> > are the maintainer, the second to let you know the review has started)?
> > They'll both have subject lines like
> >
> > CRAN submission 
> >
> >
> > The first one will start out saying something like
> > >
> > > Dear Duncan Murdoch
> > > Someone has submitted the package rgl to CRAN.
> > > You are receiving this email to confirm the submission as the
> maintainer of
> > > this package.
> >
> > and then ask you to confirm submission.
> >
> > The second one will start like
> >
> > > [This was generated from CRAN.R-project.org/submit.html]
> > >
> > > The following package was uploaded to CRAN:
> > > ===
> > >
> > > Package Information:
> > > Package: rgl
> >
> > A while later you should get a third message about the automatic checks.
> >
> > 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
> [[alternative HTML version deleted]]
>
> __
> R-package-devel@r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
>
> [[alternative HTML version deleted]]
>
>
>
>
> -- Forwarded message --
> From: "Maëlle SALMON via R-package-devel" 
> To: Duncan Murdoch , Henrik Bengtsson <
> henrik.bengts...@gmail.com>
> Cc: r-package-devel@r-project.org
> Bcc:
> Date: Wed, 13 Mar 2019 07:56:45 + (UTC)
> Subject: Re: [R-pkg-devel] CRAN review
> __
> 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

[R-pkg-devel] Help request on Rd2pdf | Fwd: [CRAN-pretest-archived] CRAN submission spsh 1.0.190311

2019-03-13 Thread Tobias KD Weber


Dear people,

I submitted a package to CRAN and got an error on the pdf manual 
creation (solved other minor issues, full response from 
cran-submissi...@r-project.org please see email below).


The response to an error and warnings detailed:

* using log directory 'd:/RCompile/CRANincoming/R-devel/spsh.Rcheck'

* using R Under development (unstable) (2019-03-09 r76216) * using 
platform: x86_64-w64-mingw32 (64-bit) * using session charset: ISO8859-1 
* checking for file 'spsh/DESCRIPTION' ... OK * checking extension type 
... Package * this is package 'spsh' version '1.0.190311' * package 
encoding: UTF-8 * checking CRAN incoming feasibility ... WARNING [... 
deleted  all OK ...] * checking PDF version of manual ... WARNING 
LaTeX errors when creating PDF version. This typically indicates Rd 
problems. LaTeX errors found: ! LaTeX Error: There's no line here to 
end. See the LaTeX manual or LaTeX Companion for explanation. Type H 
 for immediate help. ... ! Paragraph ended before \Rd@code was 
complete.  \par l.1340 * checking PDF version of 
manual without hyperrefs or index ... ERROR * DONE Status: 1 ERROR, 2 
WARNINGs, 1 NOTE



Turning to the R-Terminal executing /R CMD Rd2pdf/
Leads to:

Converting Rd files to LaTeX ...

  spsh_1.0.1.tar.gz

Warning in readLines(f) : line 1 appears to contain an embedded nul

Warning in readLines(f) : line 19 appears to contain an embedded nul

[... deleted many more lines ... ]

Warning in readLines(f) : line 3058 appears to contain an embedded nul

Warning in readLines(f) : line 3117 appears to contain an embedded nul

Warning in readLines(f) :

  incomplete final line found on 'spsh_1.0.1.tar.gz'

Error in iconv(lines, encoding, "UTF-8", sub = "byte") :

  embedded nul in string: 
'\001\f\023aIeK\021\030\023U\\,%\035\002\003\n\v\\}s\021heyt\036m\037 
PaK\032\027Z,C %2u@\031w\021('\017}gcn\004L\006\0267#!|E\017\


177\\1w\032|Gf\005JS*a\177F\\\aa_Yr]\033sVA~~\\,\026Sa_QnXMF\017B?O,<\003~\toMZ\023i\006\177\0\006\005qKvB_~\t\a\a5l\001\177=MWu\030]\t>JF\nDx\004T\t\023

`[\025?n)g^\004oMhW{%l\aO\fo>\033>\016{_n?]d|\v>V'


I have truely searched most of the morning for a solution, but none to 
be found.

Any ideas how to solve this would be very much appreciated.

Kind Regards,
Tobias



 Weitergeleitete Nachricht 
Betreff:[CRAN-pretest-archived] CRAN submission spsh 1.0.190311
Datum:  Tue, 12 Mar 2019 19:43:25 +0100
Von:lig...@statistik.tu-dortmund.de
Antwort an: cran-submissi...@r-project.org
An: tobias.we...@uni-hohenheim.de
Kopie (CC): cran-submissi...@r-project.org



Dear maintainer,
package spsh_1.0.190311.tar.gz does not pass the incoming checks 
automatically, please see the following pre-tests:
Windows: 


Status: 1 ERROR, 2 WARNINGs, 1 NOTE
Debian: 


Status: 1 ERROR, 2 WARNINGs, 1 NOTE

Please fix all problems and resubmit a fixed version via the webform.
If you are not sure how to fix the problems shown, please ask for help 
on the R-package-devel mailing list:


If you are fairly certain the rejection is a false positive, please 
reply-all to this message and explain.

More details are given in the directory:

The files will be removed after roughly 7 days.
No strong reverse dependencies to be checked.
Best regards,
CRAN teams' auto-check service

Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-ix86+x86_64
Check: CRAN incoming feasibility, Result: WARNING
  Maintainer: ''
  
  The maintainer field lacks a name
  
  New submission
  
  Version contains large components (1.0.190311)
  
  Possibly mis-spelled words in DESCRIPTION:
pedo (10:93)
  
  The Title field should be in title case. Current version is:
  'Estimation and prediction of parameters of various soil hydraulic property 
models'
  In title case that is:
  'Estimation and Prediction of Parameters of Various Soil Hydraulic Property 
Models'

Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-ix86+x86_64
Check: R code for possible problems, Result: NOTE
  transBoundFun: no visible binding for global variable '.'
  weightFun: no visible binding for global variable 'parL'
  Undefined global functions or variables:
. parL

Flavor: r-devel-linux-x86_64-debian-gcc, r-devel-windows-ix86+x86_64
Check: PDF version of manual, Result: WARNING
  LaTeX errors when creating PDF version.
  This typically indicates Rd problems.
  LaTeX errors found:
  ! LaTeX Error: There's no line here to end.
  
  See the LaTeX manual or LaTeX Companion for explanation.
  Type  H   for immediate help.
   ...  
  ! Paragraph ended before \Rd@code was complete.

Re: [R-pkg-devel] Help request on Rd2pdf | Fwd: [CRAN-pretest-archived] CRAN submission spsh 1.0.190311

2019-03-13 Thread Georgi Boshnakov

Hi,

> Turning to the R-Terminal executing /R CMD Rd2pdf/ Leads to:
> 
> Converting Rd files to LaTeX ...
> 
>   spsh_1.0.1.tar.gz
>
> Warning in readLines(f) : line 1 appears to contain an embedded nul

You really need to give the exact command you run, it is not just 'R CMD 
Rd2pdf'.
The error message indicates that probably you run  'R CMD Rd2pdf 
spsh_1.0.1.tar.gz ',
which is incorrect - you need to run Rd2pdf on the directory were your source 
package is, not on the tar ball,  eg. 'R CMD Rd2pdf spsh '.

The LaTeX error indicates that you probably used something like \code{some 
code} but omitted the closing curly parenthesis. 

Georgi Boshnakov


-Original Message-
From: R-package-devel [mailto:r-package-devel-boun...@r-project.org] On Behalf 
Of Tobias KD Weber
Sent: 13 March 2019 09:50
To: r-package-devel@r-project.org
Subject: [R-pkg-devel] Help request on Rd2pdf | Fwd: [CRAN-pretest-archived] 
CRAN submission spsh 1.0.190311

Dear people,

I submitted a package to CRAN and got an error on the pdf manual creation 
(solved other minor issues, full response from cran-submissi...@r-project.org 
please see email below).

The response to an error and warnings detailed:

* using log directory 'd:/RCompile/CRANincoming/R-devel/spsh.Rcheck'

* using R Under development (unstable) (2019-03-09 r76216) * using
platform: x86_64-w64-mingw32 (64-bit) * using session charset: ISO8859-1
* checking for file 'spsh/DESCRIPTION' ... OK * checking extension type ... 
Package * this is package 'spsh' version '1.0.190311' * package
encoding: UTF-8 * checking CRAN incoming feasibility ... WARNING [... 
deleted  all OK ...] * checking PDF version of manual ... WARNING LaTeX 
errors when creating PDF version. This typically indicates Rd problems. LaTeX 
errors found: ! LaTeX Error: There's no line here to end. See the LaTeX manual 
or LaTeX Companion for explanation. Type H  for immediate help. ... ! 
Paragraph ended before \Rd@code was complete.  \par l.1340 * 
checking PDF version of manual without hyperrefs or index ... ERROR * DONE 
Status: 1 ERROR, 2 WARNINGs, 1 NOTE


Turning to the R-Terminal executing /R CMD Rd2pdf/ Leads to:

Converting Rd files to LaTeX ...

   spsh_1.0.1.tar.gz

Warning in readLines(f) : line 1 appears to contain an embedded nul

Warning in readLines(f) : line 19 appears to contain an embedded nul

[... deleted many more lines ... ]

Warning in readLines(f) : line 3058 appears to contain an embedded nul

Warning in readLines(f) : line 3117 appears to contain an embedded nul

Warning in readLines(f) :

   incomplete final line found on 'spsh_1.0.1.tar.gz'

Error in iconv(lines, encoding, "UTF-8", sub = "byte") :

   embedded nul in string: 
'\001\f\023aIeK\021\030\023U\\,%\035\002\003\n\v\\}s\021heyt\036m\037
PaK\032\027Z,C %2u@\031w\021('\017}gcn\004L\006\0267#!|E\017\

177\\1w\032|Gf\005JS*a\177F\\\aa_Yr]\033sVA~~\\,\026Sa_QnXMF\017B?O,<\003~\toMZ\023i\006\177\0\006\005qKvB_~\t\a\a5l\001\177=MWu\030]\t>JF\nDx\004T\t\023

`[\025?n)g^\004oMhW{%l\aO\fo>\033>\016{_n?]d|\v>V'


I have truely searched most of the morning for a solution, but none to be found.
Any ideas how to solve this would be very much appreciated.

Kind Regards,
Tobias



 Weitergeleitete Nachricht 
Betreff:[CRAN-pretest-archived] CRAN submission spsh 1.0.190311
Datum:  Tue, 12 Mar 2019 19:43:25 +0100
Von:lig...@statistik.tu-dortmund.de
Antwort an: cran-submissi...@r-project.org
An: tobias.we...@uni-hohenheim.de
Kopie (CC): cran-submissi...@r-project.org



Dear maintainer,
package spsh_1.0.190311.tar.gz does not pass the incoming checks automatically, 
please see the following pre-tests:
Windows: 

Status: 1 ERROR, 2 WARNINGs, 1 NOTE
Debian: 

Status: 1 ERROR, 2 WARNINGs, 1 NOTE

Please fix all problems and resubmit a fixed version via the webform.
If you are not sure how to fix the problems shown, please ask for help on the 
R-package-devel mailing list:

If you are fairly certain the rejection is a false positive, please reply-all 
to this message and explain.
More details are given in the directory:

The files will be removed after roughly 7 days.
No strong reverse dependencies to be checked.
Best regards,
CRAN teams' auto-check service

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

[R-pkg-devel] How to debug CRAN errors?

2019-03-13 Thread David Hugh-Jones

Hi all,

My package has errors on CRAN's Linux and Solaris:

https://cran.r-project.org/web/checks/check_results_huxtable.html

which I can't reproduce on my local OSX Machine, nor on Linux on Travis.

Does anyone have any general hints on how to reproduce and/or debug such
errors?

Specifically the error relates to a call to openxlsx::saveWorkbook
producing a message. openxlsx hasn't changed recently, though.

Cheers,
David

[[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] How to debug CRAN errors?

2019-03-13 Thread William Dunlap

The complaint

> test_check("huxtable")
 -- 1. Failure: Data written in appropriate format
(@test-openxlsx.R#101) --
 `openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx", overwrite =
TRUE)` produced messages.

comes from your call to testthat::expect_silent()

test_that("Data written in appropriate format", {
  hx <- huxtable(a = 1:2 + 0.5, b = -1:-2 + 0.5, d = letters[1:2],
add_colnames = TRUE)
  wb <- as_Workbook(hx)
  expect_silent(openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx",
overwrite = TRUE))


Perhaps you should suggest to the authors of testthat that it would be nice
if expect_silent() showed some of the text of the messages, etc., instead
of just saying that messages were produced.

By the way, I think your test test should write to a file in [a
subdirectory of]] tempdir(), not to a file in the current directory.

comes from
Bill Dunlap
TIBCO Software
wdunlap tibco.com


On Wed, Mar 13, 2019 at 8:50 AM David Hugh-Jones 
wrote:
>
> Hi all,
>
> My package has errors on CRAN's Linux and Solaris:
>
> https://cran.r-project.org/web/checks/check_results_huxtable.html
>
> which I can't reproduce on my local OSX Machine, nor on Linux on Travis.
>
> Does anyone have any general hints on how to reproduce and/or debug such
> errors?
>
> Specifically the error relates to a call to openxlsx::saveWorkbook
> producing a message. openxlsx hasn't changed recently, though.
>
> Cheers,
> David
>
> [[alternative HTML version deleted]]
>
> __
> 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] How to debug CRAN errors?

2019-03-13 Thread David Hugh-Jones

Hi Bill,

I take your point. Meanwhile, though, is there any way to debug the
problem? I’ll assume that making repeated uploads to CRAN is not a viable
approach it would be great if there were a Docker image of their setup
available, for example.

On Wed, 13 Mar 2019 at 17:00, William Dunlap  wrote:

> The complaint
>
> > test_check("huxtable")
>  -- 1. Failure: Data written in appropriate format
> (@test-openxlsx.R#101) --
>  `openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx", overwrite =
> TRUE)` produced messages.
>
> comes from your call to testthat::expect_silent()
>
> test_that("Data written in appropriate format", {
>   hx <- huxtable(a = 1:2 + 0.5, b = -1:-2 + 0.5, d = letters[1:2],
> add_colnames = TRUE)
>   wb <- as_Workbook(hx)
>   expect_silent(openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx",
> overwrite = TRUE))
>
>
> Perhaps you should suggest to the authors of testthat that it would be
> nice if expect_silent() showed some of the text of the messages, etc.,
> instead of just saying that messages were produced.
>
> By the way, I think your test test should write to a file in [a
> subdirectory of]] tempdir(), not to a file in the current directory.
>
> comes from
> Bill Dunlap
> TIBCO Software
> wdunlap tibco.com
>
>
>
> On Wed, Mar 13, 2019 at 8:50 AM David Hugh-Jones 
> wrote:
> >
> > Hi all,
> >
> > My package has errors on CRAN's Linux and Solaris:
> >
> > https://cran.r-project.org/web/checks/check_results_huxtable.html
> >
> > which I can't reproduce on my local OSX Machine, nor on Linux on Travis.
> >
> > Does anyone have any general hints on how to reproduce and/or debug such
> > errors?
> >
> > Specifically the error relates to a call to openxlsx::saveWorkbook
> > producing a message. openxlsx hasn't changed recently, though.
> >
> > Cheers,
> > David
> >
> > [[alternative HTML version deleted]]
> >
> > __
> > 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] How to debug CRAN errors?

2019-03-13 Thread William Dunlap

You can stick your own version of expect_silent into the test file.  Have
it print
the messages, output, and warnings that it finds.

Bill Dunlap
TIBCO Software
wdunlap tibco.com


On Wed, Mar 13, 2019 at 10:13 AM David Hugh-Jones 
wrote:

> Hi Bill,
>
> I take your point. Meanwhile, though, is there any way to debug the
> problem? I’ll assume that making repeated uploads to CRAN is not a viable
> approach it would be great if there were a Docker image of their setup
> available, for example.
>
> On Wed, 13 Mar 2019 at 17:00, William Dunlap  wrote:
>
>> The complaint
>>
>> > test_check("huxtable")
>>  -- 1. Failure: Data written in appropriate format
>> (@test-openxlsx.R#101) --
>>  `openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx", overwrite =
>> TRUE)` produced messages.
>>
>> comes from your call to testthat::expect_silent()
>>
>> test_that("Data written in appropriate format", {
>>   hx <- huxtable(a = 1:2 + 0.5, b = -1:-2 + 0.5, d = letters[1:2],
>> add_colnames = TRUE)
>>   wb <- as_Workbook(hx)
>>   expect_silent(openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx",
>> overwrite = TRUE))
>>
>>
>> Perhaps you should suggest to the authors of testthat that it would be
>> nice if expect_silent() showed some of the text of the messages, etc.,
>> instead of just saying that messages were produced.
>>
>> By the way, I think your test test should write to a file in [a
>> subdirectory of]] tempdir(), not to a file in the current directory.
>>
>> comes from
>> Bill Dunlap
>> TIBCO Software
>> wdunlap tibco.com
>>
>>
>>
>> On Wed, Mar 13, 2019 at 8:50 AM David Hugh-Jones <
>> davidhughjo...@gmail.com> wrote:
>> >
>> > Hi all,
>> >
>> > My package has errors on CRAN's Linux and Solaris:
>> >
>> > https://cran.r-project.org/web/checks/check_results_huxtable.html
>> >
>> > which I can't reproduce on my local OSX Machine, nor on Linux on Travis.
>> >
>> > Does anyone have any general hints on how to reproduce and/or debug such
>> > errors?
>> >
>> > Specifically the error relates to a call to openxlsx::saveWorkbook
>> > producing a message. openxlsx hasn't changed recently, though.
>> >
>> > Cheers,
>> > David
>> >
>> > [[alternative HTML version deleted]]
>> >
>> > __
>> > 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] How to debug CRAN errors?

2019-03-13 Thread Klaus Schliep

On Wed, Mar 13, 2019, 1:13 PM David Hugh-Jones 
wrote:

> Hi Bill,
>
> I take your point. Meanwhile, though, is there any way to debug the
> problem? I’ll assume that making repeated uploads to CRAN is not a viable
> approach it would be great if there were a Docker image of their setup
> available, for example.
>


Have you tested your package on https://builder.r-hub.io/ or
https://win-builder.r-project.org/ ?

>
> On Wed, 13 Mar 2019 at 17:00, William Dunlap  wrote:
>
> > The complaint
> >
> > > test_check("huxtable")
> >  -- 1. Failure: Data written in appropriate format
> > (@test-openxlsx.R#101) --
> >  `openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx", overwrite =
> > TRUE)` produced messages.
> >
> > comes from your call to testthat::expect_silent()
> >
> > test_that("Data written in appropriate format", {
> >   hx <- huxtable(a = 1:2 + 0.5, b = -1:-2 + 0.5, d = letters[1:2],
> > add_colnames = TRUE)
> >   wb <- as_Workbook(hx)
> >   expect_silent(openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx",
> > overwrite = TRUE))
> >
> >
> > Perhaps you should suggest to the authors of testthat that it would be
> > nice if expect_silent() showed some of the text of the messages, etc.,
> > instead of just saying that messages were produced.
> >
> > By the way, I think your test test should write to a file in [a
> > subdirectory of]] tempdir(), not to a file in the current directory.
> >
> > comes from
> > Bill Dunlap
> > TIBCO Software
> > wdunlap tibco.com
> >
> >
> >
> > On Wed, Mar 13, 2019 at 8:50 AM David Hugh-Jones <
> davidhughjo...@gmail.com>
> > wrote:
> > >
> > > Hi all,
> > >
> > > My package has errors on CRAN's Linux and Solaris:
> > >
> > > https://cran.r-project.org/web/checks/check_results_huxtable.html
> > >
> > > which I can't reproduce on my local OSX Machine, nor on Linux on
> Travis.
> > >
> > > Does anyone have any general hints on how to reproduce and/or debug
> such
> > > errors?
> > >
> > > Specifically the error relates to a call to openxlsx::saveWorkbook
> > > producing a message. openxlsx hasn't changed recently, though.
> > >
> > > Cheers,
> > > David
> > >
> > > [[alternative HTML version deleted]]
> > >
> > > __
> > > 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
>

[[alternative HTML version deleted]]

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

[R-pkg-devel] CRAN incoming checks fail due to non-staged installation

2019-03-13 Thread David Kepplinger

Dear Community,

I am trying to update the pense package on CRAN to fix `autoreconf`
problems, but the incoming checks fail for Windows (r-devel) with 2 NOTEs.

The first NOTE is a HTTP 403 for a http://doi.org URL which I already know
about and can not change, but the other NOTE is more obscure to me. It says

* checking whether package 'pense' can be installed ... NOTE
Found the following notes/warnings:
  Non-staged installation was used


and when I check the install log, it says

install for i386
* installing *source* package 'pense' ...
** using staged installation
[]
install for x64
* installing *source* package 'pense' ...
** using non-staged installation
[...]


Is this a false positive or is there something I can do to force using a
staged installation for both architectures on Windows?

Best,
David

[[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] How to debug CRAN errors?

2019-03-13 Thread Duncan Murdoch


On 13/03/2019 12:59 p.m., William Dunlap wrote:

The complaint


test_check("huxtable")

  -- 1. Failure: Data written in appropriate format
(@test-openxlsx.R#101) --
  `openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx", overwrite =
TRUE)` produced messages.

comes from your call to testthat::expect_silent()

test_that("Data written in appropriate format", {
   hx <- huxtable(a = 1:2 + 0.5, b = -1:-2 + 0.5, d = letters[1:2],
add_colnames = TRUE)
   wb <- as_Workbook(hx)
   expect_silent(openxlsx::saveWorkbook(wb, file = "test-xlsx.xlsx",
overwrite = TRUE))


Perhaps you should suggest to the authors of testthat that it would be nice
if expect_silent() showed some of the text of the messages, etc., instead
of just saying that messages were produced.


Yes.


By the way, I think your test test should write to a file in [a
subdirectory of]] tempdir(), not to a file in the current directory.


That could be the source of the error:  it's a violation of CRAN policy 
to write to the current directory.  An obvious way to test this would be 
to make it unwriteable.


Duncan Murdoch



comes from
Bill Dunlap
TIBCO Software
wdunlap tibco.com


On Wed, Mar 13, 2019 at 8:50 AM David Hugh-Jones 
wrote:


Hi all,

My package has errors on CRAN's Linux and Solaris:

https://cran.r-project.org/web/checks/check_results_huxtable.html

which I can't reproduce on my local OSX Machine, nor on Linux on Travis.

Does anyone have any general hints on how to reproduce and/or debug such
errors?

Specifically the error relates to a call to openxlsx::saveWorkbook
producing a message. openxlsx hasn't changed recently, though.

Cheers,
David

 [[alternative HTML version deleted]]

__
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



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

Re: [R-pkg-devel] CRAN incoming checks fail due to non-staged installation

2019-03-13 Thread Maxime Turgeon

Hi David,

Non-staged installation is something new in R-devel: 
https://developer.r-project.org/Blog/public/2019/02/14/staged-install/index.html

Package maintainers can opt out of it (through DESCRIPTION), and I'm assuming 
CRAN wants a quick way to know if that was the case when diagnosing a 
submission.

To resolutely opt *in* (which will eventually be the default), you could try 
adding "StagedInstall: yes" to your DESCRIPTION file.

Of course, one question still remains: why was the behaviour different for the 
two architectures.

Max

From: R-package-devel  on behalf of 
David Kepplinger 
Sent: March 13, 2019 3:39 PM
To: r-package-devel@r-project.org
Subject: [R-pkg-devel] CRAN incoming checks fail due to non-staged installation

Dear Community,

I am trying to update the pense package on CRAN to fix `autoreconf`
problems, but the incoming checks fail for Windows (r-devel) with 2 NOTEs.

The first NOTE is a HTTP 403 for a http://doi.org URL which I already know
about and can not change, but the other NOTE is more obscure to me. It says

* checking whether package 'pense' can be installed ... NOTE
Found the following notes/warnings:
  Non-staged installation was used


and when I check the install log, it says

install for i386
* installing *source* package 'pense' ...
** using staged installation
[]
install for x64
* installing *source* package 'pense' ...
** using non-staged installation
[...]


Is this a false positive or is there something I can do to force using a
staged installation for both architectures on Windows?

Best,
David

[[alternative HTML version deleted]]

__
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

[R-pkg-devel] staged install fails on Linux VM?

2019-03-13 Thread Ben Bolker

  When I try to "R CMD check" a local copy of the lme4 package with
recent R-devel it consistently fails as follows *unless* I  first
"export R_INSTALL_STAGED=0".

** checking absolute paths in shared objects and dynamic libraries
mv: cannot move
'/media/sf_Documents/Rpkgs/lme4git/lme4.Rcheck/00LOCK-lme4/00new/lme4'
to '/media/sf_Documents/Rpkgs/lme4git/lme4.Rcheck/lme4': File exists
** testing if installed package can be loaded from final location
Warning in library(pkg_name, lib.loc = lib, character.only = TRUE,
logical.return = TRUE) :
  there is no package called ‘lme4’

  This may be a consequence of my weird setup (Linux VM with shared
folders imported from on a 'real' MacOS HFS file system) [race
condition?], and I can use the workaround above, but I'm but I'm curious
if anyone else has encountered this (and if it indicates some problem
that's likely to bite me again in the future).

  cheers
Ben Bolker

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

Re: [R-pkg-devel] CRAN incoming checks fail due to non-staged installation

2019-03-13 Thread David Kepplinger

Thank you, Max, for the clarification.
I have added the option "StagedInstall: yes" to the DESCRIPTION file, but
it doesn't seem to be forcing a staged installation for x64 on Windows. I
get the same NOTE now from winbuilder, but with more explanation which
could help isolate the problem:

install for i386
* installing *source* package 'pense' ...
** using staged installation
[...]
install for x64
* installing *source* package 'pense' ...
not using staged install with --libs-only
** using non-staged installation
[...]


Best,
David

On Wed, Mar 13, 2019 at 1:21 PM Maxime Turgeon <
maxime.turg...@mail.mcgill.ca> wrote:

> Hi David,
>
> Non-staged installation is something new in R-devel:
> https://developer.r-project.org/Blog/public/2019/02/14/staged-install/index.html
>
>
> Package maintainers can opt out of it (through DESCRIPTION), and I'm
> assuming CRAN wants a quick way to know if that was the case when
> diagnosing a submission.
>
> To resolutely opt *in* (which will eventually be the default), you could
> try adding "StagedInstall: yes" to your DESCRIPTION file.
>
> Of course, one question still remains: why was the behaviour different for
> the two architectures.
>
> Max
> --
> *From:* R-package-devel  on behalf
> of David Kepplinger 
> *Sent:* March 13, 2019 3:39 PM
> *To:* r-package-devel@r-project.org
> *Subject:* [R-pkg-devel] CRAN incoming checks fail due to non-staged
> installation
>
> Dear Community,
>
> I am trying to update the pense package on CRAN to fix `autoreconf`
> problems, but the incoming checks fail for Windows (r-devel) with 2 NOTEs.
>
> The first NOTE is a HTTP 403 for a http://doi.org URL which I already know
> about and can not change, but the other NOTE is more obscure to me. It says
>
> * checking whether package 'pense' can be installed ... NOTE
> Found the following notes/warnings:
>   Non-staged installation was used
>
>
> and when I check the install log, it says
>
> install for i386
> * installing *source* package 'pense' ...
> ** using staged installation
> []
> install for x64
> * installing *source* package 'pense' ...
> ** using non-staged installation
> [...]
>
>
> Is this a false positive or is there something I can do to force using a
> staged installation for both architectures on Windows?
>
> Best,
> David
>
> [[alternative HTML version deleted]]
>
> __
> 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] How to debug CRAN errors?

2019-03-13 Thread David Hugh-Jones

Hi guys

That might be it. But there was no error until the latest release - whereas
that test has been there for 9 months. The file is written within
testthat... is there a new check for this in CRAN?

Meanwhile, I am still figuring out how to debug this problem. I uploaded to
r-hub... does anyone know how I can access the artifacts created after the
build? The URL build was

https://builder.r-hub.io/status/huxtable_4.4.0.tar.gz-b91485ad24b7a2f9c73bad2d51ebdb9d

David


>
> > By the way, I think your test test should write to a file in [a
> > subdirectory of]] tempdir(), not to a file in the current directory.
>
> That could be the source of the error:  it's a violation of CRAN policy
> to write to the current directory.  An obvious way to test this would be
> to make it unwriteable.
>
> Duncan Murdoch
>
> >
> > comes from
> > Bill Dunlap
> > TIBCO Software
> > wdunlap tibco.com
> >
> >
> > On Wed, Mar 13, 2019 at 8:50 AM David Hugh-Jones <
> davidhughjo...@gmail.com>
> > wrote:
> >>
> >> Hi all,
> >>
> >> My package has errors on CRAN's Linux and Solaris:
> >>
> >> https://cran.r-project.org/web/checks/check_results_huxtable.html
> >>
> >> which I can't reproduce on my local OSX Machine, nor on Linux on Travis.
> >>
> >> Does anyone have any general hints on how to reproduce and/or debug such
> >> errors?
> >>
> >> Specifically the error relates to a call to openxlsx::saveWorkbook
> >> producing a message. openxlsx hasn't changed recently, though.
> >>
> >> Cheers,
> >> David
> >>
> >>  [[alternative HTML version deleted]]
> >>
> >> __
> >> 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
> >
>
>

[[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] How to debug CRAN errors?

2019-03-13 Thread Duncan Murdoch

On 13/03/2019 8:34 p.m., David Hugh-Jones wrote:

Hi guys

That might be it. But there was no error until the latest release - 
whereas that test has been there for 9 months. The file is written 
within testthat... is there a new check for this in CRAN?

Meanwhile, I am still figuring out how to debug this problem. I uploaded 
to r-hub... does anyone know how I can access the artifacts created 
after the build? The URL build was

https://builder.r-hub.io/status/huxtable_4.4.0.tar.gz-b91485ad24b7a2f9c73bad2d51ebdb9d

You should have got an email giving the link.  In the ones I've seen, 
you replace the prefix

https://builder.r-hub.io/status/

with

https://artifacts.r-hub.io/

and you'll see them.  It works for yours.

Duncan Murdoch

David

 > By the way, I think your test test should write to a file in [a
 > subdirectory of]] tempdir(), not to a file in the current directory.

That could be the source of the error:  it's a violation of CRAN policy
to write to the current directory.  An obvious way to test this
would be
to make it unwriteable.

Duncan Murdoch

 >
 > comes from
 > Bill Dunlap
 > TIBCO Software
 > wdunlap tibco.com 
 >
 >
 > On Wed, Mar 13, 2019 at 8:50 AM David Hugh-Jones
mailto:davidhughjo...@gmail.com>>
 > wrote:
 >>
 >> Hi all,
 >>
 >> My package has errors on CRAN's Linux and Solaris:
 >>
 >> https://cran.r-project.org/web/checks/check_results_huxtable.html
 >>
 >> which I can't reproduce on my local OSX Machine, nor on Linux on
Travis.
 >>
 >> Does anyone have any general hints on how to reproduce and/or
debug such
 >> errors?
 >>
 >> Specifically the error relates to a call to openxlsx::saveWorkbook
 >> producing a message. openxlsx hasn't changed recently, though.
 >>
 >> Cheers,
 >> David
 >>
 >>          [[alternative HTML version deleted]]
 >>
 >> __
 >> 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
 >

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

Re: [R-pkg-devel] CRAN review

Re: [R-pkg-devel] CRAN review

Re: [R-pkg-devel] CRAN review

[R-pkg-devel] Help request on Rd2pdf | Fwd: [CRAN-pretest-archived] CRAN submission spsh 1.0.190311

Re: [R-pkg-devel] Help request on Rd2pdf | Fwd: [CRAN-pretest-archived] CRAN submission spsh 1.0.190311

[R-pkg-devel] How to debug CRAN errors?

Re: [R-pkg-devel] How to debug CRAN errors?

Re: [R-pkg-devel] How to debug CRAN errors?

Re: [R-pkg-devel] How to debug CRAN errors?

Re: [R-pkg-devel] How to debug CRAN errors?

[R-pkg-devel] CRAN incoming checks fail due to non-staged installation

Re: [R-pkg-devel] How to debug CRAN errors?

Re: [R-pkg-devel] CRAN incoming checks fail due to non-staged installation

[R-pkg-devel] staged install fails on Linux VM?

Re: [R-pkg-devel] CRAN incoming checks fail due to non-staged installation

Re: [R-pkg-devel] How to debug CRAN errors?

Re: [R-pkg-devel] How to debug CRAN errors?

17 matches

Site Navigation

Mail list logo

Footer information