[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fitspng autopkgtest regression fail, Bug #1059970



Hi Filip,

On 17-01-2024 15:21, Filip Hroch wrote:
I'm asking for help with solving of Bug #1059970 (see [1])
with the issue:

    check FAIL stderr: zlib warning: different version (expected
    1.2.13, using 1.3)

One is, in my opinion, caused by indirect linking of the zlib
by libcfitsio-dev and libpng-dev; libcfitsio-dev is linked
against zlib1g (>= 1:1.1.4), whilst libpng-dev against
zlib1g (= 1:1.3.dfsg-3).

Is there a a way how to solve this kind of troubles?

There are multiple angles to your question: which troubles do you want to solve? In my opinion, in Debian the best solution is to remove the warning if it's harmless that the version mismatch (which probably should just be removed upstream too). You *should* have tests in place now that tell you that the package is working as intended, "proving" it's harmless. If, for some reason, there are serious issues with the version skew that are *not* caught by your test, than the warning isn't going to help the user of Debian packages much either way. If there should really be a version lock, than your package should declare that in its relations (versioned Depends), such that the Release Teams tools pick it up an a rebuild can be scheduled. But I really think this last option is probably the wrong solution.

If you just want to prevent the test from failing on a warning, you can use the allow-stderr restriction.

Paul

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059970

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


Reply to: