Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 687514

Summary: net-print/cndrvcups-common-lb: symlink from /usr/lib/libc3pl.so to /usr/lib32/libc3pl.so disrupting 17.1 profile conversion
Product: Gentoo Linux Reporter: niemand_bugs
Component: Current packagesAssignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed>
Status: UNCONFIRMED ---    
Severity: normal CC: bugs.reporter, Dan.Johansson, erkiferenc, hakimian, mgorny
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
See Also: https://bugs.gentoo.org/show_bug.cgi?id=642138
Whiteboard:
Package list:
Runtime testing required: ---
Bug Depends on:    
Bug Blocks: 506276    
Attachments: diff to prevent the creation of a symlink

Description niemand_bugs 2019-06-06 13:34:44 UTC
The ebuild 3.60-r1 for cndrvcups-common-lb installs libc3pl.so in /usr/lib32 and creates a symlink pointing to it in /usr/lib, thus preventing the migration trough unsymlink-lib.

Reproducible: Always

Steps to Reproduce:
1. sudo emerge net-print/cndrvcups-common-lb
2. sudo unsymlink-lib --analyze
Actual Results:  
The migration is not possible due to a libc3pl.so existing both in /usr/lib and /usr/lib32.

Expected Results:  
The collision shouldn't have existed.
Comment 1 niemand_bugs 2019-06-06 13:36:45 UTC
Created attachment 578978 [details, diff]
diff to prevent the creation of a symlink
Comment 2 Pacho Ramos gentoo-dev 2019-06-06 17:38:43 UTC
The symlink is only done with SYMLINK_LIB=yes only as it's needed at runtime. Other packages like chrome-gnome-shell, dracut or distcc are relying on this hacks to not break with other systems... but I don't know how to "inform" unsymlink-lib about this situation . 

@Michal, what would be the proper way to provide the symlink for SYMLINK_LIB=yes but not for the others?

Thanks
Comment 3 Brian Evans Gentoo Infrastructure gentoo-dev 2019-06-11 18:19:21 UTC
*** Bug 687876 has been marked as a duplicate of this bug. ***