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

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

Sending this again because the original seems to have gotten lost
or trapped by a SPAM filter:

On Fri, 14 Sep 2018, John D. Baker wrote:

> With more things starting to use python3? (python37, py37-*) packages,
> my latest 'pkg_rolling-replace' runs are getting confused, claiming
> such things as:
> 
> rr> devel/py-anytree - py27-anytree-2.4.3 missing
> rr> devel/py-nose - py27-nose-1.3.7 missing
> rr> textproc/py-pygments - py27-pygments-2.2.0 missing
> 
> Of course they are missing, because those packages are built for use with
> python37, not python27 (pkgsrc-HEAD).
> 
> As of pkgsrc-2018Q2, none of those packages were built for any python
> version (for my usual complement of packages).
> 
> In the past, pkg_chk didn't seem to have a problem with a py3?-* package
> that didn't also have a py27-* counterpart.  (In pkgsrc-2018Q2, I have
> py36-meson-0.44.1nb3, but not py27-meson and 'pkg_chk' doesn't complain
> that py27-meson is missing.)

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