Solved Conflict: py311-libxml2-python-2.14.4 conflicts with py311-libxml2-2.11.9_3

[Aknot]

--== SOLVED ==--

Just found on Freshports that the new package was renamed?!
Uninstalled the old package (name): pkg del textproc/py-libxml2 = solved!

--== SOLVED ==--


I'm getting the following error when running portmaster -a

Installing py311-libxml2-python-2.14.4...
pkg-static: py311-libxml2-python-2.14.4 conflicts with py311-libxml2-2.11.9_3 (installs files into the same place).
Problematic file: /usr/local/lib/python3.11/site-packages/__pycache__/drv_libxml2.cpython-311.opt-1.pyc
*** Error code 1

Stop.
make[1]: stopped in /usr/ports/textproc/libxml2-python
*** Error code 1

Stop.
make: stopped in /usr/ports/textproc/libxml2-python
===>>> Installation of py311-libxml2-python-2.14.4 (textproc/libxml2-python) failed

Anyone have any ideas?

The file drv_libxml2.cpython-311.opt-1.pyc doesn't seem to exist with that name.

I have tried to reinstall both lang/python311 and textproc/libxml2 with no luck

libxml2 seems to be dependent on libxml2-python.
This is over my head.

 

[SirDice]

MOVED - ports - FreeBSD ports tree

cgit.freebsd.org

# Port|Moved to|Date|Why
{...}
textproc/py-libxml2|textproc/libxml2-python|2025-06-28|Use correct Python package name

You don't update very often I guess?

 

[Aknot]

No it was a couple of day ago, maybe around the 26:th.

The ports are checked maybe once or twice a week.
For me a note on UPDATING would have been great, as it isn't crystal clear to me what was causing this error.

Now I know that all the renamed ports must be uninstalled first!
And that I also need to check MOVED too, and not only UPDATING.

 

[SirDice]

Now I know that all the renamed ports must be uninstalled first!

It's been a long time since I last used portmaster, but something like pkg set -o textproc/py-libxml2:textproc/libxml2-python should also end up doing the name change.

     -o oldorigin:neworigin, --change-origin oldorigin:neworigin
                Change the port origin of a given dependency from oldorigin to
                neworigin.  This corresponds to the port directory that the
                package originated from.  Typically, this is only needed for
                upgrading a library or package that has MOVED or when the
                default version of a major port dependency changes.
                (DEPRECATED) Usually this will be explained in
                /usr/ports/UPDATING.  Also see pkg-updating(8) and EXAMPLES.

pkg-set(8)

 

[Aknot]

Thanks, I appreciate it, didn't even know a name change was possible!

 

[SirDice]

Not often, but it certainly happens, MOVED contains quite a long list of renamed (and also removed) ports.

 

[Aknot]

Great to know!!