Page MenuHomePhabricator

gitlab-webhooks build fails on "The runtime.txt file isn't supported"
Closed, ResolvedPublicBUG REPORT

Description

Writing this out as a bug just in case it's a useful trail of breadcrumbs to anyone in future:

Seen just now while attempting to rebuild gitlab-webhooks:

tools.gitlab-webhooks@tools-bastion-15:~$ toolforge build start https://gitlab.wikimedia.org/repos/releng/gitlab-webhooks
...
[step-build] 2026-04-08T19:17:02.075760280Z [Determining Python version]
[step-build] 2026-04-08T19:17:02.075773716Z 
[step-build] 2026-04-08T19:17:02.075784715Z [Error: The runtime.txt file isn't supported]
[step-build] 2026-04-08T19:17:02.075794531Z The runtime.txt file can longer be used, since it has been
[step-build] 2026-04-08T19:17:02.075803823Z replaced by the more widely supported .python-version file.
[step-build] 2026-04-08T19:17:02.075813144Z 
[step-build] 2026-04-08T19:17:02.075822345Z Please delete your runtime.txt file and create a new file named:
[step-build] 2026-04-08T19:17:02.076350145Z .python-version
[step-build] 2026-04-08T19:17:02.076388546Z 
[step-build] 2026-04-08T19:17:02.076396094Z Make sure to include the '.' character at the start of the
[step-build] 2026-04-08T19:17:02.076419361Z filename. Don't add a file extension such as '.txt'.
[step-build] 2026-04-08T19:17:02.076426317Z 
[step-build] 2026-04-08T19:17:02.076431579Z In the new file, specify your app's major Python version number
[step-build] 2026-04-08T19:17:02.076437227Z only. Don't include quotes or a 'python-' prefix.
[step-build] 2026-04-08T19:17:02.076441889Z 
[step-build] 2026-04-08T19:17:02.076446811Z For example, to request the latest version of Python 3.14,
[step-build] 2026-04-08T19:17:02.076451549Z update your .python-version file so it contains exactly:
[step-build] 2026-04-08T19:17:02.076456840Z 3.14
[step-build] 2026-04-08T19:17:02.076461329Z 
[step-build] 2026-04-08T19:17:02.076465976Z We strongly recommend that you don't specify the Python patch
[step-build] 2026-04-08T19:17:02.076470319Z version number, since it will pin your app to an exact Python
[step-build] 2026-04-08T19:17:02.076475203Z version and so stop your app from receiving security updates
[step-build] 2026-04-08T19:17:02.076481166Z each time it builds.
[step-build] 2026-04-08T19:17:02.076504085Z 
[step-build] 2026-04-08T19:17:02.076508812Z 
[step-build] 2026-04-08T19:17:02.083738070Z ERROR: failed to build: exit status 1
...

I'll follow instructions here and see what happens.

Details

Related Changes in GitLab:
TitleReferenceAuthorSource BranchDest Branch
Replace runtime.txt with .python-versionrepos/releng/gitlab-webhooks!39brennenpython-versionmain
Customize query in GitLab

Event Timeline

brennen claimed this task.
bd808 subscribed.

Adding the Toolforge tag in case someone searches for this general problem only within that tag.

The cause of this change was the Toolforge wide upgrade to the "24" builder stack. This upgrade was announced at https://lists.wikimedia.org/hyperkitty/list/cloud-announce@lists.wikimedia.org/thread/EMYTA32EV2V5SQ2JIEOD2CL66YFIZEKV/. The release notes provided at that time did not explicitly include the need for this change. Thankfully the buildpack itself did a pretty good job of explaining what needed to be done.