Dear Zahra Heidari Ghahfarrokhi,
Welcome to R-package-devel!
В Tue, 28 Jan 2025 18:17:06 +0330
zahra heidari gh пишет:
>- Additional details:
> - The package FD is used during package building.
> - In a previous post on the r-h...@r-project.org mailing list,
> I was advised that
Excellent (as usual) sleuthing by Ivan -- colour me impressed (again).
As an aside, your package makes wide use of the excellent resources provided
by other CRAN packages. But with this comes added complexity. Depending on
over sixty (!!) other packages (when counting recursively, over seventy
Without seeing your package, I don't think anyone could help you, other
than very generic help: "Find what is creating that file, and figure
out how to stop it."
If you submit your package to one of the online check services (e.g.
https://win-builder.r-project.org/) then you could post a link
В Tue, 28 Jan 2025 16:07:38 +0100
Guillermo Vinue пишет:
> Thank you for your help, Ben and Ivan. Unfortunately, the note
> persists:
> https://win-builder.r-project.org/incoming_pretest/fawir_1.0_20250128_113725/Debian/00check.log
> The public source repository from my package is here:
> https:
Thank you for actually posting a reference to your package and its source
code. That allows us to take a closer look.
On 28 January 2025 at 16:07, Guillermo Vinue wrote:
| Thank you for your help, Ben and Ivan. Unfortunately, the note persists:
|
https://win-builder.r-project.org/incoming_prete
Dear R Package Development Team,
I am writing to report an issue I encountered during the R CMD check
process for my R package, RHC. A non-standard file named 'vert.txt' is
being generated in the check directory, resulting in a NOTE in the check
results. Despite adding 'vert.txt' to the .Rbuildign
Dear Ivan,
Thank you for your response.
I will wait for one or two days to see if the problem resolves itself. If it
persists, I will reach out to Dr. Uwe Ligges for further advice.
Best regards,
Gabriel
From: Ivan Krylov
Sent: 28 January 2025 11:47
To: Gabriel Co
Thank you for your help, Ben and Ivan. Unfortunately, the note persists:
https://win-builder.r-project.org/incoming_pretest/fawir_1.0_20250128_113725/Debian/00check.log
The public source repository from my package is here:
https://github.com/guivivi/fawir
The function that seems to cause the probl
В Tue, 28 Jan 2025 10:01:00 +
Gabriel Constantino Blain пишет:
> When I run check_win_devel() on my package, I encounter the following
> error:
>
> -
> Error: objects 'Surv', 'is.Surv' are not exported by
> 'namespace:survival' Execution halted
Since Surv and is.Surv
В Tue, 28 Jan 2025 14:25:23 +0100
John Clarke пишет:
> I'm wondering if there is a way to point an R package installer to a
> pre-compiled release on Github rather than rely on CRAN.
>From the point of view of install.packages(), a repository is a
collection of package files plus an index file a
On 28 January 2025 at 14:27, Iñaki Ucar wrote:
| El mar., 28 ene. 2025 14:25, John Clarke
| escribió:
|
| > Hi all,
| >
| > I'm wondering if there is a way to point an R package installer to a
| > pre-compiled release on Github rather than rely on CRAN.
|
|
| Yes, see https://r-universe.dev/
Hi all,
I'm wondering if there is a way to point an R package installer to a
pre-compiled release on Github rather than rely on CRAN. I will likely use
CRAN, but I'm curious if installing via pre-compiled versions is limited to
CRAN or whether there is another way. This is related to a Rcpp projec
El mar., 28 ene. 2025 14:25, John Clarke
escribió:
> Hi all,
>
> I'm wondering if there is a way to point an R package installer to a
> pre-compiled release on Github rather than rely on CRAN.
Yes, see https://r-universe.dev/
Iñaki
I will likely use
> CRAN, but I'm curious if installing via
Dear All,
When I run check_win_devel() on my package, I encounter the following error:
-
Error: objects 'Surv', 'is.Surv' are not exported by 'namespace:survival'
Execution halted
ERROR: lazy loading failed for package 'SPIChanges'
* removing 'd:/RCompile/CRANguest/R-devel/
14 matches
Mail list logo
