On 12 July 2012 21:17, Evangelos Foutras <evangelos@foutrelis.com> wrote:
On Thu, Jul 12, 2012 at 11:08 PM, Mateusz Loskot <mateusz@loskot.net> wrote:
I'm running current Arch 64-bit and I'm trying to install the AfterShot Pro [0] using aftershotpro 1.0.1.10-1 [1]
First obstacle is this:
$ makepkg -s ==> Making package: aftershotpro 1.0.1.10-1 (Thu Jul 12 20:42:48 BST 2012) ==> Checking runtime dependencies... ==> Installing missing dependencies... error: target not found: lib32-libpng12 ==> ERROR: 'pacman' failed to install missing dependencies.
You need to install lib32-libpng12 from the AUR.
Done.
The Dependencies section on the package page [1] does not list lib32-libpng12 but libpng12 only. So, searching for lib32-libpng12 [2], but attempt to install it results in this:
If you look at the PKGBUILD, the dependencies are overridden with their multilib counterparts when the host's architecture is x86_64. AUR just displays the original dependencies (which apply to i686).
I see, my ignorance of solely 64-bit made me expect lib32-* :)
$ makepkg -s ==> Making package: lib32-libpng12 1.2.49-1 (Thu Jul 12 20:45:54 BST 2012) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Installing missing dependencies... resolving dependencies... looking for inter-conflicts... :: gcc-libs-multilib and gcc-libs are in conflict. Remove gcc-libs? [y/N] error: unresolvable package conflicts detected error: failed to prepare transaction (conflicting dependencies) :: gcc-libs-multilib and gcc-libs are in conflict ==> ERROR: 'pacman' failed to install missing dependencies.
Does anyone know how to get around it?
Allow pacman to replace gcc-libs with gcc-libs-multilib. (Do the same for the rest of the toolchain when prompted.)
OK, done. After that, AfterShot Pro installation from the AUR package went smooth.
The package aftershotpro 1.0.1.10-1 is 32-bit installs 32-bit version of the software from AfterShotPro_i386.rpm, but there is package for Linux Debian (64-bit) available [3]. I wonder if the maintainer could update the package using the 64-bit deb.
Let them know in the comments section.
Done, and received prompt response [1] saying: "the debian 64 bit package is not 64 bit, but 32 bit with all needed 32 bit libraries packaged" So, everything is clear now. [1] https://aur.archlinux.org/packages.php?ID=55712 Thanks for help! Best regards, -- Mateusz Loskot, http://mateusz.loskot.net