Request for merging "python-team" branch

  • Done
  • quality assurance status badge
Details
3 participants
  • Andreas Enge
  • John Kehayias
  • Sharlatan Hellseher
Owner
unassigned
Submitted by
Sharlatan Hellseher
Severity
normal

Debbugs page

S
S
Sharlatan Hellseher wrote on 22 Jul 01:25 -0700
(address . guix-patches@gnu.org)
874iv44oog.fsf@gmail.com
Hi Guix,

Placing to the queue the Python team branch. It will include the work of
"On the way to pyproject-build-system everywhere"

--
Oleg
-----BEGIN PGP SIGNATURE-----

iQJKBAEBCgA0FiEEmEeB3micIcJkGAhndtcnv/Ys0rUFAmh/Sw8WHHNoYXJsYXRh
bnVzQGdtYWlsLmNvbQAKCRB21ye/9izStZGBEACROygPigBrqYNEaFvvaS+F6Sch
Rvd8cx6u67Rr4UxQkOChwB9j46cNOvQlf+0y7T2qBrxZTxN0CWCaAWRo39dfghkM
PRTcGU1oUZRhUL5ydeidx7oCn+flAwjcB8isN49B4Ith3S/PBcC0PS4C/w0/0Mf6
4dGYoMKmtmwJ7eFqejwcIvlbwKXPlYjYIbPVrl7BHmep+39pG9X8sOU0Ke0Ts/h9
NU7nBTZvS8LXPeZ/d/dgzaYFMJqCgXvEjW9vx7pfI2zn62+AMa2e3f40KDZQwvME
C2a94uy87MPHWBHyZFpMZDiJNTyJctfVz0gZf1Vccpn4C1uIuEt57655W1w8PXxr
+j5Z/1Tl0xnADfl+3S9GSfhBlwp3zi3bEK3EIW3qIJk1OtLiPqX+8OVTnLpHrTvP
zGwZ8pto8llsRK98M211ywkqUvb57O4dezvAOkeDArsluGEr4Ue5shgC0xVZ0JZl
xp60rbi6a5Qy9Cfic1h6Uije2zo4C1rosJEOhU7EVyxpVNcR66FwM3lueyuqH1iM
QYIZnFtJHoHEa1dwc/8N/Jh19C4/LMFs76tdSWz5wauEVRcN5vL3t1DhZQwyh5fG
e/vcwl/USOuysqC+l6FpCiKfYEP6vUb5+x5VIhP1dla9Dp0vdcqWeAmhGx23wtwT
FGG5VgjSUeMEF9BCyw==
=gaV2
-----END PGP SIGNATURE-----

J
J
John Kehayias wrote on 16 Sep 11:32 -0700
(name . Sharlatan Hellseher)(address . sharlatanus@gmail.com)(address . 79073@debbugs.gnu.org)
87wm5yxn85.fsf@protonmail.com
Hi Oleg!

On Tue, Jul 22, 2025 at 09:25 AM, Sharlatan Hellseher wrote:

Toggle quote (9 lines)
> Hi Guix,
>
> Placing to the queue the Python team branch. It will include the work of
> "On the way to pyproject-build-system everywhere"
> <https://codeberg.org/guix/guix/milestone/20775>
>
> --
> Oleg

What is the current status of this branch? I have a big world rebuild
going on in mesa-updates (next in the queue) and was wondering if I
should rebase on this branch?

In particular, I see python-coverage is failing tests on mesa-updates. I
tried to just cherry pick the update to that package from python-team
but it seems it is failing for other reasons (it does build on
python-team).

Thanks!
John
J
J
John Kehayias wrote on 16 Sep 12:02 -0700
(name . Sharlatan Hellseher)(address . sharlatanus@gmail.com)(address . 79073@debbugs.gnu.org)
87qzw6xlui.fsf@protonmail.com
On Tue, Sep 16, 2025 at 06:32 PM, John Kehayias wrote:

