On Tue, 4 Jun 2024 at 07:05, Dale <rdalek1...@gmail.com> wrote:
I was caught up in the upgrade problem too. Each time I would run
emerge, I would get more packages that can't use 3.12 yet. This is the
list if packages I had to add to package.use.
######################################################
# Try to remove soon. Also sci-electronics/kicad further down.
app-admin/checkrestart python_single_target_python3_11
app-portage/elogviewer python_single_target_python3_11
........
######################################################
I prefer to add the flags to a specific package version only. That way
you might have to update the list on updates if packages don't yet
support the upgrade, but as soon as it does, it will remove itself
from your py3.11 list 'automatically' and you can just clean it at
your leisure down the line.
Regards,
Arve
I agree with this, but I generally have a seperate file which I will
try removing at some point.
This upgrade to 3.12 is the worst in years, a quick check on BGO shows
288 packages still not stabilised/worked on.
I have 21 systems that need a lot of manual work to fix the mess the
devs made with this.
And before people claim I can always help out the devs. I tried this
multiple times in the past, but it's always a massive uphill struggle
to get anywhere. I update ebuilds, ask for review and comments to
improve what I do. Then nothing happens.
--
Joost
