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

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

On Sun, 16 Sep 2018, John D. Baker wrote:

> So the confusion remains for the few py27-* packages left.  'pkg_chk'
> complains that their py36-* counterparts need updating but are missing.
> [snip]
> 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.

Conversely, for py27-* packages which also have a py36-* version installed,
pkg_chk will report the py36-* version twice if either one is out of
date.  Once the py36-* version is updated, the py27-* version is skipped
entirely and not updated.

Most conspicuous with "py36-setuptools" (updated) vs "py27-setuptools"
(not updated).

-- 
|/"\ 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