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
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
On 2024-09-23 4:13 p.m., Ben Bolker wrote:
Hmmm. Assuming the previous version of the package (without the
extensions/updates) avoids all of the testing errors, I would say that
RAW ("rules as written") the only constraint I can see on submitting a
"rollback" version of the package would be the C
I can imagine a (perhaps overly complicated) scenario:
* version 1 passes tests OK when it is submitted to CRAN
* version 2 passes tests OK when it is submitted to CRAN
* CRAN introduces new tests (compiler versions, etc. etc.) that break
version 2 but not version 1.
Now version 1 would still pa
Hmmm. Assuming the previous version of the package (without the
extensions/updates) avoids all of the testing errors, I would say that
RAW ("rules as written") the only constraint I can see on submitting a
"rollback" version of the package would be the CRAN request for
updates “no more than every 1
Hello all,
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
machine to debug my package. Ideally I'd want a pr
