similar to: installing from copr after update

Many thanks I?aki. Will Quarto get pulled in from your COPR automatically as well or do we need to specifically install it before/after? Also is it worth updating the "add ons" section at https://cran.r-project.org/bin/linux/fedora/ as well? Tim On 24/09/2024 12:51, I?aki Ucar wrote: > Dear all, > > With the latest release of RStudio last week (v2024.09.0+375), support

On Wed, 15 Jul 2020 at 10:47, Tim Taylor <tim.taylor at hiddenelephants.co.uk> wrote: > > I've just updated to R 4.0.2 but am unsure how to get packages from the > COPR repository to update to those built under the new version of R. > FI - I'm not currently using CoprManager just trying to update/install from > terminal. The Copr repo has been rebuilt under R 4.0.2.

Dear all, With the latest release of RStudio last week (v2024.09.0+375), support for Qt builds has been removed. This means that we can no longer maintain RStudio packages in the official Fedora repositories, because the necessary Electron component is missing. RStudio is supported in the official repositories up to v2024.04.2+764 and F40, and has been retired from newer branches. Consequently,

Hi, After returning home from holiday I tried to update my Fedora installation with the command 'sudo dnf update -y'. This command now terminates with the following error: error: Verifying a signature using certificate 3124D2EF76DA4D972F6BE4AC9D60CBB71A3B4456 (iucar_cran (None) <iucar#cran at copr.fedorahosted.org>): 1. Certificiate 9D60CBB71A3B4456 invalid: certificate is

On Sat, 31 Oct 2020 at 20:52, H <agents at meddatainc.com> wrote: > > Understood. Since I am running CentOS 7, I guess I could create a CentOS 8 docker container and install R in that? I am not planning to upgrade the system to CentOS 8. Of course, you can do that. With podman it's even easier. But then I'd use Fedora as the base image instead, because you'll enjoy binary

On Tue, 2020-05-05 at 19:25 -0500, Robert G (Doc) Savage via CentOS wrote: > > I'm about ready to run "dnf erase *mate*" and try re-installing MATE > from scratch from the GNOME3 desktop. Is that possible without > ripping > the heart out of C8 by deleting other critical packages? I've attached a capture of "dnf erase *mate*" that shows the 104 packages

Hi all, Three months ago, I wrote to Martyn Plummer (to his Warwick email) and offered my help to maintain and modernize this [1] rather updated README, but received no response. Does anyone know how to reach him, or maybe I should contact CRAN directly? [1] https://cran.r-project.org/bin/linux/redhat/README Regards, -- I?aki ?car

On Tue, 7 Jul 2020 at 15:58, Jos? Ab?lio Matos <jamatos at fc.up.pt> wrote: > > On Tuesday, 7 July 2020 11.44.48 WEST I?aki Ucar wrote: > > Try with the CLI (see "man bodhi"): > > > > $ bodhi updates edit <update> --addbuilds <builds> > > I found that the best call in this case is instead of --addbuilds to use > --from-tag since then

Question for the list: I have a small, aircooled pc server, which is running fine, but the log gets filled with a series of messages saying the package, and each of 8 cpus is throttled because of thermal issues. Then, within the same second according to the timestamps, it reports everything is OK and throttling is off. This happens once every minute. In reality, when I try performance

Hi:please i am working on fedora 31, then i installed R (language), and i want to install a R package ("DMwR"), but i get these warning messages ...: The downloaded source packages are in ?? ??/tmp/RtmpCBUyte/downloaded_packages? Updating HTML index of packages in '.Library' Making 'packages.html' ... done Warning messages: 1: In install.packages("DMwR") :

Thanks, I?aki, for your answer. Yes, I do have a GPU: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 560.35.03 And no progress: $ rstudio GSK_RENDERER=ngl [18088:1103/205442.538796:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)].

BTW, meanwhile, you can install rstudio-server and use RStudio in your browser at http://localhost:8787 I?aki On Sun, 3 Nov 2024 at 22:10, I?aki Ucar <iucar at fedoraproject.org> wrote: > It is unlikely to be a packaging issue. I suggest you open a bug report > here: https://github.com/rstudio/rstudio/issues. > > I?aki > > On Sun, 3 Nov 2024 at 22:04, Paul Smith

It is unlikely to be a packaging issue. I suggest you open a bug report here: https://github.com/rstudio/rstudio/issues. I?aki On Sun, 3 Nov 2024 at 22:04, Paul Smith <phhs80 at gmail.com> wrote: > Thanks, but unfortunately no progress: > > $ GSK_RENDERER=ngl rstudio > > [19496:1103/210330.025303:ERROR:gl_factory.cc(120)] Requested GL > implementation

Thanks, but unfortunately no progress: $ GSK_RENDERER=ngl rstudio [19496:1103/210330.025303:ERROR:gl_factory.cc(120)] Requested GL implementation (gl=none,angle=none) not found in allowed implementations: [(gl=egl-angle,angle=default),(gl=egl-gles2,angle=none)]. [19496:1103/210330.028349:ERROR:viz_main_impl.cc(198)] Exiting GPU process due to errors during initialization Segmentation fault (core

On Tue, 5 May 2020 05:30:26 -0400 Eddie O'Connor wrote: > Are there .conf files for the desktop?....what about logs?....something's > got to be amiss somewhere....and Linux always complains when it is.....in > logs. Just wondering out loud... What happens if he sets up a new user? Does the desktop work then? -- Can we uninstall 2020 and install it again? This one has a virus.

Let's try another thing. Do you use Gnome? Any kind of hardware acceleration for graphics (NVIDIA...)? If so, you could try launching RStudio with GSK_RENDERER=ngl to see if it makes any difference. I?aki On Sun, 3 Nov 2024 at 01:44, Paul Smith <phhs80 at gmail.com> wrote: > Thanks, I?aki, for your answer. Unfortunately, that package was > already installed on my machine: >

Hi all, The admin from our setup created a script that should help you reproduce our problem (see below). Of course, it may be that it is not an RPM-related issue, but we hope you will have an idea on how to solve the issue all the same. # 1. Prepare VM and set up Samba - install Fedora 38 Workstation (Fedora-Workstation-Live-x86_64-38-1.6.iso). Username: 'user' - disable SELinux (edit

Thanks again, unfortunately it still fails when mounting the drive on a windows machine (even using nolease) on our end. We will prepare a fully reproducible example using a virtual machine. This could take us a day or two. ++ On Tue, 13 Jun 2023 at 11:05, I?aki Ucar <iucar at fedoraproject.org> wrote: > On Tue, 13 Jun 2023 at 10:35, Alexandre Courtiol > <alexandre.courtiol at

Please, see spot's comment in the BZ I linked in my previous comment. The thing is not that it can't be done (you could install a newer devtoolset, v8 or v9, build R and use it), the thing is that it cannot be distributed in EPEL, because we're allowed to build against a devtoolset, but not depend on it, so the distribution would be broken (you could not install packages unless you

On Wed, Jan 15, 2020 at 07:04:06PM +0100, Matthias Tafelmeier wrote: > > Hello, > > ran into oddish glitch on fedora 30 cloud image with tooling based on > libvirt-python onpython3.7. *qemu-img *is installed though. Could anyone > have a look. I don't see qemu-img installed there. You've requested 'qemu-kvm' and 'qemu-system-x86' which provide the