From owner-freebsd-questions@freebsd.org Tue Nov 8 17:45:43 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5FB27C370E1 for ; Tue, 8 Nov 2016 17:45:43 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (ns.dreamchaser.org [66.109.141.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0F7238F for ; Tue, 8 Nov 2016 17:45:42 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [192.168.151.122]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id uA8HjSTZ012607; Tue, 8 Nov 2016 10:45:29 -0700 (MST) (envelope-from freebsd@dreamchaser.org) Reply-To: freebsd@dreamchaser.org Subject: Re: cups problems on 10.3 release both Epson and HP 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> <20161107124357.1d278104@kalimero.tijl.coosemans.org> <20161107211429.7acb7e6b@kalimero.tijl.coosemans.org> <32481b91-6d29-7bea-6376-9a4c1b61016e@dreamchaser.org> <20161108120632.31037497@kalimero.tijl.coosemans.org> To: Tijl Coosemans Cc: FreeBSD Mailing List From: Gary Aitken Message-ID: Date: Tue, 8 Nov 2016 10:45:28 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <20161108120632.31037497@kalimero.tijl.coosemans.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [192.168.151.101]); Tue, 08 Nov 2016 10:45:30 -0700 (MST) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2016 17:45:43 -0000 On 11/08/16 04:06, Tijl Coosemans wrote: >> 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? > 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' thanks, that helped in more ways than one > 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. thanks again! Gary