Am Sat, 26 Apr 2014 17:17:22 +0400 schrieb Boris Samorodov <b...@passap.ru>:
> 26.04.2014 16:35, Boris Samorodov пишет: > > 26.04.2014 15:19, Dr. Peter Voigt пишет: > > > >> Well after this error has been solved under CUPS 1.7.1 > >> > >> http://lists.freebsd.org/pipermail/freebsd-ports/2014-April/091306.html > > > > How was is solved? > > OK, I've traced the thread ad realized that you managed to fix the > problem by a new version of cups-filters. Right? > > How did you upgrade your ports? Which versions of printing ports > do you have now? > > FYI: there has been some changes at cups-* port at the last few days. > Make sure you have the latest ports tree and appropriate ports. > The latest ports tree update provides cups-filters-1.0.53. This resolves the filter error. According to http://www.freshports.org/print/cups-filters/ it has arrived today. My latest cron based ports tree update was yesterday evening :-) # pkg version -v |grep cups cups-1.7.2 = up-to-date with port cups-base-1.7.2 = up-to-date with port cups-client-1.7.2 = up-to-date with port cups-filters-1.0.53 = up-to-date with port cups-image-1.7.2 = up-to-date with port cups-pstoraster-8.15.4_7 = up-to-date with port gutenprint-cups-5.2.8_1 = up-to-date with port Thanks for fixing that fast! Should I still execute: # pkg delete -f cups-image\* Regards, Peter _______________________________________________ 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"