Hi,

in the Archlinux32 repos, a lot of packages that install Python modules need rebuilding. It would be nice, if upgrading Python and such packages could somehow be coordinated, such that a new release of the Python interpreter and these packages are only pushed after all of them have been rebuilt. I don't know how Archlinux handles this, but I never noticed such problem there.

A cursory look through the logs seems to show that many of the packages I'm complaining about failed building, because a dependency wasn't built/updated first. For instance Borg failed because of python-jaraco.functools, which failed because the dependency python-setuptools is missing, which should have been pulled in by python-setuptools-scm.

Here is part of the build log for python-jaraco.functools:

(2/3) installing python                            [######################] 100%



Optional dependencies for python
    python-setuptools
    python-pip
    sqlite [installed]
    mpdecimal: for decimal
    xz: for lzma [installed]
    tk: for tkinter
(3/3) installing python-more-itertools             [----------------------]   0%
(3/3) installing python-more-itertools             [######################] 100%



[?25h==> Checking buildtime dependencies...
==> Installing missing dependencies...
[?25lresolving dependencies...
looking for conflicting packages...

Packages (15) perl-error-0.17029-5.0  perl-mailtools-2.21-7.0
              perl-timedate-2.33-5.0  python-iniconfig-2.0.0-2.1
              python-packaging-23.1-1.1  python-pep517-0.1-1.3
              python-pluggy-1.0.0-2.1  python-typing_extensions-4.7.1-1.0
              git-2.40.1-1.0  python-build-0.1-1.3  python-installer-0.1-1.3
              python-jaraco.classes-3.2.3-1.1  python-pytest-7.4.0-1.0
              python-setuptools-scm-7.1.0-4.1  python-wheel-0.1-1.3

Total Installed Size:  49.66 M
As you can see, python-setuptools-scm gets installed without its dependency python-setuptools. Could someone please have a look at this?

BR

Reply via email to