I have not had access to my Linux computer for 5 weeks due to some personal issues. ( I am not in jail, LOL! but still married, which is probably worse ).
But every day, I try to read the Rawhide reports and look for subtle easy things that I feel I need to learn, all of which are way way over my 72 I.Q.
For example:
In todays Rawhide email, the package below was compiled for fc34:
Package: mingw-libidn2-2.3.0-3.fc34 Old package: mingw-libidn2-2.3.0-3.fc33 Summary: MinGW Windows Internationalized Domain Name 2008 support library RPMs: mingw32-libidn2 mingw32-libidn2-static mingw64-libidn2 mingw64-libidn2-static Size: 549.89 KiB Size change: 54 B
First question: Why would size change 54 B ? I think I read somewhere that tiny fluctuations happen during a re-compile. Right ?
Second question: Why did file-version not change ? I assume because no code changed. Right ??
I would be interested in reading a weekly or bi-weekly or monthly "story" that was interesting to read about what Rawhide offers that 33 does not, or something along those lines. Like which packages had a huge update, or why a git-version was replaced with a stable-version, etc.
Cheers,
David Locklear
Why would size change 54 B ? I think I read somewhere that tiny
fluctuations happen during a re-compile. Right ?
Second question: Why did file-version not change ? I assume because
no code changed. Right ??
As mingw is a package which has the following dependencies for build time: https://src.fedoraproject.org/rpms/mingw-libidn/blob/master/f/mingw-libidn.s... , and if there's an updated version of the dependency on the build system, the resultant library can differ in size.
-- Nasir Hussain
On Mon, Dec 28, 2020 at 5:12 AM David dlocklear01@gmail.com wrote:
I have not had access to my Linux computer for 5 weeks due to some personal issues. ( I am not in jail, LOL! but still married, which is probably worse ).
But every day, I try to read the Rawhide reports and look for subtle easy things that I feel I need to learn, all of which are way way over my 72 I.Q.
For example:
In todays Rawhide email, the package below was compiled for fc34:
Package: mingw-libidn2-2.3.0-3.fc34 Old package: mingw-libidn2-2.3.0-3.fc33 Summary: MinGW Windows Internationalized Domain Name 2008 support library RPMs: mingw32-libidn2 mingw32-libidn2-static mingw64-libidn2 mingw64-libidn2-static Size: 549.89 KiB Size change: 54 B
First question: Why would size change 54 B ? I think I read somewhere that tiny fluctuations happen during a re-compile. Right ?
Second question: Why did file-version not change ? I assume because no code changed. Right ??
I would be interested in reading a weekly or bi-weekly or monthly "story" that was interesting to read about what Rawhide offers that 33 does not, or something along those lines. Like which packages had a huge update, or why a git-version was replaced with a stable-version, etc.
Cheers,
David Locklear _______________________________________________ test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
On Sun, 2020-12-27 at 18:09 -0600, David wrote:
Second question: Why did file-version not change ? I assume because no code changed. Right ??
No, actually. What happened is that someone changed the spec file and sent a new build, but didn't bump the release or edit the changelog:
https://src.fedoraproject.org/rpms/mingw-libidn2/c/473f6d26e4eba15c613cef226...
usually if you do that Koji will reject the build attempt because it has the same NVR as an existing build - but because the last time the package was built was before F33 branching, the new build had a *different* NVR (fc34 vs. fc33) and was accepted even though the release wasn't bumped. This is technically an error on the packager's part, though it doesn't have any real terrible consequences except the build not being recorded in the changelog.
Thank You Adam for correcting me and sharing what actually happened.
-- Nasir Hussain
On Mon, Dec 28, 2020 at 10:42 PM Adam Williamson adamwill@fedoraproject.org wrote:
On Sun, 2020-12-27 at 18:09 -0600, David wrote:
Second question: Why did file-version not change ? I assume because no code changed. Right ??
No, actually. What happened is that someone changed the spec file and sent a new build, but didn't bump the release or edit the changelog:
https://src.fedoraproject.org/rpms/mingw-libidn2/c/473f6d26e4eba15c613cef226...
usually if you do that Koji will reject the build attempt because it has the same NVR as an existing build - but because the last time the package was built was before F33 branching, the new build had a *different* NVR (fc34 vs. fc33) and was accepted even though the release wasn't bumped. This is technically an error on the packager's part, though it doesn't have any real terrible consequences except the build not being recorded in the changelog. -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net
test mailing list -- test@lists.fedoraproject.org To unsubscribe send an email to test-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
On Mon, 2020-12-28 at 22:49 +0500, Nasir Hussain wrote:
Thank You Adam for correcting me and sharing what actually happened.
Hi Nasir! Your reply is perfectly correct regarding a possible cause of the size change, I just answered a different question which David also asked.