-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
49 pkgs can't be installed because they are in official jammy/universe for R-4.1 but not in r2u #11
Comments
Correct,
It is actually manual labor (no prebuilds to lean on ...) and my personal focus in CRAN/ I see what I can do but this is a slight feature-creep. |
OTOH we do have a fair number. You could use my
|
I just added |
Can you provide evidence of the claimed other 48 packages not installing (if and when you have pinning set up) ? |
Also your initial post is wrong: the dependency issue is on the virtual BioC release tag the Debian maintainers add. No more, no less. |
Oh, if it implies manual labor please don't do this!
I have set apt pinning:
The 49 packages (now 48) I mentioned are not in r2u. They come from the ubuntu universe package and therefore they have the Reproducible example of the installation issue:My concern is that those 48 packages on your r2u docker image may fail to be installed without giving any notice: Here is a reproducible example of me trying to install the biocViews BioConductor package: docker run \
--rm
docker.io/eddelbuettel/r2u:22.04 \
bash -c 'install.r BiocManager; R -e "BiocManager::install(\"biocViews\"); library(biocViews)"' With the corresponding output: The install.r BiocManager` part works:
The This is the `BiocManager::install("biocViews") output, which does not show any relevant error but also it does not show any installation of the biocViews package:
And indeed we can verify it is not installed:
Since the virtual BioC release tag is there, the packages are not installable and bspm fails to install them. Maybe this should be reported to bspm instead? |
Ah, now we're talking. Your "error", if any, is to use BiocManager. And just like using the RStudio Package manager, or |
If I do a quick check (in the |
With
Gives me:
This problem happens with packages found in the ubuntu 22.04 universe repository and not found in r2u. |
Of course. The 'Depends: r-bioc-3.14' makes it so. Eg try the more explicit
|
If you want to look hard into pinning I believe there is a way to set an exclusion too so maybe you can try that (I haven't ...) Alternatively, you could create an (almost empty, near-virtual) package providing |
Ok, to prove that point I just created a dummy 'empty' package, currently called 'fake-bioc' which has a root@cffc07a66985:/deb# dpkg -i fake-bioc_0.0.1_all.deb
Selecting previously unselected package fake-bioc.
(Reading database ... 21839 files and directories currently installed.)
Preparing to unpack fake-bioc_0.0.1_all.deb ...
Unpacking fake-bioc (0.0.1) ...
Setting up fake-bioc (0.0.1) ...
root@cffc07a66985:/deb# install.r BiocViews
Install system packages as root...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Ign https://dirk.eddelbuettel.com/cranapt jammy InRelease
Get:1 https://dirk.eddelbuettel.com/cranapt jammy Release [5713 B]
Get:2 https://dirk.eddelbuettel.com/cranapt jammy Release.gpg [793 B]
Get:3 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Hit http://archive.ubuntu.com/ubuntu jammy InRelease
Get:4 https://dirk.eddelbuettel.com/cranapt jammy/main amd64 Packages [2062 kB]
Get:5 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [109 kB]
Get:6 https://ppa.launchpadcontent.net/marutter/rrutter4.0/ubuntu jammy InRelease [17.5 kB]
Get:7 https://dirk.eddelbuettel.com/cranapt jammy/main all Packages [6382 kB]
Get:8 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB]
Get:9 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 Packages [212 kB]
Get:10 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages [153 kB]
Get:11 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages [89.8 kB]
Get:12 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [229 kB]
Get:13 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 Packages [4648 B]
Get:14 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages [236 kB]
Get:15 https://ppa.launchpadcontent.net/marutter/rrutter4.0/ubuntu jammy/main Sources [8932 B]
Get:16 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages [4648 B]
Get:17 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [380 kB]
Get:18 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages [2016 B]
Get:19 https://ppa.launchpadcontent.net/marutter/rrutter4.0/ubuntu jammy/main amd64 Packages [7564 B]
Fetched 10.1 MB in 0s (0 B/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Get:1 http://archive.ubuntu.com/ubuntu jammy/universe amd64 r-bioc-biocviews all 1.62.1-1 [655 kB]
Get:2 https://dirk.eddelbuettel.com/cranapt jammy/main all r-bioc-biocgenerics all 0.42.0-1.ca2204.1 [582 kB]
Get:3 https://dirk.eddelbuettel.com/cranapt jammy/main amd64 r-bioc-biobase amd64 2.56.0-1.ca2204.1 [2096 kB]
Get:4 https://dirk.eddelbuettel.com/cranapt jammy/main amd64 r-bioc-graph amd64 1.74.0-1.ca2204.1 [1237 kB]
Get:5 https://dirk.eddelbuettel.com/cranapt jammy/main all r-cran-bh all 1.78.0-0-1.ca2204.1 [8330 kB]
Get:6 https://dirk.eddelbuettel.com/cranapt jammy/main amd64 r-bioc-rbgl amd64 1.72.0-1.ca2204.1 [2583 kB]
Get:7 https://dirk.eddelbuettel.com/cranapt jammy/main amd64 r-cran-xml amd64 3.99-0.10-1.ca2204.1 [1696 kB]
Get:8 https://dirk.eddelbuettel.com/cranapt jammy/main amd64 r-cran-bitops amd64 1.0-7-1.ca2204.1 [25.5 kB]
Get:9 https://dirk.eddelbuettel.com/cranapt jammy/main amd64 r-cran-rcurl amd64 1.98-1.7-1.ca2204.1 [799 kB]
Get:10 https://dirk.eddelbuettel.com/cranapt jammy/main all r-cran-runit all 0.4.32-1.ca2204.1 [281 kB]
Get:11 https://dirk.eddelbuettel.com/cranapt jammy/main all r-cran-biocmanager all 1.30.18-1.ca2204.1 [338 kB]
Fetched 18.6 MB in 6s (0 B/s)
Selecting previously unselected package r-bioc-biocgenerics.
(Reading database ... 21841 files and directories currently installed.)
Preparing to unpack .../00-r-bioc-biocgenerics_0.42.0-1.ca2204.1_all.deb ...
Unpacking r-bioc-biocgenerics (0.42.0-1.ca2204.1) ...
Selecting previously unselected package r-bioc-biobase.
Preparing to unpack .../01-r-bioc-biobase_2.56.0-1.ca2204.1_amd64.deb ...
Unpacking r-bioc-biobase (2.56.0-1.ca2204.1) ...
Selecting previously unselected package r-bioc-graph.
Preparing to unpack .../02-r-bioc-graph_1.74.0-1.ca2204.1_amd64.deb ...
Unpacking r-bioc-graph (1.74.0-1.ca2204.1) ...
Selecting previously unselected package r-cran-bh.
Preparing to unpack .../03-r-cran-bh_1.78.0-0-1.ca2204.1_all.deb ...
Unpacking r-cran-bh (1.78.0-0-1.ca2204.1) ...
Selecting previously unselected package r-bioc-rbgl.
Preparing to unpack .../04-r-bioc-rbgl_1.72.0-1.ca2204.1_amd64.deb ...
Unpacking r-bioc-rbgl (1.72.0-1.ca2204.1) ...
Selecting previously unselected package r-cran-xml.
Preparing to unpack .../05-r-cran-xml_3.99-0.10-1.ca2204.1_amd64.deb ...
Unpacking r-cran-xml (3.99-0.10-1.ca2204.1) ...
Selecting previously unselected package r-cran-bitops.
Preparing to unpack .../06-r-cran-bitops_1.0-7-1.ca2204.1_amd64.deb ...
Unpacking r-cran-bitops (1.0-7-1.ca2204.1) ...
Selecting previously unselected package r-cran-rcurl.
Preparing to unpack .../07-r-cran-rcurl_1.98-1.7-1.ca2204.1_amd64.deb ...
Unpacking r-cran-rcurl (1.98-1.7-1.ca2204.1) ...
Selecting previously unselected package r-cran-runit.
Preparing to unpack .../08-r-cran-runit_0.4.32-1.ca2204.1_all.deb ...
Unpacking r-cran-runit (0.4.32-1.ca2204.1) ...
Selecting previously unselected package r-cran-biocmanager.
Preparing to unpack .../09-r-cran-biocmanager_1.30.18-1.ca2204.1_all.deb ...
Unpacking r-cran-biocmanager (1.30.18-1.ca2204.1) ...
Selecting previously unselected package r-bioc-biocviews.
Preparing to unpack .../10-r-bioc-biocviews_1.62.1-1_all.deb ...
Unpacking r-bioc-biocviews (1.62.1-1) ...
Setting up r-cran-bh (1.78.0-0-1.ca2204.1) ...
Setting up r-bioc-biocgenerics (0.42.0-1.ca2204.1) ...
Setting up r-cran-bitops (1.0-7-1.ca2204.1) ...
Setting up r-cran-biocmanager (1.30.18-1.ca2204.1) ...
Setting up r-bioc-biobase (2.56.0-1.ca2204.1) ...
Setting up r-cran-runit (0.4.32-1.ca2204.1) ...
Setting up r-cran-xml (3.99-0.10-1.ca2204.1) ...
Setting up r-cran-rcurl (1.98-1.7-1.ca2204.1) ...
Setting up r-bioc-graph (1.74.0-1.ca2204.1) ...
Setting up r-bioc-rbgl (1.72.0-1.ca2204.1) ...
Setting up r-bioc-biocviews (1.62.1-1) ...
root@cffc07a66985:/deb# |
See https://github.com/eddelbuettel/bioc-api-package for a version of that helper package (now slightly renamed). |
@zeehio -- did you get a chance to test this? |
The tests I did worked fine. I think it would be nice if the bspm package could report installation errors but that's beyond this repository and the r2u packaging. I may contact the rspm maintainer and try to provide a patch. Beyond that we can close this issue if you like. (Feel free to provide the almost virtual package in your r2u repository if you feel like it) Thanks for your time and work. It helped me a lot to understand how all of this works |
The 'almost virtual' package is now on github, I think I will just point to it from the r2u documentation. Maybe sticking it into r2u is the way to go too. Gotta think about that... Repos and their mechanics are very very cool and powerful, but not that well documented. I learned some ropes as a Debian maintainer. There is a bit of a formal / bureaucratic hurdle to climb these days to join Debian but you can always experiment with local packages, or with Ubuntu via Launchpad. Bug me (or the r-sig-debian list) if you have questions -- we all want to see this used and made more robust so your inquiries do help and are appreciated. Keep it comin... |
I added such a package to jammy (and focal, though it may matter less there) and updated the FAQ with a new entry. So I think this can now be closed for good. |
The
r-bioc-affxparser
package is not included in your r2u packages probably because no CRAN package depends on it.However it is part of the ubuntu jammy universe repository https://packages.ubuntu.com/jammy/r-bioc-affxparser
And since ubuntu jammy ships with R-4.1, the package is not installable on an R-4.2 system:
Could you extend your r2u inclusion criteria to all those bioconductor packages already in ubuntu jammy? I took the 99 "r-bioc-" packages from https://packages.ubuntu.com/search?suite=jammy&arch=amd64&searchon=names&keywords=r-bioc- and with a rudimentary script I filtered out those already in r2u. If I am not mistaken, I would be asking you to include 49 additional packages in r2u that since they are already in ubuntu jammy they are not installable on my system via apt:
I'll get those packages straight from Bioconductor if I need them, but I feel it would make sense to cover those and they are not that many (I'm assuming the build process is mostly automated)
Thanks
The text was updated successfully, but these errors were encountered: