Bug 227599

Summary: emulators/linux_base-c6: Portupgrade fails due to "cp: symlink: libc-2.12.so: File exists" error
Product: Ports & Packages Reporter: Terry Kennedy <terry-freebsd>
Component: Individual Port(s)Assignee: Bryan Drewery <bdrewery>
Status: New ---    
Severity: Affects Only Me CC: dpetrov67, rene, terry-freebsd
Priority: ---    
Version: Latest   
Hardware: Any   
OS: Any   
See Also: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237069
Bug Depends on: 223943    
Bug Blocks:    
Description Flags
Transcript of failed portupgrade none

Description Terry Kennedy 2018-04-18 01:58:51 UTC
Created attachment 192607 [details]
Transcript of failed portupgrade

Attempting to portupgrade linux_base-c6-6.9_6 to linux_base-c6-6.9_7 on FreeBSD 10-stable (r331931 amd64) fails with:

--->  Backing up the old version
--->  Uninstalling the old version
[Reading data from pkg(8) ... - 336 packages found - done]
--->  Deinstalling 'linux_base-c6-6.9_6'
--->  Preserving /compat/linux/usr/lib/i686/nosegneg/libc.so.6 as /usr/local/lib/compat/pkg/libc.so.6
cp: symlink: libc-2.12.so: File exists
Copy failed!
[Reading data from pkg(8) ... - 336 packages found - done]
** Listing the failed packages (-:ignored / *:skipped / !:failed)
        ! linux_base-c6-6.9_6   (copy failed)
** Listing the failed packages (-:ignored / *:skipped / !:failed)
        ! emulators/linux_base-c6 (linux_base-c6-6.9_6) (uninstall error)

I don't believe I have made any local changes in this area, and the file in question appears in the ports plist, so I think this is a port error.

Complete transcript of the session attached.
Comment 1 Tijl Coosemans freebsd_committer 2018-04-18 08:25:33 UTC
It's a portupgrade bug.  It's trying to preserve libc.so.6 and i686/nosegneg/libc.so.6 both in the same destination.
Comment 2 Rene Ladan freebsd_committer 2019-12-31 15:34:49 UTC
FYI, Linux c6 ports are being removed today.
Comment 3 Terry Kennedy 2019-12-31 18:57:17 UTC
(In reply to Rene Ladan from comment #2)

Let's not close this PR, though - the same thing happens with the c7 port. I ran into it just the other day when c7 was updated.