Date: Tue, 8 Nov 2016 12:06:32 +0100 From: Tijl Coosemans <tijl@coosemans.org> To: Gary Aitken <freebsd@dreamchaser.org> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: cups problems on 10.3 release both Epson and HP Message-ID: <20161108120632.31037497@kalimero.tijl.coosemans.org> In-Reply-To: <32481b91-6d29-7bea-6376-9a4c1b61016e@dreamchaser.org> References: <2134837b-14ed-a35e-aec0-2490e268659d@dreamchaser.org> <20161105233720.586fd471@kalimero.tijl.coosemans.org> <0d2306ad-8f96-c9bc-78ed-af0aea4daf50@dreamchaser.org> <20161106121440.221ba2e8@kalimero.tijl.coosemans.org> <e6ac5133-613a-1546-39bc-56030521640e@dreamchaser.org> <20161107124357.1d278104@kalimero.tijl.coosemans.org> <bcc924aa-5a7f-4368-037c-8380ab9cabcd@dreamchaser.org> <20161107211429.7acb7e6b@kalimero.tijl.coosemans.org> <32481b91-6d29-7bea-6376-9a4c1b61016e@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 7 Nov 2016 15:01:22 -0700 Gary Aitken <freebsd@dreamchaser.org> wrote:
> On 11/07/16 13:14, Tijl Coosemans wrote:
>> On Mon, 7 Nov 2016 11:56:14 -0700 Gary Aitken <freebsd@dreamchaser.org> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20161108120632.31037497>