improve the flatpak manifest
Categories
(Release Engineering :: Release Automation, enhancement)
Tracking
(firefox75 fixed, firefox76 fixed)
People
(Reporter: mtabara, Assigned: mtabara)
References
Details
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
We used bug 1591387 to track the building of the flatpak in try staging releases. Starting bug 1591387 comment 15, some suggestions have been made about improving the flatpak manifest in order to obtain a more robust outcome.
I'm filing this bug to track all those conversations here, so that we let 1591387 serve its original purpose.
Assignee | ||
Comment 1•5 years ago
|
||
Users have started testing the Flatpak beta that we published to the beta channel. Dropping here some more context from Matrix:
@ahayzen[m]: hey, i just tried the Firefox beta flatpak, it looks great ! The only thing so farthat didn't work straight away was being able to access the camera/microphone - i had to add --device=all to the permissions. Maybe this is because i have older portals? (Debian Stable) Or is portal / pipewire support not ready in Firefox yet ?
@barthalion: I think it's also needed for U2F to work (when udev rules are present on the host system), so I'd add it nonetheless
Assignee | ||
Comment 2•5 years ago
|
||
@barthalion provided me a diff with some l10n fixes (see bug 1621074) - I'll take into account the --device=all
config too, either here in a separate patch or there.
Assignee | ||
Comment 3•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Comment on attachment 9132342 [details]
Bug 1621083 - open more ports for Flatpak. r=rail DONTBUILD
Beta/Release Uplift Approval Request
- User impact if declined: None, this fixes configuration under the hood in building flatpaks
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: Bug 1591387
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Releng automation change.
- String changes made/needed:
Assignee | ||
Comment 6•5 years ago
|
||
Latest staging release pushed to beta channel so latest Flatpak on Flathub should have this fix.
Comment 7•5 years ago
|
||
Comment on attachment 9132342 [details]
Bug 1621083 - open more ports for Flatpak. r=rail DONTBUILD
approved for 75.0b3
Assignee | ||
Updated•5 years ago
|
Comment 8•5 years ago
|
||
bugherder |
Comment 9•5 years ago
|
||
bugherder uplift |
Assignee | ||
Comment 10•5 years ago
|
||
Just to clarify, if we want to make more manifest improvements, let's reopen this bug. Until then, I'll keep it closed.
Updated•5 years ago
|
Comment 11•5 years ago
|
||
Could you please reopen this issue due to the following issue?
If you are installing firefox you currently get no hint (at least not on flathub.org or in Gnome software 3.36 ) that ffmpeg
is listed in the manifest as an extension.
If you however use add-extensions
instead of extension
for the ffmpeg extension that would (at least in Gnome software and I have to admit that I don't fully understand how you create your flatpak package) result in a checkbox where the user can choose individually to install the ffmepg package. An example package for this approach would be Gnome games.
Comment 12•5 years ago
|
||
(In reply to jakob.jakobson13 from comment #11)
If you however use
add-extensions
instead ofextension
for the ffmpeg extension that would (at least in Gnome software and I have to admit that I don't fully understand how you create your flatpak package) result in a checkbox where the user can choose individually to install the ffmepg package. An example package for this approach would be Gnome games.
Okay, my solution is probably not the way to go. But if you could use a checkbox in gnome software to give the user the possibility to install ffmpeg, that would be neat.
Assignee | ||
Comment 13•5 years ago
|
||
I'd check in with @barthalion for that, to be honest, he helped me polish the patches from this bug and has a deeper understanding on how that works. Either NI here or poke in #flatpaks in Matrix.
Description
•