Greetings. In the last 6-7 snapshots, i noticed some packages being constantly "upgraded" without appearing in the changelog. There are packages like that many times because some library they are depending on was upgraded and so they had to be recompiled or something like that. It doesn't seem to be the case this time though. There are quite a few packages but i mainly noticed it due to wine-mono which in my mind doesn't depend on libraries and doesn't need to be recompiled. I also did a check with zypper / rpm and it seems to only depend on wine. % cd /var/cache/zypp/packages/non-oss/noarch % ls -al wine-mono-6.3.0-1.* -rw-r--r-- 1 root root 64502590 Aug 4 10:32 wine-mono-6.3.0-1.1.noarch.rpm -rw-r--r-- 1 root root 64502587 Sep 5 08:33 wine-mono-6.3.0-1.2.noarch.rpm -rw-r--r-- 1 root root 64502573 Sep 9 08:42 wine-mono-6.3.0-1.4.noarch.rpm -rw-r--r-- 1 root root 64502582 Sep 10 08:52 wine-mono-6.3.0-1.5.noarch.rpm -rw-r--r-- 1 root root 64502589 Sep 12 13:25 wine-mono-6.3.0-1.6.noarch.rpm -rw-r--r-- 1 root root 64502588 Sep 14 16:33 wine-mono-6.3.0-1.7.noarch.rpm -rw-r--r-- 1 root root 64502584 Sep 15 09:08 wine-mono-6.3.0-1.8.noarch.rpm Here are the packages i have in my cache. As you see, it got upgraded pretty much on every snapshot. I am not saying this as a criticism. I am just asking out of curiosity. I have a relative understanding of how factory and tumbleweed snapshots work but there are some things like this that i haven't fully understood. Thank you for your time.
On Wed, 2021-09-15 at 13:31 +0300, Khelben Blackstaff wrote:
Greetings.
In the last 6-7 snapshots, i noticed some packages being constantly "upgraded" without appearing in the changelog. There are packages like that many times because some library they are depending on was upgraded and so they had to be recompiled or something like that.
It doesn't seem to be the case this time though. There are quite a few packages but i mainly noticed it due to wine-mono which in my mind doesn't depend on libraries and doesn't need to be recompiled. I also did a check with zypper / rpm and it seems to only depend on wine.
% cd /var/cache/zypp/packages/non-oss/noarch % ls -al wine-mono-6.3.0-1.* -rw-r--r-- 1 root root 64502590 Aug 4 10:32 wine-mono-6.3.0- 1.1.noarch.rpm -rw-r--r-- 1 root root 64502587 Sep 5 08:33 wine-mono-6.3.0- 1.2.noarch.rpm -rw-r--r-- 1 root root 64502573 Sep 9 08:42 wine-mono-6.3.0- 1.4.noarch.rpm -rw-r--r-- 1 root root 64502582 Sep 10 08:52 wine-mono-6.3.0- 1.5.noarch.rpm -rw-r--r-- 1 root root 64502589 Sep 12 13:25 wine-mono-6.3.0- 1.6.noarch.rpm -rw-r--r-- 1 root root 64502588 Sep 14 16:33 wine-mono-6.3.0- 1.7.noarch.rpm -rw-r--r-- 1 root root 64502584 Sep 15 09:08 wine-mono-6.3.0- 1.8.noarch.rpm
Here are the packages i have in my cache. As you see, it got upgraded pretty much on every snapshot.
I am not saying this as a criticism. I am just asking out of curiosity. I have a relative understanding of how factory and tumbleweed snapshots work but there are some things like this that i haven't fully understood.
Thank you for your time.
The last digit of the release is the build number. It means that the package has been rebuilt because some of its dependencies changed, or for some other reason. The code of wine-mono itself is not changed. I suppose that' the reason why it isn't mentioned in the summary emails. Martin
On 15.09.21 12:31, Khelben Blackstaff wrote:
Greetings.
In the last 6-7 snapshots, i noticed some packages being constantly "upgraded" without appearing in the changelog. There are packages like that many times because some library they are depending on was upgraded and so they had to be recompiled or something like that.
It doesn't seem to be the case this time though. There are quite a few packages but i mainly noticed it due to wine-mono which in my mind doesn't depend on libraries and doesn't need to be recompiled. I also did a check with zypper / rpm and it seems to only depend on wine.
% cd /var/cache/zypp/packages/non-oss/noarch % ls -al wine-mono-6.3.0-1.* -rw-r--r-- 1 root root 64502590 Aug 4 10:32 wine-mono-6.3.0-1.1.noarch.rpm -rw-r--r-- 1 root root 64502587 Sep 5 08:33 wine-mono-6.3.0-1.2.noarch.rpm -rw-r--r-- 1 root root 64502573 Sep 9 08:42 wine-mono-6.3.0-1.4.noarch.rpm -rw-r--r-- 1 root root 64502582 Sep 10 08:52 wine-mono-6.3.0-1.5.noarch.rpm -rw-r--r-- 1 root root 64502589 Sep 12 13:25 wine-mono-6.3.0-1.6.noarch.rpm -rw-r--r-- 1 root root 64502588 Sep 14 16:33 wine-mono-6.3.0-1.7.noarch.rpm -rw-r--r-- 1 root root 64502584 Sep 15 09:08 wine-mono-6.3.0-1.8.noarch.rpm
Here are the packages i have in my cache. As you see, it got upgraded pretty much on every snapshot.
the reason is the broken new rpmlint not worked around in build-compare, which lets OBS publish all these rebuilds even if they are the same... @factory_maintainers: can we please revert the rpmlint stuff until at least build-compare is fixed? -- Stefan Seyfried "For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." -- Richard Feynman
On Thu, 2021-09-23 at 13:57 +0200, Stefan Seyfried wrote:
the reason is the broken new rpmlint not worked around in build-compare, which lets OBS publish all these rebuilds even if they are the same...
@factory_maintainers: can we please revert the rpmlint stuff until at least build-compare is fixed?
The fix for build-compare is already in a staging and should find its way into Factory rather soon. So no need to revert anything. Cheers, Dominique
participants (4)
-
Dominique Leuenberger / DimStar -
Khelben Blackstaff -
Martin Wilck -
Stefan Seyfried