Re: Python issues, mostly

[John Klos <john%klos.com@localhost>]

Hi,

> I guess you should mention that you're using pkg_rollingreplace?

Oops. I had written that this was with pkg_rolling-replace originally, but 
apparently edited it out. Apologies.

> I haven't seen any of these problems, but I'm not using it.

Both python and vim-share issues happen with manual invocations.

For instance:

cd /usr/pkgsrc/emulators/qemu
make clean
...
===> su-do-clean [llvm-18.1.8] ===> Cleaning for llvm-18.1.8
sh: cannot create =20150314:../../pkgtools/cwrappers: directory nonexistent
test: /usr/pkgsrc/Makefile: unexpected operator
make[1]: don't know how to make show-depends-pkgpaths. Stop
test: stopped: unexpected operator
test: stopped: unexpected operator
===> su-do-clean [libunwind-18.1.8] ===> Cleaning for libunwind-18.1.8
===> su-do-clean [rust-1.79.0] ===> Cleaning for rust-1.79.0
===> su-do-clean [py312-maturin-1.7.1] ===> Cleaning for 
py312-maturin-1.7.1
===> su-do-clean [py312-cryptography-43.0.1] ===> Cleaning for 
py312-cryptography-43.0.1
===> su-do-clean [py312-idna-3.10] ===> Cleaning for py312-idna-3.10
cd: bad substitution
cd: bad substitution
make[1]: don't know how to make clean. Stop

make[1]: stopped in /root
*** Error code 2

Stop.
make: stopped in /usr/pkgsrc/emulators/qemu


> I'd suggest pkg_rr do the same, or add your own hook to run "pkg_admin 
> rebuild-tree" after each package is replaced.

That does fix a number of things, and the automated process includes both 
a pkg_admin rebuild and rebuild-tree, but in the case of vim-share, it 
doesn't fix anything.

There was a recent similar issue with llvm and rust, but that's been 
fixed.

John