SliTaz SliTaz Forum

You are not logged in.

#1 2011-11-27 14:21:30

Saipul
Member
Registered: 2011-06-28
Posts: 87

libpng-1.4.8 upgrade breaks all tazpkgs built against libpng-1.2.XX

before I post this, I have check in the hg repository and in the packages repository, but unfortunately I think the hg repository is down and can not access them. So I look at in packages repository any libpng-1.4.8 in there, but still a lot of packages in the repository using dependency libpng-1.2.44 or build dependency libpng-1.2.44-dev.

For example i run command:

$ ldd /usr/bin/slim

/usr/bin/slim:

    linux-gate.so.1 =>  (0xffffe000)

    libXft.so.2 => /usr/lib/libXft.so.2 (0xb777f000)

    libX11.so.6 => /usr/lib/libX11.so.6 (0xb7684000)

    libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb761f000)

    libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb7617000)

    libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb75ef000)

    libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb75d2000)

    libz.so.1 => /usr/lib/libz.so.1 (0xb75c1000)

    libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7590000)

    libXmu.so.6 => /usr/lib/libXmu.so.6 (0xb757e000)

    libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0xb7554000)

    librt.so.1 => /lib/librt.so.1 (0xb754b000)

    libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb747f000)

    libm.so.6 => /lib/libm.so.6 (0xb7459000)

    libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb7442000)

    libc.so.6 => /lib/libc.so.6 (0xb72fe000)

    libpthread.so.0 => /lib/libpthread.so.0 (0xb72e6000)

    libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb72c8000)

    libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb72b1000)

    libXau.so.6 => /usr/lib/libXau.so.6 (0xb72ae000)

    libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb72a9000)

    libdl.so.2 => /lib/libdl.so.2 (0xb72a5000)

    libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0xb7295000)

    libXt.so.6 => /usr/lib/libXt.so.6 (0xb7252000)

    libSM.so.6 => /usr/lib/libSM.so.6 (0xb724c000)

    libuuid.so.1 => /lib/libuuid.so.1 (0xb7248000)

    libICE.so.6 => /usr/lib/libICE.so.6 (0xb7235000)

    libXext.so.6 => /usr/lib/libXext.so.6 (0xb7228000)

    /lib/ld-linux.so.2 => /lib/ld-2.13.so (0xb7790000)

slim still using old libpng:

libpng12.so.0 => /usr/lib/libpng12.so.0 (0xb75d2000)

but no new packages or upgraded packages in repository using new libpng.

And for that I run command:

# tazpkg block libpng

# tazpkg recharge

# tazpkg upgrade

Yes just new gdbm package has upgraded.

Offline

#2 2011-11-27 18:09:57

Trixar_za
Administrator
Registered: 2011-03-29
Posts: 1,506

Re: libpng-1.4.8 upgrade breaks all tazpkgs built against libpng-1.2.XX

Well, the obvious question is how did you get the latest libpng and where. The SliTaz cooking repository only has libpng-1.2.44, so it's to be expected that all the applications would be compiled to use it.

Secondly, a simple symlink to the name libpng12.so.0 should fix this.

Offline

#3 2011-11-27 19:08:46

mojo
Administrator
Registered: 2011-03-29
Posts: 2,174

Re: libpng-1.4.8 upgrade breaks all tazpkgs built against libpng-1.2.XX

@Trixar_za

libpng-1.4.8 is on the cooking repo.

Symlinking doesn't work, libpng-1.4 is not compatible with libpng-1.2

The same issue happened 15 months ago:

http://mirror.slitaz.org/hg/hgwebdir.py/wok/rev/cab8d2e3649f

Reverted 10 hours later:

http://mirror.slitaz.org/hg/hgwebdir.py/wok/rev/1d0b57b25fe0

Online

#4 2011-11-27 21:16:13

Trixar_za
Administrator
Registered: 2011-03-29
Posts: 1,506

Re: libpng-1.4.8 upgrade breaks all tazpkgs built against libpng-1.2.XX

But the package search web-interface shows 1.2.44...

Do we have people committing to the package repository before testing again?

Offline

Registered users online in this topic: 0, guests: 1
[Bot] ClaudeBot

Board footer

Powered by FluxBB
Modified by Visman

[ Generated in 0.019 seconds, 7 queries executed - Memory usage: 1.54 MiB (Peak: 1.77 MiB) ]