#52450: atk @2.22.0_0: does not activate following install/upgrade due to false positive file exists error with gtk-docs on OS X 10.9 (Mavericks) ---------------------+-------------------------------- Reporter: ben@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: atk | ---------------------+-------------------------------- Comment (by ben@…): It could be, a different filesystem actually. Currently /opt/local/var/macports/build is actually a sym link to an external drive in order to keep sometimes disk hungry builds from interfering with other things on the laptop. I'll check ... Okay, yes, you're right. The laptop's SSD is case insensitive, but the external drive is Mac OS Extended (Case-sensitive, Journaled). So that's why it extracts in build, but then the copy and activation fails. Excuse me a moment while I LART myself. Still, with the fs difference in those volumes, restoring the build dir to the laptop won't help, the failure will just occur earlier in the process. If they were the other way around it'd be different, of course, but I've yet to see a technical fault that could be solved with wishing it were so. ;) Thanks for lodging the gnome bug because obviously it's only a matter of time before it hits someone else. In the mean time, is it possible to change the macports copy function to automatically rename files when copying and attempt to continue, even if that is restricted to certain file types where a rename won't hurt (as in the case of docs where at worst there's a URI link failure, unlike with libs or executables)? Obviously that shouldn't be default behaviour, but there's a pretty good case for it being a desirable option when a couple of HTML files are enough to kill the upgrade of everything from bash to wine-devel. -- Ticket URL: <https://trac.macports.org/ticket/52450#comment:9> MacPorts <https://www.macports.org/> Ports system for the Mac operating system