I did a fresh install of TW 20230222 on a new PC. My main desktop which was installed back in 2021 has also been updated ( zypper dup ) to 20230222. I found something odd when comparing packages between the 2 machines. Both PC's have wine installed, however... On my main desktop when the original install in 2021 of wine was done it installed libz1-32bit ( as per the zypper history logs ) and it still has that installed after it was updated to 20230222. On the new PC fresh install of 20230222 when wine was installed it installed libz-ng-compat1-32bit. The libz-ng-compat1-32bit version looks like it was forked in 2021, just after my main machine was originally built so that would explain why it has libz1-32bit but shouldn't it have been updated by zypper dup ??? Is this a bug that I should report? If so, which system is wrong / which version should be used? Thanks!
One other piece of information.... Both the new fresh install of TW and the older machine both have the same libz1 64 bit version installed. So a fresh TW install gets libz1 libz-ng-compat1-32bit and the older updated machine has libz1 libz1-32bit Seems like the fresh install is getting it wrong and that it should be using the same version of the library for 64 and 32 bit.
* On 3/1/23 21:36, Joe Salmeri wrote:
Both the new fresh install of TW and the older machine both have the same libz1 64 bit version installed.
So a fresh TW install gets
libz1 libz-ng-compat1-32bit
and the older updated machine has
libz1 libz1-32bit
Seems like the fresh install is getting it wrong and that it should be using the same version of the library for 64 and 32 bit.
Just a quick observation: zlib-ng is supposed to be a drop-in replacement for zlib, so this shouldn't cause any issues. The first stable release for zlib-ng came out in 2021, so it probably makes sense that the older machine just pulled in zlib in both variants when you installed it. Nowadays, zlib-ng is available, and some packages might have hardcoded dependencies on zlib itself (which is probably why zlib was preferred for you main architecture), while others have less strict dependencies, such as a dependency on the library name only. libsolv probably chose zlib-ng-compat1-32bit instead of libz1-32bit because they were equivalent (i.e., only library name dependencies, that both packages would provide), but zlib-ng-compat1-32bit's own dependencies might have been easier to satisfy (less dependencies), so this choice makes sense. This said, at least in that case, you probably don't have to worry about mismatched packages. "Getting it wrong" isn't accurate here. libsolv actually found a workable solution. Mihai
Thanks Mihai, I was aware that the ng version is supposed to be a drop replacement and your conclusions seem to match mine for why the older machine doesn't have the ng versions installed. What puzzles me is why libsolv picked libz1 for 64 bit and libz-ng for the 32bit. Your explanation might be the reason but if the ng version is a drop in replacement it seems like that shouldn't matter.
Am Donnerstag, 22. Februar 2024, 10:15:27 CET schrieb deeplymonth7822@gmail.com:
I love this post! https://suikagameonline.io
looks like spam.....
On 2024-02-22 12:17, Axel Braun wrote:
Am Donnerstag, 22. Februar 2024, 10:15:27 CET schrieb deeplymonth7822@gmail.com:
I love this post! https://suikagameonline.io
looks like spam.....
Yes. They are getting in via the hyperkitty web interface to the mail list, using the identification via gmail, AFAIK. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
participants (5)
-
Axel Braun -
Carlos E. R. -
deeplymonth7822＠gmail.com -
Joe Salmeri -
Mihai Moldovan