Skip to content

test: use 'env python3'#11

Merged
swick merged 1 commit into
flatpak:mainfrom
bluca:python3
Aug 12, 2025
Merged

test: use 'env python3'#11
swick merged 1 commit into
flatpak:mainfrom
bluca:python3

Conversation

@bluca

@bluca bluca commented Aug 11, 2025

Copy link
Copy Markdown
Contributor

'env python' only works on some RH derivatives, on Debian and derivatives it does not work by default.

Fixes #10

@bluca bluca mentioned this pull request Aug 11, 2025
@swick

swick commented Aug 11, 2025

Copy link
Copy Markdown
Collaborator

Thank you! LGTM. I'm trying to figure out why the CI doesn't work now that the project has moved to the flatpak org.

@swick

swick commented Aug 12, 2025

Copy link
Copy Markdown
Collaborator

@bluca so the CI tries to avoid building the build image every run, but the repo was moved, so the image doesn't exist there and it only gets updated/created when CI runs in the right context (i.e. not on a MR but when something got pushed to main). The CI falls back on using an image from the repo of the user creating the MR, but for that to exist, you have to push to your repo and ensure the CI runs there.

'env python' only works on some RH derivatives, on Debian and
derivatives it does not work by default.

Fixes flatpak#10
@bluca

bluca commented Aug 12, 2025

Copy link
Copy Markdown
Contributor Author

Ok, done (I think)

@bluca

bluca commented Aug 12, 2025

Copy link
Copy Markdown
Contributor Author

@swick swick merged commit de8fc7d into flatpak:main Aug 12, 2025
3 checks passed
@swick

swick commented Aug 12, 2025

Copy link
Copy Markdown
Collaborator

Thank you!

@bluca bluca deleted the python3 branch August 12, 2025 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

test_close_stdin times out

2 participants