RVM
flatpak
Our great sponsors
RVM | flatpak | |
---|---|---|
42 | 431 | |
5,046 | 4,013 | |
0.4% | 1.3% | |
7.2 | 9.0 | |
8 days ago | 4 days ago | |
Shell | C | |
GNU General Public License v3.0 or later | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
RVM
-
Ruby version
rvm (probably the most used manager)
-
Problems starting msfdb init
One suggestion would be to setup your install based on a development environment using git and a Ruby version manager like rvm or rbenv to allows you to setup a user controlled gemset and execution path.
-
Where is the best place to get specific help with errors during a Ruby install?
If you're using rvm, then the rvm repository.
-
Codespaces .devcontainer fails for Android SDK
2023-04-30 03:17:03.814Z: #20 55.72 #20 55.72 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. #20 55.72 #20 55.84 #20 55.84 Warning: PATH set to RVM ruby but GEM_HOME and/or GEM_PATH not set, see: #20 55.84 https://github.com/rvm/rvm/issues/3212 #20 55.84 2023-04-30 03:17:05.920Z: #20 57.89 ./install.sh: 32: Syntax error: "(" unexpected #20 57.89 ERROR: Feature "Android SDK" (ghcr.io/jarrodcolburn/features/android-sdk) failed to install! 2023-04-30 03:17:06.624Z: #20 ERROR: executor failed running [/bin/sh -c cp -ar /tmp/build-features-src/android-sdk_5 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/android-sdk_5 && cd /tmp/dev-container-features/android-sdk_5 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/android-sdk_5]: exit code: 2 2023-04-30 03:17:06.630Z: ------ > [dev_containers_target_stage 8/9] RUN --mount=type=bind,from=dev_containers_feature_content_source,source=android-sdk_5,target=/tmp/build-features-src/android-sdk_5 cp -ar /tmp/build-features-src/android-sdk_5 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/android-sdk_5 && cd /tmp/dev-container-features/android-sdk_5 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/android-sdk_5: #20 55.60 done. #20 55.72 #20 55.72 WARNING: apt does not have a stable CLI interface. Use with caution in scripts. #20 55.72 #20 55.84 #20 55.84 Warning: PATH set to RVM ruby but GEM_HOME and/or GEM_PATH not set, see: #20 55.84 https://github.com/rvm/rvm/issues/3212 #20 55.84 #20 57.89 ./install.sh: 32: Syntax error: "(" unexpected #20 57.89 ERROR: Feature "Android SDK" (ghcr.io/jarrodcolburn/features/android-sdk) failed to install! ------ 2023-04-30 03:17:06.633Z: ERROR: failed to solve: executor failed running [/bin/sh -c cp -ar /tmp/build-features-src/android-sdk_5 /tmp/dev-container-features && chmod -R 0755 /tmp/dev-container-features/android-sdk_5 && cd /tmp/dev-container-features/android-sdk_5 && chmod +x ./devcontainer-features-install.sh && ./devcontainer-features-install.sh && rm -rf /tmp/dev-container-features/android-sdk_5]: exit code: 2 2023-04-30 03:17:06.659Z: Stop: Run: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder 2023-04-30 03:17:06.664Z: {"outcome":"error","message":"Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder","description":"An error occurred setting up the container."} 2023-04-30 03:17:06.671Z: Error: Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder 2023-04-30 03:17:06.675Z: at wse (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1916:3264) 2023-04-30 03:17:06.677Z: at K7 (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1916:3200) 2023-04-30 03:17:06.679Z: at processTicksAndRejections (internal/process/task_queues.js:95:5) 2023-04-30 03:17:06.680Z: at async Hse (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1931:2626) 2023-04-30 03:17:06.695Z: at async Ch (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:1931:3741) 2023-04-30 03:17:06.706Z: at async cae (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2059:17376) 2023-04-30 03:17:06.715Z: at async uae (/usr/lib/node_modules/@devcontainers/cli/dist/spec-node/devContainersSpecCLI.js:2059:17117) 2023-04-30 03:17:06.717Z: devcontainer process exited with exit code 1 ====================================== ERROR ==================================== 2023-04-30 03:17:06.724Z: Failed to create container. ================================================================================= 2023-04-30 03:17:06.726Z: Error: Command failed: docker buildx build --load --build-context dev_containers_feature_content_source=/tmp/devcontainercli-root/container-features/0.37.0-1682824276795 --build-arg _DEV_CONTAINERS_BASE_IMAGE=mcr.microsoft.com/devcontainers/universal:2 --build-arg _DEV_CONTAINERS_IMAGE_USER=root --build-arg _DEV_CONTAINERS_FEATURE_CONTENT_SOURCE=dev_container_feature_content_temp --target dev_containers_target_stage -t vsc-egnore-7f7c330024417fc1c88d19e7d01b832cf3eafa6230f5d96d870e989a2113e130-features -f /tmp/devcontainercli-root/container-features/0.37.0-1682824276795/Dockerfile.extended /var/lib/docker/codespacemount/.persistedshare/empty-folder 2023-04-30 03:17:06.729Z: Error Code: 1302 ====================================== ERROR ==================================== 2023-04-30 03:17:06.731Z: Container creation failed. ================================================================================= 2023-04-30 03:17:06.741Z: ===================================== WARNING =================================== 2023-04-30 03:17:06.758Z: Creating recovery container. =================================================================================
-
Is there any reason to use Ruby 2.7 over Ruby 3.x?
For my local machine, I use RVM (head). Other options are rbenv and asdf.
- I'm at the end of my rope with my MacBook reverting to referencing some Ruby 2.6 version I can't remove because it seems to be built into my operating system...
-
Help in learning Sinatra (Ruby)
You can use tools like rbenv(https://github.com/rbenv/rbenv) and rvm(https://rvm.io/) to be able install and easily switch between different ruby versions
-
.Net dev using rails for side hustle
It depends how you install it. If you install it globally then it will work for all your projects. Are you using rvm for ruby version and gemset management? https://rvm.io/
-
react-native init - failed to build gem native extension - desperately need help
source 'https://rubygems.org'# You may use http://rbenv.org/ or https://rvm.io/ to install and use this versionruby '2.7.5'gem 'cocoapods', '~> 1.11', '>= 1.11.2'
-
Any suggestions on environment options to be able run old Ruby version required by an old app?
So, I try to `rvm install 2.6.1` however i run into this compilation issue for which a correct solution hasn't yet been found, only workarounds, the most hopeful one for me seems to be this one where people report downgrading xcode to v13.6 enables Ruby 2.6 to work. However my OS reports that it's incompatible with the earlier xcode 13.6 version, so I'm now stuck. I'm not prepared to downgrade OS to try to workaround this issue due to other potential conflict and compatibility issues.
flatpak
-
Tools for Linux Distro Hoppers
Hopping from one distro to another with a different package manager might require some time to adapt. Using a package manager that can be installed on most distro is one way to help you get to work faster. Flatpak is one of them; other alternative are Snap, Nix or Homebrew. Flatpak is a good starter, and if you have a bunch of free time, I suggest trying Nix.
-
Podman Desktop 1.6 released: Even more Kubernetes and Containers features
No, it looks like you have to do it on an application basis.
- how strong is the steam (runtime) sandbox for games?
-
Been thinking of switching to linux but I am a noob
Flatpak
- FLaNK Stack Weekly for 20 Nov 2023
-
Flathub – The Linux App Store
> CLI tools do not implement auto-complete themselves. What you are seeing are auto-complete scripts for your shell that make network connections.
nit: This is incorrect. Robust auto-complete scripts call the actual program to provide completions.
That is what Flatpak does. It is Flatpak itself that makes the network connections.
https://github.com/flatpak/flatpak/blob/main/completion/flat...
Not that it would make any differencen if it was implemented in Bash seeing as the Bash script is also provided by Flatpak.
-
Meduza co-founder's phone infected with Pegasus
Not really. Even with modern technologies, the Linux desktop technology stack is very, very far behind when it comes to security.
The Linux kernel itself is a very weak foundation security-wise, the only way Android and ChromeOS get away with it is by using a very small feature set and restricting everything else as much as possible with seccomp, SELinux and heavy sandboxing.
The Linux desktop userland doesn't have meaningful hardening features compared to other platforms (even Windows is ahead, sadly). For example, practically all distros use glibc's memory allocator which has both poor performance and security [1] and their toolchain is based on gcc, with no support for modern compiler security features such as CFI (with the sole exception of Chimera Linux). Not to mention the permission model is completely outdated, like in that xkcd cartoon. Flatpak only mitigates this partially, because the Flatpak sandbox is very weak. The people working on Flatpak are doing their best, but from reading some GitHub issues, it's clear they are badly overworked and not experts on security at all. The person responsible for Flatpak's seccomp sandbox has admitted it isn't even his main responsibility and he doesn't have much knowledge about seccomp and is learning along the way [2]. The Flatpak seccomp filter is based on denylist instead of allowlist, and many dangerous syscalls can't be blocked because many applications rely on it (e.g. Firefox needs ptrace for the crash reporter). You also have to be very careful and use Flatseal (which is not officially supported) to deny permissions such as /home filesystem access, because it lets Flatpak apps override their own permissions by design [3]. And dangerous kernel components like io_uring are exposed [4], while Google disables them on their systems for their exploitation potential.
Here is a more detailed article examining the lack of security of Linux phones in case you're interested: https://madaidans-insecurities.github.io/linux-phones.html
If you want a FOSS-based secure phone, GrapheneOS is the best option.
[1] Check this comment by GrapheneOS founder for some technical details and how it compares to hardened allocators such as Android's Scudo or Graphene's hardened_malloc: https://github.com/NixOS/nixpkgs/issues/90147#issuecomment-6...
[2] https://github.com/flatpak/flatpak/issues/4466#issuecomment-...
-
The technical merits of Wayland are mostly irrelevant
Sensitive features like screenshots, input methods, screen locking and whatnot are behind extensions (or portals). I'm not familiar with the state of GNOME/KDE/Flatpak, but at least on the wlroots side of things it is true that currently these extensions are enabled and accessible by any process that can talk to the Wayland socket (breaking those security benefits, as you say). This is changing with protocols such as security-context that allow a sandbox engine like Flatpak (or your custom scripts) to restrict what features apps can use. (so your browser can't register an input method, or some random app can't lock the screen)
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...
-
Modern CSV version 2 is now available
It shouldn't be too complicated to create a package from the provided tarball.
[1]: https://flatpak.org/
- Flutter 3 on Devuan 4: 始め方
What are some alternatives?
steam-runtime - A runtime environment for Steam applications
firejail - Linux namespaces and seccomp-bpf sandbox
rbenv - Manage your app's Ruby environment
Autodesk-Fusion-360-for-Linux - This is a project, where I give you a way to use Autodesk Fusion 360 on Linux!
distrobox - Use any linux distribution inside your terminal. Enable both backward and forward compatibility with software and freedom to use whatever distribution you’re more comfortable with. Mirror available at: https://gitlab.com/89luca89/distrobox
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
nix-gui - Use NixOS Without Coding
com.valvesoftware.Steam
protontricks - A wrapper that does winetricks things for Proton enabled games, requires Winetricks.
nix - Nix, the purely functional package manager
chruby - Changes the current Ruby
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects