Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#23325 - libtool reordering LDFLAGS and breaking as-needed linking

Attached to Project: Pacman
Opened by Lukas Fleischer (lfleischer) - Friday, 18 March 2011, 12:57 GMT
Last edited by Dan McGee (toofishes) - Sunday, 20 March 2011, 16:58 GMT
Task Type Bug Report
Category Backend/Core
Status Closed
Assigned To Dan McGee (toofishes)
Architecture All
Severity High
Priority Normal
Reported Version 3.5.0
Due in Version 3.5.1
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

New Description:

libalpm links to many additional libraries in pacman-3.5 compared to pacman-3.4.


Old Description:
pacman 3.5.0 only depends on libarchive 2.8.0 which causes breakage if you do a full system upgrade after a fresh install as xz had a soname bump and pacman requires "liblzma.so.5" (whereas the xz-utils package libarchive 2.8.0 depends on only provides "liblzma.so.0"). Please ensure we pull in xz-5.x.0 to ensure pacman doesn't break.

Additional info:
* pacman 3.5.0


Steps to reproduce:
See http://mailman.archlinux.org/pipermail/pacman-dev/2011-March/012682.html.
This task depends upon

Closed by  Dan McGee (toofishes)
Sunday, 20 March 2011, 16:58 GMT
Reason for closing:  Fixed
Additional comments about closing:  Commit b0f9477f01a5639
Comment by Lukas Fleischer (lfleischer) - Friday, 18 March 2011, 12:57 GMT
Would be nice if that would be fixed before we move pacman to [core].
Comment by Ionut Biru (wonder) - Friday, 18 March 2011, 13:18 GMT
does libalpm really needs to link to liblzma.so.5 ? pacman 3.4 only links to libarchive
Comment by Ionut Biru (wonder) - Friday, 18 March 2011, 13:19 GMT
pacman 3.4

/usr/lib/libalpm.so.5.0.3 -- libfetch.so
/usr/lib/libalpm.so.5.0.3 -- libarchive.so.2
/usr/lib/libalpm.so.5.0.3 -- libc.so.6


pacman 3.5

/usr/lib/libalpm.so.6.0.0 -- libfetch.so
/usr/lib/libalpm.so.6.0.0 -- libssl.so.1.0.0
/usr/lib/libalpm.so.6.0.0 -- libarchive.so.2
/usr/lib/libalpm.so.6.0.0 -- libacl.so.1
/usr/lib/libalpm.so.6.0.0 -- libattr.so.1
/usr/lib/libalpm.so.6.0.0 -- libexpat.so.1
/usr/lib/libalpm.so.6.0.0 -- liblzma.so.5
/usr/lib/libalpm.so.6.0.0 -- libbz2.so.1.0
/usr/lib/libalpm.so.6.0.0 -- libz.so.1
/usr/lib/libalpm.so.6.0.0 -- libcrypto.so.1.0.0
/usr/lib/libalpm.so.6.0.0 -- libc.so.6
Comment by Lukas Fleischer (lfleischer) - Friday, 18 March 2011, 13:58 GMT
Ionut: Right, `git bisect`'ed that one. Seems like this was introduced with commit f489e969 [1], when upgrading autotools (was kinda obvious). This is a huge patch set tho and I don't have enough time to figure out where this originates from. Maybe Dan can keep track of that.

[1] http://projects.archlinux.org/pacman.git/commit/?id=f489e969
Comment by Lukas Fleischer (lfleischer) - Friday, 18 March 2011, 15:05 GMT
Just another evil cross-link for reference: http://mailman.archlinux.org/pipermail/pacman-dev/2011-March/012684.html

Maybe we should rename this bug or open another one as this bug's original description doesn't really outline the actual root of the problem.

Loading...