I second this. Ran into the exact same problem - it would be nice to add this to the man page to make pkg_add easier to understand.
-----Original Message----- From: frantisek holop [mailto:min...@obiit.org] Sent: 07 January 2010 03:40 To: ports@openbsd.org Subject: pkg_add collisions hi there, i have just run into the following situation: $ sudo pkg_add gimp Collision: the following files already exist ... /usr/local/include/gimp-2.0/libgimp/gimppalette.h (same checksum) /usr/local/include/gimp-2.0/libgimp/gimppalette_pdb.h (same checksum) /usr/local/include/gimp-2.0/libgimp/gimppalettemenu.h (same checksum) /usr/local/include/gimp-2.0/libgimp/gimppalettes.h (same checksum) /usr/local/include/gimp-2.0/libgimp/gimppalettes_pdb.h (same checksum) ... /usr/local/share/locale/ca/LC_MESSAGES/gimp20-std-plug-ins.mo (same checksum) Error from ftp://ftp.fr.openbsd.org/pub/OpenBSD/snapshots/packages/i386/gimp-2.6.7p 3.tgz: ftp: -: short write 421 Service not available, remote server has closed connection. my first reaction was: there might be a -F option to handle this. but the man page mentions collisions exactly once, someplace else. what i was looking for is actually -F repair. it does the right thing and proceeds with the installation after warning about the collisions. could the word "collision" be added in some form to the -F repair section of the man page? - repair attempt to repair installed packages with miss- - ing registration data. + repair resolve collisions and attempt to repair ins- talled packages with missing registration data. -f -- i am so open-minded my brain falls out.
