Hi all,
I'm trying to upload a new version of my "huxtable" package. It is
currently failing reverse dependency checks for two packages (homnormal and
RSStest). The relevant failures are below.
I got this failure one time, and fixed the problem, which relates to
mistakenly relying on the Suggeste
On 08/02/2024 4:24 a.m., David Hugh-Jones wrote:
Hi all,
I'm trying to upload a new version of my "huxtable" package. It is
currently failing reverse dependency checks for two packages (homnormal and
RSStest). The relevant failures are below.
I got this failure one time, and fixed the problem,
Hi David,
If you didn't increase the version number it could happen that the old
version of the package was used (as CRAN might not be aware that there is a
new version).
The CRAN repository policy says: "Increasing the version number at each
submission reduces confusion so is preferred even when
Thanks for this tip. Out of interest, is there a way to make win/Mac
builder run revdep checks?
Writing: wyclif.substack.com
Book: www.wyclifsdust.com
On Thu, 8 Feb 2024 at 10:26, Lluís Revilla wrote:
> Hi David,
>
> If you didn't increase the version number it could happen that the old
> vers
I intend to change the maintainer of my package {sfdep}
https://cran.r-project.org/package=sfdep.
Is the process as simple as submitting a new release where the DESCRIPTION
file changes who has the role of `aut`?
[[alternative HTML version deleted]]
___
Are you aware of this [1]? J. Random Lurker may not be a reliable source, and
actual CRAN repo maintainers are probably a bit busy...
[1] https://cran.r-project.org/web/packages/policies.html#Submission
On February 8, 2024 8:37:50 AM PST, Josiah Parry wrote:
>I intend to change the maintainer o
I’m sorry? I do not follow.
On Thu, Feb 8, 2024 at 12:01 Jeff Newmiller via R-package-devel <
r-package-devel@r-project.org> wrote:
> Are you aware of this [1]? J. Random Lurker may not be a reliable source,
> and actual CRAN repo maintainers are probably a bit busy...
>
> [1] https://cran.r-proj
The process is described in the 6th bullet of the "Source Packages"
section of the CRAN Policies:
https://cran.r-project.org/web/packages/policies.html
"When a new maintainer wishes to take over a package, this should be
accompanied by the written agreement of the previous maintainer
(unless the p
Much appreciated, Josh! One day I’ll internalize everything in the
policies.
On Thu, Feb 8, 2024 at 12:32 Joshua Ulrich wrote:
> The process is described in the 6th bullet of the "Source Packages"
> section of the CRAN Policies:
> https://cran.r-project.org/web/packages/policies.html
>
> "When a
В Wed, 7 Feb 2024 08:40:44 -0600
Marcin Jurek пишет:
> Packages required but not available: 'Rcpp', 'FNN',
> 'RcppArmadillo' Packages suggested but not available for checking:
> 'fields', 'rmarkdown', 'testthat', 'maptools'
One of the machines running the incoming checks was having problems. If
Ok, this makes sense! I saw that Rcpp was failing the checks too but I
wasn't sure if I should resubmit or wait. Thanks!
On Thu, Feb 8, 2024 at 1:17 PM Ivan Krylov wrote:
> В Wed, 7 Feb 2024 08:40:44 -0600
> Marcin Jurek пишет:
>
> > Packages required but not available: 'Rcpp', 'FNN',
> > 'Rcpp
Hi David,
Dependency checks cannot be run on win /Mac builders as far as I know.
Some packages have more than 2000 packages depending on them.
It would be too much for the heavily used CRAN's machines.
Best,
Lluís
On Thu, 8 Feb 2024 at 13:52, David Hugh-Jones
wrote:
> Thanks for this tip. Out
On 8 February 2024 at 13:28, Marcin Jurek wrote:
| Ok, this makes sense! I saw that Rcpp was failing the checks too but I
| wasn't sure if I should resubmit or wait. Thanks!
For completeness, it was not caused by Rcpp but rather by a mix on new clang
and gcc versions which somehow got into each
13 matches
Mail list logo
