Comments
qulogic
OK, that's because of a typo that created a directory instead of installing the file. You can delete the directory (it should be empty) to proceed, and I'll have to add a scriptlet to fix the upgrade process.
I don't use it directly, but ocrmypdf builds pass and test don't say they've skipped anything due to pdfminer, so it's good enough for me.
The taskotron errors are actually real bugs:
python2-seaborn.noarch: E: non-readable /usr/lib/python2.7/site-packages/seaborn/__pycache__/conftest.cpython-27-PYTEST.pyc 600
These files should not be packaged, and I should have caught that in the PR I made. It can be fixed by setting PYTHONDONTWRITEBYTECODE=1 when running the tests.
Those 4 rebuilds have spent their week in testing; is this update going to get pushed to stable?
I ran:
$ mock -r fedora-27-x86_64 --dnf-cmd -- install 'R-*' --skip-broken
$ mock -r fedora-27-x86_64 --dnf-cmd list 'R-*' | awk '{print $1}' | sed -e 's/\.[^.]\+$//g' -e 's/^R-//' -e 's/-devel$//' | sort -u > pkgs
$ mock -r fedora-27-x86_64 --copyin pkgs /
$ mock -r fedora-27-x86_64 --shell
# for p in `cat pkgs`; do echo "library($p); quit()" | R --quiet --vanilla; done &> results
$ mock -r fedora-27-x86_64 --copyout /results results-f27
then did it again with --enablerepo=updates-testing, and diffed the results.
With this update, we are now able to also install:
- R-blob, and
- R-prettyunits.
Also, now able to correctly load:
- R-future,
- R-listenv,
- R-promises,
- R-R.cache, and
- R-R.rsp.
But now these packages are broken:
- R-chron,
- R-COPASI,
- R-GeneR,
- R-quadprog,
- R-reshape,
- R-roxygen2, and
- R-shogun.
I have rebuilt R-chron, R-quadprog, R-reshape, and R-roxygen2, but I don't have permissions to build the others. If you don't want to wait another week, I can submit these as a separate update.
Ugh, I added +1s on a bunch of the FTBFS bugs, but bodhi didn't save it.
I ran:
$ mock -r fedora-28-x86_64 --dnf-cmd -- install 'R-*' --skip-broken
$ mock -r fedora-28-x86_64 --dnf-cmd list 'R-*' | awk '{print $1}' | sed -e 's/\.[^.]\+$//g' -e 's/^R-//' -e 's/-devel$//' | sort -u > pkgs
$ mock -r fedora-28-x86_64 --copyin pkgs /
$ mock -r fedora-28-x86_64 --shell
# for p in `cat pkgs`; do echo "library($p); quit()" | R --quiet --vanilla; done &> results
$ mock -r fedora-28-x86_64 --copyout /results results-f28
then did it again with --enablerepo=updates-testing, and diffed the results.
With this update, we are now able to also install:
- R-blob,
- R-orcutt, and
- R-prettyunits.
Also, now able to correctly load:
- R-affy,
- R-affydata,
- R-lmtest,
- R-maanova,
- R-msm,
- R-multcomp,
- R-mvtnorm,
- R-preprocessCore,
- R-RM2,
- R-sandwich,
- R-statmod,
- R-systemfit, and
- R-waveslim.
But now these packages are broken:
- R-chron,
- R-COPASI,
- R-GeneR,
- R-quadprog,
- R-reshape, and
- R-roxygen2.
I have rebuilt R-chron, R-quadprog, R-reshape, and R-roxygen2, but I don't have permissions to build the other two. If you don't want to wait another week, I can submit these as a separate update.
R-Rcpp should be submitted as part of the same update, just like soname bumps.
Same problem as the F27 update:
$ mock -r fedora-28-x86_64 --install R-core-3.5.0-1.fc28 --enablerepo=updates-testing R-Rcpp
$ mock -r fedora-28-x86_64 --no-clean --shell
# R
> library(Rcpp)
Error: package or namespace load failed for ‘Rcpp’:
package ‘Rcpp’ was installed by an R version with different internals; it needs to be reinstalled for use with this R version
Not sure why negative karma did not get posted before.
Much like a minor Python version bump, this appears to require rebuilding all R packages. For example,
$ mock -r fedora-27-x86_64 --install R-core-3.5.0-1.fc27 --enablerepo=updates-testing R-Rcpp
$ mock -r fedora-27-x86_64 --no-clean --shell
# R
> library(Rcpp)
Error: package or namespace load failed for ‘Rcpp’:
package ‘Rcpp’ was installed by an R version with different internals; it needs to be reinstalled for use with this R version
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This update has been unpushed.
This triggers a double-free in R-openssl. There's a hotfix available (which is technically leaky), but it'd be nice to submit that fix in the same update. Or see if upstream's https://github.com/openssl/openssl/issues/8375 can be patched.