Christian Boltz writes:
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.)
It's been some time since I looked at this. It may not have been a date but something else leaked from the build environment into the metadata, I don't remember exactly.
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.
Yes. The comparison was done for the whole file, even though the actual image data was (and always will be) identical.
[1] against KDE - this is not a tumbleweed bug
Wouldn't this be an OBS bug? The build uses something like imagemagick (I'm fuzzy on those details, too) to convert from the source to several derivative formats. Then the OBS build process compares the full files, not just the image data, to find that yes, each time that conversion is done a different image was created. This is true at some level, but for all practical purposes these images should be treated as unchanged from any other build if only the metadata differs. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org