Re: pkg/53897: tools/pkg_chk bug with python multi-version pkgs

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

The following reply was made to PR pkg/53897; it has been noted by GNATS.

From: "John D. Baker" <jdbaker%consolidated.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: pkg/53897: tools/pkg_chk bug with python multi-version pkgs
Date: Mon, 21 Jan 2019 08:45:50 -0600 (CST)

 I have seen this back with pkgsrc-2018Q3.  When python37 appeared,
 packages that could use (or preferred) python-3.x selected the highest
 available and installed python37.  Except for some packages which are
 (still) stuck at python-2.x and simply updated python27.  Then LibreOffice
 requires python-3.x but (still) can't use python37, so began installing
 python36 (again).
 
 To keep from having to install three versions of python, I set my
 PYTHON_VERSION_DEFAULT=36 which would satisfy all packages except those
 still using python27.
 
 The subsequent runs of 'pkg_rolling-replace' (which uses 'pkg_chk') would
 report some "py36-foo" packages missing when only the "py27-foo" version
 was installed.  If not excluded with "-Xpy36-foo,py36-bar,...' it would
 try to replace them and fail due to the package missing.
 
 Likewise, where both "py27-foo" and "py36-foo" packages were installed,
 only the "py36-foo" package would be updated and the "py27-foo" version
 would be ignored.  I would have to manually update those packages with
 
   $ make PYTHON_VERSION_REQD=27 replace package clean
 
 and re-run 'pkg_rr' to pick up unsafe dependency changes caused by the
 "py27-foo" updates.
 
 -- 
 |/"\ 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