Files could not be expanded: conflict in file _constraints

Mozilla Firefox Web Browser

Edit Package MozillaFirefox

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

Sources could not be expanded: conflict in file _constraints

Show unmerged sources

Comments 5

Richard Brown's avatar

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

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

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

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

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