On Thu, Mar 15, 2018 at 02:58:56PM +0100, Andrea Bolognani wrote: > On Thu, 2018-03-15 at 13:33 +0000, Daniel P. Berrangé wrote: > > The 'brew upgrade' command is pulling in the python2 package which > > promptly fails due to clashing symlinks installed by the new python > > package (which is python3 based): > > > > ==> Pouring python@2-2.7.14_3.sierra.bottle.tar.gz > > Error: The `brew link` step did not complete successfully > > The formula built, but is not symlinked into /usr/local > > Could not symlink bin/2to3-2 > > Target /usr/local/bin/2to3-2 > > is a symlink belonging to python. You can unlink it: > > brew unlink python > > To force the link and overwrite all conflicting files: > > brew link --overwrite python@2 > > To list all files that would be deleted: > > brew link --overwrite --dry-run python@2 > > > > By running 'brew unlink python' we can get rid of the python3 links that > > we didn't want in the first place and avoid this error. > > The behavior of homebrew with respect to linking seems completely > insane to me. Why would you need to manually apply a workaround in > order to upgrade an existing system? I don't think this is really intentional - it just seems like part of the giant python disaster the packagers have created for themselves... > > Anyway, this seems to work, so > > Reviewed-by: Andrea Bolognani <abologna@xxxxxxxxxx> > > -- > Andrea Bolognani / Red Hat / Virtualization Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
