Skip to content

chore: bump runtime to gnome 49#5

Open
renner0e wants to merge 2 commits intoflathub:masterfrom
renner0e:bump-runtime
Open

chore: bump runtime to gnome 49#5
renner0e wants to merge 2 commits intoflathub:masterfrom
renner0e:bump-runtime

Conversation

@renner0e
Copy link
Copy Markdown

@renner0e renner0e commented Apr 17, 2025

also pulls in #9

@flathubbot
Copy link
Copy Markdown

🚧 Test build enqueued.

@flathubbot
Copy link
Copy Markdown

🚧 Started test build.

@flathubbot
Copy link
Copy Markdown

🚧 Test build succeeded. To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/177882/sh.loft.devpod.flatpakref

@LorbusChris
Copy link
Copy Markdown

@renner0e mind rebasing to f49, and maybe also pulling in the commit from the other open PR? Let's get an up to date PR build here and then we can escalate this to an org admin if no app maintainer steps up.

Flori Gee and others added 2 commits November 1, 2025 23:18
will cause multiple syntax errors when running in sh only. The new shebang ensures it is run with full bash support
@flathubbot
Copy link
Copy Markdown

🚧 Test build enqueued.

@flathubbot
Copy link
Copy Markdown

🚧 Started test build.

@renner0e renner0e changed the title chore: bump runtime to gnome 48 chore: bump runtime to gnome 49 Nov 1, 2025
@flathubbot
Copy link
Copy Markdown

Test build succeeded. To test this build, install it from the testing repository:

flatpak install --user https://dl.flathub.org/build-repo/224125/sh.loft.devpod.flatpakref

@LorbusChris
Copy link
Copy Markdown

cc @matthiasclasen @bkneis

@LorbusChris
Copy link
Copy Markdown

@renner0e I dug in a little, and it looks like the upstream is unmaintained :(

loft-sh/devpod#1915

@renner0e
Copy link
Copy Markdown
Author

@bkneis is there still interest in maintaining this officially?

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.

4 participants