from Benny Siegert: > It's a bug in pkg_rr. It gets confused by py27-foo vs. py37-foo etc. > Just go to the scons directory and "make package-install > PYTHON_VERSION_DEFAULT=37", then restart pkg_rr. > On Wed, Jun 26, 2019 at 12:20 PM Riccardo Mottola > <riccardo.mott...@libero.it> wrote:
> > Hi, > > after having updated userland, I am also updating pkgsrc "from source" > > and am running pkg_rolling-replace -uv > > It fails however: > > RR> Building dependency graph for installed packages > > RR> Tsorting dependency graph > > RR> Selecting serf (www/serf) as next package to replace > > RR> Checking if serf has new depends... > > RR> serf has the following new depends (need to re-tsort): > > rr> [python37 py37-scons] > > RR> Tsorting dependency graph > > pkg_info: can't find package `py37-scons' > > *** Couldn't extract PKGPATH from installed package py37-scons > > *** Please read the errors listed above, fix the problem, > > *** then re-run pkg_rolling-replace to continue. > > disc$ > > ok.. it says fix the problem, but what is the problem and how do I fix > > it? is it a package definition issue or does my pkg database have issues > locally? > > Riccardo I've been bitten/stung by that bug, to the point of impasse in updating NetBSD packages. Could I put PYTHON_VERSION_DEFAULT=37 in /etc/mk.conf ? But it's not only py37-* packages, for instance pkg_info: can't find package `libproxy' *** Couldn't extract PKGPATH from installed package libproxy *** Please read the errors listed above, fix the problem, *** then re-run pkg_rolling-replace to continue. or pkg_info: can't find package `p5-Net-LibIDN' *** Couldn't extract PKGPATH from installed package p5-Net-LibIDN *** Please read the errors listed above, fix the problem, *** then re-run pkg_rolling-replace to continue. That bug in pkg_rr has been around for some time! When will it be fixed? It even affects the most recent pkg_rolling-replace-0.24.6 . I've been stung! Tom