cups problems on 10.3 release both Epson and HP

Tijl Coosemans tijl at
Tue Nov 8 11:06:46 UTC 2016

On Mon, 7 Nov 2016 15:01:22 -0700 Gary Aitken <freebsd at> wrote:
> On 11/07/16 13:14, Tijl Coosemans wrote:
>> On Mon, 7 Nov 2016 11:56:14 -0700 Gary Aitken <freebsd at> wrote:  
>>> I'm guessing I need cups-pstoraster for the missing piece?
>>> If I try to add 
>>>   print/cups-pstoraster
>>> which also installs
>>>   print/cups-client
>>>   print/cups-image
>>> I can't because of conflicts:
>>>   pkg-static: cups-client-2.0.3_2 conflicts with cups-2.2.1
>>>     (installs files into the same place).
>>>     Problematic file: /usr/local/bin/cups-config
>>> It's unclear to me what gets installed from the print/cups port;
>>> I had thought it was a meta-port that would install cups-base and others
>>> depending on the options, but apparently not.  What is the difference 
>>> between print/cups-base and print/cups?  
>> These ports no longer exist.  cups-pstoraster is now part of cups-filters
>> and cups-base, cups-client and cups-image are part of print/cups.  If
>> you still see these ports your ports tree isn't updating properly.  
> hmmm.  Yes, I still see them.
> This is a new-ish 10.3 install.  
> UPDATING implies they were trashed 20160311; why would they still be there
> or at least not marked obsolete?
> This sys was installed within the last month and updated, now at p7;
> portsnap fetch & update several times since and including over the weekend.
> Is there an easy way to discover and remove all "no longer existing" ports?
> Or do I have to remove /usr/ports/* and rebuild everything?
> again, thanks for helping me work through this.

I haven't used portsnap in a long while and I don't know the details of
how it works, but I believe it doesn't check if your ports tree matches
upstream.  It simply downloads updates and applies them.  So if there was
a problem during one of these updates you're stuck with them.  One source
of trouble that I know of is when /var is a separate partition and
portsnap runs out of disk space there.  If you think that can happen on
your machine you can make portsnap use a different directory by setting
WORKDIR in /etc/portsnap.conf to a different value.

You can get a list of ports that should be gone with this command:
/bin/sh -c 'awk -F\| "/^[^#]/{print \$1}" MOVED | xargs ls -d 2>/dev/null'

But the only way to be sure you have all changes is to delete everything
under /usr/ports and /var/db/portsnap and run 'portsnap fetch extract'.
I don't think you have to rebuild all packages.  A regular check for
updates with portmaster/portupgrade/... should be enough.

More information about the freebsd-questions mailing list