Bug 237069 - lang/gcc8: Fails to upgrade: cp: symlink: libcc1plugin.so.0.0.0: File exists
Summary: lang/gcc8: Fails to upgrade: cp: symlink: libcc1plugin.so.0.0.0: File exists
Status: Closed DUPLICATE of bug 223943
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: arm64 Any
: --- Affects Some People
Assignee: Bryan Drewery
URL:
Keywords:
Depends on: 223943
Blocks:
  Show dependency treegraph
 
Reported: 2019-04-07 11:57 UTC by chris
Modified: 2021-10-29 21:40 UTC (History)
3 users (show)

See Also:


Attachments
Build output (613.30 KB, application/gzip)
2019-04-07 11:57 UTC, chris
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description chris 2019-04-07 11:57:40 UTC
Created attachment 203440 [details]
Build output

--->  Deinstalling 'gcc8-8.3.0'
--->  Preserving /usr/local/lib/gcc8/gcc/aarch64-portbld-freebsd12.0/8.3.0/plug$
cp: symlink: libcc1plugin.so.0.0.0: File exists
Copy failed!
[Reading data from pkg(8) ... - 340 packages found - done]
** Listing the failed packages (-:ignored / *:skipped / !:failed)
        ! gcc8-8.3.0    (copy failed)
** Listing the failed packages (-:ignored / *:skipped / !:failed)
        ! lang/gcc8 (gcc8-8.3.0)        (uninstall error)
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2019-04-07 12:23:35 UTC
What command is being run to upgrade lang/gcc8?

If it's portupgrade (which I'm guessing it is), this looks like fallout from bug 223943 (see bug 223943 comment 12). portupgrade maintainer is CC'd.

Similar issues:

bug 231694 
bug 227599
Comment 2 chris 2019-04-07 12:57:46 UTC
Yes, thankyou. I am using portupgrade, and have noted the reference bug that you note.

Chris
Comment 3 Gerald Pfeifer freebsd_committer freebsd_triage 2019-04-07 21:59:51 UTC
Bryan, may I assign this to you due to 223943 being the cause of this?
Comment 4 Gerald Pfeifer freebsd_committer freebsd_triage 2021-10-29 20:22:15 UTC
Bryan, what shall we do about this?
Comment 5 Bryan Drewery freebsd_committer freebsd_triage 2021-10-29 21:40:09 UTC
Sorry I missed this. I think this is just a dupe of Bug 223943 given it is a very specific behavior of portupgrade and really has nothing to do with the gcc port.

*** This bug has been marked as a duplicate of bug 223943 ***