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

Re: Trying to use SP Flash Tool (Mediatek), latest version requires libpng12-0, which is not available

On Tue, Sep 18, 2018 at 02:08:59PM +0000, Curt wrote:
> I read Greg W's theory regarding this error, but then saw this
> thread
> https://unix.stackexchange.com/questions/331803/cannot-install-libpng12-0-on-debian/331975
> in which an unfortunate user fails to install the Jessie version of the
> package in question (in Stretch), encountering the same (or very
> similar) error as you did (the reasons for which escape my
> understanding, however, so sadly no help from this quarter on that
> score, except to say the OP of the thread above went back to Wheezy for
> his libpng12.so.0 with success).

OK, I do not understand this at all.  I've got a stretch system here
with jessie's libpng12-0 package installed.  However, I do not know
whether this system was installed as jessie and then upgraded, or
installed as stretch, and then the package added later.

wooledg:~$ cat /etc/debian_version 

wooledg:~$ dpkg -l libpng\* | cat
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name              Version         Architecture Description
ii  libpng12-0:amd64  1.2.50-2+deb8u3 amd64        PNG library - runtime
un  libpng12-dev      <none>          <none>       (no description available)
ii  libpng16-16:amd64 1.6.28-1        amd64        PNG library - runtime (version 1.6)

wooledg:~$ ls -l /usr/lib/x86_64-linux-gnu/libpng12.so.0 
lrwxrwxrwx 1 root root 35 Jan  6  2017 /usr/lib/x86_64-linux-gnu/libpng12.so.0 -> /lib/x86_64-linux-gnu/libpng12.so.0

wooledg:~$ dpkg -l | grep deb8
ii  libdns-export100                      1:9.9.5.dfsg-9+deb8u10            amd64        Exported DNS Shared Library
ii  libhogweed2:amd64                     2.7.1-5+deb8u2                    amd64        low level cryptographic library (public-key cryptos)
ii  libicu52:amd64                        52.1-8+deb8u4                     amd64        International Components for Unicode
ii  libirs-export91                       1:9.9.5.dfsg-9+deb8u10            amd64        Exported IRS Shared Library
ii  libisc-export95                       1:9.9.5.dfsg-9+deb8u10            amd64        Exported ISC Shared Library
rc  libisc95                              1:9.9.5.dfsg-9+deb8u10            amd64        ISC Shared Library used by BIND
rc  libisccc90                            1:9.9.5.dfsg-9+deb8u10            amd64        Command Channel Library used by BIND
ii  libisccfg-export90                    1:9.9.5.dfsg-9+deb8u10            amd64        Exported ISC CFG Shared Library
rc  libjasper1:amd64                      1.900.1-debian1-2.4+deb8u3        amd64        JasPer JPEG-2000 runtime library
rc  liblwres90                            1:9.9.5.dfsg-9+deb8u10            amd64        Lightweight Resolver Library used by BIND
ii  libnettle4:amd64                      2.7.1-5+deb8u2                    amd64        low level cryptographic library (symmetric and one-way cryptos)
ii  libpng12-0:amd64                      1.2.50-2+deb8u3                   amd64        PNG library - runtime
ii  libssl1.0.0:amd64                     1.0.1t-1+deb8u6                   amd64        Secure Sockets Layer toolkit - shared libraries
rc  libxapian22                           1.2.19-1+deb8u1                   amd64        Search engine library
rc  perl-modules                          5.20.2-3+deb8u6                   all          Core Perl modules

That seems like a rather nontrivial number of jessie updates (deb8),
mostly removed, so maybe this was originally a jessie system?  I don't

Of course, if all else fails, you can grab the jessie .deb file, unpack
it manually in /tmp (or wherever you like), copy the shared library files
to where they're supposed to be, create the symlinks that are supposed
to be created, and run ldconfig.

If you're feeling especially bold, you could even try to install the
.deb package *after* that.  Maybe having the files and symlinks already
in place will somehow help it along.

Reply to: