On 2023-12-29 01:07, Michael Orlitzky wrote:
On 2023-12-28 23:00:36, stefan1 wrote:
Should I at least file bugs about those packages?
Surely there is no reason to artificially limit the python version in
::gentoo?
Yes, especially if the package has a test suite that passes under
python-3.1
On 2023-12-28 23:00:36, stefan1 wrote:
> Should I at least file bugs about those packages?
> Surely there is no reason to artificially limit the python version in
> ::gentoo?
Yes, especially if the package has a test suite that passes under
python-3.12. Most python packages are community-main
On 2023-12-28 20:23, Martin Vaeth wrote:
stefan1 wrote:
On 2023-12-28 15:21, Martin Vaeth wrote:
stefan1 wrote:
This got me wondering though, is there no way to fix this globally
via make.conf instead of adding patched ebuilds to my overlay?
No. Until https://bugs.gentoo.org/209653
Martin Vaeth wrote:
>
> /etc/portage/patches can patch practically everything
> in ebuilds *except metadata*. That's exactly what
> bug 209653 is about.
Typo: I meant /etc/portage/env/*/*
stefan1 wrote:
> On 2023-12-28 15:21, Martin Vaeth wrote:
>> stefan1 wrote:
>>> This got me wondering though, is there no way to fix this globally
>>> via make.conf instead of adding patched ebuilds to my overlay?
>>
>> No. Until https://bugs.gentoo.org/209653 is fixed (which did not
>> h
On Thu, 2023-12-28 at 18:38 +, stefan1 wrote:
>
> Anyway, at least I don't have many ebuilds to patch to support python
> 3.12.
If you're comfortable with git, you could switch your ::gentoo repo to
a git checkout and edit/commit your changes there. Then when you git
pull/rebase, you'll
On 2023-12-28 15:21, Martin Vaeth wrote:
stefan1 wrote:
This got me wondering though, is there no way to fix this globally
via make.conf instead of adding patched ebuilds to my overlay?
No. Until https://bugs.gentoo.org/209653 is fixed (which did not
happen since 16 years and presumably n
Arve Barsnes wrote:
> On Thu, 28 Dec 2023 at 16:21, Martin Vaeth wrote:
>>
>> stefan1 wrote:
>> > This got me wondering though, is there no way to fix this globally
>> > via make.conf instead of adding patched ebuilds to my overlay?
>>
>> No. Until https://bugs.gentoo.org/209653 is fixed (wh
On Thu, 28 Dec 2023 at 16:21, Martin Vaeth wrote:
>
> stefan1 wrote:
> > This got me wondering though, is there no way to fix this globally
> > via make.conf instead of adding patched ebuilds to my overlay?
>
> No. Until https://bugs.gentoo.org/209653 is fixed (which did not
> happen since 16
stefan1 wrote:
> This got me wondering though, is there no way to fix this globally
> via make.conf instead of adding patched ebuilds to my overlay?
No. Until https://bugs.gentoo.org/209653 is fixed (which did not
happen since 16 years and presumably never will), there is no
other way to fix
On 2023-12-16 09:47, Martin Vaeth wrote:
stefan1@shitposting.expert wrote:
I have done the migration to python 3.12.
The problem is that portage is pulling in python 3.11.
A python version jump in gentoo is always a horrible work:
Many ebuilds have not been updated and pull in unnecessari
rsnes"
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Python 3.11 USE flags being flipped on
On Fri, 15 Dec 2023 at 10:09, wrote:
> The problem is that I'm on python 3.12 and portage is pulling in an
> older version.
Should have mentioned it in the first post, the
stefan1@shitposting.expert wrote:
> I have done the migration to python 3.12.
> The problem is that portage is pulling in python 3.11.
A python version jump in gentoo is always a horrible work:
Many ebuilds have not been updated and pull in unnecessarily
python 3.11. If you use any of these p
On 2023-12-15 09:22, Arve Barsnes wrote:
On Fri, 15 Dec 2023 at 10:09, wrote:
The problem is that I'm on python 3.12 and portage is pulling in an
older version.
Should have mentioned it in the first post, then it would be easy to
look into it and tell you that media-libs/mesa is only supporte
On Fri, 15 Dec 2023 at 10:09, wrote:
> The problem is that I'm on python 3.12 and portage is pulling in an
> older version.
Should have mentioned it in the first post, then it would be easy to
look into it and tell you that media-libs/mesa is only supported up to
3.11 (in the ebuild anyway). You
On 2023-12-14 23:38, Nikos Chantziaras wrote:
On 15/12/2023 00:53, stefan1@shitposting.expert wrote:
I just tried to run today's emerge, when I saw that python 3.11 was
being pulled in and packages had this USE flag flipped on.
Python 3.11 is the default right now (and has been for some mo
On 15/12/2023 00:53, stefan1@shitposting.expert wrote:
I just tried to run today's emerge, when I saw that python 3.11 was
being pulled in and packages had this USE flag flipped on.
Python 3.11 is the default right now (and has been for some months now.)
You should follow the python upgrad
17 matches
Mail list logo
