1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • Re: [gentoo-user] Re: List of installed packages that don't like 3.13 P

    From Eli Schwartz@21:1/5 to Grant Edwards on Mon May 5 17:50:01 2025
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------H8Geun760u42dxdeRZADMa6b
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    On 5/5/25 10:39 AM, Grant Edwards wrote:
    What's annoying about the Python upgrade this time is that the switch
    to 3.13 apparently happened. Then an update or two later, emerge
    starts balking because it wants to update packages that don't support
    3.13. Now to get a normal daily update to "go" I have to switch _back_
    to 3.12. That means about 250 packages have to be reinstalled after
    disabling 3.13 in package.use.

    Isn't there any sort of check that emerge can run _before_ the switch
    happens to find out whether the switch is going to cause problems for installed packages?


    Yes, emerge ran that check when you did the original switch.

    Did you do the original switch without using @world?

    Did you have packages installed that aren't in world, and you are now
    trying to update?

    Which packages is it trying to update that don't support 3.13? There is
    very little we can do to help without details of the problem you are encountering. :)


    --
    Eli Schwartz

    --------------H8Geun760u42dxdeRZADMa6b--

    -----BEGIN PGP SIGNATURE-----

    wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCaBjb7QUDAAAAAAAKCRCEp9ErcA0vV2nL AP9mNrDGodrndJ+olznvPTtooZx0mmNf5ncYQNzJrMs2nwD/XBwLxag7eNjq2/OcQLtI1US6I+I8 JqYJneQpTveHowQ=
    =Jg9Z
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eli Schwartz@21:1/5 to Grant Edwards on Mon May 5 18:20:01 2025
    To: [email protected] (Jason Zaman)

    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------0HPOP6eWZesL50ZxQIULIwEj
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    On 5/5/25 11:53 AM, Grant Edwards wrote:
    Which packages is it trying to update that don't support 3.13?

    A coupled days after the May 1st switch, 'emerge -auvND world' refused
    to run because libftdi didn't support 3.13.

    I removed libftdi,


    It has gotten 3.13 support on Sunday but erroneously did so via a
    revbump and dropping keywords to ~arch.

    If it was in world, though, then you would have had to resolve it on the
    May 1st switch.


    then it was bmap-tools (zugiana overla) that wasn't
    happy.


    This is in ::gentoo?

    There's a handful of packages that you need a *build* dep on 3.12 for,
    if you're going to do much with python. But unless you upgraded using "--with-bdeps=y" you should not have to have its build dependencies...
    and bmap-tools hasn't been updated in a year and no other packages have
    forced it to rebuild, so you shouldn't be having issues.


    Since I have no idea how many packages are going to need to be
    uninstalled or fixed with use-flags, I decided to try to "defer" the
    update by putting these lines at the top of /etc/portage/package.use

    */* PYTHON_TARGETS: -* python3_12
    */* PYTHON_SINGLE_TARGET: -* python3_12

    Now I'm about half-way through an "update" that is reinstalling 225
    packages.


    You may be able to get away with just the list of packages that are dependencies of:

    - dev-python/setuptools
    - dev-python/gpep517

    Since those are the build tools which most python packages use, which
    means if you have a single 3.12 package, you'll need the build tools
    installed for:

    PYTHON_TARGETS: python3_12 python3_13


    --
    Eli Schwartz

    --------------0HPOP6eWZesL50ZxQIULIwEj--

    -----BEGIN PGP SIGNATURE-----

    wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCaBjkZAUDAAAAAAAKCRCEp9ErcA0vV1i8 AQC3HjVzqISI55HU8rQUuMqyxKhAOoqEhDpsCEkKPdrV+gD+IGJaFk5gtvR1e5LBIsQaP62gYKhg r6JyTBqUk3jkuwI=
    =obFa
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jay Faulkner@21:1/5 to Grant Edwards on Mon May 5 19:10:01 2025
    On 5/5/25 9:41 AM, Grant Edwards wrote:
    I'm afraid I don't know what "::gentoo" refers to.


    This is the usual way to refer to overlays/repositories in portage.

    For example...

    ::gentoo is the official gentoo ebuild repository

    ::guru is the GURU project ( https://wiki.gentoo.org/wiki/Project:GURU )

    ::$N would map to a repository enabled via `eselect repository enable
    $N` (as the general pattern for more obscure overlays).


    -JayF

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Eli Schwartz@21:1/5 to Grant Edwards on Tue May 6 17:50:01 2025
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------pcPKGqxT0Dz08b0AHvahAHr5
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    On 5/6/25 11:06 AM, Grant Edwards wrote:
    On 2025-05-05, Adam Carter <[email protected]> wrote:
    On Tue, May 6, 2025 at 12:12 AM Grant Edwards <[email protected]> >> wrote:

    How do I get a list of installed packages that are preventing
    switching to Python 3.13.


    Just one package blocking 3.13 for me
    # emerge -pv --emptytree world | grep PYTHON_SINGLE | grep -v 'python3_13'

    That dosn't quite work. On my machine that has 15 packages that are preventing switching to 3_13, the line above doesn't show any of them.
    None of those packages have the PYTHON_SINGLE_TARGET flag. They all
    use PYTHON_TARGETS.

    I've tried this:

    emerge -pv --emptytree world | grep PYTHON_TARGETS | grep -v '[ "]python_3_13 '

    But that doesn't work either. emerge finds all sorts of cascading
    problems and then gives up early.


    Install "pkgcore".

    Run:

    pquery -I \
    --has-use python_targets_python3_12 \
    --has-use python_single_target_python3_12 \
    --attr use | grep -v python3_13


    It will list all *installed* packages with either "targets" or "single
    target" that *do* support Python 3.12...

    ... but don't support Python 3.13


    - They may have a fixed version available that you haven't yet
    installed. If you've recently done a world update with --newuse
    (--changed-use is not good enough) then it won't have any false
    reports.

    - They may have USE="-python", in which case it doesn't matter which
    python versions the optional USE supports. If the USE flag is enabled,
    you may be able to just disable it, too. e.g. boost, vim, file,
    util-linux, pax-utils.



    --
    Eli Schwartz

    --------------pcPKGqxT0Dz08b0AHvahAHr5--

    -----BEGIN PGP SIGNATURE-----

    wnsEABYIACMWIQTnFNnmK0TPZHnXm3qEp9ErcA0vVwUCaBouogUDAAAAAAAKCRCEp9ErcA0vV909 AQDzY5SXFKGEHSa+wIVL7LIWd/FOe89+FoqpIEB0ri0UVgD/UmArKrjUbVLdnMDOQVUu68QwqoHY RarFw5J/gHOHnwc=
    =qO5m
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)