A package of mine on CRAN has some old function names (not S3 methods) that
include "." (e.g., "esa.plot"). In a new version I want to simultaneously
1. rename these functions to e.g. "esaPlot"
2. export a new S3 generic with the base name (e.g. "esa") and methods for
different model types (e.g.
Thanks both.
Josiah Parry says:
> Ben, the issue is that {rstan} is not available. Since it is a
suggested package it is not expected to always be there.
The thing is that the checks for rstan-based objects *are*
conditional. This is actually failing on the tests for brms-based
object
All,
Thank you for your feedback and suggestions. Yes, the package is Colossus
(https://github.com/ericgiunta/Colossus). From April to September of this year
version 1.1.1 was available on CRAN while I updated the GitHub version, with no
issues on CRAN. Then earlier this month I updated to vers
В Tue, 24 Sep 2024 10:27:34 -0400
Ben Bolker пишет:
>Weirdly, I can't get this to fail on my local system even if I
> remove rstan -- maybe rstan needs to be present for brms at install
> time but not at runtime ... ???
I'm noticing that despite broom.mixed having Suggests: rstan and it
bein
Ben, the issue is that {rstan} is not available. Since it is a suggested
package it is not expected to always be there.
This is referred to is the "hard" check.
Here is a GitHub CI workflow I use to perform this check:
https://github.com/JosiahParry/sfdep/blob/008a59b6009d01e5e1625319f6525c1e0ba
broom.mixed is failing tests on Fedora.
With apologies for the mangled formatting, here is the test failure
(full properly formatted details at
https://www.r-project.org/nosvn/R.check/r-devel-linux-x86_64-fedora-gcc/broom.mixed-00check.html).
══ Failed tests
═
Hi,
I run an updated Fedora platform, and can build R under clang 18.1.8. If the
affected package is Colossus, and https://github.com/ericgiunta/Colossus is the
appropriate repo, could you indicate where you posted the error reports, and if
they are not on the repo, please commit and push them
В Mon, 23 Sep 2024 16:15:28 +
Eric Giunta пишет:
> Recently I submitted a large update to the package I maintain and was
> unable to resolve the testing errors prior to it being archived. I've
> been unable to reproduce the errors, so I expect to have to setup my
> own fedora_clang virtual ma
Dear Eric,
While changing the version number of an old package could solve this, it is
a work-around that won't help much:
Users will be able to install the binaries of an old package without the
new fixes and improvements of the later at the cost of another submission,
which might delay the submi
