Software and configuration management using RPM

by Aaron Kili · Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D

		RPM-based integrity 
		checking
YUM
YAST
/my/targetdir
targetdir/var/rpm
rpm -ivh --nodeps --relocate /=/my/targetdir --root=/my/targetdir mypackage.rpm
rpm2cpio
unrpm
------------ [On Debian and Ubuntu] ------------ 
$ sudo apt update 
$ sudo apt install snapd

------------ [On Fedora Linux] ------------
# dnf install snapd                     

------------ [On CentOS and RHEL] ------------
# yum install epel-release 
# yum install snapd             

------------ [On openSUSE - replace openSUSE_Leap_15.0 with the version] ------------
$ sudo zypper addrepo --refresh https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.0 snappy
$ sudo zypper --gpg-auto-import-keys refresh
$ sudo zypper dup --from snappy
$ sudo zypper install snapd

------------ [On Manjaro Linux] ------------
# pacman -S snapd

------------ [On Arch Linux] ------------
# git clone https://aur.archlinux.org/snapd.git
# cd snapd
# makepkg -si

$ sudo systemctl enable --now snapd.socket

$ sudo systemctl is-active snapd.socket
$ sudo systemctl status snapd.socket
$ sudo systemctl is-enabled snapd.socket

$ sudo ln -s /var/lib/snapd/snap /snap

$ snap version

$ snap find "chat servers"
$ snap find "media players"

$ snap info rocketchat-server

$ sudo snap install rocketchat-server

$ sudo snap install --edge rocketchat-server        
$ sudo snap install --beta rocketchat-server
$ sudo snap install --candidate rocketchat-server

$ snap list

$ snap list mailspring
OR
$ snap list --all mailspring

$ sudo snap refresh mailspring
OR
$ sudo snap refresh             #update all snaps on the local system

$ sudo snap revert mailspring

$ snap list --all mailspring

$ sudo snap disable mailspring

$ sudo snap enable mailspring

$ sudo snap remove mailspring

$ sudo snap remove  --revision=482 mailspring

user@ubuntu:~$ sudo apt-add-repository "deb http://APT.spideroak.com/ubuntu-spideroak-hardy/ release restricted"

user@ubuntu:~$ sudo apt-add-repository ppa:gnome-desktop

user@ubuntu:~$ sudo apt-get install kate

user@ubuntu:~$ sudo apt-get remove kate

myrepo/
       /5Server
            .../repodata
            .../noarch
                      ...
            .../i686
                    ...
            .../x86_64
                      ...
       /6Server
               (see above)
               ...

# mkdir -p /var/www/html/myrepo/{5,6}Server

# yum install rpm-build createrepo rpmdevtools

# yum install httpd
# chkconfig httpd on
# system-config-firewall-tui
# service httpd start

# useradd su-rpmdev
# passwd su-rpmdev
# su - su-rpmdev
$ rpmdev-setuptree
$ ln -s /usr/src/redhat ~su-rpmdev/rpmbuild    #symb. link under EL5

$ cd ~su-rpmdev/rpmbuild/SPECS
$ rpmdev-newspec mycompany-ntp
Skeleton specfile (minimal) has been created to "mycompany-ntp.spec".

$ vim mycompany-ntp.spec
Name:           mycompany-ntp
Version:
Release:        1%{?dist}
Summary:

Group:
License:
URL:
Source0:

BuildRequires:
Requires:

%description

%prep
%setup -q

%build
%configure
make %{?_smp_mflags}

%install
rm -rf $RPM_BUILD_ROOT
make install DESTDIR=$RPM_BUILD_ROOT

%clean
rm -rf $RPM_BUILD_ROOT

%files
%defattr(-,root,root,-)
%doc

%changelog

# vi /etc/yum.repos.d/epel.repo
...
[epel-source]
...
enabled=1

ESC ZZ
# yum install yum-utils
# yumdownloader --source nrpe

$ mkdir ~/rpmbuild/SOURCES/mycompany-ntp-1.0
$ cd ~/rpmbuild/SOURCES/mycompany-ntp-1.0
$ vi ntp.conf
driftfile /var/lib/ntp/drift
server localserver.loc