Toggle quote (23 lines)
> Hi Oleg!
>
> On Tue, Jul 22, 2025 at 09:25 AM, Sharlatan Hellseher wrote:
>
>> Hi Guix,
>>
>> Placing to the queue the Python team branch. It will include the work of
>> "On the way to pyproject-build-system everywhere"
>> <https://codeberg.org/guix/guix/milestone/20775>
>>
>> --
>> Oleg
>
> What is the current status of this branch? I have a big world rebuild
> going on in mesa-updates (next in the queue) and was wondering if I
> should rebase on this branch?
>
> In particular, I see python-coverage is failing tests on mesa-updates. I
> tried to just cherry pick the update to that package from python-team
> but it seems it is failing for other reasons (it does build on
> python-team).
>

Just tried a local rebase and python-coverage does build successfully.
So if I should rebase on the python-team branch, I can do that in the
next day or so with a version bump to mesa as well. Let me know what you
are thinking with the branch or if there are a few commits I can just
cherry pick.

Toggle quote (2 lines)
> Thanks!
> John
A
A
Andreas Enge wrote on 17 Sep 02:43 -0700
(name . John Kehayias)(address . john.kehayias@protonmail.com)
aMqCwRpWgZ_yVZDj@jurong
Hello,

is the branch ready from the Python team perspective?

It currently fails to evaluate on data.qa (just as mesa-updates, but for
a different reason):

I do not know whether this is due to a problem with the branch (I could
build it locally) or a (transient?) failure of the data service (which
has some recent evaluations of the master branch).

Maybe you could try to rebase once again?

If the problem comes from the data service, we could also go by CI:
I do not quite know how to judge a branch by CI; the best way I see
(literally) is looking at the dashboard for x86_64, which currently
still has a lot of holes.

Andreas
S
S
Sharlatan Hellseher wrote on 17 Sep 04:47 -0700
(no subject)
(address . 79073@debbugs.gnu.org)
87zfatfgh8.fsf@gmail.com
Hi,

I've migrated the last python package which affect ration is >0.7%, see:
build/test issue on a wider scale.


My strategy is:
- build all packages which affect ration is >0.7%
- build all packages where input count >= 10
- if I have resources build all >0.7% with -P1

I need help to verify the builds or fix failing packages.

Toggle snippet (25 lines)
---[ Commits stats ]---
* from-to: 3d3ae727d6106ffeae9cf80e3369842610670efb..36ecf6b0f2e4fbc57bdbc222a1c002f16b7bf7b6
* count: 479

---[ Packages stats ]---
* added: 17
* fixed: 25
* adjusted: 19
* realocated: 8
* removed: 29
* updated: 262

---[ Contributors ]---
* Felix Gruber <felgru@posteo.net>
* Jake Forster <jakecameron.forster@gmail.com>
* Maxim Cournoyer <maxim.cournoyer@gmail.com>
* Nguyễn Gia Phong <mcsinyx@disroot.org>
* Nicolas Graves <ngraves@ngraves.fr>
* Sharlatan Hellseher <sharlatanus@gmail.com>
* wrobell <wrobell@riseup.net>

---[ Refresh inpact ]---
Building the following 5179 packages would ensure 18509 dependent packages are rebuilt

--
Oleg
-----BEGIN PGP SIGNATURE-----

iQJKBAEBCgA0FiEEmEeB3micIcJkGAhndtcnv/Ys0rUFAmjKn9MWHHNoYXJsYXRh
bnVzQGdtYWlsLmNvbQAKCRB21ye/9izStURFD/9wjxCcqND903n/m4DZMjtvO3K3
vbOlwLBjHapOaEQygaQzrYW5h7UcOB7heI0xqLmRgqFMUXpS2dKpKGwtfFVzy+T9
dR+5Ehh9kdc3JeMVAkvNWfX6mBpgJfZZNzgKyR1VPihmUD9SyD1/xLsIpgn5xpwO
3XTG3eqJOn7I5aGYCe96KOPMwVf53KiRDgH3lmjL766DeFH2dLyp4pj/X6388It+
BLC6T88UdBqhy7+fiXEYXticu1sAgWp9is+h9sCWevIoJsJZ9a6fiMb4LpGQmgag
Jy/y+vcUMEL0uq8O0/Nh0qIJHo5tj9PJrTHhqU55eW0z2dGpBrzABfX/o1SXusFg
OpgU//Rys/PuLrby16Z441UuYhiZbk11lMrGxNP/6lG3csgH2ZRt5TOKb8d/BtgC
YGwj/r7Izvft/0KoEksuFa6/2kXSCJnPgTnr7+YosZF1//7pY8dvKKZ/fGQzey/K
tQY5PujSJe7ik3TI2tVR8N5TlSKi+wd3ugDtazkBCIPaxexRRG6lXSqgbE3ViJVc
Nf7W2qrxjid38L9iH3z9a/TMJeFQfscjJ/lmUv9XsK9jr7mLYJY3mLIMgdDni4rS
q4DJuaX7GmhG9lx6KaU8jBRkQRsOpuqthlzaGeovY0GYe58ulOV0glFUtoeCZIlS
7WFzHQR3YrnhLqCdjg==
=us/J
-----END PGP SIGNATURE-----

