Greg KH writes:

On Mon, Nov 26, 2012 at 07:53:03PM +0100, Achim Gratz wrote:

...

Now that KDE is back in Tumbleweed it seems to rebuild almost daily. Even if that was intended, why does it also rebuild the noarch packages (all the artwork, icons and stuff) that surely never change? And if OBS absolutely must rebuild them, should they be packaged and delivered each time, with presumably the same content (the file sizes always differ by a few bytes, which seems to be logging information) and just a different label?

How do you know that I'm not updating the kde packages here, which require a rebuild to ensure that everything gets picked up properly? :)

As I said, some rebuilds may have been intended (there's just too many packages to check them all). Others are clearly rebuilt because their dependencies have changed, also OK. But a number of packages remain that rebuild even though their sources haven't changed and I can't see what dependency the build triggers on.

I watch these things very carefully, and don't do them lightly.

Please do not get me wrong, what you do is very much appreciated.

We have been over the "the build service rebuilds things too often" issue many times in the past. And it annoys no one more than myself, and solving it is one of the requirements (imho) to be able to better support a rolling distribution.

Well, let's start with oxygen-icon-theme (and maybe Raymond knows more about this and can chime in): I can't see why it needs to be rebuilt at all and I don't know if there's a way to check what actually triggers the rebuild. Once it gets rebuilt the produced (sub-)packages actually are different, which is the reason they get delivered to the repo in the end. The "large" subpackage for instance should just contain two subdirectories that come straight from the sources, which haven't been changed. But some of the files are apparently linked up by fdupes and maybe some others get re-compressed since they have different sizes in the two rpm, presumably because they contain meta-information from the build (in the PNG header most likely). So I suspect that if you triggered that build several times with absolutely nothing else changed you'll probably end up with non-identical packages. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Greg KH writes:

On Mon, Nov 26, 2012 at 07:53:03PM +0100, Achim Gratz wrote:

...

Now that KDE is back in Tumbleweed it seems to rebuild almost daily. Even if that was intended, why does it also rebuild the noarch packages (all the artwork, icons and stuff) that surely never change? And if OBS absolutely must rebuild them, should they be packaged and delivered each time, with presumably the same content (the file sizes always differ by a few bytes, which seems to be logging information) and just a different label?

How do you know that I'm not updating the kde packages here, which require a rebuild to ensure that everything gets picked up properly? :)

As I said, some rebuilds may have been intended (there's just too many packages to check them all). Others are clearly rebuilt because their dependencies have changed, also OK. But a number of packages remain that rebuild even though their sources haven't changed and I can't see what dependency the build triggers on.

I watch these things very carefully, and don't do them lightly.

Please do not get me wrong, what you do is very much appreciated.

We have been over the "the build service rebuilds things too often" issue many times in the past. And it annoys no one more than myself, and solving it is one of the requirements (imho) to be able to better support a rolling distribution.

Well, let's start with oxygen-icon-theme (and maybe Raymond knows more about this and can chime in): I can't see why it needs to be rebuilt at all and I don't know if there's a way to check what actually triggers the rebuild. Once it gets rebuilt the produced (sub-)packages actually are different, which is the reason they get delivered to the repo in the end. The "large" subpackage for instance should just contain two subdirectories that come straight from the sources, which haven't been changed. But some of the files are apparently linked up by fdupes and maybe some others get re-compressed since they have different sizes in the two rpm, presumably because they contain meta-information from the build (in the PNG header most likely). So I suspect that if you triggered that build several times with absolutely nothing else changed you'll probably end up with non-identical packages. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Factory and User Sound Singles for Waldorf rackAttack: http://Synth.Stromeko.net/Downloads.html#WaldorfSounds -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org