Nightly snap package stopped updating
Categories
(Release Engineering Graveyard :: Release Automation: Snap, defect)
Tracking
(Not tracked)
People
(Reporter: ke5trel, Unassigned)
References
(Blocks 1 open bug, )
Details
The Nightly snap package on the edge channel is stuck on version 107.0a1 (2022-10-13) and hasn't been updated in over four days. The tarball is currently version 108.0a1 (2022-10-17).
Output of snap info firefox
:
channels:
latest/stable: 105.0.3-1 2022-10-07 (1943) 248MB -
latest/candidate: 106.0-1 2022-10-14 (1969) 250MB -
latest/beta: 107.0b1-1 2022-10-17 (1979) 188MB -
latest/edge: 107.0a1 2022-10-13 (1959) 192MB -
Comment 1•3 years ago
|
||
AFAIK it's going through manual review on the snap store. Olivier might know more?
Comment 2•3 years ago
|
||
The builds are just broken on GitHub Actions: https://github.com/canonical/firefox-snap/actions/workflows/nightly-build.yml
Comment 3•3 years ago
|
||
Latest builds are busted because of waiting for a manual review https://github.com/canonical/firefox-snap/actions/runs/3270839830/jobs/5380441903#step:6:34 I guess this is due to my https://github.com/canonical/firefox-snap/pull/8
Comment 4•3 years ago
|
||
(In reply to Julien Cristau [:jcristau] from comment #1)
AFAIK it's going through manual review on the snap store. Olivier might know more?
That's it, it's waiting on a store review: https://forum.snapcraft.io/t/update-to-the-system-files-interfaces-used-by-firefox/32165
Updated•3 years ago
|
Wouldn't it be better to wait for manual review on the snap store before landing so it doesn't block the train? The usefulness of Nightly builds is greatly diminished without daily updates and having these indefinite blockages.
Comment 6•3 years ago
|
||
Yes, ideally we should have waited for the policy update to be granted in the store before landing the change in the snap.
I've asked the store team to fast-track the approval, and if it can't be done we'll revert.
Comment 7•3 years ago
|
||
The policy update was granted, nightly snaps are published in the edge channel again. Sorry for the disruption.
Updated•1 year ago
|
Description
•