Re: pkg_add python errors ...

2021-11-30 Thread Stuart Henderson
On 2021-11-29, Why 42? The lists account.  wrote:
>
> Well, errors related to the python package ...
>
> After updating to the latest snapshot and rebooting I ran "pkg_add -vu"
> to update all my packages, which I think is the right thing to do.
>
> I noticed some strange errors related to python scroll past i.e.

I made a mistake with the version switch from 3.8 to 3.9 as default and you
updated to the one snapshot package build that had bad conflict markers -
I have been told that running pkg_add -u a couple more times will clear it,
if not then rm -r /var/db/pkg/partial-python* and run pkg_add -u again.




pkg_add python errors ...

2021-11-29 Thread Why 42? The lists account.


Well, errors related to the python package ...

After updating to the latest snapshot and rebooting I ran "pkg_add -vu"
to update all my packages, which I think is the right thing to do.

I noticed some strange errors related to python scroll past i.e.
> ...
> Update candidates: p7zip-16.02p6 -> p7zip-16.02p6
> Update candidates: partial-python-3.9.7p3 -> python-3.9.9
> Unexpected symlink: /usr/local/bin/2to3
> Unexpected symlink: /usr/local/bin/pydoc3
> Unexpected symlink: /usr/local/bin/python3
> Unexpected symlink: /usr/local/bin/python3-config
> Unexpected symlink: /usr/local/lib/pkgconfig/python3-embed.pc
> Unexpected symlink: /usr/local/lib/pkgconfig/python3.pc
> Unexpected symlink: /usr/local/man/man1/python3.1
> Bad rename /usr/local/bin/2to3 to /usr/local/bin/2to3.X77AFtJWEq: No such 
> file or directory
> Bad rename /usr/local/bin/pydoc3 to /usr/local/bin/pydoc3.FLyJqqVBCV: No such 
> file or directory
> Bad rename /usr/local/bin/python3 to /usr/local/bin/python3.mct9eU2JKh: No 
> such file or directory
> Bad rename /usr/local/bin/python3-config to 
> /usr/local/bin/python3-config.LVZ4scwF2N: No such file or directory
> Bad rename /usr/local/lib/pkgconfig/python3-embed.pc to 
> /usr/local/lib/pkgconfig/python3-embed.pc.W3q0EmYVnC: No such file or 
> directory
> Bad rename /usr/local/lib/pkgconfig/python3.pc to 
> /usr/local/lib/pkgconfig/python3.pc.0svv4fWReb: No such file or directory
> Bad rename /usr/local/man/man1/python3.1 to 
> /usr/local/man/man1/python3.1.iWHWD3b3mt: No such file or directory
> [python-3.9.9]partial-python-3.9.7p3->: ok
> Update candidates: pcsc-tools-1.4.27p0 -> pcsc-tools-1.4.27p0
> Update candidates: picocom-3.1 -> picocom-3.1
> ...

I'm not sure why the "bad rename" would occur, indeed the rename does
seem to have taken place:
> mjoelnir:log 29.11 # ls -l /usr/local/bin/2to3*
> -rwxr-xr-x  1 root  bin101 Nov 26 12:37 /usr/local/bin/2to3-3.8
> -rwxr-xr-x  1 root  bin101 Nov 25 20:41 /usr/local/bin/2to3-3.9
> -rw---  1 root  wheel0 Nov 29 15:04 /usr/local/bin/2to3.H0cMphlKfH
> -rw---  1 root  wheel0 Nov 29 15:34 /usr/local/bin/2to3.X77AFtJWEq

(I ran the pkg_add a second time to capture the above error messages, so
I imagine that is why there are now two temp filenames.)

The pkg_add operation ended with:
> ...
> Update candidates: zsh-syntax-highlighting-0.7.1 -> 
> zsh-syntax-highlighting-0.7.1
> --- -partial-python-3.9.7p3 ---
> Files kept as partial-python-3.9.7p3.1 package

I now seem to have four different versions of the python package
installed:
partial-python-3.9.7p3.1
python-2.7.18p5
python-3.8.12p4
python-3.9.9

I'm not sure why python-3.9.7p3.1 has been kept around, according to
pkg_info nothing requires it:
> mjoelnir:/etc 29.11 # pkg_info -R partial-python-3.9.7p3.1
> mjoelnir:/etc 29.11 #

Running sysclean doesn't report anything obviously python related.

Has something gone wrong here? Do I need to to do any manual cleanup?

Cheers,
Robb.

mjoelnir:/etc 29.11 # sysctl kern.version
kern.version=OpenBSD 7.0-current (GENERIC.MP) #131: Mon Nov 29 00:32:40 MST 2021
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP