Dominic Fandrey wrote: > Pav Lucistnik wrote: >> Dominic Fandrey píše v st 27. 05. 2009 v 18:43 +0200: >> >>> During my last run of 'pkg_upgrade -a', cups-client forgot to install >>> the library libcups.so.2, which I fortunately recognized due to my >>> routine of running pkg_libchk after every package/port upgrade. >>> >>> Running 'pkg_upgrade cups-client' fixed that problem. The interesting >>> part is, that the reinstallation of cups-client was done from the >>> same package. So either pkg_add, tar or the file system were to blame, >>> because the package is without fault. >>> >>> I expect that this unreliability of pkg_add (or the underlying systems) >>> has a severe impact on my further development of pkg_upgrade. >> I think it was entirely different story -- >> >> installation of cups-client (put libcups on disc) >> upgrade of cups-base (remove libcups from disc) >> > > Well, that's possible, but why would cups-base perform such an evil > deed?
Stupid me, I just read UPDATING. That explains everything. But that puts the question forward how to deal with this. People using pkg_upgrade do not require a ports tree and hence do not have UPDATING. > It's a very soothing suggestion, though. At least as far as pkg_upgrade > is concerned. _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
