[bug-notifications] [pkgutil 0004693]: multiple occurences of use_gpg lead to multiple checks

[Mantis Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://www.opencsw.org/mantis/view.php?id=4693 
====================================================================== 
Reported By:                flod
Assigned To:                bonivart
====================================================================== 
Project:                    pkgutil
Issue ID:                   4693
Category:                   regular use
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2011-02-20 04:16 CET
Last Modified:              2011-02-25 18:11 CET
====================================================================== 
Summary:                    multiple occurences of use_gpg lead to multiple
checks
Description: 
With the update to CSWpkgutil 2.3,REV=2011.02.12 the behavior somehow
changed.
I always saw two gpg blocks on one machine:
pkgutil -c
Checking integrity of
/var/opt/csw/pkgutil/catalog.csw.informatik.uni-erlangen.de_csw_current_i386_5.10
with gpg.
gpg: Unterschrift vom 17. Februar 2011 18:27:53 MET mittels DSA-Schlüssel
ID E12E9D2F
gpg: Korrekte Unterschrift von "CSW Distribution Manager
<dm at opencsw.org>"
Checking integrity of
/var/opt/csw/pkgutil/catalog.csw.informatik.uni-erlangen.de_csw_current_i386_5.10
with gpg.
gpg: Unterschrift vom 17. Februar 2011 18:27:53 MET mittels DSA-Schlüssel
ID E12E9D2F
gpg: Korrekte Unterschrift von "CSW Distribution Manager
<dm at opencsw.org>"

It looks like there are two places for config files:
/etc/opt/csw/pkgutil.conf
/opt/csw/etc/pkgutil.conf

at the host both contained the configuration:
use_gpg=true
use_md5=true

I removed /etc/opt/csw/pkgutil.conf and the output is back to one block.

Nevertheless that was a somehow unexpected behaviour.
====================================================================== 

---------------------------------------------------------------------- 
 (0008836) flod (reporter) - 2011-02-25 18:11
 https://www.opencsw.org/mantis/view.php?id=4693#c8836 
---------------------------------------------------------------------- 
I have no problem using / creating complex regexes here.
And I guess my local problem is already solved.

I just wondered why these
"Checking integrity of ...."
do appear with --parse.
It just felt not exactly what one would expect from parsable stdout.
I did not know that this option exists before you mentioned it.

Without --parse it really is normal information.

So maybe you want to consider my remark on that, but the "bug" can be
closed anyway.