Can't update or use package manager -- gpg error Post: 302421718

6 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Solaris Package Manager problem

i'm trying to run Patch Manager, but i'm getting the following problem when i try and run "pprosvc" with either the -l, -d, or -i options. Assessing patches needed for your system......

2. Solaris

Solaris 10 Software Package Manager

Hi there, maybe one of you knows the software package tool during the installation of solaris 10. You are able to choose an installtion and customize it with pressing F4 .... a very nice list occurs where you can select packages like apache, ssh and so on ... Is it possible to start this...

3. Debian

apt-get package manager capability

Hi List, Recently I was doing some toubleshooting installing a package on a Redhat 6 machine using the the installer script which came with that package and I got an error message telling me that a file was missing indicating that I had to google for the dependancies and install them before this...

4. Emergency UNIX and Linux Support

Problem when trying to remove a package using rpm command - error: package is not installed

Hello, i have installed a package by using the command sudo rpm -i filepackage.rpm package filepackage is already installed when i try to remove it, i get an error saying "is not installed": sudo rpm -e filepackage.rpm error: package filepackage is not installed How can...

5. UNIX for Dummies Questions & Answers

Unable to install from synaptic package manager

i am not able to install anything from package manager .

6. UNIX for Advanced & Expert Users

Which Package Manager?

I came across a number of apparent tarballs of OS packages which are in a format which I do not recognize. Does anybody know which packet manager uses this format? # ls pkg_cfiles pkg_data pkg_data32 pkg_data64 pkg_info pkg_scripts pkg_signature # cat pkg_info PACKAGE=8.2...

LEARN ABOUT NETBSD

dscverify

DSCVERIFY(1)						      General Commands Manual						      DSCVERIFY(1)

NAME

       dscverify - verify the validity of a Debian package

SYNOPSIS

       dscverify [--keyring keyring] ... changes_or_dsc_filename ...

DESCRIPTION

       dscverify  checks  that	the  GPG  signatures  on  the  given .changes or .dsc files are good signatures made by keys in the current Debian
       keyrings, found in the debian-keyring and debian-maintainers packages.  (Additional keyrings can be specified using  the  --keyring  option
       any  number  of times.)	It then checks that the other files listed in the .changes or .dsc files have the correct sizes and checksums (MD5
       plus SHA1 and SHA256 if the latter are present).  The exit status is 0 if there are no problems and non-zero otherwise.

OPTIONS

       --keyring keyring
	      Add keyring to the list of keyrings to be used.

       --no-default-keyrings
	      Do not use the default set of keyrings.

       --no-conf, --noconf
	      Do not read any configuration files.  This can only be used as the first option given on the command-line.

       --nosigcheck, --no-sig-check, -u
	      Skip the signature verification step. That is, only verify the sizes and checksums of the files  listed  in  the	.changes  or  .dsc
	      files.

       --verbose
	      Do not suppress GPG output.

       --help, -h
	      Display a help message and exit successfully.

       --version
	      Display version and copyright information and exit successfully.

CONFIGURATION VARIABLES

       The  two  configuration	files  /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables.
       Environment variable settings are ignored for this purpose.  If the first command line option given is --noconf or  --no-conf,  then  these
       files will not be read.	The currently recognised variable is:

       DSCVERIFY_KEYRINGS
	      This is a colon-separated list of extra keyrings to use in addition to any specified on the command line.

KEYRING

       Please  note  that  the keyring provided by the debian-keyring package can be slightly out of date. The latest version can be obtained with
       rsync, as documented in the README that comes with debian-keyring.  If you sync the keyring to a non-standard location (see below), you can
       use the possibilities to specify extra keyrings, by either using the above mentioned configuration option or the --keyring option.

       Below is an example for an alias:

       alias dscverify='dscverify --keyring ~/.gnupg/pubring.gpg'

STANDARD KEYRING LOCATIONS

       By default dscverify searches for the debian-keyring in the following locations:

       - /org/keyring.debian.org/keyrings/debian-keyring.gpg

       - /usr/share/keyrings/debian-keyring.gpg

       - /usr/share/keyrings/debian-maintainers.gpg

SEE ALSO

       gpg(1) and devscripts.conf(5).

AUTHOR

       dscverify was written by Roderick Schertler <roderick@argon.org> and posted on the debian-devel@lists.debian.org mailing list, with several
       modifications by Julian Gilbey <jdg@debian.org>.

DEBIAN
								 Debian Utilities						      DSCVERIFY(1)