Pkg Install Root-repo
Kerby Reynolds
Termux does not support use of packages from the Debian, Ubuntu and other Linux distribution repositories. For this reason do not attempt put these ones into your sources.list or manually installing their .deb files. See Differences from Linux to learn why.
Packages for our official repositories are built from scripts located in github.com/termux/ and are maintained and signed by member of the Termux developer team. Public keys for verifying signatures are provided in package termux-keyring. For more information about how the repositories are signed, see termux-keyring.
You can create own repository by using termux-apt-repo from the command line and Github Pages as hosting. Be aware that Github has a strict limit of 100 MB per file and if your repository exceeds total size of 1 GB, you might receive a polite email from GitHub Support requesting that you reduce the size of the repository. So if you have really big packages you may want to use a different hostings. Choose hostings according to filetypes, for example, videos can be hosted at or similar.
Packages can be requested at -packages/issues. Note that your opened issue with request can be moved to another repository, like termux-root-packages or x11-packages if it is not suitable for the main repository.
Actually, you probably want to version control configuration files in /etc/ (you don't care about the entries of the root directory /, notably directories like proc or usr or bin in /) so you may want to install the etckeeper package
If you are going to store sensitive stuff (like /etc/shadow) in thegit repo, you should make sure it's not readable by all users, since bydefault the objects will have the permission 444 and directories willhave the permission 0755. You can change the permission of .git to700 or put it in /root
Another problem is that git doesn't store file permissions like the filesystem, and it doesn't store extended attributes. For files, git onlystores whether they are executable. So if you want to restore a deletedfile, its owner and group will be root (if you do it as root), and itspermission will be 644 or 755. It may be problematic for services'configuration files whose owner is not root.
In all cases, make sure to always use the most recent ROOT release possible to get the latest bug fixes, features and quick user support.The latest stable ROOT release is6.32.02 (about ROOT versioning scheme).
To avoid having to source thisroot.sh every time one needs to use ROOT, it is typical to add the command to.bashrc, .profile or analogous configuration files.Note, however, that sourcing thisroot.sh might interfere with ROOT versions installed with different methods.
To use ROOT from Python, the Snap package bundles its own Python 3.8 interpreterthat knows where to find the ROOT libraries. This is done to avoid interferencewith other system packages. You should use pyroot rather than python to makeuse of the PyROOT features with the Snap package:
More typically, however, users will want more than just the base package. The full list of components can be seen at by clicking in one of the offered versions.To install ROOT with support for python and notebooks, for example, run
LCG views are available for CentOS 7, RHEL 9 (which also covers the binary-compatible AlmaLinux 9), and the latest macOS and Ubuntu releases.For example, on CERN LXPLUS (AlmaLinux 9), you can set up a full environment that contains ROOT 6.30.02 with:
Note that certain features (e.g. multi-threading capabilities) are not available on lxplus.cern.ch (or, equivalently, lxplus7.cern.ch) due to incompatible versions of certain ROOT dependencies on CentOS7. You can use lxplus8.cern.ch to get access to CentOS8, where this limitation is not present.
In case no other installation method is available, or if you want full control over the options ROOT is built with,it is possible to compile ROOT from source. See Building ROOT from source for detailed instructions.
Hi Jean-Marc, thank you for the response! Is there documentation somewhere onto how this extension.json should be formatted? I can find examples in Github that seem correct, but just curious if there are other parameters in extension.json that I can tweak.
I think he is asking if he is able to clone the repository to a network or local drive, and use the file system path for the source location instead of a URL for Github, since this would eliminate the requirement to distribute a PAT in plain text files to users without Github access.
I was trying to do the same thing a couple of days ago, and I was not able to specify a folder path for the repository, and had to use Gitea to have a URL that I could then use for installation and ribbon reloads.
I have a root repo and a folder inside that repo called extensions. So it looks like the command for extend ui extensionName -github URL- assumes the extension.tab is at the root (but in some cases it might not be). I think this is what jpitts was asking too - how do you specify a file path within the private github repo.
I was trying to do the same thing a couple of days ago, and I was not able to specify a folder path for the repository, and had to use Gitea to have a URL that I could then use for installation and ribbon reloads.
I think the command pyrevit extensions paths (add forget) [--log=] might be for local and not for Github but I could be wrong here.
Elk Stack newbie here... When I install Kibana on Centos 8 I get an error on install saying that I should not run ./bin/kibana as root. Do I need to create a specific user called "Kibana" instead of running as sudo? When I run it as current user "elkstackadmin" I get errors that Babel could not write cache to file /kibana-7.6.0-linux-x86_64/optimize/.babel_register_cache.json due to a permission issue. Cache is disabled...
I rebuilt the server last night but passed out before I coulds try this. Sine the elastic site isn't very clear on which way to install/configure should I use the (Add repo to yum.repos.d or download the rpm method). Which is best practice?
Thanks Mark, I just wasn't sure if one way was better/standard over the other. I'm a newbie to ELK stack. I will try the method of manually adding the repos by creating a kibana user and installing under the kibana user.
Ok that makes sense because now I finally got Kibana loaded on firefox. Of course this is the local server to where elasticsearch, kibanan, and now metricbeats is installed. Gotta install logstash tonight or tomorrow.
Thank you for all the help. I was able to get this up and running finally. However, I'm getting high CPU from Java like 275% CPU when I run top. Not sure what could be causing it as the only thing that required Java was logstash and the only thing I have reporting from the ELK stack is the ELK stack server itself. Thoughts on what would be causing this and how to fix? Also should I be concerned?
yum --installroot= will look for packages repositories only in myroot/etc/yum.repos.d or it will only/also look in /etc/yum/repos.d? RHEL 6 is having the latter behavior. If that is expected behavior, what is the best method to achieve what I need?
This is trying to add a repository called "online-repo" in your pacman.conf and download from it which is not a thing. If you didn't change anything you are probably not actually trying to install Arch. If you did change that, then I'm not quite sure what your goal was, did you try to include a local/personal repository?
How did you create the ISO/where did you download it from? Did you take someone's USB stick? That would be quite the issue if it was in the ISO, but it's at least not present in the latest ISO, so this is something that's must have happened on your installation setup if you haven't consciously changed something here.
This is an ISO someone else made that included a driver for my wireless card so I didn't have to use a wired connection. I apologize for not mentioning this in the original post. I was under the impression that official-repo was an official repository.
If this doesn't help either you should probably ask your friend for help, as this falls squarely into unsupported 3rd party guide territory, because there have been manipulations on the ISO that deviate from what we expect and you do not know what exactly has been done, which makes this bordeline impossible to properly help you.
Changing the keyserver fixed the error. I think I'll be good to go now. If I encounter any other problems I'll use a different ISO or ask the person who made it. Thanks for the help and sorry for the nooby questions
When you install a dependency in your repository, you should install it directly in the package that uses it. The package's package.json will have every dependency that the package needs. This is true for both external and internal dependencies.
4a15465005