Make the new `r-ottr` conda package compatible with R 4.1.* about otter-grader HOT 8 CLOSED

Thanks for the fix @mfansler! @joelostblom can you check if this now works for you on Windows?

from otter-grader.

Thank you @mfansler and @chrispyles ! I don't have a windows machine myself, but today I tried installing r-ottr on a student's windows machine with R 4.1 and it worked without issues. I haven't tried the full environment from scratch yet, but I'm assuming that will work well now that there is no longer a conflict with ottr and R 4.1. Thanks again!

from otter-grader.

@joelostblom yes ottr should be compatible with any version of R v4. Where do you see it pinned to >=4.2? The recipe doesn't specify a version for r-base

from otter-grader.

That's odd, a few of my students who are on Windows encountered the following issue, which makes it seem like ottr require >=4.2. Reading the error message again, I realize that maybe it is the first issue of not finding base R 4.3 that leads to the second issue. I will try with a few student in class tomorrow to see if it works when we specify R =4.1 on windows

from otter-grader.

I just tried this with a student on their windows machine using R>=4.1 and I see the same error for ottr although the R version is now found correctly. This is the full env file https://github.ubc.ca/MDS-2023-24/DSCI_531_viz-1_students/blob/c8cc61534ec0d4b103d9888a572a3fcf84da90b5/environment.yaml

from otter-grader.

The environment.yml file link is on a github enterprise server which I can't log in to; can you share its contents here?

It looks like there was a bot-created PR in the feedstock repo to make r-ottr compatible with r-base 4.3, but I didn't think it would make it stop accepting lower versions. conda-forge/r-ottr-feedstock#1

from otter-grader.

My bad, here is the full env, it is quite extensive and could probably be reproduced with a subset of these packages but I don't have access to a windows machine to test:

name: '531'
channels:
    - conda-forge
    - r
    - defaults
dependencies:
    - python=3.11.*
    - pip
    - ipykernel
    - nb_conda_kernels
    - otter-grader=5.2.2
    - altair=5.1.2
    - vl-convert-python  # For saving altair charts as static images
    - vegafusion  # For working with charts > 5,000 graphical objects
    - vegafusion-python-embed  # Same as the previous one
    - vegafusion-jupyter  # For working with charts > 100,000 graphical objects
    - vega_datasets  # Altair example data
    - scipy
    - matplotlib
    - panel
    - r-base>=4.1
    - r-essentials
    - r-devtools
    - r-gert
    - r-usethis
    - r-testthat
    - r-startup
    - r-rmarkdown
    - r-stringi
    - r-tidyverse
    - r-hmisc
    - r-rjson
    - r-ottr
    - r-ggally
    - r-ggthemes
    - r-cowplot
    - r-irkernel

from otter-grader.

Conda R packages build against a specific R version, even if there is no constraint in the recipe. Conda Forge currently defaults to building for R 4.2 and 4.3, plus 4.1 only for Windows (which, yes, is stuck due to outdated build tools). With a pure R ("noarch") package like this, the configuration doesn't build a Windows version and therefore skips the R 4.1 build.

I've added a customization to the build variants (done through a conda_build_config.yaml) to explicitly include a R 4.1 build. It should be available in a couple hours.

from otter-grader.