Michael wrote:
> On Saturday, 17 May 2025 08:17:34 British Summer Time Dale wrote:
>> Dale wrote:
>>> SNIP
>>> Oh, tried to do the last step on my main rig, emerge spit out a nice
>>> loud and hard to miss, NO!!!. There's still a lot of packages not ready
>>> for python 3.13 yet. Maybe
On Saturday, 17 May 2025 08:17:34 British Summer Time Dale wrote:
> Dale wrote:
> > SNIP
> > Oh, tried to do the last step on my main rig, emerge spit out a nice
> > loud and hard to miss, NO!!!. There's still a lot of packages not ready
> > for python 3.13 yet. Maybe next week. If I d
Dale wrote:
> SNIP
> Oh, tried to do the last step on my main rig, emerge spit out a nice
> loud and hard to miss, NO!!!. There's still a lot of packages not ready
> for python 3.13 yet. Maybe next week. If I don't forget. Again.
>
> Dale
>
> :-) :-)
>
Little update. I just went
On 5/11/25 3:10 PM, Wol wrote:
> But anyway - a bit more - the actual targets ...
>
>> You didn't post full output so it's difficult to say for sure. But,
>> "requires just one of" sounds like this:
>>
>> $ PYTHON_SINGLE_TARGET='python3_13 python3_12' emerge -1a glib-utils
>
> That's basically wh
On 11/05/2025 19:08, Eli Schwartz wrote:
Because the news item, as written, led me up the garden path!
"Safer upgrade procedure
===
A safer approach is to add Python 3.13 support to your system first,
and only then remove Python 3.12. However, note that this involves two
On 5/11/25 1:40 PM, Wol wrote:
> On 11/05/2025 16:04, Eli Schwartz wrote:
>>> I followed the instructions at the end - depclean, -1uVD, and it just
>>> fails completely with "requires just one of 3_11 or 3_12". Including
>>> important stuff like most of kde, systemd-dbus, and so on.
>>>
>>> I thoug
On Sunday, 11 May 2025 18:40:44 British Summer Time Wol wrote:
> Found it. I will investigate, but to the best of my memory I have no
> "targets" settings whatsoever. I will take a look, but at the moment I'm
> running the emerge. So from what the news item says, it looks like
> everything should
On 11/05/2025 16:04, Eli Schwartz wrote:
On 5/11/25 7:54 AM, Wol wrote:
On 02/05/2025 18:07, Alan Mackenzie wrote:
Hello, Gentoo.
I've just been trying the update for python 3.13. It went well on my
new machine (well, after unmerging app-portage/unsymlink-lib, which was
debris from some 201
On 5/11/25 9:26 AM, Philip Webb wrote:
> I noticed others reporting Python update problems & didn't follow it,
> but in my regular Sat update today encountered a big mess.
> 'setuptools-scm' offered 13 screens of conflicts,
> which were reduced to 10 by ' --backtrack=60 '.
> I tried a 'quickpkg
On 5/11/25 7:54 AM, Wol wrote:
>
>
> On 02/05/2025 18:07, Alan Mackenzie wrote:
>> Hello, Gentoo.
>>
>> I've just been trying the update for python 3.13. It went well on my
>> new machine (well, after unmerging app-portage/unsymlink-lib, which was
>> debris from some 2019 update).
>
> I'm now t
Wol wrote:
> On 11/05/2025 13:43, Frank Schletz wrote:
>> It works for me and looks very straight forward.
>> I got a non-systemd system and not that much packages.
>>
>> Hope you got a clean emerge @world at the beginning.
>
> Yup I always make sure everything's depclean'd at the end.
>
> It's now
Philip Webb wrote:
> I noticed others reporting Python update problems & didn't follow it,
> but in my regular Sat update today encountered a big mess.
> 'setuptools-scm' offered 13 screens of conflicts,
> which were reduced to 10 by ' --backtrack=60 '.
> I tried a 'quickpkg' + 'emerge -k', but
On 11/05/2025 13:43, Frank Schletz wrote:
It works for me and looks very straight forward.
I got a non-systemd system and not that much packages.
Hope you got a clean emerge @world at the beginning.
Yup I always make sure everything's depclean'd at the end.
It's now updating stage 1 fine (app
I noticed others reporting Python update problems & didn't follow it,
but in my regular Sat update today encountered a big mess.
'setuptools-scm' offered 13 screens of conflicts,
which were reduced to 10 by ' --backtrack=60 '.
I tried a 'quickpkg' + 'emerge -k', but was refused as the ebuild wa
Am Sun, 11 May 2025 12:54:48 +0100
schrieb Wol :
> On 02/05/2025 18:07, Alan Mackenzie wrote:
> > Hello, Gentoo.
> >
> > I've just been trying the update for python 3.13. It went well on my
> > new machine (well, after unmerging app-portage/unsymlink-lib, which was
> > debris from some 2019 upda
Wol wrote:
>
>
> On 02/05/2025 18:07, Alan Mackenzie wrote:
>> Hello, Gentoo.
>>
>> I've just been trying the update for python 3.13. It went well on my
>> new machine (well, after unmerging app-portage/unsymlink-lib, which was
>> debris from some 2019 update).
>
> I'm now trying to update my syst
On 02/05/2025 18:07, Alan Mackenzie wrote:
Hello, Gentoo.
I've just been trying the update for python 3.13. It went well on my
new machine (well, after unmerging app-portage/unsymlink-lib, which was
debris from some 2019 update).
I'm now trying to update my system. And it's not even fragil
On 5/4/25 12:41 PM, Alan Mackenzie wrote:
> Hello, Eli.
>
> [ Added in some hours after writing the main bit below ]
>
> I've managed to solve my problem. In the error output from emerge there
> was a message about having to update some configuration files. Normally
> this message just means "w
Hello, Eli.
[ Added in some hours after writing the main bit below ]
I've managed to solve my problem. In the error output from emerge there
was a message about having to update some configuration files. Normally
this message just means "we advise you to get around to this sometime"
but this ti
On 5/2/25 3:17 PM, Alan Mackenzie wrote:
None of this has anything to do with Gentoo, really, it's just a
tangent.
:) Yeah, fair enough for sure! I read that "a project" in the original
email as a backhanded reference to Gentoo itself. I'm friends with a
handful of folks who have been (unfair
Hello, Jay.
On Fri, May 02, 2025 at 14:44:06 -0700, Jay Faulkner wrote:
> On 5/2/25 2:15 PM, Alan Mackenzie wrote:
> > If that's the way they see things, it would seem that having a project
> > dependent on rust should figure high on that project's risk list.
> This is ... a non-actionable take,
On 5/2/25 2:15 PM, Alan Mackenzie wrote:
If that's the way they see things, it would seem that having a project
dependent on rust should figure high on that project's risk list.
This is ... a non-actionable take, regardless of if I agree with it or not.
Do you expect Gentoo to replace Firefo
On 02/05/2025 22:15, Alan Mackenzie wrote:
I think my first summary of my problem was fair: The python update scheme
is fragile. In particular if the emerge is interrupted for any reason,
it cannot be restarted, and cannot be reverted to a workable state,
without a great deal of time and expert
You need a rust compiler to compile rust's own rust compiler.
You either need dev-lang/rust-bin, a package with binaries... Either just use
it or compile the main rust package for use.
If that's a problem. dev-lang/mrustc is another compiler for rust, written in
C/C++. It has been written speci
Hello, Gentoo.
I've just been trying the update for python 3.13. It went well on my
new machine (well, after unmerging app-portage/unsymlink-lib, which was
debris from some 2019 update).
On my old machine, however, there was a seg fault while merging rust.
This is a known problem in certain firs
25 matches
Mail list logo
