Re: pkg_chk confused over py27-* vs py37-* packages?

["John D. Baker" <jdbaker%mylinuxisp.com@localhost>]

In another thread, starting here:

  http://mail-index.netbsd.org/pkgsrc-users/2018/09/15/msg027435.html

I eventually set my own PYTHON_VERSION_DEFAULT=36 as that covers all
packages except those that can't cope with python3x at all which should
then revert to python27.

So the confusion remains for the few py27-* packages left.  'pkg_chk'
complains that their py36-* counterparts need updating but are missing.

It reports:

RR> Checking for mismatched installed packages using pkg_chk
rr> databases/py-sqlite3 - py36-sqlite3-3.6.6nb13 missing
rr> devel/py-gobject - py36-gobject-2.28.7 missing
rr> devel/py-gobject3 - py36-gobject3-3.28.3 missing
rr> graphics/py-cairo - py36-cairo-1.17.1 missing
rr> Installed: py36-sqlite3-3.6.6nb13 py36-gobject-2.28.7 py36-gobject3-3.28.3 py36-cairo-1.17.1

The "Installed:" line is completely bogus.  None of those packages are
installed as only the py27-* versions exist (due to depending packages
only supporting python27 at present).

If I don't exclude them with "-Xpy36-foo,py36-bar,..."
'pkg_rolling-replace' will try to rebuild them and fail when it can't
find them.

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]mylinuxisp[flyspeck]com    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