Hi,
I just tried to upgrade Nixpkgs to R 3.5.0, but unfortunately the new
version fails its regression test suite. We configure the build using
the flags "--without-recommended-packages", in case that's relevant. You
can see a complete build log with all relevant information at [1].
Anyway, the te
Duncan Murdoch writes:
> You can likely get rid of most of them by building with the recommended
> packages.
unfortunately, this is not an option for us. For various reasons, our
build process requires that we build those packages separately. Ricardo
appears to be in a similar situation and he
Hi Dirk,
> I have been doing for R for about 20 years (if you count the time I
> assisted Doug Bates when he was still the maintainer) (and longer for
> Debian), and you seem to follow the same model we set up years ago of
> splitting the content of r-recommended (itself a virtual package) off
Duncan Murdoch writes:
>> ./configure --without-recommended-packages && make && make check
>
> So you're getting paid to do what you do, but you want the volunteers
> in R Core to do some work for you for free.
You are jumping to conclusions. Nobody pays me a single cent to package
R for Nix;
Hi,
I tried compiling the latest pre-release for R 3.3.3 for the NixOS Linux
distribution [1], but the build fails during the "make check" phase
because of the following 2 issues:
1) The "tools" test in "tests/Examples" requires network access, which
it doesn't have in our build environment. T
Hi Brian,
> R-devel (your subject line) is not a pre-release of R 3.3.3: it is 'R
> Under development' for what is planned as R 3.4.0. Pre-release
> tarballs for 3.3.3 are things like R-rc_2017-02-26_r72260.tar.gz (and
> were previously labelled R-beta).
I did not realize this distinction exi
Hi Martin,
> Is it necessary to also run the 'make check' part in that restricted
> environment? Or could that ('checking") not get more priviledges?
in NixOS, there is no way to run any kind of build process in an
environment that has network access. On one hand, that is a security
considerati
Hi,
I maintain the R packages in the NixOS Linux distribution [1]. A while
ago, I attempted to update to version 3.1.1, but I ran into the
following test suite failure:
| Testing examples for package 'tools'
| comparing 'tools-Ex.Rout' to 'tools-Ex.Rout.save' ...
| 452c452
| < character(0)
Hi Uwe,
> Nobody in R core runs NixOS and can reproduce this. This passes on most
> other platforms, apparently. If you can point us to a problem or send
> patches, we'd appreciate it.
have tried running the test suite in a build that's configured with
'--without-recommended-packages'? That's
Hi Uwe,
>> have tried running the test suite in a build that's configured with
>> '--without-recommended-packages'?
>
> Of course this fails in the case when we check for the recommended packages:
>
> | < character(0)
> | ---
> | > [1] "Matrix" "nlme" "mgcv"
>
> If Matrix et al a
Hi Duncan,
> I don't think we should be removing tests for everybody to allow a few
> people to test a build of R that none of us actually use.
no tests need to be removed. All that needs to be done is to distinguish
tests that require the recommended packages from those that don't. Then
users
11 matches
Mail list logo