On 2020/10/08 02:33, James Cook wrote: > I'm reporting a slight hiccup upgrading from 6.7 to snapshot. This might > count as my own fault, but reporting it in case it's something that's > supposed to run smoothly. (I was able to recover; no help needed.) > > I upgraded from 6.7 to a snapshot (with sysupgrade -s), then ran > "doas pkg_add -u", and got this: > > > Collision in python-3.8.6: the following files already exist > /usr/local/bin/2to3 from python-3.8.6 > /usr/local/bin/pydoc3 from python-3.8.6 > /usr/local/bin/python3 from python-3.8.6 > /usr/local/bin/python3-config from python-3.8.6 > /usr/local/lib/pkgconfig/python3.pc from python-3.8.6 > It seems to be a missing package registration
This is because, 1) The default Python version in ports was switched from 3.7 to 3.8, so the symlinks for the "default names" moved at that time 2) After this, Python 3.7 was updated in 6.7-stable The @conflict lines in the PLIST files for 3.8 in -current should have been updated after the -stable update, so pkg_add doesn't know that it needs to update 3.7.9 to the "6.8 version" (without the symlinks) before installing 3.8. We can't do anything for the main 6.8 release packages now, but it can be fixed in 6.8-stable once it's open. For those arches with -stable packages available, once those packages are built it shouldn't be noticeable to users. > After this, pkg_delete partial-python; pkg_add python3; pkg_add -u > completed the upgrade without trouble (though I haven't tested anything). Yes that should do the trick.
