Package Details: rstudio-desktop 2024.09.1.394-1

Git Clone URL: https://aur.archlinux.org/rstudio-desktop.git (read-only, click to copy)
Package Base: rstudio-desktop
Description: A powerful and productive integrated development environment (IDE) for R programming language
Upstream URL: https://github.com/rstudio/rstudio
Licenses: AGPL-3.0-only
Conflicts: rstudio-desktop
Provides: rstudio-desktop
Submitter: None
Maintainer: xiota
Last Packager: xiota
Votes: 73
Popularity: 0.050963
First Submitted: 2011-03-04 15:02 (UTC)
Last Updated: 2024-11-11 05:37 (UTC)

Dependencies (29)

Required by (0)

Sources (3)

Pinned Comments

trap000d commented on 2024-05-16 21:42 (UTC) (edited on 2024-05-28 20:09 (UTC) by trap000d)

A note for users.

This package is quite complex. It MAY not be built because of OTHER issues. I always build, install and test it on at least two different machines. Only after that I would push a new version to AUR.

Please try some generic solutions before reporting of build problems:

1) Update all other packages (sudo pacman -Syu),

2) Clean up yay and/or makepkg caches ('yay -Sc', 'rm -rf /var/tmp/makepkg'),

3) Be sure you've got enough RAM (8 GB or more is highly recommended) and space on disk (at least 3 GB).

4) Is your Internet connection is stable, fast and not blocked somewhere?

trap000d commented on 2022-07-05 20:32 (UTC) (edited on 2022-10-03 06:28 (UTC) by trap000d)

PLEASE READ THIS MESSAGE BEFORE COMPLAINING FOR LIBBOOST

When boost is updated to a new version and you see an error message about missing libboost*.so, you will need to rebuild and reinstall the rstudio-desktop package.

trap000d commented on 2022-02-19 06:20 (UTC) (edited on 2022-02-19 06:21 (UTC) by trap000d)

Build logic is slightly changed due to changes in upstream. As they've introduced new project format (quarto), it contradicted with standard Arch package base. In brief, quarto contains pandoc as part of itself, so it's pretty hard to keep together system pandoc and embedded quarto.

So I've "resolved" it such way: if there is "quarto*" package installed, then rstudio-desktop will pick it up and use. Otherwise (not installed), quarto support in rstudio will be disabled.

'quarto' is added as optional dependency.

Latest Comments

« First ‹ Previous 1 .. 12 13 14 15 16 17 18 19 20 21 22 .. 29 Next › Last »

flying-sheep commented on 2020-06-16 11:53 (UTC)

will. what do you think the pinned comment is for? decoration?

will1942 commented on 2020-06-15 21:49 (UTC)

Hey, the package is broken. I think the is QT related. The interface does not load. It open, but do not load the components

flying-sheep commented on 2020-05-28 11:55 (UTC)

does that work? the archlinux-java script links /usr/lib/jvm/default to some specific java environment, which includes the directories bin, lib, include, jre/bin, and jre/lib.

Seems inadequate to just add something to PATH to mimick this …

mirh commented on 2020-05-27 15:29 (UTC)

Can't you export java-8-openjdk like rstudio-desktop-git has been doing?

flying-sheep commented on 2020-05-27 13:27 (UTC)

@znmeb: This is why there’s a pinned comment. Read it.

znmeb commented on 2020-05-27 08:10 (UTC) (edited on 2020-05-27 08:13 (UTC) by znmeb)

The package builds and installs but the user interface isn't there when I stsrt it up - there's just a menu bar and no panes. :-(

Meanwhile rstudio-desktop-preview-bin works and it's only one patch level behind the release - I can probably hack the PKGBUILD to get the current version.

Also ... how many votes do stable RStudio Desktop and Server need to get moved out of AUR?

daniel_shub commented on 2020-05-26 15:07 (UTC)

@fettouhi while the problem may seem to you to be "that r-assertthat wasn't installed at all and I have tried to install it, remove it & rebuild it and r-cli still won't build", the problem is you are building in a system with an unknown state. If you build in a clean change root, it works. It is really hard to debug problems and that is why it is recommended to build in a clean environment.

dviktor commented on 2020-05-26 14:56 (UTC)

@fettouhi remove r-assertthat and r-cli completely at first. then be sure that you haven't installed them by hand. after that try to clean cache of your AUR helper or just build these packages in clean environment

fettouhi commented on 2020-05-26 14:52 (UTC)

@flying-sheep the problem is that r-assertthat wasn't installed at all and I have tried to install it, remove it & rebuild it and r-cli still won't build.

flying-sheep commented on 2020-05-26 14:02 (UTC) (edited on 2020-05-26 14:06 (UTC) by flying-sheep)

Maybe by uninstalling r-assertthat and rebuilding it. Maybe having assertthat or some other package in your local R library could also give you problems, in which case you could use extra-x86_64-build to build it in a clean chroot. You’ll need to specify all AUR dependencies via -I though:

extra-x86_64-build -- -I /path/to/r-covr-x.y.z.pkg.tar.zst -I ...

Because those are a lot of packages, I wrote build.sh to make it a little easier. You could adapt it to build a package that gives you problems. Finally you could just remove r-testthat from makedeps and install testthat via install.packages, but then you have to build locally and can’t build with extra-x86_64-build.