Hi, unsure why this was removed.

Adding David W. who removed it according to above changelog.

CC: (none) => luigiwalser, ouaurelien
Status: NEW => NEEDINFO

My only guess is the addition of this function broke the build of other packages, as we were preparing the Mageia 6 release.  Hopefully more than four years later, whatever packages were having an issue with it would have adapted by now.  We should remove the patch in Cauldron and see what happens.

Version: 8 => Cauldron

Done for Cauldron!

CC: (none) => geiger.david68210

Assigning globally.

@ reporter, it seems it was build for Cauldron. Can you try it in a VM with Cauldron?

Assignee: bugsquad => pkg-bugs

Thanks very much dear maintainers. I'm impressed by the speedy follow-up.

Sure I can try along the way you sketched, BUT:
1. First installing a complete Mageia Cauldron,
2. Next, installing all of Octave's dependencies + building Octave,
is a bit beyond available time ATM; within a few days I'll be away until May 17. Somewhere in that week I can do it.

Would it be possible to just replace the lib64zlib.so.<version> library + include/zlib.h in installed Mageia-8, without provoking a kernel panic? (I suppose zlib is required to uncompress the kernel?)

That should be possible, or you can rebuild it Mageia 8 zlib package without the patch locally on your system.  As we won't be updating Octave on Mageia 8, I don't see the need to officially backport this change, so we can probably close this once we've confirmed that it fixes your issue without causing any others.

OK I'll see what's the easiest for me in available time. Could be 2nd half of May before I get back.
I think you're quite right there's no reason for a zlib backport yet. No one seems to have needed uncompress2 for > 4 years anyway :-)

Right, I rebuilt zlib from source PM and replaced libz.so.1.2.11 (+ zlib.h & zconf.h).
Result: Octave-7.0.0 could be built fine.
But also KDE/Plasma seemed to become less stable; AFAICS notably with screen locking or refreshing screen background. The rest of Mageia seemed to run fine while Octave got built (and then cross-built for windows using mxe-octave).

Obviously replacing a vital core library is risky, so it would be better to try with Cauldron but I can do that only later this month.

Until now I've had no opportunity to install cauldron somewhere; one issue is that my systems simply have insufficient space for a (another) VM.
I've installed the fixed libz both on my desktop (see comment #8) and on a laptop some months ago. The KDE/Plasma effects mentioned above might be related to other issues with configuring dual screens on that box [*], on my laptop I haven't seen any adverse effects.

BTW are there any live media for Cauldron? or are live media made only for formal releases?

[*] https://forums.mageia.org/en/viewtopic.php?t=13853

No there's no live media until we get into the release process.  Maybe some day with a newer build system we could have some continuous integration thing spitting out Live media periodically, but that's just a dream at this point.

The best ways to install Cauldron are to install Mageia 8 and upgrade to Cauldron or to do a "netinstall" (using the boot.iso / all.img stage 1 of the installer to bootstrap the rest over the network).

Cauldron is a bit broken at the moment however, since webkit2 won't build.

OK, thanks, I was busy freeing up space but I'll wait a little then until Cauldron is more stable.
Apart from that last verification step, I've built dev Octave regularly the last months so maybe this bug report can be closed? I suppose that *if* the "un"patched libz (= incl. uncompress2) didn't provoke any issues in the Cauldron builds lately it does no harm.
That said, I'm still willing to try Cauldron at some point if you wish so.

BTW, before I forget: my desktop has Mageia-8, my laptop still runs Mageia-7. Both have the libz incl. uncompress2. On my laptop I haven't noted anything unusual, on my desktop I see some Plasma issues but again those may well be unrelated.

OK, webkit2, qtwebengine5, and digikam have all been fixed, so once the fixed packages get out to the mirrors (should be good by tomorrow), Cauldron should be safe to install again.

Cauldron (netinstall CD d/led today) won't install in VBox, gives a popup "26 installation transactions failed" followed (after clicking OK) by a message along the lines of "ldconfig failed" or "ldconfig error".
AFAIK I've set disk size to dynamic so it shouldn't be space issue.
Hmm ...

Anyway what was the whole idea behind asking me to "try it in a VM with Cauldron" (comment #4)? Attempting to build dev Octave? that'll be a little biggie compared to just trying some random piece of SW as Octave needs quite a few dependencies & build tools.

Yes, we wanted to confirm that we've fixed your issue without causing others.  So, you can try building Octave in a Cauldron installation, or if you're packaging it as an rpm, you could use mock to build it for Cauldron from Mageia 8.  We'll need to check the autobuild logs to make sure it hasn't broken anything.

(In reply to David Walser from comment #2)
> My only guess is the addition of this function broke the build of other
> packages, as we were preparing the Mageia 6 release.  Hopefully more than
> four years later, whatever packages were having an issue with it would have
> adapted by now.  We should remove the patch in Cauldron and see what happens.

For once it broke swish-e:
https://pkgsubmit.mageia.org/autobuild/history.php?package=swish-e

I've fixed the symbols clash in swish-e:
http://svnweb.mageia.org/packages/cauldron/swish-e/current/SOURCES/fix-build-with-zlib.patch?view=markup&pathrev=1749653

But there might be other breakages lurking..
One could look at the other "new" breakages from https://pkgsubmit.mageia.org/autobuild/results.php?run=2021-04-27

CC: (none) => thierry.vignaud

I've tried a few times to install cauldron in a Virtual Box VM but it didn't work, it hang somewhere before the choice of packages.

Anyway I've installed the unpatched libz.so (that is w/o the removal-of-uncompress2-patch) in two Mageia-8 (and before that in two Mageia-7) installations and I didn't note any failures. But of course that's n=1.

As uncompress2 is contained in libz.so in several other Linux distros I've been trying lately I wonder what breakages could be related to it.
For me it just works now.

(In reply to Thierry Vignaud from comment #16)
> (In reply to David Walser from comment #2)
> > My only guess is the addition of this function broke the build of other
> > packages, as we were preparing the Mageia 6 release.  Hopefully more than
> > four years later, whatever packages were having an issue with it would have
> > adapted by now.  We should remove the patch in Cauldron and see what happens.
> 
> For once it broke swish-e:
> https://pkgsubmit.mageia.org/autobuild/history.php?package=swish-e
> 
> I've fixed the symbols clash in swish-e:
> http://svnweb.mageia.org/packages/cauldron/swish-e/current/SOURCES/fix-build-
> with-zlib.patch?view=markup&pathrev=1749653
> 
> But there might be other breakages lurking..
> One could look at the other "new" breakages from
> https://pkgsubmit.mageia.org/autobuild/results.php?run=2021-04-27

Right idea, but the one to look at is actually this one:
https://pkgsubmit.mageia.org/autobuild/results.php?run=2017-01-05

Unfortunately most of the build logs are gone, and the only other ones besides swish-e that look zlib related are R-base and clamav, but those are only because the zlib version changed for the first time in forever and the version detection code in those packages' build systems was broken (they were expecting a single digit for the third component which had just become 1.2.10).

Closing as the feature is said to be included.

Resolution: (none) => FIXED
Status: NEEDINFO => RESOLVED
CC: (none) => yvesbrungard

OP here.
Thanks for fixing!