Sysop: | Amessyroom |
---|---|
Location: | Fayetteville, NC |
Users: | 28 |
Nodes: | 6 (0 / 6) |
Uptime: | 56:17:07 |
Calls: | 422 |
Files: | 1,025 |
Messages: | 90,788 |
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?
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,
then it was bmap-tools (zugiana overla) that wasn't
happy.
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.
I'm afraid I don't know what "::gentoo" refers to.
On 2025-05-05, Adam Carter <adamcarter3@gmail.com> wrote:
On Tue, May 6, 2025 at 12:12 AM Grant Edwards <grant.b.edwards@gmail.com> >> 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.