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
Hey Dale, couple of comments:
- LVM should not impact the resizing of the FS at all. I'm assuming the
68GB you see for /dev/OS/var is the new size in the lvscan output? If
so, you should be ready to resize. If not, your LVM is not quite ready yet.
- Are you sure you're using ext2/3/4 as the F
Michael wrote:
> On Sunday, 11 May 2025 16:10:43 British Summer Time Dale wrote:
>> Michael wrote:
>>> I'm not the best person to advise on LVM, I just shared what I know, but I
>>> haven't used LVM in anger for a few years now. Hopefully someone with
>>> more
>>> hands on experience will chime in
On Sunday, 11 May 2025 16:10:43 British Summer Time Dale wrote:
> Michael wrote:
> > I'm not the best person to advise on LVM, I just shared what I know, but I
> > haven't used LVM in anger for a few years now. Hopefully someone with
> > more
> > hands on experience will chime in.
>
> Since the l
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
Michael wrote:
>
> I'm not the best person to advise on LVM, I just shared what I know, but I
> haven't used LVM in anger for a few years now. Hopefully someone with more
> hands on experience will chime in.
Since the lv command worked, I don't think this is a LVM problem. That
part of the gr
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 Sunday, 11 May 2025 15:39:22 British Summer Time Dale wrote:
> Michael wrote:
> > On Sunday, 11 May 2025 14:10:48 British Summer Time Dale wrote:
> >> root@fireball / # lvscan
> >>
> >> ACTIVE'/dev/home/home-lv' [<7.28 TiB] inherit
> >> ACTIVE'/dev/backup/backup' [69
Michael wrote:
> On Sunday, 11 May 2025 14:10:48 British Summer Time Dale wrote:
>
>> root@fireball / # lvscan
>> ACTIVE'/dev/home/home-lv' [<7.28 TiB] inherit
>> ACTIVE'/dev/backup/backup' [698.63 GiB] inherit
>> ACTIVE'/dev/OS/usr' [39.06 GiB] inherit
>>
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
On Sunday, 11 May 2025 14:10:48 British Summer Time Dale wrote:
> root@fireball / # lvscan
> ACTIVE'/dev/home/home-lv' [<7.28 TiB] inherit
> ACTIVE'/dev/backup/backup' [698.63 GiB] inherit
> ACTIVE'/dev/OS/usr' [39.06 GiB] inherit
> ACTIVE'/d
Dale wrote:
> Howdy,
>
> For the past three weeks or so, I can't get a clean upgrade due to
> opencv failing to compile on my old rig. I found a bug that over the
> past week or so says it has been fixed. Even tho I waited a few days
> and then synced again, it still fails to compile. It complai
Michael wrote:
> On Sunday, 11 May 2025 13:21:34 British Summer Time Dale wrote:
>> Michael wrote:
>>> On Sunday, 11 May 2025 06:41:46 British Summer Time Dale wrote:
Howdy,
I'm updating my old rig. Well, I'm trying to. I kept running out of
space while compiling rust. I need
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
On Sunday, 11 May 2025 13:21:34 British Summer Time Dale wrote:
> Michael wrote:
> > On Sunday, 11 May 2025 06:41:46 British Summer Time Dale wrote:
> >> Howdy,
> >>
> >> I'm updating my old rig. Well, I'm trying to. I kept running out of
> >> space while compiling rust. I need to make /var lar
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
Michael wrote:
> On Sunday, 11 May 2025 06:41:46 British Summer Time Dale wrote:
>> Howdy,
>>
>> I'm updating my old rig. Well, I'm trying to. I kept running out of
>> space while compiling rust. I need to make /var larger.
> There are some alternatives to this, especially for rust:
>
> 1. Fir
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/11/2025 1:20 PM, Michael wrote:
2. Or if you want to compile it locally, you can consider 'mount --bind' to a
new directory on any other local fs, which has a large enough partition for
this job. Or you if you run out of fs space altogether, or RAM isn't enough
and therefore you can't use t
On Sunday, 11 May 2025 06:41:46 British Summer Time Dale wrote:
> Howdy,
>
> I'm updating my old rig. Well, I'm trying to. I kept running out of
> space while compiling rust. I need to make /var larger.
There are some alternatives to this, especially for rust:
1. First of all not compile it
27 matches
Mail list logo
