The samba issue was solved yesterday as per
https://forum.artixlinux.org/index.php/topic,7560.0/topicseen.html All
other python 3.13 related problems that were reported in our forum and
#artix irc channel have also been fixed during the past 2 days.So the
Artix python and related packages are now 'settled' in our repo's.
The only problems I'm aware off were in the build checks, in which case
we disabled these.
artist
On 12/24/24 01:44, Javier wrote:
> Earlier Today during an artix upgrade, python was getting upgraded to
> 3.13 from 3.12 along with a bunch of packages providing python modules.
>
> However 1st, at the point I upgraded, I had uninstall samba due to
> conflicts. Eventually I had to revert all python related changes,
> :(. It seems it was too early and around half the packages still
> remained at 3.12. But the worse was AUR packages, it seems 3.13 is
> pretty aggressive deprecating several things, and Arch decided to go
> that way. I couldn't rebuilt the first three packages I tried, and I
> was not finding a clear path on the browser on how to deal with the
> failures. I do have a couple of self maintained packages I didn't
> even try.
>
> My guess, at least the Artix repos' packages might get settled for
> 3.13 at some point, so it might be a matter of time hopefully, as
> usual with just a couple of packages here and there which will require
> users to notify them. But I'm wondering how to deal with packages
> that will need re-build, it doesn't seem as trivial.
>
> Any guides available for this particular 3.12 -> 3.13 python upgrade?
> As of now I can't share output, since I already reverted, and can't
> reproduce unless moving to 3.13, but I'll wait at least an extra day
> to see if the Artix packages settle down to 3.13, and only then I'll
> go back to packages requiring re-build from AUR or self-maintained.
>
> Thanks !
>
More information about the artix-general
mailing list