pkg_chk/pkg_rr "pyXX-foo" mismatch

["John D. Baker" <jdbaker%consolidated.net@localhost>]

Although most of them appear to have been squashed, there is still at
least one case in which pkg_rolling-replace (more properly 'pkg_chk')
falsely identifies a pyXX-foo package as requiring replacement but is
not installed whereas its "py27-foo" counterpart is installed:

$ PKGSRCDIR=/x/pkgsrc pkg_rolling-replace -u             
RR> Checking for mismatched installed packages using pkg_chk
rr> Installed: py38-sqlite3-3.8.6nb18 py38-gobject-2.28.7nb2
RR> Excluding the following mismatched packages:
rr> EXCLUDE=[]
RR> Checking for rebuild-requested installed packages (rebuild=YES)
RR> Checking for unsafe installed packages (unsafe_depends=YES)
RR> Building dependency graph for installed packages
RR> Tsorting dependency graph
*** pkg_chk reports the following packages need replacing, but they are not installed: py38-sqlite3
*** Please read the errors listed above, fix the problem,
*** then re-run pkg_rolling-replace to continue.

I notice it claiming that "py38-gobject-2.28.7nb2" is installed when in
fact "py27-gobject-2.28.7nb2" is actually installed.  With my set of
packages, it only trips over "py38-sqlite3" ("py27-sqlite3-2.7.18nb18"
is installed).

This can be worked around by including "-Xpy38-sqlite3" in the pkg_rr
command line.

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645