cups update

2016-03-12 Thread Stari Karp
Hi! In /usr/ports/UPDATING is: "20160311:   AFFECTS: print/cups-base, print/cups-client, print/cups-image   AUTHOR: t...@freebsd.org   The cups-base, cups-client and cups-image packages have been combined   into one cups package.  If you build your own ports the easiest way to   update is to

Re: cups update

2016-03-12 Thread Walter Schwarzenfeld
Should be solved by a reinstall of cups-filters. No problem on my machine (10.2-RELEASE). ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to

Re: cups update

2016-03-12 Thread Tijl Coosemans
On Sat, 12 Mar 2016 06:50:36 -0500 Stari Karp wrote: > Hi! > > In /usr/ports/UPDATING is: > > "20160311: >   AFFECTS: print/cups-base, print/cups-client, print/cups-image >   AUTHOR: t...@freebsd.org > >   The cups-base, cups-client and cups-image packages have been

Re: cups update

2014-03-31 Thread Johan Hendriks
Ajtim schreef: Hi! I try to update: === The following actions will be taken if you choose to proceed: Upgrade cups-base-1.5.4_1 to cups-base-1.7.1 Upgrade cups-client-1.5.4_1 to cups-client-1.7.1 Upgrade cups-image-1.5.4_1 to cups-image-1.7.1 Upgrade

Re: cups update

2014-03-31 Thread Boris Samorodov
31.03.2014 11:38, Johan Hendriks пишет: Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts with cups-image-1.5.4_1 (installs files into the same place). Problematic file: /usr/local/include/cups/raster.h Yep, the problematic file has moved form cups-image (1.5.x) to

Re: cups update

2014-03-31 Thread Johan Hendriks
Boris Samorodov schreef: 31.03.2014 11:38, Johan Hendriks пишет: Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts with cups-image-1.5.4_1 (installs files into the same place). Problematic file: /usr/local/include/cups/raster.h Yep, the problematic file has moved form

Re: cups update

2014-03-31 Thread Boris Samorodov
31.03.2014 12:26, Johan Hendriks пишет: Boris Samorodov schreef: 31.03.2014 11:38, Johan Hendriks пишет: Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts with cups-image-1.5.4_1 (installs files into the same place). Problematic file: /usr/local/include/cups/raster.h

Re: cups update

2014-03-31 Thread Ajtim
On Monday 31 March 2014 12:00:51 Boris Samorodov wrote: 31.03.2014 11:38, Johan Hendriks пишет: Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts with cups-image-1.5.4_1 (installs files into the same place). Problematic file: /usr/local/include/cups/raster.h Yep, the

Re: cups update

2014-03-31 Thread Boris Samorodov
31.03.2014 13:56, Ajtim пишет: On Monday 31 March 2014 12:00:51 Boris Samorodov wrote: 31.03.2014 11:38, Johan Hendriks пишет: Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts with cups-image-1.5.4_1 (installs files into the same place). Problematic file:

Re: cups update

2014-03-31 Thread Ajtim
On Monday 31 March 2014 14:16:34 you wrote: 31.03.2014 13:56, Ajtim пишет: On Monday 31 March 2014 12:00:51 Boris Samorodov wrote: 31.03.2014 11:38, Johan Hendriks пишет: Installing cups-client-1.7.1...pkg-static: cups-client-1.7.1 conflicts with cups-image-1.5.4_1 (installs files into

cups update

2014-03-30 Thread Ajtim
Hi! I try to update: === The following actions will be taken if you choose to proceed: Upgrade cups-base-1.5.4_1 to cups-base-1.7.1 Upgrade cups-client-1.5.4_1 to cups-client-1.7.1 Upgrade cups-image-1.5.4_1 to cups-image-1.7.1 Upgrade py27-Jinja2-2.7.1_1 to

cups issue after gutenprint-cups update

2009-12-25 Thread Andriy Gapon
I recently upgraded gutenprint* ports, including gutenprint-cups-5.2.4, and after that I couldn't print to my CUPS/SMB printer any more. In cups logs I found that it tried to execute /usr/local/libexec/cups/filter/rastertogutenprint.5.1, but it was replaced by

cups update commited

2006-08-06 Thread Ion-Mihai Tetcu
Hi, I just updated cups to 1.2.2 and also a lot of fixes to the port. If some things still don't work please submit PRs; please put in as many details as possible and take a look first to see if the problem is known / fixed upstream. Thanks, -- IOnut - Un^d^dregistered ;) FreeBSD user