Prepared new release

CRAN-RELEASE

@@ -0,0 +1,2 @@
+This package was submitted to CRAN on 2020-10-17.
+Once it is accepted, delete this file and tag the release (commit 4183eb2).

DESCRIPTION

@@ -1,7 +1,7 @@
 Package: LexisNexisTools
 Title: Working with Files from 'LexisNexis'
-Version: 0.3.1.9000
-Date: 2020-10-12
+Version: 0.3.2
+Date: 2020-10-17
 Authors@R: person("Johannes", "Gruber", email = "[email protected]", 
   role = c("aut", "cre"))
 Description: My PhD supervisor once told me that everyone doing newspaper

NEWS.md

@@ -1,3 +1,7 @@
+# LexisNexisTools 0.3.2
+
+* Fixed tests that caused problems on CRAN
+
 # LexisNexisTools 0.3.1
 
 * Added support for last remaining new format (zip).

README.md

@@ -155,8 +155,7 @@ be in most cases:
     well. In these cases, you should remove the whole article after
     inspecting it. (Use
     `View(LNToutput@articles$Article[LNToutput@meta$Graphic])` to view
-    these articles in a spreadsheet like
-viewer.)
+    these articles in a spreadsheet like viewer.)
 
 <p align="center">
 
@@ -292,8 +291,7 @@ duplicates_df <- lnt_similarity(texts = LNToutput@articles$Article,
     ##  ...processing date 2010-01-11: 5 duplicates found [3.05 secs].      
     ## Threshold = 0.97; 4 days processed; 5 duplicates found; in 3.05 secs
 
-Now you can inspect the results using the function
-`lnt_diff()`:
+Now you can inspect the results using the function `lnt_diff()`:
 
 ``` r
 lnt_diff(duplicates_df, min = 0, max = Inf)
@@ -406,8 +404,7 @@ with ID 9, all other values are `NULL`, which means the keyword wasn’t
 found. If your focus shifts and you want to subset your data to only
 include articles which mention this keyword, you could append this
 information to the meta information in the LNToutput object and then
-subset it to articles where the list entry is different from
-`NULL`.
+subset it to articles where the list entry is different from `NULL`.
 
 ``` r
 LNToutput@meta$stats <- lnt_lookup(LNToutput, pattern = "statistical computing")

Update package.R

@@ -73,7 +73,7 @@ devtools::check_win_oldrelease()
 devtools::check_win_release()
 
 ## check r_hub
-rhub::check_for_cran()
+rhub::check_for_cran(env_vars = c(R_COMPILE_AND_INSTALL_PACKAGES = "always"))
 
 ## release
 revdepcheck::revdep_check()

cran-comments.md

@@ -2,13 +2,21 @@
 This submission is necessary as some tests fail due to the recent update of dplyr.
 
 ## Test environments
-* local Kubuntu 18.04, R version 4.0.0
-* local Windows 10, R version 4.0.0
+* local Kubuntu 18.04, R version 4.0.3
+* local Windows 10, R version 4.0.3
 * win-builder.r-project.org, R-release, R-oldrelease, R-devel
 * Ubuntu Xenial 16.04 (on travis-ci), R: release, R: oldrel, R: devel
+* rhub::check_for_cran(env_vars = c(R_COMPILE_AND_INSTALL_PACKAGES = "always"))
 
 ## R CMD check results
-0 ERRORs | 0 WARNINGs | 0 NOTEs
+0 ERRORs | 0 WARNINGs | 1 NOTEs
+
+Only on rhub: 
+"Examples with CPU (user + system) or elapsed time > 5s
+lnt_diff 6.28    0.8    7.14
+         user system elapsed"
+
+Other test environments do not note this.
 
 ## Reverse dependency and other package conflicts
 

inst/CITATION

@@ -3,5 +3,5 @@ bibentry(bibtype = "Manual",
          author = as.person("Johannes Gruber"),
          year = format(Sys.Date(), "%Y"),
          url = "https://github.com/JBGruber/LexisNexisTools",
-         note = "R package version 0.3.1"
+         note = "R package version 0.3.2"
 )

vignettes/demo.Rmd

@@ -108,7 +108,7 @@ In these cases, you should remove the whole article after inspecting it.
 (Use `View(LNToutput@articles$Article[LNToutput@meta$Graphic])` to view these articles in a spreadsheet like viewer.)
 
 <p align="center">
-   <a href="https://ibb.co/fj5YjG"><img src="https://preview.ibb.co/fOfNdb/LN.png" alt="LN" border="1"></a>
+   <a href="https://imgbb.com/MZXXd7z"><img src="https://preview.ibb.co/fOfNdb/LN.png" alt="LN" border="1"></a>
 </p>
 
 To use the function, you can again provide either file name(s), folder name(s) or nothing---to search the current working directory for relevant files---as `x` argument: