From rfg@tristatelogic.com  Tue May 14 02:21:54 2013
Return-Path: <rfg@tristatelogic.com>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1])
	by hub.freebsd.org (Postfix) with ESMTP id 712B1BB
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 14 May 2013 02:21:54 +0000 (UTC)
	(envelope-from rfg@tristatelogic.com)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com [69.62.255.118])
	by mx1.freebsd.org (Postfix) with ESMTP id 52E33957
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 14 May 2013 02:21:54 +0000 (UTC)
Received: by segfault.tristatelogic.com (Postfix, from userid 1237)
	id 0CC3E3B2A2; Mon, 13 May 2013 19:21:53 -0700 (PDT)
Message-Id: <20130514022153.0CC3E3B2A2@segfault.tristatelogic.com>
Date: Mon, 13 May 2013 19:21:53 -0700 (PDT)
From: Ronald F.Guilmette <rfg@tristatelogic.com>
Reply-To: Ronald F.Guilmette <rfg@tristatelogic.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc: rfg@tristatelogic.com
Subject: pkg_info -g fails to notice when files have been changed
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         178609
>Category:       bin
>Synopsis:       pkg_info(1): pkg_info -g fails to notice when files have been changed
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue May 14 02:30:00 UTC 2013
>Closed-Date:    
>Last-Modified:  Wed Apr 16 00:30:39 UTC 2014
>Originator:     Ronald F. Guilmette
>Release:        FreeBSD 9.1-RELEASE amd64
>Organization:
entr0py
>Environment:

FreeBSD 9.1-RELEASE amd64

>Description:

Running the "pkg_info -g" command can sometimes improperly result in
pkg_info reporting MD5 checksum mismatches for files that have simply
been modified, either by the user or by some other port or package
installation process, since the time when the file(s) in question
were first installed.  This is entirely inappropriate as it can cause
the system administrator to worry and fret that some file or files
that were installed as parts of ports or packages have gotten corrupted
somehow, when in fact the files in question, which may be locally con-
figurable config files have merely been locally configured.

More information on this problem can be found here:

http://lists.freebsd.org/pipermail/freebsd-ports/2013-May/083485.html

>How-To-Repeat:

portinstall p5-XML-SAX
portinstall p5-XML-LibXML
pkg_info -g 'p5-XML-SAX*'

(The second portinstall invocation above will result in the file named
/usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/ParserDetails.ini which was
already installed as part of the p5-XML-SAX install to be diddled.  There
after, pkg_info -g 'p5-XML-SAX*' will claim that the file is failing its
MD5 checksum check.  This is arguably true, but is also entirely superfluous,
pointless, and unnerving for the typical sysadmin.)

>Fix:

Left as an exercise for the reader.
 
But seriously folks, a proper fix should be fairly trivial.  I will cook
up patches, if requested.

>Release-Note:
>Audit-Trail:

From: "Ronald F.Guilmette" <rfg@tristatelogic.com>
To: FreeBSD-gnats-submit@freebsd.org
Cc: rfg@tristatelogic.com
Subject: bin/178609: pkg_info -g fails to notice when files have been changed
Date: Mon, 13 May 2013 19:21:53 -0700 (PDT)

 >Number:         178609
 >Category:       bin
 >Synopsis:       pkg_info -g fails to notice when files have been changed
 >Confidential:   no
 >Severity:       serious
 >Priority:       medium
 >Responsible:    freebsd-bugs
 >State:          open
 >Quarter:        
 >Keywords:       
 >Date-Required:
 >Class:          sw-bug
 >Submitter-Id:   current-users
 >Arrival-Date:   Tue May 14 02:30:00 UTC 2013
 >Closed-Date:
 >Last-Modified:
 >Originator:     Ronald F. Guilmette
 >Release:        FreeBSD 9.1-RELEASE amd64
 >Organization:
 entr0py
 >Environment:
 
 FreeBSD 9.1-RELEASE amd64
 
 >Description:
 
 Running the "pkg_info -g" command can sometimes improperly result in
 pkg_info reporting MD5 checksum mismatches for files that have simply
 been modified, either by the user or by some other port or package
 installation process, since the time when the file(s) in question
 were first installed.  This is entirely inappropriate as it can cause
 the system administrator to worry and fret that some file or files
 that were installed as parts of ports or packages have gotten corrupted
 somehow, when in fact the files in question, which may be locally con-
 figurable config files have merely been locally configured.
 
 More information on this problem can be found here:
 
 http://lists.freebsd.org/pipermail/freebsd-ports/2013-May/083485.html
 
 >How-To-Repeat:
 
 portinstall p5-XML-SAX
 portinstall p5-XML-LibXML
 pkg_info -g 'p5-XML-SAX*'
 
 (The second portinstall invocation above will result in the file named
 /usr/local/lib/perl5/site_perl/5.14.2/XML/SAX/ParserDetails.ini which was
 already installed as part of the p5-XML-SAX install to be diddled.  There
 after, pkg_info -g 'p5-XML-SAX*' will claim that the file is failing its
 MD5 checksum check.  This is arguably true, but is also entirely superfluous,
 pointless, and unnerving for the typical sysadmin.)
 
 >Fix:
 
 Left as an exercise for the reader.
  
 But seriously folks, a proper fix should be fairly trivial.  I will cook
 up patches, if requested.
 
 >Release-Note:
 >Audit-Trail:
 >Unformatted:
 _______________________________________________
 freebsd-bugs@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
 To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org"
>Unformatted:
