(sorry about the premature send, here is what I meant to say) :
I've remove the original text, as this is just some general comments.
I muddled through the update with more-or-less three total rebuilds of
everything python, and some hold-overs on two VMs. Third one I though
this has got to
I've remove the original text, as this is just some general comments.
I muddled through the update with more-or-less three total rebuilds of
everything python, and some hold-overs on two VMs. Third one I though
this has got to be doable as per the final snippet of shell code in the
news item:
On 05/06/2024 13:12, Eli Schwartz wrote:
Which I think is fine, if people want that, but not everyone does, so
delaying the update altogether might be preferable to those people.
Ie people like me who don't give a monkeys about python, and consider it
a necessary evil.
As far as I'm
On 6/5/24 1:12 PM, byte.size...@simplelogin.com wrote:
> On 05/06/2024 14:11, Joost Roeleveld wrote:
>> Here is the problem.
>> Not all "system-critical" packages were stabilised before this change
>> was pushed.
>
> Which packages do you consider to have been 'system critical' in this
> instance
I've been lurking in the background, partly amused and partly frustrated
at the arguments being thrown, but with the risk of exacerbating this
further I'm going to throw in my two cents (or pence in this corner of
the world).
I'll start by saying this wasn't the smoothest Python upgrade
On Tue, Jun 4, 2024 at 11:41 PM Marco Minutoli wrote:
What I believe is in the realm of reasonable is to ask to be
notified when important (as in popular) packages that are currently
missing support get updated with a stable version supporting python
3.12 so that we can take action on
On 6/5/24 4:27 AM, hitachi303 wrote:
> Am 04.06.24 um 22:34 schrieb Eli Schwartz:
>> - you read the news item, but decided to NOT defer the upgrade, and
>> instead tried to mix both python 3.11 and python 3.12 together on your
>> system
>
>
> I do have one question because I get the vipe
On Tue, Jun 4, 2024 at 11:41 PM Marco Minutoli wrote:
>
> What I believe is in the realm of reasonable is to ask to be notified when
> important (as in popular) packages that are currently missing support get
> updated with a stable version supporting python 3.12 so that we can take
> action
On Wed, Jun 5, 2024 at 4:27 AM hitachi303
wrote:
>
> the news item lists in the save upgrade section those lines:
> */* PYTHON_TARGETS: -* python3_11 python3_12
> */* PYTHON_SINGLE_TARGET: -* python3_11
>
> This is mixing python 3.11 and 3.12 on the same system. This should be
> working
Am 04.06.24 um 22:34 schrieb Eli Schwartz:
- you read the news item, but decided to NOT defer the upgrade, and
instead tried to mix both python 3.11 and python 3.12 together on your
system
I do have one question because I get the vipe from you that mixing
python 3.11 and 3.12 would be
Am 04.06.24 um 22:09 schrieb Eli Schwartz:
The purpose of the news item was to warn users that the event would
occur. Did it not achieve its purpose? Were you not-warned?
Do we at least agree that the news item was truthful?
Hi,
for me this was exactly what the news item did. It helped me to
Waldo should learn to actually read and base his comments on facts
instead of assumptions
--- Original message ---
From: Waldo Lemmer
To: gentoo-user@lists.gentoo.org
Date: Wed, 05 Jun 2024 05:21:59 +0200
Hello,
On Tue, Jun 4, 2024 at 4:37 PM Joost Roeleveld wrote:
>
>
> LAST ATTEMPT AS YOU CLEARLY ARE INCAPABLE OF UNDERSTANDING NORMAL
> ENGLISH. I WILL USE CAPS FOR YOU.
>
> WHERE DID I STATE I WANT TO DEFER THE UPDATE?
> I DO NOT CARE ABOUT THE VERSION!
>
> THE ISSUE IS CAUSED BY A BROKEN SET
On Tue, Jun 4, 2024, 22:10 Eli Schwartz wrote:
> On 6/4/24 3:37 PM, Joost Roeleveld wrote:
> >
> >> On 6/4/24 11:40 AM, Joost Roeleveld wrote:
> >>> Those steps do not just work.
> >>> The news item actually specifically states that portage will "just do
> >>> the update" if you have not set any
In case anyone is interested, here is my approach. In package.use my
starting point is
*/* PYTHON_TARGETS: -* python3_11 python3_12
*/* PYTHON_SINGLE_TARGET: -* python3_11
#*/* PYTHON_SINGLE_TARGET: -* python3_12
Then regularly check which packages i'm using that don't have 3.12 single
target yet
Dale wrote:
> Dr Rainer Woitok wrote:
>> Dale,
>>
>> On Tue, 4 Jun 2024 04:36:41 -0500 you wrote:
>>
>>> ...
>>> I read the thread linked to by the OP. I just wonder if waiting a
>>> little longer would have helped.
>> Did nobody of ye all ever read news item 48, dated 2024-05-09? It laid
>>
On 6/4/24 12:13 PM, Rich Freeman wrote:
> I don't want to be too picky as the core language maintainers have A
> LOT of work to do, but part of the challenge is that it isn't very
> obvious to a package maintainer (or anybody else) what packages
> actually have problems. It is obvious if you
On Tue, Jun 4, 2024 at 11:40 AM Joost Roeleveld wrote:
Those steps do not just work.
The news item actually specifically states that portage will "just do
the update" if you have not set any python_targets stuff.
I have those not set, but it fails on ALL my systems.
There are also still over
--- Original message ---
From: Eli Schwartz
To: gentoo-user@lists.gentoo.org
Date: Tue, 04 Jun 2024 22:34:52 +0200
On 6/4/24 4:19 PM, Joost Roeleveld wrote:
Gentoo provides you the
On 6/4/24 4:19 PM, Joost Roeleveld wrote:
>> Gentoo provides you the tools to control your system with this
>> specificity. You have the option to avoid this change -- everything will
>> continue to work flawlessly with python 3.11. This is the very
>> definition of not being forced.
>
> Having
On 6/4/24 3:37 PM, Joost Roeleveld wrote:
On 6/4/24 11:40 AM, Joost Roeleveld wrote:
Those steps do not just work.
The news item actually specifically states that portage will "just do
the update" if you have not set any python_targets stuff.
I have those not set, but it fails on ALL my
--- Original message ---
From: Eli Schwartz
To: gentoo-user@lists.gentoo.org
Date: Tue, 04 Jun 2024 22:12:41 +0200
On 6/4/24 2:23 AM, Joost Roeleveld wrote:
And before people claim I
On 6/4/24 2:23 AM, Joost Roeleveld wrote:
> 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.
On 6/4/24 3:37 PM, Joost Roeleveld wrote:
>
>> On 6/4/24 11:40 AM, Joost Roeleveld wrote:
>>> Those steps do not just work.
>>> The news item actually specifically states that portage will "just do
>>> the update" if you have not set any python_targets stuff.
>>> I have those not set, but it
On 6/4/24 11:40 AM, Joost Roeleveld wrote:
Those steps do not just work.
The news item actually specifically states that portage will "just do
the update" if you have not set any python_targets stuff.
I have those not set, but it fails on ALL my systems.
Certainly it did NOT say that.
The
On 6/4/24 11:40 AM, Joost Roeleveld wrote:
> Those steps do not just work.
> The news item actually specifically states that portage will "just do
> the update" if you have not set any python_targets stuff.
> I have those not set, but it fails on ALL my systems.
Certainly it did NOT say that.
On 6/4/24 9:17 AM, Dr Rainer Woitok wrote:
> Dale, in a previous post you shared a rather long list of packages which
> you classified not to be Python 3.12 ready. This list contained "sys-
> apps/portage"! This just can't be! From my 1060 installed packages ex-
> actly ONE package required
Dr Rainer Woitok wrote:
> Dale,
>
> On Tue, 4 Jun 2024 04:36:41 -0500 you wrote:
>
>> ...
>> I read the thread linked to by the OP. I just wonder if waiting a
>> little longer would have helped.
> Did nobody of ye all ever read news item 48, dated 2024-05-09? It laid
> out a three-step approach
On Tue, Jun 4, 2024 at 9:14 AM Rich Freeman wrote:
>
> On Tue, Jun 4, 2024 at 11:40 AM Joost Roeleveld
wrote:
> >
> > Those steps do not just work.
> > The news item actually specifically states that portage will "just do
> > the update" if you have not set any python_targets stuff.
> > I have
On Tue, Jun 4, 2024 at 11:40 AM Joost Roeleveld wrote:
>
> Those steps do not just work.
> The news item actually specifically states that portage will "just do
> the update" if you have not set any python_targets stuff.
> I have those not set, but it fails on ALL my systems.
>
> There are also
Rainer,
On Tue, 4 Jun 2024 04:36:41 -0500 you wrote:
...
I read the thread linked to by the OP. I just wonder if waiting a
little longer would have helped.
Did nobody of ye all ever read news item 48, dated 2024-05-09? It laid
out a three-step approach which surely caused at least some
Dale,
On Tue, 4 Jun 2024 04:36:41 -0500 you wrote:
> ...
> I read the thread linked to by the OP. I just wonder if waiting a
> little longer would have helped.
Did nobody of ye all ever read news item 48, dated 2024-05-09? It laid
out a three-step approach which surely caused at least some
--- Original message ---
From: Dale
To: gentoo-user@lists.gentoo.org
Date: Tue, 04 Jun 2024 11:36:41 +0200
Arve Barsnes wrote:
On Tue, 4 Jun 2024 at 08:56, Dale wrote:
That is one way
Arve Barsnes wrote:
> On Tue, 4 Jun 2024 at 08:56, Dale wrote:
>> That is one way to do it. Thing is, if there are several updates before
>> they can use 3.12, then you get to edit those each time. As it is, I'll
>> leave it there for a couple weeks. If emerge complains in the meantime,
>> I
On Tue, 4 Jun 2024 at 08:56, Dale wrote:
> That is one way to do it. Thing is, if there are several updates before
> they can use 3.12, then you get to edit those each time. As it is, I'll
> leave it there for a couple weeks. If emerge complains in the meantime,
> I can remove a line or two.
Arve Barsnes wrote:
> On Tue, 4 Jun 2024 at 07:05, Dale 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.
>>
>>
On Tue, 4 Jun 2024 at 07:05, Dale 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
On Tue, 4 Jun 2024 at 07:05, Dale 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.
>
> ##
> #
Marco Minutoli wrote:
> Hello,
>
> I have experienced difficulties in upgrading my system as a
> consequence of the python 3.12 update. I am aware that there is a
> "fervent" discussion on the topic [1], but I decided to keep my
> distance from those spicy tones and I hope for a more polite
>
On 6/4/24 12:02 AM, Marco Minutoli wrote:
> Hello,
>
> I have experienced difficulties in upgrading my system as a consequence of
> the python 3.12 update. I am aware that there is a "fervent" discussion on
> the topic [1], but I decided to keep my distance from those spicy tones and
> I hope for
Hello,
I have experienced difficulties in upgrading my system as a consequence of
the python 3.12 update. I am aware that there is a "fervent" discussion on
the topic [1], but I decided to keep my distance from those spicy tones and
I hope for a more polite conversation here.
Let me premise,
41 matches
Mail list logo