ESC ZZ
$ cd ..
$ tar cf mycompany-ntp-1.0.tar.gz mycompany-ntp-1.0/*

$ cd ../SPECS
$ cat mycompany-ntp.spec
Name:           mycompany-ntp
Version:        1.0
Release:        1%{?dist}
Summary:        MyCompany customized NTP configuration

Group:          System Environment/Daemons
License:        GPL
Source0:        %name-%version.tar.gz

Requires:       ntp

%description
This package includes MyCompany customized NTP configuration files.
Feel free to delete this package if received outside the MyCompany network.

%prep
%setup -q

%build

%install
rm -rf $RPM_BUILD_ROOT
install -m 0755 -d %{buildroot}%{_sysconfdir}/mycompany
install -m 0644 ntp.conf %{buildroot}%{_sysconfdir}/mycompany/ntp.conf

%clean
rm -rf $RPM_BUILD_ROOT

%files
%config(noreplace) %{_sysconfdir}/mycompany/ntp.conf

#code quote of the ntp RPM specfile
%files
%config(noreplace) %{_sysconfdir}/ntp.conf

%triggerin -- mycompany-ntp
if [ ! -h /etc/ntp.conf -o ! "`readlink /etc/ntp.conf`" = "/etc/mycompany/ntp.conf" ] ; then
        if [ -e /etc/ntp.conf ] ; then
                mv -f /etc/ntp.conf /etc/ntp.conf.orig
        fi
        ln -s /etc/mycompany/ntp.conf /etc/ntp.conf
fi

%triggerun -- mycompany-ntp
if [ $1 -eq 0 -a $2 -gt 0 -a -e /etc/ntp.conf.orig ] ; then
        mv -f /etc/ntp.conf.orig /etc/ntp.conf
fi

%triggerpostun -- mycompany-ntp
if [ $2 -eq 0 ]; then
        rm -f /etc/ntp.conf.rpmsave /etc/ntp.conf.orig
fi
if [ -e /etc/ntp.conf.rpmnew ] ; then
        mv /etc/ntp.conf.rpnnew /etc/ntp.conf.orig
fi

%postun
if [ -e /etc/ntp.conf.orig -a -h /etc/ntp.conf -a ! -e "`readlink /etc/ntp.conf`" ] ; then
        mv -f /etc/ntp.conf.orig /etc/ntp.conf
fi

$ cd SOURCES
$ mkdir mycompany-ntp-full-1.0
$ tar cvfz mycompany-ntp-full-1.0.tar.gz mycompany-ntp-full-1.0
$ cd ../SPECS
$ cat mycompany-ntp-full.spec
Name:           mycompany-ntp-full
Version:        1.0
Release:        1%{?dist}
Summary:        MyCompany customized NTP configuration and netstat utility

Group:          System Environment/Daemons
License:        GPL
Source0:        %name-%version.tar.gz

BuildArch:      noarch
Requires:       ntp mycompany-ntp net-tools

%description
This package includes MyCompany customized NTP configuration files.
Feel free to delete this package if received outside the MyCompany network.

%prep
%setup -q

%build

%install

%clean
rm -rf $RPM_BUILD_ROOT

%files

$ rpmbuild -bb mycompany-ntp-full.spec
$ rpm --query -Rp ../RPMS/noarch/mycompany-ntp-full-1.0-1.el6.noarch.rpm
ntp
mycompany-ntp
net-tools
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
rpmlib(CompressedFileNames) <= 3.0.4-1

rhel5 # rpm -qf $(which telnet)
krb5-workstation-1.6.1-70.el5_9.2
rhel6 # rpm-qf $(which telnet)
net-tools-1.60-110.el6_2.x86_64

Requires:       ntp mycompany-ntp
%{?el5:Requires: krb5-workstation}
%{?el6:Requires: net-tools}

Requires:        myapp >= 1.1
Conflicts:       myapp < 1.1

Requires:        myapp = 1.1
Conflicts:       myapp < 1.1 myapp > 1.1

# Creates a binary and source code package of myapp
$ rpmbuild -ba myapp.spec
# Creates a 32-bit binary package of myapp
$ rpmbuild -bb --target=i686 myapp.spec

$ ls RPMS/*/*.rpm
RPMS/i386/mycompany-ntp-1.0-1.el6.i386.rpm

# yum localinstall --nogpgcheck mycompany-ntp-1.0-1.el6.i386.rpm

