It depends on the specific case but attempting to check with the previous
maintainer/author looks like a courteous first step
before taking over.
Georgi Boshnakov
-Original Message-
From: R-package-devel [mailto:r-package-devel-boun...@r-project.org] On Behalf
Of Dirk Eddelbuettel
Sent
On 5 April 2019 at 13:30, peter dalgaard wrote:
| For most packages[*], I assume that you can just take on the role as
maintainer, bump the version number and resubmit. If you don't actually
maintain it, then of course it might fall of CRAN again after a while.
|
| -pd
|
| [*] Actually, I exp
On 5 April 2019 at 11:29, Jose V. Die wrote:
| I am working on my first package and I released a new version (1.0.11). The
CRAN checks link shows the last updated for today although the check details
section refers to version 1.0.1.
|
| So, I’m confused about it. Are those check results from
For most packages[*], I assume that you can just take on the role as
maintainer, bump the version number and resubmit. If you don't actually
maintain it, then of course it might fall of CRAN again after a while.
-pd
[*] Actually, I expect that CRAN policy implies "all" here; I just can't be
bo
Hi,
I am working on my first package and I released a new version (1.0.11). The
CRAN checks link shows the last updated for today although the check details
section refers to version 1.0.1.
So, I’m confused about it. Are those check results from my old version or the
current version just rel
Hi,
I've been searching for some procedures to try an get an old package back
into CRAN.
It's package that has the re exclamation mark on cran github and is not
available via install.packages() for modern version of R.
However some small changes to the source were enough to get it installed
via
