tickvue and Ubuntu 16.04

[Ralf Mardorf]

On Thu, 6 Oct 2016 11:57:33 +0200, Ralf Mardorf wrote:
>Hi,
>
>http://packages.ubuntu.com/ doesn't find tickvue by official
>repositories.
>
>Run
>
>dpkg -I /var/cache/apt/archives/package_name.deb
>
>to get a list of the libraries that are required. However, the
>information ">=" not necessarily means that each lib ">" necessarily
>will work. Chances are good that if it requires e.g. libfoo (>= 1.0)
>and Ubuntu 16.04 should provide libfoo (>= 1.5), that it will still
>work, but it unlikely would be still usable, assuming the so
>called "soname" changed, IOW not the dot release, but the major
>release, so if Ubuntu 16.04 should provide libfoo (>= 2.0), it unlikly
>would run.
>
>You could backup such a lib
>
>libfoo.so -> libfoo.so.1.0.0
>libfoo.so.1 -> libfoo.so.1.0.0
>libfoo.so.1.0.0
>
>Don't backup and restore "libfoo.so", this is only needed to build and
>should be used from the new package. But backup and restore libfoo.so.1
>and libfoo.so.1.0.0. You need to run
>
>  sudo ldconfig
>
>after restoring the lib and link.
>
>You could see, if this should be required by taking a look at the
>version of the libs at http://packages.ubuntu.com/ .
>
>If you don't have the package available in /var/cache/apt/archives/ or
>any other pass, the info provided by
>
>apt-cache showpkg pluma | grep -A1 Dependencies:
>
>does the job, too. The missing ">=" are not that important. Again,
>usually different dot release don't break a package, but if the major
>release changed you unlikely could contiue using the package, resp. you
>need to copy the old libraries.
>
>There's still a handicap for the package management, since the package
>providing tickvue does confuse the package management, assuming that
>Ubuntu 16.04 shouldn't provide the required dependencies.
>
>Copy the files of the package, listed by
>
>dpkg -L
>
>then remove the package and restore the files on Ubuntu 16.04, don't
>try to reinstall the package.

PS:

Assuming there should be a version problem regarding a dependency that
isn't a lib, you could have good luck, it might not matter, however,
start with comparing the required and provided libs.