$ ln -s /usr/src/redhat /home/su-rpmdev/rpmbuild
$ vi /home/su-rpmdev/export_repo.sh
#!/bin/sh
rsync -avz --delete /home/su-rpmdev/rpmbuild/RPMS/ /opt/myrepo
createrepo --database /opt/myrepo/
rsync -avz --delete -e ssh /opt/myrepo/ su-rpmdev@MAIN:/opt/myrepo/5Server

ESC ZZ
$ chmod +x /home/su-rpmdev/export_repo.sh
$ ./home/su-rpmdev/export_repo.sh

$ vi /home/su-rpmdev/export_repo.sh
#!/bin/sh
rsync -avz --delete /home/su-rpmdev/rpmbuild/RPMS/ /opt/myrepo/6Server
createrepo --database /opt/myrepo/6Server
rsync -avz --delete -e ssh /opt/myrepo/ su-rpmdev@WEB:/var/www/html/myrepo

ESC ZZ
$ chmod +x /home/su-rpmdev/export_repo.sh
$ ./home/su-rpmdev/export_repo.sh

# vi /etc/yum.repos.d/myrepo.repo
[myrepo]
name=mycompany packages for EL
baseurl=http://server01/$releasever
enabled=1
gppgcheck=0

ESC ZZ

# yum --disablerepo='*' --enablerepo='myrepo' makecache
# yum --disablerepo='*' --enablerepo='myrepo' list available
...
mycompany-ntp                      1.0-1                      myrepo

# vi /etc/yum.repos.d/myrepo.repo
[myrepo]
...
#baseurl=...
mirrorlist=myrepo.mirror

ESC ZZ
# vi /etc/yum.repos.d/myrepo.mirror
http://server01/$releasever
http://server02/$releasever
http://server03/$releasever

# vi SPECS/myrepo-release.spec
Name:           myrepo-release
Version:        1.0
Release:        1%{?dist}
Summary:        mycompany Packages for Enterprise Linux repository configuration

Group:          System Environment/Base
BuildArch:      noarch
License:        GPL
URL:            http://www.mycompany.com
Source0:        myrepo-release-%{version}.tar.gz
BuildRoot:      %{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n)

%description
This package contains the mycompany customized Packages for Enterprise Linux repository.

%prep
%setup -q

%build

%install
install -m 0755 -d %{buildroot}%{_sysconfdir}/yum.repos.d/
install -m 0755 myrepo.repo %{buildroot}%{_sysconfdir}/yum.repos.d/myrepo.repo
install -m 0755 myrepo.mirror %{buildroot}%{_sysconfdir}/yum.repos.d/myrepo.mirror

%clean
rm -rf $RPM_BUILD_ROOT

%files
%config(noreplace) %{_sysconfdir}/yum.repos.d/myrepo.repo
%config(noreplace) %{_sysconfdir}/yum.repos.d/myrepo.mirror

%changelog
* Sat Jun 29 2013 FirstName LastName  - 1.0-1
- initial release

ESC ZZ
# tar tvfz SOURCES/myrepo-release-1.0.tar.gz
-rw-r--r-- su-rpmdev/su-rpmdev 94 2013-06-28 18:12 myrepo-release-1.0/myrepo.mirror
-rw-r--r-- su-rpmdev/su-rpmdev 189 2013-06-28 18:09 myrepo-release-1.0/myrepo.repo

# tar xvfz SOURCES/myrepo-release-1.0.tar.gz -C SOURCES/
# cat SOURCES/myrepo-release-1.0/myrepo.mirror
http://server01/$releasever
http://server02/$releasever
http://server03/$releasever
# cat SOURCES/myrepo-release-1.0/myrepo.repo
[myrepo]
name=mycompany packages for EL
#baseurl=http://server01/$releasever
mirrorlist=/etc/yum.repos.d/myrepo.mirror
enabled=1
gppgcheck=0

# rpmbuild -bb SPECS/myrepo-release.spec
# scp RPMS/noarch/myrepo-release-1.0-1.rpm root@host:/root
root@host # yum localinstall --nogpgcheck myrepo-release*.rpm
root@host # yum repolist
repoid            reponame
...
myrepo            mycompany packages for EL

