Hello, Am Mittwoch, 19. Februar 2014 schrieb Achim Gratz:
Greg KH writes:
No, it's fine, as they came from the kde repos, and as you point out, will eventually catch up and start being used :)
Grrr… that feels dirty.
Indeed :-( That said - I wonder why this happens at all. Tumbleweed builds against 13.1:Update, so in theory OBS should ensure that the version number is always higher (or does this only work with _link'ed packages?). Can an OBS expert give some insight here, please?
Lots of things cause it to rebuild, that's just the crazy dependancy chain we have. I err on the side of being cautious and rebuilding whenever the build system thinks it needs to.
So let me ask, what specifically would be a reason to rebuild KDE? I cannot remember that it was ever rebuilt for base. And if it does rebuild, then surely all that noarch stuff (wallpapers, icons, etc.) that makes up the bulk of it is not going to change anyway (I've looked at some logs and unfortunately there's metadata in the image files that contains the date and that seems to be enough to mark the whole package as "new", bummer).
If the image metadata contains the build date, I'd consider this a bug. Please open a bugreport [1] ;-) (The file's timestamp (as shipped in the tarball) is a good replacements for the build date.) Fixing this will probably not avoid the rebuild itsself, but OBS will notice that the package is unchanged, and will throw away the just-build package instead of releasing it as a "new" version. Regards, Christian Boltz [1] against KDE - this is not a tumbleweed bug -- Benutzerfreundlichkeit Der Benutzer hat zum Admin freundlich zu sein. [Thorsten Fenk] -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org