Hi, Am 15.03.2014 21:59, schrieb Felix Miata:
On 2014-03-15 09:15 (GMT+0100) Wolfgang Rosenauer composed:
Ordinarily, that's what I would have done. However, as e.g. http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/latest-17.0esr/linux... is timestamped November 2013 when the line's support ceased, it seems illogical not to assume the corresponding version on http://download.opensuse.org/repositories/mozilla:/legacy/openSUSE_13.1/i586... would have a last built date in the days or maybe a week or two following upstream's last build.
Then you didn't really understand what Linux distribution packaging is, how reliable build systems work and what OBS is all about.
It's similarly non-obvious that content in mozilla:/legacy would have non-generic depends on some other repo than mozilla:/legacy, or that even if so, the dependency wouldn't have been published first if not coincident.
OBS has no support for dependency tracking like this. Actually it could have since it knows that mozilla is the base repo for mozilla:legacy. Keeping unmaintained packages in mozilla is no option. I'm already scared about having them in mozilla:legacy alone.
In the instant case, the system is an occasional use system. Updates need to be done in its available use window. Waiting would disrupt the use window scheduling that shouldn't need to be flexible except WRT alpha/beta testing, not supported final releases, and not "obsolete" packages.
This resurfaces the question what advantage there may be in rpm packages over the upstream generics at least WRT legacy releases? Upstream's 17.0.11 runs in 13.1's KDE4 without complaining even when all of mozilla-nspr, mozilla-nss and mozilla-nss-certs are not installed.
Your choice. It also means that you wouldn't benefit from possible security improvements in those components. It all has pros and cons. Wolfgang -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org