* using log directory 'd:/RCompile/CRANincoming/R-devel/gamlss.Rcheck'
* using R Under development (unstable) (2024-03-16 r86144 ucrt)
* using platform: x86_64-w64-mingw32
* R was compiled by
    gcc.exe (GCC) 13.2.0
    GNU Fortran (GCC) 13.2.0
* running under: Windows Server 2022 x64 (build 20348)
* using session charset: UTF-8
* checking for file 'gamlss/DESCRIPTION' ... OK
* this is package 'gamlss' version '5.4-22'
* checking CRAN incoming feasibility ... [11s] NOTE
Maintainer: 'Mikis Stasinopoulos <d.stasinopoulos@gre.ac.uk>'

Found the following (possibly) invalid URLs:
  URL: https://gamlss.com/ (moved to https://www.gamlss.com/)
    From: NEWS.md
    Status: 301
    Message: Moved Permanently
  URL: https://github.com/mstasinopoulos/GAMLSS-original/ (moved to https://github.com/gamlss-dev/gamlss)
    From: NEWS.md
    Status: 301
    Message: Moved Permanently
  For content that is 'Moved Permanently', please change http to https,
  add trailing slashes, or replace the old by the new URL.
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking serialization versions ... OK
* checking whether package 'gamlss' can be installed ... OK
* used C compiler: 'gcc.exe (GCC) 13.2.0'
* checking installed package size ... OK
* checking package directory ... OK
* checking for future file timestamps ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking code files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking whether startup messages can be suppressed ... OK
* checking use of S3 registration ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... [43s] OK
* checking Rd files ... NOTE
checkRd: (-1) VC.test.Rd:25: Lost braces
    25 | In the Clarke test, if the two models are statistically equivalent then the log-likelihood ratios of the observations should be evenly distributed around zero and around half of the ratios should be larger than zero. The test follows asymptotically a binomial distribution with parameters n and 0.5. Critical values can be obtained as shown in Clarke (2007). Intuitively, the model in \code{obj1} is preferred over that in \code{obj2} if the value of the test is significantly larger than its expected value under the null hypothesis ('code{n/2}), and vice versa. If the value is not significantly different from \code{n/2} then \code{obj1} can be thought of as equivalent to \code{obj2}.
       |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             ^
checkRd: (-1) fitDist.Rd:65: Lost braces in \itemize; meant \describe ?
checkRd: (-1) fitDist.Rd:67: Lost braces in \itemize; meant \describe ?
checkRd: (-1) fitDist.Rd:69: Lost braces in \itemize; meant \describe ?
checkRd: (-1) fitDist.Rd:71: Lost braces in \itemize; meant \describe ?
checkRd: (-1) fitDist.Rd:73-74: Lost braces in \itemize; meant \describe ?
checkRd: (-1) fitDist.Rd:76: Lost braces in \itemize; meant \describe ?
checkRd: (-1) histSmo.Rd:54: Lost braces
    54 | iv) The function \code{histSmo()} combines all the above functions in the sense that if lambda is fixed it uses  \code{histSmoO()}, if the df's are fixed it uses code{histSmoC()} and if none of these is specified it uses \code{histSmoP()}.
       |                                                                                                                                                                       ^
checkRd: (-1) lms.Rd:32: Lost braces
    32 |   \item{step}{if code{prof=TRUE} is used this determine the step for the profile GAIC }
       |                      ^
checkRd: (-1) ri.Rd:32: Lost braces
    32 | The type of penalty required, \code{Lp=2} a proper ridge regression is the default. Use code{Lp=1} for lasso and different values for different penalties.  
       |                                                                                             ^
* checking Rd metadata ... OK
* checking Rd line widths ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking pragmas in C/C++ headers and code ... OK
* checking compilation flags used ... OK
* checking compiled code ... OK
* checking examples ... [36s] OK
* checking PDF version of manual ... [17s] OK
* checking HTML version of manual ... [15s] OK
* DONE
Status: 2 NOTEs