Edit Package MozillaFirefox

Mozilla Firefox Web Browser

Linked against system libs. Pointed to shit into "${HOME}/.cache/mozilla/firefox" instead of /tmp. Mandatory extension signing is disabled. GPU acceleration is enabled by default.

Refresh
Refresh
Source Files (show merged sources derived from linked package)
Filename Size Changed
MozillaFirefox-rpmlintrc 0000000029 29 Bytes almost 14 years
MozillaFirefox.changes 0000380917 372 KB 1 day
MozillaFirefox.desktop 0000000640 640 Bytes 7 months
MozillaFirefox.spec 0000036411 35.6 KB about 4 hours
_constraints 0000001132 1.11 KB about 2 months
create-tar.sh 0000010940 10.7 KB over 1 year
firefox-102.0.source.tar.xz 0482027632 460 MB 1 day
firefox-102.0.source.tar.xz.asc 0000000833 833 Bytes 1 day
firefox-appdata.xml 0000002171 2.12 KB almost 6 years
firefox-branded-icons.patch 0000001902 1.86 KB 9 months
firefox-kde.patch 0000009599 9.37 KB 1 day
firefox-mimeinfo.xml 0000000292 292 Bytes over 14 years
firefox-search-provider.ini 0000000150 150 Bytes over 1 year
firefox.1 0000003244 3.17 KB almost 2 years
firefox.js 0000018118 17.7 KB 3 months
google-api-key 0000000040 40 Bytes almost 5 years
l10n-102.0.tar.xz 0049084872 46.8 MB 1 day
mozilla-aarch64-startup-crash.patch 0000001291 1.26 KB over 2 years
mozilla-api-key 0000000033 33 Bytes about 5 years
mozilla-bmo1005535.patch 0000001257 1.23 KB over 2 years
mozilla-bmo1504834-part1.patch 0000003981 3.89 KB over 2 years
mozilla-bmo1504834-part3.patch 0000003533 3.45 KB over 2 years
mozilla-bmo1512162.patch 0000001887 1.84 KB over 1 year
mozilla-bmo1568145.patch 0000001465 1.43 KB over 1 year
mozilla-bmo531915.patch 0000000873 873 Bytes 9 months
mozilla-bmo849632.patch 0000001324 1.29 KB over 2 years
mozilla-bmo998749.patch 0000001000 1000 Bytes almost 2 years
mozilla-fix-aarch64-libopus.patch 0000000842 842 Bytes over 2 years
mozilla-fix-top-level-asm.patch 0000002608 2.55 KB 6 months
mozilla-get-app-id 0000001123 1.1 KB over 11 years
mozilla-kde.patch 0000061252 59.8 KB 1 day
mozilla-libavcodec58_91.patch 0000000902 902 Bytes 1 day
mozilla-nongnome-proxies.patch 0000001842 1.8 KB almost 2 years
mozilla-ntlm-full-path.patch 0000001159 1.13 KB over 2 years
mozilla-pgo.patch 0000007237 7.07 KB 3 months
mozilla-reduce-rust-debuginfo.patch 0000000287 287 Bytes 5 months
mozilla-s390-context.patch 0000002067 2.02 KB 3 months
mozilla-s390x-skia-gradient.patch 0000001372 1.34 KB almost 2 years
mozilla-silence-no-return-type.patch 0000060317 58.9 KB 1 day
mozilla.keyring 0000023372 22.8 KB about 1 year
mozilla.sh.in 0000007793 7.61 KB 4 months
one_swizzle_to_rule_them_all.patch 0000001261 1.23 KB 1 day
spellcheck.js 0000000060 60 Bytes over 7 years
svg-rendering.patch 0000001082 1.06 KB 1 day
tar_stamps 0000000342 342 Bytes 1 day
tar_stamps.beta 0000000704 704 Bytes over 1 year
Comments 5

Richard Brown's avatar

RBrownSUSE wrote 5 months ago

Hello - can you please consider dropping this package from your home project? build.opensuse.org only has 12 worker servers capable of building firefox, which takes a great deal of time every time it does. As your package builds against Tumbleweed, the presence of this package in your home project draws a disproprotionate amount of resources away from other people. This delays submissions, builds, and updates to all official openSUSE Projects (Tumbleweed, MicroOS, Leap, etc). Many Thanks for the consideration. - Rich


Sergey Kondakov's avatar

X0F wrote 5 months ago

Yeah ? Why don't you consider dropping yours instead ? I wasn't maintaining my fork for SEVEN years just for shits and giggles. And it wouldn't take that much resources if you would consider my suggestions more than 5 years ago for decreasing unnecessary rebuilds (why the hell it still trigger rebuilds of all dependant packages when OBS knows that there were no API change ?) and drove me off mailing lists, as with most of home-project users.

The reason for Mozilla projects' obscene build requirements is their rust dependency, obsession with bundling most dependencies and giant binary that balloons LTO requirements. If you would even had a glance at my fork, you would have seen that I already decreased build requirements several times over your official package. If OBS still uses it's top VMs and rebuilds it on every fart than you should direct your demands to its developers, if you still have any.

How about, instead of completely driving off people from SUSE altogether, after you personally already drove them off mailing lists and any inclination to volunteer in main repo maintenance, you would volunteer your paycheck on acquiring servers (Aliexpress has thousands if not millions of cheap 8-18 core Xeons, DDR3 ECC RAM and LGA2011 boards available, by the way) and actually steer some development in OBS'es build efficiency instead of smothering it just like you did with kiwi livecd toolkit & SUSE installer's fork-install capability which made mass-install of fixed-up SUSE images impractical thus cutting out more users ?


Richard Brown's avatar

RBrownSUSE wrote 5 months ago

https://en.opensuse.org/Terms_of_site#Rules_of_conduct

https://en.opensuse.org/Terms_of_site#Open_Build_Service_.28the_.E2.80.9CBuild_Service.E2.80.9D.29


Sergey Kondakov's avatar

X0F wrote 5 months ago

And what this supposed to mean ? A threat that if someone does not comply to your passive-aggressive insults & demands and will not be completely driven off by your attitude, you will forcibly kick them off the community until there is only King Brown and his yes-men left ?


Richard Brown's avatar

RBrownSUSE wrote 5 months ago

Threat? No, just a reminder of the terms and conditions you are held under while using this platform.

What you choose to do with that information is up to you.

You might also want to peruse https://en.opensuse.org/openSUSE:Build_Service_application_blacklist also

There appears to be a number of packages in home:X0F and it's subprojects which violate the rules, do you have approved exceptions to those rules with the OBS Legal Team? If not, would you like me to contact them on your behalf?

openSUSE Build Service is sponsored by