FS#10883 - lib32-e2fsprogs 1.40.8-1 contains de-referenced symlinks

Attached to Project: Community Packages
Opened by David Spicer (azleifel) - Thursday, 10 July 2008, 19:39 GMT
Last edited by Mikko Seppälä (Neverth) - Friday, 18 July 2008, 13:47 GMT
Task Type Bug Report
Category Backend
Status Closed
Assigned To Mikko Seppälä (Neverth)
Architecture All
Severity Medium
Priority Normal
Reported Version 1.5.1
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

See discussion at http://bbs.archlinux.org/viewtopic.php?id=51469. lib32-e2fsprogs 1.40.8-1 in [community] contains de-referenced library symlinks, causing ldconfig to issue "not a symbolic link" errors each time it is run, e.g.

/sbin/ldconfig: /opt/lib32/lib/libe2p.so.2 is not a symbolic link

The PKGBUILD for lib32-e2fsprogs in ABS (but not the older version still available from the AUR page) uses the install command to copy the libs from the 32 bit package. The consequence is that the symbolic links get dereferenced. Changing the line

install -m755 $startdir/src/lib/* $startdir/pkg/opt/lib32/lib/

in the build() section to

cp -dp $startdir/src/lib/* $startdir/pkg/opt/lib32/lib/

as used in other lib32 PKGBUILDs fixes the problem.
This task depends upon

Closed by  Mikko Seppälä (Neverth)
Friday, 18 July 2008, 13:47 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed, only affected people with /opt/lib32 stuff in their linker config, I dont have them there so I only heard about it today.
New pkg alredy upped with pkgrel 1.1
Comment by Giorgos (ranger) - Sunday, 13 July 2008, 12:37 GMT
Confirmed.
But did you check the PKGBUILD for lib32-e2fsprogs in ABS?
It doesn't use the line

install -m755 $startdir/src/lib/* $startdir/pkg/opt/lib32/lib/

It is quite different.
And the PKGBUILD in AUR provides exactly the same version with the one in ABS (1.40.8-1) but hasn't the two patches.

Comment by David Spicer (azleifel) - Sunday, 13 July 2008, 12:46 GMT
Others were using the AUR version of the PKGBUILD (see forum thread). I just wanted to be different ;-)
Comment by Giorgos (ranger) - Sunday, 13 July 2008, 13:37 GMT
I have seen the forum thread. But I am not sure if this solution can be applied to the ABS PKGBUILD.

Anyway, its 3 days and this so simply bug is still unconfirmed and assigned to no-one, thats strange...
Comment by David Spicer (azleifel) - Sunday, 13 July 2008, 16:49 GMT
Strange indeed. It's also odd that there are essentially identical [community] and [unsupported] versions of the same package and perhaps this is causing some confusion - I see that a comment has recently been added to the AUR package page about correcting "cp -rPf" to "cp -r" to fix the symbolic link problem! In the meantime, I just sync'ed ABS and the PKGBUILD there has:

build() {
install -d $startdir/pkg/opt/lib32/lib/
install -m755 $startdir/src/lib/* $startdir/pkg/opt/lib32/lib/
}

whilst the AUR PKGBUILD has:

build() {
mkdir -p $startdir/pkg/opt/lib32/lib/
cp -rPf $startdir/src/lib $startdir/pkg/opt/lib32/
}

and neither applies any patches. When I rolled my own version I used:

build() {
install -d $startdir/pkg/opt/lib32/lib/
cp -dp $startdir/src/lib/* $startdir/pkg/opt/lib32/lib/
}

which is pretty much the same as the other lib32-* PKBUILDs in ABS.
Comment by David (staple) - Thursday, 17 July 2008, 23:18 GMT
annoying problem that should be fixed. really easy solution detailed already...

Loading...