Re: Bug#949659: r-cran-parameters: autopkgtest regression
Hi Graham,
thanks for your bug report.
On Thu, Jan 23, 2020 at 12:21:50PM +0200, Graham Inggs wrote:
>
> E: Package 'r-cran-brms' has no installation candidate
The excuses page says:
autopkgtest for r-cran-brms/2.11.0-1: amd64: Regression ♻ , arm64: Regression ♻
and refers in the Regression link to
https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-brms/3988759/log.gz
which has:
...
Get:102 http://deb.debian.org/debian testing/main amd64 r-cran-loo all 2.1.0-1 [2,131 kB]
...
Loading required package: Rcpp
Error: package or namespace load failed for ‘brms’:
object ‘.compute_point_estimate’ is not exported by 'namespace:loo'
Execution halted
That's pretty strange since r-cran-loo has 2.2.0-1 in unstable *and*
testing. I think it would be wrong to force some versioned Depends
here since r-cran-brms has no explicit dependency from r-cran-loo.
IMHO this issue is caused by a not up to date debci environment for
testing.
> E: Package 'r-cran-caic4' has no installation candidate
That's a bit unfortunate. The package was accepted but needs a source
only upload to migrate. I intended to do this just with latest upstream
version but its waiting for r-cran-rlrsim in new (#948264). Since I see
other issues I don't intend to push things here and wait for ftpmaster
some more days.
> E: Package 'r-cran-nfactors' has no installation candidate
Argh:
Not built on buildd: arch all binaries uploaded by tille, a new source-only upload is needed to allow migration
IMHO the fact that we can not do source uploads to new but source
upload to testing is a real nuisance and will probably beat us
several times. Just building and uploading ...
> E: Package 'r-cran-rstanarm' has no installation candidate
That's extremely strange.
r-cran-rstanarm (2.19.2-1) unstable; urgency=medium
...
* Test-Depends: r-cran-codetools
-- Andreas Tille <tille@debian.org> Mon, 07 Oct 2019 17:58:15 +0200
I verified that this was really uploaded and
$ cat debian/tests/control
Tests: run-unit-test
Depends: @, r-cran-testthat, r-cran-stanheaders (>= 2.18.1-10-2), r-cran-bh, r-cran-codetools
Restrictions: allow-stderr
But it seems that codetools has an issue here:
$ curl --silent https://ci.debian.net/data/autopkgtest/unstable/amd64/r/r-cran-rstanarm/4018302/log.gz | zcat | grep codetools
r-cran-callr r-cran-checkmate r-cran-cli r-cran-codetools r-cran-colorspace
r-cran-callr r-cran-checkmate r-cran-cli r-cran-codetools r-cran-colorspace
Get:204 http://deb.debian.org/debian unstable/main amd64 r-cran-codetools all 0.2-16-1 [90.1 kB]
Selecting previously unselected package r-cran-codetools.
Preparing to unpack .../203-r-cran-codetools_0.2-16-1_all.deb ...
Unpacking r-cran-codetools (0.2-16-1) ...
Setting up r-cran-codetools (0.2-16-1) ...
r-cran-tikzdevice r-cran-codetools r-cran-runit r-cran-sodium
code for methods in class “Rcpp_model_bernoulli” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_bernoulli” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_binomial” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_binomial” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_continuous” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_continuous” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_count” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_count” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_jm” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_jm” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_lm” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_lm” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_mvmer” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_mvmer” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_polr” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
code for methods in class “Rcpp_model_polr” was not checked for suspicious field assignments (recommended package ‘codetools’ not available?)
I do not fully understand whether this is the issue for the error or
not. At least in my pbuilder chroot the test succeeded.
Kind regards
Andreas.
> [1] https://ci.debian.net/packages/r/r-cran-parameters/unstable/amd64/
> [2] https://ci.debian.net/packages/r/r-cran-parameters/testing/amd64/
--
http://fam-tille.de
Reply to: