Hi everyone, anyone else waiting for a package to go through Staging to land in Tumbleweed? Better see yourself to a large stack of book/DVDs/BluRays/whatever, as that will probably not happen in the near future. Just have a look at the Dashboard [1], and notice almost every Staging is stuck at 99%. And if you dig any deeper, all Stagings are waiting for Firefox to be built. Now, Firefox apparently is a monster and needs 16GByte of memory to build, but that's not the relevant part. The OBS has 4 workers able to build Firefox, and as FF needs about 2 hours to complete it should be able to complete a Staging about twice an hour. Unfortunately, that's only half (or more likely 5%) of the truth ... --- As we all know, FF runs much better if you rebuild it in your home project, just _link or copypac the one from the Mozilla OBS project. Make sure you build it for Leap 15.0, 15.1 and Tumbleweed, just in case. If you need some more customization, add a llvm and gcc copy, and ideally modify their _constraints to <physicalmem>16GB - you want it to build fast, after all ... Of course you can add _constraints to any other package as well. --- end of rant --- Several of the copies are the personal development projects of the respective package maintainers, and there also a few copies which are just personal experiments. These are IMHO using the OBS for what it is meant for. The majority, however are just plain links to the development projects, revision count 1, sitting there forever, creating bit-identical copies of other projects. Currently, it is possible for a single user to stage a DoS on the OBS, deliberately, by lack of knowledge or by just not caring. I think this is far from ideal. So, any good ideas how to remove these annoying delays from the Stagings? Kind regards, Stefan [1] https://build.opensuse.org/project/staging_projects/openSUSE:Factory -- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019