[meta] Propose RPM-based repository (Fedora, Red Hat, Opensuse, etc)
Categories
(Release Engineering :: Release Automation, enhancement)
Tracking
(relnote-firefox nightly+)
| Tracking | Status | |
|---|---|---|
| relnote-firefox | --- | nightly+ |
People
(Reporter: u48850, Unassigned)
References
(Depends on 3 open bugs, Blocks 1 open bug, )
Details
(Keywords: meta)
Attachments
(2 files, 6 obsolete files)
| Comment hidden (off-topic) |
| Comment hidden (obsolete) |
| Comment hidden (obsolete) |
Comment 5•11 years ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 7•1 year ago
|
||
Updated•1 year ago
|
Comment 8•1 year ago
|
||
These functions come from the deb repackaging sub-module and were altered to
allow multiple repackaging system.
Comment 9•1 year ago
|
||
The test_rpm is mostly based on the test_deb file.
Comment 10•1 year ago
|
||
Previously, the desktop file was generated by using the DEB_PKG_NAME build
variable which contains the binary name (eg. firefox-nightly). But this binary
may not be in the PATH environment variable and the desktop file will not show
the application or the wrong one.
This patch will allow to customize the Exec command without change the behavior
of the debian repackaging, until this one migrate to the utils sub-module.
Updated•1 year ago
|
Comment 11•1 year ago
|
||
As a former Fedora packager, I remember there being robust guidelines for .spec files. Is what we're using here at the intersection of various distros' policies? Should we take a look to see if we're missing any best practices?
Comment 12•11 months ago
|
||
The prefix DEB_ was fully removed from the template variables.
The tests which are already tested in test_utils were removed from test_debian.
Comment 13•11 months ago
•
|
||
(In reply to Andrew Overholt [:overholt] from comment #11)
As a former Fedora packager, I remember there being robust guidelines for .spec files. Is what we're using here at the intersection of various distros' policies? Should we take a look to see if we're missing any best practices?
FWIW I checked out a few download/releases pages for other Browsers and they tend to target Fedora/openSUSE. Also, it seems if it works in Fedora there's a good chance it works on Fedora/Rocky/RHEL.
I am looking through the Fedora Packaging Guidelines (it seems to be one of the most detailed and well maintained sets of guidelines.) Most of them should be useful on RPM-based distributions (specially ones downstream of Fedora.)
I was also looking at the openSUSE Packaging Guidelines (which is not Fedora based.)
That seems like a good starting point.
Comment 14•11 months ago
|
||
Comment 15•11 months ago
|
||
Updated•11 months ago
|
Comment 16•11 months ago
|
||
Comment on attachment 9468022 [details]
Bug 213920 - Add taskcluster task to build rpm package r=gabriel
Revision D239350 was moved to bug 1950505. Setting attachment 9468022 [details] to obsolete.
Comment 17•11 months ago
|
||
Comment on attachment 9462514 [details]
Bug 213920 - part 1: prepare the repackaging files related to rpm r=gabriel
Revision D235974 was moved to bug 1950511. Setting attachment 9462514 [details] to obsolete.
Comment 18•11 months ago
|
||
Comment on attachment 9462515 [details]
Bug 213920 - part 2: add a common module to use with both deb and rpm r=gabriel
Revision D235975 was moved to bug 1950511. Setting attachment 9462515 [details] to obsolete.
Comment 19•11 months ago
|
||
Comment on attachment 9462516 [details]
Bug 213920 - part 3: add the rpm choice for the mach repackage action r=gabriel
Revision D235976 was moved to bug 1950511. Setting attachment 9462516 [details] to obsolete.
Comment 20•11 months ago
|
||
Comment on attachment 9466779 [details]
Bug 213920 - part 4: use the common repackaging module with debian r=gabriel
Revision D238575 was moved to bug 1950511. Setting attachment 9466779 [details] to obsolete.
Updated•10 months ago
|
Updated•10 months ago
|
Updated•10 months ago
|
Comment 21•9 months ago
|
||
Comment 22•9 months ago
|
||
Comment 23•9 months ago
|
||
| bugherder | ||
Comment 24•9 months ago
•
|
||
| resolved | ||
#c23Resolution:
---βFIXED
Where should a user acquire a package file from?
Comment 25•9 months ago
|
||
This isn't done yet.
Updated•9 months ago
|
Comment 26•8 months ago
|
||
| resolved | ||
#c10Previously, the desktop file was generated by using the
DEB_PKG_NAMEbuild variable which contains the binary name (eg.firefox-nightly).
On behalf of those who have supported connect.mozilla.org/t5/ideas/provide-native-non-deb-linux-packages-for-firefox-nightly/idc-p/28875, does this encompass non-release editions, like Developer and Nightly? If not, I'll file a separate issue, to track it (or have its rejection at least demonstrate whether). If rationale is of use, discourse.mozilla.org/t/143785/3 is an example.
| Comment hidden (obsolete) |
| Comment hidden (obsolete) |
Comment 29•3 months ago
|
||
does this encompass non-release editions, like Developer and Nightly?
Yes.
Comment 30•23 days ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: Same reason as the .deb package we shipped in Firefox 122.0. It was part of the 122.0 release note.
[Affects Firefox for Android]: No
[Suggested wording]: To be determined.
[Links (documentation, blog post, etc)]: To be added.
Comment 31•17 days ago
|
||
Done for nightly:
https://blog.nightly.mozilla.org/2026/01/19/introducing-mozillas-firefox-nightly-rpm-package-for-rpm-based-linux-distributions/
Well done Bastien & the team``
Comment 32•16 days ago
•
|
||
Note added to Firefox Nightly release notes with this wording:
Firefox Nightly now ships with a new .rpm package for Linux users on Red Hat, Fedora, openSUSE, and other RPM-based distributions.
The note will be part of the Nightly release notes for 3 cycles (149-151).
When we extend the support to the release channel, a new release note request will be needed.
Description
•