Flathub failing to consume `stable` flatpak
Categories
(Release Engineering :: Release Automation: Other, defect)
Tracking
(firefox75 wontfix, firefox76 fixed, firefox77 fixed)
People
(Reporter: mtabara, Assigned: mtabara)
References
Details
Attachments
(1 file)
47 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-beta+
RyanVM
:
approval-mozilla-release-
|
Details | Review |
While our automation was green in building flatpak, turns out for the stable
channel there's a few more sanity checks that are performed on the Flathub side that are currently failing. This is to address those.
Assignee | ||
Comment 1•5 years ago
|
||
Two things so far:
- looks like appstream-compose(?) failed to find and extract icon - we ought to compose after we move the icons and files inside the installer - https://hg.mozilla.org/integration/autoland/file/tip/taskcluster/docker/firefox-flatpak/runme.sh#l111 appstream-compose line has to be below the org.mozilla.firefox.desktop and icons for loop lines
- drop <strong> tags from appdata file as it's not supported at the moment by the tool used by flatpak
Assignee | ||
Comment 2•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 4•5 years ago
|
||
Comment on attachment 9138526 [details]
Bug 1627660 - fix Flathub related issues for Flatpak. r=rail
Beta/Release Uplift Approval Request
- User impact if declined: None, this is an automation chanege.
- 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: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This is requested so that Flathub sanity checks are fixed. For now, Flathub folks fixed those server-side but for the future releases we should make sure automation works as expected.
- String changes made/needed:
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
Note to self: once a few betas work later this week, we should uplift this to release as well, just in case of a dot release/chemspill, we don't have to do the whole magic again.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 6•5 years ago
|
||
Comment on attachment 9138526 [details]
Bug 1627660 - fix Flathub related issues for Flatpak. r=rail
Beta/Release Uplift Approval Request
- User impact if declined: None, automation change only.
- 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: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): We should also uplift to release in case of a chemspill/dot release.
- String changes made/needed:
Comment 7•5 years ago
|
||
bugherder |
Comment 8•5 years ago
|
||
Comment on attachment 9138526 [details]
Bug 1627660 - fix Flathub related issues for Flatpak. r=rail
Approved for 76.0b2.
Comment 9•5 years ago
|
||
bugherder uplift |
Comment 10•5 years ago
|
||
Comment on attachment 9138526 [details]
Bug 1627660 - fix Flathub related issues for Flatpak. r=rail
76 goes to RC today.
Updated•5 years ago
|
Updated•4 years ago
|
Description
•