Re: Upgrade of current pkgsrc fails due to gtk3 on 10.99

[Riccardo Mottola <riccardo.mottola%libero.it@localhost>]

Hi,

maybe pkg_chck should understand multi-version one day... it is becoming 
a common disease for python, perl... but also other packages.

Greg Troxel wrote:
> Yes, all flowing from python's lack of API compat.
>
> This may not help, but I recommmend:
>
>    pkgin sk
>    pkgin uk foo # for any kept foo that you don't  actually want
>    pkgin ar
>
> which gets rid of a lot of stuff that you don't need -- and don't need
> to rebuild.

should I unkeep all stuff I don't know, including dependencies? 
sometimes packages are important, but unknown since dependencies.
Python is an extreme example: I don't want it (except 2.7 core I need to 
build certain things) but it is pulled in as dependency and all its 
modules too.. from various software, where maybe it is not even a core 
thing.

I installed pkgin, I don't have it since I am using current, there is no 
repository. I understand that for the operation above no repo is needed 
though.

# pkgin sk
processing remote summary 
(https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/10.99.10/All)...
pkgin: Could not fetch 
https://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/x86_64/10.99.10/All/pkg_summary.gz: 
Not Found

Do you suggest just pointing it to 10.0 repo to silence it? I don't want 
to mix current with binaries.

> After that, if you have  py310-foo, then
>
>    make PYTHON_VERSION_REQD=310 replace
>
> in foo (or something very close to that as I haven't done this in
> months).

I will try this... next time!

I went for another route. I tried pkg_delete. I hope this one keeps 
correctly track of dependencies with versions! It seems to.

pkg_delete py39-tomli-2.0.1nb1
Package `py39-tomli-2.0.1nb1' is still required by other packages:
        py39-pyproject_hooks-1.0.0nb1
        py39-build-1.2.1
        py39-setuptools_scm-8.0.4
        py39-hatchling-1.22.5

Then I went up and tried to remove these py39 packages.. and up to the 
tree... I was able to remove them all! No non-python package depended on 
them up to python39 removal. I did the same for python 3.10 and 3.8 
stuff, so I end up with py2.7 and py3.11 which is fine!
I hope I really didn't break anything.
I wonder if this is automated by your steps above? I thought 
pkg_rolling-replace -uv would take care of it.

Now p_rr tells me
RR> No more packages to replace; done.

yay :) However lintpksgrc is less happy:

Scan Makefiles: 19598 packages
Version mismatch: 'py-cairo' 1.18.2nb6 vs 1.26.0nb1
Unknown package: 'py-gobject' version 2.28.7nb5
Unknown package: 'py-gtk2' version 2.24.0nb48
Version mismatch: 'py-setuptools' 44.1.1nb1 vs 69.5.1

again here I think the multi-version is what bites me:

# pkg_info | grep setuptools
py27-setuptools-44.1.1nb1 New Python packaging system (python 2.x version)
py311-setuptools-69.5.1 New Python packaging system

Riccardo