A
A
Andreas Enge wrote on 17 Sep 05:01 -0700
Re:
(name . Sharlatan Hellseher)(address . sharlatanus@gmail.com)
aMqjGJB3qr1JP9NH@jurong
After Oleg rebased the branch, I have tried to restart guix-data-service
on data.qa to force an evaluation, but it fails to start with messages
like this:
# herd start guix-data-service
Service user-homes has been started.
PID file '/var/run/guix-data-service/pid' did not show up; terminating process 66636.
Service guix-data-service could not be started.
herd: error: failed to start service guix-data-service

and no message in the log file. I have seen this PID file not showing
quite frequently with bffe, but there it can usually be "solved" by just
restarting the service. Could you maybe have a look, Chris?

Andreas
S
S
Sharlatan Hellseher wrote on 17 Sep 12:33 -0700
Request for merging "python-team" branch
(address . 79073@debbugs.gnu.org)
CAO+9K5psnVYfkx5QY3WSftMFtvOWLmQ6Pke_Y4ofQyAqbAmfYg@mail.gmail.com
Hi John,
I tried my best to remove development dependencies from inputs: coverage,
pylint, flake and friends (see details on the milestone).
Encourage everyone not to include them in new packages, and
exclude while refreshing existing ones.
VCS: https://github.incerto.xyz/;https://git.sr.ht/~hellseher/
GPG: 9847 81DE 689C 21C2 6418 0867 76D7 27BF F62C D2B5
… наш разум - превосходная объяснительная машина которая способна найти
смысл почти в чем угодно, истолковать любой феномен, но совершенно не в
состоянии принять мысль о непредсказуемости.
Attachment: file
A
A
Andreas Enge wrote on 18 Sep 00:46 -0700
(name . John Kehayias)(address . john.kehayias@protonmail.com)
aMu41cjIeC7dUQls@jurong
Am Wed, Sep 17, 2025 at 11:43:29AM +0200 schrieb Andreas Enge:
Toggle quote (3 lines)
> If the problem comes from the data service, we could also go by CI:
> https://ci.guix.gnu.org/jobset/python-team

The branch still fails to be evaluated by the data service, but has been
finished (on x86_64 and i686) on CI.

The dashboard
looks mostly green, but there is a certain cumulation of dark red
(failed builds) and rose (failed dependencies) dots for python-...
packages.

Maybe the python team (in cc) could have a look?

Andreas
S
S
Sharlatan Hellseher wrote on 18 Sep 15:04 -0700
Request for merging "python-team" branch
(address . 79073@debbugs.gnu.org)
87wm5vfmd4.fsf@gmail.com
1. Success to build all packages with large impact!

Toggle snippet (2 lines)
./pre-inst-env guix build -v1 $(jq -r '.[]|select(.affect_ratio > 0.7)| [.package_name + "@" + .package_guix_version]|@tsv' python-team-stats.json)
-----BEGIN PGP SIGNATURE-----

