Re: py311 conflict

[Greg Troxel <gdt%lexort.com@localhost>]

Jason Bacon <jtocino%gmx.com@localhost> writes:

> Heads-up for anyone who might be concerned.  I got the following when
> running pkg_chk -su this morning.  I don't have time to dig into it at
> the moment, so just flagging it for now.  I'm assuming that the switch
> to a new default python is meant to run smoothly.

Not really!

The actual default change is not the problem.  The problem is that when
you build py311 versions of things that have py310 versions, there are
two cases:

  The packages installs only files that are somehow namespaced by python
  version.  Examples are being under site-packages and certbot-3.10.

  The package installs files that are not namespaced like "bin/ebt" so
  that py3X-foo and py3Y-foo conflict with each other.

  The package doesn't actually install conflicting files but is marked
  as doing so.  (remember the third hard thing is off by one errors!)

For the first case, all is fine.

For the second, you have to remove the conflicting one, and the usual
approach is to "pkgin sk" and grep for py310 and then store that, remove
them, pkgin ar, then pkg_rr, and then build py311 versions of what you
deleted.

The other approach is pkg_rr and then just pkg_delete -f the old one if
it conflicts, and you don't actually want it.  This is a little
dangerous but likely ok.

The third case is fixed by removing the false conflict indication.  You
are unlikley to run into this.

> => Creating binary package
> /Users/bacon/Pkgsrc/pkgsrc/packages/All/py311-anytree-2.9.0.tgz
> ===> Installing binary package of py311-anytree-2.9.0
> pkg_add: Conflicting PLIST with py310-anytree-2.9.0: bin/ebt
> pkg_add: 1 package addition failed
> *** Error code 1
>
> Stop.
> bmake[3]: stopped in /Users/bacon/Pkgsrc/pkgsrc/devel/py-anytree
> *** Error code 1

Yep, exactly what it says.  This is how it goes with packages that
install un-namespaced binaries.