pkgsrc-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: python313 dependency mismatch?




To: jperkin%pkgsrc.org@localhost

Subject: Re: python313 dependency mismatch?

From: Havard Eidnes <he%NetBSD.org@localhost>

Date: Fri, 23 Jan 2026 11:29:05 +0100 (CET)


>>But ... why can't pkgin figure out by itself that the
>>python313-3.13.11 package needs mpdecimal and install it before
>>trying (and failing) to install python313?
>
> Is mpdecimal listed in the DEPENDS for python313 in pkg_summary?

Yes.  I'm looking at

 ftp.netbsd.org:/pub/pkgsrc/packages/NetBSD/amd64/10.0/All/pkg_summary.bz2

contains for python313:

CONFLICTS=python-[0-9]*
CONFLICTS=py313-cElementTree-[0-9]*
CONFLICTS=py313-curses-[0-9]*
CONFLICTS=py313-cursespanel-[0-9]*
CONFLICTS=py313-expat-[0-9]*
CONFLICTS=py313-readline-[0-9]*
CONFLICTS=py313-sqlite3-[0-9]*
PKGNAME=python313-3.13.11
DEPENDS=libffi>=3.4.2nb3
DEPENDS=libuuid>=2.18
DEPENDS=mpdecimal>=4.0.0
DEPENDS=readline>=6.0
DEPENDS=sqlite3>=3.49.1nb3
COMMENT=Interpreted, interactive, object-oriented programming language
SIZE_PKG=162082335
BUILD_DATE=2025-12-14 08:45:10 +0000
CATEGORIES=lang python
HOMEPAGE=https://www.python.org/
LICENSE=python-software-foundation
MACHINE_ARCH=x86_64
OPSYS=NetBSD
OS_VERSION=10.0
PKGPATH=lang/python313
PKGTOOLS_VERSION=20091115
PKG_OPTIONS=readline x11
PROVIDES=/usr/pkg/lib/libpython3.13.so
PROVIDES=/usr/pkg/lib/libpython3.13.so.1.0
...

and I use this indirectly via the single active repositories.conf
line:

https://cdn.NetBSD.org/pub/pkgsrc/packages/NetBSD/$arch/10.0/All

Fetching the latter shows basically the same entry as far as I
can see.

> You're right that this is highly unusual, and I suspect there is a
> mismatch somewhere between your binary packages and pkg_summary.

OK, it's good to have confirmation that "this should not happen".

This is, as far as I recall, the first pkgsrc release which
supplies python313, and python313 gets pulled in as something
which needs to be installed via other non-versioned packages,
such as e.g. rust, clang, meson, llvm, gobject-introspection
along with many others.

As for how that mismatch has crept in I have no idea.  This
particular problem has repeated on all the more than a handfull
of systems I have recently upgraded via "pkgin fug", and I try to
stick to "normal default behaviour" and reduce the amount of
special-treatment to an absolute minimum.

Regards,

- Havard


References:

python313 dependency mismatch?
From: Havard Eidnes

Re: python313 dependency mismatch?
From: Havard Eidnes

Re: python313 dependency mismatch?
From: Jonathan Perkin




Prev by Date: Re: Update: Chrony to 4.8

Next by Date: Re: python313 dependency mismatch?

Previous by Thread: Re: python313 dependency mismatch?

Next by Thread: Re: python313 dependency mismatch?

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index