iQJKBAEBCgA0FiEEmEeB3micIcJkGAhndtcnv/Ys0rUFAmjMggcWHHNoYXJsYXRh
bnVzQGdtYWlsLmNvbQAKCRB21ye/9izStcPuEAChkdCWPqX8tsE62EhQxArGdsH0
vXP5N1HQNFTw3fwi1iKDKilIQXdiyt/9Xnze2CRQQB+Euam1kv+5hk+N8y0HLY65
WvyzqzOhhKJLQ4WTMJ+zAYOy8o42nnORqE9kVNqbfiVRqeoHKwSuFXHnljuRlLMT
YXSZ9pIU0lLjUDMQQxR5VCMcn35uL5dTaFkQBnrjz9C2HqLaCr+OPugagMS4F9r1
AaLVVf90OdJDUfCRm47H7KTSFcOb28eMpjWM2CSWQiGWulBqCosAtbSZ/4k2g+g5
/tKxj6Y0soW7QQQ1kcy8feQuPaT/C4BjK7MeNvLk4L56vTPiW8c/KOjmD0dFnH7s
uOH/O4V/gkTI/VXFAtEV3TwrnjCB6H0vkrVbjYlhHN+Z1jbkOoyQ48Sfq6gjQssu
V8bHls1d0vNgaQtqVj/Y6qHeoqxIV/+iKO5uZWGACNK6SfBFOHnvzGNekgSCuqRm
dIn2Ae0zw7VXGykGNatvhbcwnrfwWUSfLzhp+Y9yeiHgeKd2PtL3oEJdGyNwVWoe
M9qMFB1RLRBvIMX87Dk+8SiYJ7uCle9R7BgevDtGhwIsItOh3WGilVoUDjqw181U
3OOPi5ji1forjVTFtEJzdpupETHVu5JSXPiNyIApSW4hA3caZ690Gqo8b6MoAy5T
/SkHAipf0fX+6E6R/g==
=+Xze
-----END PGP SIGNATURE-----

S
S
Sharlatan Hellseher wrote 5 days ago
(address . 79073@debbugs.gnu.org)
CAO+9K5pJVdYwUuK+aiUjM3f7_aACNLTqpnqWOmYXupfveXZG+w@mail.gmail.com
Hi,
Writing on the way for
One last check I liked to perform before merge
guix build -v1 -P1 python-cython
As cython is defaulted to V3 now with python-cython-0 for the older version
I will be available in about 3h
VCS: https://github.incerto.xyz/;https://git.sr.ht/~hellseher/
GPG: 9847 81DE 689C 21C2 6418 0867 76D7 27BF F62C D2B5
… наш разум - превосходная объяснительная машина которая способна найти
смысл почти в чем угодно, истолковать любой феномен, но совершенно не в
состоянии принять мысль о непредсказуемости.
Attachment: file
A
A
Andreas Enge wrote 3 days ago
(name . Sharlatan Hellseher)(address . sharlatanus@gmail.com)
aNRK78gk4_678ld1@jurong
Hello,

do you think you will be able to sort out
and to push to master tomorrow? I would like to go ahead with the
mesa-updates branch and the libxml2 fix, and python-team looks really
almost finished now :)

Andreas
S
S
Sharlatan Hellseher wrote 3 days ago
Request for merging "python-team" branch
(address . 79073@debbugs.gnu.org)
87segb8qxw.fsf@gmail.com
Hi!

There is a strieng forward solution for
<ttps://codeberg.org/guix/guix/pulls/2963> which we are testing right
now.
I'm quite confident that SciPy does not need all of that propoaged
inputs at all.

I can bulid some portion of -P1 for python-scipy tey are not too many,
rebased and merge tonight, WDYT?

---
Oleg
-----BEGIN PGP SIGNATURE-----

iQJKBAEBCgA0FiEEmEeB3micIcJkGAhndtcnv/Ys0rUFAmjUZpsWHHNoYXJsYXRh
bnVzQGdtYWlsLmNvbQAKCRB21ye/9izStSQ5EAChUyaaPNe7JbAxjlwfUwjWCP+H
8astmkk8kyoYEHLJQYIN4iiV+Yv38euuomqGAJPggLJLPiJ7JPEuafmsifLY0Wjq
AE1/O+zAMkgWR4t5NVuN4qxlpIcH2YvZBDAb7fCPv9yHbLGQaoy9PFEJkULCFymq
hICM5phst7xmqZMPez/0clyoMPPS0Sa1YheibKI9LBd9blfWvKeR7q5q2nC/YU4L
u5n3gt0NooeINOG4IXr7EdkksmsWVY++zHNsrw4TfdDi5HujOHgZ2lEWf5sE5xBn
e81zJDaKkOg+6nZ/bvLgMGrdF6kRQ6IxCJ5kEnnmwep4d7Xo36xmmw3KIbbIOrnM
LJGNrwAZ7UmuHIYuxi9pwUibfMjgtjG12MipX0Fb1/gTeXFhmX+6MIjuoWWmS5iv
hLb/C9gexfDLdbUZ/gN5bWTvxtCvXujIlq5xsf0hDH8mCd+7KXat1YAHtzQkXsaC
ay1wMEaAHheZ9Qu041wySgMKYfxCh7Flf2sLb7OIAZ3AF4//g+Vus/nKtEUlCLEG
u/Eesw2MSwWGASW+IM7TVP7NsU7MIXt9/UVotSgdgD6mzzyCa/YnnRRB9fNTgKjl
qXVsMOKIEIRFpJ76YvoFb3+On6F6hxA6t6/WR9a37xtHjCAEi2pIu8N3TQA1K+lf
HsBvvcvCD97jnwprZw==
=WEcy
-----END PGP SIGNATURE-----

