-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updated dependencies and runtimes to 23 #334
base: master
Are you sure you want to change the base?
Conversation
Started test build 149902 |
Build 149902 failed |
I guess you could volunteer to be a flatpak dev in the main repo |
I guess - I just barely know what I am doing in the first place. As far as I can see now the main repo also needs some work to even get to a usable manifest. |
Oh, I was just searching around for a usable flatpak version of this browser and stumbled upon this. I am using an immutable distro, so flatpak is really my only option. Hope you figure something out. |
@lkoning it builds, but have you tried running? I get this error. I wanna ask before I delve into it.
|
I am sorry, I threw the towel a while back. I have no time to dive into it without support from qutebrowser-devs themselves. |
qutebrowser maintainer here — I'm not sure where the "without support" is coming from to be honest. I'm watching this repository, am happy to help where I can, and merged various Flatpak-specific PRs. The only thing I'm unable to is maintaining a third-party package for an ecosystem I'm not using myself. |
I threw everything from my machine... I remember updating all the depencies in the manifest file but just couldn't get it to create a usable package. If you would be able to update the manifest to current versions - we might be able to go from there. |
I'm not going to do maintenance work on the Flatpak package, I expect that to be done by someone who is interested in Flatpak and knows their way around it (neither applies to me, I never used Flatpak personally and I have no idea how the packaging works). It looks like by "no support from the qutebrowser devs" you mean "the qutebrowser devs aren't maintaining the Flatpak package". The latter is correct, no qutebrowser devs are directly involved in Flatpak packaging because none of them seem to be using Flatpak themselves (just like no qutebrowser devs are involved in distro packaging for distributions they don't use, and usually even for distributions they do use). |
I got it working here: #336 Would love to hear you thoughts. |
I still would like to use Qutebrowser from a flatpak...
Updated runtimes and dependency versions to have at least a succeeding local build.
How can I run this through the build-process?