PitHole: RPM : “warning, user XXX does not exist – using root”

If while installing rpm package following error occurs

warning: user XXX does not exist – using root

Issue : I’m trying to build/install an rpm and it keeps giving me these warnings while installing the binary. Though I heard this could be safely ignored as its bcos there is no user XXX on my box, was wondering if there is a way to supress this in the rpm spec file itself. I know I could also manually build it as root. But curious if we could supress this from the spec.

Resolution:

Add the following in the spec file and recompile the spec file

%defattr(-,root,root)

A Brief Introduction of Package Management using APT

A Brief Introduction of Package Management using APT

Slackware: Enabling package update through online mirrors

Unfortunately Slackware 12.0 does not unable update of OS by default, slackpkg needs to be installed from the install CD/DVD which is located in “extra\slackpkg” folder.

installpkg slackpkg*.tgz

uncomment only one mirror on /etc/slackpkg/mirrors file which represent your version.

slackpkg update; slackpkg upgrade-all

the above command will upgrade your machine.

Slackware’s pacman through HTTP Proxy

edit the /etc/pacman.conf on your slackware/frugalware machine and add or update the following.

ProxyServer = your.proxy.server	ie	proxy.domain.com

ProxyPort = your_proxy_port	ie	8080 

Adding Public keys for apt-get

When one adds a new repositry in sources.list file then there is a high possibility that we face the following error when `apt-get update` command is executed

————————- Error —————–

W: GPG error: http://edevelop.org unstable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 7E5D69A103CA4243
W: GPG error: http://ftp.debian-unofficial.org sarge Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D5642BC86823D007
W: There are no public key available for the following key IDs:
B5D0C804ADB11277
W: You may want to run apt-get update to correct these problems ————————————————-

To resolve this issue i have created a script which when provided the KeyID will download the key and add it to your key ring.

---------------------------------- Script ------------------------

gpg --keyserver subkeys.pgp.net --recv-keys $1
gpg --armor --export $1 | apt-key add -
——————————————————————