A
A
Andreas Enge wrote 2 days ago
(name . Sharlatan Hellseher)(address . sharlatanus@gmail.com)
aNT2B3Yl8xhPfWUg@jurong
Am Wed, Sep 24, 2025 at 10:46:03PM +0100 schrieb Sharlatan Hellseher:
Toggle quote (5 lines)
> I'm quite confident that SciPy does not need all of that propoaged
> inputs at all.
> I can bulid some portion of -P1 for python-scipy tey are not too many,
> rebased and merge tonight, WDYT?

Sounds good to me, thanks!

Andreas
S
S
Sharlatan Hellseher wrote 2 days ago
Request for merging "python-team" branch
(address . 79073-done@debbugs.gnu.org)
87plbe9ayr.fsf@gmail.com
Hi!

Toggle snippet (8 lines)
remote: Resolving deltas: 100% (3085/3085), completed with 81 local objects.
remote: * Checking 1 references
remote: Checked 1 references in total
To ssh://codeberg.org/guix/guix.git
e2a42ac5aca..ea44a564d14 master -> master
updating local tracking ref 'refs/remotes/origin/master'

--
Thanks,
Oleg
-----BEGIN PGP SIGNATURE-----

iQJKBAEBCgA0FiEEmEeB3micIcJkGAhndtcnv/Ys0rUFAmjVATwWHHNoYXJsYXRh
bnVzQGdtYWlsLmNvbQAKCRB21ye/9izStfl3EACwadea7b4kokCgPdjwcVJmf91d
gfe2TNjukEnz5MBhJXZ/pzB/jM5sShGtI1Wj5Zp60B7DSaFGP6usob3yIMXV9/qy
IzFKS9ltYQXEfCh2jn96z4kPtvRsyi17+0XjEM31GkOGdThZJwDMccI2NvDShZ+C
gEm6hqdBibCdCipPBVcl8kf/ONqeqLsMVys62jzgkS1L0JPzfBjJEKujf9x8Ubxy
5H1nOJM7QGq4UgWWVgAyq7icCeLUlZvu8qEXm4CvPldmfQsTRbsRUAnEf9Z+dMav
DjZ0xU9grI9E6Bz9zFcGr9BDAfyYWyCN8xtOq+DqgdBB12J6dSwM+eVwyeaJRLTj
7ZkSLoaQ3AYOquDToXV/iU34M/iVAEN7uweIaRl2I2WD74P3pKYy0HJ2oNIljmHA
e1Pmk5qJmCv2QIc2xZnrrlbtrwcMrJPw9zKaogTZQSrD2+IoIly/FJ382Na+j6U1
ei0nhkgB7vqHUE/ULt4fT3FZETW5N68kR9WKGSJQCLq89tk6CYckEY9R3tI/KTxD
fVCGk/TaJdqlVV3fZYiOpQmvBgdYEN/+z9k9limXdks0vNpOqOLPqO1DPeMwbdeg
k+W3l/5taXIBsBuc94dwisT5YKCr8J4SnU4/gsvlNoKqAU1Sgxw79LzX56KZ6k5Q
hLZ+Ra4YWRTahRS5bw==
=e5HV
-----END PGP SIGNATURE-----

Closed
A
A
Andreas Enge wrote 2 days ago
(name . Sharlatan Hellseher)(address . sharlatanus@gmail.com)
aNVsGiHWK3wfiJ-i@jurong
Thanks to all of you for the good work in getting the branch ready
for merge!

Andreas
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 79073@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 79073
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch