Re: Install deb or rpm package (SOLVED) pacman needs.pkg.tar.gz files, not just.tar.gz. I think you can use rpmextract for rpm's, not sure of an equivalent for deb but if all else fails, you can try using alien to convert from deb to rpm and then rpm extract. For the strength of the pack is the wolf, and the strength of the wolf is the pack. In general, the order of operations should be: Check if packages is in repos. Check if package is in AUR. Check if package is available as flatpak. Check if package is available as snap. Check if the source code is available. If yes, write a PKGBUILD and install it with pacman. Convert package from debian/rpm package.
How to Check an RPM Signature Package. Always check the PGP signature of.
Maintaining Software Using RPM (Red Hat Package Manager)
RPM is a powerful software manager which can be used to build, install, query, verify, update, and uninstall individual software packages. An RPM package consists of an archive of files, and package information such as name, version, a description and information about dependencies on other RPM packages.
RPM is more than a Red Hat specific tool. Many other modern distributions, such as Ubuntu and SuSE, use RPM too. Benefits of using RPM include:
- Simplified software distribution, installation, upgrading and removal
- Guarantees that:
- prerequisite software is installed on system.
- versions of prerequisite software stay compatible.
- locally-modified configuration files are not clobbed when the RPM is updated.
- locally-modified configuration files are saved with an “.rpmsave” suffix if the package is later deleted.
- Allows certification that installed software has not been altered, modified, corrupted, or changed in any way.
RPM keeps information about installed packages under the “/var/lib/rpm” directory.
Components of the RPM tool are:
- A custom database containing information about all software installed on the system, collected from the individual RPMs.
- A “/bin/rpm” executable.
- Internet-accessible repositories of available RPM packages.
Types of RPM Packages
RPM packages come in two categories: source and binary.
A source RPM can always be recognized because the filename ends with the string “.src.rpm“. In a source RPM are not only the original program source code files but scripts that allow the code to be recompiled automatically, to be installed automatically, and to be removed automatically. There are no end-user executable files in a source RPM. Usually, only developers are interested in a source RPM.
A binary RPM contains the end-user compoments of an RPM. Binary RPM filenames identify the host architecture for the contents. For example, the binary RPM file:
It contains files only usable on a 64-bit Intel X86 architecture CPU. Other common architecture values include “i386” for 32-bit Intel hosts. Some binary RPM’s may be installed on any CPU architecture because their files will work on any host; an example of these “.noarch.rpm” packages is the “tzdata” RPM which contains information about world timezones. To update your system with the latest version of a package, you will need the most recent binary RPM for it.
RPM Naming Scheme
Each RPM package is contained in a single file. The filename has several fields to fully identify the contents of the package. While the RPM tools themselves do not rely upon the filename itself, you should understand the filename convention to help you identify or download the proper package. Here is an example RPM filename:
This RPM is for the BASH shell (“/bin/bash”). The filename is composed of several parts:
where:
- [name] is the name of the program or package. The [name] is usually assigned by the program’s author. In our example, the developers decided to name their product “bash” for reasons that seemed amusing to them.
- version] identifies which edition of the software this RPM contains. The [version] number is assigned by the program’s author. Using the
number allows one to determine which version of the author’s sources were used to generate the RPM. - [release] provides the edition number of the RPM file itself and not the version of the author’s source files. An updated RPM may be issued to supply a patched version of the author’s original software. The patch need not have come from the original developer, so the RPM [release] gets incremented instead of the [version].
- [arch] describes the contents of the RPM and tells whether this file contains the product source (a “.src.rpm”), architecture-independent files (a “.noarch.rpm”), or files which may only be installed on a particular host type (a “.sh.rpm” will work only on a STRONGHOLD embedded processor).
Note: The [version] is controlled by the original author and the [release] is controlled by whomever constructed the RPM.
Understanding RPM Versions
The RPM [version] and [release] fields are not always strictly numeric and may contain other characters besides ordinary digits. It is common to see both a version “10” and a “10a” version of the same package. Sometimes picking the most recent version can be tricky. Here is how RPM itself compares version and release numbers internally:
1. Remove the [name] prefix and the “.[arch].rpm” suffix. For example,:
“bash-3.1-16.1.x86_64.rpm” becomes “3.1-16.1” and “bash-3.1-16.5a.1.x86_64.rpm” becomes “3.1-16.5a.1”
“bash-3.1-16.1.x86_64.rpm” becomes “3.1-16.1” and “bash-3.1-16.5a.1.x86_64.rpm” becomes “3.1-16.5a.1”
2. Compare the remaining strings character-by-character, left-to-right until a digit is encountered. If the characters differ, whichever character comes later in the collating sequence is the more recent RPM.
![How To Install Rpm Package On Arch Linux How To Install Rpm Package On Arch Linux](https://averagelinuxuser.com/assets/images/posts/2020-04-26-ubuntu-vs-arch-linux/ubuntu_gnome_initial_setup5.png)
![How How](https://www.lifewire.com/thmb/Ab8csvhuQ-3_-v93du6m7h2G9q0=/1283x687/filters:no_upscale():max_bytes(150000):strip_icc()/pacman-explicitly-installed-21c18159b52e4ae2a975734a4763d017.jpg)
How To Install Rpm Package On Arch Linux Operating System
3. When a digit is encountered, convert the entire sequence of digits into a single binary number. In our example, the two characters “16” are combined into a value of sixteen (16). The resulting binary values are compared and the greater value is the more recent RPM. Thus, an RPM with a [version] of “0010” is more recent than one with a [version] of “9”.
Steps 2 and 3 are repeated as necessary until a difference occurs.
Installing and Removing Files
Note: Usually only one or of an RPM may be installed at once.
Later versions are usually installed using the “-U” (update) RPM function instead of the “-i” RPM function. Common exceptions to the only-one RPM rule are the kernel RPM’s. A system commonly has several versions of kernels installed; RPM has a list of which RPM’s may have multiple versions installed. To delete one version when several are installed, you must fully-specify the package name and version.
On the x86_64 architecture, it is common to have both the 32-bit “.i386” and the 64-bit “.x86_64” RPM packages installed tosupport both 32-bit and 64-bit applications. Normally, RPM does not display the architecture of a package on a query but you can manually display it.
Installation and Removal
Common Options
Output: -v (verbose – file name), -h (hash)
Preconditions: –nodeps, –replacefiles, –force (BE CAREFUL HERE !!!)
Relocating: –excludepath, –prefix, –relocate, –badreloc, –root
URL Support: ftp, http
Output: -v (verbose – file name), -h (hash)
Preconditions: –nodeps, –replacefiles, –force (BE CAREFUL HERE !!!)
Relocating: –excludepath, –prefix, –relocate, –badreloc, –root
URL Support: ftp, http
Examples:
Hint: Never, ever, use the “-U” option to install a new kernel RPM. The “-U” update function first deletes the current RPM from the system and then attempts to install the new RPM. Any problem that prevents the new RPM from installing will leave the system unbootable. This is not what you want, so always use the “-i” switch to install a kernel RPM.
Queries (Packages and/or Information)
Use a query for information about installed packages. You may query against all installed packages, or a single installed package. You may also find out which RPM supplies a particular file.
Information
default (package name)
-i: general information
-l: file list
default (package name)
-i: general information
-l: file list
Arch Linux Deb Or Rpm
Examples:
Hint: When searching for a particular RPM package when the exact name is not known, a command pipeline such as:
is commonly used. Later versions of the RPM tool allow this to be succinctly done as:
Queries – Verification (Files)
The RPM database contains many attributes about each and every file installed by an RPM. You may verify the current status of the file against the information cataloged by RPM when the package was installed.
Note: Many Linux distributions include a “prelink” RPM that attempts to lessen the time needed to start an application using a shared library (most applications use at least one shared library and potentially dozens) by adding special information directly into an application’s program file.
Adding this information does make applications start faster, but the file changes invalidate most of the file attributes in the RPM database, such as the last file modification date, file size, and the file’s MD5 checksum.
Queries – Verification (Packages)
Examples:
Repair the RPM database
The RPM tool uses its own custom database implementation to contain its information. Sometimes that database can get corrupted; symptoms include claims that an installed RPM package is missing; or attempts to update an RPM simply hang. If your RPM database is hung or corrupted you can try to repair it with these commands. This process is not guaranteed to work.
You must be logged in with superuser privilege (aka “root”) for these steps. The commands may be copied and pasted directly into a root terminal window.
1. Make sure there are no RPM processes left running on your system. Use the ps command to identify them. Use the kill command to terminate any “rpm” processes you find; a “kill -9” may be necessary.
2. Delete the lock files that RPM uses:
3. If you were experiencing a hanging “rpm” command, try it again. If it works, you are finished. If not, perform Step #1 and #2 again. Then proceed to the next step.
4. Make a backup of your RPM database:
5. Rebuild your RPM database:
6. Retry your failed RPM command.
This section describes how to install Privilege Management for Unix and Linux using a package installer for Red Hat Enterprise Linux (RHEL) 4 or 5 on an x86, x86_64, ia64, or S/390 computer. Use the Linux package installation if you want to install Privilege Management for Unix and Linux using the Linux RPM package manager.
The Privilege Management for Unix and Linux Linux package installer that is described here is not compatible with the Privilege ManagementPrivilege Management v5.x packages. You must remove BeyondTrustPrivilege Management packages v5.x before installing Privilege Management for Unix and Linux Linux packages.
Prerequisites
To use the Linux package installer, you must have the following:
- Package tarball file for the appropriate Privilege Management for Unix and Linux flavor
For the Privilege Management for Unix and Linux Linux package installer, the tarball files are cumulative. That is, an update tarball file contains a complete Privilege Management for Unix and Linux installation. It is not necessary to install a baseline version of Privilege Management for Unix and Linux before installing an upgrade.
- Root access or superuser privileges
- RPM Package Manager (rpm) v4.4 or later
The Privilege Management for Unix and Linux Linux package installer does not support prefix or suffix installations.
Plan Your Installation
When preparing to use the Privilege Management for Unix and Linux package installer, you should be familiar with the following concepts and restrictions:
Component packages: A Privilege Management for Unix and Linux component package is an RPM package manager (.rpm) file that installs a part of the Privilege Management for Unix and Linux application. The Privilege Management for Unix and Linux component packages are listed below with the format powerbroker-component-v.v.r.bb-pv.arch.rpm, where:
- component = Privilege Management component package name
- v = major version v = minor version r = release
- bb = build
- pv = version number of the package
- arch = architecture (for example, i386)
Component Package | Description |
---|---|
powerbroker-loghost-v.v.r.bb-pv.arch.rpm | Contains log host, pbsync, and pbsyncd. |
powerbroker-shlibs-v.v.r.bb-pv.arch.rpm | Contains shared libraries. |
powerbroker-pbrest-v.v.r.bb-pv.arch.rpm | Contains REST API files. |
powerbroker-rnssvr-v.v.r.bb-pv.arch.rpm | Contains Registry Name Service files. |
powerbroker-licsvr-v.v.r.bb-pv.arch.rpm | Contains license server files. |
powerbroker-master-v.v.r.bb-pv.arch.rpm | Contains policy server host, pbsync, and pbsyncd. |
powerbroker-submithost-v.v.r.bb-pv.arch.rpm | Contains submit host and Privilege Management for Unix and Linux shells. |
powerbroker-runhost-v.v.r.bb-pv.arch.rpm | Contains run host and Privilege Management for Unix and Linux utilities. |
powerbroker-guihost-v.v.r.bb-pv.arch.rpm | Contains GUI host and secure GUI host. |
Which component packages are required depends on the type of Privilege Management for Unix and Linux host you create, such as policy server host, submit host, and so on. You can select the types of Privilege Management for Unix and Linux hosts in the pbinstall installation menu, as shown in the following table. For readability the ending of each component in the table (-v.v.r.bb-pv.arch.rpm) is removed.
Menu Selection | Required Components (-v.v.r.bb-pv.arch.rpm) |
Install everything here (demo mode)? = Yes | powerbroker-master powerbroker-runhost powerbroker-submithost powerbroker-loghost powerbroker-guihost powerbroker-shlibs |
Install Master Host? = Yes | powerbroker-master |
Install Run Host? = Yes | powerbroker-runhost |
Install Submit Host? = Yes | powerbroker-submithost |
Install Log Host? = Yes | powerbroker-loghost |
Install GUI Host? = Yes | powerbroker-guihost |
Install Secure GUI Host? = Yes | powerbroker-guihost |
Install BeyondTrust built-in third-party libraries? = Yes | powerbroker-shlibs |
Install Registry Name Services Server? [yes] | powerbroker-rnssvr |
Install License Server? [yes] | powerbroker-licsvr |
Configuration package: RPM package that is used to install the following files:
- pb.settings: Hardcoded target location /etc/pb.settings
- pb.cfg: Hardcoded target location /etc/pb.cfg
- All the encryption keyfiles defined for networkencryption, eventlogencryption, iologencryption, reportencryption, policyencryption, and restkeyencryption
- By default, two key files are created: pb.key and pb.rest.key
- The sysadmin can define multiple encryption with different keyfiles in locations other than /etc. To upgrade and retain settings on the target machine, view all encryption settings in /etc/pb.settings and copy the files to the settings_files directory before running 'pbinstall -z' and pbcreate*cfgpkg
- pb.conf (for policy server hosts)
- Man pages for the pbinstall and pbcreatelincfgpkg programs
The Privilege Management for Unix and Linux configuration package is created by the pbcreatelincfgpkg program. The component packages must be installed before you install the configuration package.
Package name: Name of the package as stored in the RPM package manager database. For Privilege Management for Unix and Linux package installations, this name is the same as the package file name without the .arch.rpm extension.
Relocated base directory: The directory where the Privilege Management for Unix and Linux binary files and log files are installed. You can choose an alternative directory in which to install these files.
pbinstall program: To create the Privilege Management for Unix and Linux settings files, you use the pbinstall program with the -z (settings only) option. pbinstall -z only creates the settings files, and is incompatible with the following command line options:
Options Incompatible with pbinstall -z | Description |
-b | Runs pbinstall in batch mode. |
-c | Skip the steps that process or update the Privilege Management for Unix and Linux settings file. |
-e | Runs install script automatically by bypassing the menu step of pbinstall. |
-i | Ignores previous pb.settings and pb.cfg files. |
-p | Sets the pb installation prefix. |
-s | Sets the pb installation suffix. |
-u | Installs the utility programs. |
-x | Creates a log synchronization host (installs pbsyncd). |
When you execute pbinstall with the -z option, you can see two menu items that are not otherwise available:
- Enter existing pb.settings path: This enables you to specify your own pb.settings file. pbinstall reads this settings file and populates the remaining menu choices. You can override some menu choices. If set to none, then pbinstall does not read a settings file. The remaining menu choices are populated with default values.
- Enter directory path for settings file creation: This enables you to specify an alternative output directory for the settings files. The default directory is /unzip-dir/powerbroker/v<flavor>/<flavor>install/settings_files, where unzip-dir is the directory where the package tarball file was unzipped.
The behavior of pbinstall -z depends on whether certain additional command line options are specified:
- If no other command line options are specified, pbinstall initially presents a short version of the installation menu. Depending on the choices you make in these items, further menu items become available.
- If command line options -g, -l, -m, -o, -r, or -w are specified, pbinstall presents an expanded version of the installation menu that reflects the host types that you are configuring.
When running pbinstall with the -z option, the following menu items are preprogrammed and cannot be changed:
- Install man pages?
- Privilege Management daemon location
- Administration programs location
- User programs location
- GUI library directory
- Policy include (sub) file directory
- User man page location
- Admin man page location
- Policy filename
- BeyondTrust built-in third-party library directory
In addition, the values of the following menu items determine the values of other menu items:
Options Preset When Running pbinstall -z | |
---|---|
Setting this menu option to Yes | Sets these values to Yes |
Install Master Host? | Install Synchronization? Synchronization can be initiated from this host? |
Install Run Host? | Install Utilities? |
Install Submit Host? | Install PBSSH? Install pbksh? Install pbsh? Will this host use a Log Host? |
Install Log Host? | Install Synchronization? Synchronization can be initiated from this host? |
If you plan to use the package installer to install Privilege Management for Unix and Linux on a computer that already has an interactive Privilege Management for Unix and Linux installation on it, see Interactive Versus Packaged Installation for additional considerations.
If you plan to use Registry Name Service and are running pbinstall -z on a client host (non-primary server), you must perform client registration. This is necessary to properly set up the registry name service database. Client registration also requires that you collect from the Privilege Management for Unix and Linux primary server the following information:
- REST Application ID
- REST Application Key
- Primary server network name or IP address
- Primary License Server REST TCP/IP port
- Registration Client Profile name
Registering client with Primary RNS: If Registry Name Services is enabled for Privilege Management for Unix and Linux, each client host (after the first server installation) needs to be registered with the Primary Registry Name Server. When using package installers on a target host, a post-install configuration script (/opt/pbul/scripts/pbrnscfg.sh) is provided to be manually executed on that host to properly register it. This post-install configuration script asks for information about the Primary Registry Name Server, including the Application ID (appid), Application Key (appkey), address/domain name, and the REST TCP/IP port number. This is the same information provided during the client registration part of a pbinstall -z install which generates the settings file.
If you prefer a more convenient method of registering RNS clients where the post-install configuration script is non-interactive, Privilege Management for Unix and Linux can save the relevant information in a hidden file during the settings-only run of pbinstall, bundle it with the configuration package, and automatically apply it to the target host when that package is installed. However, understand that this is not secure, but is available if the security-convenience trade-off is acceptable. To enable this, refer to the question regarding post-install configuration script displayed when running pbinstall -z.
For more information, please see the following:
- On pbinstall command-line options, Installation Programs
Overview of Steps
Use of the Linux package installer involves the following steps:
- Unpack the Privilege Management for Unix and Linux package tarball file.
- Use the pbinstall program to create Privilege Management for Unix and Linux settings files.
- Use the pbcreatelincfgpkg program to create the Privilege Management for Unix and Linux configuration package.
- Perform a package installation using the Linux rpm command for any required components.
- Perform a package installation using the Linux rpm command for the Privilege Management for Unix and Linux configuration package.
- If Registry Name Service is enabled and installing on a non-primary servery, run /opt/pbul/scripts/pbrnscfg.sh to register the host.
For additional details on the above steps, please see Installation Procedure.