Package Details: lib32-libtiff4 3.9.7-6

Git Clone URL: https://aur.archlinux.org/lib32-libtiff4.git (read-only, click to copy)
Package Base: lib32-libtiff4
Description: Library for manipulation of TIFF images
Upstream URL: http://www.simplesystems.org/libtiff/
Licenses: custom
Submitter: City-busz
Maintainer: voxan24
Last Packager: City-busz
Votes: 7
Popularity: 2.97
First Submitted: 2025-10-28 10:43 (UTC)
Last Updated: 2026-01-11 00:58 (UTC)

Latest Comments

1 2 Next › Last »

ninetailedtori commented on 2026-01-12 02:35 (UTC) (edited on 2026-01-12 02:35 (UTC) by ninetailedtori)

Hunk failure (upstream change not reflected correctly in pkgbuild), please fix.

patching file configure.ac
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file configure.ac.rej
==> ERROR: A failure occurred in prepare().
    Aborting...
 -> error making: lib32-libtiff4-exit status 4

oxalin commented on 2026-01-11 01:21 (UTC) (edited on 2026-01-17 17:58 (UTC) by oxalin)

You don't want to overwrite files provided by native packages unless you add "conflicts" in PKGBUILD.

I looked at the libraries shipped with Steam itself. While "libtiff4" was a prerequisite at some point to provide SONAME version 3.9.X, it seems the latest Steam uses libtiff.so.4.3.4. Have a look under ~/.local/share/Steam/ubuntu12_32

From what I've found going over the libtiff's commits, somewhere around version 4.0.0, the libtiff's developers changed the SONAME version not because they broke the API compatibility or the symbol version, but to support the library symbol versioning under GNU systems which was then optional for a time. It seems Steam was updated properly since then.

That being said, updating to the latest libtiff version could cause problem because the SONAME version was updated to 6.X.Y since version 4.5.0 because "SONAME version bumped to 6 due to changes in symbol versioning". I don't quite understand why the version was not updated at the same time. Steam ships with 4.3.4, so as long as a libtiff.so.4.X.Y is provided, it should be fine.

If libtiff-4 is to be updated, it may have to be limited to a version prior to 4.5.0 (SONAME version must match).

City-busz commented on 2026-01-11 01:03 (UTC)

@voxan24: I reverted your changes. As aboldone stated, this package should provide the legacy libtiff 3.9.x version (libtiff.so.4), NOT the current 4.7.x version. Please don't upgrade this package to a newer version that provides a different soname.

@luis.brito: Your system will be broken if you overwrite those files. You should reinstall lib32-libtiff, and the old version of lib32-libtiff4.

luis.brito commented on 2026-01-11 00:42 (UTC) (edited on 2026-01-11 00:44 (UTC) by luis.brito)

To resolve conflicting file issues

yay -Syyuu --overwrite '*'

ixvari commented on 2026-01-11 00:19 (UTC)

Just adding that I'm seeing the exact same error as amiablechief

amiablechief commented on 2026-01-11 00:10 (UTC) (edited on 2026-01-11 00:15 (UTC) by amiablechief)

Package (2)           Old Version  New Version  Net Change

lib32-libtiff4        3.9.7-6      4.7.1-1        0.17 MiB

lib32-libtiff4-debug               4.7.1-1        3.24 MiB



Total Installed Size:  3.80 MiB

Net Upgrade Size:      3.40 MiB



:: Proceed with installation? [Y/n] Y

(2/2) checking keys in keyring                                                                                     
[---------------------------------------------------------------------] 100%

(2/2) checking package integrity                                                                                   
[---------------------------------------------------------------------] 100%

(2/2) loading package files                                                                                        
[---------------------------------------------------------------------] 100%

(2/2) checking for file conflicts                                                                                  
[---------------------------------------------------------------------] 100%

error: failed to commit transaction (conflicting files)

lib32-libtiff4: /usr/lib32/libtiff.so.6 exists in filesystem (owned by lib32-libtiff)

lib32-libtiff4: /usr/lib32/libtiff.so.6.2.0 exists in filesystem (owned by lib32-libtiff)

lib32-libtiff4: /usr/lib32/libtiffxx.so.6 exists in filesystem (owned by lib32-libtiff)

lib32-libtiff4: /usr/lib32/libtiffxx.so.6.2.0 exists in filesystem (owned by lib32-libtiff)

lib32-libtiff4: /usr/lib32/pkgconfig/libtiff-4.pc exists in filesystem (owned by lib32-libtiff)

Errors occurred, no packages were upgraded.

aboldone commented on 2026-01-10 22:02 (UTC)

The update to version 4.7.1 is incorrect and breaks the package.

This package should provide the legacy libtiff 3.9.x version (libtiff.so.4), NOT the current 4.7.x version.

Version 4.7.1 creates libtiff.so.6 which conflicts with multilib/lib32-libtiff: - lib32-libtiff (official multilib) provides libtiff.so.6 - lib32-libtiff4 (AUR) should provide libtiff.so.4 for legacy compatibility

Installing 4.7.1 fails with:

Error: Conflicting files lib32-libtiff4: /usr/lib32/libtiff.so.6 exists in filesystem (owned by lib32-libtiff)

Please revert to pkgver=3.9.7 with the old source URL or use a working mirror.

The package is a dependency of steam-native-runtime which requires BOTH lib32-libtiff (current) AND lib32-libtiff4 (legacy 3.9.x) to coexist.

rallo commented on 2026-01-10 21:37 (UTC)

patching file configure.ac
Hunk #1 FAILED at 39.
1 out of 1 hunk FAILED -- saving rejects to file configure.ac.rej

I'm also getting this issue with the build still.

voxan24 commented on 2026-01-10 20:54 (UTC)

and it build in my machine