similar to: Announcing r2u: 20k CRAN binaries for Ubuntu 22.04 + 20.04

On 26 March 2023 at 18:30, Dirk Eddelbuettel wrote: | Over the last few months I have provided multiple 'demos' as animated gifs | showing how for example `system.time(install.package("tinyverse"))` installs | all these packages and all their dependencies in under twenty seconds (!!). Classic typo as Josh kindly pointed out over DM:

CRAN, by relying on the powerful package management system that is part of R, provides an unparalleled framework for extending R with nearly 20k packages. We recently encountered an issue that highlights a missing element in the otherwise outstanding package management system. So we would like to start a discussion about enhancing its feature set. As shown below, a mechanism to force

I started using r2u (see https://eddelbuettel.github.io/r2u) recently and thought I was having a problem in that I was getting out-of-date versions of packages. I made enquiries of Dirk Eddelbuettel about this, and he enlightened me as to what the problem really was. I was seeing old versions of packages that were stored in a library, different from /usr/lib/R/site-library. I have a personal

I am putting this here as it may be of general and not just my own interest.? I am currently running 4.3.1 on Ubuntu 22.04.2 LTS but am hitting an issue that the magick package won't update because libmagick++-dev won't update because, presumably, of two repositories in my sources.list disagreeing about versions required.? That's not so urgent an issue for me that I wont just wait

I can understand why it changes the game. It would be sweet if we could do something like r2u for Debian, but for now > we can't. Switching between Debian and Ubuntu is not that onerous though. Do you mind clarifying what you do here? Do you operate Ubuntu when working in R? Or do you somehow operate Ubuntu to manage R packages and dependencies, and then switch back into Debian to carry

On 6 June 2023 at 23:33, Johan Andresen wrote: | Cheers - my response mixes up the order of things: | | The suggested apt way INSTALLED INTERFLEX nicely. Lesson learned: install | dependencies from apt if a package/library isn't in apt search. | | Yes I also tried install.packages('interflex'). RStudio console complained | about the same packages like this: | ERROR: dependency

Cheers - my response mixes up the order of things: The suggested apt way INSTALLED INTERFLEX nicely. Lesson learned: install dependencies from apt if a package/library isn't in apt search. Yes I also tried install.packages('interflex'). RStudio console complained about the same packages like this: ERROR: dependency 'xyz' is not available for package ''abc" *

I was delighted I with how fast (faster than a tickled toddler giggles) r2u scarfed packages I. up my Pop!_OS (Ubuntu in party attire tuned for System76). But, despite 40 years as my own sys admin (classic fool for a client?), I bolluxed up, ending up with an install chain that was inferior to compiling from source, despite having to occasionally track down system dependencies. Absolutely no

Btw Dirk, can I help package interflex for apt? Please be welcome to refer me to guidelines/a manual for doing so if you can imagine it happening. Johan Den ons. 7. jun. 2023 kl. 08.37 skrev Johan Andresen < johan.andresen at gmail.com>: > I can understand why it changes the game. > > It would be sweet if we could do something like r2u for Debian, but for now >> we

This is definitely tangential to the list: I'm on Ubuntu (22.04.2 LTS) not Debian and I'm sure this is about issues in the Ubuntu package management on my machine, R is only revealing them. The original subject line came from me wondering if my going over to the r2u repository would solve the problem.? However, as I think Dirk said, that's only really likely to be answered by trying

Hi, I get an error using RcppGSL: fatal error: gsl/gsl_vector.h:No such file or directory. What is the best way to install these files as they seem to be missing? Thanks, Oyvind -- View this message in context: http://r.789695.n4.nabble.com/Error-using-RcppGSL-tp3613535p3613535.html Sent from the R devel mailing list archive at Nabble.com.

Luben, We all have different types of learning and how we approach this, let alone how we decompose things. With that, sorry you found this frustrating. Many of us put volunteer time into this trying to make things 'possible' and preferably 'easy' but we don't always get there. That said, I have shown multiple times over the last few years that the simple _one statement

===== Summary ===== Version 0.9.0 of the Rcpp package is now on CRAN and its mirrors. This release marks another step in the development of the package, and a few key points are highlighted below. More details are in the NEWS and ChangeLog files included in the package. ===== Overview ===== Rcpp is an R package and associated C++ library that facilitates integration of C++ code in R

===== Summary ===== Version 0.9.0 of the Rcpp package is now on CRAN and its mirrors. This release marks another step in the development of the package, and a few key points are highlighted below. More details are in the NEWS and ChangeLog files included in the package. ===== Overview ===== Rcpp is an R package and associated C++ library that facilitates integration of C++ code in R

On 16 March 2023 at 13:39, Felipe Contreras wrote: | I see R by default installs packages in ~/R. I know I can change the | default directory with R_LIBS_USER, but software shouldn't be | polluting the home directory. | | For example both python and node install packages to ~/.local/lib, | ruby to ~/.local/share. They don't install to for example ~/node. | | R should do the same: it

>How did you upgrade ? >If I remember correctly, both 20.04 and 22.04 come with 4.15.13 (latest Samba version available), so could it be that the upgrade from 20.04 to >22.04 managed to install unrequired packages ? I did a do-release-upgrade first to go from 20.04 to 22.04, and then updated my /etc/apt/sources.list.d/mjt.list to go from focal/samba-4.18 to jammy/samba-4.19. I also

On Tue, 5 Dec 2023 15:21:50 +0100 Joachim Lindenberg via samba <samba at lists.samba.org> wrote: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> > 4.19, but the Dc is not yet working again. How did you upgrade ? If I remember correctly, both 20.04 and 22.04 come with 4.15.13 (latest Samba version available), so could it be that the upgrade from 20.04 to

05.12.2023 17:51, Luis Peromarta via samba : > It?s always recommend to demote the DC, upgrade samba, and join the DC again. Did you do it this way ? This is rarely needed and in almost all cases is unnecessary and just an extra work. The only good reason to do that is when you upgrade a very old version of samba, skipping 5..10 or more releases in between, and even there it almost always

It?s always recommend to demote the DC, upgrade samba, and join the DC again. Did you do it this way ? You may have a broken DC, or a broken installation. Instead of troubleshooting, which you can of course do, I?d demote (or force-demote), reinstall and re join. http://samba.bigbird.es/doku.php?id=samba:upgrade-sama LP On 5 Dec 2023 at 15:45 +0100, Joachim Lindenberg via samba <samba at

I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. systemctl status samba-ad-dc shows: Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) Dec 05 12:48:39 cobra samba[749]: task_server_terminate: task_server_terminate: [winbindd child process