Softpanorama May the source be with you, but remember the KISS principle ;-)	Home	Switchboard	Unix Administration	Red Hat	TCP/IP Networks	Neoliberalism	Toxic Managers
	(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix

News	Recommended Links	Building RPMs	Tutorials	Reference	Cheat sheet
--aid option	Installation/Removal	Verification	Queries	Unpacking and analysis of RPM content	`RPM-based integrity checking`	Examples
		Finding orphaned RPMs	Removal of RPMs	`YUM`	`YAST`
RPM-related PERL Modules and Utilities	Autoupdates		Admin Horror Stories	Unix History	Humor	Etc

Top Visited <p>Your browser does not support iframes.</p>					Switchboard
					Latest
					Past week
					Past month

Feature	AppImage	Snappy	Flatpak
Unique feature	Not an appstore or repository, its simply put a packaging format for software distribution.	Led by Canonical (Same company as Ubuntu), features central app repository and active contribution from Canonical.	Features an app store called FlatHub, however, individuals may still host packages and distribute it.
Target system	Desktops and Servers.	Desktops, Servers, IoT devices, Embedded devices etc.	Desktops and limited function on servers.
Libraries/Dependencies	Base system. Runtimes optional, Libraries and other dependencies packaged.	Base system or via Plugins or can be packaged.	GNOME, KDE, Freedesktop bundled or custom bundled.
Developers	Community Driven led by Simon Peter.	Corporate driven by Canonical Ltd.	Community driven by flatpak team supported by enterprise.
Written in	C.	Golang, C and Python.	C.
Initial release	2004.	2014.	2015.
Sandboxing	Can be implemented.	3 modes – strict, classic, and devmode with varying confinement capabilities. Runs in isolation.	Isolated but Uses system files to run applications by default.
Sandboxing Platform	Firejail, AppArmor, Bubblewrap.	AppArmor.	Bubblewrap.
App Installation	Not necessary. Will act as self mounted disc.	Installation using snapd.	Installed using flatpak client tools.
App Execution	Can be run after setting executing bit.	Using desktop integrated snap tools. Runs isolated with user defined resources.	Needs to be executed using flatpak command if CLI is used.
User Privileges	Can be run w/o root user access.	Can be run w/o root user access.	Selectively required.
Hosting Applications	Can be hosted anywhere by anybody.	Has to be hosted with Canonical servers which are proprietary.	Can be hosted anywhere by anybody.
Portable Execution from non system locations	Yes.	No.	Yes, after flatpak client is configured.
Central Repository	AppImageHub.	Snap Store.	Flathub.
Running multiple versions of the app	Possible, any number of versions simultaneously.	One version of the app in one channel. Has to be separately configured for more.	Yes.
Updating applications	Using CLI command AppImageUpdate or via an updater tool built into the AppImage.	Requires snapd installed. Supports delta updating, will automatically update.	Required flatpak installed. Update Using flatpak update command.
Package sizes on disk	Application remains archived.	Application remains archived.	Client side is uncompressed.

$releasever	Explanation
5Server	RHEL 5
6Server	RHEL 6
5Workstation	RHED 5
6Workstation	RHED 6
5 / 5.1 / 5.2 / …	CentOS / Scientific Linux 5
6 / 6.1 / 5.2 / …	CentOS / Scientific Linux 6
17 / 18 / …	Fedora 17 / 18 / …

Software and configuration management using RPM

NEWS CONTENTS

Old News ;-)

[Jun 10, 2020] A Beginners Guide to Snaps in Linux - Part 1 by Aaron Kili

Jun 05, 2020 | www.tecmint.com

Conclusion

[Jun 26, 2019] Linux Package Managers Compared - AppImage vs Snap vs Flatpak

Jun 26, 2019 | www.ostechnix.com

Conclusion

[Jul 29, 2018] The evolution of package managers by Steve Ovens (Red Hat)

Jul 26, 2018 | opensource.com

Software and configuration management made easy with RPM by Christian Stankowic

September 3, 2013 | servicesblog.redhat.com

Platform

Web server file structure

Preparation

Recommended Links

Google matched content

Softpanorama Recommended

Top articles

Sites

Top articles

Sites

General Use

Packager Documentation

RPM API

RPM Language Bindings

Miscellaneous Developer Docs:

Books

Other Resources

Etc

Parameter	Explanation
-ba	Creates a binary and source code package
-bb	Creates a binary package
-bp	Extracting and patching (if necessary) of the source code
-bs	Creates a source code package
–target=noarch	Creates a platform independent package
–target=i686	…a 32-bit package
–target=x86_64	…a 64-bit package