NetXMS Support Forum

English Support => General Support => Topic started by: sperlm on May 20, 2015, 04:03:38 PM

Title: New Debian Repository - importing GnuPG key [SOLVED]
Post by: sperlm on May 20, 2015, 04:03:38 PM
Hello, I have troubles following the wiki page Using APT Repository (https://wiki.netxms.org/wiki/Using_APT_Repository).

Here are the steps I took so far:
* updated /etc/apt/sources.list file with actual repository address
deb http://packages.netxms.org/debian/ wheezy main

* initialized GnuPG (if I didnt do this - key would not install and apt-get update would throw key errors)
gpg --list-keys
gpg: directory `/root/.gnupg' created
gpg: new configuration file `/root/.gnupg/gpg.conf' created
gpg: WARNING: options in `/root/.gnupg/gpg.conf' are not yet active during this run
gpg: keyring `/root/.gnupg/pubring.gpg' created
gpg: /root/.gnupg/trustdb.gpg: trustdb created

gpg --list-keys - this time no response, suppose that means OK

* download and install key
wget -q -O - http://packages.netxms.org/netxms.gpg | apt-key add -
even tried to just wget http://packages.netxms.org/netxms.gpg and apt-key add netxms.gpg

The problems are these:

1) gpg --list-keys still returns no information, I suppose it should say /root/.gnupg/netxms.gpg ?

2) apt-get update returns less key errors but also less informative...
Hit http://ftp.cz.debian.org wheezy Release.gpg
Hit http://ftp.cz.debian.org wheezy-updates Release.gpg
Hit http://ftp.cz.debian.org wheezy Release
Hit http://ftp.cz.debian.org wheezy-updates Release
Hit http://packages.netxms.org wheezy Release.gpg
Hit http://packages.netxms.org wheezy Release
Hit http://ftp.cz.debian.org wheezy/main Sources
Hit http://ftp.cz.debian.org wheezy/main amd64 Packages
Hit http://security.debian.org wheezy/updates Release.gpg
Hit http://ftp.cz.debian.org wheezy/main Translation-en
Hit http://ftp.cz.debian.org wheezy-updates/main Sources
Hit http://ftp.cz.debian.org wheezy-updates/main amd64 Packages/DiffIndex
Hit http://ftp.cz.debian.org wheezy-updates/main Translation-en/DiffIndex
Hit http://security.debian.org wheezy/updates Release
Hit http://packages.netxms.org wheezy/main amd64 Packages
Hit http://security.debian.org wheezy/updates/main Sources
Hit http://security.debian.org wheezy/updates/main amd64 Packages
Hit http://security.debian.org wheezy/updates/main Translation-en
Ign http://packages.netxms.org wheezy/main Translation-en_US
Ign http://packages.netxms.org wheezy/main Translation-en
Reading package lists... Done
W: There is no public key available for the following key IDs:
7638D0442B90D010
W: There is no public key available for the following key IDs:
7638D0442B90D010
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906


Not really sure if this is connected with netxms.gpg key at all.

3) how do I check if the key is installed correctly ?

4) is apt-get install netxms=1.2.17  the  correct command to update to 1.2.17 version or should I instruct to update all the packages specifically (netxms-agent netxms-server netxms-server-mysql netxms-base) ?
Not sure if there are versions for all packages or not. Our current version is 1.2.16.

With regards

Milan Sperl
Title: Re: New Debian Repository - importing GnuPG key
Post by: Alex Kirhenshtein on May 20, 2015, 04:13:04 PM
Hello.

APT use it's own keyring in /etc/apt/trusted.gpg and /etc/apt/trusted.gpg.d/*.gpg
You can check that: gpg --no-default-keyring --keyring /etc/apt/trusted.gpg --list-keys

Keys 7638D0442B90D010 and 9D6D8F6BC857C906 are Debian release keys, you need to install them:
apt-get install debian-keyring debian-archive-keyring

wheezy/main contains only stable version (1.2.17 at the moment), so unless you change source to "wheezy/beta", you don't need to explicitly specify version.
Title: Re: New Debian Repository - importing GnuPG key
Post by: sperlm on May 20, 2015, 05:33:33 PM
Thanks alot, as usual spot on - all problems solved ! (keeping tu actual update until tommorow)
Title: Re: New Debian Repository - importing GnuPG key
Post by: sperlm on May 22, 2015, 04:14:11 PM
Update successful.
(well, apart from that all links between nodes in manual maps disappeared  :D)

Once more thanks for the help.