On 13/02/2022 2:33 p.m., Daniel Sjoberg wrote:
Thank you so much for the response Duncan!
How does one go about writing to CRAN?
Ben gave you the address: c...@r-project.org.
The package is tested and ready to be shipped to CRAN, but since it's
failing on Win Devel, I assumed it would be auto-rejected if I submitted
for a CRAN release.
I think CRAN and Winbuilder are separate machines. If CRAN isn't showing
errors in its tests of the hardhat package then it has probably
successfully built it and will use it in tests. Currently it looks fine:
https://cran.r-project.org/web/checks/check_results_hardhat.html
I do recommend testing on Windows R-devel on one of the other platforms
I listed before submitting to CRAN. I don't think auto-rejects waste a
lot of their time, but it's better to get accepted on the first try.
Duncan Murdoch
On Sun, Feb 13, 2022 at 2:29 PM Duncan Murdoch <murdoch.dun...@gmail.com
<mailto:murdoch.dun...@gmail.com>> wrote:
I'd suggest writing to CRAN to point out that they may need to take a
look, if you haven't already done so. In the meantime, you can test
elsewhere (R-hub, Github, your own Windows machine or image, etc.)
Duncan Murdoch
On 13/02/2022 10:32 a.m., Daniel Sjoberg wrote:
> Is there something wrong with the Windows Dev machine? It's now
been 3
> weeks since the release of the hardhat package v 0.2.0 on CRAN,
and it's
> still not available in the Win Dev check.
>
> I have this in my DESCRIPTION file:
> Imports:
> hardhat (>= 0.2.0)
>
> And still getting this note when running devtools::check_win_devel().
>
> Package required and available but unsuitable version: 'hardhat'
>
> https://cran.r-project.org/package=hardhat
<https://cran.r-project.org/package=hardhat>
>
> Daniel
>
>
> On Tue, Feb 8, 2022 at 9:55 AM Daniel Sjoberg
<danield.sjob...@gmail.com <mailto:danield.sjob...@gmail.com>>
> wrote:
>
>> For what it's worth, I am seeing a similar issue.
>>
>> I am trying to make a release that depends on the hardhat
package, which
>> made a release on 2022-01-24, and it's still unavailable to check on
>> WinDevel. I am also depending on the newest release of gtsummary
which was
>> made available on CRAN on 2022-01-29 (after hardhat's release). The
>> gtsummary package, however, became available on WinDevel a few
days later.
>>
>> Thank you,
>> Daniel
>>
>> On Tue, Feb 8, 2022 at 9:06 AM Ian Lyttle <ijlyt...@me.com
<mailto:ijlyt...@me.com>> wrote:
>>>
>>> I am trying to check a package release-candidate on win-builder
r-devel.
>> This package imports a recently-released version of another package,
>> {vegawidget}.
>>> The check on win-builder (r-devel) fails:
>>> * checking package dependencies ... ERROR
>>> Package required and available but unsuitable version: 'vegawidget'
>>> {vegawidget} 0.4.1 was released on CRAN on 2022-01-29, but is
apparently
>> not available to win-builder r-devel.
>>> For what it’s worth, the check passes for win-builder r-release and
>> r-oldrel.
>>> Is this just a matter of me needing to be more patient, or
could there
>> be something “stuck” at win-builder?
>>> Thanks!
>>>
>>>
>>>
>>> [[alternative HTML version deleted]]
>>>
>>> ______________________________________________
>>> R-package-devel@r-project.org
<mailto:R-package-devel@r-project.org> mailing list
>>> https://stat.ethz.ch/mailman/listinfo/r-package-devel
<https://stat.ethz.ch/mailman/listinfo/r-package-devel>
>>
>
> [[alternative HTML version deleted]]
>
> ______________________________________________
> R-package-devel@r-project.org
<mailto:R-package-devel@r-project.org> mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel
<https://stat.ethz.ch/mailman/listinfo/r-package-devel>
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
